DBA Hub

📋Steps in this guide1/3

How To Setup Dataguard Broker Configuration (DG Broker) In 12c

Dataguard broker is used to automate monitoring and controlling standby setups. It is very much useful, when the organization has multiple standby sites.

oracle configurationintermediate
by OracleDba
16 views
1

Overview

Dataguard broker is used to automate monitoring and controlling standby setups. It is very much useful, when the organization has multiple standby sites. In this blog, we will see, how to enable dg broker configuration in existing standby setup. ENVIRONMENT DETAILS: PRIMARY UNIQUE DB NAME – PRIM STANDBY UNIQUE DB NAME – STAND - Set dg_broker_start to true ( ON BOTH PRIMARY AND STANDBY DataBase)

Code/Command (click line numbers to comment):

1
2
3
alter system set dg_broker_start=true sid='*';

System altered.
2

Section 2

- Add primary db configuration [ ON PRIMARY]

Code/Command (click line numbers to comment):

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
$dgmgrl
DGMGRL for Solaris: Release 12.2.0.1.0 - Production on Sun Apr 8 12:22:13 2018

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.

Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sysdg
Password:
Connected to "PRIM"
Connected as SYSDG.


DGMGRL> CREATE CONFIGURATION 'primdb' AS PRIMARY DATABASE IS 'PRIM' CONNECT IDENTIFIER IS PRIM;
Configuration "primdb" created with primary database "PRIM"


DGMGRL> SHOW CONFIGURATION

Configuration - primdb

Protection Mode: MaxPerformance
Members:
PRIM - Primary database

Fast-Start Failover: DISABLED

Configuration Status:
DISABLED

DGMGRL> add database STAND as connect identifier is STAND;
Database "STAND" added


DGMGRL> show configuration

Configuration - primdb

Protection Mode: MaxPerformance
Members:
PRIM - Primary database
STAND - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
DISABLED

SQL> alter system set log_Archive_dest_2=”;

System altered.

DGMGRL> show configuration

Configuration - primdb

Protection Mode: MaxPerformance
Members:
PRIM - Primary database
STAND - Physical standby database
Warning: ORA-16792: configurable property value is inconsistent with member setting

Fast-Start Failover: DISABLED

Configuration Status:
WARNING (status updated 57 seconds ago)

DGMGRL> show database 'STAND' InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE
STAND StandbyFileManagement MANUAL MANUAL
STAND ArchiveLagTarget 0 0
STAND LogArchiveMaxProcesses 4 4
STAND LogArchiveMinSucceedDest 1 1
STAND DataGuardSyncLatency 0 0
STAND LogArchiveTrace 0 (missing) 0
STAND LogArchiveFormat %t_%s_%r.dbf (missing) %t_%s_%r.dbf
3

Section 3

Code/Command (click line numbers to comment):

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
SQL> alter system set standby_file_management=AUTO scope=both;

System altered.

DGMGRL> enable configuration
Enabled.

DGMGRL> show database 'STAND' InconsistentProperties;
INCONSISTENT PROPERTIES
INSTANCE_NAME PROPERTY_NAME MEMORY_VALUE SPFILE_VALUE BROKER_VALUE

DGMGRL> show configuration

Configuration - primdb

Protection Mode: MaxPerformance
Members:
PRIM - Primary database
STAND - Physical standby database

Fast-Start Failover: DISABLED

Configuration Status:
SUCCESS (status updated 49 seconds ago)

Comments (0)

Please to add comments

No comments yet. Be the first to comment!