Managing OEM Database Control with emca for RAC 11gR2
Managing OEM Database Control with emca for RAC 11gR2
In the article you will have a look at using emca with Oracle RAC for managing OEM DC. OEM Database control can be configured either with dbca or with emca.
Starting with Oracle 10gR1 RAC upon configuring OEM DC one DC console and agent was running on each node of the cluster. After Oracle 10gR2 the behavior changed so that by default a console is started only on the node where dbca or emca was started to configure OEM DC. However, OEM DC is configured to run on each of the cluster nodes where RAC database has configured instances ( 11gR2 administrator-managed). Starting OEM DC starts OEM DC console and the agent on the default node, whereas on the all other nodes only OEM agent is started. Oracle RAC also supports running OEM DC consoles on more than one node, though it makes sense on multi-nodes clusters.
- Recreate OEM DC configuration after change (IP) or in general if nothing else works.emca -deconfig dbcontrol db -repos drop -clusteremca -config dbcontrol db -repos create -clusteroremca -deconfig dbcontrol db -clusteremca -config dbcontrol db -repos recreate -cluster
- Change portemca -reconfig ports -DBCONTROL_HTTP_PORT port# port_number -clusteremca -reconfig ports -JMS_PORT port# -clusteremca -reconfig ports -RMI_PORT port# -clusteremca -reconfig ports -AGENT_PORT port_number –cluster
- Enabling OEM DC on two nodes.An additional console will be created and started on the second node. The initial configuration is follows.-bash-3.00$ emca -displayConfig dbcontrol -clusterSTARTED EMCA at Jul 6, 2011 12:16:31 AMEM Configuration Assistant, Version 11.2.0.0.2 ProductionCopyright (c) 2003, 2005, Oracle. All rights reserved.Enter the following information:Database unique name: RACDBService name: RACDBDo you wish to continue? [yes(Y)/no(N)]: yJul 6, 2011 12:16:48 AM oracle.sysman.emcp.EMConfig performINFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/RACDB/e mca_2011_07_06_00_16_29.log.Jul 6, 2011 12:16:58 AM oracle.sysman.emcp.EMDBPostConfig showClusterDBCAgentMes sageINFO:**************** Current Configuration ****************INSTANCE NODE DBCONTROL_UPLOAD_HOST———- ———- ———————RACDB sol1 sol1RACDB sol2 sol1Agents on each node are uploading to sol1 host.On each node of the cluster (sol1,sol2) status is as follows:sol2-bash-3.00$ emctl status dbconsoleOracle Enterprise Manager 11g Database Control Release 11.2.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.EM Daemon is running.——————————————————————Logs are generated in directory /u01/app/oracle/product/11.2.0.2/db_1/sol2_RACDB/sysman/log-bash-3.00$sol1-bash-3.00$ emctl status dbconsoleOracle Enterprise Manager 11g Database Control Release 11.2.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.Oracle Enterprise Manager 11g is running.——————————————————————Logs are generated in directory /u01/app/oracle/product/11.2.0.2/db_1/sol1_RACDB/sysman/log-bash-3.00$It might be useful for multi node clusters to have more than one console on different nodes. Having more than one console allows to split the upload from the cluster agents into the available OEM DC consoles. Each console will r be used for uploads from a portion of cluster nodes. Each cluster node agent can upload to only one console. Node sol2 will be used to start a second OEM DC console and for upload a portion ( sol2 in case of two node cluster if multi-node cluster nodes can be split equally) . EM_NODE is the node for the additional console. EM_NODE_LIST is a list of the agent nodes that will upload to EM_NODE console. An agent can upload to only one console and local agents upload to the console of the same node if exists.-bash-3.00$ emca -reconfig dbcontrol -cluster -EM_NODE sol2 -EM_NODE_LIST sol2STARTED EMCA at Jul 6, 2011 2:07:29 AMEM Configuration Assistant, Version 11.2.0.0.2 ProductionCopyright (c) 2003, 2005, Oracle. All rights reserved.Enter the following information:Database unique name: RACDBService name: RACDBDo you wish to continue? [yes(Y)/no(N)]: yJul 6, 2011 2:08:02 AM oracle.sysman.emcp.EMConfig performINFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/RACDB/emca_2011_07_06_02_06_38.log.Jul 6, 2011 2:10:01 AM oracle.sysman.emcp.util.DBControlUtil stopOMSINFO: Stopping Database Control (this may take a while) …Jul 6, 2011 2:10:25 AM oracle.sysman.emcp.EMAgentConfig performDbcReconfigurationINFO: Propagating /u01/app/oracle/product/11.2.0.2/db_1/sol2_RACDB/sysman/config/emd.properties to remote nodes …Jul 6, 2011 2:10:26 AM oracle.sysman.emcp.util.DBControlUtil startOMSINFO: Starting Database Control (this may take a while) …Jul 6, 2011 2:12:04 AM oracle.sysman.emcp.EMDBPostConfig performDbcReconfigurationINFO: Database Control started successfullyJul 6, 2011 2:12:32 AM oracle.sysman.emcp.EMDBPostConfig showClusterDBCAgentMessageINFO:**************** Current Configuration ****************INSTANCE NODE DBCONTROL_UPLOAD_HOST———- ———- ———————RACDB sol1 sol1RACDB sol2 sol2Enterprise Manager configuration completed successfullyFINISHED EMCA at Jul 6, 2011 2:12:32 AM-bash-3.00$The status changes as follows:Sol2-bash-3.00$ emctl status dbconsoleOracle Enterprise Manager 11g Database Control Release 11.2.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.Oracle Enterprise Manager 11g is running.——————————————————————Logs are generated in directory /u01/app/oracle/product/11.2.0.2/db_1/sol2_RACDB/sysman/log-bash-3.00$sol1-bash-3.00$ emctl status dbconsoleOracle Enterprise Manager 11g Database Control Release 11.2.0.2.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.Oracle Enterprise Manager 11g is running.——————————————————————Logs are generated in directory /u01/app/oracle/product/11.2.0.2/db_1/sol1_RACDB/sysman/log
No comments:
Post a Comment