Preventing concurrency conflicts for installations that use Oracle databases

Applies to: On premises

If two administrators both try to modify settings at the same time, errors might occur. To help avoid concurrency errors, run the SQL enable-session-sleep.sql script.

A concurrency conflict might result in the following error message: 
Operation failed, security settings are being concurrently modified by another administrator. 
Please try again later.

Procedure

  1. On a computer that has SQL*Plus and access to the database server, log on as a user with SYSDBA permissions.
  2. Go to the /OP_<version>_Main/OP_<version>_Configuration/Database/ORACLE/INSTALL_SCRIPTS directory.
  3. Copy the enable-session-sleep.sql script to the local computer.
  4. Run the enable-session-sleep.sql script. 
    sqlplus /nolog @sql-wrapper enable-session-sleep.sql <log_file_name>
     <connect_identifier> <sysdba_user_name> <sysdba_user_password> <schema_owner_name>
    If the password contains special characters, surround the password in quotation marks:
    • Windows: "password"
    • Linux®: 'password'
    Example:
    • Windows:
      sqlplus /nolog @sql-wrapper enable-session-sleep.sql enable-session-sleep.log opx10g sys "pass~word" openpages
    • Linux:
      sqlplus /nolog @sql-wrapper enable-session-sleep.sql /tmp/log OP sys 'pass~word' openpage

    If the process completes successfully, a message is displayed.

    If the script fails, check the log files for error messages.