We are experiencing an odd problem with a database load which we are
wondering has been encountered before by anybody out there ...
Progress v 6.3F01
AT&T Unix SVR4 2.3.1
AT&T 3550 2 x i486 50Mhz
1 Gb Memory
The database is a 2.5 Gig Multi-Volume DB and the load is running as a series
of 6 background sessions running concurrently loading from ascii dumps on
disk. Session 1 is loading all files sequentially except for a very large
transaction file, the remaining 5 are each loading a section of this
transaction file. We also have 2 APW's 1 BIW and a WDOG running and the server
is started with no-integrity.
The load proceeds well for 30-40 minutes then *all* activity stops entirely.
The processes still exist (sleeping) and the clients show up in promon. The
activity screen shows that absolutely nothing is happening at all even after
several minutes - a few checkpoints had occurred earlier but nothing as
drastic as this.
sar showed that when the db goes to sleep the machine is twiddling it's thumbs
i.e. no swapping, cpus' 98% idle, no wait for i/o, low usr/sys time, the disks
are effectively doing nothing as well .... no errors on the console and
everything else looking and acting normal BTW we are the only users's on this
The database log file shows nothing untoward either.
Looking at the promon User Control screen showed that all self service clients
were waiting on a TXE transaction commit lock except 1 which was waiting for
BKEX exclusive lock on a db buffer ...
Has anyone any ideas on why this 'blockage' appeared after 30-40 mins and how
it can be cleared or prevented ....? We saved the promon snapshots if anyone
needs more information.
All advice/tips/pointers are gratefully received.
AT&T GIS European Deployment Centre
Tel: +33 22.214.171.124
Fax: +33 126.96.36.199
When all you have is a hammer, everything looks like a nail