cbartlet
Member
Hi all
Don't know if anyone can help with this problem.
We are running E1 8.12, TR 8.98.4.1. on iSeries V5R4 for the Enterprise Server.
Have been using LDAP for E1 for over 2 years with no problem. However our DC's are built on Win2003, so we are building 2008 DC's and migrating to those.
So I added a new config via P95928, activated it, the old one de-activated, restarted E1, tested online login and some UBE's, all good.
Next day we had no problems with users logging in at all, UBE's ran thru the day with no problem.
The problems started when our overnight batch schedule ran, most UBE's completed but a handful failed with "runube: jdeSecGetExtendedTokenByPwd failed"
A handful of our security kernels had this in the log;
7052/148 MAIN_THREAD Wed Mar 27 21:44:59.753560 netqueue.c2763
putExternalQueue0x04 (kernel) failed for msg id 9, pid=7106, queue name=<Krnl7106RspQ>, lastIPCError=<eIPCNotFound>.
7052/148 MAIN_THREAD Wed Mar 27 21:44:59.754528 jdeksec.c1571
JDENET Error = JDENET eIPCErr: eIPCNotFound
Our Server Manager was alerting with lots of these messages;
Event Type: Outstanding Requests
Event Time: 27/03/13 21:43
Managed Instance: RAVEN_ES_6014
Additional Information:
Enterprise Server Process Detail
======================================
OS Status: 1 (RUNNING)
E1 Status: 1 (BUSY WITH STHG)
AS/400 Job Id: 958609
Process Id: 7052
User Id: 387
Group Id: 107
Process Type: 0 [Kernel Process]
Start Time: 27/03/13 20:09
Last Updated: 27/03/13 20:09
Process Name: SECURITY KERNEL
UBE's are submitted using RUNUBE command on the iSeries.
On the thought it might just be a rogue security kernel over the next 2 nights we re-started e1 but the problems persisted.
Eventually had to back out the change and point back to the original DC, re-started E1 again and all is back to normal.
I can't figure what is going on. The new DC looks fine, no resource issues overnight etc.
Has anyone had any experience of this sort of thing happening?
I have logged this with Oracle and they are investigating but they say it isn't an LDAP problem which I don't believe as the only change made was the DC.
Thanks in advance.
Chris
Don't know if anyone can help with this problem.
We are running E1 8.12, TR 8.98.4.1. on iSeries V5R4 for the Enterprise Server.
Have been using LDAP for E1 for over 2 years with no problem. However our DC's are built on Win2003, so we are building 2008 DC's and migrating to those.
So I added a new config via P95928, activated it, the old one de-activated, restarted E1, tested online login and some UBE's, all good.
Next day we had no problems with users logging in at all, UBE's ran thru the day with no problem.
The problems started when our overnight batch schedule ran, most UBE's completed but a handful failed with "runube: jdeSecGetExtendedTokenByPwd failed"
A handful of our security kernels had this in the log;
7052/148 MAIN_THREAD Wed Mar 27 21:44:59.753560 netqueue.c2763
putExternalQueue0x04 (kernel) failed for msg id 9, pid=7106, queue name=<Krnl7106RspQ>, lastIPCError=<eIPCNotFound>.
7052/148 MAIN_THREAD Wed Mar 27 21:44:59.754528 jdeksec.c1571
JDENET Error = JDENET eIPCErr: eIPCNotFound
Our Server Manager was alerting with lots of these messages;
Event Type: Outstanding Requests
Event Time: 27/03/13 21:43
Managed Instance: RAVEN_ES_6014
Additional Information:
Enterprise Server Process Detail
======================================
OS Status: 1 (RUNNING)
E1 Status: 1 (BUSY WITH STHG)
AS/400 Job Id: 958609
Process Id: 7052
User Id: 387
Group Id: 107
Process Type: 0 [Kernel Process]
Start Time: 27/03/13 20:09
Last Updated: 27/03/13 20:09
Process Name: SECURITY KERNEL
UBE's are submitted using RUNUBE command on the iSeries.
On the thought it might just be a rogue security kernel over the next 2 nights we re-started e1 but the problems persisted.
Eventually had to back out the change and point back to the original DC, re-started E1 again and all is back to normal.
I can't figure what is going on. The new DC looks fine, no resource issues overnight etc.
Has anyone had any experience of this sort of thing happening?
I have logged this with Oracle and they are investigating but they say it isn't an LDAP problem which I don't believe as the only change made was the DC.
Thanks in advance.
Chris