Standby database open to test

Hi.
I's needed to activate some physical standby databases in the DR site to test if the applications are working correctly. Everthing ran correctly, only I have an one problem:
When the DataGuard was synchronized, this does correctly:
Ex.
Prod database
select max(sequence#) from v$log_history; Max sequence: 115
Standby database
select max(sequence#) from v$log_history; Max sequence: 114
But in OEM - DataGuard monitoring page indicate me the sequence that the database advanced during the tests and not the sequence in wich really the standby database goes.
How can I solve this issue?
Thanks

Hi Hemant.
I's followed the steps of "12.6 Using a Physical Database for Read/Write testing and reporting (Oracle Data Guard concepts and Administration guide)" and in this guide have a note for first make a guaranteed restore point, then activate the standby db and after the test restore to this point.
All the steps is running correctly but when I check in the Data guard status pages on the OEM, the *'Last received log'* column have the last sequences generated during the test and in the *'Last applied log'* column have a zero, but if I check with the next sql query in the standby database:
sql> select max(sequence#) from v$log_history;
have the sequence correctly; before I was do the steps to synchronize with the primary database.
I's make a clean of the agents on both servers, the same data.
After the some day, the databases are synchronize.

Similar Messages

  • Using LOGMNR on Standby Database

    We are running Solaris 8 9i Release 1 Patchset 3
    databases. I have a primary database and
    a delayed mode Data Guard standby in Managed Recovery mode.
    What I want to do is use the Standby to mine the Primary's Logs via LOGMNR, however I don't want to initialize the Standby. From what I recall, you can run LOGMNR against a Mounted Database rather than an OPEN READ WRITE database. Here are my questions:
    1. Can LOGMNR be run on a Standby Database opened in READ ONLY mode?
    2. Can LOGMNR be run on a Mounted Standby?
    3. Can I analyze the Primary Logs currently being Transferred and subsequently applied to the Standby?
    Obviously, I could test these one-by-one, but I thought I'd start here first. Any help would be appreciated.
    Best Regards,
    James Colestock
    OCP Oracle DBA
    Portland State University

    No this to my knowlewdge is not true.
    The DBID is created upon creation of the database. If you duplicate your database quick and dirty, you would probably simply copy the control file to a different server, assure that all mounting points and pathes are the same than on production and perform a restore and recovery based on the production backup sets and archive logs. This then would result in a complelety identical database, including the DBID.
    If you need to change the DBID because you did a manual duplication as indicated above and want to register the new database with a recovery catalog, this then would force you to utilize the dbnewid tool to overwrite the DBID.
    If you duplicate your database using the RMAN duplicat command, RMAN will assing a new DBID, so this then is the clean way. Using the RMAN frees you from any headache related to the DBID.
    Best regards,
    Jürgen

  • Active data guard standby database

    Hello,
    we have to choose which technology to use for maintain Oracle backup center synchronized with main center. This backup center should be read only, and data generated in main should be replicated into backup. So I would like to use Active Data Guard, but I have a possible issue with reading in backup center, because reading is not just select, but filling(inserting data) some temporary tables (from client side, and from procedures in database). Will Standby database in backup center allow this if Active Data Guard is used. We would go with Oracle 11gR2.
    Also other suggestions on replication technologies (I know there are RAC, ADG, Oracle Streams, Golden Gate), or any document which would help us decide which of these technologies would suit our needs the best.
    Thank You.

    Hi,
    user12121832 wrote:
    we have to choose which technology to use for maintain Oracle backup center synchronized with main center. This backup center should be read only, and data generated in main should be replicated into backup. So I would like to use Active Data Guard, but I have a possible issue with reading in backup center, because reading is not just select, but filling(inserting data) some temporary tables (from client side, and from procedures in database). Will Standby database in backup center allow this if Active Data Guard is used. We would go with Oracle 11gR2. You can use Standby Database to make yours Backup.
    In 11.1 or later you can use feature "Snapshot Standby Databases" if this write on database is temporary (i.e you will not use the new data) and at backup time you not need use Snapshot Standby Database feature.
    A snapshot standby database is a physical standby database that you temporarily convert into an updatable standby database. You can use snapshot standby databases as clones or test databases to validate new functionality and new releases, and when finished you then convert the database back into a physical standby. While running in the snapshot standby database role, it continues to receive and queue redo data so that data protection and the RPO are not sacrificed.
    A snapshot standby database has the following characteristics:
    * A snapshot standby database cannot be the target of a switchover or failover. A snapshot standby database must first be converted back into a physical standby database before performing a role transition to it.
    * A snapshot standby database cannot be the only standby database in a Maximum Protection Data Guard configuration.
    Note:
    Flashback Database is used to convert a snapshot standby database back into a physical standby database. Any operation that cannot be reversed using Flashback Database technology will prevent a snapshot standby from being converted back to a physical standby.
    http://docs.oracle.com/cd/E11882_01/server.112/e17157/unplanned.htm#HAOVW11832
    Also other suggestions on replication technologies (I know there are RAC, ADG, Oracle Streams, Golden Gate), or any document which would help us decide which of these technologies would suit our needs the best.If you need "standby" database opened in read-write all time the best option is to use Golden Gate.
    Regards,
    Levi Pereira

  • Questions regarding creating a physical standby database in 10gR2

    I'm setting up a physical standby database in a test environment using two windows 2003 servers. I was wondering if someone could answer a few questions I'm not too clear on. I've been thru the data guard manual and as much online information as i can find. I may have it working but wanted to post some things I'm not sure I did quite right.
    My tnsnames.ora files.
    On my primary database server:
    # tnsnames.ora Network Configuration File: F:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
    # Generated by Oracle configuration tools.
    PRIMARY =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = SERVER1)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = PRIMARY.MYDOMAIN.com)
    STANDBY =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = SERVER2)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = STANDBY.MYDOMAIN.com)
    On my physical standby database server:
    # tnsnames.ora Network Configuration File: f:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
    # Generated by Oracle configuration tools.
    STANDBY =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = SERVER2)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = STANDBY.MYDOMAIN.com)
    PRIMARY =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = SERVER1)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = PRIMARY.MYDOMAIN.com)
    My Listener.ora files:
    On my primary database server:
    # listener.ora Network Configuration File: F:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = PRIMARY.MYDOMAIN.com)
    (ORACLE_HOME = f:\oracle\product\10.2.0\db_1)
    (SID_NAME = primary)
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = server1.mydomain.com)(PORT = 1521))
    On my physical standby database server:
    # listener.ora Network Configuration File: f:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
    # Generated by Oracle configuration tools.
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = standby.mydomain.com)
    (ORACLE_HOME = f:\oracle\product\10.2.0\db_1)
    (SID_NAME = standby)
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = sever2.mydomain.com)(PORT = 1521))
    The next item I'm not sure about is after creating the control file for standby use.
    One the primary server I created it using:
    alter database create standby controlfile as 'sbcontrol01.ctl';
    I copied the primary database pfile I had created earlier to the standby server, renamed it and edited it.
    Initially I left the CONTROL_FILES= parameter pointing to the control01.ctl, control02.ctl and control03.ctl that I restored. But I was getting the error ORA-01665: control file is not a standby control file
    So I copied the sbcontrol01.ctl to sbcontrol02 and sbcontrol03.ctl and pointed the CONTROL_FILES= parameter at them.
    The error went away and the database came up. I still need to test it some more but wanted to see if what i did was correct or a fluke.
    Edited by: tjohnson on Mar 23, 2009 2:26 PM

    If in the primary I had control files named control01, control02 and control03 would I have been able to create a standby controlfile called control01.ctl or would I have had to name it something else like I did (sbcontrol01.ctl) and rename it to control01.ctl once I got it over to the standby database server?Suppose you have the primary database control file in C:\oracle\primary\control location with names control01.ctl and control02.ctl. Then also you can create a standby controlfile with control01.ctl and control02.ctl , but then the location to be created must be different.You can create it in C:\oracle\primary location and then transfer to the specified location mentioed in the pfile of the standby database and mount the standby database.
    But saying this i would suggested to keep the name different from control01.ctl as far as naming conventions are followed.It might confuse someoe whether its a primary database controlfe or a standby database controlfile.Usally primary database controlfile are named control01.ctl , coltrol02.ctl etc and for standby many do prefer keeping standby01.ctl, standby02.ctl.Thats just for for understanding.
    HTH
    Anand

  • Standby database not working after reinstallation of oracle in primary DB

    Hello All,
    Initially I had setup primary database (DB1) and Standby database (DB2), for test environment.
    In DB1 I had got ORA-600 error. So, after I researched, I came to know that I need to apply some patches. But I reinstalled oracle in DB1. And the problem was solved in DB1.
    After that, I issued the following commands in DB2, but I got error
    SQL>SHUTDOWN IMMEDIATE;
    ORA-01034: Oracle not available
    ORA-27101: shared memory realm does not exist
    SQL>STARTUP MOUNT;
    ORA-27102: out of memoryNow, I mean to say, both DB1 and DB2 are independent.
    Also, DB2 is not active since 2 months
    DB1 is working fine.
    Please guide me with procedure, how to configure DB2 for the current DB1

    Hello;
    After two months I would rebuild.
    If you are on Oracle 11 you can use RMAN to do this quickly.
    Here's a few short notes :
    http://www.visi.com/~mseberg/duprman2.html
    http://www.visi.com/~mseberg/standby_creation_from_active_database_using_rman.html
    Can you post your full oracle version and Primary database size?
    If you rebuild I would remove all the data files from the Standby, recopy the password file from the Primary to the Standby and double my tnsnames.ora and listener.ora on both servers.
    Best Regards
    mseberg

  • Standby database creating error oracle 10g

    Hi
    i created standby database,but i cannot access primary database data. the standby database opened read only.
    but i cannot access data from primary.so i check query in standby database,
    SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    no rows selected.
    what i mistake
    Regards
    S.Azar

    It you are not seeing any errors in the primary alert log, then I think that you have defined log_archive_dest_2 to use LOCATION instead of SERVICE. Archive logs have to be transmitted through Oracle Net in order to be automatically registered by the standby database.
    Hope this helps.
    Regards,
    Satishbabu Gunukula
    http://oracleracexpert.blogspot.com
    [Backup and Recovery of OCR|http://oracleracexpert.blogspot.com/2009/08/backup-and-recovery-of-ocr-oracle.html]

  • Error while trying to open physical standby database - (DATA GUARD)

    Hi Everyone,
    I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
    Primary Database spec: (2 Node Rac on ASM)
    Oracle Version : 10.2.0.3.0
    O/s : HP-UX B.11.23
    Standby Database spec: (Single Node)
    Oracle Version : 10.2.0.3.0
    O/s: HP-UX db01 B.11.23
    Error:
    alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database open
    2 ;
    alter database open
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
    Parameters :
    log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
    FOR=(ONLINELOGFILES,PRIMARY_
    ROLE) DB_UNIQUE_NAME=PROD
    remote_archive_enable string true
    fal_client string DPROD
    fal_server string PROD1, PROD2
    Steps tried so far:
    Changed log_archive_dest_2 = DEFER on both the primary nodes
    Standby :
    startup nomount
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    alter database recover managed standby database cancel;
    alter database open/readonly (tried both)
    Same error.
    On Primary:
    SQL> select max(sequence#) from v$log_history;
    MAX(SEQUENCE#)
    55702
    on Standby:
    MAX(SEQUENCE#)
    33289
    Primary Database:
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    55700 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55702 13-JUN-11 13-JUN-11
    60824 rows selected.
    Standby Database:
    SEQUENCE# FIRST_TIME NEXT_TIME
    55698 13-JUN-11 13-JUN-11
    55699 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    15206 rows selected.
    Additional Information :
    There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
    Any help will be highly appreciated. Thanks in advance
    Sadiq

    Hi,
    Primary Database:
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    STATUS CHECKPOINT_COUNT
    ONLINE 57717
    ONLINE 57717
    57 rows selected.
    Standby Database;
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    STATUS CHECKPOINT_COUNT
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    STATUS CHECKPOINT_COUNT
    ONLINE 30723
    ONLINE 30723
    57 rows selected.
    Archieve log list :
    Primary database:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 49111
    Current log sequence 49111
    Standby Database:
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 0
    Current log sequence 49111
    I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

  • How to open a standby database for use?

    First, let me state that I am not a DBA nor am I a systems guy; I'm a software developer.
    At work, we recently built a new virtualized db server by cloning our disaster recovery (DR) database server. The DR database was kept in 'standby' mode (I think that's the correct term) and was synched with production daily via archive logs.
    So now, we have this new virtualized server that has a clone of that 'standby' database on it, and I need to 'open' that database so that it's usable (ie, no longer a standby db). How do I do that?? We recently lost our DBA so this has fallen into my lap.
    From searching the web, I've found all sorts of instructions. It seems that I need to issue some commands via SQL*Plus? But as what user? From where do I issue these commands (I assume from the virtualized server)? And what are the commands?
    This is Oracle 10g v10.2.0.3.0 running on Solaris 10 for x86.
    Thanks!
    Dave

    Hi Dave, I do this each time we do a DR test. I have 10.2.0.3 in physical standby mode.
    First, I make sure I have flashback turned on (here is what I've done):
    connect / as sysdba
    startup nomount
    alter database mount standby database;
    alter database flashback on;
    alter database recover managed standby database through all switchover disconnect using current logfile;
    exit;Activate the physical standby:
    alter database recover managed standby database cancel;
    alter database activate physical standby database;
    alter database open;
    exit;When completed with DR test we return the database back to physical standby mode:
    Find the SCN when the physical standby was activated (this is so we can flashback to that point in time)
    select standby_became_primary_scn from v$database;connect / as sysdba
    flashback database to scn <this is the value returned from above>;
    alter database convert to physical standby;
    shutdown immediate
    startup mount
    alter database recover managed standby database disconnect from session;
    exit;I hope that helps,
    Michael Cunningham
    Edited by: Michael C on Nov 10, 2011 8:59 AM
    Edited by: Michael C on Nov 10, 2011 9:00 AM

  • Opening a Standby Database in Read-Only mode

    Is there anyway to open a Standby database up to date as of a certain time? I'm currently using the 2 commands to get close to the time required.
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Such as, similar to this? RECOVER DATABASE UNTIL TIME '2012-01-25:15:00:00';
    We're on 11.1.0.7, which I'm currently very unhappy with.
    Thanks for any help, as my google-fu hasn't worked today.
    James

    Maybe
    I did a quick test :
    8:42 open the databases and start recovery
    8:43 check status from primary
    Shows sequence 75
    and "TO STANDBY" for switchover status
    Did log switches at 8:44, 8:45, and 8:46
    8:50
    SQL> alter database recover managed standby database cancel;
    SQL> RECOVER STANDBY DATABASE UNTIL TIME ' 2012-01-25:20:43:00';
    Media recovery complete.
    SQL>
    8:52
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    Check status
    TO STANDBY and sequence 78Still need to check alert logs and do another log switch. It checks out so the quick test works.
    However the quick test is incomplete since there was no before and after data in the test and the time period was very short.
    Andy may be right, but I would test, test test. ( if you do please let us know the results )
    Thanks Andy!
    Best Regards
    mseberg
    Later
    After sleeping on this I decided my first thought is probably correct. You cannot go back in time and still be in sync. While the test statement did not error or produce any alert log entries, it probably did nothing. Oracle is smart enough to know you cannot have your Cake and eat it too.

  • Test physical standby database in dataguard

    Hi all,
    I had a successfull dataguard implementation for oracle 9r2.
    Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
    As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
    Now i want to test physical standby database with applications tier  but don't want to disturb origional primary database.
    as these are the normal switchover steps
    1) at primary db
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
    2) at standby
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
    3) at primary, now this will be the stand by database
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    4) at standby, now this will be the primary database
    SHUTDOWN IMMEDIATE;
    STARTUP
    My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
    Regards,
    Ken

    To avoid touching the primary production DB, you may try to use the following command on your standby database side:
    alter database activate standby database;
    This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
    Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

  • DBhanging in open stage after creating physical standby database

    alter database open read only hanging after creating the standby database using rman.

    hi,
    when i starts the database in restricted mode it is asking resetlogs;
    when i openthe database using the
    alter database open resetlogs;
    it is showing following errors
    alter database open RESETLOGS
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00338: log 1 of thread 1 is more recent than control file
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    RESETLOGS after complete recovery through change 28393568059
    Resetting resetlogs activation ID 3821641494 (0xe3c99f16)
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 1 of thread 1 is not current copy
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    Thu Feb 24 20:05:42 2011
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00316: log 1 of thread 1, type 0 in header is not log file
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 2 of thread 1 is not current copy
    ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 3 of thread 2 is not current copy
    ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 4 of thread 2 is not current copy
    ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 2 of thread 1 is not current copy
    ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
    Thu Feb 24 20:05:58 2011
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 3 of thread 2 is not current copy
    ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 4 of thread 2 is not current copy
    ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
    thanks in advance

  • Error during open standby database in read only mode

    hi,
    alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u02/app/oracle/oradata/standby/system01.dbf'
    Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
    what is the reason of this.
    Thanks in advance.

    thanks for your reply.
    [oracle@standby admin]$ cat listener.ora
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    LISTENER_STANDBY =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.124)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME =/opt/app/oracle/product/11.2.0/db_1)
    (PROGRAM = extproc)
    tnsfile
    [oracle@standby admin]$ cat tnsnames.ora
    standby =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.124)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby)
    ora11g =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST =10.105.1.120)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = ora11g)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.105.1.120)(PORT = 1521))
    EXTPROC_CONNECTION_DATA =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    (CONNECT_DATA =
    (SID = PLSExtProc)
    (PRESENTATION = RO)
    pfile
    [oracle@standby standby]$ cat initstandby.ora
    ora11g.__db_cache_size=130023424
    ora11g.__java_pool_size=4194304
    ora11g.__large_pool_size=4194304
    ora11g.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    ora11g.__pga_aggregate_target=146800640
    ora11g.__sga_target=276824064
    ora11g.__shared_io_pool_size=0
    ora11g.__shared_pool_size=121634816
    ora11g.__streams_pool_size=8388608
    *.audit_file_dest='/u01/app/oracle/admin/ora11g/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.1.0'
    #*.control_files='/u02/app/ora11g/oradata/ora11g/control01.ctl','/u01/app/oracle/flash_recovery_area/ora11g/control02.ctl'
    *.db_block_size=8192
    *.db_domain=''
    *.db_name='ora11g'
    *.db_recovery_file_dest='/opt/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=4039114752
    *.diagnostic_dest='/opt/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=ora11g)'
    *.memory_target=2016M
    *.open_cursors=300
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.undo_tablespace='UNDOTBS1'
    *.audit_file_dest='/opt/app/oracle/admin/standby/adump'
    *.audit_trail=none
    #*.background_dump_dest='/opt/app/oracle/admin/standby/bdump'
    #*.compatible='10.2.0.2.0'
    #*.control_files='/opt/app/oracle/oradata/standby/control01.ctl'
    #,'/opt/app/oracle/oradata/standby/control02.ctl','/opt/app/oracle/or
    *.control_files='/u02/app/oracle/oradata/standby/control_sb01.ctl'
    #,'/u02/app/oracle/oradata/standby/control_02.ctl','/u02/app/oracle/oradata/standby/control_03.ctl'
    *.core_dump_dest='/u01/app/oracle/diag/rdbms/standby/standby/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    #*.db_name='standby'
    #*.dispatchers='(PROTOCOL=TCP) (SERVICE=standby)'
    *.job_queue_processes=10
    *.log_archive_dest_1='location=/opt/app/oracle/arch'
    *.log_archive_config='dg_config=(standby,ora11g)'
    *.log_archive_dest_1='LOCATION=/opt/app/oracle/oradata/standby/archivelog'
    *.log_archive_dest_2='service=orcl valid_for=(online_logfiles,primary_role) db_unique_name=ora11g'
    *.log_archive_format='%t_%s_%r.dbf'
    *.standby_file_management=auto
    *.db_unique_name =standby
    *.fal_server='ora11g'
    *.fal_client='standby'
    *.service_names='standby'
    *.open_cursors=300
    *.pga_aggregate_target=525336576
    *.processes=1500
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=1576009728
    *.undo_management='AUTO'
    *.undo_tablespace='undotbs02'
    #*.user_dump_dest='/opt/app/oracle/diag/rdbms/standby/standby/trace'
    *.standby_file_management ='manual'
    *.instance_name =standby
    #*.standby_archive_dest=/opt/app/oracle/oradata/standby/archivelog
    *.db_file_name_convert=(/u02/app/ora11g/oradata/ora11g,/u02/app/oracle/oradata/standby)
    *.log_file_name_convert='/u02/app/ora11g/oradata/ora11g','/u02/app/oracle/oradata/standby'
    #*.remote_listener=LISTENER_ora11g

  • 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

  • Cannot open standby database in read only....

    i do the following procedure on my standby database
    ORACLE 9.2.0.7
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 538412112 bytes
    Fixed Size 742480 bytes
    Variable Size 402653184 bytes
    Database Buffers 134217728 bytes
    Redo Buffers 798720 bytes
    SQL> lter database mount standby database;
    SP2-0734: unknown command beginning "lter datab..." - rest of line ignored.
    SQL> alter database mount standby database;
    Database altered.
    SQL> SQL> recover standby database until cancel;
    ORA-00279: change 4274363673 generated at 09/18/2006 11:25:08 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9135.arc
    ORA-00280: change 4274363673 for thread 1 is in sequence #9135
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 4275275613 generated at 09/18/2006 14:03:09 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ORA-00280: change 4275275613 for thread 1 is in sequence #9136
    ORA-00278: log file '/u12/oradata/dbadmon/arch/dbadmon9135.arc' no longer
    needed for this recovery
    ORA-00308: cannot open archived log '/u12/oradata/dbadmon/arch/dbadmon9136.arc'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    THEN i check in the alert...
    Errors in file /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc:
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Mon Sep 18 13:59:16 2006
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Instance terminated by USER, pid = 24028
    ORA-1092 signalled during: alter database open read only...
    followed by the trace file...
    /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    ORACLE_HOME = /u00/oracle/product/9.2.0.1
    System name: AIX
    Node name: eserver1
    Release: 1
    Version: 5
    Machine: 000651FA4C00
    Instance name: dbadmon
    Redo thread mounted by this instance: 1
    Oracle process number: 14
    Unix process pid: 24028, image: oracle@eserver1 (TNS V1-V3)
    *** SESSION ID:(11.1) 2006-09-18 13:58:57.859
    Start recovery at thread 1 ckpt scn 4274363673 logseq 9135 block 2
    *** 2006-09-18 13:59:00.215
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9135.arc
    *** 2006-09-18 13:59:11.868
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 27062Kb in 13.99s => 1.86 Mb/sec
    Longest record: 8Kb, moves: 22/97639 (0%)
    Change moves: 43706/193539 (22%), moved: 4Mb
    *** 2006-09-18 13:59:14.688
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Current SQL statement for this session:
    select /*+ rule */ name,file#,block#,status$,user#,undosqn,xactsqn,scnbas,scnwrp,DECODE(inst#,0,NULL,inst#),ts#,spare1 from undo$
    where us#=:1
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp+0148 bl ksedst 1029170CC ?
    ksfdmp+0018 bl 01FD771C
    kgeriv+0118 bl _ptrgl
    kgesiv+0080 bl kgeriv FFFFFFFFFFEBEF0 ? 080000000 ?
    101A6C640 ? 000000000 ?
    FFFFFFFFFFEBE70 ?
    ksesic5+005c bl kgesiv 70000000E517A78 ?
    70000000E517748 ?
    Can anyone gie me a hand please???
    Thanks in advance.

    Doc ID: Note:1038418.6
    Please check permissions on dump desitnation directory.
    Also check if dual table is present.

  • Standby database errors - Alter database open read only

    alter database open read only
    AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
    Signalling error 1152 for datafile 1!
    Beginning standby crash recovery.
    Serial Media Recovery started
    Managed Standby Recovery starting Real Time Apply
    Media Recovery Waiting for thread 1 sequence 216
    Mon Dec 20 11:58:18 2010
    Standby crash recovery need archive log for thread 1 sequence 216 to continue.
    Please verify that primary database is transporting redo logs to the standby database.
    Wait timeout: thread 1 sequence 216
    Standby crash recovery aborted due to error 16016.
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!
    Completed standby crash recovery.
    Signalling error 1152 for datafile 1!
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    ORA-10458 signalled during: alter database open read only...
    Mon Dec 20 12:13:46 2010
    ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    Attempt to start background Managed Standby Recovery process (MDM2)
    Mon Dec 20 12:13:46 2010
    MRP0 started with pid=23, OS id=18974
    MRP0: Background Managed Standby Recovery process started (MDM2)
    started logmerger process
    Mon Dec 20 12:13:51 2010
    Managed Standby Recovery starting Real Time Apply
    Parallel Media Recovery started with 2 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 216
    Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    The above lines are from alert log of standby database.
    Standby standbase
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    Parameters set on primary are
    log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
    log_archive_dest_state_1 ENABLE
    log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
    log_archive_dest_state_2 ENABLE
    dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
    dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
    fal_server MDM2
    standby_file_management AUTO
    log_archive_config dg_config=(MDM1,MDM2)
    db_file_name_convert MDM2, MDM1
    ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
    Standby pfile
    *.archive_lag_target=900
    *.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='+MDMDG1'
    *.db_domain=''
    *.db_file_name_convert='MDM1','MDM2'
    *.db_name='MDM'
    *.db_recovery_file_dest='+MDMDG2'
    *.db_recovery_file_dest_size=10485760000
    *.db_unique_name='MDM2'
    *.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
    *.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
    *.fal_server='MDM11','MDM12'
    *.instance_name='MDM2'
    *.log_archive_config='dg_config=(MDM1,MDM2)'
    *.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
    *.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='MDM_%t_%s_%r.arc'
    *.log_file_name_convert='MDM1','MDM2'
    *.memory_target=838860800
    *.nls_language='ENGLISH'
    *.nls_territory='UNITED KINGDOM'
    *.open_cursors=300
    *.processes=500
    *.remote_login_passwordfile='exclusive'
    *.sessions=555
    *.standby_file_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    On standby ASM
    ASMCMD [+] > find * *
    +MDMDG1/ASM/
    +MDMDG1/ASM/ASMPARAMETERFILE/
    +MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
    +MDMDG1/MDM/
    +MDMDG1/MDM2/
    +MDMDG1/MDM2/CONTROLFILE/
    +MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
    +MDMDG1/MDM2/CONTROLFILE/current.265.738243333
    +MDMDG1/MDM2/DATAFILE/
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
    +MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
    +MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
    +MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
    +MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
    +MDMDG1/MDM2/DATAFILE/USERS.278.738243347
    +MDMDG1/MDM2/ONLINELOG/
    +MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
    +MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
    +MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
    +MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
    +MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
    +MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
    +MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
    +MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
    +MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
    +MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
    +MDMDG2/MDM/
    +MDMDG2/MDM/DG_CONFIG/
    +MDMDG2/MDM2/
    +MDMDG2/MDM2/AUTOBACKUP/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
    +MDMDG2/MDM2/CONTROLFILE/
    +MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
    +MDMDG2/MDM2/CONTROLFILE/current.271.738243335
    +MDMDG2/MDM2/ONLINELOG/
    +MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
    +MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
    +MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
    +MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
    +MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
    +MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
    +MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
    +MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
    +MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
    +MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
    +MDMDG3/MDM/
    +MDMDG3/MDM/ARCH/
    +MDMDG3/MDM2/
    +MDMDG3/MDM2/ARCH/
    -- Please can I know how to open read only standby database.

    user5846399 wrote:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!archived log for thread 1 sequence# 216
    This file is needed for recovery, Find it and move it to the standby database side.

Maybe you are looking for