1. copy of 11g GRID infrastructure from ealrier installed env .
a. Copy the above zipped file over to the target server.
b. Then untar the home.
c. If untar is done as root, make sure, to change the home ownership.
2. Set up Grid Infrastructure Home
a .
$ cd/clone/bin
$ perl ./clone.pl ORACLE_HOME= ORACLE_BASE= OSDBA_GROUP=dba
The output of above command will be similar to below.
./runInstaller -clone -waitForCompletion "ORACLE_HOME=/app/grid/11.2.0/grid" "ORACLE_BASE=/oracle/APP/grid" "oracle_install_OSDBA=dba" -defaultHomeName -silent -noConfig -nowait
Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB. Actual 16383 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-05-29_11-29-22PM. Please wait ...Oracle Universal Installer, Version 11.2.0.3.0 Production
Copyright (C) 1999, 2011, Oracle. All rights reserved.
You can find the log of this install session at:
/home/oragrid/oraInventory/logs/cloneActions2013-05-29_11-29-22PM.log
.................................................................................................... 100% Done.
Installation in progress (Wednesday, May 29, 2013 11:29:34 PM CDT)
........................................................................ 72% Done.
Install successful
Linking in progress (Wednesday, May 29, 2013 11:29:38 PM CDT)
Link successful
Setup in progress (Wednesday, May 29, 2013 11:30:04 PM CDT)
................. 100% Done.
Setup successful
End of install phases.(Wednesday, May 29, 2013 11:30:25 PM CDT)
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.
To register the new inventory please run the script '/home/oragrid/oraInventory/orainstRoot.sh' with root privileges.
If you do not register the inventory, you may not be able to update or patch the products you installed.
The following configuration scripts need to be executed as the "root" user.
/home/oragrid/oraInventory/orainstRoot.sh
/oracle/APP/grid/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 OraHome1 was successful.
Please check '/home/oragrid/oraInventory/logs/cloneActions2013-05-29_11-29-22PM.log' for more details.
As per above message, run the root.sh scripts as root as shown below.
3. Run root scripts
a. /home/grid/oraInventory/orainstRoot.sh
Changing permissions of /home/oragrid/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /home/oragrid/oraInventory to dba.
The execution of the script is complete.
b. /oracle/APP/grid/11.2.0/grid/root.sh
Check /oracle/APP/grid/11.2.0/grid/install/root_2013-05-29_23-34-18.log for the output of root script
4. Now register CRS as root.
c./perl/bin/perl -I/perl/lib -I/crs/install /crs/install/roothas.pl
The output will be similar to below.
Using configuration parameter file: /oracle/APP/grid/11.2.0/grid/crs/install/crsconfig_params
User ignored Prerequisites during installation
LOCAL ADD MODE
Creating OCR keys for user 'oragrid', privgrp 'dba'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node abxyzz successfully pinned.
Adding Clusterware entries to inittab
abcxyz 2013/05/14 02:50:14 /oracle/APP/grid/11.2.0/grid/cdata/abcxyz/backup_20130514_025014.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server
5. Start CRS.
a. cd/bin
b. ./crsctl check has
CRS-4638: Oracle High Availability Services is online
c. ./crsctl check css
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
d. ./crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
e. ./crsctl stop has
f. ./crsctl start has
g. ./crsctl check has
h ./crsctl check css
ps -eaf |grep cssd ---this will show cssd.bin running
a. Copy the above zipped file over to the target server.
b. Then untar the home.
c. If untar is done as root, make sure, to change the home ownership.
2. Set up Grid Infrastructure Home
a .
$ cd
$ perl ./clone.pl ORACLE_HOME=
The output of above command will be similar to below.
./runInstaller -clone -waitForCompletion "ORACLE_HOME=/app/grid/11.2.0/grid" "ORACLE_BASE=/oracle/APP/grid" "oracle_install_OSDBA=dba" -defaultHomeName -silent -noConfig -nowait
Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB. Actual 16383 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-05-29_11-29-22PM. Please wait ...Oracle Universal Installer, Version 11.2.0.3.0 Production
Copyright (C) 1999, 2011, Oracle. All rights reserved.
You can find the log of this install session at:
/home/oragrid/oraInventory/logs/cloneActions2013-05-29_11-29-22PM.log
.................................................................................................... 100% Done.
Installation in progress (Wednesday, May 29, 2013 11:29:34 PM CDT)
........................................................................ 72% Done.
Install successful
Linking in progress (Wednesday, May 29, 2013 11:29:38 PM CDT)
Link successful
Setup in progress (Wednesday, May 29, 2013 11:30:04 PM CDT)
................. 100% Done.
Setup successful
End of install phases.(Wednesday, May 29, 2013 11:30:25 PM CDT)
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.
To register the new inventory please run the script '/home/oragrid/oraInventory/orainstRoot.sh' with root privileges.
If you do not register the inventory, you may not be able to update or patch the products you installed.
The following configuration scripts need to be executed as the "root" user.
/home/oragrid/oraInventory/orainstRoot.sh
/oracle/APP/grid/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 OraHome1 was successful.
Please check '/home/oragrid/oraInventory/logs/cloneActions2013-05-29_11-29-22PM.log' for more details.
As per above message, run the root.sh scripts as root as shown below.
3. Run root scripts
a. /home/grid/oraInventory/orainstRoot.sh
Changing permissions of /home/oragrid/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /home/oragrid/oraInventory to dba.
The execution of the script is complete.
b. /oracle/APP/grid/11.2.0/grid/root.sh
Check /oracle/APP/grid/11.2.0/grid/install/root_2013-05-29_23-34-18.log for the output of root script
4. Now register CRS as root.
c.
The output will be similar to below.
Using configuration parameter file: /oracle/APP/grid/11.2.0/grid/crs/install/crsconfig_params
User ignored Prerequisites during installation
LOCAL ADD MODE
Creating OCR keys for user 'oragrid', privgrp 'dba'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node abxyzz successfully pinned.
Adding Clusterware entries to inittab
abcxyz 2013/05/14 02:50:14 /oracle/APP/grid/11.2.0/grid/cdata/abcxyz/backup_20130514_025014.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server
5. Start CRS.
a. cd
b. ./crsctl check has
CRS-4638: Oracle High Availability Services is online
c. ./crsctl check css
CRS-4530: Communications failure contacting Cluster Synchronization Services daemon
d. ./crsctl modify resource "ora.cssd" -attr "AUTO_START=1"
e. ./crsctl stop has
f. ./crsctl start has
g. ./crsctl check has
h ./crsctl check css
ps -eaf |grep cssd ---this will show cssd.bin running
No comments:
Post a Comment