DMiller
Guest
Just wanted to get the information out there, that the latest iSeries Access Service Pack SI21917 for V5R3 appears to be bad.
We were having all kinds of connection issues on fat clients with our 8.10 release. Sometimes you could log in successful and other times it would just hang and then crash EnterpriseOne while trying to connect to Business Data or Control Tables. In the JDE.LOG, the only errors we would see is:
176/3520 MAIN_THREAD Wed Mar 15 13:37:04.732025 Jdb_ctl.c3383
Starting OneWorld
176/3520 MAIN_THREAD Wed Mar 15 13:38:08.522001 Jdbodbc.c1297
ODB0000163 - SQLDriverConnect failure. rc=-1
176/3520 MAIN_THREAD Wed Mar 15 13:38:08.522003 Jdbodbc.c1307
ODB0000010 - SQLDriverConnect failed. ODBC DSN: Business Data - TEST.
The problem was so sporadic! There was no pattern and a certain way to make it fail every time. Therefore I ended up calling Oracle and when they called back, they said that we are customer #3 that has called in with this issue when running V5R3 Service Pack SI21917. The suggested fix is to back level the service pack to the one before this one which is SI20055. This really did fix the issues that we were having.
Apparently Oracle has opened up a PMR with IBM but who knows how long it will take to get the problem fixed.
So I just wanted to inform and warn everyone out there.
Have a great day!
We were having all kinds of connection issues on fat clients with our 8.10 release. Sometimes you could log in successful and other times it would just hang and then crash EnterpriseOne while trying to connect to Business Data or Control Tables. In the JDE.LOG, the only errors we would see is:
176/3520 MAIN_THREAD Wed Mar 15 13:37:04.732025 Jdb_ctl.c3383
Starting OneWorld
176/3520 MAIN_THREAD Wed Mar 15 13:38:08.522001 Jdbodbc.c1297
ODB0000163 - SQLDriverConnect failure. rc=-1
176/3520 MAIN_THREAD Wed Mar 15 13:38:08.522003 Jdbodbc.c1307
ODB0000010 - SQLDriverConnect failed. ODBC DSN: Business Data - TEST.
The problem was so sporadic! There was no pattern and a certain way to make it fail every time. Therefore I ended up calling Oracle and when they called back, they said that we are customer #3 that has called in with this issue when running V5R3 Service Pack SI21917. The suggested fix is to back level the service pack to the one before this one which is SI20055. This really did fix the issues that we were having.
Apparently Oracle has opened up a PMR with IBM but who knows how long it will take to get the problem fixed.
So I just wanted to inform and warn everyone out there.
Have a great day!