Running the Add User Script

Create a database account for the user in each database instance to which the user connects by running the script ocl_add_user.sql in SQL*Plus.

The Add User script prompts you for directories that users may need. You can set these directories up before or after you enter their names in the script. See Setting Up Batch Job File Viewing.

Who Needs PSUB?

The script prompts you to for a response as to whether the user needs PSUB privileges. PSUB is required to:

Run batch data load
Run batch data delete
Run batch validation
Generate a default, character-based DCM layout
Run the following reports: Randomization Report by Treatment, Patient DCI/DCM Matrix, Generate Study Report, Missing and Overdue DCMs, Investigator Corrs & Missing Pgs, Study/Investigator DCM Summary Matrix, Display Treatment Assignments

PSUB is not required to:

Perform basic data entry in either Oracle Clinical or RDC
Generate graphic layouts and DCI forms
Run most reports, including the Patient Data and Audit History reports

For more information, see:

Parent topic: Setting Up User Accounts

Granting Users Access to the ocpsub Account

Users who need to submit PSUB jobs must have the ocpsub account as a proxy database account for PSUB jobs. To give this access, enter the appropriate information in the ocl_add_user.sql script; see Running the Add User Script.

If you have user accounts you created in Oracle Clinical releases prior to 5.0, you can migrate them to the new PSUB setup by running the migration script oclupg50migrateusers.sql. PSUB users no longer need their own operating system account, and they no longer need an account name beginning with OPS$; see Running the Migrate Users Script.

You can use ocl_grant_revoke_OCPSUB.sql to add or revoke access to ocpsub at any time; see Adding or Revoking OCPSUB Access.

Users with access to ocpsub have the PSUB User? field checked in the Oracle Accounts window. The field is read-only.

Parent topic: Running the Add User Script

About the Add User Script

The ocl_add_user.sql script performs the following tasks:

Creates an Oracle database account for the user, with the specified password

Note:

If you use SQL*Plus to create a Oracle Clinical database account, do not use the IDENTIFIED EXTERNALLY clause; rather, assign an explicit password.
Sets the user's temporary tablespace to "temp" and default tablespace to "users"
Grants default Oracle Clinical database roles to the user; you can edit the script to assign additional database roles
Grants the RXC_SUPER role for data access to all studies, if specified
Grants RXC_RDC and RDC_ACCESS if access to RDC is required
Makes the RXCLIN_MOD role a non-default role
Creates a record in the Oracle Clinical table ORACLE_ACCOUNTS
Creates the setting you specify for PSUB privileges

Note:

You can copy and customize this script, or create different versions of it for different types of users.

For the example, you can change temporary and default tablespaces, provide default values for some parameters instead of entering a value for each user at a prompt.

You can add a call to crusrq.sql to create the USER_QUERIES table (see Setting Up Data Extract Users). You may want to add a role or profile to enforce password requirements; see Setting Password Requirements for User Accounts.

However, if you decide to customize the script, it is important not to modify the line: alter user &&ops_id default role all except rxclin_mod;

Note:

You can give users additional database roles directly in SQL*Plus; see Granting Additional Database Roles to User Accounts.

Parent topic: Running the Add User Script