Neoview Messages Manual (Volume 1) (R2.4)

SQL 11201
11201 Language Manager initialization failed. Details: Error occurred
while loading Java class class-name.
class-name
is the name of the Java class.
Cause Initialization of the language manager failed because a required Java class could not
be loaded or because a required Java method was not found.
Effect The operation fails.
Recovery Check the installation of the NSJ product and the language manager. Verify the
existence of the specified class. Stop and restart the session, and retry the SQL statement. HP
support will perform recovery operations.
SQL 11202
11202 Language Manager initialization failed. Details: Unable to
initialize the Java virtual machine.
Cause Initialization of the language manager failed during creation of the Java Virtual
Machine.
Effect The operation fails.
Recovery Check the installation of the NSJ product. Stop and restart the session, and retry
the SQL statement. HP support will perform recovery operations
SQL 11203
11203 The Language Manager failed to create its class loader, possibly
due to corrupt mxlangman.jar file.
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 Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
SQL 11209
11209 Specified signature is invalid. Reason: The number of SQL
parameters value must match the number of parameters in the specified
signature.
value
is number of SQL parameters in the SPJ definition.
Cause In a CREATE PROCEDURE request, the EXTERNAL NAME clause includes a Java
signature, and the number of parameters in that signature does not match the number of
parameters in the SPJ definition.
Effect The operation fails.
Recovery Correct the EXTERNAL NAME clause and resubmit.
SQL 11212
11212 Specified signature is invalid. Reason: Java signature size is
bigger than the maximum supported size.
Cause In a CREATE PROCEDURE request, the Java signature size exceeded the maximum
supported size. The currently supported maximum Java signature size is 8192 characters.
Possible causes include an incorrect Java signature specified in the EXTERNAL NAME clause
or a very large number of parameters in the Java method.
230 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399)