RE: Database accidentally left in backup mode

From: Lange, Kevin G <>
Date: Mon, 15 Mar 2010 16:11:17 -0500
Message-ID: <>

This has happened to ours a few time ( I ran an end backup command on each tablespace.

-----Original Message-----
[] On Behalf Of Janine Sisk Sent: Monday, March 15, 2010 3:15 PM
To: oracle-l L
Subject: Database accidentally left in backup mode

Oracle 11gR2, running on an Amazon CentOS Linux instance.

In order to use Amazon's snapshot feature for backups, I have a nightly script that executes "alter database begin backup", takes the snapshot, and then "alter database end backup". Well, it seems that for reasons unknown, the snapshot process sometimes throws an error (on Amazon's end), and this has resulted in the database being left in backup mode for about a week.

This is not a crisis situation; it's a test copy of a dev database and it's backed up other ways, so I could just scrap it and start over. But I wanted to make this into a learning experience (not to mention a wake up call to make my script a bit more robust), so I decided to make sure I could recover from this.

I checked with the person using the database and they haven't done anything that would add much new data, so I figured this would be easy. However, I ran the "alter database end backup" about an hour ago, and "select file#, status from v$backup" still shows all files in active status, which means they are still in backup mode.

My question is two-fold:
- is it normal for it to take this long, and when should I start to
- is there anywhere else I can look to see what is going on?




This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

Received on Mon Mar 15 2010 - 16:11:17 CDT

Original text of this message