Re: User-managed incomplete recovery in noarchivelog mode
- From: sybrandb@xxxxxxxxx
- Date: Mon, 30 Jun 2008 13:28:49 +0200
On Mon, 30 Jun 2008 04:02:31 -0700 (PDT), Helma
<helma.vinke@xxxxxxxxxxx> wrote:
Your only choice is to restore the backup of June 28, pray and forget
about anything that happened after June 28.
If that doesn't work, your database is toast, thanks to the decision
of someone to run in NOARCHIVELOG.
" The tables in USERS tablespace is NOT important, is there any way
for
me to open the database? "
Sybrand,
Can't he use the 29th backup, and drop the USER tablespace ? In that
case, the db should open , i guess. Is that true?
H.
Helma, he could try if he
- restored the db from 29 (including controlfiles)
- MOUNTED the database
- OFFLINED the datafile for the users tablespace
- open the database and drop the users tablespace.
Note: ALL files are from 1 backup!
--
Sybrand Bakker
Senior Oracle DBA
.
- References:
- User-managed incomplete recovery in noarchivelog mode
- From: Woody Ling
- Re: User-managed incomplete recovery in noarchivelog mode
- From: sybrandb
- Re: User-managed incomplete recovery in noarchivelog mode
- From: Helma
- User-managed incomplete recovery in noarchivelog mode
- Prev by Date: Re: User-managed incomplete recovery in noarchivelog mode
- Next by Date: ORA-00959: tablespace '_$deleted$8$0' does not exist
- Previous by thread: Re: User-managed incomplete recovery in noarchivelog mode
- Next by thread: Re: User-managed incomplete recovery in noarchivelog mode
- Index(es):
Relevant Pages
|