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-14
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.
SQL 11206
Cause. Initialization of the class failed, either because of a problem with a static code
block in the class file or because the class file has an incorrect format.
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 static initialization code is correct,
check that the class file was not modified after it was generated with the NonStop
Server for Java javac utility.
SQL 11207
Cause. The Java method given in the CREATE PROCEDURE statement was not
found in the class file or, if this is a CALL statement, the Java method corresponding to
the stored procedure was not found in the class file.
Effect. The operation fails.
11205 Java class class-file-name was not found in external
path path-name.
11206 Java class class-file-name failed to initialize.
11207 Java method method-name was not found in Java class
class-file-name.