This section describes the error codes in Natural for Db2 for zIIP(NDZ).
Note that no Action is specified for an internal error in the following table.
If it is an internal error or if the error is not resolved after the recommended action is
performed, contact Software AG support mentioning the specific error code and associated
message.
The following table explains the error codes with their description.
| Error category | Return code | Message |
|---|---|---|
| Error during session initialization | 101 | Error occurred while obtaining a storage area |
| 102 | NDZ Server is not available
Verify the value of the parameter NDZSRV and ensure the NDZ Server specified is up and running |
|
| 103 | Number of connected clients reached the maximum clients limit(ndz.maxClients)
specified in the ndz.properties file
Modify the ndz.maxClients parameter in ndz.properties file to run more jobs parallelly |
|
| 104 | Error creating pause element | |
| 105 | Error releasing pause element | |
| 106 | Error pausing a client task | |
| 107 | Session initialization request for the client cannot be processed because the
NDZ Server is already in terminating state
If the NDZ server is terminating, restart the NDZ server again and execute the job |
|
| 108 | Insufficient access for caller to access a protected storage | |
| Error during processing request | 201 | NDZ Server is not available
Verify the value of the parameter NDZSRV and ensure the NDZ Server specified is up and running |
| 202 | The client address is invalid | |
| 203 | Error releasing pause element | |
| 204 | Error pausing client task | |
| 205 | Request to stop the client is pending. The client is either in Invalid or in
terminating state
If the NDZ server is terminating, restart the NDZ server again and execute the job |
|
| 206 | Client JOBID does not match with the client NDZ server is processing. | |
| 207 | There is already a request pending for the client | |
| 208 | Insufficient access for caller to access a protected storage | |
| Error during session termination | 301 | NDZ Server is not available
Verify the value of the parameter NDZSRV and ensure the NDZ Server specified is up and running |
| 302 | The client address is invalid | |
| 303 | Error releasing pause element | |
| 304 | Error pausing client task | |
| 305 | Request to stop the client is pending. The client is either in Invalid or in
terminating state
If the NDZ server is terminating, restart the NDZ server again and execute the job |
|
| 306 | Client JOBID does not match with the client NDZ server is processing. | |
| 307 | There is already a request pending for the client | |
| 308 | Insufficient access for caller to access a protected storage | |
| Error during connection to Db2 | 500 | Error creating User Context. The associated exception text describes the possible cause for the error. |
| 501 | Error registering static statement during static execution. The associated
exception text describes the possible cause for the
error
Ensure the static preparation steps were successfully executed and the associated profile is available in the NDZ static directory(ndz.staticPath) specified in the ndz.properties file |
|
| 540 | Error fetching CURRENT PATH special register value from Db2. The associated exception text describes the possible cause for the error. | |
| 550 | Error getting connection for Db2. The associated exception text describes the possible cause for the error. | |
| 551 | Error creating pooled connection for Db2. The associated exception text describes the possible cause for the error. | |
| 552 | Error creating pooled connections. Number of connections exceed maximum
clients
Adjust the maximum clients parameter in ndz.properties file to run more jobs parallelly |
|
| Error during request execution through distributed connection | 600 | The statement type <statement type> is not supported by NDZ |
| 601 | The type <data type> is not supported by NDZ | |
| 602 | The java.sql type <jdbcsqltype> is not supported by NDZ | |
| 603 | NDZ does not support the set var statement requested. (internal request number='') | |
| 604 | Error fetching parameter types for procedure <Procedure name>. Please verify if the procedure name is correct | |
| 605 | The cursor <Cursor name> is not available | |
| 606 | UPDATE and DELETE statements with the clause WHERE CURRENT OF are not supported by the IBM Db2 JDBC driver for scrollable cursors when useRowsetCursor is specified | |
| 650 | The encoding <Encoding type> is not supported | |
| Error related to LOB columns | 701 | Error reading LOB file <File name> (SQL file option: <>, File mode: <>) |
| 702 | Error writing LOB file <File name> (SQL file option: <>) | |
| 703 | Error fetching data from LOB column | |
| Error related to SQL data unavailability | 800 | The input SQLDA is not present or does not contain any SQLVAR |
| 801 | The output SQLDA is not present or does not contain any SQLVAR | |
| 802 | The first extended output SQLDA is not present | |
| Error related to password encryption | 901 | The file 'db2.properties' was not found
Please make sure the db2.properties file present in directory <NDZPATH>/etc/ and the user have the access to the file. The associated exception text describes the possible cause for the error |
| 910 | Error creating directory for Db2 encrypted password (<Exception message>). The associated exception text describes the possible cause for the error | |
| 911 | Error reading Db2 password encryption key (<Exception message>). The associated exception text describes the possible cause for the error | |
| 912 | Error reading Db2 encrypted password file (<Exception message>). The associated exception text describes the possible cause for the error | |
| 913 | Error writing Db2 password encryption key (<Exception message>). The associated exception text describes the possible cause for the error | |
| 914 | Error writing Db2 encrypted password file (<Exception message>). The associated exception text describes the possible cause for the error | |
| 915 | Error while generating Db2 password encryption key. The associated exception text describes the possible cause for the error | |
| 916 | Error while decrypting Db2 password. The associated exception text describes the possible cause for the error | |
| 917 | The Db2 encrypted password file is not available at <file_path> and the
property 'password' is not set in the file
db2.properties
Execute the script <NDZ home directory>/bin/ndz-db2-pass.sh to encrypt the password to use or specify the password in db2.properties file |
|
| 918 | The Db2 encryption key is not available at
<file_path>
Verify if the key file is present in <NDZ home directory>/var and the user has the required access. If the file is not present, execute the script <NDZ home directory>/bin/ndz-db2-pass.sh with option -g to generate the key and encrypt the password to use |
|
| Unspecified errors | 997 | Error executing rollback due to an unhandled exception. The associated exception text describes the possible cause for the error |
| 998 | Runtime exception caused by:<Error description>. The associated exception text describes the possible cause for the error | |
| 999 | Unhandled exception. The associated exception text describes the possible cause for the error |