Neoview Messages Manual (R2.3)

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 The HP Neoview database software 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.
name1
is the name of the constraint.
name2
is the name of the table.
Cause You attempted to perform an operation on table name1 that is prevented by referential
integrity constraint name2.
Effect The operation fails.
Recovery Change the data you are attempting to enter to be consistent with the constraint.
The data must exist in another table. For example, if you are trying to enter a department
number for an employee, the department number must exist in a department number table.
SQL 8104
8104 The operation is prevented by the check on view name1 cascaded
from the check option on name2.
name1
is the name of the view.
name2
is the name of the table.
Cause You attempted to perform an operation on table name1. The operation has been
prevented by the check on view name2, cascaded from the check option on the table.
Effect The operation fails.
Recovery Change the view properties, if appropriate.
SQL 8105
8105 The operation is prevented by the check option on view name.
name
is the name of the view.
Cause You attempted to perform an operation on table name that is prevented by the check
option on view name.
Effect The operation fails.
Recovery Insert into the base table rather than this view.
SQL 8106
8106 The last row fetched by this cursor was updated or deleted between
the FETCH and UPDATE/DELETE...WHERE CURRENT... of statements.
Cause The last row fetched by the cursor was updated or deleted between the FETCH and
UPDATE/DELETE...WHERE CURRENT statements and is no longer available.
Effect The UPDATE/DELETE WHERE CURRENT statement is invalid.
172 Executor Messages (8000 Through 8999)