vmcdaniel
Active Member
Hello again JDEList,
It's been a while since I've posted here...but we need some insight as to what has worked for others in our situation:
Since migrating our database from SQL 2000 SP4 to SQL 2005 SP2 on Windows 2003 Server Enterprise SP1 we have been experiencing nightly database disconnects in batch, for example...
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.707000 Runbatch.c317
INITIALIZING RUNBATCH job: 3531601
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722000 ipcmisc.c299
process 5728 <runbatch.exe> registered in entry 60
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722001 Runbatch.c462
Startup for User=GLSCHEDULR, Env=PD810, Role=*ALL, Job#=3531601
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722002 Runbatch.c479
bAPListening=0
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660000 zdrv.cpp328
Initializing the Z Driver
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660001 zdrv.cpp342
Gettting user data from hEnv
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660002 zdrv.cpp364
User data is GLSCHEDULR, PD810
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660003 zdrv.cpp373
Creating XML Session
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.488000 Odbc_p1.c1650
ODB0000163 - wSQLExtendedFetch failure. rc=-1
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503000 Odbc_p1.c1650
ODB0000164 - STMT:00 [08S01][10054] [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503001 Odbc_p1.c1650
ODB0000164 - STMT:01 [08S01][10054] [Microsoft][SQL Native Client]Communication link failure
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503002 Odbc_p1.c1664
ODB0000091 - SQLExtendedFetch failed. Table(1st) F03B14, ODBC DSN Business Data - PROD.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503003 Odbclog.c436
ODB0000162 - Connection lost during earlier operation.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503004 Jdb_drvm.c1042
JDB9900172 - Failed to execute db fetch
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503005 Jtp_cm.c1300
JDB9900255 - Database connection to F03B14 (Business Data - PROD) has been lost.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.550000 Jtp_cm.c1252
JDB9900256 - Database connection to F03B14 (Business Data - PROD) has been re-established.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566000 Jdbodbc.c2698
ODB0000020 - DBInitRequest failed - lost database connection.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566001 Jdb_drvm.c893
JDB9900168 - Failed to initialize db request
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566002 Jtp_cm.c1004
JDB9909007 - Unable to obtain driver request handle
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566003 Jtp_cm.c1300
JDB9900255 - Database connection to F03B11 (Business Data - PROD) has been lost.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566004 Jtp_cm.c1252
JDB9900256 - Database connection to F03B11 (Business Data - PROD) has been re-established.
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.490000 ipcmisc.c299
API ipcSawUnregisterProcV1 : process 5728 unregistered in entry 60
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.647000 zdrv.cpp389
Terminating Z driver
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.647001 zdrv.cpp406
Calling freeSession
_____________________________________________________
Oracle support steered us in the direction of taking two SQL 2005 hotfixes:
KB 945442 - Fast Forward Query takes longer to cancel in SQL 2005 vs. SQL 2005
KB 945443 - Fast Forward query takes longer in SQL 2005 vs. SQL 2000
Installing these hotfixes did alleviate some disconnect popup errors from E1 apps such as P4210, but as you can see, we still get disconnect errors in report logs. We don't see these very often in our E1 kernel logs. Also, by taking the fix, Oracle stated that we could then remove the server/fat client jde.ini workaround of Rowset Size=1 in the [DB System Settings] section. We did that too.
Currently, we have an urgent case with Microsoft open for them to look at our network traffic and E1 server and separate database server, and figure out the root cause of this. When using SQL 2000 SP4 prior to SQL 2005, we experienced ZERO disconnects in our E1 logs.
I see that some on JDEList have experienced some similar issues:
117415
I'd like some good feedback from someone who has had the problem and who has fixed it.
Thanks,
Vernon
It's been a while since I've posted here...but we need some insight as to what has worked for others in our situation:
Since migrating our database from SQL 2000 SP4 to SQL 2005 SP2 on Windows 2003 Server Enterprise SP1 we have been experiencing nightly database disconnects in batch, for example...
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.707000 Runbatch.c317
INITIALIZING RUNBATCH job: 3531601
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722000 ipcmisc.c299
process 5728 <runbatch.exe> registered in entry 60
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722001 Runbatch.c462
Startup for User=GLSCHEDULR, Env=PD810, Role=*ALL, Job#=3531601
5728/4420 MAIN_THREAD Tue Feb 05 03:53:53.722002 Runbatch.c479
bAPListening=0
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660000 zdrv.cpp328
Initializing the Z Driver
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660001 zdrv.cpp342
Gettting user data from hEnv
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660002 zdrv.cpp364
User data is GLSCHEDULR, PD810
5728/4420 MAIN_THREAD Tue Feb 05 03:53:54.660003 zdrv.cpp373
Creating XML Session
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.488000 Odbc_p1.c1650
ODB0000163 - wSQLExtendedFetch failure. rc=-1
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503000 Odbc_p1.c1650
ODB0000164 - STMT:00 [08S01][10054] [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503001 Odbc_p1.c1650
ODB0000164 - STMT:01 [08S01][10054] [Microsoft][SQL Native Client]Communication link failure
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503002 Odbc_p1.c1664
ODB0000091 - SQLExtendedFetch failed. Table(1st) F03B14, ODBC DSN Business Data - PROD.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503003 Odbclog.c436
ODB0000162 - Connection lost during earlier operation.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503004 Jdb_drvm.c1042
JDB9900172 - Failed to execute db fetch
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.503005 Jtp_cm.c1300
JDB9900255 - Database connection to F03B14 (Business Data - PROD) has been lost.
5728/4420 WRK:Starting jdeCallObject Tue Feb 05 04:05:41.550000 Jtp_cm.c1252
JDB9900256 - Database connection to F03B14 (Business Data - PROD) has been re-established.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566000 Jdbodbc.c2698
ODB0000020 - DBInitRequest failed - lost database connection.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566001 Jdb_drvm.c893
JDB9900168 - Failed to initialize db request
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566002 Jtp_cm.c1004
JDB9909007 - Unable to obtain driver request handle
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566003 Jtp_cm.c1300
JDB9900255 - Database connection to F03B11 (Business Data - PROD) has been lost.
5728/4420 MAIN_THREAD Tue Feb 05 04:05:41.566004 Jtp_cm.c1252
JDB9900256 - Database connection to F03B11 (Business Data - PROD) has been re-established.
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.490000 ipcmisc.c299
API ipcSawUnregisterProcV1 : process 5728 unregistered in entry 60
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.647000 zdrv.cpp389
Terminating Z driver
5728/4420 MAIN_THREAD Tue Feb 05 04:10:24.647001 zdrv.cpp406
Calling freeSession
_____________________________________________________
Oracle support steered us in the direction of taking two SQL 2005 hotfixes:
KB 945442 - Fast Forward Query takes longer to cancel in SQL 2005 vs. SQL 2005
KB 945443 - Fast Forward query takes longer in SQL 2005 vs. SQL 2000
Installing these hotfixes did alleviate some disconnect popup errors from E1 apps such as P4210, but as you can see, we still get disconnect errors in report logs. We don't see these very often in our E1 kernel logs. Also, by taking the fix, Oracle stated that we could then remove the server/fat client jde.ini workaround of Rowset Size=1 in the [DB System Settings] section. We did that too.
Currently, we have an urgent case with Microsoft open for them to look at our network traffic and E1 server and separate database server, and figure out the root cause of this. When using SQL 2000 SP4 prior to SQL 2005, we experienced ZERO disconnects in our E1 logs.
I see that some on JDEList have experienced some similar issues:
117415
I'd like some good feedback from someone who has had the problem and who has fixed it.
Thanks,
Vernon