Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1)
Part No. B12012-03
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

B Management Repository Database Settings

The following topics are covered in this appendix:

Initialization Parameters

The required initialization parameters must be set correctly for your qualified existing Enterprise Edition database to be able to run a Management Repository. You should also set all recommended parameters for your Management Repository database.


See Also:

For more information about managing initialization parameters, refer to the "Managing Initialization Parameters Using the Server Parameters File" chapter of the Oracle Database Administrator's Guide.

After making the changes, you must shut down and restart the database.


See Also:

For instructions on shutting down the database, refer to the "Starting Up and Shutting Down" chapter in the Oracle Database Administrator's Guide.

Required Parameters

The following table lists the minimum or absolute values for required initialization parameters for the existing Enterprise Edition database you have selected for the Management Repository. These required parameters are verified by Oracle Universal Installer pre-requisite checks during installation. Management Repository creation will fail if these required settings are not met.


Note:

Make sure that the Enterprise Edition database you select for your Management Repository has the fine-grained access control option set to true. This is required for successful Management Repository creation. Check v$options for this setting.

Table B-1 Minimum Required Oracle Database Parameter Values

Parameter Value
job_queue_processes 10
db_block_size 8192
remote_login_passwordfile EXCLUSIVE
timed_statistics TRUE
open_cursors 300
session_cached_cursors 200
shared_pool_size 67108864 (for 9.2.0.4 databases)Foot 
dispatchersFoot  NULL
aq_tm_processesFoot  1
compatible 9.0.1.3 or greater

Footnote For 10g databases, this is checked by querying the dynamic SGA components rather than checking initialization parameters.
Footnote This parameter must either be NULL or not present in the init.ora file. No other value should be used.
Footnote If this parameter is not set, or is set to zero, dequeued messages will not be purged. Set to 1 or greater.

Note:

For Grid Control, the resource_manager_plan parameter in the init.ora file for the existing database should not be set.

Recommended Parameters

The following table lists the minimum values for recommended initialization parameters for the existing Enterprise Edition database you have selected for the Management Repository. These parameters should be set in addition to all required parameters.

Table B-2 Minimum Recommended Oracle Database Parameter Values

Parameter Value
db_cache_size 134217728
large_pool_size 0
processes 150
fast_start_mttr_target 300
hash_area_size 1048576
sort_area_size 1048576
pga_aggregate_target 33554432
undo_management AUTO
undo_retention 10800
undo_tablespace UNDOTBS

Other Database Settings

You may want to check the following settings for your Management Repository database to make sure they are set correctly.

UNDO Tablespace and Temporary Tablespace

Oracle recommends that the Management Repository database have the UNDO Tablespace and the Temporary Tablespace set to AUTOEXTEND ON.


See Also:

For more information, refer to the "Managing the UNDO Tablespace" chapter of the Oracle Database Administrator's Guide.

Archive Logging

Oracle recommends that the Management Repository database have archive logging turned on for any environment where continuity of data is important. Regular backups are also recommended.

Ensure the Database is Not in QUIESCE Mode

Oracle recommends that you do not put the Management Repository database in QUIESCE mode. Check your Resource Plan for INTERNAL_QUIESCE.

  1. Navigate to the Database Home page of your Management Repository.

  2. On the Administration property page, under Resource Manager, click Resource Plans.

  3. Make sure INTERNAL_QUIESCE has not been selected.

In QUIESCE mode, only DBA transactions are processed; all other transactions are suspended. Putting the Management Repository database in the QUIESCE mode suspends Enterprise Manager transactions.