D Routine Server Administration

This appendix covers system administration tasks that arise from changes to the system hardware or software.

• Recreating Symbolic Links — UNIX Only

• Relinking Server Code — UNIX Only

• Relocating Oracle Clinical

• Updating Oracle Clinical Seed Data

• Collecting Statistics for Optimization

Recreating Symbolic Links — UNIX Only

The symbolic links to the Oracle Clinical executables are lost when you, for example, copy the installation directory to a new drive (see also "Relocating Oracle Clinical"). To recreate the symbolic links, use the relink_rxc.sh script as follows:

% ksh
$ $RXC_TOOLS/relink_rxc.sh symbolic_links > $RXC_ROOT/relink_rxc.log 2>&1
exit%

The parameter link tells the script to re-establish symbolic links to the current Oracle Clinical executables, not to be confused with relinking the server code (see the next section).

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.

1. Enter the following commands:

   % ksh 
   $ $RXC_TOOLS/relink_rxc.sh > $RXC_ROOT/relink_rxc.log 2>&1
   $ exit
   

2. 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/46/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.

Relocating Oracle Clinical

Should you decide to move the Oracle Clinical installation, you will have to edit the location references in one or more files, according to your server platform.

UNIX

In the file oc/46/psub/launchps.sh, modify the directory reference in this section:

p1=$1; export p1;
p2=$2; export p2;
. /pharm/home/opapps/oc/46/bin/opa_setup
USERNAME=$5; export USERNAME;

In the file bin/opa_setup, modify the directory reference in this section:

if [ ${OPA_BIN:-0} = 0 ]
then
  OPA_BIN=/pharm/home/opapps/oc/46/inst/bin
fi

Windows

Edit the file oc/46/psub/launchps.bat.

Updating Oracle Clinical Seed Data

If you run the Installer to create or upgrade an Oracle Clinical database, the Installer places the correct seed data in that database. If, however, you upgrade an existing Oracle Clinical database manually, you must also upgrade the seed data manually.

To upgrade Oracle Clinical seed data manually:

1. Set the environment variables as follows (for details, see Appendix A):

   opa_setup database code_environment
   

   Variable	Description
   ORACLE_SID	set to the name of the database
   ORACLE_HOME	set to your desired Oracle home directory
   PATH	make sure oracle_home/bin is in your PATH variable

   
   

2. Collect the passwords for OPA and RXC.

3. From the install directory,  run the script loadseed.sql:

   SQLPLUS RXC/password@database
   loadseed.sql 
   

4. Enter responses for the loadseed.sql prompts:

   Enter the password for OPA: opa_password
   Enter the password for RXC: rxc_password
   Enter product code (OC or TMS): OC
   

Collecting Statistics for Optimization

Oracle Clinical provides SQL scripts that you can use to collect computed statistics on the data distribution and storage characteristics of certain tables, indexes, and partitions. These statistics are used by the Cost-based optimizer.

Note:

See the Oracle Database Performance Tuning Guide for information on optimization.

Table D-1 lists the schema for which each script gathers statistics. If you want computed statistics for customer-created tables, such as Thesaurus Management System tables, you must collect them yourself. The Oracle Clinical scripts are located in the RXC_INSTALL directory.

Table D-1 Scripts for Optimization Statistics

Schema	Collection script
RXA_DES	anadestab.sql
RXA_LR	analrtab.sql
RXC	anarxctab.sql
OPA	anaopatab.sql

You must gather statistics on a regular basis to provide the optimizer with information about schema objects. How often you run these scripts depends on how quickly the data volumes in your Oracle Clinical tables increase.

During the initial use of Oracle Clinical you should run these scripts frequently since the data distribution changes rapidly. Once the database is populated, you should run statistics whenever the data volume changes by more than 20% or when some event, such as using a new feature, causes the data distribution to change measurably.

Table D-2, "Suggested Frequency for Analysis Scripts" gives a rough estimate on the frequency of running the analysis scripts.

Table D-2 Suggested Frequency for Analysis Scripts

Number of Studies	Frequency
Less than 10	For each new study
10 to 20	For every other study
20 to 100	For every 5 studies
More than 100	For every 20 studies