Getting error "java.sql.SQLException: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLTABLES;00E79002, DRIVER=3.62.56"
We recently upgraded DB2 on Z/OS to v10.1.
Now the Developers are now getting this error from the java apps:
java.sql.SQLException: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLTABLES;
They connect through to the database using DB2 Connect v9.7.6. The DB2 Connect environment is on a z/Linux vm.
We've found that the 00E79002 has 3 possible causes, two of which we ruled out already (the procedure is stopped or the WLM environment is unavailable). The third has to do with dispatching priority of the WLM task on the mainframe. It basically says the mainframe couldn’t schedule the stored procedure before some timeout value hit. We have looked and looked, spoken with some IBM folk, and nobody knows about any WLM timeout value.
We attempted to elevate the priority of the stored procedure within WLM, but that apparently did not help.
Now we are looking at what else might be involved, and DB2 Connect is next in line.
What is causing this error and how can we fix it?
Now the Developers are now getting this error from the java apps:
java.sql.SQLException: DB2 SQL Error: SQLCODE=-471, SQLSTATE=55023, SQLERRMC=SYSIBM.SQLTABLES;
They connect through to the database using DB2 Connect v9.7.6. The DB2 Connect environment is on a z/Linux vm.
We've found that the 00E79002 has 3 possible causes, two of which we ruled out already (the procedure is stopped or the WLM environment is unavailable). The third has to do with dispatching priority of the WLM task on the mainframe. It basically says the mainframe couldn’t schedule the stored procedure before some timeout value hit. We have looked and looked, spoken with some IBM folk, and nobody knows about any WLM timeout value.
We attempted to elevate the priority of the stored procedure within WLM, but that apparently did not help.
Now we are looking at what else might be involved, and DB2 Connect is next in line.
What is causing this error and how can we fix it?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As far as I know, no db2 zparms were changed, nor changes made to any wlm definitions.
Do I need to connect from the DB2 Connect server and re-issue the relink commands? Namely,
cd $HOME/sqllib/bnd
db2 connect to TESTMFDB user mylogin1 using PPPPPP
db2 bind @ddcsmvs.lst blocking all sqlerror CONTINUE GRANT PUBLIC
Do I need to connect from the DB2 Connect server and re-issue the relink commands? Namely,
cd $HOME/sqllib/bnd
db2 connect to TESTMFDB user mylogin1 using PPPPPP
db2 bind @ddcsmvs.lst blocking all sqlerror CONTINUE GRANT PUBLIC
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did you change any other db2 zparm values?