RE: Urgent, please: what are my options???

From: Michael Fontana <>
Date: Mon, 26 Jan 2009 12:56:54 -0600 (CST)
Message-ID: <>

Actually, in thinking about this scenario over the weekend, even backups would not have helped if the only copies of the online redo logs were "whacked".

All of the updates not yet committed to disk would be lost, even with a recovery.

Even if you consider your database lost and must rebuild it, this is the best argument for duplexing online redologs in the world. Moving on from here, when this database is recreated (for whatever it's purpose), please be sure to duplex the logs to different devices. This will help address the human error factor as well as physical devices being lost.

-----Original Message-----
From: [] On Behalf Of Guillermo Alan Bort
Sent: Friday, January 23, 2009 6:30 PM
Cc:; Subject: Re: Urgent, please: what are my options???

I seem to remember that it is possible to open a corrupt database, *only* for export. However data corruption may occur. I would suggest, yet again, that you contact Oracle Support, but I'm not certain they will help you. On one hand they don't like to suggest hidden parameters just for the heck of it, and usually first and second level support won't know them well enough, so perhaps you could open the SR with an escalation request.

Other than that, create a test environment and perform *everything* oracle suggests on that environment (thus leaving a backup of the original environment).

Again, why no backups? the only valid reason to have a database without backup is that you can obtain all the information from other sources, if this is the case, you should rebuild the database from other sources instead of messing around with a corrupt db. If CT refused to have backup of a database solely based on cost, then this is what they deserve, and as a DBA I urge you not to solve the issue and let them burn (though I understand it's not always possible).

I know this isn't of much help, but the situation is a rather hopeless one.

I have recovered databases in worse conditions, but data loss was significant, and Functional Analysts spent a *LOT* of time making sure the data was valid (and correcting inconsistencies). (a 'cold' backup taken with db up... luckily it was archivelog on, db was fuzzy nonetheless)

Alan Bort
Oracle Certified Associate

On Fri, Jan 23, 2009 at 7:39 PM, Robert Freeman <> wrote:
> I'm not about to touch this question with a 10 foot pole.
> A google search for things like Oracle force open database might provide
> some help and suggestions.
> If you get it back up, understand that it's inconsistent.... there is no
> assurance that the data is in any state that is usable.
> I have to ask... why no backup?
> Robert G. Freeman
> Author:
> OCP: Oracle Database 11g Administrator Certified Professional Study
> (Sybex)
> Oracle Database 11g New Features (Oracle Press)
> Portable DBA: Oracle (Oracle Press)
> Oracle Database 10g New Features (Oracle Press)
> Oracle9i RMAN Backup and Recovery (Oracle Press)
> Oracle9i New Features (Oracle Press)
> Other various titles out of print now...
> Blog:
> The LDS Church is looking for DBA's. You do have to be a Church member
> good standing. A lot of kind people write me, concerned I may be
> the law by saying you have to be a Church member. It's legal I promise!
> ________________________________
> From: Eugene Pipko <>
> To: "" <>
> Sent: Friday, January 23, 2009 1:31:14 PM
> Subject: Urgent, please: what are my options???
> Hi all,
> I have a 9i on Windows2003 with no backup.
> Database was open while drive where redo logs resided was gone. So I
> all redo logs.
> I shutdown d/b, mounted it, backed up controlfile to trace.
> Recreated control file, but when I try to open resetlogs d/base I
receive an
> error:
> ORA-01194: file 1 needs more recovery to be consistent
> ORA-01110: data file 1: 'D:\ORACLE_SAN\DATA\SYSTEM\REPD_SYSTEM_01.DBF'
> What are my options besides rebuilding d/base???
> Eugene
> P Please consider the environment before printing this e-mail.


Received on Mon Jan 26 2009 - 12:56:54 CST

Original text of this message