HPE NonStop SQL/MX Error – 11215 Java execution: Invalid null input value at parameter position value.

In this blog post, let’s learn about the error message “11215 Java execution: Invalid null input value at parameter position value.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

11215 Java execution: Invalid null input value at parameter position value.

Reason for the Error

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.

Solution

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. To change the Java data type, the procedure must be dropped and recreated

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022