At 5AM the ODBC is KO, at 7AM With user it Work !!!

bibollet

New Member
I use an ODBC connection to get information from a Progress Base.
At 5AM I have this message and the base is out :
05:00:02 SQLSRV2 1: Login usernum 170, remote SQL client. (8873)
05:00:02 SQLSRV2 1: Usr 170 set name to administrateur. (7129)
05:00:02 SQLSRV2 1: Logout by administrateur on . (453)
05:22:35 BROKER 0: SYSTEM ERROR: bkioWrite: Bad file descriptor was used during write, fd 888, len 8192, offset 95353, file d:\Quorum\Data\Naef\Reg\reg.b1. (9446)
05:22:35 BROKER 0: bkwrite: write to disk failed errno 9. (3645)
05:22:35 BROKER 0: SYSTEM ERROR: Releasing regular latch. latchId: 1 (5028)
05:22:35 SRV 10: Stopped. (2520)
05:22:35 BROKER 0: User 0 died holding 1 shared memory locks. (2522)
05:22:35 SQLSRV2 1: Found shutdown value 2.
05:22:35 SQLSRV2 1: Stopped. (2520)
05:22:35 BROKER 0: Begin ABNORMAL shutdown code 2 (2249)
05:22:35 SRV 4: Stopped. (2520)

At 7 PM all is Ok :

07:55:21 SQLSRV2 12: SQL Server 9.1D.06 started, configuration: "reg.virtualconfig"
07:55:21 SQLSRV2 12: "d:\quorum\data\naef\reg\reg" started on port 5011, pid 1692 (0x0000069c).
07:55:21 SQLSRV2 12: Thread stack size: 1024000 (bytes).
07:55:21 SQLSRV2 12: DLC from ENVIRONMENT VARIABLE is: d:\Dlc
07:55:21 SQLSRV2 12: WRKDIR from REGISTRY is: d:\temp\
07:55:21 SQLSRV2 12: JDKHOME from REGISTRY is: d:\Dlc\jdk
07:55:21 SQLSRV2 12: JREHOME from REGISTRY is: d:\Dlc\jre
07:55:21 SQLSRV2 12: CLASSPATH from DEFAULT is:
07:55:21 SQLSRV2 12: PROSQL_LOCKWAIT_TIMEOUT value is: 5 seconds
07:55:22 SQLSRV212: Login usernum 141, remote SQL client. (8873)
07:55:22 SQLSRV212: Usr 141 set name to administrateur. (7129)
07:55:22 SQLSRV212: Logout by administrateur on . (453)
 

dcheatham

New Member
I would strongly suggest upgrading to 91D09. We had crashes related to SQL pulls for years. Our database is finally stable after this release came out.
 
Top