Amazon books

Thursday, January 30, 2014

Check if patch is a rolling patch Upgrade

Just run command like below and you get the answer:

#####################################################################
[hostname-+ASM1]/tmp/14727310> opatch query -is_rolling_patch /tmp/14727310/14727310
Oracle Interim Patch Installer version 11.2.0.3.6
Copyright (c) 2013, Oracle Corporation.  All rights reserved.


Oracle Home       : /opt/oracle/products/11.2/grid
Central Inventory : /opt/oracle/oraInventory
   from           : /opt/oracle/products/11.2/grid/oraInst.loc
OPatch version    : 11.2.0.3.6
OUI version       : 11.2.0.3.0
Log file location : /opt/oracle/products/11.2/grid/cfgtoollogs/opatch/opatch2014-01-30_18-43-03PM_1.log

--------------------------------------------------------------------------------
 Patch is a rolling patch: true



OPatch succeeded.
[hostname-+ASM1]/tmp/14727310>
#####################################################################

Best Regards,
Paulo Portugal

Monday, January 27, 2014

Don't forget to set PGA_AGGREGATE_LIMIT in 12c Database

As per documentation :

"This feature limits the total amount of Program Global Area (PGA) that an instance can allocate, using a parameter called PGA_AGGREGATE_LIMIT. When the instance has allocated the PGA_AGGREGATE_LIMIT amount of PGA, sessions with the highest amount of allocated PGA are stopped until the limit is complied with.
This feature is important for consolidation because, without a hard limit, the instance can become unstable due to excessive paging. Excessive paging is one of the leading causes of instance eviction in an Oracle RAC database and can cause a multitude of performance and stability problems."

Best Regards,
Paulo Portugal

Thursday, January 16, 2014

Fixing RMAN-04022 in a simple RMAN backup


If you are getting this error below while trying to backup your database:

RMAN> run
2> {
3> allocate channel ch1 device type disk format '+DG_OTM_BACKUP' CONNECT='sys/c4c1ld1s2012@BWOTMPR1';
4> backup as compressed backupset incremental level 0 database tag 'BKP_Full_Disk';
5> }

using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-12001: could not open channel ch1
RMAN-10008: could not create channel context
RMAN-10003: unable to connect to target database
RMAN-04022: target database mount id 2149207483 does not match channel's mount id 2141641889


Just try to run the same command on another instance of your RAC database.

For me this works. I just didn't realized yet what was the root cause for that. DBID is ok of course.

Best Regards,
Paulo Portugal

Thursday, January 9, 2014

Don't forget to generate ASM Metadata Backup - MD_BACKUP

It's simple and can be very helpful!

Create a shell script like bellow and schedule it in your control manager, appwrx or crontab.

cat backup_asm_metadata.sh
rm -rf /tmp/backup_asm_metadata_MYDB.bkp
asmcmd md_backup -b /tmp/backup_asm_metadata_MYDB.bkp

Best Regards,
Paulo Portugal