SQL/MX 2.x Messages Manual (H06.04+)

Trigger, UDR Server, and Language Manager
Messages (11000 through 11399)
HP NonStop SQL/MX Messages Manual—540498-003
12-14
SQL 11203
Cause. Initialization of the language manager failed during creation of an internal
LmClassLoader object. This failure might have happened because the file
mxlangman.jar is missing or corrupted.
Effect. The operation fails.
Recovery. The LmClassLoader class is part of the file
/usr/tandem/sqlmx/udr/mxlangman.jar. Verify that the file exists and has not
been modified after installation. Stop and restart the session, and retry the SQL/MX
statement.
SQL 11204
Where method-name is the name of a Java method.
Where description is text further explaining the problem.
Cause. During a CREATE PROCEDURE operation, the specified Java method could
not be located for verification purposes.
Effect. The operation fails.
Recovery. Determine if the Java class file specified in the CREATE PROCEDURE
statement exists. Determine if the Java method exists in the class file. The method
must have the attributes public and static and must return void. Correct the class file or
the method and resubmit.
SQL 11205
Cause. The class file did not exist in the given directory.
Effect. The operation fails.
Recovery. Determine if the class file exists in the directory. If the SQL/MX statement is
a CALL statement, determine if the class file was moved from the directory that was
specified when the procedure was created. If the class file has been moved, either
restore it to the original location, or drop the procedure and re-create it with the new
location of the class file.
11203 The Language Manager failed to create its class loader,
possibly due to corrupt mxlangman.jar file.
11204 Unable to validate Java method ‘method-name’ because a
Java exception was encountered. Details: description.
11205 Java class class-file-name was not found in external
path path-name.