SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Trigger, UDR Server, and Language Manager
Messages (11000 through 11399)
HP NonStop SQL/MX Messages Manual—523730-004
12-10
SQL 11041
Cause. You attempted to create a trigger and one or more of the following conditions
are true:
•
The primary key length of the temporary table (which needs to be created when
the first trigger is created) is longer than the allowed maximum length.
•
The length of the temporary table name is longer than the maximum allowed user
table name length.
Effect. The operation fails.
Recovery. If the primary key length is too long, re-create your subject table with a
primary key that is 12 bytes shorter than the maximum allowed primary key length. If
the table name is too long, re-create your subject table with a name length that is six
characters shorter than the maximum allowed table name length.
SQL 11042
Where name is the name of the trigger you are trying to create.
Cause. You attempted to create a trigger that already exists.
Effect. The operation fails.
Recovery. Specify a different trigger name and resubmit.
SQL 11101
Cause. The SQL/MX UDR server received a request message with an unknown
message type.
Effect. The request message is rejected, and the SQL/MX statement fails.
Recovery. None. Contact your service provider.
SQL 11102
Cause. The SQL/MX UDR server received a request for a stored procedure that is no
longer present in the SQL/MX UDR server context.
11041 Temporary table could not be created! Check default
partitions.
11042 Trigger name already exists.
11101 MXUDR: Unknown message type: value.
11102 MXUDR: Invalid UDR handle: string.