Clone non-rac Grid Infrastructure

Posted: May 17, 2012 | Author: | Filed under: General DBA | Leave a comment »

[oracle@my562b bin]$ ./detachHome.sh

Starting Oracle Universal Installer…

Checking swap space: must be greater than 500 MB.   Actual 4094 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /apps/oraInventory
‘DetachHome’ was successful.

The contents of the inventory XML file looks like this:
[root@my562b ContentsXML]# cat inventory.xml
<?xml version=”1.0″ standalone=”yes” ?>
<!– Copyright (c) 1999, 2010, Oracle. All rights reserved. –>
<!– Do not modify the contents of this file by hand. –>
<INVENTORY>
<VERSION_INFO>
   <SAVED_WITH>11.2.0.2.0</SAVED_WITH>
   <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME=”OraDb11g_home1″ LOC=”/apps/oracle/product/11.2.0/db” TYPE=”O” IDX=”2″/>
<HOME NAME=”Ora11g_gridinfrahome1″ LOC=”/apps/11.2.0/grid” TYPE=”O” IDX=”1″ REMOVED=”T”/>
</HOME_LIST>
</INVENTORY>
 

[oracle@my562b bin]$ perl clone.pl -silent ORACLE_BASE=/apps/oracle ORACLE_HOME=/apps/11.2.0/grid ORACLE_HOME_NAME=Ora11g_gridinfrahome1 INVENTORY_LOCATION=/apps/oraInventory

./runInstaller -clone -waitForCompletion  “ORACLE_BASE=/apps/oracle” “ORACLE_HOME=/apps/11.2.0/grid” “ORACLE_HOME_NAME=Ora11g_gridinfrahome1″ “INVENTORY_LOCATION=/apps/oraInventory” -silent -noConfig -nowait
Starting Oracle Universal Installer…

Checking swap space: must be greater than 500 MB.   Actual 4094 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-05-09_11-33-45AM. Please wait …
 
Copyright (C) 1999, 2010, Oracle. All rights reserved.


You can find the log of this install session at:
 /apps/oraInventory/logs/cloneActions2011-05-09_11-35-10AM.log
………………………………………………………………………………………. 100% Done.


Could not backup file /apps/11.2.0/grid/rootupgrade.sh to /apps/11.2.0/grid/rootupgrade.sh.ouibak
Could not backup file /apps/11.2.0/grid/root.sh to /apps/11.2.0/grid/root.sh.ouibak

Installation in progress (Monday, May 9, 2011 11:35:29 AM CDT)
………………………………………………………………                                                        72% Done.
Install successful

Linking in progress (Monday, May 9, 2011 11:35:38 AM CDT)

Link successful

Setup in progress (Monday, May 9, 2011 11:36:57 AM CDT)
…………….                                                100% Done.
Setup successful

End of install phases.(Monday, May 9, 2011 11:37:05 AM CDT)
WARNING:
The following configuration scripts need to be executed as the “root” user.
/apps/11.2.0/grid/root.sh
To execute the configuration scripts:
    1. Open a terminal window
    2. Log in as “root”
    3. Run the scripts
   
Run the script on the local node.
The cloning of Ora11g_gridinfrahome1 was successful.
Please check ‘/apps/oraInventory/logs/cloneActions2011-05-09_11-35-10AM.log’ for more details.

Contents of inventory XML after the clone:
[root@my562b ContentsXML]# cat inventory.xml
<?xml version=”1.0″ standalone=”yes” ?>
<!– Copyright (c) 1999, 2010, Oracle. All rights reserved. –>
<!– Do not modify the contents of this file by hand. –>
<INVENTORY>
<VERSION_INFO>
   <SAVED_WITH>11.2.0.2.0</SAVED_WITH>
   <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME=”OraDb11g_home1″ LOC=”/apps/oracle/product/11.2.0/db” TYPE=”O” IDX=”2″/>
<HOME NAME=”Ora11g_gridinfrahome1″ LOC=”/apps/11.2.0/grid” TYPE=”O” IDX=”1″/>
</HOME_LIST>
</INVENTORY>


[oracle@my562b bin]$ cd ../..
[oracle@my562b grid]$ ./root.sh
Check /apps/11.2.0/grid/install/root_my562b_2011-05-09_11-39-15.log for the output of root script



What a mess .. trying force delete and re-configuring GRID Home

I don’t think I need to go through the exercise of detaching and re-cloning the oracle home
I think the roothas.pl with the deconfig option followed with the force option works if all else fails.
The other option to deconfig is:
$ORACLE_HOME/perl/bin/perl -I $ORACLE_HOME/perl/lib -I $ORACLE_HOME/crs/install $ORACLE_HOME/crs/install/roothas.pl -delete
[root@my562b utl]# /apps/11.2.0/grid/crs/install/roothas.pl -deconfig -force

Using configuration parameter file: /apps/11.2.0/grid/crs/install/crsconfig_params
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Stop failed, or completed with errors.
CRS-4639: Could not contact Oracle High Availability Services
CRS-4000: Command Delete failed, or completed with errors.
CLSU-00100: Operating System function: opendir failed with error data: 2
CLSU-00101: Operating System error message: No such file or directory
CLSU-00103: error location: scrsearch1
CLSU-00104: additional error information: cant open scr home dir scls_scr_getval
CRS-4544: Unable to connect to OHAS
CRS-4000: Command Stop failed, or completed with errors.
ACFS-9459: ADVM/ACFS is not supported on this OS version: ’2.6.32-100.26.2.el5
‘
ACFS-9201: Not Supported
Successfully deconfigured Oracle Restart stack
[root@my562b utl]# $ORACLE_HOME/perl/bin/perl -I $ORACLE_HOME/perl/lib -I $ORACLE_HOME/crs/install $ORACLE_HOME/crs/install/roothas.pl
Using configuration parameter file: /apps/11.2.0/grid/crs/install/crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user ‘oracle’, privgrp ‘oinstall’..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ‘root’, privgrp ‘root’..
Operation successful.
CRS-4664: Node my562b successfully pinned.
Adding daemon to inittab
ACFS-9459: ADVM/ACFS is not supported on this OS version: ’2.6.32-100.26.2.el5
‘

my562b     2011/05/09 11:50:06     /apps/11.2.0/grid/cdata/my562b/backup_20110509_115006.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server
[root@my562b bin]# ./crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘my562b’
CRS-2673: Attempting to stop ‘ora.evmd’ on ‘my562b’
CRS-2677: Stop of ‘ora.evmd’ on ‘my562b’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘my562b’ has completed
CRS-4133: Oracle High Availability Services has been stopped.
[root@my562b bin]# ./crsctl start has
CRS-4123: Oracle High Availability Services has been started.

[oracle@my562b admin]$ srvctl add listener
[oracle@my562b admin]$ srvctl add asm -d ‘ORCL:*’
[oracle@my562b admin]$ srvctl start listener
[oracle@my562b admin]$ srvctl start asm
[oracle@my562b admin]$ srvctl status diskgroup -g data
PRCA-1000 : ASM Disk Group DATA does not exist
PRCR-1001 : Resource ora.DATA.dg does not exist
[oracle@my562b admin]$ asmcmd

ASMCMD> lsdg
ASMCMD> mount data   
ASMCMD> mount mydata
ASMCMD> mount myfra


Now the database home 

[oracle@my562b bin]$ ./detachHome.sh

Starting Oracle Universal Installer…

Checking swap space: must be greater than 500 MB.   Actual 4091 MB    Passed
The inventory pointer is located at /etc/oraInst.loc
The inventory is located at /apps/oraInventory
‘DetachHome’ was successful.

[root@my562b bin]# cd /apps/oraInventory/ContentsXML/
You have new mail in /var/spool/mail/root
[root@my562b ContentsXML]# cat inventory.xml
<?xml version=”1.0″ standalone=”yes” ?>
<!– Copyright (c) 1999, 2010, Oracle. All rights reserved. –>
<!– Do not modify the contents of this file by hand. –>
<INVENTORY>
<VERSION_INFO>
   <SAVED_WITH>11.2.0.2.0</SAVED_WITH>
   <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME=”Ora11g_gridinfrahome1″ LOC=”/apps/11.2.0/grid” TYPE=”O” IDX=”1″/>
</HOME_LIST>
</INVENTORY>

[oracle@my562b bin]$ cd ../../clone/bin

[oracle@my562b bin]$ perl clone.pl -silent ORACLE_BASE=/apps/oracle ORACLE_HOME=/apps/oracle/product/11.2.0/db ORACLE_HOME_NAME=OraDb11g_home1 INVENTORY_LOCATION=/apps/oraInventory

./runInstaller -clone -waitForCompletion  “ORACLE_BASE=/apps/oracle” “ORACLE_HOME=/apps/oracle/product/11.2.0/db” “ORACLE_HOME_NAME=OraDb11g_home1″ “INVENTORY_LOCATION=/apps/oraInventory” -silent -noConfig -nowait
Starting Oracle Universal Installer…

Checking swap space: must be greater than 500 MB.   Actual 4090 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-05-09_12-13-20PM. Please wait …Oracle Universal Installer, Version 11.2.0.2.0 Production
Copyright (C) 1999, 2010, Oracle. All rights reserved.

You can find the log of this install session at:
 /apps/oraInventory/logs/cloneActions2011-05-09_12-13-20PM.log
………………………………………………………………………………………. 100% Done.



Installation in progress (Monday, May 9, 2011 12:13:56 PM CDT)
……………………………………………………………………                                                  78% Done.
Install successful

Linking in progress (Monday, May 9, 2011 12:14:05 PM CDT)

Link successful

Setup in progress (Monday, May 9, 2011 12:17:12 PM CDT)
Setup successful

End of install phases.(Monday, May 9, 2011 12:17:18 PM CDT)
WARNING:
The following configuration scripts need to be executed as the “root” user.
/apps/oracle/product/11.2.0/db/root.sh
To execute the configuration scripts:
    1. Open a terminal window
    2. Log in as “root”
    3. Run the scripts
   
The cloning of OraDb11g_home1 was successful.
Please check ‘/apps/oraInventory/logs/cloneActions2011-05-09_12-13-20PM.log’ for more details.

[root@my562b ContentsXML]# cd /apps/oracle/product/11.2.0/db
[root@my562b db]# ./root.sh
Check /apps/oracle/product/11.2.0/db/install/root_my562b_2011-05-09_12-19-12.log for the output of root script

[root@my562b db]# cd -
/apps/oraInventory/ContentsXML
[root@my562b ContentsXML]# cat inventory.xml
<?xml version=”1.0″ standalone=”yes” ?>
<!– Copyright (c) 1999, 2010, Oracle. All rights reserved. –>
<!– Do not modify the contents of this file by hand. –>
<INVENTORY>
<VERSION_INFO>
   <SAVED_WITH>11.2.0.2.0</SAVED_WITH>
   <MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME=”Ora11g_gridinfrahome1″ LOC=”/apps/11.2.0/grid” TYPE=”O” IDX=”1″/>
<HOME NAME=”OraDb11g_home1″ LOC=”/apps/oracle/product/11.2.0/db” TYPE=”O” IDX=”2″/>
</HOME_LIST>
</INVENTORY>

Best Practices for Gathering Optimizer Statistics

Posted: April 17, 2012 | Author: | Filed under: General DBA | Comments Off

A must read for everyone:  twp-bp-optimizer-stats-04042012-1577139.pdf

ASM Disk Group Configuration

Posted: April 16, 2012 | Author: | Filed under: ASM, Exadata, General DBA, Linux | Comments Off

ASM Disk Group Configuration

Everyone should be leveraging ASMLIB instead of using block devices to create our ASM disk groups    

Proper ASM configuration and standardization and following best practices is just as important in a virtualized environment as it is in a bare metal environment            
First, create ASMLIB disks with oracleasm

  • sudo to root
  • cd /etc/init.d 
  • ./oracleasm createdisk DATA101_DISK000 /dev/oracle/DATA101_disk000p1
    • Repeat for each disk
  • On other RAC nodes
    • ./oracleasm scandisks
    • ./oracleasm listdisks


List of available disks on April 29, 2012
cd /dev/oracle
lrwxrwxrwx 1 root root 8 Apr 28 16:22 DATA501_disk009p1 -> ../dm-85

lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk003p1 -> ../dm-105
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk003p1 -> ../dm-100
lrwxrwxrwx 1 root root 8 Apr 28 16:22 DATA101_disk001p1 -> ../dm-99
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk002p1 -> ../dm-102
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk005p1 -> ../dm-110
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk004p1 -> ../dm-101
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA101_disk000p1 -> ../dm-104
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk006p1 -> ../dm-111
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk008p1 -> ../dm-107
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk004p1 -> ../dm-112
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk000p1 -> ../dm-108
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk002p1 -> ../dm-109
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk001p1 -> ../dm-103
lrwxrwxrwx 1 root root 9 Apr 28 16:22 DATA501_disk007p1 -> ../dm-106

Naming Convention Legend for Disk Groups

  • Diskgroup names will be DATA101 or PF101 for RAID 10 disk groups
  • Diskgruop names will DATA501 or PF501 for RAID 5 disk groups
Naming Convention Legend for Disks
  • pd = production data
  • pf = production fast recovery area(fra)
  • dd = would be development data
  • df = would be development fra
  • 101 = raid 10 first disk group
  • 501 = raid 05 first disk group
  • And _diskxxx can be disk000 to disk999


Modify /etc/sysconfig/oracleasm (on each node)

As root:  Make changes to the following lines:
# ORACLEASM_SCANORDER: Matching patterns to order disk scanning

ORACLEASM_SCANORDER=”dm-”

# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan
ORACLEASM_SCANEXCLUDE=”sd”
   Important Notes:

  • Only use the partitioned disk when creating ASMLIB disks
  • The partitioned disk will have p1, p2, etc. at the end of the device name
  • After you scan the disk, you should see an entry in /proc/partitions
  • Do NOT use /dev/oracle devices
  • Instead use /dev/mapper devices

RAID 10
——-
[root@dllprdorl01 tmp]# cat ora_asm.txt

/etc/init.d/oracleasm createdisk DATA101_DISK000 /dev/mapper/DATA101_disk000p1
/etc/init.d/oracleasm createdisk DATA101_DISK001 /dev/mapper/DATA101_disk001p1
/etc/init.d/oracleasm createdisk DATA101_DISK002 /dev/mapper/DATA101_disk002p1
/etc/init.d/oracleasm createdisk DATA101_DISK003 /dev/mapper/DATA101_disk003p1
/etc/init.d/oracleasm createdisk DATA101_DISK004 /dev/mapper/DATA101_disk004p1

RAID 5
——
/etc/init.d/oracleasm createdisk DATA501_DISK000 /dev/mapper/DATA501_disk000p1
/etc/init.d/oracleasm createdisk DATA501_DISK001 /dev/mapper/DATA501_disk001p1
/etc/init.d/oracleasm createdisk DATA501_DISK002 /dev/mapper/DATA501_disk002p1
/etc/init.d/oracleasm createdisk DATA501_DISK003 /dev/mapper/DATA501_disk003p1
/etc/init.d/oracleasm createdisk DATA501_DISK004 /dev/mapper/DATA501_disk004p1
/etc/init.d/oracleasm createdisk DATA501_DISK005 /dev/mapper/DATA501_disk005p1
/etc/init.d/oracleasm createdisk DATA501_DISK006 /dev/mapper/DATA501_disk006p1
/etc/init.d/oracleasm createdisk DATA501_DISK007 /dev/mapper/DATA501_disk007p1
/etc/init.d/oracleasm createdisk DATA501_DISK008 /dev/mapper/DATA501_disk008p1
/etc/init.d/oracleasm createdisk DATA501_DISK009 /dev/mapper/DATA501_disk009p1



ASM Disk Group Information

  • First, we will set our Allocation Unit (AU) to 4MB in size
  • Second, we will use ‘ORCL:*’ disks instead of block devices when creating our new disk groups
SQL> alter system set asm_diskstring=’/dev/oracle’,'ORCL:PD*’;

 
System altered.
 
Add the following to the init+ASM1.ora on each node
For automatic mount of diskgroups
asm_diskgroups=’DATA03′,’DATA60′,’FRA03′,’FRA60′,’DATA101′,’DATA501′ 


#asm_diskstring=’/dev/oracle’
asm_diskstring=’/dev/oracle’,'ORCL:PD*’
 
For the time being, manually mount the diskgroups on each node:
SQL> alter system set asm_diskstring=’/dev/oracle’,'ORCL:PD*’;

System altered.

SQL> alter diskgroup DATA101 mount;
Diskgroup altered.

SQL> alter diskgroup DATA501 mount;
Diskgroup altered.
 
 
Creating ASM Disk Groups

RAID 10 DATA Disk Group

+ASM1 > cat cr_DATA101.sql

create diskgroup DATA101 external redundancy disk ‘ORCL:DATA101_DISK000′,
‘ORCL:DATA101_DISK001′,
‘ORCL:DATA101_DISK002′,
‘ORCL:DATA101_DISK003′,
‘ORCL:DATA101_DISK004′
ATTRIBUTE ‘au_size’ = ’4M’,
‘compatible.rdbms’ = ’11.1′,
‘compatible.asm’ = ’11.1′;

RAID 5 DATA Disk Group
+ASM1 > cat cr_DATA501.sql

create diskgroup DATA501 external redundancy disk ‘ORCL:DATA501_DISK000′,
‘ORCL:DATA501_DISK001′,
‘ORCL:DATA501_DISK002′,
‘ORCL:DATA501_DISK003′,
‘ORCL:DATA501_DISK004′,
‘ORCL:DATA501_DISK005′,
‘ORCL:DATA501_DISK006′,
‘ORCL:DATA501_DISK007′,
‘ORCL:DATA501_DISK008′,
‘ORCL:DATA501_DISK009′
ATTRIBUTE ‘au_size’ = ’4M’,
‘compatible.rdbms’ = ’11.1′,
‘compatible.asm’ = ’11.1′;

Parse OSWatcher Logs for cpu utilization

Posted: March 1, 2012 | Author: | Filed under: General DBA, Linux, RAC | Comments Off

$/opt/app/oracle/util/OSW/osw/archive/oswtop
+ASM1 > grep -i “^top” $(ls -l |grep “May  3″ |awk {‘print $9′}) >/tmp/load_02MAY11.txt
 
rac22:/tmp
+ASM1 > tail load_02MAY11.txt
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:55:29 up 2 days,  1:19,  4 users,  load average: 5.05, 9.17, 12.54
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:55:59 up 2 days,  1:19,  4 users,  load average: 5.60, 8.88, 12.34
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:56:29 up 2 days,  1:20,  4 users,  load average: 5.17, 8.46, 12.09
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:56:59 up 2 days,  1:20,  4 users,  load average: 4.65, 8.02, 11.82
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:57:29 up 2 days,  1:21,  4 users,  load average: 6.02, 7.99, 11.69
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:57:59 up 2 days,  1:21,  4 users,  load average: 4.96, 7.55, 11.42
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:58:29 up 2 days,  1:22,  4 users,  load average: 4.41, 7.17, 11.18
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:58:59 up 2 days,  1:22,  4 users,  load average: 4.66, 6.98, 10.98
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:59:29 up 2 days,  1:23,  4 users,  load average: 4.32, 6.66, 10.75
rac22.visctech.com_top_11.05.02.2200.dat:top – 22:59:59 up 2 days,  1:23,  4 users,  load average: 3.87, 6.33, 10.51

Using logrotate to manage log files

Posted: February 29, 2012 | Author: | Filed under: ASM, General DBA, Linux | Comments Off

We are leveraging the logrotate linux executable to rotate ASM log files, database alert log files, and listener log files.  With log rotate we have the option to compress the previous version of the log file, keep X amount of copied of the log file, rotate the log file on a hourly/daily/weekly/monthly  intervals, etc.

rac22:/apps/oracle/general/sh

DBATOOLS3 – oracle: cat log_rotate.rac22.ksh
export CONF=/tmp/alertlog.conf
cat <<!! >$CONF
/apps/oracle/diag/rdbms/dbatools/DBATOOLS3/trace/alert_DBATOOLS3.log {
weekly
copytruncate
rotate 4
compress
}
!!
 
logrotate -s $SH/log_rotate_status -f $CONF
 
export CONF=/tmp/alert_asm.conf
cat <<!! >$CONF
/apps/oracle/diag/asm/+asm/+ASM3/trace/alert_+ASM3.log {
weekly
copytruncate
rotate 4
compress
}
!!
logrotate -s $SH/log_rotate_status -f $CONF
 
export CONF=/tmp/listener.conf
cat <<!! >$CONF
/apps/oracle/diag/tnslsnr/rac22/listener/trace/listener.log {
weekly
copytruncate
rotate 4
compress
}
!!
logrotate -s $SH/log_rotate_status -f $CONF
 
export CONF=/tmp/extproc_listener.conf
cat <<!! >$CONF
/apps/oracle/diag/tnslsnr/rac22/extproc_listener/trace/extproc_listener.log {
monthly
copytruncate
rotate 4
compress
}
!!
logrotate -s $SH/log_rotate_status -f $CONF
 
 
export CONF=/tmp/alertlog.conf
cat <<!! >$CONF
/apps/oracle/diag/rdbms/gridrac/GRIDRAC3/trace/alert_GRIDRAC3.log {
weekly
copytruncate
rotate 4
compress
}
!!
logrotate -s $SH/log_rotate_status -f $CONF

dbca delete database in silent mode

Posted: February 25, 2012 | Author: | Filed under: General DBA | Comments Off
$ cat del_DBATOOLS_dbca.txt
dbca -silent -deleteDatabase -sourceDB DBATOOLS -sysDBAUserName sys -sysDBAPassword xxx4DBA

RMANDR – oracle: ksh del_DBATOOLS_dbca.txt

Connecting to database
4% complete
9% complete
14% complete
19% complete
23% complete
28% complete
47% complete
Updating network configuration files
52% complete
Deleting instance and datafiles
76% complete
100% complete
Look at the log file “/apps/oracle/cfgtoollogs/dbca/DBATOOLS.log” for further details.

RAC with NFS

Posted: January 30, 2012 | Author: | Filed under: General DBA, Linux, RAC | Comments Off


In the table below 

  • Binaries is the shared mount points where the Oracle Home and CRS_HOME is installed.
  • Datafiles includes Online Logs, Controlfile and Datafiles
  • nfsvers and vers are identical on those OS platforms that has nfsvers.  The ver option is an alternative to the nfsvers option. It is included for compatibility with other operating systems,

Operating System

 Mount options for Binaries Mount options for Oracle Datafiles Mount options for CRS Voting Disk and OCR
Sun Solaris *

rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,

vers=3,suid

 rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,
forcedirectio, vers=3,suid		 rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,vers=3,
noac,forcedirectio
AIX (5L) **

rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,

vers=3,timeo=600

cio,rw,bg,hard,nointr,rsize=32768,
wsize=32768,proto=tcp,noac,
vers=3,timeo=600

cio,rw,bg,hard,intr,rsize=32768,
wsize=32768,tcp,noac,
vers=3,timeo=600
HPUX 11.23 ***  – rw,bg,vers=3,proto=tcp,noac,
hard,nointr,timeo=600,
rsize=32768,wsize=32768,suid		 rw,bg,vers=3,proto=tcp,noac,
forcedirectio,hard,nointr,timeo=600,
rsize=32768,wsize=32768,suid		 rw,bg,vers=3,proto=tcp,noac,
forcedirectio,hard,nointr,timeo=600
,rsize=32768,wsize=32768,suid
Windows Not Supported Not Supported Not Supported
Linux x86
#
****

rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp, vers=3,
timeo=600, actimeo=0

 rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600

rw,bg,hard,nointr,rsize=32768,
wsize=32768,tcp,actimeo=0,
vers=3,timeo=600
Linux x86-64 #
****		 rw,bg,hard,nointr,rsize=32768,
 wsize=32768,tcp,vers=3,
timeo=600, actimeo=0		 rw,bg,hard,nointr,rsize=32768, 
wsize=32768,tcp,actimeo=0, 
vers=3,timeo=600		 rw,bg,hard,nointr,rsize=32768, 
wsize=32768,tcp,vers=3,
timeo=600,actimeo=0
Linux – Itanium rw,bg,hard,nointr,rsize=32768, 
wsize=32768,tcp,vers=3,
timeo=600, actimeo=0		 rw,bg,hard,nointr,rsize=32768, 
wsize=32768,tcp,actimeo=0, 
vers=3,timeo=600		 rw,bg,hard,nointr,rsize=32768, 
wsize=32768,tcp,vers=3,
timeo=600,actimeo=0

* NFS mount option “forcedirectio” is required on Solaris platforms when mounting the OCR/CRS files when using Oracle 10.1.0.4 or 10.2.0.2 or later (Oracle unpublished bug 4466428) 
** AIX is only supported with NAS on AIX 5.3 TL04 and higher with Oracle 10.2.0.1 and later (NetApp) 
*** NAS devices are only supported with HPUX 11.23 or higher ONLY 
**** As per BUG 11812928, the ‘intr’ & ‘nointr’ are deprecated in OEL 5.6 kernels and up including Oracle Linux 6. It is harmless to still include it, but the “NFS: ignoring mount option: nointr” will appears. This message can be ingnored.

# These mount options are for Linux kernels 2.6 and above for older kernels please check Note 279393.1

Due to Unpublished bug 5856342, it is necessary to use the following init.ora parameter when using NAS with all versions of RAC on Linux (x86 & X86-64 platforms) until 10.2.0.4. This bug is fixed and included in 10.2.0.4 patchset.
filesystemio_options = DIRECTIO

 Single Instance

 

Operating System

 Mount options for Binaries Mount options for Oracle Datafiles
Sun Solaris *
(8, 9, 10)

rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,proto=tcp,suid

 rw,bg,hard,rsize=32768,wsize=32768,vers=3,[forcedirectio or llock],nointr,proto=tcp,suid
AIX (5L) **

rw,bg,hard,rsize=32768,wsize=32768,vers=3,intr,timeo=600,proto=tcp

rw,bg,hard,rsize=32768,wsize=32768,vers=3,cio,intr,timeo=600,proto=tcp
HPUX 11.23 **** rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp,suid rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp, suid, forcedirectio
Windows Not Supported Not Supported
Linux x86
#		 rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp,actimeo=0*
Linux x86-64 # rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp,actimeo=0*
Linux – Itanium rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp

 

* actime=0 or noac can be used

Create Seeded Database with dbca

Posted: November 29, 2011 | Author: | Filed under: General DBA, RMAN | Comments Off

Create a golden image of your database and create a template of that database for future database provisioning

Create Seeded Database with dbca

With proper planning and infrastructure, you should be able to provision a new database in matter of minutes rather than days.  You can create a template of a golden image of your database with all the corporate standards, auditing requirements and security compliance components.

PSU Compliance

Posted: July 14, 2011 | Author: | Filed under: General DBA | Leave a comment »

As part of the best practice compliance, you should apply the latest Patch Set Update (PSU) or be at a N-1 PSU release cycle specific to your database release. For the latest PSU, please check the following Metalink note:
• Oracle Recommended Patches — Oracle Database [ID 756671.1]

As of end of February 2011, 11.2.0.2.1 PSU is available by downloading patch number 10248523. For Oracle Database 11g Release 1 customers, 11.1.0.7.6 Patch Set Update (Patch 10248531) is available, and the Data Guard Broker Recommended Patch Bundle #1 is also available (Patch 7628357).

Database Growth Trend Report By The Week

Posted: July 14, 2011 | Author: | Filed under: General DBA | Leave a comment »

Here’s a new version of the database growth report. The new version determines the growth trend for the database for the past one year. Check out this script:

set pages 255 lines 2000 trims on
compute sum of growth_in_gb on report
col week_number for a35
break on report
select to_char(creation_time, 'ww mon yyyy') week_number, round(sum(bytes)/1024/1024/1024,1) growth_in_gb
from sys.v_$datafile
where creation_time &gt; SYSDATE-365
group by to_char(creation_time, 'ww mon yyyy')
order by 1
/

Posted by Charles Kim, Oracle ACE Director

← Older Entries