User Other than Schema Owner

To enable a user who is not the schema owner to run UCS with an Oracle database:

1. Open the script ucs_oracle_create_additional_user.sql, which is located in the sql_scripts directory of UCS's starting directory.
   
2. Locate the following lines:
   

   ucs_user := 'UCS_RUNTIME'; 
   ucs_db_creator := 'UCS_OWNER';

3. Replace UCS_RUNTIME with the name of the non-owner that you want to be able to run the database.
   
4. Replace UCS_OWNER with the name of the Oracle user that created (is the owner of) the schema.
   
5. Run the script from an Oracle account that has SYSDBA privileges. This creates the user identified in Step 2 and creates synonyms of all objects so that they are accessible to the newly created user.
   
6. Adjust the DAP that UCS uses (or create a new DAP if you want to retain the existing one), as follows:
   

• On the DB Info tab, set the User Name equal to the user identified in Step 2, and set the password equal to the user name. This is how the script creates the user and password. If you want a different password you must modify it in Oracle.
  
• On the Options tab, settings section, create the db-schema-name option. For its value, enter an upper-case version of the name of the Oracle user that created the UCS database schema (the user identified in Step 3).
  
• Also in the settings section, add an option called includeSynonyms and set it to true.

After completing these steps on the main database, repeat them for the archive database.

Important

When using UCS with a limited DB user, UCS is not able to check for the existence of table indexes. The log will display a message warning that indexes do not exist, but you can ignore this warning. Using a limited user does not prevent DB from using indexes.