SQL3608N is returned when running SET INTEGRITY with IMMEDIATE CHECKED in DB2 for LUW
Troubleshooting
Problem
When running the SET INTEGRITY FOR
IMMEDIATE CHECKED statement, error SQL3608N is returned.
Symptom
Steps to reproduce:
1. Run SET INTEGRITY FOR table1 IMMEDIATE CHECKED
SQL3608N Cannot check a dependent table table1 using the SET INTEGRITY statement while the parent table or underlying table "table2" is in the Set Integrity Pending state or if it will be put into the Set Integrity Pending state by the SET INTEGRITY statement.
2. Run SET INTEGRITY FOR table2 IMMEDIATE CHECKED
SQL3608N Cannot check a dependent table table2 using the SET INTEGRITY statement while the parent table or underlying table "table1" is in the Set Integrity Pending state or if it will be put into the Set Integrity Pending state by the SET INTEGRITY statement.
[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Routines (SP \u0026 UDF) - SQL","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;10.1;10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.