"Translated from MoS article" Oracle 11gR2 relink new features

Oracle 11gR2 relink New features

From:
Oracle 11gR2 relink New Feature (document ID 883299.1)

Suitable for:
Oracle database-enterprise edition-version 11.2.0.0 to 11.2.0.0 [Release 11.2]
Generic UNIX

Solution:
I) Oracle 11gr2 There are 2 ways to relink binary $ORACLE _home
1) Traditional method: Relink All
The method runs the $oracle_home/bin/relink script, which only accepts all of the arguments, and the other parameters are not accepted.

     % $ORACLE _home/bin/relink all     % $ORACLE _home/bin/relink (by default it takes the "all" parameter) is the all parameter.

Note: relink all provides backward compatibility (' relink all ' are provided for backward compatibility)
2) use Runinstaller to relink
The method uses the following command:

       -relink:for performing relink actions on the Oracle home         Usage:-relink-maketargetsxml <location of MAKETARGETSX ml> [-makedepsxml <location of Makedepsxml>] [Name=value]

Examples are as follows:
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

II) Location of the Relink log

Case 1
If the relink operation is performed through Oui, the "$ORACLE _home/install/relink.log" file is not generated by default.
In order to send relink output to $ORACLE _home/install/relink.log, we need to explicitly redirect the output

$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
With the relink All command, Oracle establishes a log file named Relink.log, and does not append to create it.
The previous log will be saved with a timestamp (Ex:relinkactions2009-09-14_09-01-10-pm.log)

"Translated from MoS article" Oracle 11gR2 relink new features