Primary RAC physical standby

Hi all

We plan to set up physics in waiting for our CARS database. Can anyone let us know how config in the case of RAC database? Also after you set up the night before with the protection mode max is possible to change physical Snapshot standby standby for our app objective test team?

RDS,

Varun

Hi Varun,

I recently put in place an environment of two RAC nodes to a custodian of data environment is only a single node. Nothing very special when configuring Data Guard in a CCR environment. The most important thing is that each RAC instance must send waiting for BD archivers.

This setting is configured the destination archive database pending.

Once the archivers reach the Data Guard environment are applied correctly and consistently to the comics of the day before.

You have this MOS score that helps the creative process.

Create a sleep using RMAN Duplicate (RAC or Non-RAC) (Doc ID 1617946.1)

Yes, you can convert the Standby database to a snapshot of BD, are supported read/write operations.

Use the command alter database convert on the eve of the snapshot;

And when people apps to complete the test, convert it to sleep with the command:

ALTER database convert physical standby;

And the standby for the role of sleep and if you turn on the AutoRecover apply all redo it in anticipation of is to apply because you put the backup database into the snapshot mode.

Is very powerful and easy.

I hope to help.

Best regards

Arturo

Tags: Database

Similar Questions

  • How to check if physical Standby is in phase with the primary

    Hi all

    I'm new in Data Guard. In our current production, my boss asked me to write a shell scripts for monitoring physical standby and archive primary's sync (gap of archive)

    I refer metalink [861595.1 ID], but when I ran the first query to the primary node, the screen lock.

    On primary
    ========

    SQL > SELECT THREAD # "Thread", SEQUENCE # 'last generated sequence.
    V $ ARCHIVED_LOG
    WHERE (THREAD #, FIRST_TIME) IN (SELECT THREAD #, MAX (FIRST_TIME) FROM V$ ARCHIVED_LOG GROUP BY THREAD #)
    ORDER BY 1;

    I tried to turn on 10046 trace SQL, SQL consume a lot of CPU and it full table scan in X table KCCAL $.

    Eye of TKPROF result as below:
    call     count       cpu    elapsed       disk      query    current        rows
------- ------  -------- ---------- ---------- ---------- ----------  ----------
Parse        1      0.00       0.00          0          0          0           0
Execute      1      0.00       0.00          0          0          0           0
Fetch        1     88.29     115.59          0          0          0           0
------- ------  -------- ---------- ---------- ---------- ----------  ----------
total        3     88.30     115.60          0          0          0           0

Misses in library cache during parse: 1
Misses in library cache during execute: 1 Optimizer mode: ALL_ROWS Parsing user id: 80  

Rows     Row Source Operation
-------  ---------------------------------------------------
      0  SORT ORDER BY (cr=0 pr=0 pw=0 time=21 us)
      0   FILTER  (cr=0 pr=0 pw=0 time=19 us)
   1124    FIXED TABLE FULL X$KCCAL (cr=0 pr=0 pw=0 time=40537 us)
      0    FILTER  (cr=0 pr=0 pw=0 time=115538625 us)
   1122     HASH GROUP BY (cr=0 pr=0 pw=0 time=115530193 us)
7465972      FIXED TABLE FULL X$KCCAL (cr=0 pr=0 pw=0 time=94648975 us)

Elapsed times include waiting on following events:
  Event waited on                        Times   Max. Wait  Total Waited
  -----------------------------------   Waited  ----------  ------------
  SQL*Net message to client               1        0.00          0.00
  control file sequential read        16841        0.05         30.88
  SQL*Net break/reset to client           1        0.00          0.00
    Because of this is the production environment, so I had put an end to the session, anyone can teach me or share with me the physical monitor in standby mode scripts is sync with primary or not? Or you encounter the above problem when you run the SQL code?

    My version of db is Oracle 11.2.0.1.0


    Thanks in advance.

    Kind regards
    Klnghau

    Just be aware that these queries are queries controlfile and if they run too long can get in the road of the database as they hold controlfile locks. You'd better watch the view v$ dataguard_stats the day before and look at the GAL apply and transport.

    We are also a few scripts in our book - http://www.amazon.com/Oracle-Guard-Handbook-Osborne-ORACLE/dp/0071621113

    Larry

  • Switching between primary CARS and standby instance

    Hi all

    I'm using Oracle 11 g 2.

    I'm redoing a switch between the primary data base (RAC 2 knots) and physical standby (single instance)

    If my primary is the only forum I've followed the steps below:
    On the standby
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;

On the primary database:
alter database commit to switchover to standby with session shutdown;
shutdown immediate;
startup nomount;
alter database mount standby database;

On the standby again:

alter database commit to switchover to primary WITH SESSION SHUTDOWN;

On the new standby:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;
    now, and since my first is CARS when I'm working on switch I get the below error:
    SQL> alter database commit to switchover to standby with session shutdown;
alter database commit to switchover to standby with session shutdown
*
ERROR at line 1:
ORA-01105: mount is incompatible with mounts by other instances
    In addition, when I want to apply the remaining steps (below step), can I do it on every single instance? or is it all still to do using srvctl command:
     
alter database mount standby database;
    Kind regards

    Hello

    Since you are using 2 primary CCR node, so for the failover operation, you need to stop
    instance (instance 2 assuming) database.

    Assume your node1:
    host name is dcpdb1
    and node 2:
    host name is dcpdb2

    and Eve hostname is drpdb1

    Then follow these steps for the digital switchover .

    How to transition from primary school on the eve of the database?

    Process:

    On the principal server, check the log of the last archived redo and force a log switch.

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL > SELECT sequence #, first_time, next_time
    V $ archived_log
    ORDER BY next_time;
    SQL > ALTER SYSTEM SWITCH LOGFILE;

    Check the new archived redo log has arrived on the standby server and is enabled.

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > SELECT sequence #, first_time next_time, applied
    V $ archived_log
    ORDER BY next_time;

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL > SELECT sequence #, first_time, next_time
    V $ archived_log
    ORDER BY next_time;

    SQL > ALTER SYSTEM SWITCH LOGFILE;

    Check the new archived redo log has arrived on the standby server and is enabled.

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > SELECT sequence #, first_time next_time, applied
    V $ archived_log
    ORDER BY next_time;

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    IN THE STANDBY MODE

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    IN THE STANDBY MODE

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    NOT ALLOWED

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL > shutdown immediate
    The database is closed.
    The database is dismounted.
    ORACLE instance stops.
    SQL >

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL > ALTER DATABASE COMMIT to SWITCH STANDBY mode PHYSICS WITH the STOP of the SESSION;

    Database altered.

    SQL >
    SQL > shutdown immediate
    ORA-01507: database not mounted
    ORACLE instance stops.
    SQL >

    SQL > startup mount
    ORACLE instance started.
    System Global area 1.5400E + 10 bytes
    Bytes of size 2184872 fixed
    7751076184 variable size bytes
    7616856064 of database buffers bytes
    Redo buffers 29409280 bytes
    Mounted database.
    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    AT THE ELEMENTARY LEVEL

    SQL >

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    ACTIVE SESSIONS

    SQL > alter database validation at the transition to the primary with the stop of the session;

    Database altered.

    SQL > shutdown immediate
    ORA-01109: database is not open
    The database is dismounted.
    ORACLE instance stops.
    SQL >
    SQL > Startup
    ORACLE instance started.
    System Global area 1.5400E + 10 bytes
    Bytes of size 2184872 fixed
    7717521752 variable size bytes
    7650410496 of database buffers bytes
    Redo buffers 29409280 bytes
    Mounted database.
    Open database.

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL > alter database open read-only;

    Database altered.

    SQL > change recover managed standby database disconnect log file using current;

    Database altered.

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL > startup mount
    ORACLE instance started.

    System Global area 1.5400E + 10 bytes
    Bytes of size 2184872 fixed
    7751076184 variable size bytes
    7616856064 of database buffers bytes
    Redo buffers 29409280 bytes
    Mounted database.
    SQL > alter database open read-only;

    Database altered.

    SQL > change recover managed standby database disconnect log file using current;

    Database altered.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    NOT ALLOWED

    SQL >

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    IN THE STANDBY MODE

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    NOT ALLOWED

    SQL >

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL > SELECT SWITCHOVER_STATUS FROM V$ DATABASE;

    SWITCHOVER_STATUS
    --------------------
    NOT ALLOWED

    SQL >

    * # Complete passage # *.

    Check

    * # Connection as the user Oracle Drpdb1 # *.

    SQL > alter system switch logfile;

    SQL >
    SELECT the sequence #, first_time, next_time
    V $ archived_log
    ORDER BY sequence #.

    SQL > archive log list

    * # Connection as the user Oracle Dcpdb1 # *.

    SQL >
    SELECT the sequence #, first_time next_time, applied
    V $ archived_log
    ORDER BY sequence #.

    SQL > archive log list

    * # Connection as the user Oracle Dcpdb2 # *.

    SQL >
    SELECT the sequence #, first_time next_time, applied
    V $ archived_log
    ORDER BY sequence #.

    SQL > archive log list

    Thank you
    Solaiman

    Published by: 876149 on April 12, 2013 11:51

  • logical standby local and remote physical standby

    Dear all,

    My version of the database is 10.2.0.1.0 (production) and the x 86-64 OS Version Red Hat Enterprise 4 Linux operating system

    Here's my configuration details:

    Rprimary database: two-node RAC

    LOCAL database backup database: autonomous

    Database watch remotely: two node RAC

    So, my question is, I want my local DR physical to convert logical standby and

    Remote DR will work as physical sleep as it IS.



    SQL > EXECUTE DBMS_LOGSTDBY. BUILD

    Will after running the statement above in my primary database production there be any performance HIT.

    And another important thing is that my statement above, should not affect my remote physical Dr.

    Just the local DR should get converted to logic of the standby database


    Thanks and greetings
    Yvon Das

    Yvon says:
    Mr President, thank you very much for your answer...

    Actually in my case I want to be a logical and physical database to aid in total. What I'm trying to tell you, it's that.

    We have already two CARS physical distance DR nodes and a physical local autonomous local DR, a * nd we want to convert the local logical physical DR DR *, * this means I want to keep my DR RAC as physical standby*.so, when we will realize the package on the primary database

    exec dbms_logstdby.build;

    It will cause no problem for my CAR remote physical DR.

    Only local DR must be converted into logic.

    Thanks and greetings
    Yvon Das

    Published by: Yvon March 4, 2013 12:17 AM

    I understand your question completely, you can convert logical physical standby standby either locally or remotely. By running the package it will not impact any performance on the primary production database. By running the package SQL apply will be activated.
    There will be no problem with it. Again, you can have physics or logic of Eve in the same configuration of data protection.

  • Log_archive_format with physical standby

    Oracle RDBMS: 11.2.0.2 (RAC) on RHEL 5.6


    We need to define any particular value for log_archive_format parameter when creating physical database from the night before?

    In our primary, the value of the parameter is log_archive_format = 't_ % s_ % r.dbf % '. Do we need to change it to another value or can leave us like this for the physics of the standby database?

    Number of documents online in various blogs include log_archive_format ='% t_ % s_ % r.arc as well as all the other required parameters for the physical creation of the standby database. I am bit confused, can someone please clarify.


    Thank you

    Hello;

    Do we need to set any particular value for log_archive_format parameter while creating physical standby database?

    N °

    In our primary the parameter value is log_archive_format='% t_% s_% r.dbf'. Do we need to change it to a different value or can we leave it like that for physical standby database?

    I love them the same thing only it gaps check more easily. Yours seems to be the default for Linux.

    SQL> show parameter log_archive_format

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_format                   string      %t_%s_%r.dbf
SQL>

    On all mine, I don't put that and allow you to apply the default value for the parameter.

    Best regards

    mseberg

  • Physical standby Archive newspapers vs

    Hi all

    11 GR 2

    Rhel6.5

    I'm confused how archivelogs be appied physical standby.

    CASES1:

    Assuming I backup my primary Db with RMAN full backup now.,

    then question crosscheck backup and delete obsolete. It will remove all archivelogs not yet taken to the waiting?

    CASE2:

    Right now my database pending is on a mode "real apply", so updates to the primary level is done directly on the eve as well, even if the archive logs have not yet carried.

    Assuming that I will delete archive records at the primary level, such that it cannot carry, will be the sleep EEG 'gaps' in its Archives logs status?

    Your comments are appreciated hightly.

    Thank you very much

    JC

    Read in the mseberg response:

    A way to remove applied log file stored in the backup database

    How to ensure that RMAN is NOT delete archived logs that have not yet shipped to standby [394261.1 ID]

    Kind regards

    Juan M

  • Redolog files to physical standby standby in 11g

    Hi all

    Configure a physical in 11 g standby database on Linux.

    My first question is, Create SRL (Standby Redo Logs)-

    Is - mandatory to set up physical standby?


    If I create SRL , what would be the advantage for the installation of DR?

    If I ignore it, what would be the downside for the installation of DR?


    Hello;

    Laughing out loud

    But it is a good idea.

    If your database pending is in maximum protection or maximum availability mode you need.

    If you use Real Time apply on Standby Database you need.

    If you use cascading Destinations you need.

    If you create both primary and Standby you pass quickly without additional measures or issue.

    Redo Eve can also buffer it again entering.

    Best regards

    mseberg

  • Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

    Here's my question after tons of research and test without have the right solutions.

    Target:

    (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

    (2) I created physical standby database "stbydb" on the server "node2".

    (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

    (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

    (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

    (6) I do RMAN backup (database and archivelog) on the site of relief only.

    (7) I want to use this backup for full restore of the database on the primary database.

    He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

    Here is how to save, on the database pending:

    (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

    (2) RMAN > backup database;

    (3) RMAN > backup archivelog all;

    I got elements of backup and copied to primary db Server something like:

    /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

    /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

    /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

    So here's how to restore, on the main site:

    I clean all the files (data files, controlfiles oder all gone).

    (1) restore spfile from pfile

    RMAN > startup nomount

    RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    (2) modify pfile to convert to db primary content. pFile shows below

    *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

    * .audit_trail = "db".

    * full = '12.1.0.2.0'

    *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

    * .db_block_size = 8192

    * .db_domain = "

    *.db_file_name_convert='/testdb/','/testdb /'

    * .db_name = "testdb".

    * .db_recovery_file_dest ='/ orafra'

    * .db_recovery_file_dest_size = 10737418240

    * .db_unique_name = "testdb".

    *.diagnostic_dest='/opt/Oracle/DB '

    * .fal_server = "stbydb".

    * .log_archive_config = 'dg_config = (testdb, stbydb)'

    * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

    * .log_archive_dest_state_2 = 'ENABLE '.

    *.log_file_name_convert='/testdb/','/testdb /'

    * .memory_target = 1800 m

    * .open_cursors = 300

    * runoff = 300

    * .remote_login_passwordfile = "EXCLUSIVE."

    * .standby_file_management = "AUTO".

    * .undo_tablespace = "UNDOTBS1.

    (3) restart db with updated file pfile

    SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

    SQLPLUS > the judgment

    SQLPLUS > startup nomount

    (4) restore controlfile

    RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

    RMAN > change the editing of the database

    (5) all elements of backup catalog

    RMAN > catalog starts by ' / home/oracle/backupset / '.

    (6) restore and recover the database

    RMAN > restore database;

    RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

    (7) open resetlogs

    RMAN > alter database open resetlogs;

    Everything seems perfect, except one of the file log roll forward pending is not generated

    SQL > select * from v$ standby_log;

    ERROR:

    ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

    ORA-27037: unable to get file status

    Linux-x86_64 error: 2: no such file or directory

    Additional information: 3

    no selected line

    I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

    So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

    And I got the same missing log file.

    The problem is:

    (1) complete alert.log filled with this error, not the concern here

    (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

    (3) I can't delete and re-create this log file

    Then I tried several and found:

    The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

    For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 19 ACTIVE 133632

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    So until I take the backup, I tried on the primary database:

    SQL > alter system set log_archive_dest_state_2 = delay;

    This was the Group of standby_log side Eve #4 was released:

    SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

    GROUP # SEQUENCE # USED STATUS

    ---------- ---------- ---------- ----------

    4 0 0 UNASSIGNED

    5 0 0 UNASSIGNED

    6 0 0 not ASSIGNED

    7 0 0 UNASSIGNED

    Then, the backup has been restored correctly without missing standby logfile.

    However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

    Finally, my real questions come:

    (1) what I do may not do on parameter change?

    (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

    I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

    And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

    I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

    Your idea is very much appreciated.

    Thank you!

    Hello

    1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

    2nd--> when we opened the ORL database should be deleted and created

    3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

    DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

    THREAD # SEQUENCE # GROUP # STATUS

    ---------- ---------- ---------- ----------

    1 233 4 ACTIVE

    1 238 5 ACTIVE

    DR sys@cdb01 SQL > select * from v$ logfile;

    GROUP # STATUS TYPE MEMBER IS_ CON_ID

    ---------- ------- ------- ------------------------------ --- ----------

    3 /u03/cdb01/cdb01/redo03.log no. 0 online

    /U03/cdb01/cdb01/redo02.log no. 0 2 online

    1 /u03/cdb01/cdb01/redo01.log no. 0 online

    4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

    /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

    DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

    DR sys@cdb01 SQL > alter database force claire logfile 4;

    change the database group claire logfile 4

    *

    ERROR on line 1:

    ORA-01156: recovery or current flashback may need access to files

    DR sys@cdb01 SQL > alter database recover managed standby database cancel;

    Database altered.

    DR sys@cdb01 SQL > change the database group claire logfile 4;

    Database altered.

    DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

    -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

    DR sys@cdb01 SQL >

    If you do, you can recreate the controlfile without waiting for redo log entry...

    If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

    Thank you

  • DataGuard (activate a physical standby as a stand-alone database database)?

    Hi all

    Can I please ask advice on how it would activate a physical database ensures for 11.2.0.4?

    Note - I do not want to return the "standby" to watch again...

    Note 1 – I don't have (and don't use flashback technology to do this) - so I can't use a watch "snapshot"...

    Note 2 - the 'primary' current cannot be touched.

    Something like below?

    Repeat stop applies to pending

    SQL > alter database recover managed standby database cancel;

    Stop redo pending transaction logs.

    PRIMARY

    SQL > ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2 = DELAY;

    Activate and open the database physical sleep.

    Physical STANDBY

    SQL > ALTER DATABASE ENABLE PENDING DATA base;

    SQL > STARTUP MOUNT FORCE;

    SQL > alter database base_de_donnees ensures together to improve performance;

    SQL > ALTER DATABASE OPEN;

    Concerning

    It wouldn't affect Production (primary). It's just the steps of failover.

    The same applies to the role transition, but in a role transition, you must first pass at the primary level of Eve and the day before, you must run the digital switchover to make primary.

    You could refer to this https://docs.oracle.com/cd/E11882_01/server.112/e41134/role_management.htm#SBYDB4769 you would get to the difference of the steps for the passage and failover.

    -Jonathan Rolland

  • How to get down the database since the failure of the upgrade in case of physical standby

    Hi people,

    Can you please tell me how to get down the has no upgrade in case of physical standby database?

    Kind regards

    Taoqir

    The generic steps to upgrade db at the dg environment

    1. stop the database pending the application of recovery logs

    2. stop the recovery of his expedition logs

    3. upgrade the primary database server executable files

    4 level database server executable files shall ensure that

    5. switch to the main database using DBUA or upgrade scripts

    6 mount the backup database

    7 reactivate shipping again Eve elementary school

    8 restart the recovery process run on the standby database again progress apply

  • Test failover with physical standby

    Hello

    I have a primary at base of 11.2.0.4 (cars) and an instance of unique physical standby (on a virtual machine).

    I need to test failover.

    I'm looking some procedure or steps.

    Can they be valid?

    On primary

    • change the built-in system again to standby_db_name;
    • alter system archive log current;
    • Stop the shipment of archive: alter system set log_archive_dest_state_2 = "DAVID";

    Standby:

    • ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    • ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
    • stop immediately; --> the snapshot can be done at this stage or need to get after 'RECOVER MANAGED STANDBY DATABASE CANCEL'
    • Make a snapshot of the virtual machine
    • startup nomount
    • ALTER database base_de_donnees eve of Mount;
    • ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE.
    • ALTER DATABASE OPEN;

    Test what finish

    Standby:

    • stop the database
    • restore from snapshot
    • Put the database in recovery mode

    Elementary school:

    • Allow destination of the Journal 2

    What do you think?

    Use the snapshot before...

    https://docs.Oracle.com/CD/B28359_01/server.111/b28294/manage_ps.htm#BACIEJJI

  • Test of physical Standby DB 11 g

    Hi all

    My company is considering a DR test in a few months, and since I never did this until I was wondering what would be the best way to go on the DB pending tests. This is a database of 11G (11.2.0.3). I read the following articles:

    http://gavinsoorma.com/2009/09/11g-snapshot-standby-for-real-time-testing/

    http://www.Pythian.com/blog/testing-a-physical-standby-database-in-Oracle-10G/

    http://www.Oracle.com/technetwork/articles/SQL/11g-DataGuard-083323.html

    From what I can tell the snapshot method is the easiest. My main question is when the primary method still must send the archive logs to the waiting or can I defer only to archive log shipping? How we test normally the site of DR is completely disconnect the network connections and put everything in place for the primary will not be able to speak to the waiting and vice versa. Or is the best method to follow the other article that speaks using the flashback database?

    Thanks in advance for your help.

    From what I can tell the snapshot method is the easiest. My main question is when the primary method still must send the archive logs to the waiting or can I defer only to archive log shipping?

    Are you in 11g, yes instant is a nice feature to test your intelligence. If you enable the destination, there is no problem. Meanwhile if too many records are generated and then it takes a long time to get a site to DR.

    How we test normally the site of DR is completely disconnect the network connections and put everything in place for the primary will not be able to speak to the waiting and vice versa

    You can also completely disconnect the primary DR and tests after the conversion of the physics on the eve of the snapshot if it is your condition to do so.

    Or is the best method to follow the other article that speaks using the flashback database?

    In traditional flashback, you will need to take care just like the creation of restore point with guarantee, mode standby manually and run again then flashback to the restore point. Snapshot is really simple and easy to use. If am in your position of course I use the standby database snapshot.

  • Several primary and physical databases Configuration ensures in Data Guard Broker

    Hello

    Is it possible to add two or several primary and physical databases configuration ensures in data guard broker?

    I have 1 primary databases and two databases physical standby that is

    (1) primary that is pri - (database primary)

    (2) secondary i, e, s (physical pending)

    (3) Secondary2 i.e. sec2 (physical pending)

    Practical AM sinister place, my scenario is my pri and dry machines are in seat, if the pri crashed it switch to s that works very well and my S2 is in another area office. Suppose that if my two siege machines pri and sec crashed, so I want to do my mahcine sec2 as primary.

    I have two separate computers to the broker a headquarters and a District Office

    Use failure of quick start on Data Guard Broker, broker headquarters machine I have configured pri and dry but in sector office broker not able congifured pri and S2 and the machine.

    can be done several primary database configuration with data bases on hold?

    Has anyone done this before, or has a perform a recovery after loss of place...

    need help or suggestion

    thanx

    No.... It is not possible. When you use the DG broker, the first thing you can do in the DGMGRL utility is to deliver CONFIGURATION to CREATE. You can see on the doc of this command that you define here the PRIMARY DATABASE.

    The command to add a DATABASE to the broker, adds a new database pending. You cannot add an another primary.

    The broker configuration is explicitly for a primary and all standby databases is supported. If you have an another primary, you create a separate DG broker configuration.

    See you soon,.
    Brian

  • Failover to physical standby

    Hi all

    I have a custodian of data configured in my local system. Please find the slot configuration of the data protection

    Data type of guard:-physical Standby (version Oracle 11 g)

    Service responsible for log transport:-ARCH

    No newspaper to redo the previous day:- neither primary Nor in standby mode

    I'm failing by using the command 'alter database recover managed standby database finish. "

    Please find the below info alert log after this command.

    Killed Dec 03 01:42:14 2013

    ALTER database recover managed standby database finish

    Try to perform a recovery of Terminal (PRD)

    Beginning media recovery: recovery ensures managed (PRD)

    Parallel media enabled rapid recovery

    Managed Standby recovery not using real time applies

    Media, recovery waiting for thread 1 sequence 145

    "Terminal recovery Timestamp is December 3, 2013 01:42:15.

    Terminal recovery: application standby redo logs.

    Terminal recovery: thread 1 seq # 145 again required

    Media, recovery waiting for thread 1 sequence 145

    Terminal recovery: allowance end Redo log

    Recovery Terminal: waiting for redo logfile created 3 ' / data/PRD_DR/arch/arch_1_0_831359165.arch'

    This waiting for redo log file is created as part of the recovery

    operation.  This waiting for redo log file should be deleted after the

    transition to a primary operation complete.

    Recovery Media Log /data/PRD_DR/arch/arch_1_0_831359165.arch

    Terminal retrieval: newspaper 3 reserved for thread 1 sequence 145

    Online Redo Log recovery: thread 1 mem Group 3 Seq 145 reading 0

    Mem # 0: /data/PRD_DR/arch/arch_1_0_831359165.arch

    Identified end-of-Redo for thread 1 sequence 145

    Incomplete recovery applied all redo them ever generated.

    Change recovery completed by 559773 23/11/2013 time 13:38:13

    Recovery media Complete (PRD)

    Terminal recovery: success of

    Activation reset sleep ID 1895332757 (0x70f87b95)

    Completed: alter database recover managed standby database finish

    Killed Dec 03 01:42:50 2013

    change the database for validation at the crossing elementary school

    ALTER DATABASE TRANSITION TO PRIMARY SCHOOL (PRD)

    Waiting for the transition from role maximum is 15 minutes.

    Backup controlfile written to trace the file /apps/oracle/diag/rdbms/stand/PRD/trace/PRD_ora_9466.trc

    tkcrrxms: kill 3 process (all the RFS)

    Terminal standby recovery start SCN: 559772

    RESETLOGS after complete through change 559773

    Log in/data/PRD_DR/REDOLOG11 line. JOURNAL: Thread 1 Group 1 had been previously authorized

    Log in/data/PRD_DR/REDOLOG21 line. JOURNAL: Thread 1 group 2 was previously disabled

    Standby became primary YVERT: 559771

    Killed Dec 03 01:42:53 2013

    Here, my question is, why oracle implicitly creates a newspaper waiting redo pending data base for the realization of "alter database recover managed standby database finish".

    Thank you

    Like to, its due to the following bug.

    Bug 5889025 : FINISHING SWITCH GENERATES INCORRECT STANDBY REDO LOG.

    This bug refers to version 9i and standby redo logs/realtime concept is not available.

    OP using the 11g version...  Although if you see in the State of the article, the State is "92 - closed, not a Bug", according to me this is the default behavior and is not bug.

  • DG 1 physical standby

    Hello

    11.2.0.1

    We have a DEV database which is also as critical as the PROD db since there are many strategic projects running on it.

    This DEV database has been configured with dataguard physical standby on the DR server.

    Well, that's what I read in the documents only as I'm newly taken over as a dba. Setup has been done outsourced

    by 3rd party, and I can't talk to the implentors, as they were long gone.

    When I check the DR server that only the PROD is running and the DEV was arrested for the last 12 months.

    My question is if the physical standby is stopped for almost a year, can it still be activated? or is it still valid?

    This will affect the performance of the primary database? Since he could always check heartbeat for her? or delay some process as archivers?

    How to disable the physical standby from the primary database?

    Thank you

    Petra k.

    Hello;

    "If the physical standby is stopped for almost a year, can it still be activated? or is it still valid? »

    No and no. Even a tiny production database would have generated and remove too many archives in a year for the old standby at any value. Rebuild it.

    How to disable the physical standby from the primary database?

    You could do just that: (primary side)

    ALTER system set log_archive_dest_state_2 = reporter;

    And you can clean all the parameters for DG too.

    How to remove a primary database data protection Configuration (Doc ID 733794.1)

    Best regards

    mseberg

Maybe you are looking for