Re: {Disarmed} Re: dataguart fal issue

Carel-Jan Engel wrote:
> Did you set the FAL_SERVER / FAL_CLIENT parameters?
> If so, does the FAL_CLIENT (as configured in the standby instance)
> point to the Standby? (e.g. the same as the service mentioned in the
> LOG_ARCHOVE_DEST_n parameter)

Hi Carel-Jan,

This brings up a point I have been meaning to ask, and hoping you could answer. In the 10g Data Guard Concepts and Administration manual, there is a confusing section on gap resolution. The upshoot is that it is somewhat unclear from the documentation if FAL_% parameters are really needed for a plain vanilla 10g primary-standby pair:

http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1268281

http://tinyurl.com/3x6znn

"Gap recovery is handled through the polling mechanism... Data Guard performs gap detection and resolution by automatically retrieving missing archived redo log files from the primary database. No extra configuration settings are required to poll the standby databases, to detect any gaps, or to resolve the gaps..."

"Note: Prior to Oracle Database 10g Release 1, the FAL client and server were used to resolve gaps from the primary database..."

"The fetch archive log (FAL) client and server resolve gaps detected in the range of archived redo log files..."

So which is it? It seems almost everyone is stull using and recommending FAL for 10g standbys, but the documentation seems to say it is deprecated.

Thanks,

Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net

--
http://www.freelists.org/webpage/oracle-l