Fix #DB2 SQL1639N ( SQLCODE=-1639, SQLSTATE=08001, SQLERRMC=null) authentication issue

By | November 21, 2017

After migrating my full DB2 backup (binaries and data) to a new server I got into several issue. One was already described in the previous post here.

ISSUE:

Even after fixing that start issue I was still not OK. My WebSphere data source that linked to the DB2 instance was not responding.

Trying to ping the data source resulted in the following reported error:

INVESTIGATION:

Then I tried to see from the command line what is the result:

OK so this is more clear. Instead of the cryptic SQL error reported to the client by the jdbc driver I got I more explicit description of the error code “1639”.

FIX:

After some digging through the IBM DB2 documentation the solution was to change the ownership and rights of two executable scripts. Note that I use system-based authentication.

Contribute to this site maintenance !

This is a self hosted site, on own hardware and Internet connection. The old, down to earth way 🙂. If you think that you found something useful here please contribute. Choose the form below (default 1 EUR) or donate using Bitcoin (default 0.0001 BTC) using the QR code. Thank you !

€1,00

Advertisements

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.