 |
|
Managing a 9i RAC
Database on 10g Clusterware
Oracle Tips by Burleson Consulting |
The key to managing a 9i database after the 10g
CRS has been installed is to use the 9i version of srvctl, sqlplus,
rman, etc. to start, stop and maintain the 9i instances.
Use the racenv script to ensure the correct
version of a given application is used to manage a given database, and
use the Linux which command to double check that the correct version
is accessed for a given database. Switching from a 9i database to a
10g database is just a matter of using racenv to change the
environmental variables. It is really that simple!
The 10g version of gsd
will provide service to the 9i srvctl just fine. The 9i version of the
gsdctl script was intentionally disabled in Chapter 8 because it
should not be used to manage the 10g gsd service.
Registering the 9i
Service with a 10g Listener
It is extremely easy to register a 9i database
with a 10g listener. Simply start it up with the 9i version of srvctl,
and use the 10g version of lsnrctl status LISTENER_<node_name> to
check the service.
When starting the 9i database, the error message
“PRKP-1040 Failed to get the status
of the listeners associated with instance…” should be ignored! The
database will start normally and will be served by the 10g listener
even though this message may appear.
The tnsnames.ora file in the 9i oracle home will
serve the 9i clients that need to connect to 9i instances. Edit the 9i
tnsnames.ora file so that the host names read “vip-oracle1” and
“vip-oracle2”. There is no need to edit the tnsnames.ora file in the
10g oracle home.
 |
If you want to learn RAC at home, get the bestselling book "Personal
Oracle Real Application Clusters" by Edward Stoever.
You can buy it direct from the publisher for 30%-off and get
instant access to the code depot of Oracle tuning scripts. |
|
