Grid DBA

Recently I was running some tests in my lab environment consisting of two Oracle 11.2.0.3 databases on separate RHEL 6.2 VMs. The databases were configured in a Data Guard configuration and used ASM as storage. However, I ran into an issue where my standby database was becoming out of sync with the primary database because the standby was out of disk space. At the time I couldn't request additional storage for my standby (that's what happens when you work at 1:00 am while everyone works normal hours) and I needed to complete my testing. The standby server had some NFS mounted shares that had plenty of space however. This is where social interaction is of benefit because I can recall having several discussions with fellow colleagues on twitter about choosing to use NFS as ASM devices and under what conditions one would choose such a route. Yury also wrote up a blog  post about it. This seemed like a good opportunity to test it out. Only this time I will be mixing ASM block de...

Thanks to @BrianPardy for tweeting the availability of the first patch set update for Oracle Enterprise Manager 12.1.0.2.0. Brian also blogged about it. The PSU Readme lists quite a number of bugs fixed in the PSU. Surprisingly the application of the patch is quite easy. I applied it to my 12.1.0.2.0 lab environment without any issues. Just to test for real application on test and production servers. Download the patch  14840279  from My Oracle Support to your OMS server. Extract the zip file Make sure opatch is in your PATH. [oracle@oem3 14840279]$ which opatch /usr/bin/which: no opatch in (/u01/app/oracle/Middleware/oms/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oracle/bin) [oracle@oem3 14840279]$ export PATH=$OMS_HOME/OPatch:$PATH [oracle@oem3 14840279]$ which opatch /u01/app/oracle/Middleware/oms/OPatch/opatch  Set your ORACLE_HOME environment variable to your OMS Home. [oracle@oem3 14840279]$ echo ...