Lock timeout on SMP machine

We have the following setup; SCO OS 5.0.5 with RS505A oss497c SMP 1.1.1Eb Informix IDS (Workgroup) 7.30 on a Dual Pentium II 450 Intel 440GX+ board About 4 times a day (seems like 100 today) we get; Lock timeout: caller= .. lock= .. owner= .. Unable to freeze processor 2, proceeding then panic and crash. This has only been in evidence since we started using out RDBMS server in earnest (Informix 7.3). Has anyone seen (and cured) this SCO panic, possibly in conjunction with the database engine ? TIA Bryan Tonnet bryan@printman.com.au

Bryan Tonnet wrote: > > We have the following setup; > > SCO OS 5.0.5 with RS505A > oss497c > SMP 1.1.1Eb > > Informix IDS (Workgroup) 7.30 > > on a > > Dual Pentium II 450 > Intel 440GX+ board > > About 4 times a day (seems like 100 today) we get; > > Lock timeout: caller= .. lock= .. owner= .. > Unable to freeze processor 2, proceeding > > then panic and crash. This has only been in evidence since we started > using out RDBMS server in earnest (Informix 7.3). Has anyone seen > (and cured) this SCO panic, possibly in conjunction with the database > engine ? > > TIA > > Bryan Tonnet > bryan@printman.com.au Bryan, I seem to remember that an incorrect installation order could drive to problems like the one you're experiencing (or better, I've read some articles posted here stating that if the installation order is not fully honored, you could have SMP problems even with RS505A and OSS497C installed). From memory, the installation pattern should be : - install the base OS - install the SMP package but DO NOT RELINK (if possible) or reboot - apply patch RS505A - relink + reboot - apply patch OSS497C Hope this helps ! Best, Roberto -- --------------------------------------------------------------------- Roberto Zini email : fred@strhold.it Strhold Sistemi EDP Reggio Emilia ITALY --------------------------------------------------------------------- "Has anybody around here seen an aircraft carrier?" (Pete "Maverick" Mitchell - Top Gun)