1. relink script description in 11gr2
The two blogs of oracleoption and its link are described as follows:
Oraclebinary options description
Http://blog.csdn.net/tianlesoftware/article/details/7577637
Description of relink binary options for a single oracle instance
Http://blog.csdn.net/tianlesoftware/article/details/7577652
From 11gr2 (11.2.0.1, 11.2.0.2 etc ...) the relink script no longer scans *. MK files andno longer runs the make commands (that is, what it used to do in 11.1 and lowerversions ).
Oracle has modified the relink script since Oracle 11gr2. Starting from oracle11.2.x, The relink script does not scan *. mk or execute the make command. All relink operations are performed using the runinstaller method. For new relink features in 11gr2, refer to the mos documentation.
Oracle11gr2 relink new feature [ID 883299.1]
A compatibilityscript was put in place for 11gr2 so if someone runs "relink all" itwill actually use the runinstaller method of relinking.
-- For script compatibility, even if relink all is executed in 11gr2, runinstaller is actually used for relink.
One exception in11.2.0.1: Sun iSCSI Solaris which for scan of *. mk and make are still in use.
-- Here, the exception is 11.2.0.1 in Sun iSCSI, which still scans *. mk and executes the make command.
2. Use the relink script in 11gr2
Oracle11gr2 can be used to relink all product binaries.
2.1 Traditional relink
Run the $ ORACLE_HOME/bin/relink script directly. You can add or omit the All parameter because the All parameter is used by default. For example:
% $ ORACLE_HOME/bin/relink all
% $ ORACLE_HOME/bin/relink (by default it takes the 'all' parameter)
Note:
This method only applies to forward compatibility because it is used in earlier versions than 11.2.x.
2.2 run relink with runinstaller
This is a new feature in 11.2.x. The command is as follows:
-Relink: for faster Ming relink actions on the Oracle Home
Usage:-relink-maketargetsxml <location of maketargetsxml> [-makedepsxml <location of makedepsxml>] [name = value]
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
3. View relink log
3.1 Case 1:
If you directly use Oui to execute relink, the log file $ ORACLE_HOME/install/relink. log will not be generated by default. In this case, we need to display the specified output log. The command is as follows:
$ 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
3.2 Case 2:
If we use the relink all command, a relink is generated by default. log File, if relink exists. log File, will not continue to append to the existing log file, but uses timestamp to rename the existing file, such as: relinkActions2009-09-14_09-01-10-PM.log, and then write relink. log.
Bytes -------------------------------------------------------------------------------------------------------
All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!
Skype: tianlesoftware
QQ: tianlesoftware@gmail.com
Email: tianlesoftware@gmail.com
Blog: http://www.tianlesoftware.com
WEAVER: http://weibo.com/tianlesoftware
Twitter: http://twitter.com/tianlesoftware
Facebook: http://www.facebook.com/tianlesoftware
LinkedIn: http://cn.linkedin.com/in/tianlesoftware
------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----
Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)
Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823
Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940