SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

Trigger, UDR Server, and Language Manager
Messages (11000 through 11399)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
13-8
SQL 11029
Where column-name is the name of the column.
Cause. You attempted to change a column of a particular row from a particular table to
two different values at two different instances. You have designed a set of triggers that
can result in nondeterministic behavior.
Effect. The operation fails.
Recovery. None. Redesign the triggers in such a way that this condition is not raised.
This usually involves following the cascading of triggers and identifying when the
column is being modified more than once. From error 11028, which was raised along
with this error, you can identify the trigger that made the second change to the same
column of a given row.
SQL 11030
Cause. You attempted to drop or alter a trigger that does not exist.
Effect. The operation fails.
Recovery. None, if the name of the trigger was entered correctly. Otherwise, correct
the trigger name and resubmit.
SQL 11033
Where name1 is the object name you are attempting to drop.
Where name2 is the trigger name.
Cause. You attempted to drop an object name that is being used by a trigger.
Effect. The operation fails.
Recovery. If possible, drop the trigger first, and then drop the object. You can use the
cascade option to drop the object, but you risk dropping all objects that use that object,
including the triggers.
11029 Attempt to change the value of column column-name of a
given row more than once in the same statement.
Note. As of the ABU SPR, this message is no longer generated.
11030 Trigger does not exist.
11033 Object name1 cannot be dropped because it is being used
by trigger name2.