Datafile corrupted On standby database

one of the datafile got corrupted in the standby database . when backing up with rman i got ora-15966 error .
i found the corrupted datafile but i did not have any backups to recover .
is there any way to recover the block corruption ?

Hello,
What's your Oracle version? OS? following link shows how to fix it , you can search oracle documentation according to your version.
http://www.mpi-inf.mpg.de/departments/d5/teaching/ss05/is05/oracle/server.920/a96521/repair.htm#11355
Regards

Similar Messages

  • Block corruption on Standby database

    Oracle 10g R2 64bit on Solaris 10 installed on two database server, Sun M5000 and Sun V890
    Primary and physical Standby database is configured with Max performance Async mode, log shipping is ok, archive logs are also applying..
    I opened the standby database on readonly mode, couple of SQLs are running successfully but few SQLS are throwing error meesaage, here is log message -
    SQL> select count(1) from inventory_stock;
    select count(1) from inventory_stock
    ERROR at line 1:
    ORA-01578: ORACLE data block corrupted (file # 12, block # 28109)
    ORA-01110: data file 12: '/backup1/np13/data/invindx01.dbf'
    ORA-26040: Data block was loaded using the NOLOGGING option
    However there is no error meesage recorded in Alert log files related to block corruption. Please suggest

    select file#,UNRECOVERABLE_CHANGE#,UNRECOVERABLE_TIME
    from V$DATAFILE
    where UNRECOVERABLE_TIME is not null
    FILE# UNRECOVERABLE_CHANGE# UNRECOVER
    4 9.7333E+12 12-SEP-10
    5 9.7333E+12 12-SEP-10
    6 9.7333E+12 12-SEP-10
    7 9.7333E+12 12-SEP-10
    9 9.7333E+12 12-SEP-10
    12 9.7333E+12 13-SEP-10
    13 9.7333E+12 13-SEP-10
    14 9.7327E+12 01-SEP-10
    15 9.7333E+12 13-SEP-10
    17 9.7333E+12 13-SEP-10
    22 9.7333E+12 13-SEP-10
    23 9.7333E+12 13-SEP-10
    24 9.7333E+12 13-SEP-10
    32 9.7333E+12 13-SEP-10
    33 9.7333E+12 13-SEP-10
    34 9.7333E+12 13-SEP-10
    35 9.7333E+12 13-SEP-10
    41 9.7324E+12 25-AUG-10
    42 9.7333E+12 13-SEP-10
    43 9.7333E+12 13-SEP-10
    44 9.7333E+12 13-SEP-10
    45 9.7333E+12 13-SEP-10
    57 9.7332E+12 11-SEP-10
    60 9.7333E+12 13-SEP-10
    62 9.7333E+12 12-SEP-10
    63 9.7333E+12 13-SEP-10
    65 9.7333E+12 13-SEP-10
    66 9.7333E+12 13-SEP-10
    68 9.7333E+12 13-SEP-10
    70 9.7333E+12 13-SEP-10
    71 9.7333E+12 12-SEP-10
    73 9.7333E+12 12-SEP-10
    74 9.7333E+12 13-SEP-10
    75 9.7333E+12 12-SEP-10
    77 9.7324E+12 25-AUG-10
    79 9.7333E+12 13-SEP-10
    83 9.7333E+12 13-SEP-10
    84 9.7333E+12 13-SEP-10
    86 9.7333E+12 13-SEP-10
    87 9.7333E+12 12-SEP-10
    89 9.7333E+12 12-SEP-10

  • Add Datafile in Logical Standby Database

    Hi,
    I have add one datafile in our primary RAC DB. We had logical standby database with file management is equal to manual. Both the primary RAC and logical standby db have the different storage structure. When the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";
    Would appreciate if come to know the steps to add the datafile in this kind of environment. and how can i overcome from this problem now except skip transaction for that ddl.
    Thanks in advance.
    Dewan

    When the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";Can you post the error message with the number.
    From Manual..
    8.3.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
    The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
    Add a new tablespace to the primary database:
    SQL> CREATE TABLESPACE new_ts DATAFILE '/disk1/oracle/oradata/payroll/t_db2.dbf'
    2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
    Verify the new datafile was added to the primary database:
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/oradata/payroll/t_db1.dbf
    /disk1/oracle/oradata/payroll/t_db2.dbf
    Perform the following steps to copy the tablespace to a remote standby location:
    Place the new tablespace offline:
    SQL> ALTER TABLESPACE new_ts OFFLINE;
    Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
    % cp /disk1/oracle/oradata/payroll/t_db2.dbf
    /disk1/oracle/oradata/payroll/s2t_db2.dbf
    Place the new tablespace back online:
    SQL> ALTER TABLESPACE new_ts ONLINE;
    Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
    %rcp /disk1/oracle/oradata/payroll/s2t_db2.dbf standby_location
    Archive the current online redo log file on the primary database so it will get transmitted to the standby database:
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    Use the following query to make sure that Redo Apply is running. If the MRP or MRP0 process is returned, Redo Apply is being performed.
    SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
    Verify the datafile was added to the standby database after the archived redo log file was applied to the standby database:
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/oradata/payroll/s2t_db1.dbf
    /disk1/oracle/oradata/payroll/s2t_db2.dbf

  • Add a new datafile to the standby database

    Hi,
    i have a standby database in recovery managed mode.
    Now i must add a new datafile on the production database and i would like
    to know how i realized adding the new datafile on the stanby database.
    is it right when i do the follow steps?
    Before i add a datafile to the primary database,
    cancel the recovery on the standby database.
    -> add the new datafile on the primary database
    after all archived redo logs have been applied, cancel managed recovery:
    alter database recover managed standby database cancel;
    startup nomount
    alter database mount standby database;than
    ALTER DATABASE CREATE DATAFILE '/oracle/DB1/db1_9/data9' as '/oracle/DB1/db1_9/data9';
    alter database recover managed standby database disconnect;Thanks

    8.4.1.1 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to AUTO
    The following example shows the steps required to add a new datafile to the primary and standby databases when the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
    Add a new tablespace to the primary database:
    SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
    2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
    Archive the current redo log so it will get copied to the standby database:
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    Verify that the new datafile was added to the primary database:
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/dbs/t_db1.dbf
    /disk1/oracle/dbs/t_db2.dbf
    Verify that the new datafile was added to the standby database:
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/dbs/s2t_db1.dbf
    /disk1/oracle/dbs/s2t_db2.dbf
    8.4.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
    The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
    Add a new tablespace to the primary database:
    SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
    2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
    Verify that the new datafile was added to the primary database:
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/dbs/t_db1.dbf
    /disk1/oracle/dbs/t_db2.dbf
    Perform the following steps to copy the tablespace to a remote standby location:
    Place the new tablespace offline:
    SQL> ALTER TABLESPACE new_ts OFFLINE;
    Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time that the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
    % cp t_db2.dbf s2t_db2.dbf
    Place the new tablespace back online:
    SQL> ALTER TABLESPACE new_ts ONLINE;
    Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
    %rcp s2t_db2.dbf standby_location
    Archive the current redo log on the primary database so it will get copied to the standby database:
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    Use the following query to make sure that managed recovery is running. If the MRP or MRP0 process is returned, managed recovery is being performed.
    SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
    Verify that the datafile was added to the standby database after the redo log was applied to the standby database.
    SQL> SELECT NAME FROM V$DATAFILE;
    NAME
    /disk1/oracle/dbs/s2t_db1.dbf
    /disk1/oracle/dbs/s2t_db2.dbf
    From Oracle Docs...

  • Add new datafile to logical standby database but not in primary

    Hi,
    Is it ok to add a new datafile to the SYSAUX tablespace on the logical standby database but not on primary? We are running out of disk space on the partition where SYSAUX01.dbf resides so we want to add a new SYSAUX02.dbf in another partition which has space. but this will only be on the logical standby not on primary, there is still lots of space in primary. standby_file_management is MANUAL and this is LOGICAL STANDBY not PHYSICAL.
    Is this possible or where there be any issues?
    Thanks.

    Logical Standby can differ from Primary, it can have extra tablespaces, datafiles, tables, indexes, users ...
    HTH
    Enrique

  • Add temporary datafiles after creating standby database

    I used data guard manager to create standby database and it went fine. Before finish, system pop up a window and says,
    "The data guard configuration has been created in a disabled state. It must be enabled using the Enable option in the configuration menu. Pior to ebaling the configuration, please verify the following:
    The Primary database contains temporary datafiles. The files will not be duplicated in the new standby database. You must manually recreate the temporary files on the standby node by adding them to their respective tablespaces in the standby database after creation process in complete."
    The problem is, in the standby database, how do I add tempfile without open the standby database? the documentation is very unclear...

    Thanks for the reply and the useful link. I had followed the instructions when creating the standby database, although under database options there is a difference between the OEM version we are using and the version shown, whereby the 'RMAN backup location' option has been replaced with 'working directory location'.
    Just found the following and am guessing this is the issue.
    NFS mounts established within a zone are local to that zone. The mounts cannot be accessed from other zones, including the global zone.
    I suspect I will need to copy the backup pieces onto the local server in order to create the standby database using OEM. Not something I was expecting to have to do as copying will take a long time due to the size of the backup, but unless anyone else can shed any light on the reason for the initial error
    RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
    then I guess this is the only way forward.
    Regards,
    JP

  • Data block corrupted on standby database (logical corruption)

    Hi all,
    we are getting the below error on our DRSITE,it is MANUAL PHYSCIAL STANDBY DATABSE...
    The following error has occurred:
    ORA-01578: ORACLE data block corrupted (file # 3, block # 3236947)
    ORA-01110: data file 3: '/bkp/oradata/orcl_raw_cadata01'
    ORA-26040: Data block was loaded using the NOLOGGING option
    I have checked in the Primary database, that there are some object which are not being logged into the redo logfiles.....
    SQL> select table_name,INDEX_NAME,logging from dba_indexes where logging='NO'
    TABLE_NAME INDEX_NAME LOG
    MENU_MENUS NUX_MENU_MENUS_01 NO
    MENU_USER_MENUS MENU_USER_MENUS_X NO
    OM_CITY IDM_OM_CITY_CITY_NAME NO
    OM_EMPLOYER                    EMPLR_CODE_PK                  NO
    OM_EMPLOYER                    IDM_EMPLR_EMPLR_NAME           NOOM_STUDENT_HEAD OM_STUDENT_HEAD_HEAD_UK01 NO
    OT_DAK_ENTRY_DETL DED_SYS_ID_PK NO
    OT_DAK_ENTRY_HEAD DEH_SYS_ID_PK NO
    OT_DAK_ENTRY_HEAD IDM_DEH_DT_APPL_REGION NO
    OT_DAK_ENTRY_HEAD IDM_DEH_REGION_CODE NO
    OT_DAK_REFUNDS_DETL DRD_SYS_ID_PK NO
    TABLE_NAME INDEX_NAME LOG
    OT_MEM_FEE_COL_DETL IDM_MFCD_MFCH_SYS_ID NO
    OM_STUDENT_HEAD IDM_STUD_COURSE NO
    13 rows selected.
    so the main problem is in the OM_EMPOYER tables if i would delete the indexes from that table recreate it again with the logging clause,and then apply the archvied logs to the DRSITE.WILL THE problem will resolve.
    Pls suggest me...

    Hi..
    Firstly how did you confirm that it was that index only.Can you post the output of
    SELECT tablespace_name, segment_type, owner, segment_name
    FROM dba_extents WHERE file_id = 3 and 3236947 between block_id
    AND block_id + blocks - 1;
    This query can take time, if are sure that its the index don't fire this command .
    Secondly, when you will drop and recreate the index, it will be logged into the redo logfile.This information will be be logged in to an the archivelog file as its the replica of the redo logfile. Then when you apply this archive log maually, it will drop that index and then recreate it using the same sql.
    HTH
    Anand

  • Relocating datafiles on standby database after mount point on stanby is ful

    Hi,
    We have a physical standby database.
    The location of datafiles on primary database are at /oracle/oradata/ and the location of datafiles on standby database are at /oracle/oradata/
    Now we are facing a situation of mount mount getting full on standby database so we need to move some tablespaces to another location on standby.
    Say old location is /oracle/oradata/ and new location is /oradata_new/ and the tablespaces to be relocated are say tab1 and tab2.
    Can anybody tell me whether following steps are correct.
    1. Stop managed recovery on standby database
    alter database recover managed standby database cancel;
    2. Shutdown standby database
    shutdown immediate;
    3. Open standby database in mount stage
    startup mount;
    4. Copy the datafiles to new location say /oradata_new/ using os level command
    4. Rename the datafile
    alter database rename file
    '/oracle/oradata/tab1.123451.dbf', '/oracle/oradata/tab1.123452.dbf','/oracle/oradata/tab2.123451.dbf',''/oracle/oradata/tab2.123452.dbf'
    to '/oradata_new/tab1.123451.dbf', '/oradata_new/tab1.123452.dbf','/oradata_new/tab2.123451.dbf',''/oradata_new/tab2.123452.dbf';
    5. Edit the parameter db_file_name_convert
    alter system set db_file_name_convert='/oracle/oradata/tab1','/oradata_new/tab1','/oracle/oradata/tab2','/oradata_new/tab2'
    6. Start a managed recovery on standby database
    alter database recover managed standby database disconnect from session;
    I am littelbit confused in step 5 as we want to relocate only two tablespaces and not all tablespaces so we have used.
    Can we use db_file_name_convert like this i.e. does this work for only two tablespaces tab1 and tab2.
    Thanks & Regards
    GirishA

    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010428
    8.3.4 Renaming a Datafile in the Primary Database
    When you rename one or more datafiles in the primary database, the change is not propagated to the standby database. Therefore, if you want to rename the same datafiles on the standby database, you must manually make the equivalent modifications on the standby database because the modifications are not performed automatically, even if the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
    The following steps describe how to rename a datafile in the primary database and manually propagate the changes to the standby database.
    To rename the datafile in the primary database, take the tablespace offline:
    SQL> ALTER TABLESPACE tbs_4 OFFLINE;
    Exit from the SQL prompt and issue an operating system command, such as the following UNIX mv command, to rename the datafile on the primary system:
    % mv /disk1/oracle/oradata/payroll/tbs_4.dbf
    /disk1/oracle/oradata/payroll/tbs_x.dbf
    Rename the datafile in the primary database and bring the tablespace back online:
    SQL> ALTER TABLESPACE tbs_4 RENAME DATAFILE 2> '/disk1/oracle/oradata/payroll/tbs_4.dbf'
    3> TO '/disk1/oracle/oradata/payroll/tbs_x.dbf';
    SQL> ALTER TABLESPACE tbs_4 ONLINE;
    Connect to the standby database, query the V$ARCHIVED_LOG view to verify all of the archived redo log files are applied, and then stop Redo Apply:
    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# APP
    8 YES
    9 YES
    10 YES
    11 YES
    4 rows selected.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Shut down the standby database:
    SQL> SHUTDOWN;
    Rename the datafile at the standby site using an operating system command, such as the UNIX mv command:
    % mv /disk1/oracle/oradata/payroll/tbs_4.dbf /disk1/oracle/oradata/payroll/tbs_x.dbf
    Start and mount the standby database:
    SQL> STARTUP MOUNT;
    Rename the datafile in the standby control file. Note that the STANDBY_FILE_MANAGEMENT initialization parameter must be set to MANUAL.
    SQL> ALTER DATABASE RENAME FILE '/disk1/oracle/oradata/payroll/tbs_4.dbf'
    2> TO '/disk1/oracle/oradata/payroll/tbs_x.dbf';
    On the standby database, restart Redo Apply:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
    2> DISCONNECT FROM SESSION;
    If you do not rename the corresponding datafile at the standby system, and then try to refresh the standby database control file, the standby database will attempt to use the renamed datafile, but it will not find it. Consequently, you will see error messages similar to the following in the alert log:
    ORA-00283: recovery session canceled due to errors
    ORA-01157: cannot identify/lock datafile 4 - see DBWR trace file
    ORA-01110: datafile 4: '/Disk1/oracle/oradata/payroll/tbs_x.dbf'

  • Standby Database Datafile Move

    Hi All
    Oracle v10g (10.2.0.4)
    Windows 2003
    I need to move some datafiles onto a larger volume on our primary database. I have no issue with this task, except for some uncertainty on what to do with the Standby database?
    Our Standby database (on the other side of the atlantic) has the exact same drive/file layout as the primary. I have a larger volume ready for the move on the Standby.
    We have standby_file_management set to auto.
    I assume that the data dictionary/control file information (datafile locations) will be updated via the logs being shipped? I assume I would need to manually move the files on the standby database?
    Has anyone practiced this recently? could you give me a little guidance.
    Much appreciated.

    user3655049 wrote:
    Hi All
    Oracle v10g (10.2.0.4)
    Windows 2003
    I need to move some datafiles onto a larger volume on our primary database. I have no issue with this task, except for some uncertainty on what to do with the Standby database?
    Our Standby database (on the other side of the atlantic) has the exact same drive/file layout as the primary. I have a larger volume ready for the move on the Standby.
    We have standby_file_management set to auto.
    I assume that the data dictionary/control file information (datafile locations) will be updated via the logs being shipped? I assume I would need to manually move the files on the standby database?
    Has anyone practiced this recently? could you give me a little guidance.
    Much appreciated.You no need to modify datafile locations on standby. structure can be different from primary and standby. Even primary can be ASM and standby can be non-ASM.
    So no need to worry. But after changing the files location, you have to update DB_FILE_NAME_CONVERT parameter on databases.
    Some more information to you, check this http://docs.oracle.com/cd/E11882_01/server.112/e17022/manage_ps.htm#i1034172
    >
    When you rename one or more datafiles in the primary database, the change is not propagated to the standby database. Therefore, if you want to rename the same datafiles on the standby database, you must manually make the equivalent modifications on the standby database because the modifications are not performed automatically, even if the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
    >
    Edited by: CKPT on Jan 17, 2013 9:02 PM

  • Creating standby database using data guard.

    Current Env:
    Oracle 11.2.0.1
    ASM
    Size 1.7T and growing.
    I'm rebuilding a standby database and need to use rman because of a few factors. In the past, I did a file copy create a standby control file config init.ora and it always worked.
    We have a database and had the stanby build; but someone issued a flashback and corrupted the standby database.
    Because of the size 1.7T and growing and we are now using ASM.
    My research is only showing building standby through rman using dupicate database command.
    I would like to copy the cold backup to a external drive and ship it to the standby site where I'll do the restore. This is because of time and bandwith required to rebuild the standby will interfere with operaitions for the period the files are being copied.
    So what would be the high level steps.
    1) get the cold backup
    2) create the standby control file
    3) ship the data via corrier
    4) restore the database
    5) and this is where i'm not sure. recover the standby control file - but during the restore of the database the "normal" control file will open and perhaps do a checkpoint. therefore the standby controlfile will be usless.
    6) recover the standby database.
    Has anyone accomplished this?
    As much specifics will be helpful. This system is operational and needs to be done right the first time.
    thanks,
    -Rob

    Thank you.
    1) I'm going to off load the cold backup to an external drive and have a courier take it to the DR site.
    Why, we are replicating the SAN over to the DR site. When SAN replication backs up Oracle becomes non-responsive. Therefore; sending the data over the pipe is not an option for the standby rebuild. Yea' that's the easy way to do it. But this system is operational and critical to operations; so we will not risk saturating the pipe for any period of time. The pipe got saturated one time and it was not pretty.
    2) I'm running the test in my lab to make sure I can create the standby database using the cold backup and rman.
    3) In the past it was easy; I got a cold backup of the data files using the same ksh scripts that have been working for 20 years. Copy the files over to the standby site, and put it into managed recovery. This technique has been working fine sense Oracle 8i days. ASM through a huge monkey wrench in the ksh script backup and now I'm forced to use rman. Hey, I'm told it's an okay product but when it comes to backups I never get fancy; that just makes things more complicated. Okay I wont complain about asm anymore, i guess there is an advantage in there somewhere.
    -Rob

  • Standby database datafile corruption.

    Hi:
    I am getting the following errors on my standby db. Could u please tell me how to handle the situation. I am skeptical to try out any thing as this might end up in datafile corruption. Please advice..
    MRP0: Background Media Recovery terminated with error 1237
    Fri Nov 30 09:15:25 2007
    Errors in file /u01/prod/oraprod/proddb/9.2.0/admin/PROD_hunter/bdump/prod2_mrp0_19630.trc:
    ORA-01237: cannot extend datafile 392
    ORA-01110: data file 392: '/u03/prod/oraprod/proddata/a_txn_data01.dbf'
    ORA-19502: write error on file "/u03/prod/oraprod/proddata/a_txn_data01.dbf", blockno 424577 (blocksize=8192)
    ORA-27072: skgfdisp: I/O error
    Linux Error: 4: Interrupted system call
    Additional information: 424576
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    MRP0: Background Media Recovery process shutdown
    ---------------------------------------------------------------------------------------------------------------------

    Check this error,
    ORA-01237: cannot extend datafile string
    Cause: An operating system error occurred during the resize.
    Action: Fix the cause of the operating system error and retry the command.
    Is there any DDL statement in your primary to resize datafile ? Do you have enough space on standby server?

  • StandBy Database goes Corrupt

    Hi,
    I'm new to Data Guard tech. I've installed Oracle 10g Data Guard on Solaris platform.
    However, while doing some operation i noticed that the control file of the StandBy db has been corrupted, soon after i took its backup (By Renaming it) and create new Control file from Primary DB and placed at same location with same name.
    As i restarted the Standby Db - it gave me an error of Datafile old and i got it as the SCN number has been changed with respect to new control file and Datafile.
    Currently, there is nothing in the DB's and both (Primary and Standby DB) are blank and will go in production after some days.
    Now, my Query is how to make them synchronize - how to make my StandBy Db in working condition???
    Note: >> If required, I can Shutdown Primary DB.
    >> Db is running in Archive Log mode but it got corrupted long back and i dont know the exact date of its corruption.
    While Surfing, i got at some site that:
    Create StandBy control file from Primary DB and place it at StandBy DB.
    Place all Datafiles and index and Redo log files form primary to StandBy DB And then try to start. Now please suggest - Will these steps make my StanDby Db working - Else Plz provide me the correct stpes ot make my StandBy Db working.
    PS: Both my DBs are empty currently.
    Thanks a lot for your help.

    mate I suggest that you do a number of different things.
    one is shut down the database and copy all the files to the standby database location,
    startup mount the production database and create the standby control file
    alter database create standby controlfile ' location /standby.ctl';then copy it to the location of the control files in your standby database. then delete all the control file there. and copy the standby in control01.ctl control02.ctl and control03.ctl
    the startup no mount your standby,
    alter database mount standby database; then get your connectivity to your production working by doing a conn to each database from the other one, ie. from the sql prompt on the production , connect to the standby,from the sql prompt on the standby connect to the production etc.
    if that is fine then on the production database at the prompt
    open it up
    alter database openon the standby database .
    alter database recover managed standby database disconnect from session;and it should go.

  • Datafile issues in manual standby database

    Hi all,
    oracle - 10gR2
    OS - RHEL 2.6
    We have primary and standby database setup using manual methods('rsync') to send archive logs from primary to standby database and they are applied there. Today I have created a new datafile in primary and seen that the same is not replicated in standby( i was not aware of the functionality of this kind of setup) later I have seen that "standby_file_management parameter is set to MANUAL".
    I have seen the following message in standby alert log(not disabled the archive log application script in satndby),
    "Media Recovery Log /u01/app/oracle/oradata/bmprod/archivelog/1_1761_703415336.arc
    File #6 added to control file as 'UNNAMED00006' because
    the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
    The file should be manually created to continue.
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail"
    Later I have copied the required file from primary to standby database(now I have disabled the archive log application script in standby), and renamed the datafile 'UNNAMED00006' to 'desired one' and restarted the archive log application script. I have seen the following messages,
    "ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 6 needs more recovery to be consistent
    ORA-01110: data file 6: '/u02/app/oracle/oradata/bmprod/BMTEST.dbf'"
    Now I am unable to figure out what I should do to come out of this situation. Atleast tell me this condition is not worse than I thought(I think that the standby database should be recreated).
    Any help is appreciated.......
    regards
    Edited by: techfeud on Jan 18, 2010 11:26 PM

    Hi,
    when you set the standby_file_management parameter as mannual then , if you create any datafile or adding it to the tablespace then you should mannaully run the command on the standby side , if its auto then auto matically it will create the file over in the respective locationa and with the name what you have used to create the datafile on the primary side,
    as the parameter value is mannual ypu need to create the datafile over the standby side and then performt the recovery,
    Farhan.

  • The password file is getting corrupted after rebooting the standby database

    Hi,
    The password file is getting corrupted after rebooting the standby database.
    Since the databases are not in sync, I had to copy the pwfile from primary to standby to make 'em sync.
    (BUT.... the pwfile is not getting corrupted every time I reboot the standby by)
    Could somebody please explain the reason for the pwfile on the standby database getting corrupted while rebooting ?
    Env: Oracle 11g on Windows 7
    Thanks in advance

    Moderator Action:
    This thread was originally posted to the Oracle/Sun Servers HARDWARE forum.
    This is definitely not an issue related to any hardware components.
    ... it's now moved to Database General Questions, hopefully for closer topic alignment.

  • DBV-0200,block already marked corrupted on physical standby database

    Dear all,
    we are facing the problem of *'DBV-200 that is block already marked corupted on standby database'* on all index datafile, we facing this error in oracle 10.2.0.3 version of database when we are running dbv utility.
    but this error can't found on our production database. It is only on standby database.
    We canot find the root cause of this error so any body tell me the cause and solution on this.
    Thanks
    Kiran Rane.

    Hi Ravi,
    i checked all indexes on our primary database some indexes is in logging mode and more than half indexes is in nologging mode but i have some doubt about index logging and nologging mode,
    when our primary database is running on 9.2.0.8 version of database this kind of error not observe but after upgrading to 10.2.0.3 version of database we are getting this kind of error so if this version having some bugs or for avoiding this error any patch is available. so tell me what is the exact reason behind this error.
    Thanks
    Kiran Rane.

Maybe you are looking for