SQL0707N The object "<name>" cannot be created because the first three characters are reserved for system objects.
Cause: The following is a list of reserved names:
Action: Select a name that does not start with a reserved prefix.
sqlcode: -707
sqlstate: 42939
SQL0713N The replacement value for "<special-register>" is invalid.
Cause: Either the value specified in the SET <special-register> statement is not a valid value of the indicated special register, or the value specified is NULL as a result of an indicator variable.
The statement cannot be executed.
Action: Correct the replacement value and/or any indicator variables. See the SQL Reference for an explanation of the valid values of each special register.
sqlcode: -713
sqlstate: 42815
SQL0723N An error occurred in a triggered SQL statement in trigger "<trigger-name>". Information returned for the error includes SQLCODE "<sqlcode>", SQLSTATE "<sqlstate>" and message tokens "<token-list>"
Cause: An SQL statement in the trigger "<trigger-name>" has failed during execution of the trigger. The sqlcode, sqlstate and message token list (each token is separated by the vertical bar character) are provided. The message tokens may be truncated. See the corresponding message for the "<sqlcode>" for further explanation of the error.
The trigger and the original SQL statement that caused the trigger to execute cannot be processed.
Action: Check the message associated with the SQLCODE of the SQL statement that failed. Follow the action suggested by that message.
sqlcode: -723
sqlstate: 09000
SQL0724N The activation of trigger "<trigger-name>" would exceed the maximum level of cascading.
Cause: Cascading of triggers occurs when a triggered SQL statement in a trigger would result in another trigger being activated or when a referential constraint delete rule causes additional triggers to be activated. The depth of this cascading is limited to 16.
Note that recursive situations where a trigger includes a triggered SQL statement that directly or indirectly causes the same trigger to be activated is a form of cascading that is very likely to cause this error if there are no conditions to prevent cascading from exceeding the limit.
The "<trigger-name>" specified is one of the triggers that would have been activated at the seventeenth level of cascading.
Action: Start with the triggers that are activated by the UPDATE, INSERT or DELETE statement that received this error. If any of these triggers are recursive, ensure that there is some condition that prevents the trigger from being activated more than the limit allows. If this is not the cause of the problem, follow the chain of triggers that are activated to determine the chain that exceeds the cascading limit.
sqlcode: -724
sqlstate: 54038
SQL0727N An error occurred during implicit system action type "<action-type>". Information returned for the error includes SQLCODE "<sqlcode>", SQLSTATE "<sqlstate>" and message tokens "<token-list>".
Cause: DB2 attempted to implicitly rebind an invalid package or to implicitly prepare a cached Dynamic SQL statement and encountered an error during this attempt. The action attempted is shown by the "<action-type>":
The sqlcode, sqlstate and message token list (each token is separated by the vertical bar character) are provided. The message tokens may be truncated. See the corresponding message for the "<sqlcode>" for further explanation of the error.
The original SQL statement that caused the "<action-type>" cannot be processed and the implicit system action was not successful.
Action: Check the message associated with the SQLCODE of the SQL statement that failed. Follow the action suggested by that message.
For an invalid package, the REBIND command can be used to recreate the error or to explicitly validate the package once the cause of the error has been resolved.
sqlcode: -727
sqlstate: 56098
SQL0750N The source table cannot be renamed because it is referenced in a view, trigger, check constraint or referential constraint.
Cause: The source table in a RENAME statement cannot be renamed for one or more of the following reasons.
The statement cannot be processed.
Action: Drop the views, triggers, check constraints or referential constraints on the table before issuing the RENAME statement. For views dependent on the table, query SYSCAT.VIEWDEP where the table matches BSCHEMA and BNAME columns. For triggers dependent on the table, query SYSCAT.TRIGDEP where the table matches BSCHEMA and BNAME columns. For check constraints on the table, query SYSCAT.CHECKS where the table matches TABSCHEMA and TABBNAME columns. For referential constraints dependent on the table, query SYSCAT.REFERENCES where the table matches TABSCHEMA and TABNAME columns or REFTABSCHEMA and REFTABNAME columns.
sqlcode: -750
sqlstate: 42986
SQL0751N The trigger "<trigger-name>" is defined with an unsupported triggered SQL statement.
Cause: The trigger is defined with a triggered SQL statement that does match the following list.
In some cases the "<trigger-name>" is not available for use in the message.
Action: Check the triggered SQL statements in the trigger for any statement that does not match the above list and remove it.
sqlcode: -751
sqlstate: 42987
SQL0752N Connecting to a database is not permitted within a logical unit of work when the CONNECT type 1 connection setting is in use.
Cause: An attempt was made to connect to either another database or the same database before issuing a COMMIT or ROLLBACK statement. The request cannot be processed within a CONNECT type 1 environment.
Action:
sqlcode: -752
sqlstate: 0A001