Neoview Messages Manual (R2.2)

Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
SQL 11111
11111 MXUDR: Internal error: value.
Cause The HP Neoview database UDR server received an incorrectly formatted message.
Effect The request message is rejected, and the HP Neoview SQL statement 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 11113
11113 MXUDR: Internal error: An unexpected UNLOAD request arrived for
UDR handle handle.
handle
is an internal identifier generated by the HP Neoview database software and used
in messages to and from the Neoview database UDR server.
Cause The HP Neoview database UDR server received a request out of sequence.
Recovery Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition.
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 HP Neoview platform for Java product and the HP
Neoview database software language manager. Verify the existence of the specified class. Stop
and restart the session, and retry the Neoview database statement.
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 HP Neoview platform for Java product. Stop and
restart the session, and retry the HP Neoview database statement.
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.
218 Trigger, UDR Server, and Language Manager Messages (11000 Through 11399)