solidDB Help : solidDB reference : SQL: Database system tables and system views : System tables : SYS_BACKGROUNDJOB_INFO
  
SYS_BACKGROUNDJOB_INFO
If the body of a START AFTER COMMIT statement cannot be started, the reason is logged in the system table SYS_BACKGROUNDJOB_INFO. Only failed START AFTER COMMIT statements are logged in this table. If the statement (for example, a procedure call) starts successfully, no information is stored in this system table. Statements that start successfully but do not finish executing are not stored in this system table either.
The user can retrieve information from the table SYS_BACKGROUNDJOB_INFO by using either an SQL SELECT statement or by calling a system procedure SYS_GETBACKGROUNDJOB_INFO, see SYS_GETBACKGROUNDJOB_INFO.
Also a system-defined event SYS_EVENT_SACFAILED is posted when a START AFTER COMMIT statement fails to start, see Miscellaneous events. The application can wait for this event and use the jobid to retrieve the error message from the system table SYS_BACKGROUNDJOB_INFO.
The system table SYS_BACKGROUNDJOB_INFO can be emptied with the following command:
ADMIN COMMAND 'cleanbgjobinfo';
Only a DBA can execute the 'cleanbgjobinfo' command.
The columns in the SYS_BACKGROUNDJOB_INFO system table are described in the following table:
 
Column name
Data type
Description
ID
INTEGER
Job identifier.
STMT
WVARCHAR
The statement that could not be executed.
USER_ID
INTEGER
User or role identifier.
ERROR_CODE
INTEGER
The error that occurred when statement was executed.
ERROR_TEXT
WVARCHAR
A description of the error.
Go up to
System tables