> >--------
> > Error while trying to write to file
> > The process cannot access the file because another process has
> >locked a portion of the file.
> >
> >internal gds software consistency check (error during savepoint backout
> >(290))
> >----------
> >
> My comment on this is that they haven't looked hard enough. It's an
> absolutely typical log message that you get when someone is trying to log
> in while a zip or other file-level copying process is going on.
99.99% sure that no other process is/was accessing the file
> Another place worth a look is where someone is using an external tool to
> access and copy the database. If their security isn't good enough, it
> could be happening from anywhere on their network
This is (hopefully) the most secure network in the UK, so if it is a security
problem, they have more things to worry about than a bit of DB corruption <g>
> OTOH, it could be something much more local, like the early throes of
> hard-drive death...
Could it also be down to a lack of disk space?
Phil
--
Linux 2.4.4-4GB
8:31am up 21 days, 19:33, 1 user, load average: 0.47, 0.16, 0.04