Needle: IBM iSeries (AS400) Power Outage JDE Recovery
Read Time:1 Min, 30 Sec
Crazy to think but this issue has come up a few times in my years as an Oracle JD Edwards CNC Admin as evidenced by my post a few years ago (EnterpriseOne IBM iSeries (AS400) Power Outage Fix). No one is sure what happened, but the system went down hard. The whole IT department has been in a panic since it happened and now everything is back up and running… except JDE. You run STRNET but the only thing that starts is the subsystem or nothing at all.
That’s where this little needle-in-a-hay-stack comes in:
Oracle Support Doc ID 2226846.1 – E1: KER: Recovering From An IBM iSeries (AS/400) Enterprise Server Hard Crash Due To A Power Outage
The document breaks the process down into 7 steps to perform from the green screen (assuming the AS400 itself is up and running without issues and you have tried to start JDE by either issuing a STRNET command or using the normal startup script when the server was turned back on):
- Run the following command:
ENDNET - Run the following command several times (3-5):
CLRIPC - Delete *SQLPKG objects – Oracle Doc ID 626568.1
WRKOBJ *ALL/*ALL *SQLPKG- Delete only EnterpriseOne owned SQL Packages
- Do NOT delete any system packages in libraries QIWS and QSYS or any SQL packages starting with “Q”.
- Delete the dddict.ddb, dddict.xdb, ddtext.ddb, ddtext.xdb, glbtbl.ddb and glbtbl.xdb – Oracle Doc ID 1298216.1
WRKLNK '/PATHCODE/specfile'
- Delete Orphaned User Queues – Oracle Doc ID 659250.1
WRKOBJ E910SYS/Q0000*- Delete objects of type *USRQ
- Disable journaling of the icudt32e.dat file – Oracle Doc ID 654345.1
- Use STRNET to start the JDE services
If you have questions, either check out the Oracle docs or leave me a comment.
Happy
0
Sad
0
Excited
0
Sleepy
0
Angry
0
Surprise
0
Average Rating