Problems after Restoring AS/400 System

wkaauamo

wkaauamo

Active Member
Hello list, hopefully someone will have an applicable suggestion...

We experienced an AS/400 hardware failure and eventually got the system back up after restoring from tape. I then deleted all *SQLPKG objects in the JDE libraries on the AS/400 and started up the ES. However, we're now receiving errors on the fat client when signing on to JDE, running UTB, etc. Here is the fat client JDE.LOG just from signing on to JDE:

2096/776 Mon Jun 21 13:12:07 2004 jdb_ctl.c2763
Starting OneWorld

2096/776 Mon Jun 21 13:12:15 2004 JDBODBC.C3635
ODB0000025 - SQLTables failed

2096/776 Mon Jun 21 13:12:15 2004 jdb_drvm.c1538
JDB9900189 - Failed to verify that table exists in System - B7334 - DNT

2096/776 Mon Jun 21 13:12:15 2004 JDBODBC.C3635
ODB0000025 - SQLTables failed

2096/776 Mon Jun 21 13:12:15 2004 jdb_drvm.c1538
JDB9900189 - Failed to verify that table exists in System - B7334 - DNT

2096/776 Mon Jun 21 13:12:15 2004 JDBODBC.C3635
ODB0000025 - SQLTables failed

2096/776 Mon Jun 21 13:12:15 2004 jdb_drvm.c1538
JDB9900189 - Failed to verify that table exists in System - B7334 - DNT

2096/776 Mon Jun 21 13:12:15 2004 combined.c344
RDEL0000045 - Could not open tables for reliable event delivery (F90703 and F90704). Reliable event delivery will be disabled

2096/776 Mon Jun 21 13:12:15 2004 Environment.cpp172
Solution Explorer Started

Anyone have any ideas?
 
How many objects do you have in SYS7333 lib? In that lib I have 566.

Wes
 
I have 621 files inside my SYS7334 (ERP 8.0) library. Some are from *SQLPKG objects of course. So, it would be hard to tell whats going on without excluding those. What did you have in mind?

Also, we're going to try to reindex (reclaim) the IBM catalog in about 30 minutes. We think this will solve the problem since the errors all indicate that the system can sometimes see an object and sometimes not (the same object).
 
Enaure you still have these *SQLPKGS

QZDAPKG *SQLPKG QGPL
QSQLPKG2 *SQLPKG QSYS PACKAGE
QSQXDPKG *SQLPKG QSYS
 
All, thanks for the help and suggestions. The problem was the QGPL/QZDAPKG sqlpkg object that needed to be rebuilt. Normally, we don't touch that object because it is an IBM object. However, it became corrupt. So, by deleting it, the system recreated it upon next use. It seems to retain the information for the QSERVER and QUSRWRK subsystems, etc. Again, thanks for the help.
 
Back
Top