Issue Information
| Incident Number | 701380b |
| Issue | On a parent table where a PK/UNIQUE constraint uses a non-unique index with more columns than the constraint columns through USING INDEX, TBR-10009 (foreign key exists) occurs when only an index column that is not part of the constraint is updated if referencing child rows exist. The UPDATE should succeed because the referenced key was not changed. |
| Cause | The logic for determining whether the referenced key (PK/UNIQUE constraint columns) of the parent table had changed compared the entire index key and incorrectly determined that it had changed. As a result, even when the referenced key value had not changed but another column in the index had changed, the existence of referencing rows in the child table was unnecessarily checked, causing an error. This occurred because a previous prerequisite regarding the constraint columns and index configuration had changed. The criteria were modified to match the referenced key columns to prevent unnecessary checks. |
| Solutions | Fixed the FK check so that it operates correctly even when the column order of the index reused by a PK/UNIQUE constraint differs from that of the constraint or when multiple constraints exist on one index. |
| Occurrence Date | 09/22/26. |
| Required Patch Version | 7FS02PS |
Patch Information
| Patch Name | FS02PS_701380b |
| Major Version | 7 |
| Minor Version | FS02PS |
| Version Title | Fixing FK check errors for PK/UNIQUE constraints with a different constraint and index column configuration using index |
| Available for Deployment | 09/29/26. |
| Compatibility | • TAC rolling patch: Yes • TSC rolling patch: Yes • Backup data compatibility: Yes • Protocol compatibility: Yes • Data format compatibility: Yes |
| AP Impact | • Plan change: No • Result value change: Yes • SQL syntax change: No • System object change: No • Existing functionality change: No |
| Parameters | - |
| Workaround | - |