Set Up SAS Data Extract

Users need access to the opapps account to run Oracle Clinical SAS Data Extract jobs.

For more information, see:

• Give Users Access to the opapps Account
  
• Add the opapps Account to the oclsascr User Group
  
• Give opapps Access to the Directory Specified in the RXC_SAS_VIEW Environment Variable
  
• Set Up SAS User Authentication and Set OCL_STATE Reference Codelist Values
  
• Changes in SAS Data Extract Implementation
  

Give Users Access to the opapps Account

The same setup is required for SAS users in Oracle Clinical as for PSUB users; see Enable Users to Submit PSUB Jobs.

Add the opapps Account to the oclsascr User Group

1. Add the opapps user to the oclsascr user group. It is the only user required to be in this group.
   See the Oracle Clinical Administrator's Guide for more information.

Give opapps Access to the Directory Specified in the RXC_SAS_VIEW Environment Variable

See the Oracle Clinical Administrator's Guide for more information.

Set Up SAS User Authentication and Set OCL_STATE Reference Codelist Values

1. Choose one of the following user authentication methods:
   • Oracle Wallet
   • SAS password encryption with a proxy user
2. Indicate your choice in the OCL_STATE local reference codelist along with other SAS-related settings. By default the value is set to Oracle Wallet.

See the Oracle Clinical Administrator's Guide for more information.

Changes in SAS Data Extract Implementation

If you are upgrading Oracle Clinical from any release prior to 5.0, SAS files generated in earlier releases of Oracle Clinical cannot be re-used in Release 5.0 or later because they contain a database connection string that is no longer usable.

You must re-run Data Extract job or gen_views utility to create new *.sas files. For more information and other options, see Data Extract batch jobs fail in INCREMENTAL mode (after upgrading from OC 4.6.x to 5.x.x) (Doc ID 2029953.1) on My Oracle Support (Doc ID 2029953.1).