-723   AN ERROR OCCURRED IN A TRIGGERED SQL STATEMENT IN trigger-name. INFORMATION RETURNED: SQLCODE: sql-code, SQLSTATE: sql-state, MESSAGE TOKENS token-list, SECTION NUMBER section-number

Explanation

During execution of an UPDATE, MERGE, INSERT, or DELETE statement, a trigger was activated. One of the triggered SQL statements received an SQL error condition.

trigger-name
The trigger that was activated when the error occurred.
section-number
The section number that is associated with the failing triggered SQL statement. For triggers that contain a WHEN clause, the WHEN clause is section number one. The triggered SQL statements are numbered sequentially, beginning with section number two. This is true for triggers with or without a WHEN clause.
sql-code
A numeric value that indicates why the SQL statement execution was unsuccessful. This code is received by the activated trigger.
sql-state
The corresponding SQLSTATE for the SQLCODE.
token-list
The list of tokens from the original SQL error. This list might be truncated.

System action

The trigger and the original statement cannot be processed. The triggering table is unchanged.

System programmer response

Identify the failing SQL statement by using one of the following methods:

  • Use the trigger name and section number.
  • If the trigger definition is available, use the section number.
  • Use the following SELECT statement to retrieve the statement from the SYSIBM.SYSPACKSTMT catalog table:
    SELECT STMT, SEQNO FROM SYSIBM.SYSPACKSTMT 
   WHERE COLLID = 'schema-name' AND
   NAME = 'trigger-name' AND
   SECTNOI = section-number 
   ORDER BY SEQNO

    For triggers that were created in DB2® Version 8 new-function mode or later, the STMT result will be in Unicode. To view a Unicode result as EBCDIC, issue the DISPLAY UTF8 command in the ISPF browse program within SPUFI.

Refer to the explanation of the SQLCODE that is indicated by sql-code in this code and take the appropriate action or actions.

Programmer response

Contact your database administrator to determine why the trigger named in the message received the error.

SQLSTATE

09000