Just to make you smile and let you remember all those sweet holidays I would like to congratulate you and wish you MERRY CHRISTMAS! in Oracle style:
Hey ALL! I just got a very good present from Santa :) I Passed 1Z1-536 Oracle Exadata 11g Essentials and 1Z1-515 Data Warehousing 11g Essentials certification exams. How cool it is if small things like these can make you rejoice like a child :) I am still smiling ….
For last few months I was part of the Pythian’s team helping implement Oracle 11gR2 Clusters for different Oracle customers. All the implementations had different requirements and configurations, however, in all cases, the client’s DBAs made the same mistake over and over again. They used sqlplus and lsnrctl utilities to manage (start/stop) databases and listeners. This is totally wrong in the 11gR2 Cluster world. The following commands are just few examples on how you should start/stop Oracle processes
11gR2, lib32 directory no longer exists and 32 bit libraries are no longer provided. Which means that there is no way to use 32 bit Perl to connect to Oracle. BTW. This applies to other 32 bit clients as well. I’ve heard that SAP can’t support 11gR2 for a similar reason. What do we do? Here are the options.
Sorry, no funny nick name for version 1.27 but here is the scoop on it anyway. This version removes ‘PERL_POLLUTE’ and adds in PL_ so it will be fully compatible with Perl 5.13. So in a nutshell 1.27 is a single issue maintenance release.
Welcome to Log Buffer, the weekly news update of happenings in the database world.
In this post I want to talk about updating ASMLIB after or before updating kernel version. Beginning oracleasm-support version 2.1.0 and higher we can use the embedded function “update-driver” which can help us to save time and simplify the process of updating ASMLIB driver.
I always tell DBAs to practice their restore skills because this is one area that you are not allowed to get wrong. Having experience with different types of restores give you the confidence to do the right thing in an emergency. However, I noticed that when it comes to practicing, not all DBAs are equally imaginative on what to practice. Practicing the same failure over and over is not the best possible practice. Here are few scenarios you should be able to recover from
The past four days have found me very frustrated and at wits’ end while testing upgrades of standalone Oracle Grid Infrastructure (ASM) 184.108.40.206 to 220.127.116.11 on RHEL/OEL 5 VMs. The upgrade would seem to go fine, but after rebooting, I would see ASM and LISTENER running under the old (18.104.22.168) grid home directories again. This is the second bug with the 22.214.171.124 upgrade process that I’ve encountered.
Welcome to Log Buffer, the weekly round up of news and happenings in the database world.