Database Reference
In-Depth Information
ora.crsd
1 ONLINE ONLINE rac1
ora.cssd
1 ONLINE ONLINE rac1
ora.cssdmonitor
1 ONLINE ONLINE rac1
ora.ctssd
1 ONLINE ONLINE rac1 ACTIVE:0
ora.diskmon
1 OFFLINE OFFLINE
ora.drivers.acfs
1 ONLINE ONLINE rac1
ora.evmd
1 ONLINE ONLINE rac1
ora.gipcd
1 ONLINE ONLINE rac1
ora.gpnpd
1 ONLINE ONLINE rac1
ora.mdnsd
1 ONLINE ONLINE rac1
ora.storage
1 ONLINE ONLINE rac1
4.
Modify all existing scripts to reflect the new Oracle 12c GI home settings; for example,
in the
.bash_profile
, other manual scripts that you may maintain at your premises.
5.
Perform the filesystem backup of the new GI home.
6.
Perform the manual physical backup of the OCR.
7.
Optionally deconfigure and clean the previous Cluster.
Clusterware Downgrade
Whenever you prepare to introduce a new change to the existing environment, it is always a recommended and safe
approach to have a complete backout plan to recover from any disasters that may occur after the change. If you work
for a reputable organization, the management naturally expects a back-out plan to accompany all changes to the
current environment. The back-out plan is a procedure to roll back the changes that were applied if the change didn't
go well, or the change creates new problems.
The objective of this section is to summarize all the necessary steps that are required to downgrade from a
successfully upgraded or from a failed Clusterware/ASM to earlier versions.
Oracle's out-of-place upgrade option makes the downgrade procedure faster by keeping the old and new versions
of Oracle Clusterware software in different homes/locations. This makes the downgrade procedure a very light and
quick process, in contrast with pre-11gR2 versions.
Initiating Downgrade Procedure
In order to kick-start the downgrade procedure, perform the following steps:
From the new 12c Grid Home, run the following command on all nodes of the cluster sequentially, preferably
starting from the first node to the last node:
$GRID_HOME/crs/install/rootcrs.pl -downgrade
