Quote:
Originally Posted by aflorin27
DB2 error messages are not so "user-friendly" as the SQL Server ones. But you may find some useful clues when searching on the Internet the SQLSTATE error codes.
|
Google eg. "db2 SQLSTATE: 42605, SQLCODE: -170" for a more elaborate error messages.
There is a way to tell DB2, in the connect string, to do the lookup for you and give a more verbose error message, but I forgot how to do it. You may want to post that question on the DB2 forum.