FAL behavior on 11.2 (文档 ID 1394472.1)

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Enterprise Manager for Oracle Database - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

Goal

This Document talks about how FAL request work on 11.2

Fix

In DG configuration if primary has only one standby then no need to mention the FAL parameter.

From 11.2 no need to mentione FAL_CLIENT primary will take it from log_archiver
_dest_n (remote destination standby from where it received the FAL request) service.

For example,

1. On standby MRP now waiting for GAP sequence 24.

SQL> select process,sequence#,status from v$managed_standby;

PROCESS SEQUENCE# STATUS
--------- ---------- ------------
ARCH 0 CONNECTED
ARCH 0 CONNECTED
ARCH 0 CONNECTED
ARCH 0 CONNECTED
MRP0 24 WAIT_FOR_GAP
RFS 0 IDLE
RFS 28 IDLE

7 rows selected.

2. The corresponding Alert log shows FAL fetching the GAP sequence.

-------------Standby Alert log-----------

Wed Nov 30 19:44:43 2011
Fetching gap sequence in thread 1, gap sequence 24-25

3. But FAL defined on standby,

SQL> show parameter fal;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
fal_client string
fal_server string
SQL>

4. Standby received sequence 24-25 and now applying sequence 28.

SQL> select process,sequence#,status from v$managed_standby;

PROCESS SEQUENCE# STATUS
--------- ---------- ------------
ARCH 0 CONNECTED
ARCH 0 CONNECTED
ARCH 0 CONNECTED
ARCH 0 CONNECTED
MRP0 28 WAIT_FOR_LOG
RFS 0 IDLE
RFS 28 IDLE
RFS 0 IDLE
RFS 0 IDLE

9 rows selected.