Grid DBA

My OEM environment consists of two management servers (OMS) for high availability ( level 3 HA ). We also have a SLB configured for the OMSs but they haven't been configured with the SLB virtual hostname. I know, this sounds very confusing but there's a difference. Essentially they act as individual OMSs since agents can only upload to one OMS and console is pointed to a single OMS. The load balancer is a F5 BIG-IP and all the configuration setting were done for using OEM. This whitepaper clearly describes how to do this.   After upgrading my OEM environment from 12.1.0.2.0 to 12.1.0.3.0 I decided to reconfigure the OMSs to use the SLB virtual hostname. Reconfiguring the SLB involves securing the OMSs with the virtual hostname of the SLB. [oracle@oms1[]-/u01/Oracle/Middleware/oms/bin >./emctl secure oms -host oemcc.example.com -secure_port 4899 -slb_port 4889 -slb_console_port 443 Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 20...

I just had the arduous task of sifting through numerous documents on My Oracle Support (formerly Metalink) to determine whether or not my Grid Control infrastructure needs to be patched for DST change on November 1, 2009 in the US. Global Support could have done a better job at consolidating the documents since it's a pretty common task. Instead, I had to be going back and forth between six or so documents in order to try and figure out what I need to change. In the end I determined that rather apply patch sets to the management agents below 10.2.0.5, just to apply the 10.2.0.5 patch set instead to be on the safe side. The OMS Java also required DST updates. Since the OMS is running on AIX 5.3 I had to use the IBM Timezone Java Update Utility (JTZU). Steps to update OMS Java Download the JTZU utility here http://www.ibm.com/developerworks/java/jdk/dst/jtzu.html Follow the instructions to extract and install the utility Stop the OMS using opmnctl stopall Apply the update to the ...