Ansicht
Dokumentation

CPD32BB - Constraint is not valid. ( OS/400 )

ROGBILLS - Synchronize billing plans   Vendor Master (General Section)  
This documentation is copyright by IBM.


Message : CPD32BB
Constraint is not valid.

Message Long Text :

Cause . . . . . : Constraint &12 cannot be added for file &1 in library &2 for TYPE value &4. For a referential constraint (TYPE *REFCST), the parent file &5 in library &6 has a delete rule of &10 and update rule of &11. The constraint was not added because of errors. The reason code is &7. The reason codes and their meanings are as follows:
01 - The file has the maximum number of constraints allowed.
02 - The specified constraint name already exists in the library.
03 - For a delete rule of *SETNULL, the foreign key of the dependent
file must have at least one field in the key that is NULL
capable.
04 - There are problems with the system cross reference files. A
wait timeout occurred.
05 - The file has records that contain duplicate key values.
06 - A delete cascade rule cannot be added to a file with a delete
trigger event. A delete set null or set default rule cannot
be added to a file with an update trigger event.
07 - The parent file access path fields do not match the fields
for the referential constraint, or if the file is partitioned,
the access path of the parent file must be non-partitioned.
08 - Mismatch between the KEYs of the parent file and dependent file
when processing a secondary referential constraint for a unique
or primary key constraint.
09 - The parent file has the maximum number of constraints allowed.
10 - A delete cascade rule can not be added to a file with a
datalink field.
Recovery . . . : Do one of the following based on the reason code shown, and then try the request again.
01 - Remove a constraint (RMVPFCST) and retry the function.
02 - Retry the function with a different constraint name.
03 - SPECIFY A FOREIGN KEY WITH AT LEAST ONE FIELD NULL CAPABLE
(ALWNULL KEYWORD).
04 - Try the operation again. If the operation fails again with this
message and reason code, run reclaim storage (RCLSTG) to update
the system cross reference files.
05 - See previously listed CPF3240 message(s).
06 - Remove the trigger (RMVPFTRG) so the constraint can be added.
07 - Add a primary key or unique constraint to the parent file
that matches the referential constraint, or if the parent file
is partitioned, add a non-partitioned access path.
08 - Remove the constraint (RMVPFCST) and add the constraint back
(ADDPFCST) with a KEY that matches the secondary referential
constraint.
09 - Remove a constraint (RMVPFCST) and retry the function.
10 - Do not use the delete cascade rule.
Technical description . . . . . . . . : &3

Message File : QCPFMSG
Library Message File : QSYS2924


ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by IBM.

Length: 3282 Date: 20240424 Time: 145851     sap01-206 ( 3 ms )