New Features for Oracle 11gR2 Relinking

This is a small note for the new features introduced in Oracle 11g related to Relinking.

Methods of Relinking

Oracle 11gR2 has two methods of relinking all product binaries in a home:

1. Traditional relink with ‘all’ option only

The first method is the normal running the $ORACLE_HOME/bin/relink script, which now only accepts the ‘all’ parameter (no other parameters are accepted).

% $ORACLE_HOME/bin/relink all
% $ORACLE_HOME/bin/relink (By default it takes the 'all' parameter)

Note: ‘Relink all’ is provided for backward compatibility.

2. relink using runInstaller

This runs the command:

-relink : For performing relink actions on the oracle home.

Usage: -relink -maketargetsxml [location of maketargetsxml] [-makedepsxml [location of makedepsxml]] [name=value]

For example:

$ORACLE_HOME/oui/bin/runInstaller -relink -waitForCompletion -maketargetsxml  $ORACLE_HOME/inventory/make/makeorder.xml -logLocation $ORACLE_HOME/install ORACLE_HOME=$ORACLE_HOME > $ORACLE_HOME/install/relink.log 2>&1

Relink log location

Case 1

If relink is performed using OUI then “$ORACLE_HOME/install/relink.log” is not created by default. To send the relink output to $ORACLE_HOME/install/relink.log we need to redirect the output explicitly.

$ORACLE_HOME/oui/bin/runInstaller -relink -waitForCompletion -maketargetsxml $ORACLE_HOME/inventory/make/makeorder.xml -logDir $ORACLE_HOME/install ORACLE_HOME=$ORACLE_HOME > $ORACLE_HOME/install/relink.log 2>&1

Case 2

In case of “relink all’ command, it always creates a new log file with a name “relink.log” and it will not append log information to the existing relink log file . The previous log will be saved with a timestamp (Ex: relinkActions2009-09-14_09-01-10-PM.log)