Introduction This article describes you(few) post tasks to be done if the database is upgraded to any recent version or downgrade to lower version when it is being monitored by the Enterprise Manager 12c. This article written based on the upgrade of database from 11.2.0.3 to 12.1.0.2 and what are the changes to be done from the enterprise manager 12c. Database changes After the upgrade of the database(11.2.0 -> 12.0.1), by default we can see the instance as running because agent can push the database with the active instances, listeners which are running. For example Maindb we have upgraded, after the upgrade we able to monitor the databaes and status of the databaes shows healthy and we can see the active sessions, top sqls and all kind of information like below. Navigation: Target à Databases à “select ORCL” The database is monitoring with the old values i.e. Old Oracle HOME of 11gR2. From the below pictures we can see what the oracle home is configured for the database(11.2.0) infact we are into 12.1.0.2. From the database navigate to the configuration as below. Now we can see the configuration of the target “ORCL” Maindb Database, here the Oracle Home path still shows to the Oracle Home i.e. 11gR2 of path /u01/app/oracle/product/11.2.0/db_1, now we have to change the oracle home to point out to the new Home “/u01/app/oracle/product/12.1.0/db_1” Now we have changed to the new Home which points to 12.1.0.2 After changing , you test the connection by clicking "Test connection" , If the result succeeds then we can confirm that session able to establish. Now we can see the configuration is validated with the correct Oracle Home by clicking the "Next/Submit" button. The overall steps helps to avoid misleading monitoring and to ensure OEM is assuming the database is running on the new Home. Listener As we seen above the database was in healthy status even though target monitored by the Old Oracle home, In case of database Listener the target status shows as DOWN from EM12c. By the belowimage it is clear that status from EM shows as down, we will connect to the listener and update the configuration by changing the oracle home Connect to the actual server ORA-C1 and gather the Oracle home and the network directory. [oracle@ORA-C1 ~]$ ps -ef|grep tns root 21 2 0 2015 ? 00:00:00 [netns] oracle 3920 3902 0 12:06 pts/0 00:00:00 grep tns oracle 29031 1 0 Jan23 ? 03:00:19 /u01/app/oracle/product/ 12.1.0 /db_1//bin/tnslsnr LISTENER -inherit [oracle@ORA-C1 ~]$ ps -ef|grep pmon oracle 3979 3902 0 12:07 pts/0 00:00:00 grep pmon oracle 10024 1 0 Jan23 ? 00:45:48 ora_pmon_DV02 [oracle@ORA-C1 ~]$ pwdx 10024 10024: /u01/app/oracle/product/12.1.0/db_1/dbs [oracle@ORA-C1 ~]$ echo $ORACLE_HOME /u01/app/oracle/product/12.1.0/db_1 [oracle@ORA-C1 ~]$ We will access the monitoring configuration of the Listener by using the below navigation in order to check the configuration of the listener. Here change/alter the locations of listener.ora directory and oracle home as below. Now the status shows as the configuration changes were performed and whenever with the next agent push the actual data will be retrieved. Earlier the status was in down and now the status should show to Up (green) , If still the status shows as down then then try to upload agent manually like below. [oracle@ORA-C1 ~]$ . oraenv ORACLE_SID = [oracle] ? agent12c The /u01/app/oracle/12cc_agent/core/12.1.0.5.0/bin/orabase binary does not exist You can set ORACLE_BASE manually if it is required. Resetting ORACLE_BASE to its previous value or ORACLE_HOME The Oracle base remains unchanged with value /u00/app/oracle [oracle@ORA-C1 ~]$ emctl status agent Oracle Enterprise Manager Cloud Control 12c Release Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved. --------------------------------------------------------------- Agent Version : 12.1.0.5.0 OMS Version : 12.1.0.5.0 Protocol Version : 12.1.0.1.0 Agent Home : /u01/app/oracle/12cc_agent/agent_inst Agent Log Directory : /u01/app/oracle/12cc_agent/agent_inst/sysman/log Agent Binaries : /u01/app/oracle/12cc_agent/core/12.1.0.5.0 Agent Process ID : 21024 Parent Process ID : 20909 Agent URL : https://ORA-C1.oracle-ckpt.com:3872/emd/main/ Local Agent URL in NAT : https://ORA-C1.oracle-ckpt.com:3872/emd/main/ Repository URL : https://ORA-CC.oracle-ckpt.com:4903/empbs/upload Started at : 2016-02-01 03:55:24 Started by user : oracle Operating System : Linux version 2.6.32-300.7.1.el5uek (amd64) Last Reload : (none) Last successful upload : 2016-03-30 12:14:35 Last attempted upload : 2016-03-30 12:14:35 Total Megabytes of XML files uploaded so far : 57.19 Number of XML files pending upload : 0 Size of XML files pending upload(MB) : 0 Available disk space on upload filesystem : 55.23% Collection Status : Collections enabled Heartbeat Status : Ok Last attempted heartbeat to OMS : 2016-03-30 12:17:28 Last successful heartbeat to OMS : 2016-03-30 12:17:28 Next scheduled heartbeat to OMS : 2016-03-30 12:18:28 --------------------------------------------------------------- Agent is Running and Ready [oracle@ORA-C1 ~]$ emctl upload agent Oracle Enterprise Manager Cloud Control 12c Release 5 Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved. --------------------------------------------------------------- EMD upload completed successfully [oracle@ORA-C1 ~]$ emctl status agent Oracle Enterprise Manager Cloud Control 12c Release 5 Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved. --------------------------------------------------------------- Agent Version : 12.1.0.5.0 OMS Version : 12.1.0.5.0 Protocol Version : 12.1.0.1.0 Agent Home : /u01/app/oracle/12cc_agent/agent_inst Agent Log Directory : /u01/app/oracle/12cc_agent/agent_inst/sysman/log Agent Binaries : /u01/app/oracle/12cc_agent/core/12.1.0.5.0 Agent Process ID : 21024 Parent Process ID : 20909 Agent URL : https://ORA-C1.oracle-ckpt.com:3872/emd/main/ Local Agent URL in NAT : https://ORA-C1.oracle-ckpt.com:3872/emd/main/ Repository URL : https://ORA-CC.oracle-ckpt.com:4903/empbs/upload Started at : 2016-02-01 03:55:24 Started by user : oracle Operating System : Linux version 2.6.32-300.7.1.el5uek (amd64) Last Reload : (none) Last successful upload : 2016-03-30 12:18:07 Last attempted upload : 2016-03-30 12:18:07 Total Megabytes of XML files uploaded so far : 57.2 Number of XML files pending upload : 0 Size of XML files pending upload(MB) : 0 Available disk space on upload filesystem : 55.23% Collection Status : Collections enabled Heartbeat Status : Ok Last attempted heartbeat to OMS : 2016-03-30 12:18:28 Last successful heartbeat to OMS : 2016-03-30 12:18:28 Next scheduled heartbeat to OMS : 2016-03-30 12:19:28 --------------------------------------------------------------- Agent is Running and Ready [oracle@ORA-C1 ~]$ We will check the latest status of the listener target from EM12c. As we see above image, after performing changes to the configuration the agent status showing up and in healthy status. Conclusion We’ve seen how to perform the changes of the database and listener configuration from Enterprise Manager 12c after the upgrade of the database in order to avoid false monitoring.
↧