RE: primary configured with max performance (all defaults), yet creator still shows LGWR
Date: Wed, 15 Jun 2011 16:25:02 +0200
Message-ID: <4814386347E41145AAE79139EAA3989815028998BC_at_ws03-exch07.iconos.be>
Arch and lgwr are deprecated keywords since 11gR1. So, I don't think arch is the default anymore (it was in 10g)
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge_at_uptime.be
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of fmhabash
Sent: woensdag 15 juni 2011 16:05
To: Oracle L
Subject: primary configured with max performance (all defaults), yet creator still shows LGWR
Hi all,
Using RDBMS 11.2, I configured my primary remote destination as follows ...
log_archive_dest_2 SERVICE=BostonStby DB_UNIQUE_NAME=BostonStby
If the process is not specified, it defaults to ARCH.
However, when I examine primary v$archived_log I see creator/registerar=LGWR not ARCH.
What is it showing LGWR instead of ARCH?
THREAD# SEQUENCE# CREATOR REGISTR
---------- ---------- ------- -------
2 12181 LGWR LGWR
1 20061 LGWR LGWR
1 20062 LGWR LGWR
2 12182 LGWR LGWR
1 20063 LGWR LGWR
1 20064 LGWR LGWR
2 12183 LGWR LGWR
1 20065 LGWR LGWR
2 12184 LGWR LGWR
1 20066 LGWR LGWR
1 20067 LGWR LGWR
Also, v$managed_standby shows client_process (last row)
PROCESS STATUS THREAD# SEQUENCE# STATUS DELAY_MINS CLIENT_P
--------- ------------ ---------- ---------- ------------ ----------
ARCH CONNECTED 0 0 CONNECTED 0 ARCH ARCH CONNECTED 0 0 CONNECTED 0 ARCH ARCH CONNECTED 0 0 CONNECTED 0 ARCH ARCH CONNECTED 0 0 CONNECTED 0 ARCH RFS IDLE 0 0 IDLE 0 UNKNOWN RFS IDLE 0 0 IDLE 0 UNKNOWN RFS IDLE 2 12214 IDLE 0 LGWR
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jun 15 2011 - 09:25:02 CDT