We have run into an issue with our JDBC pool connections and wanted to see if anybody else has experienced this before. It is a standard at our company that database user IDs (we run on AIX platform) are non-interactive IDs. In other words if you use command line you cannot log into the server directly using this ID. You have to login using a diffeerent Id and then via the “su” command become the database ID.
We found that the moment our database Ids were changed to enforce this restriction the JDBC pools could no longer connect to the databases. (while running the TEST it comes back saying the Id has been revoke or is invalid). When they were changed back to interactive IDs the JDBC pools worked again.
According to our DBAs our other vender supplied packages do not have a problem with this ID restriction being enforced. They believe it has something to do with the dataDirect driver and how the application is trying to connect to the database.
Has anybody seen or come across this before?