Menu
When I call a SQL statement via JDBC on the DB2 and the statement fails, I catch an SQLException with the following message text:
com.ibm.db2.jcc.a.nn: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703,
SQLERRMC=O.METADATENSATZ, DRIVER=3.52.95
I tried an automatic translation of the message according to the error list published by IBM, but there are placeholders inside the messages referencing other elements of the exception.
While looking for these elements inside the exception, I found the DB2ExceptionFormatter and tried to use it to access the missing elements.
But here I stopped, because the DB2ExceptionFormatter gave me a clue:
Error occurred while trying to obtain message text from server. Only message tokens are available.
So my question is: What do I have to configure to get the correct messages from the DB2 server?
If I can get a human readable message from the server, I could use it directly and wouldn't have to translate it by myself.
386
The error diagnostic containing the SQL Return Code is held in the field SQLCODE within the Db2 SQLCA block.
When called in a CATCH block, ERROR_MESSAGE returns the complete text of the error message that caused the CATCH block to run. The text includes the values supplied for any substitutable parameters - for example, lengths, object names, or times. ERROR_MESSAGE returns NULL when called outside the scope of a CATCH block.
Qualify the ambiguous column name with a correct table name. If the SQL statement try to use INSERT , UPDATE or SELECT a column name which is not part of the table, then this DB2 SQL Error code is generated. ORDER BY clause in wrong because the column name is not a part of the result table .
Explanation. An application program attempted to use a package that was not found. The package that was not found. The collection-id is blank if the CURRENT PACKAGESET special register was blank for the local program execution.
I'm not sure what message reference you're looking at above (it seems to be iSeries?) but you're better off going to the DB2 Message Reference over here.
Looking up SQL0206 gets us this page, with the following information:
name is not valid in the context where it is used.
The SQLERRMC is "O.METADATENSATZ" so I would take this to mean you have sent an SQL statement to DB2 and it is reporting that "O.METADATENSATZ" is not valid...either the column doesn't exist or the table "O" does not exist.
As the message reference states, if you want to automatically translate DB2 error messages:
To invoke message help, open the command line processor and enter:
? XXXnnnnn
where XXX represents a valid message prefix and nnnnn represents a valid message number.
The message text associated with a given SQLSTATE value can be retrieved by issuing:
? nnnnn
or
? nn
where nnnnn is a five digit SQLSTATE (alphanumeric) and nn is the two digit SQLSTATE class code (first two digits of the SQLSTATE value).
In your case, typing "? SQL0206" in a DB2 CLP will get you the error message.
61
I found a hint here:
retrieveMessagesFromServerOnGetMessage:
Specifies whether JDBC SQLException.getMessage calls cause the IBM DB2 Driver for JDBC and SQLJ to invoke a DB2 for z/OS stored procedure that retrieves the message text for the error. The data type of this property is boolean. The default is false, which means that the full message text is not returned to the client.
I tried this, but the output of sqlException.getMessage() only changed to
O.METADATENSATZ
without any surrounding message text.
Now I found this:
Before you can use certain functions of the IBM® Data Server Driver for JDBC and SQLJ on a DB2® for z/OS® subsystem, you need to install a set of stored procedures and create a set of tables.
...
WLM must be installed on the z/OS system.
WLM is the DB2 Workload Manager that isn't available for the DB2 Express edition I'm using for development :-(
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With