Learning Oracle: Dataguard

Showing posts with label Dataguard. Show all posts

Saturday, December 31, 2022

Physical Standby Creation Steps For Single Instance

Tuesday, April 19, 2022

Standby RFS & MRP Process

Standby RFS & MRP Process

select process, status,sequence#,block#,blocks, delay_mins from v$managed_standby;

PROCESS STATUS SEQUENCE# BLOCK# BLOCKS DELAY_MINS

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

ARCH CONNECTED 0 0 0 0

ARCH CLOSING 23760 813056 1925 0

ARCH CLOSING 23713 567296 1119 0

ARCH CLOSING 23759 958464 656 0

ARCH CLOSING 23715 1 116 0

RFS IDLE 0 0 0 0

RFS IDLE 0 0 0 0

RFS IDLE 23761 200510 1 0

MRP0 APPLYING_LOG 23761 200510 1024000 0

RFS IDLE 0 0 0 0

10 rows selected.

Here RFS process is idle its mean there is no archive log generation on primary.

SQL> select thread#, process,status,sequence#, block#,blocks from v$managed_standby where process='RFS';

THREAD# PROCESS STATUS SEQUENCE# BLOCK# BLOCKS

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

0 RFS IDLE 0 0 0

0 RFS IDLE 0 0 0

1 RFS IDLE 23761 204221 1

0 RFS IDLE 0 0 0

SQL> select process,pid,status from v$managed_standby;

PROCESS PID STATUS

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

ARCH 9352 CONNECTED

ARCH 9354 CLOSING

ARCH 9356 CLOSING

ARCH 9358 CLOSING

ARCH 9360 CLOSING

RFS 1468 IDLE

RFS 1462 IDLE

RFS 1464 IDLE

MRP0 9376 APPLYING_LOG

RFS 1466 IDLE

10 rows selected.

SQL> !ps -ef|grep 9376

oraprod 7178 7176 0 12:09:19 pts/1 0:00 grep 9376

oraprod 9376 1 0 Mar 06 ? 1:30 ora_mrp0_QASKDR

oraprod 7176 7149 0 12:09:19 pts/1 0:00 /usr/bin/bash -c ps -ef|grep 9376

SQL> !ps -ef|grep 1466

oraprod 7181 7179 0 12:09:49 pts/1 0:00 grep 1466

oraprod 1466 1 0 Apr 15 ? 0:00 oracleQASKDR (LOCAL=NO)

oraprod 7179 7149 0 12:09:49 pts/1 0:00 /usr/bin/bash -c ps -ef|grep 1466

SQL>

Sunday, March 27, 2022

Oracle Dataguard Troubleshooting Steps

select * from v$archive_gap;

select * from v$dataguard_stats;

select flashback_on from v$database;

SELECT * FROM v$block_change_tracking;

show parameter fal;

!tnsping <server/client>

show parameter dump;

show parameter listener;

show parameter service;

show parameter log_archive_dest_2;

show parameter log_archive_dest_state_2;

show parameter dg_broker_start;

SELECT DEST_ID,dest_name,status,type,srl,RECOVERY_MODE

FROM V$ARCHIVE_DEST_STATUS;

RECOVERY_MODE

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

MANAGED REAL TIME APPLY

RECOVERY_MODE

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

MANAGED

On Primary Database

===================

select DEST_ID,DEST_NAME,DESTINATION,TARGET,STATUS,ERROR

from v$archive_dest where DESTINATION dest_id=2;

SELECT THREAD# "Thread",SEQUENCE# "Last Sequence generated" FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#) ORDER BY 1

select max(sequence#),thread# from gv$log group by thread#;

set numwidth 15

select max(sequence#) current_seq,archived,status from v$log;

On Standby Database

===================

SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP

select PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS

from v$managed_standby;

select max(sequence#),thread# from gv$archived_log

where applied='YES' group by thread#;

set numwidth 15

select max(applied_seq#) last_seq from v$archive_dest_status;

FIND GAP

--------

select thread#,low_sequence#,high_sequence# from v$archive_log;

LISTNER VERIFICATION FROM PRIMATY DB

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

select status,error from v$archive_dest where dest_name='LOG_ARCHIVE_DEST_2';

DEFER Log Shipping

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

alter system set log_archive_dest_state_2='DEFER' scope=both;

alter system set dg_broker_start=false;

ENABLE Log Shipping

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

alter system set log_archive_dest_state_2='ENABLE' scope=both;

alter system set dg_broker_start=true;

DELAY CHANGE

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

SQL> alter system set log_archive_dest_2='ARCH DELAY=15

OPTIONAL REOPEN=60 SERVICE=S1';

ARCHIVE_LAG_TARGET tells Oracle to make sure to switch a log every n seconds

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

ALTER SYSTEM SET ARCHIVE_LAG_TARGET = 1800 SCOPE=BOTH;

This sets the maximum lag to 30 mins.

On Primary to Display info about all log destinations

set pages 300 lines 300

set numwidth 15

column ID format 99

column "SRLs" format 99

column active format 99

col type format a4

select ds.dest_id id,ad.status,ds.database_mode db_mode,

ad.archivertype,ds.recovery_mode, ds.protection_mode,

ds.standby_logfile_count "SRLs",ds.standby_logfile_active active,

ds.archived_seq# from v$archive_dest_status ds,v$archive_dest ad

where ds.dest_id = ad.dest_id and ad.status != 'INACTIVE'

order by ds.dest_id

On Primary to Display log destinations options

set pages 300 lines 300

set numwidth 10

column id format 99

select dest_id id ,archiver,transmit_mode,affirm,

async_blocks async,net_timeout net_time,delay_mins delay,

reopen_secs reopen,register,binding from v$archive_dest order by dest_id

Standby Database

select NAME,DATABASE_ROLE,OPEN_MODE,PROTECTION_MODE,PROTECTION_LEVEL, CURRENT_SCN,FLASHBACK_ON,FORCE_LOGGING from v$database;

Some possible statuses for the MRP

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

ERROR - This means that the process has failed.

See the alert log or v$dataguard_status for further information.

WAIT_FOR_LOG - Process is waiting for the archived redo log to be completed.

Switch an archive log on the primary and requery

v$managed_standby to see if the status changes to APPLYING_LOG.

WAIT_FOR_GAP - Process is waiting for the archive gap to be resolved.

Review the alert log to see if FAL_SERVER has been called to resolve the gap.

APPLYING_LOG - Process is applying the archived redo log

to the standby database.

CHECK MANAGED RECOVERY PROCESS : SHOWS STATUS OF ARCH,RFS,MRP PROCESS.

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

select inst_id,process,status,client_process,thread#,sequence#,block#,

blocks,delay_mins from gv$managed_standby;

select * from gv$active_instances;

!ps -ef|grep -i mrp

STARTING MRP0

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

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

STOPING MRP0

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

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

To Display MRP0 Speed

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

set pages 300 lines 300

Col Values For A65

Col Recover_start For A21

Select To_char(START_TIME,'Dd.Mm.Yyyy Hh24:Mi:ss') "Recover_start",

To_char(Item)||' = '||To_char(Sofar)||' '||To_char(Units)||' '||

To_char(TIMESTAMP,'Dd.Mm.Yyyy Hh24:Mi') "Values"

From V$Recovery_progress Where Start_time=(Select Max(Start_time) From V$Recovery_progress);

checking log transfer and apply

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

SELECT SEQUENCE#,FIRST_TIME,NEXT_TIME,APPLIED

FROM V$ARCHIVED_LOG ORDER BY SEQUENCE# ;

select count(*) from V$ARCHIVED_LOG where applied='NO';

TIME TAKEN TO APPLY A LOG

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

set pages 300 lines 300

select TIMESTAMP,completion_time "ArchTime",SEQUENCE#,

round((blocks*block_size)/(1024*1024),1) "SizeM",

round((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP)

OVER (order by TIMESTAMP))*24*60*60,1) "Diff(sec)",

round((blocks*block_size)/1024/ decode(((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),0,1, (TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),1) "KB/sec", round((blocks*block_size)/(1024*1024)/ decode(((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP)

OVER (order by TIMESTAMP))*24*60*60),0,1, (TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),3) "MB/sec",round(((lead(TIMESTAMP,1,TIMESTAMP) over (order by TIMESTAMP))-completion_time)*24*60*60,1) "Lag(sec)" from v$archived_log a, v$dataguard_status dgs where a.name = replace(dgs.MESSAGE,'Media Recovery Log ','') and dgs.FACILITY = 'Log Apply Services' order by TIMESTAMP desc;

CHECKING FOR DATAGAURD ERROR

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

set pages 300 lines 300

column Timestamp Format a20

column Facility Format a24

column Severity Format a13

column Message Format a80 trunc

Select to_char(timestamp,'YYYY-MON-DD HH24:MI:SS') Timestamp,Facility,Severity,error_code,message_num,Message from v$dataguard_status where severity in ('Error','Fatal') order by Timestamp;

select * from v$ARCHIVE_GAP;

--OR---

Here is another script with v$dataguard_status:

select *

from (select TIMESTAMP,

completion_time "ArchTime",

SEQUENCE#,

round((blocks * block_size) / (1024 * 1024), 1) "Size Meg",

round((TIMESTAMP - lag(TIMESTAMP, 1, TIMESTAMP)

OVER(order by TIMESTAMP)) * 24 * 60 * 60,

1) "Diff(sec)",

round((blocks * block_size) / 1024 /

decode(((TIMESTAMP - lag(TIMESTAMP, 1, TIMESTAMP)

OVER(order by TIMESTAMP)) * 24 * 60 * 60),

(TIMESTAMP - lag(TIMESTAMP, 1, TIMESTAMP)

OVER(order by TIMESTAMP)) * 24 * 60 * 60),

1) "KB/sec",

round((blocks * block_size) / (1024 * 1024) /

decode(((TIMESTAMP - lag(TIMESTAMP, 1, TIMESTAMP)

OVER(order by TIMESTAMP)) * 24 * 60 * 60),

(TIMESTAMP - lag(TIMESTAMP, 1, TIMESTAMP)

OVER(order by TIMESTAMP)) * 24 * 60 * 60),

3) "MB/sec",

round(((lead(TIMESTAMP, 1, TIMESTAMP) over(order by TIMESTAMP)) -

completion_time) * 24 * 60 * 60,

1) "Lag(sec)"

from v$archived_log a, v$dataguard_status dgs

where a.name = replace(dgs.MESSAGE, 'Media Recovery Log ', '')

and dgs.FACILITY = 'Log Apply Services'

order by TIMESTAMP desc)

where rownum < 10;

Finding Missing Logs on Standby

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

select local.thread#,local.sequence# from (select thread#,sequence# from v$archived_log where dest_id=1) local where local.sequence# not in (select sequence# from v$archived_log where dest_id=2 and thread# = local.thread#)

Check which logs have not been applied

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

alter session set nls_date_format='YYYY-MM-DD HH24:MI.SS';

SELECT SEQUENCE#, APPLIED, completion_time FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

REGISTRYING LOGFILE

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

alter database register logfile '/file/path/';

RECOVERY PROGRESS ON STANDBY SITE

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

v$managed_standby

v$archived_standby

v$archive_dest_status - TO FIND THE LAST ARCHIVED LOG RECEIVED AND APPLIED ON THIS SITE.

select archived_thread#,archived_seq#,applied_thread#,applied_seq# from v$archive_dest_status;

v$log_history

select max(sequence#),latest_archive_log from v$log_history;

v$archived_log - individual archive log

select thread#,sequence#,applied,registrar from v$archived_log;

standby_file_management - playes when attributes of datafiles are modified primary site.

-IF IT IS RAW DEVICE STANDBY_FILE_MANAGEMENT SHOULD BE MANUAL.OTHERWISE AUTO

TROUBLESHOOTING A PHYSICAL STANDBY DATABASE:

NOTE: Pls check Metalink 232649.1 (Data Guard Gap Detection and Resolution)

On Standby server:

Run the below query to check the type of Standby database,

PHYSCIAL or LOGICAL:

sqlplus "/ as sysdba"

select database_role from v$database;

If Physical Standby then follow:

Step1: Check which logs have not been applied:

======

alter session set nls_date_format='YYYY-MM-DD HH24:MI.SS';

SELECT SEQUENCE#, APPLIED, completion_time FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

Step2:Check if there is a gap in the archive logs:

======

SELECT * FROM V$ARCHIVE_GAP;

If there is a gap, then it is most likely that the log has been compressed on the Primary server, and the Standby FAL service cannot retrieve the log.If so, then temporarily stop archivelog compression job on the primary and unzip the required archive logs. After a few minutes, the FAL service will retrieve the log and the Standby apply services will resume.Check the progress by running the SQL in step-1 above.

If the logs haven't been processed after 5-10 minutes, then you will have to perform the following tasks:

Step3: Copy the (zipped) log to the standby archive log destination on the Standby server, (unzip the archive), and register,

ALTER DATABASE REGISTER LOGFILE '/u01/oradata/stby/arch/arch_1_443.arc';

Step4: Check if this is a 'real-time apply standby:

=======

select recovery_mode from V$ARCHIVE_DEST_STATUS;

Step5: Stop/restart the standby apply services:

=======

alter database recover managed standby database cancel;

If a real-time apply standby then:

alter database recover managed standby database using current logfile disconnect from session;

Found this:

RECOVER MANAGED STANDBY DATABASE cancel;

ORA-16136: Managed Standby Recovery not active

RECOVER MANAGED STANDBY DATABASE disconnect from session;

Media recovery complete.

Else (non- realtime apply):

alter database recover managed standby database disconnect from session;

Check the progress by running the SQL in step-1 above.

Useful Standby query:

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

Startup standby database

startup nomount;

alter database mount standby database;

alter database recover managed standby database disconnect;

To remove a delay from a standby

alter database recover managed standby database cancel;

alter database recover managed standby database nodelay disconnect;

Cancel managed recovery

alter database recover managed standby database cancel;

alter database register physical logfile '<fullpath/filename>';

If FAL doesn't work and it says the log is already registered

alter database register or replace physical logfile '<fullpath/filename>';

If that doesn't work, try this...

shutdown immediate

startup nomount

alter database mount standby database;

alter database recover automatic standby database;

>> wait for the recovery to finish - then cancel

shutdown immediate

startup nomount

alter database mount standby database;

alter database recover managed standby database disconnect;

Check which logs are missing (Run this on the standby)

select local.thread#, local.sequence# from

(select thread#, sequence# from v$archived_log where dest_id=1) local where local.sequence# not in

(select sequence# from v$archived_log where dest_id=2 and thread# = local.thread#);

Disable/Enable archive log destinations

alter system set log_archive_dest_state_2 = 'defer';

alter system set log_archive_dest_state_2 = 'enable';

Turn on fal tracing on the primary db

alter system set LOG_ARCHIVE_TRACE = 128;

Stop the Data Guard broker

alter system set dg_broker_start=false;

Show the current instance role

select name, open_mode, database_role from v$database;

=====

Logical standby apply stop/start

Stop Logical standby >> alter database stop logical standby apply;

Start Logical standby >> alter database start logical standby apply;

See how up to date a physical standby is: (Run this on the primary)

set numwidth 15

select max(sequence#) current_seq from v$log;

Then run this on the standby

set numwidth 15

select max(applied_seq#) last_seq from v$archive_dest_status;

Display info about all log destinations (run on the primary)

set lines 100 set numwidth 15 column ID format 99 column "SRLs" format 99 column active format 99 col type format a4

select ds.dest_id id , ad.status , ds.database_mode db_mode , ad.archiver type , ds.recovery_mode , ds.protection_mode , ds.standby_logfile_count "SRLs" , ds.standby_logfile_active active , ds.archived_seq# from v$archive_dest_status ds , v$archive_dest ad where ds.dest_id = ad.dest_id and ad.status != 'INACTIVE' order by ds.dest_id;

Display log destinations options (run on the primary)

set numwidth 8 lines 100 column id format 99

select dest_id id , archiver , transmit_mode , affirm , async_blocks async , net_timeout net_time , delay_mins delay , reopen_secs reopen , register,binding from v$archive_dest order by dest_id;

List any standby redo logs

set lines 100 pages 999 col member format a70

select st.group# , st.sequence# , ceil(st.bytes / 1048576) mb , lf.member from v$standby_log st , v$logfile lf where st.group# = lf.group#;

Script for Standby archivelog monitoring….(removed the duplicate rows)

select arch.thread# "Thread", arch.sequence# "Last Sequence Received", appl.sequence# "Last Sequence Applied", (arch.sequence# - appl.sequence#) "Difference" from

(select thread# ,sequence# from v$archived_log where (thread#,first_time ) in (select thread#,max(first_time) from v$archived_log group by thread#)) arch,

(select thread# ,sequence# from v$log_history where (thread#,first_time ) in (select thread#,max(first_time) from v$log_history group by thread#)) appl

where arch.thread# = appl.thread#

order by 1;

Troubleshooting Commands:

select NAME,DATABASE_ROLE,OPEN_MODE,PROTECTION_MODE,PROTECTION_LEVEL, CURRENT_SCN,FLASHBACK_ON,FORCE_LOGGING from v$database;

select inst_id,process, status, client_process, thread#, sequence#, block#, blocks from gv$managed_standby

where process = 'MRP0';

STARTING MRP0

RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION PARALLEL 64;

FOR RAC, USE:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT USING CURRENT LOGFILE;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE THROUGH ALL SWITCHOVER DISCONNECT FROM SESSION PARALLEL 132 USING CURRENT LOGFILE;

On Standby

select * from gv$active_instances;

ps -ef|grep -i mrp

select PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS from v$managed_standby;

RECOVER MANAGED STANDBY DATABASE CANCEL;

Defer Log Shipping

alter system set log_archive_dest_state_2=defer scope=both;

alter system set dg_broker_start=false;

Enable Log Shipping

alter system set log_archive_dest_state_2 = 'enable';

alter system set dg_broker_start=true;

Starting the STANDBY DATABASE

startup nomount

alter database mount standby database;

alter database recover managed standby database disconnect from session;

CHECKING FOR DATAGAURD ERROR

select to_char(timestamp,'DD/MM/YY HH24:MI:SS') timestamp,severity, message_num, message from v$dataguard_status where severity in ('Error','Fatal') order by timestamp;

select * from v$ARCHIVE_GAP;

Missing Logs on Standby

select local.thread# , local.sequence# from (select thread# , sequence# from v$archived_log where dest_id=1) local where local.sequence# not in (select sequence# from v$archived_log where dest_id=2 and thread# = local.thread#)

STARTING MRP0

RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

STOPING MRP0

RECOVER MANAGED STANDBY DATABASE CANCEL;

MRP0 STATUS - RAC

select inst_id,process, status, client_process, thread#, sequence#, block#, blocks from gv$managed_standby where process = 'MRPO';

select severity, error_code,message,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') from v$dataguard_status;

REGISTRYING LOGFILE

alter database register logfile ' ';

How To Check Oracle Physical Standby is in Sync with the Primary or Not?

On Primary

set pages 1000

set lines 120

column DEST_NAME format a20

column DESTINATION format a35

column ARCHIVER format a10

column TARGET format a15

column status format a10

column error format a15

select DEST_ID,DEST_NAME,DESTINATION,TARGET,STATUS,ERROR from v$archive_dest where DESTINATION is NOT NULL

SELECT THREAD# "Thread",SEQUENCE# "Last Sequence generated" FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#) ORDER BY 1

select max(sequence#),thread# from gv$log group by thread#;

set numwidth 15

select max(sequence#) current_seq from v$log;

On Standby

SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH, (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1

SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP

select PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS from v$managed_standby;

select max(sequence#),thread# from gv$archived_log where applied='YES' group by thread#;

set numwidth 15

select max(applied_seq#) last_seq from v$archive_dest_status;

Check which logs are missing

Run this on the standby...

select local.thread#, local.sequence# from (select thread# , sequence# from v$archived_log where dest_id=1) local

where local.sequence# not in (select sequence# from v$archived_log where dest_id=2 and thread# = local.thread#)

Display info about all log destinations

To be run on the primary

set lines 100

set numwidth 15

column ID format 99

column "SRLs" format 99

column active format 99

col type format a4

select ds.dest_id id, ad.status, ds.database_mode db_mode, ad.archiver type, ds.recovery_mode, ds.protection_mode, ds.standby_logfile_count "SRLs" , ds.standby_logfile_active active, ds.archived_seq# from v$archive_dest_status ds, v$archive_dest ad where ds.dest_id = ad.dest_id and ad.status != 'INACTIVE' order by ds.dest_id

Display log destinations options

To be run on the primary

set numwidth 8 lines 100

column id format 99

select dest_id id , archiver, transmit_mode, affirm , async_blocks async, net_timeout net_time, delay_mins delay, reopen_secs reopen

, register,binding from v$archive_dest order by dest_id

MRP Speed

Set Linesize 400

Col Values For A65

Col Recover_start For A21

Select To_char(START_TIME,'Dd.Mm.Yyyy Hh24:Mi:ss') "Recover_start",To_char(Item)||' = '||To_char(Sofar)||' '||To_char(Units)||' '|| To_char(TIMESTAMP,'Dd.Mm.Yyyy Hh24:Mi') "Values" From V$Recovery_progress Where Start_time=(Select Max(Start_time) From V$Recovery_progress);

TIME IT TOOK TO APPLY A LOG

select TIMESTAMP,completion_time "ArchTime",SEQUENCE#,round((blocks*block_size)/(1024*1024),1) "SizeM",round((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60,1) "Diff(sec)",round((blocks*block_size)/1024/ decode(((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),0,1, (TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),1) "KB/sec", round((blocks*block_size)/(1024*1024)/ decode(((TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP)

OVER (order by TIMESTAMP))*24*60*60),0,1, (TIMESTAMP-lag(TIMESTAMP,1,TIMESTAMP) OVER (order by TIMESTAMP))*24*60*60),3) "MB/sec",

round(((lead(TIMESTAMP,1,TIMESTAMP) over (order by TIMESTAMP))-completion_time)*24*60*60,1) "Lag(sec)" from v$archived_log a, v$dataguard_status dgs where a.name = replace(dgs.MESSAGE,'Media Recovery Log ','') and dgs.FACILITY = 'Log Apply Services'

order by TIMESTAMP desc;

Tuesday, March 8, 2022

Manual Switchover In Oracle Database (19c)

Primary Database:

tnsping QPROD
tnsping QPRODR

echo $ORACLE_SID

sqlplus / as sysdba

SQL> select name,status,database_role,open_mode from v$instance,v$database;

SQL> select switchover_status from v$database;
SQL> alter database commit to switchover to physical standby with session shutdown;

SQL> !ps -ef|grep pmon
SQL> exit

(or)
SQL> shutdown immediate;

SQL> startup mount;
SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> recover managed standby database disconnect from session;

SQL> !ps -ef | grep mrp

SQL> !lsnrctl status

Standby Database:

tnsping QPROD

tnsping QPRODR

echo $ORACLE_SID

sqlplus / as sysdba

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;
SQL> alter database commit to switchover to primary;

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> alter database open;
SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

Sunday, March 6, 2022

Manual Switchover Activity in Oracle Database 12c

Manual Switchover In Oracle Database (12c)

Switchover Steps

Primary Database:

tnsping QPROD

tnsping QPRODR

echo $ORACLE_SID

sqlplus / as sysdba

SQL> select name,status,database_role,open_mode from v$instance,v$database;

SQL> select switchover_status from v$database;

SQL> alter database commit to switchover to physical standby with session shutdown;

SQL> shutdown immediate;

SQL> startup mount;

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> recover managed standby database disconnect from session;

SQL> !ps -ef | grep mrp

SQL> !lsnrctl status

Standby Database:

tnsping QPROD

tnsping QPRODR

echo $ORACLE_SID

sqlplus / as sysdba

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> alter database commit to switchover to primary;

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> alter database open;

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

SQL> !lsnrctl status

Switchback Steps:

Follow same steps in reverse order.

Actual Steps:

PRIMARY:

Check the database status:

SQL> select name,status,database_role,open_mode from v$instance,v$database;

NAME STATUS DATABASE_ROLE OPEN_MODE

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

QPROD OPEN PRIMARY READ WRITE

SQL> select thread#,max(sequence#) from v$archived_log group by thread#;

THREAD# MAX(SEQUENCE#)

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

1 23326

SQL>

Check the sync status:

SQL> @sync_p.sql

THREAD# MAX(SEQUENCE#)

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

1 23307

Check the switchover status:

SQL> select switchover_status from v$database;

SWITCHOVER_STATUS

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

TO STANDBY

Issue the command:

SQL> alter database commit to switchover to physical standby with session shutdown;

Database altered.

SQL> shut immediate;

ORA-01012: not logged on

SQL> exit

Make sure the background processes of primary is down.

ps -ef|grep pmon

Startup the database mount state:

SQL> startup nomount;

ORACLE instance started.

Total System Global Area 3.2212E+10 bytes

Fixed Size 5292336 bytes

Variable Size 4294975184 bytes

Database Buffers 2.7850E+10 bytes

Redo Buffers 61808640 bytes

SQL> alter database mount;

Database altered.

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

NAME INSTANCE_NAME STATUS DATABASE_ROLE OPEN_MODE

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

QPROD QPROD MOUNTED PHYSICAL STANDBY MOUNTED

SQL> recover managed standby database disconnect from session;

Media recovery complete.

SQL> !ps -ef|grep mrp

oraprod 5060 4931 0 22:22:09 pts/1 0:00 /usr/bin/bash -c ps -ef|grep mrp

oraprod 5062 5060 0 22:22:09 pts/1 0:00 grep mrp

oraprod 5025 1 0 22:21:54 ? 0:03 ora_mrp0_QPROD

Standby:

Check the database status:

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

NAME INSTANCE_NAME STATUS DATABASE_ROLE OPEN_MODE

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

QPROD QPRODR MOUNTED PHYSICAL STANDBY MOUNTED

SQL> select thread#,max(sequence#) from v$archived_log group by thread#;

THREAD# MAX(SEQUENCE#)

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

1 23326

Check the sync status:

SQL> @sync_s.sql

Thread Last Sequence Received Last Sequence Applied Difference

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

1 23307 23307 0

Issue the command:

SQL> alter database commit to switchover to primary;

Database altered.

Open the database:

SQL> alter database open;

Database altered.

Check the database status:

SQL> select name,instance_name,status,database_role,open_mode from v$instance,v$database;

NAME INSTANCE_NAME STATUS DATABASE_ROLE OPEN_MODE

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

QPROD QPRODR OPEN PRIMARY READ WRITE

SQL> alter system switch logfile;

System altered.

Monday, April 12, 2021

Switchover and Switchback Using Dataguard Broker For Oracle 11.2.0.3.0 Database

Switchover and Switchback Using Dataguard Broker For Oracle 11.2.0.3.0 Database

---Primary---

[oracle@host01 ~]$ dgmgrl

DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production

Welcome to DGMGRL, type "help" for information.

DGMGRL> connect sys/Welcome1

Connected.

DGMGRL> show configuration

Configuration - gtp2prod

Protection Mode: MaxPerformance

Databases:

gtp2_live - Primary database

gtp2_stdy - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

To check the PRIMARY status:

DGMGRL> show database verbose gtp2_live

Database - gtp2_live

Role: PRIMARY

Intended State: TRANSPORT-ON

Instance(s):

GTP2PROD

Properties:

DGConnectIdentifier = 'gtp2_live'

ObserverConnectIdentifier = ''

LogXptMode = 'ASYNC'

DelayMins = '0'

Binding = 'optional'

MaxFailure = '0'

MaxConnections = '1'

ReopenSecs = '300'

NetTimeout = '30'

RedoCompression = 'DISABLE'

LogShipping = 'ON'

PreferredApplyInstance = ''

ApplyInstanceTimeout = '0'

ApplyParallel = 'AUTO'

StandbyFileManagement = 'AUTO'

ArchiveLagTarget = '0'

LogArchiveMaxProcesses = '30'

LogArchiveMinSucceedDest = '1'

DbFileNameConvert = 'GTP2_STDY, GTP2_LIVE'

LogFileNameConvert = 'GTP2_STDY, GTP2_LIVE'

FastStartFailoverTarget = ''

InconsistentProperties = '(monitor)'

InconsistentLogXptProps = '(monitor)'

SendQEntries = '(monitor)'

LogXptStatus = '(monitor)'

RecvQEntries = '(monitor)'

SidName = 'GTP2PROD'

StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.7)(PORT=1523))(CONNECT_DATA=(SERVICE_NAME=GTP2_LIVE_DGMGRL)(INSTANCE_NAME=GTP2PROD)(SERVER=DEDICATED)))'

StandbyArchiveLocation = '/u01/app/oracle/arch'

AlternateLocation = ''

LogArchiveTrace = '0'

LogArchiveFormat = 'arch%s%t%r.arc'

TopWaitEvents = '(monitor)'

Database Status:

SUCCESS

To check the STANDBY status:

DGMGRL> show database verbose gtp2_stdy

Database - gtp2_stdy

Role: PHYSICAL STANDBY

Intended State: APPLY-ON

Transport Lag: 0 seconds

Apply Lag: 0 seconds

Real Time Query: ON

Instance(s):

GTP2PROD

Properties:

DGConnectIdentifier = 'gtp2_stdy'

ObserverConnectIdentifier = ''

LogXptMode = 'ASYNC'

DelayMins = '0'

Binding = 'OPTIONAL'

MaxFailure = '0'

MaxConnections = '1'

ReopenSecs = '300'

NetTimeout = '30'

RedoCompression = 'DISABLE'

LogShipping = 'ON'

PreferredApplyInstance = ''

ApplyInstanceTimeout = '0'

ApplyParallel = 'AUTO'

StandbyFileManagement = 'AUTO'

ArchiveLagTarget = '0'

LogArchiveMaxProcesses = '30'

LogArchiveMinSucceedDest = '1'

DbFileNameConvert = 'GTP2_LIVE, GTP2_STDY'

LogFileNameConvert = 'GTP2_LIVE, GTP2_STDY'

FastStartFailoverTarget = ''

InconsistentProperties = '(monitor)'

InconsistentLogXptProps = '(monitor)'

SendQEntries = '(monitor)'

LogXptStatus = '(monitor)'

RecvQEntries = '(monitor)'

SidName = 'GTP2PROD'

StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.8)(PORT=1524))(CONNECT_DATA=(SERVICE_NAME=GTP2_STDY_DGMGRL)(INSTANCE_NAME=GTP2PROD)(SERVER=DEDICATED)))'

StandbyArchiveLocation = '/u01/app/oracle/arch'

AlternateLocation = ''

LogArchiveTrace = '0'

LogArchiveFormat = 'arch%s%t%r.arc'

TopWaitEvents = '(monitor)'

Database Status:

SUCCESS

Check the current status:

DGMGRL> show configuration

Configuration - gtp2prod

Protection Mode: MaxPerformance

Databases:

gtp2_live - Primary database

gtp2_stdy - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

Switchover

It is always advised to view the alert.log files for both PRIMARY and STANDBY databases.

Issue the below command:

DGMGRL> switchover to gtp2_stdy

Performing switchover NOW, please wait...

New primary database "gtp2_stdy" is opening...

Operation requires shutdown of instance "GTP2PROD" on database "gtp2_live"

Shutting down instance "GTP2PROD"...

ORACLE instance shut down.

Operation requires startup of instance "GTP2PROD" on database "gtp2_live"

Starting instance "GTP2PROD"...

ORACLE instance started.

Database mounted.

Database opened.

Switchover succeeded, new primary is "gtp2_stdy"

Check the current status:

DGMGRL> show configuration

Configuration - gtp2prod

Protection Mode: MaxPerformance

Databases:

gtp2_stdy - Primary database

gtp2_live - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

Switchback

To revert (switch back) to the previous situation, perform the same action. Remember now your primary is your previous STANDBY and standby is previous PRIMARY.

Issue the below command:

DGMGRL> swtichover to gtp2_live

Unrecognized command "swtichover", try "help"

DGMGRL> switchover to gtp2_live

Performing switchover NOW, please wait...

New primary database "gtp2_live" is opening...

Operation requires shutdown of instance "GTP2PROD" on database "gtp2_stdy"

Shutting down instance "GTP2PROD"...

ORACLE instance shut down.

Operation requires startup of instance "GTP2PROD" on database "gtp2_stdy"

Starting instance "GTP2PROD"...

ORACLE instance started.

Database mounted.

Database opened.

Switchover succeeded, new primary is "gtp2_live"

Check the current status:

DGMGRL> show configuration

Configuration - gtp2prod

Protection Mode: MaxPerformance

Databases:

gtp2_live - Primary database

gtp2_stdy - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:

SUCCESS

Wednesday, February 17, 2021

Check Whether Physical Standby Is In Sync With The Primary Or NOT

Check Whether Physical Standby Is In Sync With The Primary Or NOT

Method.1

set lines 555

select instance_name,name,open_mode,to_char(startup_time,'DD-MM-YY:HH24:MI:ss') startup_time from v$database,v$instance;

select database_role,db_unique_name instance,open_mode,protection_mode,protection_level,switchover_status from v$database;

+ From Primary:

SQL > select thread#, max(sequence#) "Last Primary Seq Generated" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

SQL> SELECT thread#, dest_id, gvad.status, error, fail_sequence FROM gv$archive_dest gvad, gv$instance gvi WHERE gvad.inst_id = gvi.inst_id AND destination is NOT NULL ORDER BY thread#, dest_id;

+ From Physical Standby:

SQL > select thread#, max(sequence#) "Last Standby Seq Received" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

SQL > select thread#, max(sequence#) "Last Standby Seq Applied" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and applied='YES' group by thread# order by 1;

SQL> select process,status,thread#,sequence# from v$managed_standby;

SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference" FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL WHERE ARCH.THREAD# = APPL.THREAD#;

select max(sequence#) from v$log_history;

select max(sequence#) from v$archived_log where applied='YES';

--Without realtime:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

--With realtime apply:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;

Method.2

From Primary Side:

select thread#, max(sequence#) "Last Primary Seq Generated" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

select thread#, dest_id, gvad.status, error, fail_sequence FROM gv$archive_dest gvad, gv$instance gvi WHERE gvad.inst_id = gvi.inst_id AND destination is NOT NULL ORDER BY thread#, dest_id;

select max(sequence#) from v$log_history;

v$archived_log

gv$archive_dest

v$database

gv$instance

From Physical Standby Side:

select thread#, max(sequence#) "Last Standby Seq Received" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

select thread#, max(sequence#) "Last Standby Seq Applied" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and applied='YES' group by thread# order by 1;

select max(sequence#) from v$log_history;

select process,status,thread#,sequence# from v$managed_standby;

v$archived_log

gv$archive_dest

v$database

v$managed_standby

Primary Side:

SQL> select thread#, max(sequence#) "Last Primary Seq Generated" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

THREAD# Last Primary Seq Generated

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

1 2915

SQL> SELECT thread#, dest_id, gvad.status, error, fail_sequence FROM gv$archive_dest gvad, gv$instance gvi WHERE gvad.inst_id = gvi.inst_id AND destination is NOT NULL ORDER BY thread#, dest_id;

THREAD# DEST_ID STATUS

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

ERROR FAIL_SEQUENCE

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

1 1 VALID

1 2 VALID 0

SQL>select max(sequence#) from v$log_history;

MAX(SEQUENCE#)

————–

2915

Standby Side:

SQL> select thread#, max(sequence#) "Last Standby Seq Received" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# group by thread# order by 1;

THREAD# Last Standby Seq Received

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

1 2915

SQL> select thread#, max(sequence#) "Last Standby Seq Applied" from v$archived_log val, v$database vdb where val.resetlogs_change# = vdb.resetlogs_change# and applied='YES' group by thread# order by 1;

THREAD# Last Standby Seq Applied

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

1 2915

SQL>select max(sequence#) from v$log_history;

MAX(SEQUENCE#)

————–

2915

SQL> select process,status,thread#,sequence# from v$managed_standby;

PROCESS STATUS THREAD# SEQUENCE#

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

DGRD ALLOCATED 0 0

ARCH CLOSING 1 2897

DGRD ALLOCATED 0 0

ARCH CLOSING 1 2914

ARCH CLOSING 1 2893

ARCH CLOSING 1 2915

MRP0 APPLYING_LOG 1 2916

RFS IDLE 1 0

RFS IDLE 1 2916

9 rows selected.

Friday, November 6, 2020

Difference Between Oracle Goldengate & Oracle Dataguard

Difference Between Oracle Goldengate & Oracle Dataguard

Friday, August 28, 2020

Data Guard Physical Standby Setup Using Active Duplicate

Data Guard Physical Standby Setup Using Active Duplicate

VM Machine Details:

node1.oracle.com (147.43.0.15)

node2.oracle.com (147.43.0.16)

Note:

1. Both VM machines should be ping each, Network adapter setting choose "Host-Only".

2. Configure or add both machine ip addresses in /etc/hosts file.

3. Check or test the connectivity using ping or ssh commands.

Database Details:

Database Name :- PRODUAT

Primary db_unique_name :- PRODUAT

standby db_unique_name :- PRODSIT

Steps:

1. Ensure that the database is in archivelog mode.

SQL> select log_mode from v$database;

LOG_MODE

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

ARCHIVELOG

2. Enable force logging.

SQL> ALTER DATABASE FORCE LOGGING;

Database altered.

-- Make sure at least one logfile is present.

ALTER SYSTEM SWITCH LOGFILE;

SQL> select force_logging from v$database;

FORCE_LOGGING

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

YES

3. Create standby redologs.

Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:

(maximum number of logfiles for each thread + 1) * maximum number of threads

SQL> select bytes from v$standby_log;

no rows selected

SQL> SELECT * FROM V$LOGFILE;

SQL> select group#,thread#,bytes from v$log;

GROUP# THREAD# BYTES

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

1 1 52428800

2 1 52428800

3 1 52428800

alter database add standby logfile '/u01/app/oracle/fast_recovery_area/PRODUAT/stbyredo03.log' size 50M;

alter database add standby logfile '/u01/app/oracle/fast_recovery_area/PRODUAT/stbyredo04.log' size 50M;

alter database add standby logfile '/u01/app/oracle/fast_recovery_area/PRODUAT/stbyredo05.log' size 50M;

SQL> select bytes from v$standby_log;

BYTES

----------

52428800

Note: We no need to create standby redo log files on standby and Oracle take cares of it during RMAN duplicate.

4. Modify the primary initialization parameter for dataguard on primary.

SQL> alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(PRODUAT,PRODSIT)';

System altered.

SQL> alter system set LOG_ARCHIVE_DEST_1='LOCATION=/u01/app/oracle/fast_recovery_area/PRODUAT/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRODUAT';

System altered.

SQL> alter system set LOG_ARCHIVE_DEST_2='SERVICE=PRODSIT LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRODSIT';

System altered.

SQL> alter system set LOG_ARCHIVE_DEST_STATE_1=ENABLE;

System altered.

SQL> alter system set standby_file_management=auto scope=both;

System altered.

SQL> alter system set FAL_SERVER=PRODSIT;

System altered.

SQL> alter system set FAL_CLIENT=PRODUAT;

System altered.

SQL> alter system set DB_FILE_NAME_CONVERT='PRODUAT','PRODSIT' scope=spfile; System altered.

SQL> alter system set LOG_FILE_NAME_CONVERT='PRODUAT','PRODSIT' scope=spfile;

System altered.

5. Create the necessary directories on the standby server.

mkdir -p /u01/app/oracle/oradata/PRODSIT

chown -R oracle:oinstall /u01/app/oracle/oradata/PRODSIT

6. Configure Oracle net service/TNS names for standby system using NETCA or NETMGR

Make sure tnsnames.ora file contains both entries in Primary and Standby servers

Primary:

[oracle@node1 admin]$ cat tnsnames.ora

# tnsnames.ora Network Configuration File: /u01/MTEST/network/admin/tnsnames.ora

# Generated by Oracle configuration tools.

PRODUAT =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = node1.oracle.com)(PORT = 1522))

)

(CONNECT_DATA =

(SERVICE_NAME = PRODUAT)

)

PRODSIT =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = node2.oracle.com)(PORT = 1522))

)

(CONNECT_DATA =

(SERVICE_NAME = PRODSIT)

)

Standby:

[oracle@node2 admin]$ cat tnsnames.ora

# tnsnames.ora Network Configuration File: /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/tnsnames.ora

# Generated by Oracle configuration tools.

PRODSIT =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = node2.oracle.com)(PORT = 1522))

)

(CONNECT_DATA =

(SERVICE_NAME = PRODSIT)

)

PRODUAT =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = node1.oracle.com)(PORT = 1522))

)

(CONNECT_DATA =

(SERVICE_NAME = PRODUAT)

)

7. Check with the SQL*Net configuration using the following commands on the Primary and Standby

tnsping MQMPROD

tnsping MQMDR

8. Create the standby database

-Copy the password file from the primary $ORACLE_HOME/dbs and rename it to the standby database name.

-Create a initialization parameter with only one parameter DB_NAME.

DB_NAME=PRODUAT

DB_UNIQUE_NAME=PRODSIT

compatible='12.1.0.2.0'

log_file_name_convert='PRODUAT','PRODSIT'

9. Create the necessary directories in the standby location to place database files and trace files ($ADR_HOME)

mkdir -p /u01/app/oracle/admin/MQMDR/adump

10. Set the environment variable ORACLE_SID to the standby service and start the standby-instance.

export ORACLE_SID=MQMDR

sqlplus "/ as sysdba"

SQL> startup nomount pfile=$ORACLE_HOME/dbs/initPRODSIT.ora

11. Verify if the connection 'AS SYSDBA' is working

sqlplus /nolog

SQL> connect sys/Welcome1@MQMDR AS SYSDBA

Connected.

SQL> connect sys/Welcome1@MQMPROD AS SYSDBA

Connected.

12. Connect to RMAN, specifying a full connect string for both the TARGET and AUXILIARY instances ( Issue on Standby )

Connect RMAN using target and auxiliary should connected as “not mounted” only.

[oracle@node2 ~]$ rman target sys/Welcome1@PRODUAT auxiliary sys/Welcome1@PRODSIT

Recovery Manager: Release 12.1.0.2.0 - Production on Fri Aug 28 05:23:39 2020

connected to target database: PRODUAT (DBID=1381890412)

connected to auxiliary database: PRODUAT (not mounted)

RMAN> duplicate target database for standby from active database nofilenamecheck dorecover;

An explanation of the above RMAN command.

FOR STANDBY: This tells the DUPLICATE command is to be used for a standby, so it will not force a DBID change.

FROM ACTIVE DATABASE: The DUPLICATE will be created directly from the source datafile, without an additional backup step.

DORECOVER: The DUPLICATE will include the recovery step, bringing the standby up to the current point in time.

NOFILENAMECHECK: Destination file locations are not checked.

Once the command is complete, we can start the apply process.

Output:

Starting Duplicate Db at 28-AUG-20

using target database control file instead of recovery catalog

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=23 device type=DISK

current log archived

contents of Memory Script:

{

backup as copy reuse

targetfile '/u01/MTEST/dbs/orapwPRODUAT' auxiliary format

'/u01/app/oracle/product/12.1.0/dbhome_1/dbs/orapwPRODSIT' ;

}

executing Memory Script

Starting backup at 28-AUG-20

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=55 device type=DISK

Finished backup at 28-AUG-20

contents of Memory Script:

{

restore clone from service 'PRODUAT' standby controlfile;

}

executing Memory Script

Starting restore at 28-AUG-20

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: restoring control file

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03

output file name=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/cntrlPRODSIT.dbf

Finished restore at 28-AUG-20

contents of Memory Script:

{

sql clone 'alter database mount standby database';

}

executing Memory Script

sql statement: alter database mount standby database

contents of Memory Script:

{

set newname for tempfile 1 to

"/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_temp_hnkbdtkj_.tmp";

switch clone tempfile all;

set newname for datafile 1 to

"/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_system_hnkb8mqx_.dbf";

set newname for datafile 3 to

"/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_sysaux_hnkb68cx_.dbf";

set newname for datafile 4 to

"/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_undotbs1_hnkbcn7x_.dbf";

set newname for datafile 6 to

"/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_users_hnkbcm4m_.dbf";

restore

from service 'PRODUAT' clone database

; sql 'alter system archive log current';

}

executing Memory Script

executing command: SET NEWNAME

renamed tempfile 1 to /u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_temp_hnkbdtkj_.tmp in control file

executing command: SET NEWNAME

Starting restore at 28-AUG-20

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set

channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_system_hnkb8mqx_.dbf

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:35

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set

channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_sysaux_hnkb68cx_.dbf

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:25

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set

channel ORA_AUX_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_undotbs1_hnkbcn7x_.dbf

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:02

channel ORA_AUX_DISK_1: starting datafile backup set restore

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set

channel ORA_AUX_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_users_hnkbcm4m_.dbf

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

Finished restore at 28-AUG-20

sql statement: alter system archive log current

current log archived

contents of Memory Script:

{

restore clone force from service 'PRODUAT'

archivelog from scn 1618367;

switch clone datafile all;

}

executing Memory Script

Starting restore at 28-AUG-20

using channel ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: starting archived log restore to default destination

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: restoring archived log

archived log thread=1 sequence=14

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

channel ORA_AUX_DISK_1: starting archived log restore to default destination

channel ORA_AUX_DISK_1: using network backup set from service PRODUAT

channel ORA_AUX_DISK_1: restoring archived log

archived log thread=1 sequence=15

channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01

Finished restore at 28-AUG-20

datafile 1 switched to datafile copy

input datafile copy RECID=1 STAMP=1049648103 file name=/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_system_hnkb8mqx_.dbf

datafile 3 switched to datafile copy

input datafile copy RECID=2 STAMP=1049648103 file name=/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_sysaux_hnkb68cx_.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=3 STAMP=1049648103 file name=/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_undotbs1_hnkbcn7x_.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=4 STAMP=1049648103 file name=/u01/app/oracle/oradata/PRODUAT/datafile/o1_mf_users_hnkbcm4m_.dbf

contents of Memory Script:

{

set until scn 1618687;

recover

standby

clone database

delete archivelog

;}

executing Memory Script

executing command: SET until clause

Starting recover at 28-AUG-20

using channel ORA_AUX_DISK_1

starting media recovery

archived log for thread 1 with sequence 14 is already on disk as file /u01/app/oracle/product/12.1.0/dbhome_1/dbs/arch1_14_1049631726.dbf

archived log for thread 1 with sequence 15 is already on disk as file /u01/app/oracle/product/12.1.0/dbhome_1/dbs/arch1_15_1049631726.dbf

archived log file name=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/arch1_14_1049631726.dbf thread=1 sequence=14

archived log file name=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/arch1_15_1049631726.dbf thread=1 sequence=15

media recovery complete, elapsed time: 00:00:00

Finished recover at 28-AUG-20

Finished Duplicate Db at 28-AUG-20

12. Start managed recovery

Connect to standby using SQL*Plus and start the MRP (Managed Recovery Process). Compare the primary last sequence and MRP (Managed Recovery Process) applying sequence.

SQL> alter database recover managed standby database disconnect from session;

Database altered.

SQL> select NAME,CONTROLFILE_TYPE,OPEN_MODE,DATABASE_ROLE,PROTECTION_MODE from v$database;

NAME CONTROL OPEN_MODE DATABASE_ROLE PROTECTION_MODE

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

PRODUAT STANDBY MOUNTED PHYSICAL STANDBY MAXIMUM PERFORMANCE

SQL> host

[oracle@node2 ~]$ ps -ef|grep mrp

oracle 10077 1 0 17:17 ? 00:00:02 ora_mrp0_PRODSIT

oracle 10158 10129 0 17:23 pts/1 00:00:00 grep mrp

The Managed Recovery Process (MRP) applies information from the archived redo logs to the standby database. When performing managed recovery operations, log apply services automatically apply archived redo logs to maintain transactional synchronization with the primary database.

Alertlog:

Fri Aug 28 17:17:52 2020

alter database recover managed standby database disconnect from session

Fri Aug 28 17:17:52 2020

Attempt to start background Managed Standby Recovery process (PRODSIT)

Starting background process MRP0

Fri Aug 28 17:17:52 2020

MRP0 started with pid=21, OS id=10077

Fri Aug 28 17:17:52 2020

MRP0: Background Managed Standby Recovery process started (PRODSIT)

Fri Aug 28 17:17:57 2020

Serial Media Recovery started

Managed Standby Recovery starting Real Time Apply

Fri Aug 28 17:17:57 2020

Waiting for all non-current ORLs to be archived...

Fri Aug 28 17:17:57 2020

All non-current ORLs have been archived.

Media Recovery Waiting for thread 1 sequence 16

Completed: alter database recover managed standby database disconnect from session

Note:

If you face any SYNC issue, try to set the standby related parameters.

Tuesday, July 21, 2020

Dataguard Broker Configuration In Oracle 12c

Primary side:

oracle@mqm-testdb1:~$ export ORACLE_SID=QPROD
oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 12:30:27 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

Check the dgbroker config files:

SQL> show parameter dg_broker_config

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
dg_broker_config_file1 string /u01/app/oracle/product/12.1.0.2/db_1/dbs/dr1QPROD.dat
dg_broker_config_file2 string /u01/app/oracle/product/12.1.0.2/db_1/dbs/dr2QPROD.dat

SQL> exit
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
oracle@mqm-testdb1:~$

DGMGRL> exit
oracle@mqm-testdb1:~$ ps -ef|grep pmon
grid 12699 1 0 Oct 22 ? 35:04 asm_pmon_+ASM1
grid 23378 1 0 Oct 22 ? 28:37 mdb_pmon_-MGMTDB
oracle 28481 1 0 Jan 07 ? 23:02 ora_pmon_OGGSRC1
oracle 14556 1 0 Feb 18 ? 9:15 ora_pmon_QPROD1
oracle 24956 11452 0 12:34:49 pts/13 0:00 grep pmon

De-activate the log shipping:

oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:10:15 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2='defer' SCOPE=BOTH sid='*';
System altered.

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------
QPROD1

SQL> select password from sys.user$ where name like 'SYS';

PASSWORD
--------------------------------------------------------------------------------
27889DA827C33694

Check the passwordfile parameters:

SQL> show parameter remote

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
remote_dependencies_mode string TIMESTAMP
remote_listener string mqm-testscan.local:1521
remote_login_passwordfile string EXCLUSIVE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
result_cache_remote_expiration integer 0
SQL>

Change the sys password from sql level:

SQL> alter user sys identified by sys_1234;
User altered.

SQL> exit
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

Check the passwordfile status:

oracle@mqm-testdb1:~$ srvctl config database -d QPROD
Database unique name: QPROD
Database name: QPROD
Oracle home: /u01/app/oracle/product/12.1.0.2/db_1
Oracle user: oracle
Spfile: +DATA/QPROD/spfilerac2.ora
Password file: +DATA/QPROD/PASSWORD/pwdprQPROD/
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups: DATA,REDO
Mount point paths:
Services: QUATRAC,ANSQ
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: dba
Database instances: QPROD1,QPROD2
Configured nodes: mqm-testdb1,mqm-testdb2
Database is administrator managed
oracle@mqm-testdb1:~$
oracle@mqm-testdb1:~$
oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"

SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:19:37 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ WRITE

Create the passwordfile using orapwd utility:

oracle@mqm-testdb1:~$ orapwd file='+DATA/QPROD/PASSWORD/pwdQPROD' dbuniquename='QPROD' password=sys_1234 entries=10

Add the passwordfile using srvctl:

oracle@mqm-testdb1:~$ srvctl modify database -d QPROD -pwfile '+DATA/QPROD/PASSWORD/pwdQPROD'

oracle@mqm-testdb1:~$ srvctl config database -d QPROD
Database unique name: QPROD
Database name: QPROD
Oracle home: /u01/app/oracle/product/12.1.0.2/db_1
Oracle user: oracle
Spfile: +DATA/QPROD/spfilerac2.ora
Password file: +DATA/QPROD/PASSWORD/pwdQPROD
Domain:
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools:
Disk Groups: DATA,REDO
Mount point paths:
Services: QUATRAC,ANSQ
Type: RAC
Start concurrency:
Stop concurrency:
OSDBA group: dba
OSOPER group: dba
Database instances: QPROD1,QPROD2
Configured nodes: mqm-testdb1,mqm-testdb2
Database is administrator managed

Test the new passwordfile:

oracle@mqm-testdb1:~$ sqlplus sys/sys_1234@QPROD as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:25:36 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options
SQL> exit

Activate the log shipping:

oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:40:07 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2='enable' SCOPE=BOTH sid='*';
System altered.

Check the config file status:

oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:49:21 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

SQL> show parameter dg_broker_config

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
dg_broker_config_file1 string /u01/app/oracle/product/12.1.0.2/db_1/dbs/dr1QPROD.dat
dg_broker_config_file2 string /u01/app/oracle/product/12.1.0.2/db_1/dbs/dr2QPROD.dat

SQL> select instance_name from v$instance;

INSTANCE_NAME
----------------
QPROD1

Move the config files to ASM:

oracle@mqm-testdb1:~$ sqlplus "/ as sysdba"
SQL*Plus: Release 12.1.0.2.0 Production on Mon Mar 9 13:49:21 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Advanced Analytics and Real Application Testing options

SQL> alter system set dg_broker_start=FALSE scope=both sid='*';
System altered.

SQL> alter system set dg_broker_config_file1='+DATA/QPROD/DGBROKERCONFIGFILE/dr1QPROD.dat' scope=both sid='*';
System altered.

SQL> alter system set dg_broker_config_file2='+DATA/QPROD/DGBROKERCONFIGFILE/dr2QPROD.dat' scope=both sid='*';
System altered.

SQL> alter system set dg_broker_start=TRUE scope=both sid='*';
System altered.

SQL> alter system set LOG_ARCHIVE_DEST_2='' scope=both;
System altered.

Create the configuration:

oracle@mqm-testdb1:~$ dgmgrl
DGMGRL for Solaris: Version 12.1.0.2.0 - 64bit Production
Copyright (c) 2000, 2013, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/sys_1234@QPROD
Connected as SYSDBA.

DGMGRL> CREATE CONFIGURATION UATRAC_DG AS PRIMARY DATABASE IS QPROD CONNECT IDENTIFIER IS QPROD;
Configuration "UATRAC_DG" created with primary database "QPROD"

DGMGRL> ADD DATABASE QPRODN AS CONNECT IDENTIFIER IS QPRODN MAINTAINED AS PHYSICAL;
Database "QPRODN" added

Enable the configuration:

DGMGRL> ENABLE CONFIGURATION;
Enabled.
DGMGRL> show configuration;

Configuration - UATRAC_DG

Protection Mode: MaxPerformance
Members:
QPROD - Primary database
QPRODn - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 6 seconds ago)

Check the status:

oracle@mqm-testdb1:~$ dgmgrl
DGMGRL for Solaris: Version 12.1.0.2.0 - 64bit Production

Copyright (c) 2000, 2013, Oracle. All rights reserved.

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/sys_1234@QPROD
Connected as SYSDBA.
DGMGRL> show configuration;

Configuration - UATRAC_DG

Protection Mode: MaxPerformance
Members:
QPROD - Primary database
QPRODn - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 47 seconds ago)

DGMGRL> show database QPROD

Database - QPROD

Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
QPROD1
QPROD2

Database Status:
SUCCESS

DGMGRL> show database QPRODN

Database - QPRODn

Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Average Apply Rate: 66.00 KByte/s
Real Time Query: ON
Instance(s):
QPRODN1 (apply instance)
QPRODN2

Database Status:
SUCCESS

Stop and Start Log Shipping for an Oracle Standby Database

DEACTIVATE THE LOG SHIPPING:

SQL> alter system set log_archive_dest_state_2=defer scope=both; (If RAC sid = '*';)
System altered.

SQL> show parameter log_archive_dest_state_2
NAME TYPE VALUE
------------------------------------ ----------- -----
log_archive_dest_state_2 string DEFER

SQL> select max(sequence#) from v$log_history;
54276

SQL> alter system switch logfile;

SQL> select max(sequence#) from v$log_history;
24277

ACTIVATE THE LOG SHIPPING:

SQL> alter system set log_archive_dest_state_2=enable scope=both; (If RAC sid = '*';)

SQL> show parameter log_archive_dest_state_2
NAME TYPE VALUE
------------------------------------ ----------- -----
log_archive_dest_state_2 string ENABLE

SQL> select max(sequence#) from v$log_history;
54279

SQL> alter system switch logfile;

SQL> select max(sequence#) from v$log_history;
54280

Learning Oracle

Pages

Saturday, December 31, 2022

Physical Standby Creation Steps For Single Instance

Physical Standby Creation Steps For Single Instance

Tuesday, April 19, 2022

Standby RFS & MRP Process

Sunday, March 27, 2022

Oracle Dataguard Troubleshooting Steps

Oracle Dataguard Troubleshooting Steps

Tuesday, March 8, 2022

Manual Switchover In Oracle Database (19c)

Manual Switchover In Oracle Database (19c)

Sunday, March 6, 2022

Manual Switchover Activity in Oracle Database 12c

Manual Switchover In Oracle Database (12c)

Monday, April 12, 2021

Switchover and Switchback Using Dataguard Broker For Oracle 11.2.0.3.0 Database

Wednesday, February 17, 2021

Check Whether Physical Standby Is In Sync With The Primary Or NOT

Friday, November 6, 2020

Difference Between Oracle Goldengate & Oracle Dataguard

Friday, August 28, 2020

Data Guard Physical Standby Setup Using Active Duplicate

Tuesday, July 21, 2020

Dataguard Broker Configuration In Oracle 12c

Dataguard Broker Configuration In Oracle 12c

Stop and Start Log Shipping for an Oracle Standby Database

Stop and Start Log Shipping for an Oracle Standby Database

Translate

Followers