#Incontrol ha install#

See 'Best Practices for Configuring the Cloud Control OMS to be Compatible with Disaster Recovery using Alias Host Names and Storage Replication' for details on these steps. Regardless of the manner selected to provide high availability, and the level of availability selected for initial installation, there are a number of steps that can be taken to best prepare the environment for a future move to higher levels of availability including disaster recovery. See Chapter 18, 'High Availability Solutions' for more details on architectural options for achieving high availability. Depending upon your Recovery Time Objective (RTO), this can be accomplished without downtime from loss of a node in an active/active configuration by adding at least one additional OMS, or with limited downtime from loss of a node in an active/passive configuration by ensuring that the OMS can be run with the same address on a different server if the primary server fails.

OMS high availability begins with ensuring there is at least one OMS available at any given time. The following sections document configuring the OMS for high availability.

If you have multiple Management Services configured, this command must be run on each Management Service.Įmctl config oms -store_repos_details -repos_conndesc '(DESCRIPTION= (ADDRESS_LIST=(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=EMREP)))' -repos_user sysmanĪfter updating the Repository connect descriptor, run the following command from any one OMS to make the same change to the monitoring configuration used for the Management Services and Repository target:ġ9.3 Oracle Management Service High Availability The Repository connect descriptor is configured by running the emctl command from Management Service. NECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=))) The following example shows a connect string for Repository where database version is 11g Release 2 or higher (DESCRIPTION= (ADDRESS_LIST=(FAILOVER=ON) (ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521)) (ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=EMREP))) The following example shows a connect string for Repository where database version is lower than 11g Release 2. Refer to the Oracle Database Net Services Administrator's Guide for details. SERVICE_NAME should always be used in connect strings instead of SID_NAME SCAN connect strings are recommended to avoid reconfiguration of the Repository connect descriptor following addition or removal of nodes in the Repository tier. If the Management Repository is a Real Application Cluster (RAC) database, the Management Services should be configured with the appropriate connect strings. See Oracle Database High Availability Best Practices for more information on these and other best practices to ensure the database that hosts the Management Repository is configured to provide required availability.ġ9.2.2 Configuring RAC for the Management Repository MAA Advisor can be accessed by selecting Availability > MAA Advisor from the Homepage of the Repository Database. Use the MAA Advisor for additional high availability recommendations that should be applied to the Management Repository. Use Fast-Start Fault Recovery to Control Instance Recovery Time

#Incontrol ha install#

Install the database using Database Configuration Assistant (DBCA) to make sure that you inherit all Oracle install best practices.Ĭhoose Automatic Storage Management (ASM) as the underlying storage technology.Ĭonfigure the Size of Redo Log Files and Groups Appropriately The watchdog will not restart the Management Agent if the watchdog detects that the Management Agent has required restart more than EM_MAX_RETRIES within the EM_RETRY_WINDOW time period.ġ9.2.1 General Best Practice for Repository High Availabilityīefore installing Enterprise Manager, you should prepare the database, which will be used for setting up Management Repository. The default is to attempt restart of the Management Agent three times.ĮM_RETRY_WINDOW - This is the time interval in seconds that is used together with the EM_MAX_RETRIES environmental variable to determine whether the Management Agent is to be restarted. All testing discussed here was done with the default settings.ĮM_MAX_RETRIES – This is the maximum number of times the watchdog will attempt to restart the Management Agent within the EM_RETRY_WINDOW. The environment variables that control this behavior follow. The behavior of the watchdog is controlled by environment variables set before the Management Agent process starts. Once the Management Agent is started, the watchdog process monitors the Management Agent and attempts to restart it in the event of a failure. 19.1.2 Configuring Restart for the Management Agent