RE: Database accidentally left in backup mode

From: Powell, Mark <>
Date: Mon, 15 Mar 2010 20:24:07 +0000
Message-ID: <>


How were the tablspaces put into backup mode? (At the database or tablespace level)

Generate the end backup commands for each tablespace with a file in backup mode and try again to end the backup.

I could suggest you consider switching to rman since it does not require that the tablespaces be placed into backup mode to run a hot backup.

HTH -- Mark D Powell --

-----Original Message-----
From: [] On Behalf Of Janine Sisk Sent: Monday, March 15, 2010 4: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 worry?

  • is there anywhere else I can look to see what is going on?




Received on Mon Mar 15 2010 - 15:24:07 CDT

Original text of this message