DBA Hub

📋Steps in this guide1/5

Important Parameters in Data Guard

1. DB_UNIQUE_NAME Specifies a unique name for the database within the Data Guard configuration. Primary Example  ALTER SYSTEM SET DB_UNIQUE_NAME='primary_db'

oracle configurationintermediate
by OracleDba
14 views
1

Overview

- Specifies a unique name for the database within the Data Guard configuration. - Primary Example - Standby Example - Enables or disables the sending of redo logs to remote destinations and specifies the DB_UNIQUE_NAME for all databases in the Data Guard configuration.

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
ALTER
SYSTEM
SET
DB_UNIQUE_NAME
=
'primary_db'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
DB_UNIQUE_NAME
=
'primary_db'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
DB_UNIQUE_NAME
=
'standby_db'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
DB_UNIQUE_NAME
=
'standby_db'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
LOG_ARCHIVE_CONFIG
=
'DG_CONFIG=(primary_db,standby_db)'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
LOG_ARCHIVE_CONFIG
=
'DG_CONFIG=(primary_db,standby_db)'
SCOPE
=
BOTH
;
2

Section 2

- Specifies the local and remote destinations for archived redo logs. Multiple parameters can be configured. - Specifies the state (ENABLE or DEFER) of the corresponding parameter. - LOG_ARCHIVE_DEST_1 archives redo data generated by the primary database from the local online redo log files to the local archived redo log files in /arch1/chicago/. - LOG_ARCHIVE_DEST_2 is valid only for the primary role. This destination transmits redo data to the remote physical standby destination boston. - Specifies whether Oracle should use a password file to authenticate the database administrator remotely.

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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_1
=
'LOCATION=/u01/app/oracle/arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary_db'
SCOPE
=
BOTH
;
ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_2
=
'SERVICE=standby_db LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_1
=
'LOCATION=/u01/app/oracle/arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary_db'
SCOPE
=
BOTH
;
ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_2
=
'SERVICE=standby_db LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_STATE_1
=
'ENABLE'
SCOPE
=
BOTH
;
ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_STATE_2
=
'ENABLE'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_STATE_1
=
'ENABLE'
SCOPE
=
BOTH
;
ALTER
SYSTEM
SET
LOG_ARCHIVE_DEST_STATE_2
=
'ENABLE'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
REMOTE_LOGIN_PASSWORDFILE
=
'EXCLUSIVE'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
REMOTE_LOGIN_PASSWORDFILE
=
'EXCLUSIVE'
SCOPE
=
SPFILE;
3

Section 3

- Specifies the FAL (Fetch Archive Log) server, which is used by the standby database to fetch missing archived redo logs from the primary database. - Primary Example : - Standby Example : - Specifies the FAL client, which is used by the primary database to fetch missing archived redo logs from the standby database. - Primary Example : - Standby Example :

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
ALTER
SYSTEM
SET
FAL_SERVER
=
'standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_SERVER
=
'standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_SERVER
=
'primary_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_SERVER
=
'primary_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_CLIENT
=
'primary_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_CLIENT
=
'standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
FAL_CLIENT
=
'primary_db'
SCOPE
=
BOTH
;
4

Section 4

- Determines whether or not standby file management is enabled. When set to , Oracle automatically manages the creation and deletion of files on the standby database. - Specifies the conversion parameters for filenames between the primary and standby databases. - Specifies the conversion parameters for redo log filenames between the primary and standby databases.

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
ALTER
SYSTEM
SET
FAL_CLIENT
=
'standby_db'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
STANDBY_FILE_MANAGEMENT
=
'AUTO'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
STANDBY_FILE_MANAGEMENT
=
'AUTO'
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
DB_FILE_NAME_CONVERT
=
'/primary/db/location/'
,
'/standby/db/location/'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
DB_FILE_NAME_CONVERT
=
'/primary/db/location/'
,
'/standby/db/location/'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
LOG_FILE_NAME_CONVERT
=
'/primary/log/location/'
,
'/standby/log/location/'
SCOPE
=
SPFILE;
5

Section 5

- Specifies the target of how far behind (in seconds) the standby database can be in terms of archived redo log application.

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
ALTER
SYSTEM
SET
LOG_FILE_NAME_CONVERT
=
'/primary/log/location/'
,
'/standby/log/location/'
SCOPE
=
SPFILE;

ALTER
SYSTEM
SET
ARCHIVE_LAG_TARGET
=
1800
SCOPE
=
BOTH
;

ALTER
SYSTEM
SET
ARCHIVE_LAG_TARGET
=
1800
SCOPE
=
BOTH
;

Comments (0)

Please to add comments

No comments yet. Be the first to comment!