This discussion is archived
7 Replies Latest reply: Feb 11, 2013 9:45 PM by Fayn_dba RSS

UNNAMED00044

Fayn_dba Newbie
Currently Being Moderated
Hi experts;

I am getting an error from standby database

alter database recover managed standby database disconnect;
Database altered.

but alert log shows
name for data file 44 is unknown - rename to correct file
ORA-01110: data file 44: '/u02/app/oracle/product/11.1.0/db_1/dbs/UNNAMED00044'
Errors in file /u02/app/oracle/diag/rdbms/orcl_sb/orcl/trace/orcl_mrp0_10335.trc:
ORA-01111: name for data file 44 is unknown - rename to correct file
ORA-01110: data file 44: '/u02/app/oracle/product/11.1.0/db_1/dbs/UNNAMED00044'
MRP0: Background Media Recovery process shutdown (orcl)
Completed: alter database recover managed standby database disconnect

Actually my assistant added a datafile but & after that when i came back it alert show that Standby is unsynchoronized

In production db i have make this datafile offline & when I alter it it says media recovery is needed for datafile 44

Please help regards
  • 1. Re: UNNAMED00044
    Richard Harrison . Expert
    Currently Being Moderated
    Hi,
    Recover the datafile on the production db and rename the file in the standby db ( using alter database command) It should then sort itself out.

    Cheers,
    Harry
  • 2. Re: UNNAMED00044
    Shivananda Rao Guru
    Currently Being Moderated
    Hello,

    Please refer this http://shivanandarao.wordpress.com/2012/04/02/managed-recovery-process-mrp-terminates-on-standby-database-upon-adding-datafile-on-the-primary-database/

    Hope it helps !!

    Regards,
    Shivananda
  • 3. Re: UNNAMED00044
    Victor Armbrust Oracle ACE
    Currently Being Moderated
    Also don't forget to use standby_file_management='AUTO' in your Standby database. This will help you out with new datafiles names and in case of changes on PRIMARY database

    Victor
  • 4. Re: UNNAMED00044
    Chanchal Wankhade Journeyer
    Currently Being Moderated
    Hi,

    Basic reason for this you have not set correct parameter on primary database. you need to set STANDBY_FILE_MANAGEMENT='AUTO' parameter on primary database so whenever you made the changes in primary database like addition of the datafile modificatio of data file etc that time all the changes will automatically reflect to standby database.

    If you omit this parameter then you would everytime need to recover that file and vice versa.

    Better you modify that parameter.
  • 5. Re: UNNAMED00044
    Mihael Pro
    Currently Being Moderated
    Basic reason for this you have not set correct parameter on primary database. you need to set STANDBY_FILE_MANAGEMENT='AUTO' parameter on primary database
    on standby :)
  • 6. Re: UNNAMED00044
    Chanchal Wankhade Journeyer
    Currently Being Moderated
    Hi,

    Ya agree with you. I should have specified both the database in case of switch over switch back this parameter will required on both the database.
  • 7. Re: UNNAMED00044
    Fayn_dba Newbie
    Currently Being Moderated
    Hi experts;

    You guys are great. I have resolved the issue by

    Setting the Standby Database to

    1. standby_file_management='MANUAL'

    2. Rename the file in Standby >> alter database create datafile ‘/u02/app/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00044′ as '/u02/app/oracle/oradata/orcl/users15.dbf'

    3. Again setting >> standby_file_management='AUTO'

    Logs started reporting that standby is in Sync

    After doing all this I recovered the datafile# 44 through RMAN ( from this link http://www.orafaq.com/node/2395)

    The Data Recovery Advisor tool can assist with diagnosing media failures, making recommendations and providing the RMAN commands to resolve the problem;

    1.List failure
    2.Advice failure
    3.Repair failure

    Issued the following commands on Primary

    select file#,status from v$datafile;

    FILE# STATUS
    ---------- -------
    1 SYSTEM
    6 ONLINE
    44 RECOVER
    set oracle_sid=orcl
    Connect to RMAN >> rman target /
    RMAN> list failure;
    List of Database Failures
    =========================

    Failure ID Priority Status Time Detected Summary
    ---------- -------- --------- ------------- -------
    44 HIGH OPEN 11-FEB-13 one or more non-system datafiles are corrupt

    RMAN> advise failure;

    List of Database Failures
    =========================

    Failure ID Priority Status Time Detected Summary
    ---------- -------- --------- ------------- -------
    44 HIGH OPEN 19-MAY-10 One or more non-system datafiles are corrupt

    analyzing automatic repair options; this may take some time
    using channel ORA_DISK_1
    analyzing automatic repair options complete

    Mandatory Manual Actions
    ========================
    no manual actions available

    Automated Repair Options
    ========================
    Option Repair Description
    ------ ------------------
    1 Restore and recover datafile 7
    Strategy: The repair includes complete media recovery with no data loss
    Repair script: d:\oracle\app\diag\rdbms\che\che\hm\reco_948713839.hm

    RMAN> repair failure;

    Strategy: The repair includes complete media recovery with no data loss
    Repair script: /u02/app/oracle/diag/rdbms/orcl/orcl/hm/reco_948713839.hm

    contents of repair script:
    # restore and recover datafile
    sql 'alter database datafile 44 offline';
    restore datafile 44;
    recover datafile 44;
    sql 'alter database datafile 44 online';

    Do you really want to execute the above repair (enter YES or NO)? yes
    executing repair script

    sql statement: alter database datafile 44 offline

    Starting restore at 11-FEB-10
    using channel ORA_DISK_1

    .......
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
    Finished restore at 11-FEB-10

    Starting recover at 11-FEB-10
    using channel ORA_DISK_1

    starting media recovery
    ........Continues


    sql statement: alter database datafile 44 online
    repair failure complete

    5. Verify the database

    SQL> select file#,error,time from v$recover_file;

    no rows selected

    SQL> select file#,status from v$datafile;

    FILE# STATUS
    ---------- -------
    1 SYSTEM
    3 ONLINE
    44 ONLINE


    Warm Regards

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points