Modifying Oracle Grid Infrastructure for a Standalone Server Binaries After Installation
After installation, if you do not patch binaries using OPatch with the opatchauto
flag, then you must stop the stack, modify the software, and and then restart the stack.
You must first stop the Oracle Restart stack to modify the software installed in your Grid home. For example, to apply a one-off patch or modify any of the dynamic link libraries (DLLs) used by Oracle Restart or Oracle ASM, you must stop the stack manually, modify the software, and then restart the stack.
However, if you run the OPatch utility with the auto option, opatchauto
, then OPatch stops and starts the software stack for you. If you run OPatch with the apply option, opatch apply
, then you must also stop and restart the stack manually .
You must relink the Oracle Restart and Oracle ASM binaries every time you apply an operating system patch or after an operating system upgrade.
Caution:
Before relinking executables, you must shut down all executables that run in the Oracle home directory that you are relinking. In addition, shut down applications linked with Oracle shared libraries.Modifying Oracle Grid Infrastructure for a Standalone Server Binaries
-
Log in as the Oracle Grid Infrastructure for a standalone server software owner user and change the directory to the path
Grid_home/bin
, whereGrid_home
is the path to the Oracle Grid Infrastructure for a standalone server home:$ cd Grid_home/bin
-
Shut down the Oracle Restart stack using the following command:
$ crsctl stop has -f
-
Log in as
root
and unlock the grid home:# cd Grid_home/crs/install # roothas.sh -unlock
-
Apply the patches using
opatch apply
. -
Relink the binaries.
$ export ORACLE_HOME=Grid_home $ Grid_home/bin/relink
-
Lock the grid home:
# cd Grid_home/crs/install # roothas.sh -lock
-
Enter the following command to restart the Oracle Restart stack:
$ crsctl start has
Relinking the Oracle Restart and Oracle ASM Binaries