Fal Client User Error 12154
Contents |
issue-archivelogs not getting applied If this is your first visit, be sure to check out the FAQ by fal client user error 12154 connecting to clicking the link above. You may have to register before you
Fal Client User Error 12154 Connecting To For Fetching Gap Sequence
can post: click the register link above to proceed. To start viewing messages, select the forum error 12154 fetching gap sequence that you want to visit from the selection below. Results 1 to 4 of 4 Thread: dataguard issue-archivelogs not getting applied Tweet Thread Tools Show Printable Version
Fal[client, User]: Error 1031 Connecting To
Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-17-2007,12:14 PM #1 areeb View Profile View Forum Posts Junior Member Join Date Jul 2005 Posts 87 dataguard issue-archivelogs not getting applied Hi Guys, Trying to configure standby(phyiscal) having following issues database version 10g(hp-ux 11.2). fal[client]: failed to request gap sequence Here are the output for the following queries. SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY; PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS --------- ------------ ---------- ---------- ---------- ---------- ARCH CONNECTED 0 0 0 0 ARCH CONNECTED 0 0 0 0 MRP0 WAIT_FOR_GAP 2 10902 0 0 SQL> select * from v$archive_gap; no rows selected SQL> SELECT max(sequence#) from v$archived_log where applied='YES'; MAX(SEQUENCE#) select message from v$dataguard_status; MESSAGE -------------------------------------------------------------------------------- ARC0: Archival started ARC1: Archival started ARC0: Becoming the 'no FAL' ARCH ARC0: Becoming the 'no SRL' ARCH ARC1: Becoming the heartbeat ARCH Attempt to start background Managed Standby Recovery process MRP0: Background Managed Standby Recovery process started Managed Standby Recovery not using Real Time Apply Media Recovery Waiting for thread 1 sequence 12335 Fetching gap sequence in thread 1, gap sequence 12335-12431 FAL[client, MRP0]: Error 12154 connecting to RUBIP1 for fetching gap sequence MESSAGE -------------------------------------------------------------------------------- FAL[client, MRP0]: Error 12154 connecting to RUBIP1 for fetching gap sequence FAL[client, M
June 15, 2016 - 1:15 am UTC Category: Database – Version: 11.2.0.4 Latest Followup You
Fal[client]: All Defined Fal Servers Have Been Attempted.
Asked Hi , I had to build new physical
Error 12154 Received Logging On To The Standby
standby with enabling log shipping, as this is m y first time have faced how to resolve archive gap in standby database few difficulties. Errors in file /u01/app/diag/rdbms/daqibliv_stby/DAQIBLIV/trace/DAQIBLIV_mrp0_10554.trc: ORA-00313: open failed for members of log group 3 of thread 1 ORA-00312: online log 3 thread 1: http://www.dbasupport.com/forums/showthread.php?55191-dataguard-issue-archivelogs-not-getting-applied '/data/IBDATA/DAQIBLIVE/redo03.log' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Clearing online redo logfile 3 complete Media Recovery Waiting for thread 1 sequence 1831 Fetching gap sequence in thread 1, gap sequence 1831-1831 Error 12154 received logging on to the https://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:9529765900346770886 standby FAL[client, USER]: Error 12154 connecting to DAQIBLIV_STBY for fetching gap sequence Completed: alter database recover managed standby database disconnect from session Mon Jun 13 11:39:08 2016 Error 12154 received logging on to the standby FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 1831-1831 DBID 3565392237 branch 883597935 FAL[client]: All defined FAL servers have been attempted. I cannot see RFS being started also little confused between locations for convert_log_file_name and dest_1 paths:- *.log_archive_dest_1='location=/data/IBDATA/DAQIBLIVE/' *.log_archive_dest_2='SERVICE=DAQIBLIV_STBY NOAFFIRM ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DAQIBLIV_STBY' *.log_file_name_convert='/data/IBDATA/DAQIBLIVE/redo01.log','/data/ibdata/DAQIBLIVE/redo01.log','/data1/IBLIVE/DAQIBLIVE/redo02.log','/data1/redo02.log','/data/IBDATA/DAQIBLIV E/redo03.log','/data/ibdata/DAQIBLIVE/redo03.log' and we said... 12154 is the error you get when we've got a connectivity issue, most typically a problem with tnsnames.ora. For example, I have no "blah" entry in my tnsnames.ora C:\>sqlplus qwe/qwe@blah SQL*Plus: Release 12.1.0.2.0 Production on Wed Jun 15 09:13:28 2016 Copyright (c) 1982, 2014, Oracle. All rights reserved. ERROR: ORA-12154: TNS:could not resolve the connec
by the reviewers are theirs alone and may not reflect my opinion whether implied or not. None http://arup.blogspot.com/2009/12/resolving-gaps-in-data-guard-apply.html of the advice is warranted to be free of errors and ommision. Please use at your own risk and after thorough testing in your environment. Pages Home Collection of Some of My Very Popular Published Web Articles Friday, December 18, 2009 Resolving Gaps in Data Guard Apply Using Incremental RMAN BAckup Recently, we had a glitch on error 12154 a Data Guard (physical standby database) on infrastructure. This is not a critical database; so the monitoring was relatively lax. And that being done by an outsourcer does not help it either. In any case, the laxness resulted in a failure remaining undetected for quite some time and it was eventually discovered only when the customer complained. fal client user This standby database is usually opened for read only access from time to time.This time, however, the customer saw that the data was significantly out of sync with primary and raised a red flag. Unfortunately, at this time it had become a rather political issue.Since the DBA in charge couldn't resolve the problem, I was called in. In this post, I will describe the issue and how it was resolved. In summary, there are two parts of the problem:(1) What happened(2) How to fix itWhat HappenedLet's look at the first question - what caused the standby to lag behind. First, I looked for the current SCN numbers of the primary and standby databases. On the primary:SQL> select current_scn from v$database;CURRENT_SCN----------- 1447102On the standby:SQL> select current_scn from v$database;CURRENT_SCN----------- 1301571Clearly there is a difference. But this by itself does not indicate a problem; since the standby is expected to lag behind the primary (this is an asynchronous non-real time apply setup). The real question is how much it is lagging in th