B SAS_VIEW Directory Tree

All Oracle Clinical data not stored in the database, such as SAS Views created with the Data Extract facility, is stored in the sas_view directory on the database server computer. The access restrictions enforced in the database must also be enforced at the file-system level.

The structure of the sas_view directory tree is shown below using indentation.

opapps
   sas_view
      db_service
         study
            account_type
            *.sas
            *.log
            *.com

The following table shows the permissions for each folder and file. The owner is not relevant; in fact, the owner is the user who created the file or directory through the use of the application. The top-level directory, opapps, is set by the Installer. Entries are indented to show the relative subdirectory nesting level.

Where db_name is the name of the database instance, study is the study code in Oracle Clinical, and account_type is the data extract view account type (TEST, CURRENT, STABLE or SNAPSHOTn).

For example:

UNIX: 

/pharm/home/opapps/sas_view

Windows: 

\\opa-db1\sas_view

To change the location of location of the SAS_VIEW storage sas_view, change the appropriate environment settings for your platform, as shown below. This may already be set in the setup file for your operating system; see "Database Tier Settings".

UNIX: 

db_env_setting:_DEFAULT_:RXC_USER:/u01/home/opapps

db_env_setting:_DEFAULT_:RXC_SAS_ROOT:root/home/opapps/sas_view/database

where database is the value of $ORACLE_SID for a local database or $TWO_TASK for a remote database.

Windows: 

set RXC_SAS_ROOT=%oui_sas_root%\%database%

To set the protections on your directory structure, run the appropriate script:

UNIX: 

$RXC_TOOLS/set_rxc_user.sh

Windows: 

%RXC_TOOLS%\set_rxc_user.bat

(These scripts are run automatically by the Installer.)

On UNIX Systems Only:

The path to the SAS_VIEW directory must not contain uppercase characters (PSUB changes all path specifications to lowercase for UNIX). If your standard naming conventions require uppercase characters in the path, you can provide lowercase and uppercase versions of paths with symbolic links as needed. For example, if the standard path to the SAS_VIEW directory is

/usr1/home/Clinical/opapps/sas_view

you could create this link:

% cd /usr1/home
% ln -s Clinical clinical 

References to

/usr1/home/clinical/opapps/sas_view

would also work.