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-2
Recovery. The threshold of 16 is hard-coded and cannot be changed. You can either
rewrite your statement or redesign your triggers for less trigger recursion by adding
conditions to your trigger actions.
SQL 11004
Cause. You attempted to create a trigger on a subject table whose name length
exceeds 122 characters. The maximum length of a user table is 128 characters.
However, triggers require an internal temporary table whose name is derived from the
subject table name, which is an additional six characters.
Effect. The operation fails.
Recovery. The trigger can only be created if you drop and re-create the subject table
with a name that is less than 123 characters.
SQL 11006
Cause. Rowsets were used in a statement that is a trigger event.
Effect. The operation fails
Recovery. Either remove the rowset from the statement or drop all triggers defined on
the table and operation that caused the error. For example, if the operation is a delete,
you need to drop all delete triggers defined on the DELETE statement target table. If
the triggers cannot be dropped, avoid the use of rowsets.
SQL 11010
Cause. You attempted to specify a statement granularity for a BEFORE trigger, which
is not supported.
Effect. The operation fails.
Recovery. Either specify a row granularity or do not specify a granularity. Row
granularity is the default for BEFORE triggers.
11004 Triggers cannot be created on tables with names longer
than 122 characters.
11006 Use of rowsets with statements involving triggers is
not supported.
Note. As of the ABU SPR, this message is no longer generated.
11010 A BEFORE trigger works only at row granularity.