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.

Similar Messages

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

  • How to deal with tempfiles named '+DATA' on physical standby databases

    Hi gurus,
    I have a 3-node RAC with 2 standby databases, all of them 11.2.0.3, on CentOS 5.10 64 bits.
    I use Active Data Guard (with DB open in read-only mode, obviously).
    My problem is that somehow I have 3 tempfiles named '+DATA' on one standby database, so I can't drop nor rename these files. Is there any way to fix this?
    Looks like the tempfiles couldn't be created when the database was opened in read-only mode.
    Thanks a lot for your help.
    # Primary DB:
    col TABLESPACE format a10
    col TEMPFILE format a50
    select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
      TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
      TEMP                3          4 +DATA/racdb/tempfile/temp.382.873892319                  8192 ONLINE
      TEMP                3          7 +DATA/racdb/tempfile/temp.383.873892341                  8192 ONLINE
      TEMP                3          8 +DATA/racdb/tempfile/temp.384.873892341                  8192 ONLINE
    # Standby DB:
    col TABLESPACE format a10
    col TEMPFILE format a50
    select a.name TABLESPACE, b.TS#, b.FILE#, b.name TEMPFILE, b.bytes/1024/1024 MB, b.status from v$tablespace a, v$tempfile b where a.name='TEMP';
      TABLESPACE        TS#      FILE# TEMPFILE                                                   MB STATUS
      TEMP                3          4 +DATA                                                       0 ONLINE
      TEMP                3          7 +DATA                                                       0 ONLINE
      TEMP                3          8 +DATA                                                       0 ONLINE
      TEMP                3          9 /u02/oradata/RACDBSB1/tempfile/temp_01.dbf                512 ONLINE
    RMAN> report schema;
    using target database control file instead of recovery catalog
    RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
    Report of database schema for database with db_unique_name RACDBSB1
    List of Temporary Files
    =======================
    File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
    4    3072     TEMP                 8192        +DATA
    7    3584     TEMP                 8192        +DATA
    8    5120     TEMP                 8192        +DATA
    9    512      TEMP                 8192        /u02/oradata/RACDBSB1/tempfile/temp_01.dbf
    SQL> show parameter db_create_file_dest
    NAME                                 TYPE                             VALUE
    db_create_file_dest                  string                           /u02/oradata
    Thanks!

    Hi all,
    Regarding Hemant's question, YES, I use that config, and the error I receive is:
    SQL> alter database tempfile 4 drop;
      alter database tempfile 4 drop
      ERROR at line 1:
      ORA-01516: archivo log, archivo de datos o archivo temporal "+DATA" inexistente
    Segey, yes, I've tried with no luck.
    The good news are that today we've resolved the problem, we had to use:
    SQL> alter tablespace temp drop tempfile 4;
    Tablespace altered.
    OMG, what's the difference... alter database tempfile 4, alter tablespace temp drop tempfile 4... they are both the same...!! lol
    Thanks guys!

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

  • How to identify that my physical standby database in use real time apply?

    Hi,
    Can any one give me the SQL to identifiy that my physical standby database is in real time applying redo logs?
    Its urgen please....
    Thanks.

    You could just look at the alert log. Look for "Recovery of Online Redo Log"
    Or you could select from v$standby_apply_snapshot to see if the standby is up-to-date.
    select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
    to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
    to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;

  • 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

  • How to stop and cancel physical standby database (ORACLE 10g)

    Dear All,
    I have physical standby setup and I want stopped for the time being that to use the database as an normal DB (standalone inestance).
    Kindly advise and show me how do I do that.
    Regards,

    executing below query on primary db stops log shipping to standby.......i think this is sufficient for disabling your physical standby setup temporary
    alter system set log_archive_dest_state_2=defer scope=both;
    In future if you want your dataguard setup back..............you can rebuild the standby and enable the log_archive_dest_state_2 parameter.
    Edited by: Veeresh.S on Nov 14, 2012 5:45 PM

  • 11g Data guard 建physical standby database配置相关问题

    General information
    OS:red hat Linux 2.6.32-200.13.1.el5uek x86_64(primary,standby)
    Home version:11.2.0.3(primary,standby)
    Situation:
    实验用库,想学习data guard,在另一个服务器上克隆了一个HOME并按照官方文档http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#i1225703
    中去实验,步骤均按照官方文档来,最后在mount standby库时校验select sequence# from v$archived_log没有记录,出错日志如下(从mount开如截取)
    standby alert_dbacoe.log
    Error logs
    alter database mount
    Completed: alter database mount
    Error 604 received logging on to the standby
    +FAL[client, ARC2]: Error 604 connecting to PRIMARYSV for fetching gap sequence+
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo01_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u03/app/oracle/oradata/dbacoe/redo01.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo02_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 2 thread 1: '/u03/app/oracle/oradata/dbacoe/redo02.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    Errors in file /u05/oracle/app/oracle/diag/rdbms/standby/dbacoe/trace/dbacoe_lgwr_1912.trc:
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u04/app/oracle/redundancy/dbacoe/redo03_s.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 3 thread 1: '/u03/app/oracle/oradata/dbacoe/redo03.log'
    ORA-27037: unable to obtain file status
    Linux-x86_64 Error: 2: No such file or directory
    Additional information: 3
    ARC3: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    Addition:
    因为是实验用库,所以结构有点怪,大体如下:
    Primary
    数据文件在BASE所在的oradata下 即/u03/app/oracle下,
    redo文件每组两份,一份在oradata下,另一份在同机的/u04/app/oracle/redundancy中(以_s结尾命名)
    archive文件在/u04/app/oracle/fast_recovery_area中
    standby
    数据文件在/u05/oracle/app/oracle/oradata下
    redundancy中的redo文件随着该目录放到oradata下的red中了
    archive文件目录则是/u05/oracle/app/oracle/fast_recovery_area中
    接下来是对应的init文件与TNS信息
    Primary端的init主要信息
    db_unique_name='PRIMARY'
    fal_client='PRIMARYSV'
    fal_server='STANDBYSV'
    log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
    log_archive_dest_1='location=/u04/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=PRIMARY'
    log_archive_dest_2='service=STANDBY ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=STANDBY'
    log_archive_dest_state_1='enable'
    log_archive_dest_state_2='enable'
    db_file_name_convert='/u05/oracle/app/oracle/oradata/dbacoe','/u03/app/oracle/oradata/dbacoe',/u05/oracle/app/oracle/oradata/red','/u04/app/oracle/redundancy'
    log_file_name_convert='/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog','/u04/app/oracle/fast_recovery_area/DBACOE/archivelog'
    Standby端的init信息
    log_archive_config='DG_CONFIG=(PRIMARY,STANDBY)'
    db_unique_name='STANDBY'
    db_file_name_convert='/u03/app/oracle/oradata/dbacoe','/u05/oracle/app/oracle/oradata/dbacoe','/u04/app/oracle/redundancy','/u05/oracle/app/oracle/oradata/red'
    log_file_name_convert='/u04/app/oracle/fast_recovery_area/DBACOE/archivelog','/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog'
    log_archive_dest_1='location=/u05/oracle/app/oracle/fast_recovery_area/DBACOE/archivelog VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=STANDBY'
    log_archive_dest_state_1=enable
    log_archive_format=log%t_%s_%r.arc
    log_archive_dest_2='SERVICE=PRIMARYSV ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
    log_archive_dest_state_2=enable
    TNS信息如下(均能tnsping通)
    PRIMARYSV =
    +(DESCRIPTION =+
    +(ADDRESS = (PROTOCOL = TCP)(HOST = db1.ad.xxxxxx.com)(PORT = 1521))+
    +(CONNECT_DATA =+
    +(SERVER = DEDICATED)+
    +(SERVICE_NAME = dbacoe)+
    +)+
    +)+
    STANDBYSV =
    +(DESCRIPTION =+
    +(ADDRESS = (PROTOCOL = TCP)(HOST = db2.ad.xxxxx.com)(PORT = 1529))+
    +(CONNECT_DATA =+
    +(SERVER = DEDICATED)+
    +(SERVICE_NAME = dbacoe)+
    +)+
    +)+
    PS:请大家花费一点点时间阅读一下这冗长的段子,刚开学data guard,参数上设置都很生疏,(光照着文档做了,是否有redo log相关的操作遗漏?)敬请指教
    Edited by: 961394 on Dec 10, 2012 1:52 AM
    Edited by: 961394 on 2012-12-10 上午4:58

    结贴了,感谢maclean一群的Jesse Lui帮我解决问题

  • 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

  • Backups on Physical standby database?

    I am using dataguard and a physical standby database.How to assign backups on physical standby database to reduce the load on Primary database.
    environment: windows
    Database version:11.2.0.1.0
    What are the pro and cons on assigning RMAN backups jobs to physical standby database?

    Is it better to assign the RMAN backups on standby?i am using the RMAN catalog.Yes, Already mentioned to reduce contention on primary. You can register even standby.
    Do i need to change the setting to backup archive logs from standby database? If i won't backup the archive logs on Primary the FRA will be full and i can't access it ?You can include even archive logs with your database backup.
    How to assign the archive logs backups,full backup on standby database?Same script will work, Before that cancel MRP and after backup start MRP. That should be fine.
    Recently i tested backup from standby and restore, Please see below log.
    =================================================================================================
    Backup Scrpts:-
    =================================================================================================
    RMAN> run
    2> 3> ALLOCATE CHANNEL dev11 type disk;
    4> backup as compressed backupset
    5> format '/home/oracle/backup/DBF_FULLCOLD_BKP_%s'
    6> filesperset 30
    7> (database);
    backup current controlfile format
    8> 9> '/home/oracle/backup/CTL_FULLCOLD_BKP_%s';
    RELEASE CHANNEL dev1;
    RELEASE CHANNEL dev2;
    10> 11> 12> }
    using target database control file instead of recovery catalog
    allocated channel: dev11
    channel dev11: SID=1 device type=DISK
    Starting backup at 03-FEB-13
    Starting implicit crosscheck backup at 03-FEB-13
    Finished implicit crosscheck backup at 03-FEB-13
    Starting implicit crosscheck copy at 03-FEB-13
    Crosschecked 4 objects
    Finished implicit crosscheck copy at 03-FEB-13
    searching for all files in the recovery area
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/orcl/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/orcl/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/orcl/undotbs01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/orcl/users01.dbf
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:03:57
    channel dev11: starting compressed full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    including current control file in backup set
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_24 tag=TAG20130203T192535 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:00:02
    Finished backup at 03-FEB-13
    Starting backup at 03-FEB-13
    channel dev11: starting full datafile backup set
    channel dev11: specifying datafile(s) in backup set
    including current control file in backup set
    channel dev11: starting piece 1 at 03-FEB-13
    channel dev11: finished piece 1 at 03-FEB-13
    piece handle=/home/oracle/backup/CTL_FULLCOLD_BKP_25 tag=TAG20130203T192939 comment=NONE
    channel dev11: backup set complete, elapsed time: 00:00:03
    Finished backup at 03-FEB-13
    released channel: dev11
    =================================================================================================
    Backup Files:-
    =================================================================================================
    [oracle@oracle-stby backup]$ ls -ltr
    total 364572
    -rw-r----- 1 oracle oinstall 361684992 Feb  3 19:29 DBF_FULLCOLD_BKP_23
    -rw-r----- 1 oracle oinstall   1163264 Feb  3 19:29 DBF_FULLCOLD_BKP_24
    -rw-r----- 1 oracle oinstall  10092544 Feb  3 19:29 CTL_FULLCOLD_BKP_25
    [oracle@oracle-stby backup]$
    =================================================================================================
    Restore CONTROL FILE:-
    =================================================================================================
    RMAN> restore controlfile from '/home/oracle/backup/CTL_FULLCOLD_BKP_25';
    Starting restore at 03-FEB-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/u02/app/oracle/oradata/orcl/control01.ctl
    output file name=/u02/app/oracle/flash_recovery_area/orcl/control02.ctl
    Finished restore at 03-FEB-13
    RMAN> sql 'alter database mount';
    sql statement: alter database mount
    released channel: ORA_DISK_1
    RMAN>
    =================================================================================================
    Restore Database:-
    =================================================================================================
    RMAN> restore database;
    Starting restore at 03-FEB-13
    Starting implicit crosscheck backup at 03-FEB-13
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=19 device type=DISK
    Crosschecked 2 objects
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
    Sun Feb 03 19:37:47 2013
    Checker run found 4 new persistent data failures
    Sun Feb 03 19:38:40 2013
    Full restore complete of datafile 3 /u01/app/oracle/oradata/orcl/undotbs01.dbf.  Elapsed time: 0:00:56
      checkpoint is 1595132
      last deallocation scn is 1519218
      channel ORA_DISK_1: piece handle=/home/oracle/backup/DBF_FULLCOLD_BKP_23 tag=TAG20130203T192535
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:07
    Finished restore at 03-FEB-13
    RMAN>
    =================================================================================================
    Open Database:-
    =================================================================================================
    SQL> alter database open resetlogs;
    Database altered.
    SQL> select open_mode,database_role from v$database;
    OPEN_MODE            DATABASE_ROLE
    READ WRITE           PRIMARY
    SQL>Edited by: CKPT on Feb 21, 2013 11:24 PM

  • Failover To Physical Standby Database

    We have 3 node RAC 11.2.0.3 Primary database data guarded to a 3 node RAC 11.2.0.3 Standby database. There is an activity scheduled to perform some of order extracts in the database which is going to result in a lot of changes. Currently the discussion is on whether what should be the quickest way to go back to a point in time before the extract process starts in case of any issues. The options that we are looking at are:
    1) Create a guaranteed restore point on both the Primary and Standby and use this to flashback the database (Quick but we have had issues where in the guaranteed restore point still does not guarantee the availability of the flashback logs) - Tested
    2) Use RMAN backup from a day before to restore and recover to point in time before the extract process began (Time consuming) - Tested
    3) Use export backup to perform a redirected restore i.e import the data from before the extract process (Time consuming) - Tested
    4) Create a guaranteed restore point on both Primary and Standby, stop the Redo Apply/Ship at the time we create the guaranteed restore point and at a point we face some issue and need to go back, simply failover to the physical standby database and then reinstate the new standby database - This has not been tested yet but seems a viable option
    With regard to the point 4, note that we are not concerned about data loss as the whole point of stopping the redo apply is to prevent the standby to be caught up with Primary during the run of the extract process. The question is whether the dataguard broker will allow failover of the primary to standby, in a situation described in bullet point 4). Please advice.

    HI,
    Please check this link:
    Physical Standby Database SWITCHOVER &amp;amp; FAILOVER Operations | Talip Hakan Ozturk&amp;#039;s ORACLE BLOG
    Thank you

  • Goldengate replicate physical standby database

    Friends,
    I did not get a answer in data guard place
    Could we use oracle golden gate  to replicate a data guard  physical standby database into a  new logical database?
    Or we must replicate data guard primary database into a new logical database?
    Thanks
    newdba

    Thanks for your help. In the physical standby database, the log_mode shows archive log. per your statement, we can configure  golden gate Extract parameter TRANLOGOPTIONS with the ARCHIVEDLOGONLY option to replicate physical standby database into new customer DB.
    But I have  other question, As I understand, data guard physical standby database requested the same as primary database.
    If you install golden gate in physical standby database host, are there any issue for data guard configuration?
    Thanks
    newdba

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

  • How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

    Hi,
    Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
    DB : 11.2.0.2
    OS : RHEL5
    RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
    Thanks in Advance..

    Hi;
    Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
    DB : 11.2.0.2
    OS : RHEL5I had similar issue, what i did
    1. Used source oracle_home on standby server
    2. Created new asm instance and use same naming
    3. I took RMAN full backup on source and move it to target
    4. I edit initora file remove RAC setting and restore db(also edited listener file)
    Regard
    Helios

Maybe you are looking for