Fal Client Arc2 Error 12154

issue-archivelogs not getting applied If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can fal[client, user]: error 1031 post: click the register link above to proceed. To start viewing messages, select

Fal Client User Error 12154 Connecting To Primary For Fetching Gap Sequence

the forum that you want to visit from the selection below. Results 1 to 4 of 4 Thread: dataguard fal[client]: failed to request gap sequence issue-archivelogs not getting applied Tweet Thread Tools Show Printable Version 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 error 16191 connecting to for fetching gap sequence 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). 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

Error 12154 Received Logging On To The Standby

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, MRP0]: Error 12154 connecting to RUBIP1 for fetching gap sequence FAL[client, MRP0]: Error 12154 connecting to RUBIP1 for fetching gap sequence FAL[client, MRP0]: Error 12154 connecting to RUBIP1 for fetching gap sequence FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 12335-12431 DBID 1860283776 branch 613346304 FAL[client]: All defined FAL servers have been attempted. MRP0: Background Media Recovery cancelled with status 16037 MRP0: Background Media Recovery process shutd

Testing Data Guard [message #558524] Sat, 23 June 2012 09:38 patb error 1017 received logging on to the standby Messages: 4Registered: June 2012 Junior Member I have been error 1031 received logging on to the standby trying to setup a test data guard environment to become more familiar with it,

Mrp0 Wait_for_gap

but so far I have been unsuccessful. I have been using the guide located at docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm for the steps I am following. Right http://www.dbasupport.com/forums/showthread.php?55191-dataguard-issue-archivelogs-not-getting-applied now, I'm just trying to get a non-production physical standby configured and working. I have kept kind of a running summary of the commands I have run so far, and would like to paste them below and see if I am missing anything obvious. If necessary, http://www.orafaq.com/forum/t/182259/ I can post a pfile from both servers to see if maybe I am missing something in the parameters. I have verified that both instances can be connected to via sqlplus from the opposite server. Any help or guidance is appreciated. -------- ALTER DATABASE FORCE LOGGING; ALTER DATABASE ADD STANDBY LOGFILE GROUP 10 ('c:\app\pbbesadmin\oradata\primary\standby01.log') SIZE 50M; ALTER DATABASE ADD STANDBY LOGFILE GROUP 11 ('c:\app\pbbesadmin\oradata\primary\standby02.log') SIZE 50M; ALTER DATABASE ADD STANDBY LOGFILE GROUP 12 ('c:\app\pbbesadmin\oradata\primary\standby03.log') SIZE 50M; ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(primary,standby)'; ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=c:\app\pbbesadmin\oradata\primary\ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary'; ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=standby LGWR ASYNC VALID_FOR=(ONlINE_LOGFILES,PRIMARY_ROLES) DB_UNIQUE_NAME=standby'; ALTER SYSTEM SET LOG_ARCHIVE_FORMAT='%t_%s_%r.arc' SCOPE=SPFILE; ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=7; ALTER SYSTEM SET FAL_SERVER=standby; ALTER SYSTEM SET FAL_CLIENT=primary; ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO; SHUTDOWN IMMEDIATE; STARTUP MOUNT; ALTER DATABASE ARCHIVELOG; ALTER DATABASE OPEN; Backup the database: rman target primary BACKUP DATABASE PLUS ARCHIVELOG; SHUTDOWN

±ÈÌØ±Ò Ð¡¶î´û¿î ´û¿î crm ORACLE ÏîÄ¿¹ÜÀíϵͳ thread android python java ±¾°æÎÄÕÂÌû×ÓÓû§ ITPUBÂÛ̳£­Öйú×îרҵµÄIT¼¼ÊõÉçÇø»ÂÛ̳ › ¡Ô ´óÊý¾ÝÓëÊý¾Ý¿â ¡Ô › OracleÊý¾Ý¿â¹ÜÀí http://www.itpub.net/thread-1721487-1-1.html › FAL[client, USER]: Error 12154 connecting to pridb http://arup.blogspot.com/2009/12/resolving-gaps-in-data-guard-apply.html f ... ϸÊý ¡°·Ö²¼Ê½¼ÆËãϵͳ¡±ÁîÄ㲻ˬµÄÄÇЩ˲¼ä£¡ oracle¼¼Êõ½»Á÷Ⱥ£¬»¶Ó­´ó¼Ò¼ÓÈ룡 ´óÊý¾Ýʱ´ú£¬Ã¿¼Ò¹«Ë¾¶¼ÒªÓдóÊý¾Ý²¿ÃÅ£¿ 12 / 2 Ò³ÏÂÒ»Ò³ ·µ»ØÁÐ±í ²é¿´: 7046|»Ø¸´: 10 ÊÕ²Ø | [±¸·Ý»Ö¸´] FAL[client, USER]: Error 12154 connecting to pridb for fetching gap sequence [¸´ÖÆÁ´½Ó] esou esou µ±Ç°ÀëÏß »ý·Ö101 error 12154 IP¿¨ ¹·×п¨ ÂÛ̳»ÕÕÂ:5 µçÌÝÖ±´ï 1# ·¢±íÓÚ 2012-9-24 14:37 | Ö»¿´¸Ã×÷Õß |µ¹Ðòä¯ÀÀ |ÔĶÁģʽ ÔÚн¨µÄDR serverÀïÃæÎÞ·¨Ó¦ÓôÓÖ÷¿âÉÏcopy¹ýÀ´µÄarchive log, ¸ù¾ÝÈçÏ´íÎóÏÔʾÊǶªÊ§log 43064,µ«ÎÒÓÃselect applied...Óï¾ä²éѯ¸Ãlog״̬ÏÔʾÊÇApplied״̬¡£Èç¹ûÎÒÖØÐÂ×¢²áÒ»±é£¬ÔÙÓ¦ÓÃÒ»±é£¬¾Í»á·¢ÏÖ±»Ó¦ÓÃÁËÁ½´Î£¬ÈçÏÂËùʾ¡£Õâ¸ölogÊÇÎÒ´Ó±¸·Ý´Å´ø»Ö¸´³öÀ´µÄ£¬µ«Ä¿Ç°Êý¾Ý¿âÖÐÏÔʾÒѾ­applied״̬µÄlogÊÇ44869£¬Èç¹û¶¼Òª»Ö¸´µÄ»°»áÓÐ1800¶à¸ö£¬¶øÇÒ»¹²»ÖªµÀÖØÐÂÓ¦ÓÃÒ»±éÊÇ·ñÄܽâ¾ö´ËÎÊÌâ¡£ ÇëÎÊÕâ¸öÎÊÌâ»áÊÇʲôԭÒòµ¼Öµģ¬´ó¼ÒÊÇ·ñÓÐʲôºÃµÄ½â¾ö°ì·¨£¿Ð»Ð»£¡ SQL> select sequence#,applied from v$archived_log where sequence#=43063; SEQUENCE# APPLIE ---------- ------ 43064 YES 43064 YES SQL> select message from v$dataguard_status; MESSAGE received logging on ------------------------------------------------------------------------------ ARC0: Archival started ARC1: Archival started ARC2: Archival started ARC3: Archival started ARC4: Archival started ARC5: Archival started ARC6: Archival started ARC7: Archival started ARC8: Archival started ARC9: Archival started ARC0: Becoming the 'no FAL' ARCH MESSAGE ------------------------------------------------------------------------------ ARC0: Becoming the 'no SRL' ARCH ARC1: Becoming the heartbeat ARCH Media Recovery Start: Managed Standby Recovery Managed Standby Recovery not using Real Time Apply Media Recovery Waiting for thread 1 sequence 43064 Fetching gap sequence in thread 1, gap sequence 43064-43064 FAL[client, USER]: Error 12154 connecting to pridb for fetching gap sequence FAL[client, USER]: Error 12154 connecting to pridb for fetching gap sequence FAL[client, USER]: Error 12154 connecting to pridb for fetching gap sequence FAL[client, USER]: Error 12154 connecting to pridb for fetching ga

by the reviewers are theirs alone and may not reflect my opinion whether implied or not. None 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 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. 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 the terms of wall clock. To know that I used the scn_to_timestamp function to translate the SCN to a timestamp:SQL> select scn_to_timestamp(1447102) from dual;SCN_TO_TIMESTAMP(1447102)-------------------------------18-DEC-09 08.54.28.000000000 AMI ran the same query to know the timestamp associated with the SCN of the standby database as well (note, I ran it on the primary database, though; since it will fail in the standby in a mounted mode):SQL> select scn_to_timestamp(1301571) from dual;SCN_TO_TIMESTAMP(1301571)------------