File missing in standby database

Hi all,
We have a oracle 9.2 database on sun solaris box.....
Oor Standby DB went down in the month of April and i have taken all the backups of datafile to DAT drive but one of the datafile is missing so we are not able to open the db in read only mode.......
can anubody suggest me how to recover the datafile
as we are also not having any rman backup......

But when we are mounting our DB it is asking to apply the logs from 19 march 09 onwards Are you sure that DB is asking for archives to mount the database?
so if we would take our DB is in the backup mode then that tablespace might have different SCN as compare to the controlfile so will we be able to ioen the DB in readonly mode or not.That is why we are putting the database in recovery mode (to synchronize the database files). Are all archives available?
Regards,
S.K.

Similar Messages

  • Archived log missed in standby database

    Hi,
    OS; Windows 2003 server
    Oracle: 10.2.0.4
    Data Guard: Max Performance
    Dataguard missed some of the archivelog files and but latest log files are applying. standby database is not in sync with primary.
    SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
    I queried above command and I found some files are missed in standby.
    select status, type, database_mode, recovery_mode,protection_mode, srl, synchronization_status,synchronized from V$ARCHIVE_DEST_STATUS where dest_id=2;
    STATUS TYPE DATABASE_MODE RECOVERY_MODE PROTECTION_MODE SRL SYNCHRONIZATION_STATUS SYN
    VALID PHYSICAL MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE NO CHECK CONFIGURATION NO
    Anyone can tell me how to apply those missed archive log files.
    Thanks in advacne

    Deccan Charger wrote:
    I got below error.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    ERROR at line 1:
    ORA-01153: an incompatible media recovery is activeYou need to essentially do the following.
    1) Stop managed recovery on the standby.
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;2) Resolve the archive log gap - if you have configured FAL_SERVER and FAL_CLIENT Oracle should do this when you follow step 3 below, as you've manually copied the missed logs you should be OK
    3) restart managed recovery using the command shown above.
    You can monitor archive log catchup using the alert.log or your original query.
    Niall Litchfield
    http://www.orawin.info/
    Edited by: Niall Litchfield on May 4, 2010 2:29 PM
    missed tag

  • Tnsnames.ora / listener.ora files on Oracle Standby Database

    Hi I am configuring an Oracle Standby Database to my production system 4.7 and Oracle 9.2.0.4
    My production server is: PR01
    Database SID: PRD
    Standby database server is: PRDR
    Database SID: PRD
    I have already configured the server to a standby database offline backup. Was generated the control files of the standby database and the database is in standby mode.
    Now I will create a script to start the synchronization of offline redolog from the production server to standby server.
    I have a question: in the document SAP Oracle Standby Database, tells me I should change the tnsnames.ora production server pointing to an additional entry disaster recovery server. The tnsnames.ora  file must have two entries???  corresponding to a production server and another to the disaster recovery server??
    In several links of oracle tells me I should configure listener.ora disaster recovery server that is true??
    Guys my question is: where should I change my listener.ora and tnsnames.ora files?
    Please clear my doubt.
    Best regards,
    Desiree

    Hi Desiree,
    The entry in your TNSNAMES.ORA is a nothing but a tns service, when you define archive log destination it will point to a service. This service's host name will be resolved in your tnsnsmaes.ora file.
    Below is the eg of an entry in pfile:
    *.log_archive_dest_2='SERVICE=<service_name> ARCH OPTIONAL'
    Below is the entry in your tnsnames.ora file
    <service_name>.WORLD=
      (DESCRIPTION = (ADDRESS_LIST = (ADDRESS =
              (COMMUNITY = SAP.WORLD)
              (PROTOCOL = TCP)
              (HOST = <DR_HOST>)
              (PORT = 1527)
        (CONNECT_DATA =
           (SID = <DB_SID>)
           (GLOBAL_NAME = <DB_SID>.WORLD)
    So, your tnsnames.ora will have one entry for your host and the other for the DR host, i.e two entries.
    Listener entry for the convenience when there is a switch over.
    Regards,
    Bala

  • ORA-01157: cannot identify/lock data file error in standby database.

    Hi,
    i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
    PRIMARY DATABASE
    SQL> select name from v$datafile;
    NAME
    +DATA/oradb/datafile/system.256.788911005
    +DATA/oradb/datafile/sysaux.257.788911005
    +DATA/oradb/datafile/undotbs1.258.788911005
    +DATA/oradb/datafile/users.259.788911005
    STANDBY DATABASE
    SQL> select name from v$datafile;
    NAME
    +STDBY/oradb/datafile/system.256.788911005
    +STDBY/oradb/datafile/sysaux.257.788911005
    +STDBY/oradb/datafile/undotbs1.258.788911005
    +STDBY/oradb/datafile/users.259.788911005
    The Actual physical location of standby database files in ASM in standby server is shown below
    ASMCMD> pwd
    +STDBY/11gdb/DATAFILE
    ASMCMD>
    ASMCMD> ls
    SYSAUX.259.805921967
    SYSTEM.258.805921881
    UNDOTBS1.260.805922023
    USERS.261.805922029
    ASMCMD>
    ASMCMD> pwd
    +STDBY/11gdb/DATAFILE
    i even tried to rename the datafiles in standby database but it throws error
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is
    automatic.
    Regards,
    007

    Hi saurabh,
    I tried to rename the datafiles in standby database after restoring it throws the below error
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is
    automatic.
    Also in my pfile i have mentioned the below parameters
    *.db_create_file_dest='+STDBY'
    *.db_domain=''
    *.db_file_name_convert='+DATA','+STDBY'
    *.db_name='ORADB'
    *.db_unique_name='11GDB'
    Regards,
    007

  • Standby database unable to fetch missing archive sequence from primary

    Hi,
    My primary oracle db version is 10.2.0.5 which is n Windows 2003 server 32 bit in file system
    My standby database version is 10.2.0.5 which in wondows 2008 server in ASM instance.
    some of the archivelogs are not fetching by standby database from primary db.because of that recovery is not happening and it waits for missing archive logs but its not transfering on satndby database.
    I tried many time by doing manuall..manuall its hapening but again sometimes its stucks and waits for next missing archivelog.
    standby alert log mesage
    Sun Jul 08 21:33:13 Pacific Daylight Time 2012
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 128945-128945
    DBID 4176230406 branch 617106566
    FAL[client]: All defined FAL servers have been attempted.
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    Sun Jul 08 21:44:03 Pacific Daylight Time 2012
    db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    trace file of standby
    Dump file d:\oracle\admin\mks01p\bdump\mks01p_mrp0_6628.trc
    Sun Jul 08 21:30:23 2012
    ORACLE V10.2.0.5.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
    With the Oracle Label Security, OLAP, Data Mining and Real Application Testing options
    Windows NT Version V6.1 Service Pack 1
    CPU : 8 - type 8664, 4 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:37019M/49108M, Ph+PgF:87277M/103214M
    Instance name: mks01p
    Redo thread mounted by this instance: 1
    Oracle process number: 19
    Windows thread id: 6628, image: ORACLE.EXE (MRP0)
    *** SERVICE NAME:() 2012-07-08 21:30:23.422
    *** SESSION ID:(95.1) 2012-07-08 21:30:23.422
    *** 2012-07-08 21:30:23.422 64949 kcrr.c
    MRP0: Background Managed Standby Recovery process started
    *** 2012-07-08 21:30:28.445 1170 krsm.c
    Managed Recovery: Initialization posted.
    *** 2012-07-08 21:30:28.445 64949 kcrr.c
    Managed Standby Recovery not using Real Time Apply
    *** 2012-07-08 21:30:39.833
    Recovery target incarnation = 1, activation ID = -118713082
    Influx buffer limit = 10000 min(50% x 191963, 10000)
    Successfully allocated 7 recovery slaves
    Using 158 overflow buffers per recovery slave
    Start recovery at thread 1 ckpt scn 7982577982885 logseq 128945 block 2
    *** 2012-07-08 21:30:40.784
    Media Recovery add redo thread 1
    *** 2012-07-08 21:30:40.784 1170 krsm.c
    Managed Recovery: Active posted.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    *** 2012-07-08 21:30:40.940 64949 kcrr.c
    Clearing online redo logfile 1 +ORAREDO1/mks01p/mks01p_redo01a.rdo
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
    ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    ORA-00349: failure obtaining block size for '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
    ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
    Error 349 creating/clearing online redo logfile 1
    *** 2012-07-08 21:30:40.987 64949 kcrr.c
    Clearing online redo logfile 1 complete
    *** 2012-07-08 21:30:41.034 64949 kcrr.c
    Media Recovery Waiting for thread 1 sequence 128945
    *** 2012-07-08 21:30:41.050 64949 kcrr.c
    Fetching gap sequence in thread 1, gap sequence 128945-128945
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
    *** 2012-07-08 21:30:41.533 64949 kcrr.c
    Error 1031 received logging on to the standby
    *** 2012-07-08 21:30:41.533 64949 kcrr.c
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privileges
    *** 2012-07-08 21:31:11.610
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
    *** 2012-07-08 21:31:12.094 64949 kcrr.c
    Error 1031 received logging on to the standby
    *** 2012-07-08 21:31:12.094 64949 kcrr.c
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privileges
    *** 2012-07-08 21:31:42.186
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
    *** 2012-07-08 21:31:42.654 64949 kcrr.c
    Error 1031 received logging on to the standby
    *** 2012-07-08 21:31:42.670 64949 kcrr.c
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privileges
    *** 2012-07-08 21:32:12.747
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
    *** 2012-07-08 21:32:13.215 64949 kcrr.c
    Error 1031 received logging on to the standby
    *** 2012-07-08 21:32:13.230 64949 kcrr.c
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privileges
    *** 2012-07-08 21:32:43.276
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
    *** 2012-07-08 21:32:43.759 64949 kcrr.c
    Error 1031 received logging on to the standby
    *** 2012-07-08 21:32:43.775 64949 kcrr.c
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privileges
    *** 2012-07-08 21:33:13.821
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    i created new password fle on bith primary and standby database also.
    Please help me to resolve this issue.

    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
    ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
    post from standby:-
    SQL> select name, state From v$asm_diskgroup;
    FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
    ORA-01031: insufficient privilegesPost from primary & standby
    SQL> select * from v$pwfile_users;
    User Profile for 919131
    919131     
    Handle:     919131  
    Status Level:     Newbie
    Registered:     Mar 6, 2012
    Total Posts:     16
    Total Questions:     8 (8 unresolved)
    OTN failed 100% to help you, then why you posted another question?
    First close all your old answered threads and then better continue your updates in your thread.
    Edited by: CKPT on Jul 9, 2012 11:45 AM

  • Dropping log file in standby database

    Please,
    I need a help for the following issue:
    I'm making a technical documentation on various event that occur on dataguard configuraation, right now I drop a redo log group file on primary database, and when I try to drop the equivalent log group file on standby database I got the following error:
    SQL> alter database drop logfile group 3;
    alter database drop logfile group 3
    ERROR at line 1:
    ORA-01156: recovery in progress may need access to files
    this is the current state of the redolog file on standby database.
    SQL> select group#,members,status from v$log;
    GROUP# MEMBERS STATUS
    1 3 CLEARING_CURRENT
    3 3 CLEARING
    2 3 CLEARING
    Eventhough I do the following command on standby I also get an error.
    SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
    ALTER DATABASE CLEAR LOGFILE GROUP 3
    ERROR at line 1:
    ORA-01156: recovery in progress may need access to files
    Can someone tell me how to drop on dataguard configuration the redolog file on primary database and their corresponding on standby database
    I'm working on 10 release 2, on Windows
    Thanks you

    Oracle Dataguard Concept and administration release 2,ref b14239: is my source but it doesn't work when trying to drop stanby group or logile member.
    For example, if the primary database has 10 online redo log files and the standby
    database has 2, and then you switch over to the standby database so that it functions
    as the new primary database, the new primary database is forced to archive more
    frequently than the original primary database.
    Consequently, when you add or drop an online redo log file at the primary site, it is
    important that you synchronize the changes in the standby database by following
    these steps:
    1. If Redo Apply is running, you must cancel Redo Apply before you can change the
    log files.
    2. If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO,
    change the value to MANUAL.
    3. Add or drop an online redo log file:
    ■ To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log'
    SIZE 100M;
    ■ To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    4. Repeat the statement you used in Step 3 on each standby database.
    5. Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
    Thank

  • Trying to recover an standby database

    - Oracle 10.2.0.4 Standard Edition
    - O/S: Windows Server 2003
    - Phisically Standby
    We have primary and a standby database. My standby database was synchronized through copying archive redo logs from Primary to Standby. They were copied every 15 min to standby server and then they were recovered from there. Because a lot of archive logs were missed for ever, now my standby database is not synchronized with my primary.
    In order to recover my Standby, one week ago I followed these instructions:
    Step 1: On the standby database check the current scn.
    STDBY> select current_scn from v$database;
    CURRENT_SCN
    2527075174
    Step 2: On the primary database create the needed incremental backup from the above SCN
    C:\Documents and Settings\frego>rman target /
    run {
    allocate channel c1 type disk;
    BACKUP INCREMENTAL FROM SCN 2527075174 DATABASE
    format '\\srvbackup\archiveslogs-35\arch\incr_bkp_%U';
    Step 3: Cancel managed recovery at the standby database
    STDBY>alter database recover managed standby database cancel;
    Media recovery complete.
    Copied the backup files to standby server to "D:\arch\" folder.
    Step 4: Catalog the Incremental Backup Files at the Standby Database
    D:\arch> rman target /
    RMAN> CATALOG START WITH 'D:\arch\';
    Step 5: Apply the Incremental Backup to the Standby Database
    RMAN> RECOVER DATABASE NOREDO;
    Step 6: Put the standby database back to managed recovery mode.
    STDBY>> recover managed standby database disconnect;
    Media recovery complete.
    Step 7: On the primary create new standby controlfile
    PRIM>alter database create standby controlfile as 'C:\incr_bkp\standby01.ctl';
    System altered.
    Step 8: At Standby .. Replace standby controlfile at all location as shown by controle_files parameter.
    Copy the standby control file to the standby site. Shutdown the standby database and replace the stanby controlfiles and restart the >standby database in managed recovery mode...
    Problem was that there were new datafiles created in primary that didn't exist in standby. I had to created them manually on standby:
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA';
    ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA';
    Also, I tried this commands:
    On Standby:
    RMAN> SHUTDOWN;
    RMAN> STARTUP NOMOUNT;
    RMAN> RESTORE STANDBY CONTROLFILE FROM 'D:\arch\standby01.ctl';
    RMAN> SHUTDOWN;
    RMAN> STARTUP MOUNT;
    STDB> ALTER DATABASE CLEAR LOGFILE GROUP 1;
    STDB> ALTER DATABASE CLEAR LOGFILE GROUP 2;
    STDB> ALTER DATABASE CLEAR LOGFILE GROUP 3;
    STDB> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01154: database busy. Open, close, mount, and dismount not allowed now
    SQL> recover managed standby database cancel;
    Media recovery complete.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\ORADATA\PROD\OPEXT\SYSTEM01.DBF'My Questions:
    - What is missing in order to open standby database?
    - Can I again generate rman incremental backups on Primary (from SCN 2527075174), copy them to Standby and start recovery again? Would it generate duplicate records on tables?
    - Should I generate new rman incremental backup pieces on Primary (from last SCN of Standby), copy them to standby and apply there?
    Remember that my Primary is growing every day and those rman backup pieces and standby01.ctl, that are copied on my standby server, are from one week ago.
    Thanks
    Edited by: user521219 on 22-jun-2012 9:31

    user521219 wrote:
    Should I restart and mount my standby database again?
    If I apply Step 3 now:
    STB> alter database recover managed standby database cancel;
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not activeRefer the above mentioned link. First restore controlfile & then perform recovery on standby database.
    >
    user521219      
         Newbie
    Handle:      user521219
    Status Level:      Newbie
    Registered:      Jul 20, 2006
    Total Posts:      48
    Total Questions:      29 (23 unresolved)
    >
    Consider closing your threads and keep the forum clean.
    Edited by: CKPT on Jun 22, 2012 10:43 PM

  • Issue on physical standby database

    Hi
    I've a problem on standby database.
    I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
    I get following message in my alert log
    WARNING! Recovering data file 88 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    how can I fix this now.
    We keep physical standby database 2 day behind, and apply logs manually.
    Physical standby database is maintained manually.
    Could someone help me in getting out of this problem.
    Oracle 9.2.0.7
    solaris

    Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
    From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
    6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
    In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
    Note:
    If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
    Specifying a Time Delay
    You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
    Canceling a Time Delay
    You can cancel a specified delay interval as follows:
    For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
    For logical standby databases, specify the following SQL statement:
    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
    These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
    Section 12.8, "Using a Physical Standby Database with a Time Lag"
    Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

  • Can Grid Control 10gR2 create a standby database when primary db uses ASM?

    Does anyone know if Grid Control 10gR2 will be able to create a standby database when the primary database uses ASM for data files, redo log files, and archive log files but the standby database will use mounted disks? If it can, would it matter that the primary db will be a RAC cluster and the standby will be a single instance db?

    I appreciate your reply and hope you are correct. Have you had a look at the 10gR2 Grid Control to confirm this or are you only going on published statements? The reason I ask is because previous versions of Grid Control claimed to support ASM but they would only allow you to work with them AFTER you had created a standby database manually but you couldn't actually use Grid Control to create a standby database from a primary database that had its log files on ASM disks.

  • CONFIGURE STANDBY DATABASE IN 10G

    hi experts,
                  Need help for configuring standby database in Oracle 10g/Windows.

    Hi Sumeesh,
    Please refer the below mentioned link for configuring data guard.
    http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10823/create_ps.htm
    Below mentioned are the sequence of stpes, which needs to be followed for setting up data guard.
    3.1     Configuring the Primary Database     
    3.1.1     Enable archiving and define a local archiving destination     
    3.1.2     Create a password file     
    3.1.3     Configuring the Oracle networking files     
    3.1.4     Set initialization parameters on the primary database     
    3.1.5     Take Offline/Online backup of the primary database     
    3.1.6     Create a control file for the standby database     
    3.1.7     Prepare initialization parameter file for the standby database and start the primary database with the changed pfile.     
    3.1.8     Copy all files from the primary host to the standby host     
    3.2     Configuring the Standby Database     
    3.2.1     Configuring the Oracle networking files     
    3.2.2     Create a INIT parameter file for the standby database     
    3.2.3     Copy the standby controlfile to the appropriate location     
    3.2.4     Create Oracle Password File     
    3.2.5     Start the physical standby database     
    3.2.6     Initiate log apply services
    Regards,
    Ranjith

  • Standby Database

    Hi all,
    Its ciirctical
    We have prodution database in 10.2.0.1 on sun solaris and its standby with same configuration on remote site.
    Both the database are operating in maximum avaialbilty mode:
    select protection_mode,protection_level name ,db_unique_name from v$database;
    PROTECTION_MODE NAME DB_UNIQUE_NAME
    MAXIMUM AVAILABILITY RESYNCHRONIZATION STANDBY
    I have switched primary to standby and it worked fine but when i reverting back i am getting below error:
    SQL> /
    alter database commit to switchover to standby
    ERROR at line 1:
    ORA-16416: Switchover target is not synchronized with the primary
    When i tried to perform recovery on standby machine it completed successfully. And all archived are applied . But still i am getting same error on primary site when i am trying to switch over to standby.
    Please refer alert log file of primary:
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    LNSb started with pid=20, OS id=1252
    Sat Oct 23 14:53:50 2010
    Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
    Sat Oct 23 14:53:50 2010
    Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
    ORA-16086: standby database does not contain available standby log files
    LGWR: Failed to archive log 2 thread 1 sequence 190 (16086)
    Thread 1 advanced to log sequence 190
    Current log# 2 seq# 190 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo02.log
    Please refer standby alert_log :
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    LNSb started with pid=20, OS id=1252
    Sat Oct 23 14:53:50 2010
    Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
    Sat Oct 23 14:53:50 2010
    Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
    ORA-16086: standby database does not contain available standby log files
    LGWR: Failed to archive log 2 thread 1 sequence 190 (16086)
    Thread 1 advanced to log sequence 190
    Current log# 2 seq# 190 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo02.log
    Sat Oct 23 15:00:49 2010
    Destination LOG_ARCHIVE_DEST_2 is SYNCHRONIZED
    LNSb started with pid=20, OS id=1270
    Sat Oct 23 15:00:52 2010
    Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
    Sat Oct 23 15:00:52 2010
    Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc:
    ORA-16086: standby database does not contain available standby log files
    LGWR: Failed to archive log 3 thread 1 sequence 191 (16086)
    Thread 1 advanced to log sequence 191
    Current log# 3 seq# 191 mem# 0: /export/home/oracle/product/10.2.0/db1/oradata/PRIMARY/redo03.log

    Add one or more standby log files to the standby database. This can be done while the standby database is mounted.
    Errors in file /export/home/oracle/product/10.2.0/db1/admin/PRIMARY/bdump/standby_lgwr_1104.trc
    Please check standby_lgwr_1104.trc file.

  • 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.

  • Standby database SRL & Online logs

    Hi,
    I have just tried my hand at building a Physical standby database in Oracle 10gR2 using RMAN. I will detail out the steps that i have performed before asking my question.
    I configured every pre-requisite and i did not create any SRL's on primary before building a standby database. I am using LGWR ASYNC for redo transmission. I have configured FAL_CLIENT and FAL_SERVER. Protection mode is MAX PERFORMANCE and it is on Solaris 10 x86_64
    1. Took a RMAN full backup
    and created a standby control file as
    SQL> alter database create standby controlfile as '/tmp/standby.ctl';
    2. On another server, I copied the pfile, standby controlfile (renamed it) from primary and mounted the database.
    sqlplus /as sysdba'
    SQL> startup mount pfile='...';
    rman target /
    RMAN> restore database;
    SQL> alter database recover managed standby database disconnect from session;
    Everything worked and MRP was applying the archived logs as they were received from the primary. But, i have seen the SRL's created with default names on the primary database & standby database by Oracle even though i did not explicitly create them. Is this a normal behaviour? I saw them using v$standby_log.
    As a Physical standby database will not use any ONLINE REDO LOGS and i haven't created any with the procedure i have used. i have performed a SWITCHOVER, which has worked with out any problem. My question here is
    1. How did Oracle open the database database when there were no redo logs physically present on the standby site? Is this a normal behavior in a standby environment where Oracle creates ONLINE REDO LOG files for a Standby database being transitioned to Primary whenever a SWITCHOVER or FAILOVER occurs? If this is the case, it is obvious that Oracle will take the LOG SEQUENCE from the last applied ARCHIVED LOG and will start the ONLINE LOG from that sequence?
    Please correct me if i have understood anything wrong here or if i have configured anything wrong. But with the above configuration the Standby database worked perfectly well and switchover was successful too.
    Thanks,
    Harris.

    Correction: I have not created the Standby Database using RMAN but only performed a FULL backup, which i have restored before starting the MRP.

  • Clarification on creating a Physical Standby Database

    I'm practicing with data guard with Oracle 10.2.0.1.0 on two Windows 2003 servers.
    I'm in the process of creating a physical standby database by following the steps outlined in the guide http://www.filibeto.org/sun/lib/nonsun/oracle/10.2.0.1.0/B19306_01/server.102/b14239/create_ps.htm
    I've created the primary database and did a cold backup of all the datafiles and copied them to the standby server using OS commands. I've created a pfile from the spile in primary database and changed the needed parameters for the standby database.
    What I don't understand is this statement I think is creating a control file for the standby database: SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tamp/standby.ctl'
    Exactly what I don't understand is what to do with this control file. I'm thinking that if I try to use it as the controlfile for the standby database, the standby database will refuse to open since the database name in the control file wont match the one the server expects.
    I don't want to proceed until this becomes clear. So my question is what to do with the output of the above statement that seems to create a control file for the standby database.
    Any help would be appreciated.
    Dula

    >
    You're thinking wrong.
    Please clarify the difference between db_name and
    db_unique_name.
    Db_unique_name needs to be identical for both primary
    AND standby database.
    If db_unique_name differs, you'll get errors.
    Sybrand,
    Perhaps, you meant DB_NAME has to be identical for both databases.
    DB_NAME name has to be the same for both primary and physical standby database.
    DB_UNIQUE_NAME should be unique for each database in the standby configuration.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i68626
    If you configure Logical Standby Database, DB_NAME may be different.
    For the original poster: Chapter 3 - Creating a Physical Standby Database of Oracle® Data Guard Concepts and Administration has all the steps you have to do in order to configure a physical standby database.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
    Cheers,

  • How to apply archive in Standby Database?

    Hello,
    My Database are running in linux plateform. I am seeing that archives which are generating are not copying to standby server & not applying.
    Can anybody suggest me how to copy archive from primary database(ASM file system) to standby Database & apply those archives?
    Thanks

    Hi,
    I am having similar problem. The primary logs are shipping on to standby but are not getting applied.
    Here are the outputs:
    From primary
    SQL > select thread#,max(sequence#) from v$archived_log where archived='YES' group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 27908
    2 28476
    3 31643
    select max(sequence#) from gv$archived_log;
    MAX(SEQUENCE#)
    31643
    From Standby
    SQL > select thread#,max(sequence#) from v$archived_log where applied ='YES' group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 26862
    2 27580
    3 30874
    select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    31643
    Any help is appreciated.
    Thanks in advance.

Maybe you are looking for

  • How to diferenciate apps on iphone and ipad

    I am using same iTunes for my iphone and Ipad. I would like to have this devices with different applications and different files. Is this possible on the same computer ? BTW. New iTunes is unusable - if Apple wants to get rid of their customers  new

  • Help With Deleting a Saved Photo

    I saved a very high resolution picture from the internet on my iPod, and every time I try to delete it, it freezes up while trying to load it. What can I do?

  • Why the battery of iphone 5s  be decharged too soon?

    why the battery of iphone 5s  be decharged too soon?

  • MDB Suspend/Resume server startup

    Hello All, We have a requirement where we want to stop MDBs from starting even after server restart. We have tried the following In MDB control page in Admin Console there is a feature in WLS where we can Suspend/Resume MDBs from consuming messages.

  • Action: Open a web link vs Run a JavaScript

    I've been able to add a "Run a JavaScript" Action to my Link, but what I really need to do is use the "Open a web link" action instead. Is there anything I can change in this code... Link.setAction("app.launchURL('http://www.lego.com/', true);" ); or