After building the complete Infra structure for Oracle (Grid Infra with Asm) and Rdbms in 188.8.131.52.0. version this Database Administrator is now facing a new challenge made by his Project leader. Please investigate the consequences of a Operating Upgrade from Red Hat Linux 5 ( 5.6) to (5.7) and change your Oracle environment to adapt to the changed Operating system. As they say often say in the Netherlands the Customer is King so this Admin was on his way. And of course set up a plan in which this will be done one step at the time , starting with a Test box. Because even with Kings the Dba should consider a Quote of one of the Oracle gurus (Arup Nanda : What’s more important guts or caution?” I would say pragmatism, bordering on caution; not guts. And i do believe the Guru is right in this matter.
Relinking Oracle software after Upgrading RH 5 from (5.6) to (5.7)
Of course Documentation is most and reading carefully will be everything in this world:
Stopping the databases under control in an easy way:
As prep for the relinking of the software I performed following steps:
srvctl status home -o /opt/oracle/product/112_ee_64/db -s /var/tmp/state_file.status
srvctl stop home -o /opt/oracle/product/112_ee_64/db -s /var/tmp/state_file.dmp
In order to relink the Rdbms software:
After shutting down the databases (see above):
Had the ORACLE_HOME set properly
Note: the process was writing relink log to:/opt/oracle/product/112_ee_64/db/install/relink.log. Tailing that log is a good recommendation.
In Order to relink the Oracle Restart software:
Prepare the Oracle Grid Infrastructure for a Standalone Server home for modification using the following procedure:
1. Logged in as the Oracle Grid Infrastructure software owner user (often the user ORACLE) and change the directory to the path Grid_home
/bin where Grid_home is the path to the Oracle Grid Infrastructure home:
2. Shut down the Oracle Restart stack using the following command:
crsctl stop has –f
This will show:
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘<server>’
CRS-2673: Attempting to stop ‘ora.LISTENER.lsnr’ on ‘<server>’
CRS-2677: Stop of ‘ora.LISTENER.lsnr’ on'<server>’ succeeded
CRS-2673: Attempting to stop ‘ora.evmd’ on ‘<server>’
CRS-2677: Stop of ‘ora.evmd’ on ‘<server>’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘<server>’ has completed
CRS-4133: Oracle High Availability Services has been stopped.
Then it was time for the next step:
Relink Oracle Grid Infrastructure for a Standalone Server using the following procedure:
3. Had to login as ROOT
4. # cd /opt/crs/product/112_ee_64/crs/crs/install
5. # perl roothas.pl -unlock
6. Log in as the Oracle Grid Infrastructure for a Standalone Server owner (most Times this is the user Oracle):
7. $ export ORACLE_HOME=/opt/crs/product/112_ee_64/crs
8. $ $ORACLE_HOME/bin/relink
This will show: oracle@<server>:/opt/oracle [+ASM]# $ORACLE_HOME/bin/relink
writing relink log to: /opt/crs/product/112_ee_64/crs/install/relink.log
9. Login as
root again (or of course if you had a second window open allready switch to the window in which you root session is still in place):
Note. Rootadd_rdbms came back very fast without any output so that was a bit puzzling but i decided to continue.
12. cd /opt/crs/product/112_ee_64/crs/crs/install
13. perl roothas.pl -patch
That did the trick but of course this needed Checking with:
- export $ORACLE_HOME=/opt/crs/product/112_ee_64/crs/
- ./crsctl check has
This showed:CRS-4638: Oracle High Availability Services is online
So at this point and time this Dba was heading towards being happy already but of course one final step to make.
Starting the databases under control in an easy way:
In the paragraph stopping the databases under control in an easy way we have already made preparations for the final step. So at this point and time i just had to give following command:
srvctl start home -o /opt/oracle/product/112_ee_64/db -s /var/tmp/state_file.dmp
After that all working and happy Dba..