Dataguard Gap

What happend to the dataguard if it lost a archive_log sequence and it doesn´t event apear on disk?

If there is a gap on the standby, then it will request the missing logs from the privary via the fal_server, fal_client parameters.
If the logs are not on disk on the primary then you will need to restore from backup. (or maybe they are still in online logs and you need to switch logs ?)
If you don't have a backup, then you can recover the standby via an incremental backup instead of the missing archivelogs.

Similar Messages

Dataguard GAP showing in Minus(-)

hi there,
we have just migrated from oracle 9.2.0.3.0 to 11.2.3.0 on IBM - AIX
DR also have been migrated from 9.2.0.3.0 to 11.2.3.0.
previously we used to check for the DR GAP count with the help of below query on 9i.
{code}
SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
FROM
(SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
(SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
WHERE
ARCH.THREAD# = APPL.THREAD#
ORDER BY 1;
{code}
{code}
Thread Last Sequence Received Last Sequence Applied Difference
1
403280
404811
-1531
{code}
so why its showing the difference in Minus.
MRP process is down when there was a GAP of 7000 logs. and some 1000 logs have been copied manually. and below command have been fired on DR site
{code}
alter database recover standby database
{code}
so friends what is the issue here. need help.

V$LOG_HISTORY displays log history information from the control file.
V$LOG_HISTORY is obsolete and retained for backwards compatibility only.
V$ARCHIVED_LOG displays archived log information from the control file, including archive log names. An archive log record is inserted after the online redo log is successfully archived or cleared (name column is NULL if the log was cleared). If the log is archived twice, there will be two archived log records with the same THREAD#, SEQUENCE#, and FIRST_CHANGE#, but with a different name. An archive log record is also inserted when an archive log is restored from a backup set or a copy and whenever a copy of a log is made with the RMAN COPY command.
How to Clean-Up Entries in V$LOG_HISTORY, V$ARCHIVED_LOG (Doc ID 1060139.6)
Best Regards
mseberg

Archive log not shipped to standby.

Dear Experts,
We have are using oracle 10.2.0.4.0 on AIX.
And we have configured physical standby database which was working fine till date.
suddenly i found that the MRP process is waiting for gap.
i have all the archive logs on the primary system and all the logs are getting shipped to standby database expect one file.
/oracle/PRD/saparch/PRDarch1_46811_755493268.dbf only this file is not getting shipped to standby database....due to which the standby is waiting for this log.
log applied till 46810
other logs are getting shipped.
However i tried to manually copy this log to standby but it didnt start applying this log.
and i heard that if i copy the log file manually then i need to register it...please let me know how to register it if it is the correct method.
Please help to overcome this issue....
Thanks,
Shankar.
Edited by: Shankar Viji on Jun 19, 2012 10:34 PM

Shankar Viji wrote:
Dear Mesberg,
Is there any way to over come this bug.
Bug 6851669 - ORA-308 / ORA-27037 from Dataguard GAP resolution [ID 6851669.8]
if not i am planing to take offline backup of my primary and restore it on standby and start the DR again.
Please suggest is that the correct way to do it r not.
Thanks,
Shankar.
Edited by: Shankar Viji on Jun 21, 2012 10:51 PMHi,
It looks for me that archive unable to read, it may be because of any header verification or corrupted blocks.
Now do you have backup of archives ?
If so restore it and retry again.
If not, I suggest you to go with incremental scn for standby instead of recreation whole DR.
Check this link http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/

Fal_srver and fal_client doubt

Hi friends,
I have doubt on this parameter FAL_SERVER and Fal_client.
1.In oracle 11g FAL_CLIENT initialization no more required. then what about FAL_SERVER parameter ?
2.Is it mandatory to initialize the parameters during data guard configuration FAL_SERVER and FAL_CLIENT ?
3.if not mandatory then how automatic gap resolution done in case of dataguard ?
4.what is the role of archiver process in dataguard gap resolution ?
Thanks & Regards
Arya

Hi,
1.In oracle 11g FAL_CLIENT initialization no more required. then what about FAL_SERVER parameter ?
Yes, after 11g version FAL_CLIENT is no more required. FAL_SERVER parameter is require for data guard configuration.
2.Is it mandatory to initialize the parameters during data guard configuration FAL_SERVER and FAL_CLIENT ?
FAL_SERVER paramater is only for mandatory standby database. because, RFS using FAL_SERVER parameter for request redo changes.
FAL_SERVER is primary database.
3.if not mandatory then how automatic gap resolution done in case of dataguard ?
It is mandatory. When Automatic Gap Resolution is using standby database, RFS process using FAL_SERVER parameter for request
redo from primary for resolution redo gap.
4.what is the role of archiver process in dataguard gap resolution ?
When occur redo gap. Standby send request to primary via RFS, requested archive log sequence#.
NLS send info to ARCH process, and ARCH process connecting to standby RFS and sending requested archived log.
and MRP apply received archived logs.
Regards
Mahir M. Quluzade
http://www.mahir-quluzade.com

Gaps in Oracle Dataguard Standby

Hello,
The system is a Logical Standby Dataguard.
With the following query it is possible to see that there are gaps:
SQL> set numformat 99999999999
SQL> set linesize 2000
SQL> set pagesize 20000
SQL> select thread# trd, sequence#,
2 first_change#, next_change#,
3 dict_begin beg, dict_end end,
4 to_char(timestamp, 'DD-MON-YYYY HH24:MI:SS') timestamp,
5 (case when l.next_change# < p.read_scn then 'YES'
6 when l.first_change# < p.applied_scn then 'CURRENT'
7 else 'NO' end) applied
8 from dba_logstdby_log l, dba_logstdby_progress p
9 order by thread#, first_change#;
1 614 18542918309 18542918429 NO NO 04-DEC-2009 09:31:11 YES
1 633 18543602669 18543836687 NO NO 04-DEC-2009 09:31:10 YES
1 637 18543836687 18544028244 NO NO 04-DEC-2009 09:31:10 YES
1 12832 203846572934 203846572944 NO NO 22-DEC-2009 09:31:10 YES
Although all of them are APPLIED, and it is still receiving and applying the redo, it seems like there are some gaps.
How can I check that the Standby is totally synchronized? How can I check if the Standby has still those archive logs that haven't been applied?
Thanks in advance.

There are errors in the alert of the Primary on the 4th of Dec. and it seems like the Primary had problems trying to do the archive in the Standby:
Error 1034 received logging on to the standby
Errors in file /opt/oracle/diag/rdbms/db_s2/DB1/trace/DB1_arc5_15720.trc:
ORA-01034: ORACLE not available
FAL[server, ARC5]: FAL archive failed, see trace file.
Errors in file /opt/oracle/diag/rdbms/db_s2/DB1/trace/DB1_arc5_15720.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance DB1 - Archival Error. Archiver continuing.
The thing is that I don't know if those archive logs where sent or not to the Standby and if the Standby applied them or not.
By the following query, it seems like there are some archive logs that weren't applied, but the strange thing is that the Standby is still working and applying and that there are archive logs from today which have been received and applied, and as far as I know, the DG stops applying if there are gaps...
1 633 18543602669 18543836687 NO NO 04-DEC-2009 09:31:10 YES
1 637 18543836687 18544028244 NO NO 04-DEC-2009 09:31:10 YES
1 12832 203846572934 203846572944 NO NO 22-DEC-2009 09:31:10 YES
...

Log gap detection WITHOUT Dataguard

Heys,
I am looking for a solution to keep my standby database up2date.
I set up the enviroment according to http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
The RedoLog Apply works fine.
But how can I ensure that log are re-transfered so that no gaps come up.
Is there a way to manually configure this ?
Thx for your help
Christian

Check this script
SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
Go for real time apply

DataGuard Standby 環境で db が open できない.

DataGuard Standby 環境で db が open できなくて困っています。
詳しい方いれば、原因と対処方法を教えていただきたいと思います。
create した spfile が正確に読み込まれていないことが原因のようなのですが。。
なぜ読み込めないのかが分からない状態です。
pfile を読み込んだ起動は可能ですが、spfile を読み込んだ起動の前提条件とは、
何なのでしょうか。単に整合性が取れていないだけなのか、それとも、、。
[grid@osaka1 shell]$ asmcmd
ASMCMD> ls
DATA/
FRA/
ASMCMD> cd data
ASMCMD> ls
ASM/
WEST/
ASMCMD> ls -l
Type Redund Striped Time             Sys Name
                                        Y    ASM/
                                        N    WEST/
ASMCMD>
ASMCMD> cd west
ASMCMD> ls
CONTROLFILE/
DATAFILE/
ONLINELOG/
PARAMETERFILE/
TEMPFILE/
spfilewest.ora
ASMCMD> ls -l
Type           Redund Striped Time             Sys Name
                                                 N    CONTROLFILE/
                                                 N    DATAFILE/
                                                 N    ONLINELOG/
                                                 N    PARAMETERFILE/
                                                 N    TEMPFILE/
                                                 N    spfilewest.ora => +DATA/WEST/PARAMETERFILE/spfile.257.824236121
ASMCMD> pwd
+data/west
ASMCMD>
ASMCMD> cd para*
ASMCMD> ls -l
Type           Redund Striped Time             Sys Name
PARAMETERFILE MIRROR COARSE   AUG 23 18:00:00 Y    spfile.257.824236121
ASMCMD>
ASMCMD> pwd
+data/west/PARAMETERFILE
ASMCMD> quit
[grid@osaka1 shell]$
[oracle@osaka1 dbs]$ more initHPYMUSIC.ora
SPFILE='+DATA/west/spfilewest.ora'
[oracle@osaka1 dbs]$
よろしくお願い致します。
ps.
ORA-12154 は整合性の問題であるので、それを合わせれば消えると思っています。
そもそも RAC を前提としていたのですが、それを standalone に置き換えて検証始めた結果、
こうなってしまっています。
open できない原因が ORA-12154 だったりして。。
■ プライマリの場合
○ open するほうは、シンプルに以下だけで open することが確認できる。
   が、db_name を変更した関係で
   「ORA-12154: TNS: 指定された接続識別子を解決できませんでした」
   が出続けている。
   ORA-12154 は db が open できない原因とは無関係かもしれない。
srvctl stop database -d east -f
srvctl start database -d east -o open
srvctl config database -d east
srvctl status database -d east
○ 参考出力
set linesize 500 pages 0
col value for a90
col name for a50
select name, value
from v$parameter
where name in ('db_name','db_unique_name','log_archive_config', 'log_archive_dest_1','log_archive_dest_2',
               'log_archive_dest_state_1','log_archive_dest_state_2', 'remote_login_passwordfile',
               'log_archive_format','log_archive_max_processes','fal_server','db_file_name_convert',
               'log_file_name_convert', 'standby_file_management');
SQL>
db_file_name_convert
log_file_name_convert
log_archive_dest_1
log_archive_dest_2            SERVICE=HPYMUSIC SYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=west
log_archive_dest_state_1      enable
log_archive_dest_state_2      enable
fal_server
log_archive_config
log_archive_format            %t_%s_%r.dbf
log_archive_max_processes     4
standby_file_management       AUTO
remote_login_passwordfile     EXCLUSIVE
db_name                       HPYMUSIC
db_unique_name                HPYMUSIC    ← ▼ db_name だけを変更したつもりが db_unique_name も変更されていた
14行が選択されました。
[oracle@tokyo1 shell]$ srvctl stop database -d east -f
[oracle@tokyo1 shell]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Cluster Resources
ora.east.db
      1        OFFLINE OFFLINE                               Instance Shutdown
[oracle@tokyo1 shell]$ srvctl start database -d east -o open
[oracle@tokyo1 shell]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Local Resources
ora.DATA.dg
               ONLINE ONLINE       tokyo1
ora.FRA.dg
               ONLINE ONLINE       tokyo1
ora.LISTENER.lsnr
               ONLINE ONLINE       tokyo1
ora.asm
               ONLINE ONLINE       tokyo1                   Started
Cluster Resources
ora.cssd
      1        ONLINE ONLINE       tokyo1
ora.diskmon
      1        ONLINE ONLINE       tokyo1
ora.east.db
      1        ONLINE ONLINE       tokyo1                   Open ← ▼
[oracle@tokyo1 shell]$
[oracle@tokyo1 shell]$ srvctl config database -d east
一意のデータベース名: east
データベース名: east
Oracleホーム: /u01/app/oracle/product/11.2.0/dbhome_1
Oracleユーザー: grid
spfile: +DATA/east/spfileeast.ora
ドメイン:
開始オプション: open
停止オプション: immediate
データベース・ロール: PRIMARY
管理ポリシー: AUTOMATIC
ディスク・グループ: DATA,FRA
サービス:
[oracle@tokyo1 shell]$ srvctl status database -d east
データベースは実行中です。
Fri Aug 23 19:44:10 2013
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_7579.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
[oracle@tokyo1 dbs]$ pwd
/u01/app/oracle/product/11.2.0/dbhome_1/dbs
[oracle@tokyo1 dbs]$
[oracle@tokyo1 dbs]$
[oracle@tokyo1 dbs]$ more 2013.08.23_east_pfile.txt
HPYMUSIC.__db_cache_size=301989888
HPYMUSIC.__java_pool_size=4194304
HPYMUSIC.__large_pool_size=8388608
HPYMUSIC.__pga_aggregate_target=339738624
HPYMUSIC.__sga_target=503316480
HPYMUSIC.__shared_io_pool_size=0
HPYMUSIC.__shared_pool_size=176160768
HPYMUSIC.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/east/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+DATA/east/controlfile/current.270.823277705','+FRA/east/controlfile/current.
260.823277707'
*.db_block_checking='TRUE'
*.db_block_checksum='TRUE'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_name='HPYMUSIC'
*.db_recovery_file_dest='+FRA'
*.db_recovery_file_dest_size=3038773248
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=HPYMUSICXDB)'
*.log_archive_format='%t_%s_%r.dbf'
*.memory_target=842006528
*.nls_language='JAPANESE'
*.nls_territory='JAPAN'
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
Fri Aug 23 19:49:38 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
ARCH: Warning; less destinations available than specified
by LOG_ARCHIVE_MIN_SUCCEED_DEST init.ora parameter
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/dbhome_1/dbs/spfileHPYMUSIC.ora
System parameters with non-default values:
processes                = 150
nls_language             = "JAPANESE"
nls_territory            = "JAPAN"
memory_target            = 804M
control_files            = "+DATA/east/controlfile/current.270.823277705"
control_files            = "+FRA/east/controlfile/current.260.823277707"
db_block_checksum        = "TRUE"
db_block_size            = 8192
compatible               = "11.2.0.0.0"
log_archive_dest_2       = "SERVICE=HPYMUSIC SYNC NOAFFIRM VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=west"
log_archive_format       = "%t_%s_%r.dbf"
db_create_file_dest      = "+DATA"
db_recovery_file_dest    = "+FRA"
db_recovery_file_dest_size= 2898M
standby_file_management = "AUTO"
undo_tablespace          = "UNDOTBS1"
db_block_checking        = "TRUE"
remote_login_passwordfile= "EXCLUSIVE"
db_domain                = ""
dispatchers              = "(PROTOCOL=TCP) (SERVICE=HPYMUSICXDB)"
audit_file_dest          = "/u01/app/oracle/admin/east/adump"
audit_trail              = "DB"
db_name                  = "HPYMUSIC"
open_cursors             = 300
diagnostic_dest          = "/u01/app/oracle"
Fri Aug 23 19:49:39 2013
PMON started with pid=2, OS id=8442
Fri Aug 23 19:49:39 2013
VKTM started with pid=3, OS id=8444 at elevated priority
VKTM running at (10)millisec precision with DBRM quantum (100)ms
Fri Aug 23 19:49:39 2013
GEN0 started with pid=4, OS id=8448
Fri Aug 23 19:49:39 2013
DIAG started with pid=5, OS id=8450
Fri Aug 23 19:49:39 2013
DBRM started with pid=6, OS id=8452
Fri Aug 23 19:49:39 2013
PSP0 started with pid=7, OS id=8454
Fri Aug 23 19:49:39 2013
DIA0 started with pid=8, OS id=8456
Fri Aug 23 19:49:39 2013
MMAN started with pid=9, OS id=8458
Fri Aug 23 19:49:39 2013
DBW0 started with pid=10, OS id=8460
Fri Aug 23 19:49:39 2013
LGWR started with pid=11, OS id=8462
Fri Aug 23 19:49:39 2013
CKPT started with pid=12, OS id=8464
Fri Aug 23 19:49:39 2013
SMON started with pid=13, OS id=8466
Fri Aug 23 19:49:39 2013
RECO started with pid=14, OS id=8468
Fri Aug 23 19:49:39 2013
RBAL started with pid=15, OS id=8470
Fri Aug 23 19:49:39 2013
ASMB started with pid=16, OS id=8472
Fri Aug 23 19:49:39 2013
MMON started with pid=17, OS id=8474
Fri Aug 23 19:49:39 2013
MMNL started with pid=18, OS id=8478
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
NOTE: initiating MARK startup
starting up 1 shared server(s) ...
Starting background process MARK
Fri Aug 23 19:49:39 2013
MARK started with pid=20, OS id=8482
NOTE: MARK has subscribed
ORACLE_BASE not set in environment. It is recommended
that ORACLE_BASE be set in the environment
Reusing ORACLE_BASE from an earlier startup = /u01/app/oracle
Fri Aug 23 19:49:39 2013
ALTER DATABASE MOUNT
NOTE: Loaded library: System
SUCCESS: diskgroup DATA was mounted
ERROR: failed to establish dependency between database HPYMUSIC and diskgroup resource ora.DATA.dg
SUCCESS: diskgroup FRA was mounted
ERROR: failed to establish dependency between database HPYMUSIC and diskgroup resource ora.FRA.dg
Fri Aug 23 19:49:46 2013
NSS2 started with pid=24, OS id=8572
Successful mount of redo thread 1, with mount id 2951868947
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
ALTER DATABASE OPEN
LGWR: STARTING ARCH PROCESSES
Fri Aug 23 19:49:47 2013
ARC0 started with pid=26, OS id=8574
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Fri Aug 23 19:49:48 2013
ARC1 started with pid=27, OS id=8576
Fri Aug 23 19:49:48 2013
ARC2 started with pid=28, OS id=8578
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Fri Aug 23 19:49:48 2013
ARC3 started with pid=29, OS id=8580
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Error 12154 received logging on to the standby
Fri Aug 23 19:49:51 2013
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_lgwr_8462.trc:
ORA-12154: TNS: ?????????????????????
Error 12154 for archive log file 2 to 'HPYMUSIC'
LGWR: Failed to archive log 2 thread 1 sequence 8 (12154)
Thread 1 advanced to log sequence 8 (thread open)
Thread 1 opened at log sequence 8
Current log# 2 seq# 8 mem# 0: +DATA/hpymusic/onlinelog/group_2.272.824213887
Current log# 2 seq# 8 mem# 1: +FRA/hpymusic/onlinelog/group_2.262.824213889
Successful open of redo thread 1
Fri Aug 23 19:49:51 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Aug 23 19:49:51 2013
SMON: enabling cache recovery
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
Archived Log entry 7 added for thread 1 sequence 7 ID 0xaff1210d dest 1:
Error 12154 received logging on to the standby
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc3_8580.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
FAL[server, ARC3]: Error 12154 creating remote archivelog file 'HPYMUSIC'
FAL[server, ARC3]: FAL archive failed, see trace file.
Errors in file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc3_8580.trc:
ORA-16055: FALリクエストが拒否されました。
ARCH: FAL archive failed. Archiver continuing
ORACLE Instance HPYMUSIC - Archival Error. Archiver continuing.
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is AL32UTF8
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Aug 23 19:49:55 2013
QMNC started with pid=32, OS id=8590
Completed: ALTER DATABASE OPEN
Fri Aug 23 19:49:59 2013
Starting background process CJQ0
Fri Aug 23 19:49:59 2013
CJQ0 started with pid=33, OS id=8609
Fri Aug 23 19:49:59 2013
db_recovery_file_dest_size of 2898 MB is 6.38% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
[root@tokyo1 app]#
[root@tokyo1 app]# more /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc
Trace file /u01/app/oracle/diag/rdbms/hpymusic/HPYMUSIC/trace/HPYMUSIC_arc2_8578.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name:    Linux
Node name:      tokyo1.oracle11g.jp
Release:        2.6.18-348.12.1.el5
Version:        #1 SMP Wed Jul 10 05:28:41 EDT 2013
Machine:        x86_64
Instance name: HPYMUSIC
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 8578, image: [email protected] (ARC2)
*** 2013-08-23 19:49:51.707
*** SESSION ID:(15.1) 2013-08-23 19:49:51.707
*** CLIENT ID:() 2013-08-23 19:49:51.707
*** SERVICE NAME:() 2013-08-23 19:49:51.707
*** MODULE NAME:() 2013-08-23 19:49:51.707
*** ACTION NAME:() 2013-08-23 19:49:51.707
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:49:51.972 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:49:51.972 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:49:51.973 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:49:51.973 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
*** 2013-08-23 19:50:49.816
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:50:50.070 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:50:50.070 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:50:50.070 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:50:50.070 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
*** 2013-08-23 19:51:51.147
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:51:51.403 4132 krsh.c
Error 12154 received logging on to the standby
*** 2013-08-23 19:51:51.403 869 krsu.c
Error 12154 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
Error 12154 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'HPYMUSIC'
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
*** 2013-08-23 19:51:51.403 4132 krsh.c
PING[ARC2]: Heartbeat failed to connect to standby 'HPYMUSIC'. Error is 12154.
*** 2013-08-23 19:51:51.403 2747 krsi.c
krsi_dst_fail: dest:2 err:12154 force:0 blast:1
[root@tokyo1 app]#
[grid@tokyo1 shell]$ ./grid_info_east-x.sh
+ export ORACLE_SID=+ASM
+ ORACLE_SID=+ASM
+ LOGDIR=/home/grid/log
+ PRIMARYDB=east_DGMGRL
+ STANDBYDB=
+ PASSWORD=dataguard
+ mkdir -p /home/grid/log
++ date +%y%m%d,%H%M%S
+ echo 'asm info,130823,195709'
+ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:57:09 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option
に接続されました。
SQL> SQL>
SYSDATE
13-08-23
SQL> SQL> SQL>
NAME                                 TYPE                VALUE
asm_diskgroups                       string              FRA
asm_diskstring                       string              /dev/sd*1
asm_power_limit                      integer             1
asm_preferred_read_failure_groups    string
audit_file_dest                      string              /u01/app/11.2.0/grid/rdbms/audit
audit_sys_operations                 boolean             FALSE
audit_syslog_level                   string
background_core_dump                 string              partial
background_dump_dest                 string              /u01/app/grid/diag/asm/+asm/+ASM/trace
cluster_database                     boolean             FALSE
cluster_database_instances           integer             1
cluster_interconnects                string
core_dump_dest                       string              /u01/app/grid/diag/asm/+asm/+ASM/cdump
db_cache_size                        big integer         0
db_ultra_safe                        string              OFF
db_unique_name                       string              +ASM
diagnostic_dest                      string              /u01/app/grid
event                                string
file_mapping                         boolean             FALSE
filesystemio_options                 string              none
ifile                                file
instance_name                        string              +ASM
instance_number                      integer             1
instance_type                        string              asm
large_pool_size                      big integer         12M
ldap_directory_sysauth               string              no
listener_networks                    string
local_listener                       string
lock_name_space                      string
lock_sga                             boolean             FALSE
max_dump_file_size                   string              unlimited
memory_max_target                    big integer         272M
memory_target                        big integer         272M
nls_calendar                         string
nls_comp                             string              BINARY
nls_currency                         string
nls_date_format                      string
nls_date_language                    string
nls_dual_currency                    string
nls_iso_currency                     string
nls_language                         string              AMERICAN
nls_length_semantics                 string              BYTE
nls_nchar_conv_excp                  string              FALSE
nls_numeric_characters               string
nls_sort                             string
nls_territory                        string              AMERICA
nls_time_format                      string
nls_time_tz_format                   string
nls_timestamp_format                 string
nls_timestamp_tz_format              string
os_authent_prefix                    string              ops$
os_roles                             boolean             FALSE
pga_aggregate_target                 big integer         0
processes                            integer             100
remote_listener                      string
remote_login_passwordfile            string              EXCLUSIVE
remote_os_authent                    boolean             FALSE
remote_os_roles                      boolean             FALSE
service_names                        string              +ASM
sessions                             integer             172
sga_max_size                         big integer         272M
sga_target                           big integer         0
shadow_core_dump                     string              partial
shared_pool_reserved_size            big integer         6081740
shared_pool_size                     big integer         0
sort_area_size                       integer             65536
spfile                               string              +DATA/asm/asmparameterfile/registry.253.823204697
sql_trace                            boolean             FALSE
statistics_level                     string              TYPICAL
timed_os_statistics                  integer             0
timed_statistics                     boolean             TRUE
trace_enabled                        boolean             TRUE
user_dump_dest                       string              /u01/app/grid/diag/asm/+asm/+ASM/trace
workarea_size_policy                 string              AUTO
++ date +%y%m%d,%H%M%S
+ echo 'asmcmd info,130823,195709'
+ asmcmd ls -l
State    Type    Rebal Name
MOUNTED NORMAL N      DATA/
MOUNTED NORMAL N      FRA/
+ asmcmd ls -l 'data/asm/*'
Type              Redund Striped Time             Sys Name
ASMPARAMETERFILE MIRROR COARSE   AUG 11 19:00:00 Y    REGISTRY.253.823204697
+ asmcmd ls -l 'data/east/*'
Type           Redund Striped Time             Sys Name
+data/east/CONTROLFILE/:
CONTROLFILE    HIGH    FINE     AUG 12 15:00:00 Y    Current.260.823276231
CONTROLFILE    HIGH    FINE     AUG 23 19:00:00 Y    Current.270.823277705
+data/east/DATAFILE/:
DATAFILE       MIRROR COARSE   AUG 12 15:00:00 Y    SYSAUX.257.823276133
DATAFILE       MIRROR COARSE   AUG 23 19:00:00 Y    SYSAUX.267.823277615
DATAFILE       MIRROR COARSE   AUG 12 15:00:00 Y    SYSTEM.256.823276131
DATAFILE       MIRROR COARSE   AUG 23 19:00:00 Y    SYSTEM.266.823277615
DATAFILE       MIRROR COARSE   AUG 12 15:00:00 Y    UNDOTBS1.258.823276133
DATAFILE       MIRROR COARSE   AUG 23 19:00:00 Y    UNDOTBS1.268.823277615
DATAFILE       MIRROR COARSE   AUG 12 15:00:00 Y    USERS.259.823276133
DATAFILE       MIRROR COARSE   AUG 23 19:00:00 Y    USERS.269.823277615
+data/east/ONLINELOG/:
ONLINELOG      MIRROR COARSE   AUG 12 15:00:00 Y    group_1.261.823276235
ONLINELOG      MIRROR COARSE   AUG 12 15:00:00 Y    group_2.262.823276241
ONLINELOG      MIRROR COARSE   AUG 12 15:00:00 Y    group_3.263.823276247
+data/east/PARAMETERFILE/:
PARAMETERFILE MIRROR COARSE   AUG 23 12:00:00 Y    spfile.265.823277967
+data/east/TEMPFILE/:
TEMPFILE       MIRROR COARSE   AUG 12 15:00:00 Y    TEMP.264.823276263
TEMPFILE       MIRROR COARSE   AUG 23 19:00:00 Y    TEMP.274.823277733
                                                 N    spfileeast.ora => +DATA/EAST/PARAMETERFILE/spfile.265.823277967
+ asmcmd ls -l 'fra/east/*'
Type         Redund Striped Time             Sys Name
+fra/east/ARCHIVELOG/:
                                               Y    2013_08_12/
                                               Y    2013_08_15/
                                               Y    2013_08_19/
                                               Y    2013_08_22/
                                               Y    2013_08_23/
+fra/east/CONTROLFILE/:
CONTROLFILE HIGH    FINE     AUG 12 15:00:00 Y    Current.256.823276231
CONTROLFILE HIGH    FINE     AUG 23 19:00:00 Y    Current.260.823277707
+fra/east/ONLINELOG/:
ONLINELOG    MIRROR COARSE   AUG 12 15:00:00 Y    group_1.257.823276237
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_10.272.823535727
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_11.273.823535737
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_12.274.823535745
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_13.275.823535757
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_14.276.823535763
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_15.277.823535771
ONLINELOG    MIRROR COARSE   AUG 12 15:00:00 Y    group_2.258.823276245
ONLINELOG    MIRROR COARSE   AUG 12 15:00:00 Y    group_3.259.823276251
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_7.269.823535685
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_8.270.823535695
ONLINELOG    MIRROR COARSE   AUG 23 19:00:00 Y    group_9.271.823535703
+fra/east/STANDBYLOG/:
                                               N    standby_group_07.log => +FRA/EAST/ONLINELOG/group_7.269.823535685
                                               N    standby_group_08.log => +FRA/EAST/ONLINELOG/group_8.270.823535695
                                               N    standby_group_09.log => +FRA/EAST/ONLINELOG/group_9.271.823535703
                                               N    standby_group_10.log => +FRA/EAST/ONLINELOG/group_10.272.823535727
                                               N    standby_group_11.log => +FRA/EAST/ONLINELOG/group_11.273.823535737
                                               N    standby_group_12.log => +FRA/EAST/ONLINELOG/group_12.274.823535745
                                               N    standby_group_13.log => +FRA/EAST/ONLINELOG/group_13.275.823535757
                                               N    standby_group_14.log => +FRA/EAST/ONLINELOG/group_14.276.823535763
                                               N    standby_group_15.log => +FRA/EAST/ONLINELOG/group_15.277.823535771
+ asmcmd find +data 'group*'
+data/EAST/ONLINELOG/group_1.261.823276235
+data/EAST/ONLINELOG/group_2.262.823276241
+data/EAST/ONLINELOG/group_3.263.823276247
+data/HPYMUSIC/ONLINELOG/group_1.271.824213881
+data/HPYMUSIC/ONLINELOG/group_2.272.824213887
+data/HPYMUSIC/ONLINELOG/group_3.273.824213895
+ asmcmd find +data 'spf*'
+data/EAST/PARAMETERFILE/spfile.265.823277967
+data/EAST/spfileeast.ora
+ asmcmd ls -l data/east/CONTROLFILE
Type         Redund Striped Time             Sys Name
CONTROLFILE HIGH    FINE     AUG 12 15:00:00 Y    Current.260.823276231
CONTROLFILE HIGH    FINE     AUG 23 19:00:00 Y    Current.270.823277705
+ asmcmd find +fra 'group*'
+fra/EAST/ONLINELOG/group_1.257.823276237
+fra/EAST/ONLINELOG/group_10.272.823535727
+fra/EAST/ONLINELOG/group_11.273.823535737
+fra/EAST/ONLINELOG/group_12.274.823535745
+fra/EAST/ONLINELOG/group_13.275.823535757
+fra/EAST/ONLINELOG/group_14.276.823535763
+fra/EAST/ONLINELOG/group_15.277.823535771
+fra/EAST/ONLINELOG/group_2.258.823276245
+fra/EAST/ONLINELOG/group_3.259.823276251
+fra/EAST/ONLINELOG/group_7.269.823535685
+fra/EAST/ONLINELOG/group_8.270.823535695
+fra/EAST/ONLINELOG/group_9.271.823535703
+fra/HPYMUSIC/ONLINELOG/group_1.261.824213883
+fra/HPYMUSIC/ONLINELOG/group_2.262.824213889
+fra/HPYMUSIC/ONLINELOG/group_3.263.824213897
+ asmcmd find +fra 'spf*'
+ asmcmd ls -l fra/east/CONTROLFILE
Type         Redund Striped Time             Sys Name
CONTROLFILE HIGH    FINE     AUG 12 15:00:00 Y    Current.256.823276231
CONTROLFILE HIGH    FINE     AUG 23 19:00:00 Y    Current.260.823277707
++ date +%y%m%d,%H%M%S
+ echo END,130823,195712
[grid@tokyo1 shell]$
■ 以下、スタンバイ側 ■ ■ ■ ■ ■ ■ ■
export ORACLE_SID=HPYMUSIC
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
create spfile='+data/west/spfilewest.ora' from pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt';
srvctl stop database -d west -f
srvctl start database -d west -o open
srvctl start database -d west -o mount
srvctl start database -d west
startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
srvctl start database -d west -o open
srvctl config database -d west
srvctl status database -d west
alter database recover managed standby database disconnect from session;
select name, database_role, open_mode from gv$database;
srvctl modify database -d west -s open
○ spfile を作成する
export ORACLE_SID=HPYMUSIC
sqlplus / as sysdba
startup nomount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
create spfile='+data/west/spfilewest.ora' from pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt';
○ 落とす
srvctl stop database -d west -f
○ open したいが起動しない（ Mounted (Closed) 状態で起動することもある）。
srvctl start database -d west -o open
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ open したいが起動しない（ Mounted (Closed) 状態で起動することもある）。
srvctl start database -d west -o mount
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ open したいが起動しない（ Mounted (Closed) 状態で起動することもある）。
srvctl start database -d west
PRCR-1079 : リソースora.west.dbの起動に失敗しました
CRS-2674: Start of 'ora.west.db' on 'osaka1' failed
○ 起動するがエラーあり（ alert_HPYMUSIC.log ）
startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
[oracle@osaka1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:05:35 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
アイドル・インスタンスに接続しました。
SQL> startup mount pfile='/u01/app/oracle/product/11.2.0/dbhome_1/dbs/pfile_for_standby_HPYMUSIC.txt'
ORACLEインスタンスが起動しました。
Total System Global Area 839282688 bytes
Fixed Size                  2217992 bytes
Variable Size             515901432 bytes
Database Buffers          314572800 bytes
Redo Buffers                6590464 bytes
データベースがマウントされました。
Error 12154 received logging on to the standby
FAL[client, ARC3]: Error 12154 connecting to HPYMUSIC for fetching gap sequence
Errors in file /u01/app/oracle/diag/rdbms/west/HPYMUSIC/trace/HPYMUSIC_arc3_25690.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
Errors in file /u01/app/oracle/diag/rdbms/west/HPYMUSIC/trace/HPYMUSIC_arc3_25690.trc:
ORA-12154: TNS: 指定された接続識別子を解決できませんでした
○ open にならず Mounted (Closed) としかなってくれない。
srvctl start database -d west -o open
[oracle@osaka1 dbs]$ srvctl start database -d west -o open
[oracle@osaka1 dbs]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Local Resources
ora.DATA.dg
               ONLINE ONLINE       osaka1
ora.FRA.dg
               ONLINE ONLINE       osaka1
ora.LISTENER.lsnr
               ONLINE ONLINE       osaka1
ora.asm
               ONLINE ONLINE       osaka1                   Started
Cluster Resources
ora.cssd
      1        ONLINE ONLINE       osaka1
ora.diskmon
      1        ONLINE ONLINE       osaka1
ora.west.db
      1        ONLINE INTERMEDIATE osaka1                   Mounted (Closed)
○
srvctl config database -d west
srvctl status database -d west
[oracle@osaka1 dbs]$ srvctl config database -d west
一意のデータベース名: west
データベース名: HPYMUSIC
Oracleホーム: /u01/app/oracle/product/11.2.0/dbhome_1
Oracleユーザー: grid
spfile: +data/west/spfilewest.ora
ドメイン:
開始オプション: open
停止オプション: immediate
データベース・ロール: physical_standby
管理ポリシー: AUTOMATIC
ディスク・グループ: DATA,FRA
サービス:
[oracle@osaka1 dbs]$ srvctl status database -d west
データベースは実行中です。
○ mrp プロセスが起動するが、Read Only ではない。
alter database recover managed standby database disconnect from session;
select name, database_role, open_mode from gv$database;
[oracle@osaka1 dbs]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on 金 8月 23 19:33:08 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
に接続されました。
SQL>
SQL> alter database recover managed standby database disconnect from session;
データベースが変更されました。
SQL> select name, database_role, open_mode from gv$database;
NAME                        DATABASE_ROLE
OPEN_MODE
HPYMUSIC                    PHYSICAL STANDBY
MOUNTED
[root@osaka1 app]# ps -ef |egrep -i mrp
oracle   26269     1 0 19:33 ?        00:00:00 ora_mrp0_HPYMUSIC
○ modify しても open にならない。
srvctl modify database -d west -s open
[oracle@osaka1 dbs]$ srvctl modify database -d west -s open
[oracle@osaka1 dbs]$ /u01/app/11.2.0/grid/bin/crsctl status resource -t
NAME           TARGET STATE        SERVER                   STATE_DETAILS
Local Resources
ora.DATA.dg
               ONLINE ONLINE       osaka1
ora.FRA.dg
               ONLINE ONLINE       osaka1
ora.LISTENER.lsnr
               ONLINE ONLINE       osaka1
ora.asm
               ONLINE ONLINE       osaka1                   Started
Cluster Resources
ora.cssd
      1        ONLINE ONLINE       osaka1
ora.diskmon
      1        ONLINE ONLINE       osaka1
ora.west.db
      1        ONLINE INTERMEDIATE osaka1                   Mounted (Closed)

standby 側に、アーカイブログファイルを少し適用すれば open できそうに感じます。
これを解決するためには、以下のエラーを解決するのがよいと思います。
・ORA-12154: TNS: 指定された接続識別子を解決できませんでした
両ノードの tnsnames.ora を確認させて貰えますか？
この推測が間違えていたら再検討しましょう。

Archive log can not ship to GAP logfiles to standby DB automatically

we have a non-real time standby database, which will receive the archive file from the primary database server most of the time, and will apply the logfiles only at one point of time daily.
Some times, we need to shutdown the Standby DB server for a while ( 3-4 hours).
The missed logfiles will catch up during the standby down time later.
But since last week we had an storage incident, the primary DB server stops to catch up the missed logfiles, and saw this message at the archvie trace file:
ABC: tkrsf_al_read: No mirror copies to re-read data
Current, we found the archive log gaps on the standby server, and have to manually copy those logfiles over and register them.
Saw some tips on the internet to change the parameter "log_archive_max_processes", but no help for us at all.
Here is the parameter on the Primary DB server:
log_archive_dest_2 = SERVICE=Standby_server reopen=300

which will receive the archive file from the primary database server most of the timeMost times from primary. Then remaining times? so you Copy manually and register?
Then it's dataguard not an manual standby.
Error 1034 received logging on to the standby
Errors in file /******/***arc210536.trc:
ORA-01034: ORACLE not available
FAL[server, ARC2]: FAL archive failed, see trace file.these errors in primary when , stanby is down and when primary tries to connect to standby, so tese errors not considerable to investigate ,
When you don't want to apply archives on standby no need to shutdown. Just put this value log_archive_dest_state_2='defer'
Once you enable check what are the errors in primary alert log file.
How is your network band width speed? Is it capable to hold that much archive data?
May be it will take some time when you pause & start.
Also use LGWR in log_archive_dest_2 for real time apply after creatin standby redo logs.
So post the alert log information once you enable standby database.

DataGuard FAL Client not re-transfering log

Hey, in my dataguard config the standby system detects a log gap.
The log on the primary site was not marked for the standby location - thats a known bug. OK.
But anyway, when the standby system detects a log gap, why is it not requesting the missing logfile from the primary site. Its still available on the primary site in the FRA.
#Standbysite - Detecting log-gap
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Media Recovery Waiting for thread 2 sequence 164952
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Fetching gap sequence in thread 2, gap sequence 164952-164952
Redo shipping client performing standby login
#Primiary Site - check for missing logfile
SQL> SELECT name FROM v$archived_log where sequence# like'164952';
NAME
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stdynode3-vip.local)(PORT
=1521)))(CONNECT_DATA=(SERVICE_NAME=TEST_XPT.local)(INSTANCE_NAME=TEST3)(SERVER
=dedicated)))
+FLASH/testp/1_164952_692118044.dbf
+FLASH/testp/2_164952_692118044.dbf
SQL>

Christian wrote:
Hey, in my dataguard config the standby system detects a log gap.
The log on the primary site was not marked for the standby location - thats a known bug. OK.
But anyway, when the standby system detects a log gap, why is it not requesting the missing logfile from the primary site. Its still available on the primary site in the FRA.
#Standbysite - Detecting log-gap
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Media Recovery Waiting for thread 2 sequence 164952
*** 2011-05-30 09:22:57.602 64207 kcrr.c
Fetching gap sequence in thread 2, gap sequence 164952-164952
Redo shipping client performing standby login
#Primiary Site - check for missing logfile
SQL> SELECT name FROM v$archived_log where sequence# like'164952';
NAME
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=stdynode3-vip.local)(PORT
=1521)))(CONNECT_DATA=(SERVICE_NAME=TEST_XPT.local)(INSTANCE_NAME=TEST3)(SERVER
=dedicated)))
+FLASH/testp/1_164952_692118044.dbf
+FLASH/testp/2_164952_692118044.dbf
SQL>and also make sure is it priamary is two node rac?
Post the output of below query. from standby
select name,applied from v$archived_log where sequence#=164952 and thread#=2;and from primary:
select name from v$archived_log where sequence#=164952 and thread#=2;

Standby database failover flashback restart as standby gap 1-100

Hi,
I have setup a physical standby database for a 3 node RAC primary database and configured the database to run in MAXIMUM AVAILABILITY mode. Both the primary and standby databases use ASM for managing the IO. I have enabled FLASHBACK ON on both the databases.
I did failover to standby database with primary db SHUTDOWN for doing some testing. After testing is done, I flashbacked the (standby, currently primary)database to the point when it became primary and start it as standby again and the old primary as primary.
Following are the steps:
Failover steps
.Shutdown the primary database
To finisish the recovery at standby
SQL>alter database recover managed standby database finish;
To start as primary
SQL>alter database commit to switchover to primary;
do some DML on the new primary
SQL>flashback database to scn <standby_became_primary_scn>;
SQL>alter database create standby controlfile as '/backup/standby.ctl';
Changed the spfile to point control_files to '/backup/standby.ctl';
Restarted the standby db in mount mode and
created the required stanbdy logs on it.
Then issued
SQL>alter database recover managed standby database using current logfile disconnect;
I have the following message in v$dataguard_status at standby db;
Fetching gap sequence in thread 1 branch(resetlogs_id) 653234404, gap seq 1-100
DBID 2651011616 branch 653234404
GAP - thread 1 sequence 1-100
FAL[client]: Failed to request gap sequence
FAL[client]: All defined FAL servers have been attempted.
The same error is found in alert log file also.
The status of the varioud managed standby db are as follows.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CLOSING
ARCH CLOSING
ARCH CLOSING
MRP0 WAIT_FOR_GAP
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
PROCESS STATUS
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
15 rows selected.
SQL>
Could you please help me how to resolve the above error.
Thanks,
Sreekanth

Sreekanth,
I think your steps are right on for your requirement, except instead of
alter database create standby controlfile as '/backup/standby.ctl';
you can do this:
ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
(although perhaps it achieves the same thing internally but you don't need to repoint to new controlfile).
So far as the GAP - thread 1 sequence 1-100
Let me guess, your current sequences are probably well ahead of this reported gap?
If so, this is a bogus gap in a sense that your standby has long ago applied them, but for some reason standby controlfile gets a little confused and starts asking for them again.
I have had this issue and opened multiple TAR's with Oracle since 10.2.0.1, got a few patches and advises to upgrade, but still occasionally get it now in 10.2.0.3
I strongly believe this is related to combination of RAC (i.e. multiple threads of redo) and dataguard.
It is also pretty hard to reproduce (I have not figured out how to reproduce this reliably, if you have, let me know), so I can understand why Oracle has so far been unable to fix this.
Anyway, the workaround is to re-create standby controlfile with a copy generated on primary, and move it in place of the existing (and confused) controlfiles on standby.

Gap resolution is not always happening with real time apply

Hi
I noticed a strange behavior in one of my 10.2.0.4 dataguards , and I am wondering if anyone else has encountered it :
When there is an archive gap that need to be resolved , the gap is NOT always being identified and acted upon , when the recovery is started as such :
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION.
its just sitting there doing nothing, and nothing is written to the alert log regarding the gap and nothing is being transferred from the primary as needed.
However, if I restart the apply , omitting the 'USING CURRENT LOGFILE' clause , the gap is identified and acted upon, as such :
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION.
At first I thought its merely due to me stopping and starting the apply process ( nothing like a "reboot" , right ? ) , but that is not the case.
if I restart , but still use the USING CURRENT LOGFILE clause , the gap is still not being identified .
Anyone had this issue ? any theories as to why that happens ?

Using Real-Time Apply to Apply Redo Data Immediately
http://docs.oracle.com/cd/E11882_01/server.112/e25608/log_apply.htm#i1022881
1.What is compatible parameter, it should be 11.1
2.Try to check parameters mentioned in below link:
http://easyoradba.com/2011/01/10/real-time-apply-in-oracle-data-guard-10g/
Regards
Girish Sharma
Edited by: Girish Sharma on Nov 15, 2012 12:37 PM

DataGuard Lagging Issue

Hi,
DataGuard is lagging behind primary database.
For that i had shipped the missing archived log files and register them in DG side.
But still on the DG side showing there is gap archived files of DG and Primary.
Thread Last Sequence Received Last Sequence Applied Difference
1 42899 42775 124
2 42637 42637 0
3 42779 42626 153
what might be the reason and what is possible solution.
Can you please help in finding out the cause?
Thanks
Vijay
Edited by: cherukuri on Jul 2, 2011 4:32 PM
Edited by: cherukuri on Jul 2, 2011 4:33 PM

cherukuri wrote:
HI,
This is the measage on Primary Db
\Error 16191 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'ITSMPRD_dg'
Error 16191 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'ITSMPRD_dg'
ORA-16191: Primary log shipping client not logged on standby
*** 2011-06-19 05:44:52.264 64896 kcrr.c
PING[ARC4]: Heartbeat failed to connect to standby 'ITSMPRD_dg'. Error is 16191.
*** 2011-06-19 05:44:52.264 63005 kcrr.c
kcrrfail: dest:2 err:16191 force:0 blast:1
*** 2011-06-19 05:49:52.381
Redo shipping client performing standby login
ORA-01017: invalid username/password; logon denied
OCI_DBVER attribute value retrieval failed error=1017
*** 2011-06-19 05:49:52.599 64896 kcrr.c
Error 1017 received logging on to the standby
and this is on DG side
Media Recovery Waiting for thread 1 sequence 42600
Fetching gap sequence in thread 1, gap sequence 42600-42699
Fri Jul 01 14:01:57 EDT 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 42600-42699
DBID 3152143266 branch 697006498
FAL[client]: All defined FAL servers have been attempted.
and I just shipped missing archive logs and registered them after what i need to do.
Thanks
Vijay
16191, 0000, "Primary log shipping client not logged on standby"
// *Cause: An attempt to ship redo to standby without logging on
// to standby or with invalid user credentials.
// *Action: Check that primary and standby are using password files and that
//          both primary and standby have the same SYS password.
//          Restart primary and/or standby after ensuring that
//          password file is accessible and REMOTE_LOGIN_PASSWORDFILE
//          initialization parameter is set to SHARED or EXCLUSIVE. copy the external password file from the Primary to the Standby system

Oracle Dataguard issue

Hi
Could you please help me on this...
We started Oracle data guard setup for a production database where primary is located in Europe Region and standby is located in Latin America.
We configured dataguard parameters on primary and performed cold backup of DB size nearly one terabyte. At the same time we kept standby server kept ready.
But it took 15 days to reach cold backup and get restored on to standby location. In these 15 days we shipped manually all the archive logs to standby which were generated on primary.
After restoration on standby server, today i created standby contro lfile on primary and transferred to standby using scp and then copied to standby control file locations. As per the standby database setup procedure i performed all the steps...
I am able to mount the database in standby mode. After that i given the command "RECOVER STANDBY DATABASE;" to apply all the logs which were shipped manually in these 15 days....I am getting error given below:
Physical Standby Database mounted.
Completed: alter database mount standby database
Mon Jun 28 07:53:33 2010
Starting Data Guard Broker (DMON)
INSV started with pid=22, OS id=1246
Mon Jun 28 07:54:35 2010
ALTER DATABASE RECOVER standby database
Mon Jun 28 07:54:35 2010
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
Mon Jun 28 07:54:35 2010
Errors in file /oracle/P19/saptrace/background/p19_dbw0_1173.trc:
ORA-01157: cannot identify/lock data file 322 - see DBWR trace file
ORA-01110: data file 322: '/oracle/P19/sapdata1/sr3_289/sr3.data289'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Mon Jun 28 07:54:35 2010
Errors in file /oracle/P19/saptrace/background/p19_dbw0_1173.trc:
ORA-01157: cannot identify/lock data file 323 - see DBWR trace file
ORA-01110: data file 323: '/oracle/P19/sapdata1/sr3_290/sr3.data290'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Mon Jun 28 07:54:35 2010
Errors in file /oracle/P19/saptrace/background/p19_dbw0_1173.trc:
ORA-01157: cannot identify/lock data file 324 - see DBWR trace file
ORA-01110: data file 324: '/oracle/P19/sapdata2/sr3_291/sr3.data291'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Mon Jun 28 07:54:35 2010
Errors in file /oracle/P19/saptrace/background/p19_dbw0_1173.trc:
ORA-01157: cannot identify/lock data file 325 - see DBWR trace file
ORA-01110: data file 325: '/oracle/P19/sapdata3/sr3_292/sr3.data292'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
The above datafiles are added after the cold backup on primary....I am getting this error due to the latest standby controlfile used on standby....so i used the below commands on standby database:
alter database datafile '/oracle/P19/sapdata1/sr3_289/sr3.data289' offline drop;
alter database datafile '/oracle/P19/sapdata1/sr3_290/sr3.data290' offline drop;
alter database datafile '/oracle/P19/sapdata2/sr3_291/sr3.data291' offline drop;
alter database datafile '/oracle/P19/sapdata3/sr3_292/sr3.data292' offline drop;
and then recovery started by applying the logs...please find the details from alert log file given below:
Media Recovery Log /oracle/P19/oraarch/bkp_arch_dest/P19arch1_401780_624244340.dbf
Mon Jun 28 08:37:22 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jun 28 08:37:22 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jun 28 08:37:22 2010
Media Recovery Log /oracle/P19/oraarch/bkp_arch_dest/P19arch1_401781_624244340.dbf
Mon Jun 28 08:38:02 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jun 28 08:38:02 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jun 28 08:38:02 2010
Media Recovery Log /oracle/P19/oraarch/bkp_arch_dest/P19arch1_401782_624244340.dbf
Mon Jun 28 08:38:32 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jun 28 08:38:32 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Jun 28 08:38:32 2010
Media Recovery Log /oracle/P19/oraarch/bkp_arch_dest/P19arch1_401783_624244340.dbf
Mon Jun 28 08:39:05 2010
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Jun 28 08:39:05 2010
ALTER DATABASE RECOVER CONTINUE DEFAULT
After the manual shipped logs applying completion, i started the dataguard setup....logs are shipping and applying perfectly.....
Media Recovery Waiting for thread 1 sequence 407421
Fetching gap sequence in thread 1, gap sequence 407421-407506
Thu Jul 1 00:26:41 2010
RFS[2]: Archived Log: '/oracle/P19/oraarch/P19arch1_407529_624244340.dbf'
Thu Jul 1 00:26:49 2010
RFS[3]: Archived Log: '/oracle/P19/oraarch/P19arch1_407530_624244340.dbf'
Thu Jul 1 00:27:17 2010
RFS[1]: Archived Log: '/oracle/P19/oraarch/P19arch1_407531_624244340.dbf'
Thu Jul 1 00:28:41 2010
RFS[2]: Archived Log: '/oracle/P19/oraarch/P19arch1_407532_624244340.dbf'
Thu Jul 1 00:29:14 2010
RFS[3]: Archived Log: '/oracle/P19/oraarch/P19arch1_407421_624244340.dbf'
Thu Jul 1 00:29:19 2010
Media Recovery Log /oracle/P19/oraarch/P19arch1_407421_624244340.dbf
Thu Jul 1 00:29:24 2010
RFS[1]: Archived Log: '/oracle/P19/oraarch/P19arch1_407422_624244340.dbf'
Thu Jul 1 00:29:51 2010
Media Recovery Log /oracle/P19/oraarch/P19arch1_407422_624244340.dbf
But the above files showing as recover as status...could you please tell how to go ahead on this....
NAME
STATUS
/oracle/P19/sapdata1/sr3_289/sr3.data289
RECOVER
/oracle/P19/sapdata1/sr3_290/sr3.data290
RECOVER
/oracle/P19/sapdata2/sr3_291/sr3.data291
RECOVER
NAME
STATUS
/oracle/P19/sapdata3/sr3_292/sr3.data292
RECOVER
can i recover these files in standby mount mode? Any other solution is there? All archivelogs applied, log shipping and applying is going on...
Thank You....

try this out
1.On the Primary server issue this command
SQL> Alter database backup control file to trace;
2.Go to your Udump directory and look for the trace file that has been generated by this comman.
3.This file will contain the CREATE CONTROLFILE statement. It will have two sets of statement one with RESETLOGS and another withOUT RESETLOGS. use RESETLOGS option of CREATE CONTROLFILE statement. Now copy and paste the statement in a file. Let it be c.sql
4.Now open a file named as c.sql file in text editor and set the database name from [example:ica] to [example:prod] shown in an example below
CREATE CONTROLFILE
   SET DATABASE prod
   LOGFILE GROUP 1 ('/u01/oracle/ica/redo01_01.log',
                    '/u01/oracle/ica/redo01_02.log'),
           GROUP 2 ('/u01/oracle/ica/redo02_01.log',
                    '/u01/oracle/ica/redo02_02.log'),
           GROUP 3 ('/u01/oracle/ica/redo03_01.log',
                    '/u01/oracle/ica/redo03_02.log')
   RESETLOGS
   DATAFILE '/u01/oracle/ica/system01.dbf' SIZE 3M,
            '/u01/oracle/ica/rbs01.dbs' SIZE 5M,
            '/u01/oracle/ica/users01.dbs' SIZE 5M,
            '/u01/oracle/ica/temp01.dbs' SIZE 5M
   MAXLOGFILES 50
   MAXLOGMEMBERS 3
   MAXLOGHISTORY 400
   MAXDATAFILES 200
   MAXINSTANCES 6
   ARCHIVELOG5. Start the database in NOMOUNT STATE
SQL>Stratup Nomount;
6.Now execute the script to create a new control file
SQL> @/u01/oracle/c.sql
7. Now open the database
SQL>Alter database open resetlogs;
IMPORTANT NOTE: Before implementing this suggested solution try it out on ur laptop or PC if possible
Edited by: Suhail Faraaz on Jun 30, 2010 3:00 PM
Edited by: Suhail Faraaz on Jun 30, 2010 3:03 PM

Archive Log Gap between Disaster recovery server & Production Server

Hi
Can anybody provide me the script to find out the archive log missing on Production Server means that archive log backed up & deleted from the production server & rest of the Archive logs has been shipped on to the DR server. Means it will shot the gap between production server & DR server until that log which has been deleted from the production server , but next logs has been shipped to the DR server. But rest of the logs only be applied when delete log be restored on the production server & shipped on the DR server.
thanks.
Regards
Ravi Kant Arya

Ravi,
The question is how are you getting the archive logs shipped over to your standby database? If you are doing it via FTP or scripts, then you may want to look at configuring DataGuard to do it for you. Look at "Setting Up Oracle Dataguard for SAP" at:
http://www.oracle.com/us/solutions/sap/wp-ora4sap-dataguard11g-303811.pdf
Good Luck.
Mike Kennedy

Waiting for Gap Email Notification

Hi all,
11.2.0.1
Aix 6.1
Is there an email system in 11g that will notify me if our standby DB is "waiting for gap"?
What other status value are needed to be watched for?
Thanks,
zxy

Hi Mse,
We have 2 database on 1 server named PROD1, PROD2.
At PROD1, I got this:
DT        MBPS_REQ_A_DAY MIN_MBPS_REQ_AN_HOUR MAX_MBPS_REQ_AN_HOUR AVG_MBPS_REQ_AN_HOUR
15-SEP-13     28.4012215           .640219932           2.57893228           2.02865868
16-SEP-13      68.943453           .147678891           20.4264564           3.44717265
17-SEP-13     69.4071543           .639978837           28.1937717           3.47035771
18-SEP-13     54.1598321           .614150599            17.484673            2.7079916
19-SEP-13     55.7515449           .370225948           15.4680441           2.78757725
20-SEP-13     25.9854426           .135556096           17.5167623           3.71220608
6 rows selected.
At PROD2, I got this:
DT        MBPS_REQ_A_DAY MIN_MBPS_REQ_AN_HOUR MAX_MBPS_REQ_AN_HOUR AVG_MBPS_REQ_AN_HOUR
15-SEP-13     28.4012215           .640219932           2.57893228           2.02865868
16-SEP-13      68.943453           .147678891           20.4264564           3.44717265
17-SEP-13     69.4071543           .639978837           28.1937717           3.47035771
18-SEP-13     54.1598321           .614150599            17.484673            2.7079916
19-SEP-13     55.7515449           .370225948           15.4680441           2.78757725
20-SEP-13     25.9854426           .135556096           17.5167623           3.71220608
6 rows selected.
So what Mbps plan do we get from network service provider to accommodate our dataguard standby sync process?
Also can you teach me how to format the display above?
Thanks a lot,
zxy

Dataguard Gap

Similar Messages

Maybe you are looking for