Corrupted Redolog file and no backup - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Corrupted Redolog file and no backup

  1. #11
    Join Date
    Jan 2003
    Location
    France
    Posts
    5
    Try :

    ALTER DATABASE RECOVER DATABASE UNTIL CANCEL;
    or
    ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE.

    then

    ALTER DATABASE OPEN RESETLOGS;




    ----
    XD

  2. #12
    Hei,
    It seems that your instance crashed, and your lost redo log is needed by instance recovery.
    In such case, the only solution is restore backup(no matter hot or cold) and do incomplete recovery.
    If you really have no any backup, the only final solution is use undocumented parameter:
    _allow_resetlogs_corruption= true.
    and startup mount database,
    Recover database until cancel
    Cancel
    Alter database open resetlogs.
    Do full exp and rebuild your database.
    Good luck.
    www.cnoug.org

  3. #13
    Join Date
    Feb 2001
    Location
    UAE
    Posts
    304
    I think _allow_resetlogs_corruption is the only solution you have since you have no backups. But it should be used only with Oracle's guidance. If you have Oracle support, then better take their help.

    But if you want to do it on your own, then better take backup of current database, before using this parameter.
    Agasimani
    OCP(10g/9i/8i/8)

  4. #14
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    Quote Originally Posted by DBAtom View Post
    If you end up losing any data from the corruption, I know Soaring Eagle Consulting has a new tool they use to pull data out of corrupted files. I would contact them about it.
    Do you realize this thread was TEN years old?
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  5. #15
    Join Date
    Nov 2000
    Location
    Pittsburgh, PA
    Posts
    4,014
    Quote Originally Posted by PAVB View Post
    Do you realize this thread was TEN years old?
    I don't think that spammer's care. I would not buy from soaring turkey consulting, just because they spam a forum...
    How tacky is that!
    this space intentionally left blank

  6. #16
    Join Date
    Apr 2013
    Posts
    1
    SQL> startup
    ORACLE instance started.

    Total System Global Area 285212672 bytes
    Fixed Size 1218992 bytes
    Variable Size 117442128 bytes
    Database Buffers 163577856 bytes
    Redo Buffers 2973696 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1:
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo01.log'

    shut immediate
    then again create the control file
    SQL> startup nomount
    Create controlfile reuse set database "chaitu"
    MAXINSTANCES 8
    MAXLOGHISTORY 1
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    Datafile
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/system01.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/undotbs01.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/sysaux01.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/users01.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb1.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb2.dbf',
    '/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/tb3.dbf'
    LOGFILE GROUP 1 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo01.log') SIZE 51200K,
    GROUP 2 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo02.log') SIZE 51200K,
    GROUP 3 ('/u01/app/oracle/product/10.2.0/db_1/oradata/chaitu/redo03.log') SIZE 51200K
    RESETLOGS;
    Control file created.
    SQL> alter database mount;
    SQL> alter database open resetlogs;
    try this it will work

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width