Asynchronous background jobs and administrative functions

IBM OpenPages® supports asynchronous execution of processes in the background.

The most common examples of these types jobs are FastMap web-based data import jobs, object resets, and reporting schema generation.

For example, after a user submits a data import file, that file is queued for loading and the import process occurs in the background. Because it is important for asynchronous background jobs to run to completion, certain administrative operations are suspended until all background jobs complete.

By default, the following administrative functions will not start until background jobs are complete:

  • OPBackup command
  • OPRestore command
  • System Administrative Mode (SAM)
Note: To disable the default setting that checks for background jobs before you start OPBackup or OPRestore, see Enabling and disabling asynchronous background processes checking.
If asynchronous processes are found, error messages are written to the OPBACKUP restore log. The .log file name has the format op_backup_<yyyy_mm_dd_hh_mm_ss>.log. For example:
  • On Windows: C:\OpenPages\openpages-backup-restore\op_backup_2019_07_26_09_35_42.log
  • On Linux®: /opt/OpenPages/openpages-backup-restore/op_backup_2019_07_26_09_35_42.log

Example

The following samples show the error log message that occurred when an OPBackup command was initiated while the reporting schema was still being generated.

IBM® Db2®
  • For IBM Db2 environments, a sample error log message might look similar to this text:

    • can-proceed: [exec] ERROR near line 26: [exec] SQL0438N Application raised error or warning with diagnostic [exec] text: "There are existing processes running. Please let them [exec] finish or termi".

    • can-proceed: [exec] ERROR near line 26: [exec] SQL0438N Application raised error or warning with diagnostic [exec] text: "There are existing object reset operations running.[exec] Please let them finish or termi".

Oracle database
For Oracle environments, a sample error log message might look similar to this text:

  • can-proceed: [exec] declare [exec] * [exec] ERROR at line 1: [exec] ORA-20001: There are existing processes running. [exec] Please let them finish or terminate them before proceeding. [exec] ORA-06512: at line 7 [exec]

  • can-proceed: [exec] declare [exec] * [exec] ERROR at line 1: [exec] ORA-20001: There are existing object reset operations running. [exec] Please let them finish or terminate them before proceeding. [exec] ORA-06512: at line 7 [exec]