Enable Local Locking in Oracle Argus Safety

Before enabling Local Locking in Oracle Argus Safety, you must make sure that you have upgraded your database to this release successfully.

1. Execute the batch file Enable_local_lock.bat from Argus Release Media\Database\Argus Safety\Utilities\Enable_local_lock directory.
2. Enter the response for Do you wish to turn on the Local Locking feature for one or more enterprises (Yes/No)?, enter Yes to continue.
3. Enter the log file name to record the results.

   This is the execution log that is created on the client workstation under the Enable_local_lock directory mentioned above.

4. Enter TNSNAMES Entry to Connect to the source SAFETY Database.
5. Enter SAFETY schema owner name in source Database.
6. Enter the password for safety schema name in source Database.
7. Enter comma separated list of enterprises where local locking feature is to be enabled or enter ALL for all enterprises in Source safety Database.

   If no value is entered script will run for enterprise 1 by default.

8. Enter the Agency name for PMDA reporting destination as configured in Reporting Destination codelist.
9. To enable local locking privileges for the Oracle Argus Safety Japan users, enter Yes.

   Follow the prompts for confirmation.

   Note:

   If the agency entered is invalid for any of the enterprises, the utility will abort and no changes will be committed.

   In case of a multi-tenant environment, if this utility is re-run for any of the enterprises, it will display a list of the enterprises for which it has already executed and will continue to process rest of the enterprises.