Reason:
This error occurs when an attempt to rebind fails. The following identifies the information displayed in the message text in place of A, B, C, D, E, and F.
|
A thru F |
Description |
|---|---|
|
A |
The SQL code that precipitated this failure. |
|
B |
The name of the constraint being rebound. |
|
C |
The name of the table on which the constraint was defined. |
|
D |
1 if this rebind was triggered by the rebind of another constraint, otherwise 0. |
|
E |
Bits indicating the state of the rebind in process. This is for support personnel. |
|
F |
The authorization ID of the table in C. |
Note: This error message may be truncated if the names printed are too long. If this happens (and the information lost is actually needed), a complete error summary can be found in the PXX.
The SQLSTATE that equates to this SQL return code is 55S04.
Action:
If D is 1, (if this rebind was triggered by the rebind of another constraint), then users can scan for the string "REBIND FAILURE" in the PXX to determine which constraints had rebind failures caused by this failure. Each (subsequent) instance of a failure starts with "SEE PREVIOUS -37 ERROR RPT. FOR RECURSIVE CNS. REBIND FAILURE." The following lines give various information. Look for CNSREBIND FAILURE: CNS=x,TBL=y, AUTH=z, where x is the constraint name, y is the table that the constraint is defined on, and z is the authorization ID of the table.
Make appropriate corrections and resubmit.
|
Copyright © 2014 CA.
All rights reserved.
|
|