Oracle Clinical Setup Files

The Oracle Clinical server environment definition and setup system, known as opa_setup, consists of a set of scripts (on UNIX systems) or command files (on Windows systems).

The four types of setup files are:

• Definition – Edit this file, if necessary, to set or change values on a system-wide or database-specific level. The Oracle Universal Installer creates the file in drive:\opapps\bin.

  • opa_settings – UNIX

  • opa_settings.bat – Windows

• Initialization (login) – This file is optional, edit it to set or change values for an individual user.

  • .profile – UNIX platforms, Bourne/Korn shells

  • .cshrc – UNIX platforms, C shell

  • .login – UNIX platforms, C shell

  • login.bat – Windows

• Selection – Run this file to choose a configuration from among those defined in the settings file.

  • opa_setup – UNIX platforms, Bourne/Korn shells

  • copa_setup – UNIX platforms, C shell

  • opa_setup.bat – Windows

• Supplemental – For compatibility with previous versions of Oracle Clinical; belongs in the user's home directory on the PSUB server machine.

  • .oclrc – UNIX platforms

  • oclrc.bat – Windows

You can edit and maintain the Definition scripts for your installations. However, do not modify the Selection scripts, which call the definition script. The selection script is used in the following contexts:

• When you start or stop the PSUB process for a database, you log in to the operating system as opapps. The selection script is called to set the environment to that database.

• Each time a PSUB job is requested, PSUB executes the setup script to condition its environment to the correct version of the Oracle Clinical code, running against the correct database.

• You may execute the selection script at the command line to define server environments for various purposes, such as connecting to a particular database or running SQL scripts under RXC_TOOLS.

Administrators are not required to create or modify users' installation scripts to enable users to submit back end jobs through the client interface. However, you must add entries to the initialization scripts of users who need to run opa_setup, SAS, or SQL*Plus from the back end command line. See Setting Up Power Users for details.