> Hi, > > we have a 6.4_06 ingres installation on Unix HP-D370 serveur. > > We use 3 servers on 3 different databases... Last time one of our > database was entirely locked... > > I didn't know that a database could entirely been locked. > > The ressources of the system are far above the needs so I suspected > that one of our openroad application may have caused such a mess > > Any idea ? Comment ? > > Please answers to f94-bel@nada.kth.se > > Thanks > > Best regards > > Laurent BERTRAND HI Laurent, Yes databases can be locked. This can be done directly by such actions as sql -l , or sql +U or sql +Y Or indirectly, by any of: 1. There are no spare slots available in any server to allow connection to the database 2. The Log Full point may have been reached, in which case no new sessions will be permitted to connect to any database. 3. You are taking a checkpoint turning journaling on/off 4. You are attempting an online checkpoint however there is an active transaction already in existence on the database. Hence any new transactions will stall waiting for the checkpoint to start! Thats a sneaky one! Unfortunatly, you havent reaaly given enough information on this one. Check your errlog.log and see if that can shed light on the situation. Martin Bowes
© William Yuan 2000
Email William