dpeplinski
Active Member
I was going to post this on the recent SQLPKG thread, but decided it's different enough to warrant a new thread.
We upgraded to V5R2 in the spring, and since then we've had repeated problems with corrupt SQLPKGs. The symptom in OW is usually the same - a user goes into an application and clicks "find", but no records are returned. The application can vary, but it seems to affect only one application at a time. JDE.log contains:
440/988 Fri Aug 13 09:55:37 2004 JDBODBC.C5319
[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL0516 - Prepared statement QZ88435337A32CEDA2 not found. - SQLSTATE: S1000
440/988 Fri Aug 13 09:55:37 2004 jdb_drvm.c920
JDB9900401 - Failed to execute db request
The solution is to take services down, delete all SQLPKGS (I believe the problem SQLPKG is the OEXPLORFJA in PRODDTA) and bring it back up again - at least once a week.
I'm working with both IBM and PS on this, but no solutions seem to be forthcoming. Now I seem to recall someone else mentioning problems with SQLPKGS and V5R2. I'd like to get a couple more IBM clients with problems in order to get a bit more visibility on this problem. Has anyone else had this problem?
We upgraded to V5R2 in the spring, and since then we've had repeated problems with corrupt SQLPKGs. The symptom in OW is usually the same - a user goes into an application and clicks "find", but no records are returned. The application can vary, but it seems to affect only one application at a time. JDE.log contains:
440/988 Fri Aug 13 09:55:37 2004 JDBODBC.C5319
[IBM][iSeries Access ODBC Driver][DB2 UDB]SQL0516 - Prepared statement QZ88435337A32CEDA2 not found. - SQLSTATE: S1000
440/988 Fri Aug 13 09:55:37 2004 jdb_drvm.c920
JDB9900401 - Failed to execute db request
The solution is to take services down, delete all SQLPKGS (I believe the problem SQLPKG is the OEXPLORFJA in PRODDTA) and bring it back up again - at least once a week.
I'm working with both IBM and PS on this, but no solutions seem to be forthcoming. Now I seem to recall someone else mentioning problems with SQLPKGS and V5R2. I'd like to get a couple more IBM clients with problems in order to get a bit more visibility on this problem. Has anyone else had this problem?