| Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 2 (12.1.0.2) Part Number E22624-13 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 2 (12.1.0.2) Part Number E22624-13 |
|
|
PDF · Mobi · ePub |
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:
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 action automatically, to the extent possible, when a prerequisite check fails. The kit also takes postrequisite steps 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.
Note:
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.
The EM Prerequisite Kit is run internally by the Enterprise Manager Installation Wizard while installing or upgrading an Enterprise Manager system. However, if any of the repository prerequisite checks fail for some reason, you can manually run them by invoking this kit.
The EM Prerequisite Kit is available in the following location of the software kit (DVD, downloaded software):
install/requisites/bin/emprereqkit
Note:
Ensure that the user running the EM Prerequisite Kit has write permission to the central inventory.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:
install/requisites/bin/emprereqkit -executionType install -prerequisiteXMLLoc <prereq_xml_location> -connectString <connect_string> -dbUser SYS -dbPassword <db_password> -dbRole sysdba -showPrereqs
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:
install/requisites/bin/emprereqkit -executionType install -prerequisiteXMLLoc <prereq_xml_location> -connectString <connect_string> -dbUser SYS -dbPassword <db_password> -dbRole sysdba -runPrerequisites -runCorrectiveActions
Note:
To learn about the other arguments that can be passed with the kit, see Running the EM Prerequisite Kit with Additional Arguments.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. So, in future, if you decide to install any plug-ins, then before installing them, ensure that you invoke the EM Prerequisite Kit from this location.
$<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:
Enable the Self Update functionality within Enterprise Manager Cloud Control so that the new or updated prerequisite XML files are automatically downloaded to the $<OMS_HOME>/install/requisites/list directory.
Manually download the new or updated prerequisite XML files from Oracle store to the $<OMS_HOME>/install/requisites/list directory.
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? | Example | Description |
|---|---|---|---|---|
|
- |
Mandatory |
Yes |
|
Enables performing prerequisite checks for different repository configurations. |
|
Mandatory |
Ye |
|
Specify the type of execution, which can be one of the following:
|
|
|
Mandatory |
Yes |
|
Specify the absolute path to the location where the XML files related to the prerequisites are present. If you do not specify a location, the default location is |
|
|
One of these options is mandatory |
Yes |
For example (connect string):
For example (database details):
|
Specify the database details. |
|
Mandatory Even if you do not pass this option, you will be prompted to provide a value |
Yes |
|
Specify |
|
|
Mandatory Even if you do not pass this option, you will be prompted to provide a value |
Yes |
|
Specify the database password. |
|
|
Mandatory Even if you do not pass this option, you will be prompted to provide a value |
Yes |
|
Specify |
|
|
Optional |
Yes |
|
Specify the absolute path to a directory where the results (in the form of XML files) of the prerequisite checks can be stored. If you do not pass this option, the results are stored in a default location which is the current directory. Note: If you specify details for a different database before completing all the actions, you will need to specify a different -prereqResultLoc. |
|
|
Optional |
No |
Example using $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc $ORACLE_HOME/install/requisites/list -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -showPrereqs Example using $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc $ORACLE_HOME/install/requisites/list -connectString "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=example.com)(PORT=15044)))(CONNECT_DATA=(SID=sv902)))" -dbUser SYS -dbPassword example_passwd -dbRole sysdba -showPrereqs |
Lists the prerequisite checks to be run. |
|
|
One of these options is mandatory. |
No |
An example for -runPrerequisites: $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -prerequisiteXMLLoc $ORACLE_HOME/install/requisites/list -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -runPrerequisites An example for -showCorrectiveActions: $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -showCorrectiveActions Example for $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -runCorrectiveActions
$ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -showPostCorrectiveActions Example for $ORACLE_HOME/install/requisites/bin/emprereqkit -executionType upgrade -dbHost example.com -dbPort 15044 -dbSid sv902 -dbUser SYS -dbPassword example_passwd -dbRole sysdba -runPostCorrectiveActions |
Important: If you passed
Note: Show actions must be independent, that is, they should not be combined with any other action. |
|
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 |
|
|
Optional |
Yes |
|
Specify the components that must be selected instead of the XML files for checking the prerequisites.
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. |
|
|
Optional |
Yes |
|
Specify the absolute path to a location where the response file is available. |
|
|
Optional |
Yes |
|
Specify a unique name for this run. If you do not specify this, a default name with the format |
|
|
Optional |
Yes |
|
Specify the name and value of the component variable in the following format:
For example:
You can pass as many component variables as you want, but ensure that you separate them by a comma. For example:
|
|
|
Optional |
Yes |
|
Defaults to |
|
|
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 |
|
|
Optional Must be passed independently while invoking the utility |
No |
|
Organizes and lists the prerequisite check results (stored in the database) based on when it was run and the context. |
|
|
|
Optional Must be passed independently while invoking the utility |
No |
|
Copies the prerequisite check results (XML files) from the database to an external file system. |
|
Optional Must be passed independently while invoking the utility |
No |
|
Defaults to |
|
|
Optional |
No |
|
This option gives details of various parameters which can be passed to 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.
Table A-2 EM Prerequisite Kit Result File Location (Instance XML File)
| invocation Type | Instance File LocationFoot 1 | Latest Instance File LocationFoot 2 |
|---|---|---|
|
Note: When you provide |
Note: When you provide |
|
|
Automatically Invoked by the Enterprise Manager Cloud Control Installation Wizard |
Note: When you proceed through the installation wizard pages, EM Prerequisite Kit result XMLs are created in When install begins, the |
Note: When you proceed through the installation wizard pages, EM Prerequisite Kit result xmls are created in When install begins, the |
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.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 |
|---|---|
|
Contains information about every step taken or action performed by the kit |
|
|
Contains only the error and stacktrace of the exceptions occurred |
|
|
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.s |
|
|
Contains information about the function area-specific prerequisite checks that are run. For example, |
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.output file. For emprereqkit.output file, see the note after the table.
Table A-4 EM Prerequisite Kit Log File Locations
| invocation Type | Latest Log File LocationFoot 1 | Log File LocationFoot 2 |
|---|---|---|
|
Note: When you provide |
Note: When you provide |
|
|
Automatically Invoked by the Enterprise Manager Cloud Control Installation Wizard |
Note: When you proceed through the installation wizard pages, EM Prerequisite Kit logs are created in either When install begins, the / |
Note: When you proceed through the installation wizard pages, EM Prerequisite Kit logs are created in either When install begins, the |
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 fileemprereqkit.output 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.output is stored in <MW_HOME>/.gcinstall_temp/log/<time-stamp>. And the latest log file is stored in <MW_HOME>/.gcinstall_temp/log/<LATEST>.
This section describes all the repository prerequisites that the EM Prerequisites Kit checks. This section also describes how to manually check these prerequisites.
Following are the repository prerequisites for upgrading Enterprise Manager.
Table A-5 Repository Prerequisites for Upgrading Enterprise Manager System
| Prerequisite | Applies to Install/Upgrade | Automatic | Description |
|---|---|---|---|
|
Basic Policy Requirements |
Upgrade |
No |
Ensure that valid policy exists for MGMT_TARGETS. To verify, run the following query:
The query must not return any rows. |
|
Active Jobs Requirements |
Upgrade |
No |
Ensure that there are no background DBMS jobs currently running in the Repository Database. To verify, 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 |
Ensure that the GVM Performance Metric Collection job is stopped and deleted. To verify if a job named
If it exists, then stop and delete. |
|
Valid Reference Requirements |
Upgrade |
No |
Ensure that all entries for To verify, run the following query. The query must not return any rows.
|
|
Job Type Uniqueness Requirements |
Upgrade |
No |
Ensure that there are no duplicate entries in To verify, run the following query. The query must not return any rows.
|
|
SQL Plan Baseline Capture Parameter Requirements |
Install, Upgrade |
No |
Ensure that the parameter 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 |
Ensure that the current availability index is renamed to the following:
|
|
My Oracle Support User Name Size Requirements |
Upgrade |
No |
Ensure 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 |
Ensure that the ARU user name is not longer than 239 characters. If it is, you cannot upgrade. |
|
DBMS Package Requirements |
Install, Upgrade |
No |
Ensure that you compile the required DBMS 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:
If the package is invalid, run the following query:
If the packages do not compile successfully, contact Oracle Support. |
|
Snapshot Log Requirements |
Upgrade |
No |
Ensure that the snapshot logs are deleted from the tables. |
|
Connector Configuration Table Requirements |
Upgrade |
No |
Ensure 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 |
Ensure 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. |
|
Primary Key and Foreign Key Requirements |
Upgrade |
No |
Ensure that Primary Key and Foreign keys are not disabled. To verify, run the following query: select count(*) from (select constraint_name, table_name from DBA_CONSTRAINTS where owner = 'SYSMAN' and (constraint_type = 'P' or constraint_type = 'R') and status = 'DISABLED') If the result is not 0, then use the following query to enable the constraint: alter table SYSMAN.<TABLE_NAME> modify constraint <CONSTRAINT_NAME> enable If the constraints cannot be enabled for any reason, contact Oracle Support. |
|
Enable Queue Requirements |
Upgrade |
No |
Ensure that queues are enabled in the Repository Database. To verify, 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 |
Ensure that all the triggers in the Repository Database are not disabled. To verify, run the following query: select count(*) from (select trigger_name, trigger_type, table_name from DBA_TRIGGERS where table_owner = 'SYSMAN' and status = 'DISABLED') If result is not 0, then enable the trigger. |
|
SYSTEM tablespace requirement |
Install and Upgrade |
No |
Ensure that the SYSTEM tablespace has at least one datafile set to autoextensible. To verify, run the following query:
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 |
Ensure that the emkey is copied to the repository. To verify, run the following query:
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. Configure the emkey.ora file by running |
|
EM_USER_CONTEXT requirements |
Upgrade |
No |
Ensure that EM_USER_CONTEXT is present in the repository. To verify, run the following query:
If the query result is 0, check that the procedure SETEMUSERCONTEXT is valid by executing the following query:
where object_name='SETEMUSERCONTEXT' and owner='SYSMAN' The above query must return 'VALID'. Then run:
Create or replace context EM_USER_CONTEXT using SETEMUSERCONTEXT; If the context cannot be created for any reason, contact Oracle Support. |
|
Audit Master table requirement |
Upgrade |
No |
Ensure that there are no abnormal conditions stored in the Audit Master Table. To verify, run the following query:
If the query result is not 1 then, contact Oracle Support to analyze the Enterprise Manager repository before attempting to perform the patch/upgrade. |
|
Exempt Access Policy requirement |
Upgrade |
No |
Ensure that EXEMPT ACCESS POLICY is not granted directly to SYSMAN or indirectly grants to a role that is granted to SYSMAN. To verify, run the following query:
If the result of the query is not 0, then revoke EXEMPT ACCESS POLICY from SYSMAN and the roles. For example:
|
|
max_enabled_roles init parameter requirement |
Install and Upgrade |
No |
Ensure 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 verify, run the following query:
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:
|
|
PAF execution requirements |
Upgrade |
No |
Ensure that no PAF executions are scheduled or running. To verify, run the following query:
If the query result is not 0, then abort or wait for PAF executions to complete. |
|
Secured Agent requirements |
Upgrade |
No |
Ensure that all the agents are secured with latest CA. To know the list of agents to be secured, run the following command:
|
|
Pre-upgrade console patch requirements |
Upgrade |
No |
Ensure that pre-upgrade patch is applied. To verify, run the following query:
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 |
Ensure that global stale percentage is in between 5 and 25. To verify, run the following query:
The query result must be 1. |
|
Account status requirements |
Upgrade |
No |
Ensure that SYSMAN, MGMT_VIEW and ORACLE_OCM accounts are not locked or expired. To verify, 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 |
Ensure that SYSMAN schema is present for upgrade. To verify, 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 |
Ensure that size of the log file is 300 megabytes or greater. To verify, run the following query: select min(bytes) from v$log The query result must be greater or equal to 300000000 (bytes). |
|
Existing Database Not to Be in QUIESCE Mode |
Install and Upgrade |
No |
Ensure that existing, certified Oracle Database is not in QUIESCE mode. To verify this, run the following SQL in the database in the SYS role: select active_state from v$instance; The result returned must be |
|
Existing Database Not to Have Database Control (only for fresh install) |
Fresh Install |
No |
(If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 12c Cloud Control using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.) Ensure 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.
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 |
(If you are upgrading from Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 12c Cloud Control using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.) Ensure that your existing, certified Oracle Database does NOT have Enterprise Manager Grid Control SYSMAN schema and Metadata (MDS) schema.
|
|
Database Initialization Parameters Requirements |
Install and Upgrade except db_block_size which applies only to install. |
No |
Ensure that you have correctly set the database initialization parameters. For information about the database initialization parameters to be set, refer to Setting Database Initialization Parameters. |
|
Fine-Grained Access Control Requirements |
Upgrade |
No |
Ensure that the fine-grained access control option is set to TRUE in the existing, certified Oracle Database so that the Management Repository can be created. To verify this, run the following command: select value from v$option where parameter = 'Fine-grained access control'; |
|
UNDO Tablespace Size Requirements |
Install and Upgrade |
No |
Ensure that the UNDO tablespace has a minimum space of 200 MB. To verify this, run the following query: SELECT SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total FROM dba_data_files f, dba_tablespaces s WHERE s.contents = 'UNDO' AND s.tablespace_name = f.tablespace_name; Note: The result of this query is in bytes. 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 |
Ensure that the UNDO tablespace and the TEMP tablespace are autoextensible in the existing, certified Oracle Database. To 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. http://www.oracle.com/technology/documentation/database.html |
|
Archive Logging Settings Requirements |
Install and Upgrade |
No |
(Recommended) Ensure that you turn on archive logging in the existing, certified Oracle Database for any environment where continuity of data is important. To verify this, run the following command in the SYS role: select log_mode from v$database; The result returned must be |
|
Tablespace-Related Hard Disk Space Requirements |
Install |
No |
Ensure 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_ad4j.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 |
Ensure 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 |
Ensure 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 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 |
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, do the following:
|
|
Database and Listener Status Requirements |
Install |
No |
Ensure that the existing, certified Oracle Database and its listener are running. |
|
Valid Objects Requirements |
Install, Upgrade, and Post requisite |
No |
Ensure that you do have only valid SYSMAN and SYS objects in the existing, certified Oracle Database.
|
|
DBMS Jobs and DBMS Scheduler Status Requirements |
Install and Upgrade |
Yes |
Ensure that you stop the DBMS Jobs and the DBMS Scheduler in the existing, certified Oracle Database. To do so, log in to the database as SYS:
|
|
Gather Statistics Job Status Requirements |
Install and Upgrade |
Yes |
Ensure that you stop the Gather Statistics job that is running in the existing, certified Oracle Database. To do so, log in to the database as SYS and run the following commands: For Oracle Database 10g (10.2.0.4) or higher: execute dbms_scheduler.disable('GATHER_STATS_JOB',TRUE); execute dbms_scheduler.stop_job('GATHER_STATS_JOB',TRUE); For Oracle Database 11g (11.1.0.7) or higher: execute dbms_auto_task_admin.disable('auto optimizer stats collection',null,null); |
|
User Privilege Requirements |
Upgrade |
No |
Ensure that SYSMAN and DBSNMP users have EXECUTE privileges to access the DBMS_RANDOM package in the existing, certified Oracle Database. To 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. SQL> CONNECT AS SYS; SQL> SELECT grantee, grantor, owner, table_name FROM DBA_TAB_PRIVS WHERE table_name = 'DBMS_RANDOM' AND privilege = 'EXECUTE' AND grantee IN ( SELECT DISTINCT granted_role FROM DBA_ROLE_PRIVS START WITH grantee = '<user_account_name>' CONNECT BY PRIOR granted_role=grantee UNION ALL SELECT '<user_account_name>' FROM dual WHERE ROWNUM = 1 UNION ALL SELECT 'PUBLIC' FROM dual WHERE ROWNUM = 1 ) 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 |
Ensure 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 |
Ensure 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 ensure that you manually copy all those scripts to another directory outside any Oracle home, and then update 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 |
Ensure 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 verify this, log in to the database as SYS user, and run the following query: select count(*) group_name from DBA_TABLESPACE_GROUPS where UPPER(group_name)='TEMP' The result of the above query should not be 0. |
|
SYSMAN_OPSS account status requirement |
Upgrade |
No |
Ensure that SYSMAN_OPSS account is not locked. To 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 |
Ensure that Global names of old and new database are not same. To 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 |
Ensure that you are using Oracle Enterprise Database edition to install Enterprise Manager. To 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 |
Ensure that existing database does not have previous Enterprise Manager's details in schema_version_registry table. To verify this, log in to the database as SYS user and run the following query: select count(1) from SCHEMA_VERSION_REGISTRY where comp_name in ('Authorization Policy Manager','Metadata Services','Oracle Platform Security Services')
If the result of the above query is not 0 then delete the entries from SCHEMA_VERSION_REGISTRY using the following query: Delete from SCHEMA_VERSION_REGISTRY where comp_name in ('Authorization Policy Manager','Metadata Services','Oracle Platform Security Services');
commit;
|
|
Existing Database Not to Have any Enterprise Manager Repository schemas |
Install |
No |
Ensure that your existing, certified Oracle Database does not have Enterprise Manager Repository schemas:
|
|
Existing database Not to have tablespaces of previous Enterprise Manager |
Install |
No |
Ensure that your existing, certified Oracle Database does not have tablespaces of previous Enterprise Manager. Following query can be used to verify if the database contains such table spaces: 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 re-use 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 |
Ensure that your existing, certified Oracle Database does NOT have any public synonyms on the tables owned by any of the following schemas: SYSMAN', SYSMAN_MDS,MGMT_VIEW,'SYSMAN_BIP,'SYSMAN_APM,BIP,SYSMAN_OPSS and SYSMAN_RO
|
This section describes the following:
Setting Database Initialization Parameters for Advanced Installation
Setting Database Initialization Parameters for Simple Installation
For an advanced installation, the database initialization parameters to be set for different deployment sizes (small, medium, large) are described in Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
For a simple installation, the following are the database initialization parameters to be set:
Table A-6 Database Initialization Parameters Set for Simple Installation
| Parameter | Value |
|---|---|
|
DB_BLOCK_SIZE_VALUE |
8192 |
|
PROCESSES_PARAMETER_VALUE |
300 |
|
PGA_AGGREGATE_TARGET_PARAMETER_VALUE |
200000000 |
|
SESSION_CACHED_CURSORS_PARAM_MIN_VALUE |
200 |
|
SESSION_CACHED_CURSORS_PARAM_MAX_VALUE |
500 |
|
JOB_QUEUE_PROCESSES_PARAM_INS_VALUE |
20 |
|
JOB_QUEUE_PROCESSES_PARAM_UPG_VALUE |
0 |
|
OPEN_CURSORS_PARAM_MIN_VALUE |
300 |
|
OPEN_CURSORS_PARAM_MAX_VALUE |
400 |
|
SGA_TARGET_PARAM_VALUE |
800000000 |
|
LOG_BUFFER_PARAM_VALUE |
1000000 |
|
SHARED_POOL_SIZE_PARAM_VALUE |
300000000 |
|
DB_CACHE_SIZE_PARAM_DEFAULT_VALUE |
TRUE |
|
LARGE_POOL_SIZE_PARAM_DEFAULT_VALUE |
TRUE |
|
JAVA_POOL_SIZE_PARAM_DEFAULT_VALUE |
TRUE |
|
STREAMS_POOL_SIZE_PARAM_DEFAULT_VALUE |
TRUE |
|
TIMED_STATISTICS_PARAM_DEFAULT_VALUE |
TRUE |
|
TIMED_STATISTICS_PARAM_VALUE |
TRUE |
|
STATISTICS_LEVEL_PARAM_DEFAULT_VALUE |
TRUE |
|
 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|