Re: Help: one DB file often becomes unreadable

At a recent SIG meeting a poll of the group indicated that of the 40 or so users of Oracle on NT everyone did cold backups, and half did full exports as a safety measure.

4 different backup packages were named that were supposed to be able to handle hot backups (one was Seagate), and all had given trouble to at least one member of the group usually because of NT file locking collisions - in some cases the backup did not take place, in other cases Oracle suddenly failed because it had been locked out by the backup software.

The reason why this might happen intermittently is that Oracle has various timeout events that cause things like database writes, so it is possibly just a matter of luck as to whether the occasional 'idling' file access from Oracle might take place on specific file just as a backup has locked it out - I can't really make any firmer guess than that.

I would get a list of the error times, and a matching list of the backup times, and take it to Seagate support as reasonable indication that there was a problem for them to address. (Though it would probably be fairly reasonable for them to say it is a problem internal to NT).

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

y0h8797_at_my-deja.com wrote in message <7kj0c6$iu9$1_at_nnrp1.deja.com>...
>Yes. The software is Seagate Backup (or Seagate Backup Exec). Our IT
>support guy is doing incremental backup almost every weekday and full
>back up every weekend both with the database running. I think the backup
>time roughly corresponds to the problem (10pm). So, should I report this
>to Seagate Backup tech support, or is there anything obvious I can do
>first? I'm a new DBA although I've been a regular Oracle user for 2
>years. Thank you.
>
>BTW, I'm pretty sure nobody uses this development database at 10pm. Why
>does the problem occur only once in a while?
Received on Sun Jun 20 1999 - 14:25:59 CDT