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-15
Recovery. Verify that the Java method exists in the class file and that it has the public
and static attributes, and then retry the SQL/MX statement. Use the NonStop Server
for Java javap utility to determine which methods exist in a given class file. If this is a
CALL statement, determine if the class file was removed or modified after the stored
procedure was created. If so, you might need to drop and re-create the stored
procedure.
SQL 11208
Cause. In a CREATE PROCEDURE statement, the list of parameter types specified in
the EXTERNAL NAME clause was not enclosed in parentheses.
Effect. The operation fails.
Recovery. Correct the EXTERNAL NAME clause and retry the SQL/MX statement.
SQL 11209
Cause. In a CREATE PROCEDURE statement, 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 Java method.
Effect. The operation fails.
Recovery. Correct the EXTERNAL NAME clause and resubmit.
SQL 11210
Cause. In a CREATE PROCEDURE statement, the OUT or INOUT parameter at the
specified parameter position did not have opening and closing square brackets ([ ]) in
the EXTERNAL NAME clause.
Effect. The operation fails.
Recovery. Correct the EXTERNAL NAME clause and resubmit.
11208 Specified signature is invalid. Reason: The list of
parameter types must be enclosed in parentheses.
11209 Specified signature is invalid. Reason: the number of
parameters value must match the number of parameters in Java
method.
11210 Specified signature is invalid. Reason: Missing [] for
OUT/INOUT parameter at position value.