Relinking Server Code — UNIX Only
With UNIX servers, you need to relink Oracle Clinical code files after either of the following events:
-
a patch or upgrade to your operating system
-
a patch to your Oracle RDBMS
Use the opapps
userid to link all the server code from the supplied object files and set the file protections.
-
Enter the following commands:
% ksh $ $RXC_TOOLS/relink_rxc.sh > $RXC_ROOT/relink_rxc.log 2>&1 $ exit
-
Check for errors in the log file,
relink_rxc.log
, using the following command:% grep -i error $RXC_ROOT/relink_rxc.log
Or, to find out whether a relink has been successful by using a utility, enter:
% ksh $RXC_TOOLS/rxcchkobj.sh progs relink.mk
If all executables are created successfully, the output shows a set of empty directory paths. Any executable that is not created is listed in the rxcchkobj output. For example:
Expected progs in =====> /u01/home/oppaps/bin/52/build/tools gen_views: No such file or directory cnvstatus: No such file or directory
This indicates that two executables, gen_views and cnvstatus, were expected but not created.You should investigate the cause of the listed executables not being created.
Parent topic: Routine Server Administration