| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2) for Linux x86 Part Number B16228-02 |
|
|
View PDF |
| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 2 (10.2) for Linux x86 Part Number B16228-02 |
|
|
View PDF |
The following topics are covered in this appendix:
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 a Server Parameter 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. |
The following table lists the parameters and their fixed values that must be met for successful Management Repository database creation. These parameters are verified by Oracle Universal Installer prerequisite checks during installation.
|
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. Checkv$options for this setting. |
Table B-1 Fixed Initialization Parameter Values
| Parameter | Value |
|---|---|
|
job_queue_processes |
10 |
|
db_block_size |
8192 |
|
timed_statistics |
TRUE |
|
open_cursors |
300 |
|
session_cached_cursors |
200 |
|
aq_tm_processes |
1 |
|
compatible |
<currently installed Oracle RDBMS version> (default) |
|
undo_management |
AUTO |
|
undo_retention |
10800 |
|
undo_tablespace |
<any acceptable name> |
|
processes |
150 |
|
log_buffer |
1048576 |
|
statistics_level |
TYPICAL (Note that this value is specific only to 10g Enterprise Manager Repository Database versions and higher.) |
|
TEMP Space |
50 MB (extending to 100MB) |
|
_b_tree_bitmap_plans |
false (hidden parameter) |
The variable parameter setting values are based on the size of the Enterprise Manager environment. For the sake of clarity, we have categorized the environment as Small, Medium, and Large based on the number of targets in the environment, where:
Small = Approximately 100 monitored targets
Medium = Approximately 1000 monitored targets
Large = 10000 or more monitored targets
Table B-2 Variable Initialization parameter Values
| Size | pga_aggregate_target | Redo logsFoot 1 | db_cache_size (for 91 rep. DB) | shared_pool_size (for 91 rep. DB) | sga_target (for 10g rep. DB)Foot 2 |
|---|---|---|---|---|---|
|
Small |
256 MB |
100 MB |
384 MB (or more) |
128 MB |
512 MB (or more) |
|
Medium |
384 MB |
512 MB |
1024 MB (or more) |
384 MB |
1408 MB (or more) |
|
Large |
512 MB |
1024 MB |
2048 MB (or more) |
512 MB |
2560 MB (or more) |
You may want to check the following settings for your Management Repository database to make sure they are set correctly.
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. |
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.
Oracle recommends that you do not put the Management Repository database in QUIESCE mode. Check your Resource Plan for INTERNAL_QUIESCE.
Navigate to the Database Home page of your Management Repository.
On the Administration property page, under Resource Manager, click Resource Plans.
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.
