OS/400 database server code

cdeckard

Active Member
Hi all,

We are experiencing problems in the application P4210 with the following errors.
Anyone have any ideas. We are stuck and unable to retrieve or enter any Sales orders.

I appreciate your quick responses.

Thank you.


10872/10628 Thu Jul 24 10:08:09 2008 JDBODBC.C5319
ODB0000071 - SQLPrepare failed

10872/10628 Thu Jul 24 10:08:09 2008 JDBODBC.C5319
[IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]PWS0005 - Error occurred in the OS/400 database server code. - SQLSTATE: S1000

10872/10628 Thu Jul 24 10:08:09 2008 jdb_drvm.c920
JDB9900401 - Failed to execute db request

10872/10628 Thu Jul 24 10:08:26 2008 JDBODBC.C5319
ODB0000071 - SQLPrepare failed

10872/10628 Thu Jul 24 10:08:26 2008 JDBODBC.C5319
[IBM][Client Access Express ODBC Driver (32-bit)][DB2/400 SQL]PWS0005 - Error occurred in the OS/400 database server code. - SQLSTATE: S1000

10872/10628 Thu Jul 24 10:08:26 2008 jdb_drvm.c920
JDB9900401 - Failed to execute db request

10872/10628 Thu Jul 24 10:09:22 2008 JDBODBC.C5319
ODB0000071 - SQLPrepare failed
 
Hi,

1. Have you checked that your server is MTR compliant?
(I mean PTFs, CUMs, OS level, etc)
2. Have you tried stopping services and deleting all
*SQLPKG packages (except for Q* ones)?
 
Sebastian,

We just did an IPL 2 days ago. In this process all SQLPKG are deleted. We do this approx every week. We will do another IPL and delete the SQLPKG in appox 30 minutes. We have not had any AS/400 system changes for quite some time. Could there be other underlying issues?

Thank you for your response.
 
Hi,

Have you installed any PTFs lately?
How about your OS/400 journals? Are they full or almost?
Do you have enough free disk space on your ASPs?
(Disk occupation above 80% may also cause a negative
impact on performance)
Have you installed a Client Access Service Pack update
on your Fat Clients?
 
Sebastian,

We IPL'd and deleted all the *SQLPKGs. We noticed that our CL that we run does NOT delete the *SQLPKG that begin with 'OEXPLORxxxxx'. These are ok to delete? You say all but those beginning with 'Q' only. Our previous mngr set up the procedure to delete all but 'Q' and 'O'. Just checking befoe we commit as the AS/400 will not allow us to rename or copy the *SQLPKGs.

In response to your previous questions, our journals were just cleared, our disk space is 72% and we have not installed a Client Access Service Pack.

Thank you again for your help.
 
Hi,

Yes, you should also delete OEXPLORE* *SQLPKG files, these
are generated by Xe fat/citrix clients.
The only ones to never delete are those beginning with Q*.
 
[ QUOTE ]
Our previous mngr set up the procedure to delete all but 'Q' and 'O'.

[/ QUOTE ]

I would highly recommend taking db services down and deleting QZDAPKG.

It is almost always the source of this kind of problem.
 
Back
Top