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-22
SQL 11222
Cause. The Java Virtual Machine, hosted by an SQL/MX UDR server, did not have
enough memory to execute a Java method. This error condition will be accompanied
by another condition that shows when the Java Virtual Machine encountered the error.
Effect. The operation fails.
Recovery. Stop and restart the session and retry the SQL/MX statement.
SQL 11223
Cause. The language manager encountered an unexpected internal error. More
information appears in detail text.
Effect. The operation fails.
Recovery. None. Report the entire message to your service provider.
SQL 11224
Cause. The Java Virtual Machine encountered an internal error and raised an
exception. More information appears in detail text. Also see the errors that
accompany this message for more information.
Effect. The operation fails.
Recovery. Perform whatever corrective action is required to eliminate the Java
exception. Stop and restart the session, and retry the SQL/MX statement.
SQL 11225
Cause. In a CREATE PROCEDURE statement, an invalid Java signature was used in
the EXTERNAL NAME clause.
Effect. The operation fails.
11222 The operation failed because the Java Virtual Machine
ran out of memory.
11223 Language Manager encountered an internal error detail
text.
11224 The Java virtual machine raised an exception. Details:
detail text.
11225 Specified signature is invalid. Reason: The Java
signature for a Java main method must be
(java.lang.string[]).