Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Redo logs lost, old backups

Re: Redo logs lost, old backups

From: Joan Hsieh <joan.hsieh_at_tufts.edu>
Date: Wed, 19 Dec 2001 08:24:40 -0800
Message-ID: <F001.003E032A.20011219081528@fatcity.com>

Hi Maser,

I am not sure this work or not. Actually my suggestion is call oracle support before you do anything. Just for your reference.

  1. BACKUP the current situation with the database closed.

        The instructions here are destructive. You are STRONGLY advised to

        backup the current situation before proceeding. If you do NOT do this

        you may lose the chance to try other options.

   2) If your datafiles are from different points in time it is best to

        try to use system tablespace files at a similar timestamp to the

        OLDEST files you have online in the database. This reduces the chance

        that you will get problems during the bootstrap phase of opening the

        database.

   3) Edit your initSID.ora file and set:

                _ALLOW_RESETLOGS_CORRUPTION = TRUE
                _CORRUPTED_ROLLBACK_SEGMENTS = list of all rollback
segments

        Comment out any 'ROLLBACK_SEGMENTS= ' clause.

   4) Invoke either server manager (svrmgrl) or SQL*DBA and issue

        the commands below:

> connect internal
> startup mount
> select * from v$datafile;

        ...
        Check here that all files you want to open with are listed as
ONLINE
        (or as SYSTEM).
        If not: ALTER DATABASE DATAFILE 'full_path_to_file' ONLINE;
until
        all required files are listed as online.
        ...

> RECOVER DATABASE UNTIL CANCEL;
or
> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
At the prompt enter the word: Cancel
> ALTER DATABASE OPEN RESETLOGS;

   5) If this works you should attempt to export the database IMMEDIATELY.
        Once you have an export the database must be recreated from scratch.

        This means dropping and deleting ALL datafiles and creating a
        new database from scratch.

        A database which has been opened in this way, but not rebuilt
will
        not be supported by Oracle. Any delay in extracting the
contents,
        or any attempt to use the system may cause irreparable
damage.

  NOTE: Be sure to remove the init.ora parameters added in step 3 otherwise

        you may accidentally corrupt any new database created using the same

        init.ora file.

   6) It is possible that the OPEN RESETLOGS may fail with an error,

      or that accessing the data (eg: using export) may fail with an error.

      In this case note down the exact error and identify any trace files

      produced then contact Oracle Support Services with this information.

      Depending on the errors it may be possible to proceed further.

Joan


>                            Name: arsqaALRT.LOG
>    arsqaALRT.LOG           Type: Text Document

"Maser, Donna (SEA)" wrote:

> 
> HELP!  I got hit with something or someone today and all the redologs for 2
> of my production databases disappeared.  I have no idea how, and will leave
> it to the SysAdmin
> to figure out what happened and how to prevent it from happening again.  I
> am not in archivelog mode and normally take nightly cold backups.  If at all
> possible, I need to recover these databases.  The other problem is that my
> backup script was broken and (during my absence, I should never have taken a
> 2 week honeymoon!) no backups were taken.
> So, I'm working with 2 week old cold backup, and wondered if anyone knows a
> way (unsupported, of course) to recover the tablespaces that hold data with
> the old system datafile?
> I have tried all methods of recovery I could come up with to get the
> database to start without the logfiles, (using "recover ... using backup
> controlfile", rebuilding controlfile) ... but always end up with a message
> that the system tablespace needs media recovery.
> 
> I took a cold backup of the mess before I started tinkering with it, and I'm
> willing to try anything.  Any ideas?
> 
> The information contained in this email is intended for the
> personal and confidential use of the addressee only. It may
> also be privileged information. If you are not the intended
> recipient then you are hereby notified that you have received
> this document in error and that any review, distribution or
> copying of this document is strictly prohibited. If you have
> received  this communication in error, please notify Celltech
> Group immediately on:
> 
> +44 (0)1753 534655, or email 'is_at_celltech.co.uk'
> 
> Celltech Group plc
> 216 Bath Road, Slough, SL1 4EN, Berkshire, UK
> 
> Registered Office as above. Registered in England No. 2159282
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Maser, Donna  (SEA)
>   INET: Donna.Maser_at_sea.celltechgroup.com
> 
> Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
> San Diego, California        -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from).  You may
> also send the HELP command for other information (like subscribing).
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Joan Hsieh
  INET: joan.hsieh_at_tufts.edu

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
Received on Wed Dec 19 2001 - 10:24:40 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US