Has anyone ever run into a problem where the UNDO.Dat file disappears?
I've scripted a Transaction Log restore with standby to a server. The restore works fine until, after a couple of days, BANG, the Undo.Dat file that the "With Standby" is pointing to suddenly disappears. Then the job fails until I do a manual restore of one transaction log to recreate the UNDO.Dat file.
The user in control of this machine swears he hasn't touched the file or attempted to delete it. In fact, he claims to have been nowhere near the share name, only using Enterprise Manager to look at the database.
Does anyone know of anyway this file could disappear or be deleted without deliberately choosing it and clicking delete? Has anyone ever had this problem before?
Thanks!
Catadmin - MCDBA, MCSA
"Just because I'm paranoid doesn't mean the universe *isn't* out to get me!"
I've scripted a Transaction Log restore with standby to a server. The restore works fine until, after a couple of days, BANG, the Undo.Dat file that the "With Standby" is pointing to suddenly disappears. Then the job fails until I do a manual restore of one transaction log to recreate the UNDO.Dat file.
The user in control of this machine swears he hasn't touched the file or attempted to delete it. In fact, he claims to have been nowhere near the share name, only using Enterprise Manager to look at the database.
Does anyone know of anyway this file could disappear or be deleted without deliberately choosing it and clicking delete? Has anyone ever had this problem before?
Thanks!
Catadmin - MCDBA, MCSA
"Just because I'm paranoid doesn't mean the universe *isn't* out to get me!"