Data Guard - MRP stuck issues on a physical standby database

Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?

Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

Similar Messages

  • How to make a physical standby database in the read_only state in 11g?

    In 10g, we can make a physical standby database in the read_only state. But in 11g, no a read_only state for a physical standby database. How to make a physical standby database in the read_only state in 11g?

    Hi
    read-only mode (for 11g physical standby)
    A mode in which a database can be opened that allows queries, but disallows modifications.
    A physical standby database can be opened read-only so that queries may be performed. If a license for the Oracle Active Data Guard option has been purchased, a physical satndby database can be open while redo apply is active. This capability is known as Real-time Query.
    For more details have a look at:
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#SBYDB00706
    Hipe this Helps
    Regards

  • Problem with data guard Creating a Physical Standby Database turorial

    There is a tutorial of Creating a data guard Physical Standby Database:
    http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
    I tried to install it on two servers. One for primary database second for physical standby.
    I have error on C. Creating the standby database over the network, action #6:
    "On the standby system, set the ORACLE_SID environment variable to your <physical standby SID> (i.e. orclsby1) and start the instance in NOMOUNT mode with the text initialization parameter file."
    When I try to connect to idle instance there is an error pops up:
    C:\>sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Thu May 21 16:28:10 2009
    Copyright (c) 1982, 2008, Oracle. All rights reserved.
    ERROR:
    ORA-12560: TNS:protocol adapter error
    I'v checked listener and it is runned. There is no service for database because there is no database yet.
    The question is did some one installed data guard configuration using this tutorial? Is there any errors in it? What should I do to finish this installation?

    On Windhose for every instance a service must have been created using the oradim command.
    Oracle tutorials are usually Unix-centric, as Windhose is an odd man out, so they don't discuss that bit.
    'Kindly do the needful' and create the service prior to starting the instance in nomount mode
    Hint: oradim is documented and has a help=y clause.
    IIRC there is an option in database control (in the maintenance part) which automates everything.
    Sybrand Bakker
    Senior Oracle DBA
    Experts: those who do read documentation

  • About Data Guard - Physical Standby Database

    Dear All,
    I have read many documents regading Data Guard.
    I am about to setup Data Guard in our current environment but want to clear few tings.
    I have a confusion between physical and logical standby database.
    What I have read from different documents is:
    -Physical Standby Database in (11g)
    1) It is the most efFicient
    2) I can be either in mount or open state
    3) Select queries and reporting can be done to improve performance of the primary database.
    4) Schema on primary and standby database is always the same
    -- Logical Standby Database
    1) You can create additional tables, indexes, etc.
    2) Always in open mode
    3) Select queries and reporting can be done to improve performance of the primary database
    Now our scenerio is, that we have one server at the moment, OS is linux and operating system is 11g. We want to setup an other server in another country, will also be 11g on Linux in a way that it acts as standby/backup server. Schema and data is always the same. In case due to unavailability of primary server, standby server acts as the primary server (This has to be automated). The reason for unavailability could be any like maintenance work on primary server, network or hardware failure at primary server. The last and the most important thing is that users from this country where we will setup standby database will insert/update data on the primary server BUT queries and reporting will be done from this newly created standby data.
    Kindly recomend the best Data Guard in this scenerio and kindly correct me where I am wrong.
    Thanks, Imran

    A logical standby has various limitations on things like data types. It's also a much more complex architecture, which makes it more likely that something will break periodically and require attention. Applying redo to a physical standby is code that has been around forever and is as close to bullet-proof as you'll get. And you would generally prefer to fail over to a physical standby-- if you do things like create new objects in the logical standby, you may have to get rid of those objects during a failover to get acceptable OLTP performance.
    Justin

  • Difference between physical standby database and Data Guard

    Hi guys,
    Today I attended one interview. They asked me a difference between the Oracle Physical Standby database and Oracle Dataguard?
    Upto my knowledge Oracle Physical Standby Database is one type of Standby Database can be configured using Oracle Databaguard Feature.
    Can you people calrify me on this.
    Regards,
    Vijayaraghavan K

    hello,
    yes you are right upto some extent...here is para form oracle doc
    Oracle Data Guard is the most effective and comprehensive
    data availability, data protection, and disaster recovery solution
    for enterprise databases. It provides the management, monitoring,
    and automation software infrastructure to create and maintain one
    or more synchronized standby databases to protect data from failures,
    disasters, errors, and corruptions.
    Data Guard standby databases can be located at remote disaster
    recovery sites thousands of miles away from the production data center,
    or they may be located in the same city, same campus,
    or even in the same building. If the production database
    becomes unavailable because of a planned or an unplanned outage,
    Data Guard can switch any standby database to the production role,
    thus minimizing downtime and preventing any data loss.oracle data guard is maximum availiblity solution which maintain physical standby databases and in case of failure of production can switch production role to and standby database.
    read it here
    http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
    thanks and regards
    VD
    Edited by: Dixit on Aug 31, 2009 1:35 AM
    Edited by: Dixit on Aug 31, 2009 1:36 AM

  • Problem in recover physical standby database(Data Guard) by rman

    Hello to all
    I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
    scenarios is follow
    1- In rman I create a backup of standby database by this command:
    backup database plus archivelog delete all input;
    2- I run this comman in rman for recover standby database
    run{
    2> set until scn 1392701;
    3> restore database;
    4> recover database;
    5> }
    (1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
    V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
    DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
    but RMAN result is like this:
    executing command: SET until clause
    Starting restore at 13-DEC-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
    channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/backup/0ek24dt4_1_1
    tag=TAG20081213T042506
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
    Finished restore at 13-DEC-08
    Starting recover at 13-DEC-08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
    archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
    archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
    archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
    unable to find archive log
    archive log thread=1 sequence=118
    RMAN-03002: failure of recover command at 12/13/2008 05:14:13
    RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700
    3- then I decline 1392701 to 1392700 and i run this command
    run{
    2> set until scn 1392700;
    3> restore database ;
    4> recover database;
    5> }
    executing command: SET until clause
    Starting restore at 13-DEC-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
    channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
    Finished restore at 13-DEC-08
    Starting recover at 13-DEC-08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 116 is already on disk as
    file /u01/app/oracle/oradata/archive/1_116_666786084.arc
    archive log thread 1 sequence 117 is already on disk as
    file /u01/app/oracle/oradata/archive/1_117_666786084.arc
    archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
    sequence=116archive log
    filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
    thread=1 sequence=117Oracle Error:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS
    would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf'
    media recovery complete, elapsed time: 00:00:10
    Finished recover at 13-DEC-08
    4- if I run
    run{
    restore database;
    recover database;
    I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700)
    5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
    but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
    do you know what is problem
    thanks
    Edited by: ARKH on Dec 12, 2008 11:06 PM

    hi
    I myself have found the solution , when I recover the standby database
    it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700) but if I begain redo apply before open the database
    and I wait till all redo apply process start and communication between the
    standby database and the primary database start, then I can
    open the standby database and no error will raise
    but if befor restarting redo apply I open the database I'll recieve the
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
    thanks

  • Data Guard - Steps to install Physical standby database in an RHEL 5.6 x86

    HI Team,
    I need to install Physical standby database in a OS installed from factory with most basic packages. Please find the info in detail
    Standby Server :
    Database Version : 10g Release 2
    Operating System : Red Hat Enterprise Linux Server release 5.6 (Tikanga) , RHEL 5.6 x86_64
    swartis.dc$ free -m
    total used free shared buffers cached
    Mem: 34158 33847 311 0 558 28367
    -/+ buffers/cache: 4921 29237
    Swap: 10001 63 9937
    - Things i need to validate in the PROD server. Eg : Are the prod db version & standby db version should be the same, Do the OS need to be same ............ETC
    - Basic Linux rpm required for standby server & any other pre-requisites required at standby server
    - Verify connectivity speed btw servers to decide log file size
    - Please give me more detailed steps , where i need to start the steps in installation of Physical standby database.
    Thanks in advance.
    -- Rakesh
    Edited by: Rakesh on Jan 10, 2012 8:23 AM

    Hello again;
    Sorry for the Delay.
    To this question "Do i need to install 10.2.0.2.0 ORACLE_HOME & on top of it apply 10.2.0.3.0 patchset.?"
    Yes.
    All my Oracle 10 installs started with 10.2.0.1 and then I patched up from there. If I remember correctly 10.2.0.1 may bark on Red Hat 5.
    You can work around this by reviewing this file :
    /etc/redhat-releaseSave whatever is in there somewhere and replace it with :
    redhat-3After the install put back what was there and get rid of the "redhat-3".
    I extra RPM's I used were :
    rpm -ivh kernel-headers-2.6.18-164.el5.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh elfutils-libelf-devel*.x86_64.rpm glibc-devel-2* gcc-4*.x86_64.rpm gcc-c++-4*.x86_64.rpm libstdc++-devel-4*.x86_64.rpm glibc-headers*.x86_64.rpm libgomp*.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh sysstat*I searched my Red Hat Disks before hand and ran the RPM commands as shown. Adjust as needed.
    To verify that the required packages have been installed on your system, run the following command :
    pm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" binutils \
    compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc \
    glibc-common glibc-devel-2.5 libaio libaio-devel libgcc libstdc++ libstdc++-devel \
    make sysstatThis document is for Oracle 11, but the OS part should be the same.
    http://www.visi.com/~mseberg/installing_oracle_11g_r2_64.html
    Currently I have 3 servers running both Oracle 10 and 11 ( In different homes ) using this OS.
    I have used Oracle 11 document with Oracle 10 also : ( Better once you are setup and a great standby recovery document )
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Rman backup on physical standby database without cancelling MRP

    Hi all,
    Could anyone share, is this possible to take RMAN backup on physical standby database without cancelling MRP process.
    regarrds,

    Hi,
    On Standby Side:
    SQL> alter database mount;
    Database altered.
    SQL> alter database recover managed standby database using current logfile disconnect from session;
    Database altered.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:31:43 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=390 RECID=391 STAMP=815416638
    input archived log thread=1 sequence=391 RECID=392 STAMP=815421952
    input archived log thread=1 sequence=392 RECID=393 STAMP=815422343
    input archived log thread=1 sequence=393 RECID=394 STAMP=815422434
    input archived log thread=1 sequence=394 RECID=395 STAMP=815422570
    input archived log thread=1 sequence=395 RECID=396 STAMP=815476598
    input archived log thread=1 sequence=396 RECID=397 STAMP=815476615
    input archived log thread=1 sequence=397 RECID=398 STAMP=815476645
    input archived log thread=1 sequence=398 RECID=399 STAMP=815477471
    input archived log thread=1 sequence=399 RECID=400 STAMP=815477475
    input archived log thread=1 sequence=400 RECID=401 STAMP=815477628
    input archived log thread=1 sequence=401 RECID=403 STAMP=815584146
    input archived log thread=1 sequence=402 RECID=402 STAMP=815584137
    input archived log thread=1 sequence=403 RECID=405 STAMP=816017446
    *input archived log thread=1 sequence=404 RECID=404 STAMP=816017444*
    *input archived log thread=1 sequence=405 RECID=406 STAMP=816017455*
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T153202_8spm937d_.bkp tag=TAG20130521T153202 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_390_8s48hfrp_.arc RECID=391 STAMP=815416638
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_391_8s4fohwb_.arc RECID=392 STAMP=815421952
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_392_8s4g1q0v_.arc RECID=393 STAMP=815422343
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_393_8s4g4l8z_.arc RECID=394 STAMP=815422434
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_14/o1_mf_1_394_8s4g8t9h_.arc RECID=395 STAMP=815422570
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_395_8s631622_.arc RECID=396 STAMP=815476598
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_396_8s631qjj_.arc RECID=397 STAMP=815476615
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_397_8s632od8_.arc RECID=398 STAMP=815476645
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_398_8s63whqc_.arc RECID=399 STAMP=815477471
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_399_8s63wly4_.arc RECID=400 STAMP=815477475
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_15/o1_mf_1_400_8s641d8j_.arc RECID=401 STAMP=815477628
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_401_8s9d21jk_.arc RECID=403 STAMP=815584146
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_16/o1_mf_1_402_8s9d1skv_.arc RECID=402 STAMP=815584137
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_403_8spm6p4h_.arc RECID=405 STAMP=816017446
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_404_8spm6mqj_.arc RECID=404 STAMP=816017444
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc thread=1 sequence=405
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T153213_8spm9fnc_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:02:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T153213_8spmfqxf_.bkp tag=TAG20130521T153213 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> exit
    Recovery Manager complete.
    [oracle@oel62-x64 Desktop]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.3.0 Production on Tue May 21 15:34:42 2013
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select max(Sequence#) from  v$archived_log;
    MAX(SEQUENCE#)
            405
    SQL> select max(Sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            404
    SQL> There have no problem, backup database when MRP is running. But if you want delete, then you are getting RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
    And will not delete this archived log, because it is needed for standby or upstream capture process.
    Updated
    When MRP stoped
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:46:07 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=24 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=405 RECID=406 STAMP=816017455
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154617_8spn3s9w_.bkp tag=TAG20130521T154617 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_405_8spm6yg0_.arc RECID=406 STAMP=816017455
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154618_8spn3v4f_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:16
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154618_8spn6779_.bkp tag=TAG20130521T154618 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> Apply process is stopped and new redo received from primary.
    SQL> select max(Sequence#)  from v$archived_log;
    MAX(SEQUENCE#)
            407
    SQL> select max(Sequence#)  from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
            405
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@oel62-x64 Desktop]$ rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue May 21 15:49:28 2013
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ADMDB (DBID=4063877183, not open)
    RMAN> backup database plus archivelog delete all input;
    Starting backup at 21-MAY-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=32 device type=DISK
    channel ORA_DISK_1: starting archived log backup set
    channel ORA_DISK_1: specifying archived log(s) in backup set
    input archived log thread=1 sequence=406 RECID=407 STAMP=816018527
    input archived log thread=1 sequence=407 RECID=408 STAMP=816018530
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_annnn_TAG20130521T154937_8spnb1y3_.bkp tag=TAG20130521T154937 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
    channel ORA_DISK_1: deleting archived log(s)
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_406_8spn8hkn_.arc thread=1 sequence=406
    RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
    archived log file name=/u01/app/oracle/fast_recovery_area/stldb/STLDB/archivelog/2013_05_21/o1_mf_1_407_8spn8l69_.arc thread=1 sequence=407
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/stldb/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/stldb/sysaux01.dbf
    input datafile file number=00005 name=/u01/app/oracle/oradata/stldb/example01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/stldb/undotbs01.dbf
    input datafile file number=00006 name=/u01/app/oracle/oradata/stldb/appdata01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/stldb/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_nnndf_TAG20130521T154939_8spnb3f5_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    including current control file in backup set
    including current SPFILE in backup set
    channel ORA_DISK_1: starting piece 1 at 21-MAY-13
    channel ORA_DISK_1: finished piece 1 at 21-MAY-13
    piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_05_21/o1_mf_ncsnf_TAG20130521T154939_8spndhly_.bkp tag=TAG20130521T154939 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
    Finished backup at 21-MAY-13
    Starting backup at 21-MAY-13
    using channel ORA_DISK_1
    specification does not match any archived log in the repository
    backup cancelled because there are no files to backup
    Finished backup at 21-MAY-13
    RMAN> I think, codes is understandable.
    Regard
    Mahir M. Quluzade
    Edited by: Mahir M. Quluzade on May 21, 2013 3:36 PM

  • Physical standby database backup issue

    Hello
    We have a Data Guard environment if I open Physical Standby database for query by this statement:
    "Alter database recover managed standby database cancel" and then start redo apply by
    "alter database recover managed standby database using current logfile" and then backup the Physical standby database by RMAN
    for example
    RMAN> backup database;
    I will get this error :
    Starting backup at 03-FEB-09
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of backup command at 02/03/2009 15:36:45
    ORA-01219: database not open: queries allowed on fixed tables/views only
    but if before restarting redo apply after opening standby database for query I shutdown the database first and then start redo apply I don't get that error while backing up
    If DataGuard mode is Maximum Performance or Maximum Availability shutting down the standby database before
    restarting redo apply is possible but if DataGuard mode is Maximum Protection shutting down the standby database
    cause failing Primary database
    do you know what is problem and it's solution ?
    thanks

    like I said bro, i have made standby controlfile....
    I made it on Primary Database (DG1)...........
    but when I copied it to Physical Standby Database, the error message raised "DBID IS NOT SAME",
    thanks Renato OCP for uR attention..........
    is there any other suggestion.............?
    regards
    abip

  • 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

  • Data Guard DB Broker configuration failed after adding Standby DB

    I am trying to set up DG Broker configuration between Primary and Physical Standby DB. I have added Standby db and enabled it. But when i try to show configuration it failed. Given below are the errors.
    Any help regarding this error is appreciated.
    GMGRL> show configuration
    Configuration
    Name: DBTEST
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    DBSOURCE - Primary database
    DBTARGET - Physical standby database
    Fast-Start Failover: DISABLED
    Current status for "DBTEST":
    Warning: ORA-16607: one or more databases have failed
    DGMGRL> show database verbose DBTARGET
    Object "dbtarget" was not found
    Given below is the alert.log error
    Fatal NI connect error 12514, connecting to:
    (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=pdg2.localdomain)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=DBTARGET_DGB.US.JT.COM)(CID=(PROGRAM=oracle)(HOST=pdg1.localdomain)(USER=oracle))))
    VERSION INFORMATION:
    TNS for Linux: Version 11.1.0.6.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.1.0.6.0 - Production
    Time: 29-AUG-2011 14:58:08
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12564
    TNS-12564: TNS:connection refused
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    # tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.1.0/db_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    DBSOURCE =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = pdg1.localdomain)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = DBSOURCE.US.JT.COM)
    DBTARGET =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = pdg2.localdomain)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = DBTARGET.US.JT.COM)
    I can connect from Primary to Standby db (DBTARGET). Given below is the status of that
    [oracle@pdg1 ~]$ sqlplus sys@dbtarget as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Mon Aug 29 15:01:43 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL>

    MSEBERG,
    Hi yes i am using spfile in both Primary and Standby. Given below is the list for inconsistent properties. It did not report anything.
    While running the status report on DBTARGET i get the following error. It waited for about 5 mins before giving the err
    Current status for "DBTARGET":
    Error: ORA-16662: network timeout when contacting a database
    Given below is the complete status.
    DGMGRL> SHOW DATABASE 'DBSOURCE' 'StatusReport'
    STATUS REPORT
    INSTANCE_NAME SEVERITY ERROR_TEXT
    DGMGRL> show database 'DBSOURCE' 'LogXptStatus';
    LOG TRANSPORT STATUS
    PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
    DBSOURCE DBTARGET
    DGMGRL> SHOW DATABASE 'DBSOURCE' 'InconsistentProperties';
    INCONSISTENT PROPERTIES
    INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
    DGMGRL> SHOW DATABASE 'DBSOURCE' 'InconsistentLogXptProps';
    INCONSISTENT LOG TRANSPORT PROPERTIES
    INSTANCE_NAME STANDBY_NAME PROPERTY_NAME MEMORY_VALUE BROKER_VALUE
    DGMGRL> SHOW DATABASE VERBOSE 'DBSOURCE';
    Database
    Name: DBSOURCE
    Role: PRIMARY
    Enabled: YES
    Intended State: TRANSPORT-ON
    Instance(s):
    DBSOURCE
    Properties:
    DGConnectIdentifier = 'dbsource'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '30'
    RedoCompression = 'DISABLE'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'MANUAL'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '3'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = '/u01/app/oracle/oradata/DBSOURCE,
    /u01/app/oracle/oradata/DBSOURCE'
    LogFileNameConvert = '/u01/app/oracle/oradata/DBSOURCE,
    /u01/app/oracle/oradata/DBSOURCE, /u01/app/oracle/flash_recovery_area/DBSOURCE/onlinelog,
    /u01/app/oracle/flash_recovery_area/DBSOURCE/onlinelog'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName = 'pdg1.localdomain'
    SidName = 'DBSOURCE'
    StandbyArchiveLocation = '/u01/app/oracle/oradata/DBSOURCE'
    AlternateLocation = ''
    LogArchiveTrace = '0'
    LogArchiveFormat = '%t_%s_%r.arc'
    LatestLog = '(monitor)'
    TopWaitEvents = '(monitor)'
    Current status for "DBSOURCE":
    SUCCESS
    DGMGRL> SHOW DATABASE VERBOSE 'DBTARGET'
    Database
    Name: DBTARGET
    Role: PHYSICAL STANDBY
    Enabled: YES
    Intended State: APPLY-ON
    Instance(s):
    DBTARGET
    Properties:
    DGConnectIdentifier = 'dbtarget'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '30'
    RedoCompression = 'DISABLE'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'MANUAL'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '3'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = '/u01/app/oracle/oradata/DBSOURCE,
    /u01/app/oracle/oradata/DBSOURCE'
    LogFileNameConvert = '/u01/app/oracle/oradata/DBSOURCE/archive,
    /u01/app/oracle/oradata/DBSOURCE/archive, /u01/app/oracle/oradata/flash_recovery_area/DBSOURCE,
    /u01/app/oracle/flash_recovery_area/DBSOURCE/onlinelog'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName = 'pdg2.localdomain'
    SidName = 'DBTARGET'
    StandbyArchiveLocation = '/u01/app/oracle/oradata/DBSOURCE/archive'
    AlternateLocation = ''
    LogArchiveTrace = '0'
    LogArchiveFormat = '%t_%s_%r.arc'
    LatestLog = '(monitor)'
    TopWaitEvents = '(monitor)'
    Current status for "DBTARGET":
    Error: ORA-16662: network timeout when contacting a database
    DGMGRL> show configuration
    Configuration
    Name: DBTEST
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    DBSOURCE - Primary database
    DBTARGET - Physical standby database
    Fast-Start Failover: DISABLED
    Current status for "DBTEST":
    Warning: ORA-16607: one or more databases have failed
    Edited by: 880215 on Aug 29, 2011 2:47 PM

  • How to check data in physical standby database?

    Hi!
    I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
    But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
    thankS

    I hope the following will help
    Verifying the Physical Standby Database
    ==========================================
    Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
    To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
    Step 1 Identify the existing archived redo logs.
    On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
    SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
    2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
    9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
    10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
    3 rows selected.
    Step 2 Archiving the current log.
    On the primary database, archive the current log using the following SQL statement:
    SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
    Step 3 Verify that the new archived redo log was received.
    On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
    SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
    2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
    9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
    10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
    11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
    4 rows selected.
    The logs are now available for log apply services to apply redo data to the standby database.
    Step 4 Verify that the new archived redo log was applied.
    On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
    SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    2 ORDER BY SEQUENCE#;
    SEQUENCE# APP
    8 YES
    9 YES
    10 YES
    11 YES
    4 rows selected.

  • Using streams to capture data from physical standby database.

    Does anybody know if it is possible to use streams to capture data from physical standby database instead of PROD database? The standby database is in read only mode. We use Oracle 11gR2.
    Thanks in advance.

    physical are closed : how will it managed the queues and overspill queues when target is not present? Also the data dictionary must reflect the primary but If you run capture, then you introduce rules that are not on primary: How ?

  • Issue with physical standby database not in sync with primary

    Hi,
    I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
    SQL> select thread#,max(sequence#) from v$log_history group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 7
    PROCESS STATUS THREAD# SEQUENCE#
    ARCH CONNECTED 0 0
    ARCH CONNECTED 0 0
    RFS OPENING 1 12
    ALERT LOG :
    Tue Mar 20 07:31:32 2012
    alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:32 2012
    Attempt to start background Managed Standby Recovery process (PRIMARY)
    MRP0 started with pid=18, OS id=16370
    Tue Mar 20 07:31:32 2012
    MRP0: Background Managed Standby Recovery process started (PRIMARY)
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 8 processes
    Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
    Tue Mar 20 07:31:39 2012
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:54 2012
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 9677325080303
    Tue Mar 20 07:31:54 2012
    MRP0: Media Recovery Complete (PRIMARY)
    Tue Mar 20 07:31:55 2012
    MRP0: Background Media Recovery process shutdown (PRIMARY)
    Thanks,
    Rakesh

    HI CKPT,
    Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
    SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
    Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
    Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
    Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
    Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
    Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
    36 rows selected.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oracle/STDBY/arch/
    Oldest online log sequence 13
    Next log sequence to archive 0
    Current log sequence 14
    SQL> ho ls -ltra /oracle/STDBY/arch/
    total 3754456
    drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
    -rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
    -rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
    -rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
    -rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
    -rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
    -rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
    -rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
    -rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
    -rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
    -rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
    -rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
    drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
    SQL>

  • Starting Physically Standby Database in Mount Mode

    Hi All
    I have configured Data Guard using Oracle 10g 10.2.0.4.0 (64 bits) on Windows 2008 Server (64 bits) Release 2 Enterprise.
    Data guard configuration was OK as the message from "Enable Configuration DG1" was "SUCCESS" for both
    Primary and Standby Database. I have also set both Databases and TNS to start Automatically whenever Windows Starts.
    The Problem is as long as the Standby Server is running, there is No issue.
    But when we Restarts the Backup Server, Physically Standby Database is Started and TNS is also Started,
    but Archives  are not received until I physically do the following steps so that it can received the Archives.
    SQL> startup nomount;                                                                                                                
    SQL> alter database mount standby database;                                                                 
    SQL> alter database recover managed standby database disconnect from session;
    Is there a way to start Physically Standby Database in Mount mode when windows started.
    Regards
    Thunder2777

    Hi Mihael
    I have created 2 files. 1 Bat file 2nd sql file which contains all commands as written above.
    When I execute start.bat file
    1. set ORACLE_HOME=C:\oracle\product\10.2.0\db_1
    2. set ORACLE_SID=UMISBK
    3. sqlplus / [email protected]
    1 & 2 executed properly. At 3 it just display SQL help for login as shown below.
    SQL*Plus: Release 10.2.0.4.0 - Production
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Usage 1: sqlplus -H | -V
        -H             Displays the SQL*Plus version and the usage help.
        -V             Displays the SQL*Plus version.
    Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
      <option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
    It Did Not execute start.sql file to excute sql commands.
    Regards
    Thunder2777

Maybe you are looking for

  • Urgent:Error while deploying the BPEL process

    Hi, I am doing a BPEL process to insert some data into employees table depending upon the employee Number. Means before inserting data, a check should be made whether that employee number already exists or not.If it exists then we have to update the

  • Adobe CS5 quit unexpectedly on 10.7.3

    Hello, I have installed Adobe CS5 Master Collection on my MacBook Alu (late 2008) and it's works fine on 10.5.8 then I updated to 10.6 -- still works fine, until I updated to 10.7, it quit unexpectedly. I searched on the internet and I found that I m

  • InDesign font size problems

    Hi Am having trouble with InDesign - My font size small arrow buttons (up and down) in top dock have decided not to work anymore - Can still change font size manually but I would rather they worked. Any ideas? Cheers

  • Forms 10g hanging.

    Has anyone else encountered this problem. I leave my 10g application running (doing nothing) and start a new browser session looking at OTN. After a while the forms application goes permanently busy and CPU useage goes up to 100%. The only way to get

  • Connection object in other classes

    i am writing a JDBC application. There will only be one user for this application. I want to know whether i am doing it the right way. Main program sets the connection to database and provides a static method getDBConnection() which returns a Connect