Grid DBA

Disclaimer: The steps described in this post have only been tested in a lab environment. Verify that your organization's security policy isn't being violated when doing any of these steps. Twitter is a public social networking platform and has inherent security risks. I will not accept responsibility if you perform this in your production environment. Many applications built in the past couple of years have integrated social networking widgets (useful or not) to connect a social world via Twitter, Facebook, Google+ etc. However, most enterprise applications still rely on email as the primary notification method. Oracle Enterprise Manager Cloud Control 12c allows us to send notifications for incidents, events, jobs out of the box via email. In addition, EM12c supports advanced notification methods including OS scripts, PL/SQL scripts and SNMP traps. For the complete description of Notification Methods you can read the chapter in the Oracle Enterprise Manager Cloud Control...

The latest release of Oracle Enterprise Manager Cloud Control 12c (12.1.0.2) is accompanied by a Database template pre-configured for the repository. I was quite pleased to see this addition, since installing Enterprise Manager required some upfront footwork in configuring the database to be used as the repository. Personally, I was a bit annoyed every time the installer complained about parameters that it needed changed on the repository database during installation  (though some we not mandatory during installation). As a pre-requisite to using the template you should have a software-only installation of a Oracle 11.2.0.3 RDBMS software. The installation instructions warn that the template is suitable for a Simple Install. However you may also use it as a basis of an Advanced Installation. You can read the rest of the instructions here . Note: The instructions in the documentation has a screenshot of a Oracle Database 12c DBCA instead of the 11.2.0.3 DBCA. I suspect this...

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 ...