HP Neoview Messages Manual page 245

Table of Contents

Advertisement

Effect
The operation fails.
Recovery
Correct the EXTERNAL NAME clause and resubmit.
SQL 1 1212
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.
Effect
The operation fails.
Recovery
Verify that your Java method signature size is less than the supported maximum,
and resubmit.
SQL 1 1213
11213 Specified signature is invalid. Reason: A return type must not
be specified.
Cause
In a CREATE PROCEDURE statement, a return type was given in the EXTERNAL
NAME clause.
Effect
The operation fails.
Recovery
Correct the EXTERNAL NAME clause and resubmit.
SQL 1 1214
11214 Specified signature is invalid. Reason: Unknown or unsupported
type used as a return type.
Cause
In a CREATE PROCEDURE statement, an unknown or unsupported return type was
given in the EXTERNAL NAME clause.
Effect
The operation fails.
Recovery
Correct the EXTERNAL NAME and resubmit.
SQL 1 1215
11215 Java execution: Invalid null input value at parameter position
parameter number.
Cause
A null value was supplied as input to a stored procedure in Java and the corresponding
Java data type is a primitive type that does not support null values.
Effect
The operation fails.
Recovery
Either correct the CALL statement so that the null value is not used, or change the
Java data type of the parameter to the corresponding Java wrapper type. For example, if the
Java data type is integer, change it to java.lang.Integer. Note that to change the Java data
type, the procedure must be dropped and re-created.
SQL 1 1216
11216 Java execution: Data overflow occurred while retrieving data at
parameter position parameter number.
Cause
During execution of a CALL statement, numeric or string overflow occurred during
processing the stored procedure output value returned in parameter parameter number.
Effect
The operation fails.
Recovery
Increase the field size of the SQL data type for the specified parameter.
245

Advertisement

Table of Contents
loading

Table of Contents