Home » Server Options » Data Guard » standby FAL help
standby FAL help [message #174371] Sun, 28 May 2006 21:54 Go to next message
lazycat
Messages: 57
Registered: November 2005
Member
i want to configure a standby database on 10.1.0.3.0


after i finished the configure

i type
SQL> startup mount;
ORACLE instance started.

Total System Global Area 1660944384 bytes
Fixed Size 779396 bytes
Variable Size 400825212 bytes
Database Buffers 1258291200 bytes
Redo Buffers 1048576 bytes
Database mounted.
SQL> alter database recover managed standby database disconnect;

Database altered.
but the alert log have the fault message like this

LOG_FILE_NAME_CONVERT initialization parameter not defined
Online logfile pre-clearing operation cannot be performed
Consider defining the LOG_FILE_NAME_CONVERT parameter to
improve standby database switchover and failover performance
Media Recovery Waiting for thread 1 sequence 6142
Fetching gap sequence in thread 1, gap sequence 6142-6143
FAL[client]: Trying FAL server: dw1
Mon May 29 10:28:53 2006
Completed: alter database recover managed standby database di
Mon May 29 10:29:55 2006
FAL[client]: Failed to request gap sequence for thread 1 gap sequence 6142-6143
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------
[oracle@tzdbdw1back bdump]$ tail -f alert_dw2.log
Managed Standby Recovery not using Real Time Apply
LOG_FILE_NAME_CONVERT initialization parameter not defined
Online logfile pre-clearing operation cannot be performed
Consider defining the LOG_FILE_NAME_CONVERT parameter to
improve standby database switchover and failover performance
Media Recovery Waiting for thread 1 sequence 6142
Fetching gap sequence in thread 1, gap sequence 6142-6143
FAL[client]: Trying FAL server: dw1
Mon May 29 10:31:55 2006
Completed: alter database recover managed standby database di
Mon May 29 10:33:00 2006
FAL[client]: Failed to request gap sequence for thread 1 gap sequence 6142-6143
FAL[client]: All defined FAL servers have been attempted.
-------------------------------------------------------------
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
-------------------------------------------------------------


why?
i have the archive log in the primary database archive dictionary
Re: standby FAL help [message #174479 is a reply to message #174371] Mon, 29 May 2006 06:18 Go to previous messageGo to next message
lazycat
Messages: 57
Registered: November 2005
Member
I have reslove the problem
Re: standby FAL help [message #177859 is a reply to message #174371] Sat, 17 June 2006 02:19 Go to previous messageGo to next message
suryamz
Messages: 17
Registered: March 2006
Junior Member
I am having a similar situation, can you please share with me
how you resolved the issue ?

Thnx
Re: standby FAL help [message #180938 is a reply to message #174371] Wed, 05 July 2006 22:30 Go to previous messageGo to next message
herman_santoso
Messages: 2
Registered: July 2006
Junior Member
I am facing the same problem as well..

can you share me how to resolve it?
Re: standby FAL help [message #184534 is a reply to message #180938] Wed, 26 July 2006 23:28 Go to previous messageGo to next message
anurag078
Messages: 34
Registered: May 2006
Location: West Des Moines
Member


Sometimes, the archive log files which were requested by Standby, might have been backed up to tape already, when FAL request comes from the Standby.

Then you have to manually restore the files in the primary database host, remote copy the files to the standby databse host, manually register the logfiles in the standby database.

Then the standby will apply these files. You can see this in V$ARCHIVED_LOG view in the Standby database.

Re: standby FAL help [message #412909 is a reply to message #174479] Mon, 13 July 2009 06:42 Go to previous messageGo to next message
yuvi1029
Messages: 1
Registered: July 2009
Junior Member
even i hv same prob can u tel me the solution please my id yususf1029@gmail.com
Re: standby FAL help [message #525986 is a reply to message #174371] Fri, 07 October 2011 05:42 Go to previous message
maguirt
Messages: 1
Registered: October 2011
Location: Bristol
Junior Member
I was getting this error despite the archivelogs being present on disk for the primary, and it turned out that the log_archive_dest_state_2 parameter on the primary source database was set to 'RESET', and it was therefore refusing FAL requests. All I had to so was change the parameter to 'ENABLE'.
Previous Topic: Copying Archived log file From Primary to DR
Next Topic: Dataguard Query
Goto Forum:
  


Current Time: Mon Dec 22 22:55:40 CST 2014

Total time taken to generate the page: 0.08864 seconds