RE: dataguard parms
Date: Thu, 9 Apr 2015 13:56:34 +0000
Message-ID: <179EA88836EABD488B716D853751C34A0606B5DB_at_SFRFIDCEXMB004P.statoilfuelretail.com>
Hi,
On standby db:
Select * from v$managed_standby
See what's up.
Apart of that: alert logs (both primary and standby) are your friend. It can take lot of work by listers to nail it down: you better check the logs.
Issue _at_Standby sqlplus SQL> recover managed standby database ; might be you need more like " recover managed standby database using current logfile disconnect from session; "
Issue a few _at_Primary sqlplus SQL> alter system switch logfile; (this is a kick-ass to get things rolling in the Data Guard)
Then check both alert logs.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Howard Latham
Sent: Wednesday, April 08, 2015 5:57 PM
To: ORACLE-L
Subject: dataguard parms
Just back from holiday and my dataguard is broken. Can some kind soul look at these tell whats wrong? THE PROBLEM IS THE STANDBY JUST WAITS AND WAITS WITH NO ATTEMPTS AT FETCHING LOGS. 11g rh enterprise
primary
log_archive_config='dg_config=(auxstby,AUXPRODSTBY)';
fal_client string AUXPRODSTBY fal_server string auxstby
DEST_9=SERVICE='AUXPRODSTBY ASYNC
valid_for=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=AUXPRODSTBY'
)
STANDBY
fal_server='AUXPRODSTBY';
fal_client='auxstby'
log_archive_config='DG_CONFIG=(AUXPRODSTBY,auxstby)'
log_archive_dest_2 string SERVICE=auxstby
VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=aux OPTIONAL LGWR
ASYNC=102400
REOPEN=30 MAX_FAILURE=5 NET_TIMEOUT=10
--
Howard A. Latham
--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 09 2015 - 15:56:34 CEST