If you have a disk backup, you can restore that. But you will lose all
transactions since the backup.

If you don't, or if the disk backup version of the db doesn't work, you
can call consulting, and spend $15K. You might get something, you might
not, as no doubt oracle will be sure to explain.  But that is it, I think.

There is a cost to having insurance, and a cost to not having it.
Sometimes one is cheaper than the other. Sometimes not. Wish I could help
more, but you are in a pickle, as it were.

        --Dean

On Sun, 27 Jul 2003, Rick Perron wrote:

> Here's the short question:
> Does anyone have any experience or recommendations for recovering data
> from an Oracle database that was running in NOARCHIVE mode while it was
> backed up?
>
> Oracle's standard support service is unable to help me.  Which is
> understandable since this is something they are quite clear about not
> supporting.  They tried, but just can't do anything for me.  They have
> said that there is an expensive option.  They do offer a data recovery
> service through their consulting.  Does anyone have any experience with
> that?
> Does anyone know of other companies that provide that type of service?
> ActionFront appears to be one.  Has anyone here dealt with them?
> http://www.actionfront.com/os_sql.asp
>
> Here's the long story:
>
> I knew what I was doing when I set this database up.  (Honest,  I really
> did)  We setup this database to store a recent copy of production data
> to be queried for reporting.  Based on that assumption, all of the data
> was reproducible, and based on that assumption we didn't need backups.
> If we ever had a system crash, we could always just build a new database
> and copy the production data over and we were up and running again.
> Great plan.  Oh, if only it were that simple.
>
> So I went about setting up the database and ran it in NOARCHIVE mode.
> For those of you that don't know, running an Oracle database in
> NOARCHIVE mode means you can't back the database up while it is
> running.  However, it uses less diskspace.  Which is great, when your
> management refuses to buy disk space.  Especially when they find out you
> can do things like this.  Which just means more work for the DBA when it
> comes to restoring things, but no money spent right now.  Great plan.
> Oh, if only it were that simple.
>
> Somewhere along the way, a business user that had access to this
> database was granted the CREATE TABLE privilege  This is great, she
> thought.  What a convenient place to store all my data.  Well, it would
> be a great place to store her data, if it wasn't the only copy of that
> data OR if it wasn't all that important.  Great plan.  Oh, if only it
> were that simple.
>
> Well, if only she knew what I knew.  Or of I knew what she knew.  Well,
> obviously you can guess that wasn't the case.  Because, I knew that that
> database was unrecoverable if the system crashed; and she knew that data
> was unrecoverable if that database disappeared.  And, as you can guess
> by know, Mr. Murphy paid us a visit and we are in the predicament that
> we are in now.  And management says, find a way to get that data back
> and do it!  Great plan.  Oh, if only it were that simple.
>
>
>
>
> ---
> Send mail for the `bblisa' mailing list to [EMAIL PROTECTED]'.
> Mail administrative requests to [EMAIL PROTECTED]'.
>


---
Send mail for the `bblisa' mailing list to [EMAIL PROTECTED]'.
Mail administrative requests to [EMAIL PROTECTED]'.

Reply via email to