HP NonStop SQL/MX Messages Manual page 254

Table of Contents

Advertisement

Executor Messages (8000 through 8999)
table will then have a valid row count although the row count for the source table will
remain invalid.
SQL 8100
8100 Define name does not exist.
Cause. You attempted to reference a define that does not exist.
Effect. The operation fails.
Recovery. Define the item, or use the correct define name.
SQL 8101
8101 The operation is prevented by check constraint name1 on
table name2.
Where constraint name1 is the name of the constraint.
Where table name2 is the name of the table.
Cause. You attempted to perform an operation on table name1 that is prevented by
check constraint name2.
Effect. The operation fails.
Recovery. Change the data you are attempting to enter to be consistent with the
constraint.
SQL 8102
8102 The operation is prevented by a unique constraint.
Cause. You attempted to perform an operation that is prevented by a unique
constraint.
Effect. NonStop SQL/MX could not perform the operation.
Recovery. Make the data you enter unique to be consistent with the constraint.
SQL 8103
8103 The operation is prevented by referential integrity
constraint name1 on table name2.
Where name1 is the name of the constraint.
Where name2 is the name of the table.
HP NonStop SQL/MX Messages Manual—640324-001
10- 6

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents