The script content on this page is for navigation purposes only and does not alter the content in any way.

A Overview of the EM Prerequisite Kit

This appendix describes the Enterprise Manager Prerequisite Kit utility (EM Prerequisite Kit) that the installation wizard runs every time it installs or upgrades your Enterprise Manager. In particular, this appendix covers the following:

A.1About EM Prerequisite Kit

The EM Prerequisite Kit is a command line utility that runs repository-related prerequisite checks in your environment to ensure that you meet all the repository requirements for installing or upgrading an Enterprise Manager system.

The kit not only runs the prerequisite checks but also takes corrective actions automatically, to the extent possible, when a prerequisite check fails. The kit also takes postrequisite steps automatically to revert the corrective actions taken and ensure that the system is back to how it was before installing or upgrading the Enterprise Manager system.

The EM Prerequisite Kit is run internally by the Enterprise Manager Installation Wizard while installing or upgrading an Enterprise Manager system. In addition, you can run the kit yourself beforehand to ensure that your environment meets all the repository-related requirements.

WARNING:

If you plan to use a database instance that was created with a preconfigured Management Repository using the database templates offered by Oracle, then make sure you pass the following parameter while invoking the EM Prerequisite Kit.

-componentVariables repository:EXECUTE_CHECKS_NOSEED_DB_FOUND:false

A.2Running the EM Prerequisite Kit

This section describes the following ways of running the EM Prerequisite Kit:

A.2.1Running the EM Prerequisite Kit from the Software Kit (for fresh install) or from the OMS Home (for upgrade)

Although the EM Prerequisite Kit is run internally by the Enterprise Manager Installation Wizard while installing or upgrading an Enterprise Manager system, you can choose to run the kit yourself beforehand to ensure that your environment meets all the repository-related requirements. This helps in detecting and fixing repository-related issues beforehand, thus enabling a much smoother installation or upgrade experience.

This section describes how you can run the EM Prerequisite Kit from the software Kit (DVD, downloaded location) for fresh installation, or from the OMS home for upgrade.

The EM Prerequisite Kit is available in the following location of the software kit (DVD, downloaded software):

<DVD/SW_Download_Location>/install/requisites/bin/emprereqkit

Note:

Ensure that the user running the EM Prerequisite Kit has write permission to the central inventory.

Note:

On Microsoft Windows, run emprereqkit.bat.

To run the EM Prerequisite Kit, do one of the following:

To view a list of repository requirements to be met without taking any corrective actions, run the EM Prerequisite Kit from the software kit (DVD, downloaded software) as SYS user with the following arguments. To learn about the other arguments that can be passed with the kit, see Section A.2.1.3.

To run the prerequisite utility and also take corrective actions to meet the repository requirements, run the EM Prerequisite Kit from the software kit (DVD, downloaded software) as SYS user with the following additional arguments. To learn about the other arguments that can be passed with the kit, see Section A.2.1.3.

A.2.1.2 Running the EM Prerequisite Kit from the OMS Home (for upgrade)

Once the Enterprise Manager system is installed or upgraded, the EM Prerequisite Kit and all the other files and directories present in the install/requisites/ directory of the software kit (DVD, downloaded software) are copied to the following location in the OMS home.

$<OMS_HOME>/install/requisites/bin/emprereqkit

Note:

The default XML files related to the prerequisite checks, which are stored in the install/requisites/list directory on the software kit (DVD, downloaded software), are current at the time of the release of the product. However, after the release of the product, if a new prerequisite check is introduced or if an existing prerequisite check is updated, then you must do one of the following:

A.2.1.3 Supported Additional Arguments for EM Prerequisite Kit

Table A-1 describes the additional arguments you can pass while invoking the EM Prerequisite Kit:

Table A-1 Arguments Supported by EM Prerequisite Kit

Option

Optional or Mandatory

Value Required?

Description

Example

-configurationType

Optional

Yes

Enables performing prerequisite checks for different repository configurations such as small, medium, and large. If you do not pass this option, then by default, the prerequisite checks are run for medium deployment size.

-showPostCorrectiveActions lists the post-corrective actions that will be taken for the prerequisite checks for which corrective actions were taken.

-runPostCorrectiveActions takes post-corrective actions for the prerequisite checks for which corrective actions were taken. In other words, reverts to values that existed before corrective actions were taken.

Important: If you passed -prereqResultLoc with -runPrerequisites, then pass -prereqResultLoc with the following options also, and specify the same custom location:

-showCorrectiveActions

-runCorrectiveActions

-showPostCorrectiveActions

-runPostCorrectiveActions

Note: Show actions must be independent, that is, they should not be combined with any other action.

The default XML files related to the prerequisite checks are current at the time of the release of the product. However, after the release of the product, if a new prerequisite check is introduced or if an existing prerequisite check is updated, then you can download the new or updated XMLs either manually or using Self Update.

If you have XMLs for two higher versions (for example, for 12.1.0.4.0 and 12.1.0.5.0), then while upgrading, you can run the prerequisite checks for even one of them by passing the -upgradeVersion argument.

-upgradeVersion 12.1.0.5.0

-logLoc

Optional

Yes

Specify the absolute path to a directory where the logs of the execution of the EM Prerequisite Kit utility can be stored. The default location is <prereqResultloc>/prerequisiteResults/log.

-logLoc /scratch/logs

-runOnlyFor

Optional

Yes

Specify the components that must be selected instead of the XML files for checking the prerequisites.

{comp1|<version1>, comp2|<version2>}]

If there are two prerequisite XML files with the same component name, then the <version*> is used to select the correct one. This option is particularly useful when running the prerequisites for installing plug-ins.

-runOnlyFor "repository|11.2.0.43"

-responseFile

Optional

Yes

Specify the absolute path to a location where the response file is available.

-responseFile /scratch/response.rsp

-contextName

Optional

Yes

Specify a unique name for this run. If you do not specify this, a default name with the format executionType_timestamp is created.

-contextName 11.2.0.1

-componentVariables

Optional

Yes

Specify the name and value of the component variable in the following format:

component_name:variable_name:variable_value

For example:

global:EM_REPOS_USER:sysman

You can pass as many component variables as you want, but ensure that you separate them by a comma.

For example:

global:EM_REPOS_USER:sysman,repository:DB_VERSION:10.2.0.5.0

-componentVariables global:EM_REPOS_USER:sysman

-logInDB

Optional

Yes

Defaults to true and stores the result XMLs in the database. If you do not want to store them in the database, pass this option and specify false.

-logInDB false

-stopExecOnFirstError

Optional

No

Stops the utility the first time it encounters an error, and does not run the remaining prerequisites.

Note: This action must be executed in combination with runPrerequisites.

This option gives details of various parameters which can be passed to EM Prerequisite Kit.

emprereqkit -help

A.2.2Running the EM Prerequisite Kit Using EM CLI for Upgrade

This section describes how you can run the EM Prerequisite Kit using Enterprise Manager Command Line Interface (EM CLI). However, at the moment, using EM CLI you can only view the list prerequisites and run the prerequisite checks for upgrade. In particular, this section covers the following:

A.2.2.3 Description of the Parameters Passed While Running the EM Prerequisite Kit Using EM CLI

db_user

Enter SYS. The connection to the database is established using this user account.

db_password

Enter the password for the SYS database user account.

db_role

Enter sysdba.

repos_user

Enter SYSMAN. The prerequisite checks will be run using this user account.

prerequisite_xml_root_dir

Enter the absolute path to the requisites/list directory where the XML files are available. The XML files may be in a subdirectory within the requisites/list directory, but make sure the path you enter leads only up to the list directory. The following is the location:

$<OMS_HOME>/install/requisites/list

prerequisite_resource_locs

Enter the absolute path to the directory where the plug-in .opar files or the platform binaries, which contain the XML files for the prerequisite checks, are present. If you are entering the path to the plug-in .opar files, then make sure the you follow the format plugin_id=<plugin_home>.

log_loc

Enter the absolute path to a directory where the logs of the execution of the EM Prerequisite Kit can be stored.

upgrade_version

Enter the version of Enterprise Manager to which you are upgrading. For example, 12.1.0.5.0.

(Only for Upgrade to Next Enterprise Manager Cloud Control Software Release) You can download the latest version of EM Prerequisite Kit from the Self Update framework as follows:

In Cloud Control, from the Setup menu, select Extensibility, and then select Self Update.

On the Self Update page, download the new version of XMLs under the entity EM Deployment Prerequisite Resources Updates, if there are any available.

Once you download and apply these updates, you cannot rollback to the previous version of XMLs.

If you have XMLs for two higher versions (for example, for 12.1.0.4.0 and 12.1.0.5.0), then while upgrading, you can run the prerequisite checks for even one of them by passing the -upgrade_version argument.

When you run the prerequisite checks using these revised XMLs for your next deployment, the revised XMLs are copied to the Management Repository automatically. If the downloaded revised XMLs are more recent than the ones available on the DVD of next Enterprise Manager Cloud Control software release, then the Enterprise Manager Installation Wizard uses these revised XMLs directly from the Management Repository instead of the ones available on the DVD.

Do not run multiple emcli run_prerequisites commands in parallel (from different EM CLI clients) to run the prerequisite checks with the downloaded revised XMLs and copy the XMLs to the Management Repository.

A.3Viewing the Results of the Prerequisite Checks Run by the EM Prerequisite Kit

Every time the EM Prerequisite Kit is run, the results of the prerequisite checks run for a particular component are stored in an instance XML file. The instance XML file has the file name <component>.xml. The results are in the same format as the information stored in the prerequisite XML files. The only difference is the new column that indicates the actual result of the prerequisite check.

Table A-2 lists the instance file locations depending on how the EM Prerequisite Kit was invoked.

Note: When you provide prereqResultLoc value, the result xml location is as mentioned above. Else, the result xml location is <Current Directory>/ prerequisiteResults/resultXMLs/<time-stamp>

<prereqResultLoc>/resultXMLs/LATEST/

Note: When you provide prereqResultLoc value, the result xml location is as mentioned above. Else, the result xml location is <Current Directory>/ prerequisiteResults/resultXMLs/LATEST

Automatically Invoked by the Enterprise Manager Cloud Control Installation Wizard

<MW_HOME>/.gcinstall_temp/resultXMLs/<time-stamp>

Note: When you proceed through the installation wizard pages, EM Prerequisite Kit result XMLs are created in /tmp/OraInstall<timestamp>/emprereqkit/resultXMLs/<time-stamp>.

When install begins, the /tmp/OraInstall<timestamp>/emprereqkit/resultXMLs/<time-stamp> result xmls are copied to <MWHOME>/.gcinstall_temp/resultXMLs/<time-stamp>.

<MW_HOME>/.gcinstall_temp/resultXMLs/LATEST

Note: When you proceed through the installation wizard pages, EM Prerequisite Kit result xmls are created in /tmp/OraInstall<timestamp>/ emprereqkit/p; resultXMLs/LATEST.

When install begins, the /tmp/OraInstall<timestamp>/ emprereqkit/ resultXMLs/LATEST result xmls are copied to <MW_HOME>/.gcinstall_temp/resultXMLs/LATEST

Footnote 1 Instance File Location refers to the <time-stamp> directory that is created dynamically by the utility every time the EM Prerequisite Kit is run. The instance file created here is retained until you decide to delete it.

Footnote 2 Latest Instance File Location refers to a single, standard location maintained for the latest instance file created when the EM Prerequisite Kit was last run. The instance file created here is overwritten every time the utility is run.

Note:

The <prereqResultLoc> location refers to the location you enter for the -prereqResultLoc option while invoking the utility. If this option is not passed, then by default, the directory from where you invoke the utility is considered as the base directory, and a directory titled prerequisiteResults is dynamically created in it, and then the instance file is stored in it.

A.4Viewing the Log Files Created by the EM Prerequisite Kit

Table A-3 lists all the log files that are created every time the EM Prerequisite Kit is run.

Table A-3 EM Prerequisite Kit Log Files

Log File Name

Description

emprereqkit.log

Contains information about every step taken or action performed by the kit

emprereqkit.err

Contains only the error and stacktrace of the exceptions occurred

emprereqkit.out

Contains information about the status (pass or fail) of all the prerequisite checks that are run. It also contains detailed information regarding each prerequisite check.For example, prerequisite name, execution status, detailed recommendation (what queries are to be executed to correct the failed prerequisite), and so on.

<functional_area>.log

Contains information about the function area-specific prerequisite checks that are run. For example, repository.log that contains repository-specific performance-related prerequisite checks that are run. The repository.log is present in the <log location>/componentLog directory.

For example, $OraInventory/logs/emdbprereqs/LATEST/componentLog/repository.log

Table A-4 lists the log file locations depending on how the EM Prerequisite Kit was invoked. This table lists the locations for all the log files except for the emprereqkit.out file. For emprereqkit.out file, see the note after the table.

Note: When you provide logLoc as the value, the log location is as mentioned above. Else, it is <Current Directory>/prerequisiteResults/log/LATEST

<logLoc>/<time-stamp>

Note: When you provide logLoc as the value, the log location is as mentioned above. Else, it is <Current Directory>/ prerequisiteResults/log/<time-stamp>

Automatically Invoked by the Enterprise Manager Cloud Control Installation Wizard

<MW_HOME>/.gcinstall_temp/LATEST

Note: When you proceed through the installation wizard pages, EM Prerequisite Kit logs are created in either $OraInventory/logs/emdbprereqs/LATEST or /tmp/OraInstall<timestamp>/ emdbprereqs/LATEST

When install begins, the /tmp/OraInstall<timestamp>/emprereqkit logs are copied to <MW_HOME>/.gcinstall_temp/emprereq/LATEST

<MW_HOME>/.gcinstall_temp/<time-stamp>

Note: When you proceed through the installation wizard pages, EM Prerequisite Kit logs are created in either $OraInventory/logs/emdbprereqs/<timestamp> or /tmp/OraInstall<timestamp>/ emdbprereqs/<timestamp>

When install begins, the /tmp/OraInstall<timestamp>/ emdbprereqs/<time-stamp> logs are copied to <MW_HOME>/.gcinstall_temp/emprereq/<time-stamp>

Footnote 1 Latest Log File location refers to a single, standard location maintained for the latest log files created when the EM Prerequisite Kit was last run. The log files created here are overwritten every time the utility is run.

Footnote 2 Log File Location refers to the <time-stamp> directory that is created dynamically by the utility every time the EM Prerequisite Kit is run. The log file created here are retained until you decide to delete them.

Note:

When the EM Prerequisite Kit is run manually, the log file emprereqkit.out is stored in <prereqResultLoc>/log/<time-stamp>. The latest log file is stored in <prereqResultLoc>/log/LATEST/.

When the EM Prerequisite Kit is run internally by the Enterprise Manager Cloud Control Installation Wizard, the log file emprereqkit.out is stored in <MW_HOME>/.gcinstall_temp/log/<time-stamp>. And the latest log file is stored in <MW_HOME>/.gcinstall_temp/log/<LATEST>.

A.5Repository Prerequisite Checks Run by the EM Prerequisite Kit

Table A-5 describes all the repository prerequisites that the EM Prerequisites Kit checks. This section also describes how to manually check these prerequisites.

Table A-5 Repository Prerequisites

Prerequisite

Applies to Install/Upgrade

Automatic

Description

Basic Policy Requirements

Upgrade

No

Ensures that valid policy exists for MGMT_TARGETS.

To manually verify this, run the following query:

select 'EM_TARGET_POLICY' from dual where not exists (select policy_name from dba_policies where object_owner=SYSMAN' and pf_owner='SYSMAN' and object_name='MGMT_TARGETS') )

The query must not return any rows.

Active Jobs Requirements

Upgrade

No

Ensures that there are no background DBMS jobs currently running in the Repository Database.

To manually verify this, run the following query:

select count(*) FROM dba_jobs_running run_job,gv$session sess WHERE sess.sid=run_job.sid AND sess.schemaname='SYSMAN'

If the result of the query is 0 then there are no active DBMS jobs, if result is not 0 then wait for the active jobs to complete.

Checks if GVM Performance collection job is running

Upgrade

Yes

Ensures that the GVM Performance Metric Collection job is stopped and deleted.

To manually verify if a job named GVMPERFMETRICCOLL exists, run the following query:

Ensures that the parameter optimizer_capture_sql_plan_baselines is set to FALSE (or default).

The SQL plan baseline capture must never be turned on for the Management Repository. Enterprise Manager heavily depends on updated CBO statistics. If stale CBO statistics exist, the SQL plan baseline capture could cause bad execution plans to be used for critical functionality.

Current Availability Index Requirements

Install, Upgrade

No

Ensures that the current availability index is renamed to the following:

If you are running the kit before upgrading from 10g Release 5 (10.2.0.5) or 11g Release 1 (11.1.0.1) to 12c Release X (12.1.0.X), then set the current availability index to MGMT_CURRENT_AVAILABILITY_PK.

If you are running the kit before upgrading from one 12c Release X (12.1.0.X) release to another 12c Release X (12.1.0.X) release, then set the current availability index to EM_CURRENT_AVAILABILITY_PK.

My Oracle Support User Name Size Requirements

Upgrade

No

Ensures that the My Oracle Support user name is not longer than 239 characters. If it is, then you cannot upgrade.

ARU User Name Size Requirements

Upgrade

No

Ensures that the ARU user name is not longer than 239 characters. If it is, you cannot upgrade.

DBMS Package Requirements

Install, Upgrade

No

Ensures that you compile the required DBMS packages.

To manually compile the packages, log in to the database, where the Management Repository is configured, as SYS user, and run the following query to retrieve the list of invalid DBMS packages:

SELECT object_name, object_type FROM all_objects WHERE status = 'INVALID' AND object_name LIKE 'DBMS%'

If the package is invalid, run the following query:

For package:

ALTER PACKAGE <PACKAGE_NAME> COMPILE

For package body:

ALTER PACKAGE <PACKAGE_NAME> COMPILE BODY

If the packages do not compile successfully, contact Oracle Support.

Snapshot Log Requirements

Upgrade

No

Ensures that the snapshot logs are deleted from the tables.

Connector Configuration Table Requirements

Upgrade

No

Ensures that there is no bad data in the connector configuration table. If there is any, then run the following query to clean the table.

delete from mgmt_cntr_config where connector_guid is null or connector_type_guid is null;
commit;

Compatible Instance Parameter Requirements

Install, Upgrade

No

Ensures that the compatible instance parameter is set to the same version value as the database instance of the Management Repository. Any other value might result in unexpected problems, poor performance, or both.

If the constraints cannot be enabled for any reason, contact Oracle Support.

Enable Queue Requirements

Upgrade

No

Ensures that queues are enabled in the Repository Database.

To manually verify this, run the following query:

select count(*) from dba_queues where owner = 'SYSMAN' and queue_type like '%NORMAL_QUEUE%' and (enqueue_enabled like '%NO%' OR dequeue_enabled like '%NO%')

If result is not 0, use the following query to retrieve the list of disabled queue names:

select name, queue_table from dba_queues where owner = 'SYSMAN' and upper(queue_type) not like 'EXCEPTION_QUEUE' and (upper(enqueue_enabled) NOT LIKE '%YES%' OR upper(dequeue_enabled) NOT LIKE '%YES%'))

Execute the following SQL statement to enable the queue:

begin
dbms_aqadm.start_queue('<disabled_queue_name>');
end;

If the queue cannot be started, contact Oracle Support.

Trigger Requirements

Upgrade

No

Ensures that all the triggers in the Repository Database are not disabled.

If the result is 0, then add a new datafile with the autoextend attribute to the SYSTEM tablespace so it has at least one listed in the DBA_DATA_FILES view with autoextensible equal to 'YES'. Contact Oracle Support if there are any errors

emkey requirement

Upgrade

No

Ensures that the emkey is copied to the repository.

To manually verify this, run the following query:

select COUNT(*) from sysman.mgmt_repos_time_coefficient

If the result of the query is not 1, then copy the emkey.ora file from another OMS or backup machine to the ORACLE_HOME/sysman/config directory.

If the result of the query is not 0, then revoke EXEMPT ACCESS POLICY from SYSMAN and the roles.

For example:

revoke exempt access policy from SYSMAN

max_enabled_roles init parameter requirement

Install and Upgrade

No

Ensures that the max_enabled_roles parameter value is set such that it contains at least 3 more than the flattened roles granted to SYS.

To manually verify this, run the following query:

select 1 from DUAL where (select count(*) from v$instance where version like '9.%') = 0 or (select value from v$parameter where name like 'max_enabled_roles') > (select count(*) from dba_role_privs start with grantee='SYS' connect by prior granted_role=grantee)+2;

If the result of the query is not 1 then, increase the max_enabled_roles parameter to ensure it contains at least 3 more than the flattened roles granted to SYS.

To modify max_enabled_roles, perform the following steps:

Bring down all the OMS instances.

Bring down the database cleanly.

Modify the max_enabled_roles parameter in the init.ora or whichever is used by the database's initialization process.

Bring up the database cleanly.

Verify with v$parameter to ensure the parameter value is indeed increased.

PAF execution requirements

Upgrade

No

Ensures that no PAF executions are scheduled or running.

To manually verify this, run the following query, and note down the GUID of the running or scheduled deployment procedures.

To manually stop the running or scheduled deployment procedures, run the following query, and pass the GUID you noted down from the output of the preceding command:

emcli stop_instance -instance=<instance id from sql query>

Secured Agent requirements

Upgrade

No

Ensures that all the agents are secured with latest CA.

To know the list of agents to be secured, run the following command:

emcli get_ca_info -details

Pre-upgrade console patch requirements

Upgrade

No

Ensures that pre-upgrade patch is applied.

To manually verify this, run the following query:

select count(*) from all_objects where object_name ='PRE_UPGC_MASTER_INFO' and object_type='TABLE' and owner='SYSMAN'

If the result of the query is not 1, then apply pre-upgrade Console patch before upgrading.

Global Stale percentage requirements

Install and Upgrade

No

Ensures that global stale percentage is in between 5 and 25.

To manually verify this, run the following query:

select count(*) from dual where dbms_stats.get_prefs('STALE_PERCENT') between 5 and 25

The query result must be 1.

Account status requirements

Upgrade

No

Ensures that SYSMAN, MGMT_VIEW and ORACLE_OCM accounts are not locked or expired.

To manually verify this, run the following queries:

select account_status from dba_users where username='SYSMAN';
select account_status from dba_users where username='MGMT_VIEW';
select account_status from dba_users where username='ORACLE_OCM';

The query result must be OPEN.

SYSMAN schema requirements

Upgrade

No

Ensures that SYSMAN schema is present for upgrade.

To manually verify this, run the following query:

SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'

The query result must be 1.

Redo Log size requirement

Install and Upgrade

No

Ensures that the size of the log file is equal or greater than following the values defined for different installation types and deployment options:

Simple Installation: 300 MB or greater.

Advanced Installation:

- Small: 300 MB or greater

- Medium: 600 MB or greater

- Large: 1000 MB or greater

To manually verify this, run the following query:

select min(bytes) from v$log

Existing Database Not to Be in QUIESCE Mode

Install and Upgrade

No

Ensures that existing, certified Oracle Database is not in QUIESCE mode.

To manually verify this, run the following SQL in the database in the SYS role:

select active_state from v$instance;

The result returned must be NORMAL.

Existing Database Not to Have Database Control (only for fresh install)

Fresh Install

No

Ensures that your existing, certified Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.

To manually deconfigure the Database Control SYSMAN schema, follow these steps:

Verify whether your database has Database Control SYSMAN schema.

To do so, log in to the database as SYS user and run the following query:

SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'

If the result of this query is 1, then the database has this schema, so deconfigure it.

Before deconfiguring the Database Control, set the environment variable ORACLE_HOME to the Oracle home of the database, and ORACLE_SID to the SID of the database.

To deconfigure Database Control for a standalone database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

To deconfigure Database Control for a Real Application Cluster (Oracle RAC) database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

Note: If the deconfigure operation hangs, then refer to My Oracle Support note 375946.1

Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema

Fresh Install

No

Ensures that your existing, certified Oracle Database does NOT have the Enterprise Manager SYSMAN schema and the Metadata (MDS) schema already configured. These schemas can exist if you had configured the database for another Enterprise Manager installation in the past, and if you are now trying to reuse the same database for a new installation.

To manually verify if the schemas are present and to drop them, run the following query:

SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

If the minimum space is less than 200 MB, then set it to 200 MB by running the following command:

alter database datafile <location datafile> resize 200M;

UNDO Tablespace and Temporary Tablespace Settings Requirements

Install and Upgrade

No

Ensures that the UNDO tablespace and the TEMP tablespace are autoextensible in the existing, certified Oracle Database.

To manually verify this, run the following command:

select count(*) from dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE <> 'YES';
select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE <> 'YES';

If the result of the query is 0, then the tablespace is autoextensible. If the result it not 0, then refer to Oracle Database Administrator's Guide available at the following location to make the tablespace autoextensible.

(Recommended) Ensures that you turn on archive logging in the existing, certified Oracle Database for any environment where continuity of data is important.

To manually verify this, run the following command in the SYS role:

select log_mode from v$database;

The result returned must be ARCHIVELOG.

Tablespace-Related Hard Disk Space Requirements

Install

No

Ensures that you allocate a minimum of 200 MB hard disk space for the following tablespaces:

- Management Tablespace (mgmt.dbf)

- Configuration Data Tablespace (mgmt_ecm_depot1.dbf)

- JVM Diagnostics Data Tablespace (mgmt_deepdive.dbf)

Oracle also recommends that you keep the auto-extend feature enabled for the tablespace data files.

Note that the space requirement increases as the number of monitored targets increase, along with the input/output performance demands on the storage devices.

Existing Management Repository

Upgrade

No

Ensures that the existing, certified Oracle Database, which houses the Management Repository, already has a Management Repository configured, and that the Management Repository is compatible with Oracle Management Service 11g Release 1 (11.1).

Database Partitioning Requirements

Install and Upgrade

No

Ensures that the existing, certified Oracle Database has the Partitioning Option enabled (therefore, ensure that you install it into Oracle Database Enterprise Edition.) Installing and using the partitioning option in the Enterprise Manager repository does not add costs to customers when used solely by Enterprise Manager.

To manually verify this, connect to the database as SYSDBA and run the following query:

select value from v$option where parameter = 'Partitioning';

The result of this query should be VALUE=TRUE. No additional partitioning license is required for the database that houses the Management Repository.

Database Partition Maintenance Requirements

Upgrade

No

Checks if the partitions have been created in the database.

If the Enterprise Manager system that you are about to upgrade was shut down for a long period of time, then you will not have partitions created in the existing, certified Oracle Database, which houses the Management Repository, to load new data. Therefore, under such circumstances, to manually create the partitions, follow these steps:

Log in to the database as SYSMAN and run the following command:

execute emd_maintenance.analyze_emd_schema('SYSMAN');
commit;

Restart the OMS from its Oracle home:

$<ORACLE_HOME>/bin/emctl start oms

Database and Listener Status Requirements

Install

No

Ensures that the existing, certified Oracle Database and its listener are running.

Valid Objects Requirements

Install, Upgrade, and Post requisite

No

Ensures that you do have only valid SYSMAN and SYS objects in the existing, certified Oracle Database.

To manually verify whether there are only valid SYSMAN objects, log in to the database as SYS and run the following command:

Ensures that SYSMAN and DBSNMP users have EXECUTE privileges to access the DBMS_RANDOM package in the existing, certified Oracle Database.

To manually verify whether the users have EXECUTE privileges, run the following query. When you run this query for the SYSMAN user, the <user_account_name> must be SYSMAN, and when you run it for the DBSNMP user, the <user_account_name> must be DBSNMP.

If these users do not have EXECUTE privileges, then grant them the privileges by running the following command. When you run this command for granting the privileges for the SYSMAN user, the <user_account_name> must be SYSMAN, and when you run it for the DBSNMP user, the <user_account_name> must be DBSNMP.

SQL> GRANT EXECUTE ON DBMS_RANDOM TO <user_account_name>;

Environment Variable Setting Requirements

Install

No

Ensures that the environment variable ORACLE_HOME is set to the Oracle home of the OMS.

For example, in Cshell, set it in the following way:

setenv ORACLE_HOME /home/OraHomes/oms10g

For example, in bash shell, set it in the following way:

export ORACLE_HOME= /home/OraHomes/oms10g

SUDO Configuration Requirements

Install

No

Ensures that you configure SUDO in your environment. If you are unable to do so or if you have already upgraded any of the core components (OMS or Management Agent) without configuring SUDO, then follow the workaround described in My Oracle Support note 789363.1.

User-Defined Metric Script Definition Requirement

Upgrade

No

If you have any user-defined metric scripts in the Oracle home of a Management Agent that you are upgrading, then checks if you have manually copied all those scripts to another directory outside any Oracle home, and then updated the user-defined metric definitions to reflect the new script location.

This is because, after the Management Agent is upgraded, the user-defined metric scripts are not automatically copied to the new Oracle home.

TEMP Tablespace Group requirement

Upgrade/Install

No

Ensures that there is no tablespace group name called TEMP already existing. If it does, then ensure that you rename it to a different name before installing or upgrade Enterprise Manager. You can always revert to the original name after you finish installing or upgrading.

To manually verify this, log in to the database as SYS user, and run the following query:

To manually verify this, log in to the database as SYS user and run the following query:

select account_status from dba_users where username='SYSMAN_OPSS'

SYSMAN_OPSS account status should be unlocked and unexpired

Global Name requirement

Upgrade(2-system upgrade only)

No

Ensures that Global names of old and new database are not same.

To manually verify this, log in to the database as SYS user and run the following query:

select count(1) from global_name where global_name=(select property_value from SYSMAN.pre_upgc_master_info where upper(property_name)=upper('oldReposGlobalName') and rownum=1) and exists (select 1 from ${EM_REPOS_USER}.pre_upgc_master_info where upper(property_name)=upper('upgrade_type') and upper(property_value) =upper('TWO_SYSTEM')) and exists (select 1 from SYSMAN.pre_upgc_master_info where upper(property_name)=upper('oldReposGlobalNames') and rownum=1 and upper(property_value)='TRUE')

The result of the above query should be 0, if not then change global-names in old repository to a temporary name as this repository/Enterprise Manager would cease to exist after upgrade; or change GLOBAL_NAME of new repository.

Database Edition Requirements

Install

No

Ensures that you are using Oracle Enterprise Database edition to install Enterprise Manager.

To manually verify this, log in to the database as SYS user and run the following query:

select count(1) from PRODUCT_COMPONENT_VERSION where PRODUCT like '%Oracle Database%' and instr(PRODUCT,'Enterprise Edition')>0

The result of the above query should not be 0.

Existing database not to have previous Enterprise Manager's details in schema_version_registry table

Install

No

Ensures that existing database does not have previous Enterprise Manager's details in schema_version_registry table.

To manually verify this, log in to the database as SYS user and run the following query:

Existing database Not to have tablespaces of previous Enterprise Manager

Install

No

Ensures that your existing, certified Oracle Database does not have tablespaces of previous Enterprise Manager.

To manually verify if the database contains such table spaces, run the following query:

select count(1) from dba_tablespaces where TABLESPACE_NAME in ('MGMT_ECM_DEPOT_TS','MGMT_TABLESPACE','MGMT_AD4J_TS')

If the result of the above query is not 0, then you can drop these table spaces otherwise new Enterprise Manager will reuse it.

Existing database not to have public synonym on the tables owned by any of the following Enterprise Manager Repository schemas: SYSMAN', SYSMAN_MDS,MGMT_VIEW,'SYSMAN_BIP,'SYSMAN_APM,BIP,SYSMAN_OPSS and SYSMAN_RO

Install

No

Ensures that your existing, certified Oracle Database does NOT have any public synonyms on the tables owned by any of the following schemas: