Archiving redo log on standby [message #672492] |
Tue, 16 October 2018 09:25 |
|
Mdumala
Messages: 2 Registered: October 2018
|
Junior Member |
|
|
Hello Guys
I have question about archiving logs in standby database.
My current config is
Primary database (SID = prod)
Standby database (SID = prodstb)
Primary have params like :
log_archive_dest_1 string LOCATION=use_db_recovery_file_
dest VALID_FOR=(ALL_LOGFILES,A
LL_ROLES) DB_UNIQUE_NAME=prod
log_archive_dest_2 string service="prodstb", ASYNC NOAFF
IRM delay=0 optional compressi
on=disable max_failure=0 max_c
onnections=1 reopen=300 db_uni
que_name="prodstb" net_timeout
=30, valid_for=(online_logfile
,all_roles)
And standby :
log_archive_dest_1 string LOCATION=use_db_recovery_file_
dest VALID_FOR=(ALL_LOGFILES,A
LL_ROLES) DB_UNIQUE_NAME=prods
tb
Everything works fine with transport and applying but when i look in v$archived log on standby database i see things like :
1 ARCH 13
2 LGWR 14
1 ARCH 15
1 ARCH 16
1 ARCH 17
1 ARCH 18
1 ARCH 19
1 ARCH 20
1 ARCH 21
2 LGWR 22
1 ARCH 23
2 LGWR 24
1 ARCH 25
1 ARCH 26
2 LGWR 27
1 ARCH 28
2 LGWR 29
1 ARCH 30
2 LGWR 31
1 ARCH 32
2 LGWR 33
1 ARCH 34
2 LGWR 35
1 ARCH 36
2 ARCH 37
1 ARCH 38
1 ARCH 39
1 ARCH 40
The question is why the heck i'm seeing LWGR as process which creating my archive logs?
Regards
|
|
|
|
|
Re: Archiving redo log on standby [message #672495 is a reply to message #672492] |
Tue, 16 October 2018 10:20 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
Your log_archive_dest_n parameters are not set correctly. For example, if you do a switch over it will stop working. Your best option would be to set log_archive_dest_2 to null in your primary and then to enable the Data Guard Broker, which will set all the relevant parameters correctly.
[Updated on: Tue, 16 October 2018 11:04] Report message to a moderator
|
|
|
Re: Archiving redo log on standby [message #672502 is a reply to message #672495] |
Tue, 16 October 2018 15:27 |
|
JPBoileau
Messages: 88 Registered: September 2017
|
Member |
|
|
Your environment is not set currently. This is what I get in my case, for one Primary + 2 Standby's:
DEST_ID CREATOR SEQUENCE#
1 ARCH 31900
2 LGWR 31900
3 LGWR 31900
1 ARCH 31899
2 LGWR 31899
3 LGWR 31899
1 gets archived locally on the Prod server, the 2 other are being written to by Log Writer to the standby DB's.
JP
[Updated on: Tue, 16 October 2018 15:27] Report message to a moderator
|
|
|