14 Replies Latest reply on Apr 21, 2011 7:32 AM by ADaniel

    Problems with dataguard on primary and standby db

    user10182692
      Hello, i have a lots of problems to sinchronize the dataguard, here I attach the alert.log and the pfiles, any help would be appreciated.

      Primary Pfile:

      orcl.__db_cache_size=92274688
      orcl.__java_pool_size=4194304
      orcl.__large_pool_size=4194304
      orcl.__shared_pool_size=62914560
      orcl.__streams_pool_size=0
      *.audit_file_dest='c:\oracle\product\10.2.0/admin/orcl/adump'
      *.background_dump_dest='c:\oracle\product\10.2.0/admin/orcl/bdump'
      *.compatible='10.2.0.1.0'
      *.control_files='e:\oradata\orcl\control01.ctl','e:\oradata\orcl\control02.ctl','e:\oradata\orcl\control03.ctl'
      *.core_dump_dest='c:\oracle\product\10.2.0/admin/orcl/cdump'
      *.db_block_size=8192
      *.db_domain=''
      *.db_file_multiblock_read_count=16
      *.db_name='orcl'
      *.db_unique_name='orcl'
      *.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
      *.db_recovery_file_dest_size=2147483648
      *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
      *.job_queue_processes=10
      *.log_archive_dest_1='LOCATION=e:\oradata\archivelogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCL'
      *.log_archive_dest_2='SERVICE=orcl1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl1'
      *.log_archive_dest_state_1=ENABLE
      *.log_archive_dest_state_2=ENABLE
      *.log_archive_max_processes=30
      *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,orcl1)'
      *.log_archive_format='ARC%S_%R.%T'
      *.open_cursors=300
      *.pga_aggregate_target=16777216
      *.processes=150
      *.remote_login_passwordfile='EXCLUSIVE'
      *.sga_target=167772160
      *.undo_management='AUTO'
      *.undo_tablespace='UNDOTBS1'
      *.user_dump_dest='c:\oracle\product\10.2.0/admin/orcl/udump'

      # standby role parameters ----------------------------------
      *.fal_server=orcl1
      *.fal_client=orcl
      *.standby_file_management=auto
      *.db_file_name_convert='ORCL1/ORCL1','ORCL/ORCL'
      *.log_file_name_convert='e:\oradata\archivelogs\orcl1\','e:\oradata\archivelogs\orcl\'

      Standby Pfile:

      orcl1.__db_cache_size=92274688
      orcl1.__java_pool_size=4194304
      orcl1.__large_pool_size=4194304
      orcl1.__shared_pool_size=62914560
      orcl1.__streams_pool_size=0
      *.audit_file_dest='c:\oracle\product\10.2.0/admin/orcl1/adump'
      *.background_dump_dest='c:\oracle\product\10.2.0/admin/orcl1/bdump'
      *.compatible='10.2.0.1.0'
      *.db_create_file_dest='e:\oradata\orcl1'
      *.control_files='e:\oradata\orcl1\control01.ctl','e:\oradata\orcl1\control02.ctl','e:\oradata\orcl1\control03.ctl'
      *.core_dump_dest='c:\oracle\product\10.2.0/admin/orcl1/cdump'
      *.db_block_size=8192
      *.db_domain=''
      *.db_file_multiblock_read_count=16
      *.db_name='orcl'
      *.instance_name='orcl1'
      *.db_unique_name='orcl1'
      *.db_recovery_file_dest='c:\oracle\product\10.2.0/flash_recovery_area'
      *.db_recovery_file_dest_size=2147483648
      *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
      *.job_queue_processes=10
      *.log_archive_dest_1='LOCATION=e:\oradata\archivelogs\ORCL1\ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCL1'
      *.log_archive_dest_2='SERVICE=orcl LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl'
      *.log_archive_dest_state_1=ENABLE
      *.log_archive_dest_state_2=ENABLE
      *.log_archive_max_processes=30
      *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,orcl1)'
      *.log_archive_format='ARC%S_%R.%T'
      *.open_cursors=300
      *.pga_aggregate_target=16777216
      *.processes=150
      *.remote_login_passwordfile='EXCLUSIVE'
      *.sga_target=167772160
      *.undo_management='AUTO'
      *.undo_tablespace='UNDOTBS1'
      *.user_dump_dest='c:\oracle\product\10.2.0/admin/orcl1/udump'

      # standby role parameters ----------------------------------
      *.fal_server='orcl'
      *.fal_client='orcl1'
      *.standby_file_management='auto'
      *.db_file_name_convert='E:\ORADATA\ORCL1','E:\ORADATA\ORCL'
      *.log_file_name_convert='e:\oradata\archivelogs\orcl1\','e:\oradata\archivelogs\orcl\'

      Alert log prumary:

      LICENSE_MAX_USERS = 0
      SYS auditing is disabled
      ksdpec: called for event 13740 prior to event group initialization
      Starting up ORACLE RDBMS Version: 10.2.0.1.0.
      System parameters with non-default values:
      processes = 150
      __shared_pool_size = 75497472
      __large_pool_size = 4194304
      __java_pool_size = 4194304
      __streams_pool_size = 0
      sga_target = 167772160
      control_files = E:\ORADATA\ORCL\CONTROL01.CTL, E:\ORADATA\ORCL\CONTROL02.CTL, E:\ORADATA\ORCL\CONTROL03.CTL
      db_file_name_convert = ORCL1/ORCL1, ORCL/ORCL
      log_file_name_convert = e:\oradata\archivelogs\orcl1\, e:\oradata\archivelogs\orcl\
      db_block_size = 8192
      __db_cache_size = 79691776
      compatible = 10.2.0.1.0
      log_archive_config = DG_CONFIG=(orcl,orcl1)
      log_archive_dest_1 = LOCATION=e:\oradata\archivelogs VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCL
      log_archive_dest_2 = SERVICE=orcl1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl1
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      log_archive_max_processes= 30
      log_archive_format = ARC%S_%R.%T
      fal_client = orcl
      fal_server = orcl1
      db_file_multiblock_read_count= 16
      db_recovery_file_dest = c:\oracle\product\10.2.0/flash_recovery_area
      db_recovery_file_dest_size= 2147483648
      standby_file_management = auto
      undo_management = AUTO
      undo_tablespace = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain =
      dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
      job_queue_processes = 10
      audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
      background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
      user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
      core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
      db_name = orcl
      db_unique_name = orcl
      open_cursors = 300
      pga_aggregate_target = 16777216
      PMON started with pid=2, OS id=3104
      PSP0 started with pid=3, OS id=3120
      MMAN started with pid=4, OS id=3064
      DBW0 started with pid=5, OS id=3156
      LGWR started with pid=6, OS id=3132
      CKPT started with pid=7, OS id=3136
      SMON started with pid=8, OS id=3128
      RECO started with pid=9, OS id=3124
      CJQ0 started with pid=10, OS id=3148
      MMON started with pid=11, OS id=3152
      MMNL started with pid=12, OS id=3184
      Thu Aug 13 10:02:53 2009
      starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
      starting up 1 shared server(s) ...
      Thu Aug 13 10:02:54 2009
      ALTER DATABASE MOUNT
      Thu Aug 13 10:02:58 2009
      Setting recovery target incarnation to 2
      Thu Aug 13 10:02:58 2009
      Successful mount of redo thread 1, with mount id 1222555470
      Thu Aug 13 10:02:58 2009
      Database mounted in Exclusive Mode
      Completed: ALTER DATABASE MOUNT
      Thu Aug 13 10:02:59 2009
      ALTER DATABASE OPEN
      Thu Aug 13 10:02:59 2009
      Beginning crash recovery of 1 threads
      Thu Aug 13 10:02:59 2009
      Started redo scan
      Thu Aug 13 10:02:59 2009
      Completed redo scan
      97 redo blocks read, 22 data blocks need recovery
      Thu Aug 13 10:02:59 2009
      Started redo application at
      Thread 1: logseq 6, block 1032
      Thu Aug 13 10:02:59 2009
      Recovery of Online Redo Log: Thread 1 Group 2 Seq 6 Reading mem 0
      Mem# 0 errs 0: E:\ORADATA\ORCL\REDO02.LOG
      Thu Aug 13 10:02:59 2009
      Completed redo application
      Thu Aug 13 10:02:59 2009
      Completed crash recovery at
      Thread 1: logseq 6, block 1129, scn 673938
      22 data blocks read, 21 data blocks written, 97 redo blocks read
      Thu Aug 13 10:02:59 2009
      LGWR: STARTING ARCH PROCESSES
      ARC0 started with pid=16, OS id=3168
      ARC1 started with pid=17, OS id=2764
      ARC2 started with pid=18, OS id=3196
      ARC3 started with pid=19, OS id=1884
      ARC4 started with pid=20, OS id=1652
      ARC5 started with pid=21, OS id=2264
      ARC6 started with pid=22, OS id=3236
      ARC7 started with pid=23, OS id=2460
      ARC8 started with pid=24, OS id=1824
      ARC9 started with pid=25, OS id=3092
      ARCa started with pid=26, OS id=988
      ARCb started with pid=27, OS id=3088
      ARCc started with pid=28, OS id=2956
      ARCd started with pid=29, OS id=2960
      ARCe started with pid=30, OS id=2656
      ARCf started with pid=31, OS id=2328
      ARCg started with pid=32, OS id=2880
      ARCh started with pid=33, OS id=3244
      ARCi started with pid=34, OS id=3240
      ARCj started with pid=35, OS id=1404
      ARCk started with pid=36, OS id=3300
      ARCl started with pid=37, OS id=3312
      ARCm started with pid=38, OS id=3296
      ARCn started with pid=39, OS id=3204
      ARCo started with pid=40, OS id=3268
      ARCp started with pid=41, OS id=3272
      ARCq started with pid=42, OS id=3308
      ARCr started with pid=43, OS id=3304
      ARCs started with pid=44, OS id=3212
      Thu Aug 13 10:03:00 2009
      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
      ARCa: Archival started
      ARCb: Archival started
      ARCc: Archival started
      ARCd: Archival started
      ARCe: Archival started
      ARCf: Archival started
      ARCg: Archival started
      ARCh: Archival started
      ARCi: Archival started
      ARCj: Archival started
      ARCk: Archival started
      ARCl: Archival started
      ARCm: Archival started
      ARCn: Archival started
      ARCo: Archival started
      ARCp: Archival started
      ARCq: Archival started
      ARCr: Archival started
      ARCs: Archival started
      ARCt: Archival started
      LGWR: STARTING ARCH PROCESSES COMPLETE
      ARCt started with pid=45, OS id=3208
      LNS1 started with pid=46, OS id=3340
      Thu Aug 13 10:03:03 2009
      Thread 1 advanced to log sequence 7
      Thread 1 opened at log sequence 7
      Current log# 3 seq# 7 mem# 0: E:\ORADATA\ORCL\REDO03.LOG
      Successful open of redo thread 1
      Thu Aug 13 10:03:03 2009
      ARCn: Becoming the 'no FAL' ARCH
      ARCn: Becoming the 'no SRL' ARCH
      Thu Aug 13 10:03:03 2009
      MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
      Thu Aug 13 10:03:03 2009
      ARCm: Becoming the heartbeat ARCH
      Thu Aug 13 10:03:03 2009
      SMON: enabling cache recovery
      Thu Aug 13 10:03:04 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc2_3196.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Thu Aug 13 10:03:04 2009
      FAL[server, ARC2]: Error 16012 creating remote archivelog file 'orcl1'
      FAL[server, ARC2]: FAL archive failed, see trace file.
      Thu Aug 13 10:03:04 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arc2_3196.trc:
      ORA-16055: FAL request rejected

      ARCH: FAL archive failed. Archiver continuing
      Thu Aug 13 10:03:04 2009
      Successfully onlined Undo Tablespace 1.
      Thu Aug 13 10:03:04 2009
      SMON: enabling tx recovery
      Thu Aug 13 10:03:04 2009
      Database Characterset is WE8MSWIN1252
      replication_dependency_tracking turned off (no async multimaster replication found)
      Starting background process QMNC
      QMNC started with pid=47, OS id=3372
      Thu Aug 13 10:03:06 2009
      Completed: ALTER DATABASE OPEN
      Thu Aug 13 10:03:06 2009
      db_recovery_file_dest_size of 2048 MB is 7.32% 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.
      Thu Aug 13 10:09:00 2009
      Error 12514 received logging on to the standby
      Thu Aug 13 10:09:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
      ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

      PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 12514.
      Thu Aug 13 10:14:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Thu Aug 13 10:14:00 2009
      PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
      Thu Aug 13 10:19:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Thu Aug 13 10:19:00 2009
      PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
      Thu Aug 13 10:24:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Thu Aug 13 10:24:00 2009
      PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.

      Log standby:

      LICENSE_MAX_USERS = 0
      SYS auditing is disabled
      ksdpec: called for event 13740 prior to event group initialization
      Starting up ORACLE RDBMS Version: 10.2.0.1.0.
      System parameters with non-default values:
      processes = 150
      __shared_pool_size = 62914560
      __large_pool_size = 4194304
      __java_pool_size = 4194304
      __streams_pool_size = 0
      sga_target = 167772160
      control_files = E:\ORADATA\ORCL1\CONTROL01.CTL, E:\ORADATA\ORCL1\CONTROL02.CTL, E:\ORADATA\ORCL1\CONTROL03.CTL
      db_file_name_convert = E:\ORADATA\ORCL1, E:\ORADATA\ORCL
      log_file_name_convert = e:\oradata\archivelogs\orcl1\, e:\oradata\archivelogs\orcl\
      db_block_size = 8192
      __db_cache_size = 92274688
      compatible = 10.2.0.1.0
      log_archive_config = DG_CONFIG=(orcl,orcl1)
      log_archive_dest_1 = LOCATION=e:\oradata\archivelogs\ORCL1\ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ORCL1
      log_archive_dest_2 = SERVICE=orcl LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      log_archive_max_processes= 30
      log_archive_format = ARC%S_%R.%T
      fal_client = orcl1
      fal_server = orcl
      db_file_multiblock_read_count= 16
      db_create_file_dest = e:\oradata\orcl1
      db_recovery_file_dest = c:\oracle\product\10.2.0/flash_recovery_area
      db_recovery_file_dest_size= 2147483648
      standby_file_management = auto
      undo_management = AUTO
      undo_tablespace = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain =
      instance_name = orcl1
      dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
      job_queue_processes = 10
      audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL1\ADUMP
      background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL1\BDUMP
      user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL1\UDUMP
      core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL1\CDUMP
      db_name = orcl
      db_unique_name = orcl1
      open_cursors = 300
      pga_aggregate_target = 16777216
      PMON started with pid=2, OS id=2948
      PSP0 started with pid=3, OS id=2960
      MMAN started with pid=4, OS id=2980
      DBW0 started with pid=5, OS id=2984
      LGWR started with pid=6, OS id=2988
      CKPT started with pid=7, OS id=3000
      SMON started with pid=8, OS id=3004
      RECO started with pid=9, OS id=2996
      CJQ0 started with pid=10, OS id=2720
      MMON started with pid=11, OS id=2976
      MMNL started with pid=12, OS id=2972
      Thu Aug 13 10:09:34 2009
      starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
      starting up 1 shared server(s) ...
      Thu Aug 13 10:09:35 2009
      ALTER DATABASE MOUNT
      Thu Aug 13 10:09:39 2009
      Setting recovery target incarnation to 2
      ARCH: STARTING ARCH PROCESSES
      ARC0 started with pid=16, OS id=3028
      ARC1 started with pid=17, OS id=3012
      ARC2 started with pid=18, OS id=3016
      ARC3 started with pid=19, OS id=3032
      ARC4 started with pid=20, OS id=1280
      ARC5 started with pid=21, OS id=1496
      ARC6 started with pid=22, OS id=3128
      ARC7 started with pid=23, OS id=3144
      ARC8 started with pid=24, OS id=3008
      ARC9 started with pid=25, OS id=3108
      ARCa started with pid=26, OS id=848
      ARCb started with pid=27, OS id=2328
      ARCc started with pid=28, OS id=3140
      ARCd started with pid=29, OS id=3100
      ARCe started with pid=30, OS id=3124
      ARCf started with pid=31, OS id=3136
      ARCg started with pid=32, OS id=3104
      ARCh started with pid=33, OS id=3112
      ARCi started with pid=34, OS id=3116
      ARCj started with pid=35, OS id=3120
      ARCk started with pid=36, OS id=3152
      ARCl started with pid=37, OS id=3096
      ARCm started with pid=38, OS id=3148
      ARCn started with pid=39, OS id=3184
      ARCo started with pid=40, OS id=3176
      ARCp started with pid=41, OS id=3180
      ARCq started with pid=42, OS id=3196
      ARCr started with pid=43, OS id=3188
      ARCs started with pid=44, OS id=3056
      Thu Aug 13 10:09:39 2009
      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
      ARCa: Archival started
      ARCb: Archival started
      ARCc: Archival started
      ARCd: Archival started
      ARCe: Archival started
      ARCf: Archival started
      ARCg: Archival started
      ARCh: Archival started
      ARCi: Archival started
      ARCj: Archival started
      ARCk: Archival started
      ARCl: Archival started
      ARCm: Archival started
      ARCn: Archival started
      ARCo: Archival started
      ARCp: Archival started
      ARCq: Archival started
      ARCr: Archival started
      ARCs: Archival started
      ARCt: Archival started
      ARCH: STARTING ARCH PROCESSES COMPLETE
      Thu Aug 13 10:09:39 2009
      ARC0: Becoming the 'no FAL' ARCH
      ARC0: Becoming the 'no SRL' ARCH
      ARC0: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC1: Becoming the heartbeat ARCH
      ARC1: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC2: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC3: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC4: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC5: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC6: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC7: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC8: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARC9: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCa: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCb: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCc: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCd: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCe: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCf: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCg: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCh: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCi: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCj: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCk: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCl: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCm: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCn: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCo: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCp: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCq: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCr: Thread not mounted
      Thu Aug 13 10:09:39 2009
      ARCs: Thread not mounted
      Thu Aug 13 10:09:39 2009
      Successful mount of redo thread 1, with mount id 1222541535
      Thu Aug 13 10:09:39 2009
      Physical Standby Database mounted.
      Completed: ALTER DATABASE MOUNT
      ARCt started with pid=45, OS id=3084
      Thu Aug 13 10:09:41 2009
      alter database recover managed standby database disconnect from session
      MRP0 started with pid=46, OS id=3172
      Managed Standby Recovery not using Real Time Apply
      MRP0: Background Media Recovery terminated with error 1110
      Thu Aug 13 10:09:46 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl1\bdump\orcl1_mrp0_3172.trc:
      ORA-01110: data file 1: 'E:\ORADATA\ORCL\SYSTEM01.DBF'
      ORA-01122: database file 1 failed verification check
      ORA-01110: data file 1: 'E:\ORADATA\ORCL\SYSTEM01.DBF'
      ORA-01206: file is not part of this database - wrong database id

      Thu Aug 13 10:09:46 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl1\bdump\orcl1_mrp0_3172.trc:
      ORA-01110: data file 1: 'E:\ORADATA\ORCL\SYSTEM01.DBF'
      ORA-01122: database file 1 failed verification check
      ORA-01110: data file 1: 'E:\ORADATA\ORCL\SYSTEM01.DBF'
      ORA-01206: file is not part of this database - wrong database id

      Thu Aug 13 10:09:47 2009
      Completed: alter database recover managed standby database disconnect from session
      Using STANDBY_ARCHIVE_DEST parameter default value as e:\oradata\archivelogs\ORCL1\
      Redo Shipping Client Connected as PUBLIC
      -- Connected User is Valid
      RFS[1]: Assigned to RFS process 3048
      RFS[1]: Identified database type as 'physical standby'
      Standby database ID mismatch [0x1222483553:0x1222042911]
      Thu Aug 13 10:14:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl1\udump\orcl1_rfs_3048.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Redo Shipping Client Connected as PUBLIC
      -- Connected User is Valid
      RFS[2]: Assigned to RFS process 3272
      RFS[2]: Identified database type as 'physical standby'
      Standby database ID mismatch [0x1222483553:0x1222042911]
      Thu Aug 13 10:19:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl1\udump\orcl1_rfs_3272.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Redo Shipping Client Connected as PUBLIC
      -- Connected User is Valid
      RFS[3]: Assigned to RFS process 3244
      RFS[3]: Identified database type as 'physical standby'
      Standby database ID mismatch [0x1222483553:0x1222042911]
      Thu Aug 13 10:24:00 2009
      Errors in file c:\oracle\product\10.2.0\admin\orcl1\udump\orcl1_rfs_3244.trc:
      ORA-16012: Archive log standby database identifier mismatch

      Thu Aug 13 10:24:38 2009
      db_recovery_file_dest_size of 2048 MB is 0.00% 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.


      Thanks for any help.
        • 1. Re: Problems with dataguard on primary and standby db
          Pavan DBA
          try to post few lines from
          c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
          and
          c:\oracle\product\10.2.0\admin\orcl1\udump\orcl1_rfs_3244.trc:

          few questions for you
          1) have you checked DBID of both primary and standby?
          2) is standby database is in mount stage?
          3) did you tried to (or) changed DBID of primary recently?
          • 2. Re: Problems with dataguard on primary and standby db
            340744
            Hi there,

            somethink happened to your standby database, it is physical standby, but it does not have db files with a corresponding dbid.
            What happened on that server?
            To fix this - you need to resetup the standby database.
            E.g. in rman
            duplicate target database for standby dorecover nofilenamecheck;

            HTH Mathias
            • 3. Re: Problems with dataguard on primary and standby db
              user10182692
              Dump file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc
              Thu Aug 13 10:03:03 2009
              ORACLE V10.2.0.1.0 - Production vsnsta=0
              vsnsql=14 vsnxtr=3
              Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
              With the Partitioning, OLAP and Data Mining options
              Windows Server 2003 Version V5.2 Service Pack 2
              CPU : 1 - type 586, 1 Physical Cores
              Process Affinity : 0x00000000
              Memory (Avail/Total): Ph:89M/511M, Ph+PgF:447M/1257M, VA:1525M/2047M
              Instance name: orcl

              Redo thread mounted by this instance: 1

              Oracle process number: 38

              Windows thread id: 3296, image: ORACLE.EXE (ARCm)


              *** SERVICE NAME:() 2009-08-13 10:03:03.343
              *** SESSION ID:(134.1) 2009-08-13 10:03:03.343
              kcrrwkx: work to do 0x1 (start)
              kcrrwkx: work to do 0x2 (end)
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:04:00.004
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:05:00.150
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:06:00.197
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:07:00.223
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:08:00.229
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:09:00.256
              Redo shipping client performing standby login
              OCIServerAttach failed -1
              .. Detailed OCI error val is 12514 and errmsg is 'ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
              '
              *** 2009-08-13 10:09:00.276 60680 kcrr.c
              Error 12514 received logging on to the standby
              Error 12514 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              Error 12514 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
              *** 2009-08-13 10:09:00.276 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 12514.
              *** 2009-08-13 10:09:00.276 58942 kcrr.c
              kcrrfail: dest:2 err:12514 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:10:00.312
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:11:00.328
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:12:00.345
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:13:00.361
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:14:00.367
              Redo shipping client performing standby login
              *** 2009-08-13 10:14:00.427 64562 kcrr.c
              Logged on to standby successfully
              Client logon and security negotiation successful!
              Error 16012 attaching RFS server to standby instance at host 'orcl1'
              Error 16012 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-16012: Archive log standby database identifier mismatch
              *** 2009-08-13 10:14:00.437 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
              *** 2009-08-13 10:14:00.437 58942 kcrr.c
              kcrrfail: dest:2 err:16012 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:15:00.474
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:16:00.500
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:17:00.506
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:18:00.533
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:19:00.559
              Redo shipping client performing standby login
              *** 2009-08-13 10:19:00.619 64562 kcrr.c
              Logged on to standby successfully
              Client logon and security negotiation successful!
              Error 16012 attaching RFS server to standby instance at host 'orcl1'
              Error 16012 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-16012: Archive log standby database identifier mismatch
              *** 2009-08-13 10:19:00.629 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
              *** 2009-08-13 10:19:00.629 58942 kcrr.c
              kcrrfail: dest:2 err:16012 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:20:00.655
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:21:00.702
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:22:00.738
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:23:00.764
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:24:00.801
              Redo shipping client performing standby login
              *** 2009-08-13 10:24:00.861 64562 kcrr.c
              Logged on to standby successfully
              Client logon and security negotiation successful!
              Error 16012 attaching RFS server to standby instance at host 'orcl1'
              Error 16012 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-16012: Archive log standby database identifier mismatch
              *** 2009-08-13 10:24:00.871 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
              *** 2009-08-13 10:24:00.871 58942 kcrr.c
              kcrrfail: dest:2 err:16012 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:25:00.907
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:26:00.933
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:27:00.970
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:28:00.986
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:29:01.002
              Redo shipping client performing standby login
              *** 2009-08-13 10:29:01.062 64562 kcrr.c
              Logged on to standby successfully
              Client logon and security negotiation successful!
              Error 16012 attaching RFS server to standby instance at host 'orcl1'
              Error 16012 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-16012: Archive log standby database identifier mismatch
              *** 2009-08-13 10:29:01.072 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
              *** 2009-08-13 10:29:01.072 58942 kcrr.c
              kcrrfail: dest:2 err:16012 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:30:01.099
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:31:01.125
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:32:01.141
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:33:01.158
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:34:01.184
              Redo shipping client performing standby login
              *** 2009-08-13 10:34:01.234 64562 kcrr.c
              Logged on to standby successfully
              Client logon and security negotiation successful!
              Error 16012 attaching RFS server to standby instance at host 'orcl1'
              Error 16012 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'orcl1'
              ORA-16012: Archive log standby database identifier mismatch
              *** 2009-08-13 10:34:01.254 60680 kcrr.c
              PING[ARCm]: Heartbeat failed to connect to standby 'orcl1'. Error is 16012.
              *** 2009-08-13 10:34:01.254 58942 kcrr.c
              kcrrfail: dest:2 err:16012 force:0 blast:1
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:35:01.290
              kcrrwkx: nothing to do (end)
              *** 2009-08-13 10:36:00.426
              kcrrwkx: nothing to do (end)

              Dump file c:\oracle\product\10.2.0\admin\orcl1\udump\orcl1_rfs_3244.trc
              Thu Aug 13 10:24:00 2009
              ORACLE V10.2.0.1.0 - Production vsnsta=0
              vsnsql=14 vsnxtr=3
              Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
              With the Partitioning, OLAP and Data Mining options
              Windows Server 2003 Version V5.2 Service Pack 2
              CPU : 1 - type 586, 1 Physical Cores
              Process Affinity : 0x00000000
              Memory (Avail/Total): Ph:146M/511M, Ph+PgF:537M/1257M, VA:1545M/2047M
              Instance name: orcl1

              Redo thread mounted by this instance: 1

              Oracle process number: 15

              Windows thread id: 3244, image: ORACLE.EXE (SHAD)


              *** SERVICE NAME:() 2009-08-13 10:24:00.842
              *** SESSION ID:(127.599) 2009-08-13 10:24:00.842
              Detected dead process 3272; subsuming V$MANAGED_STANDBY slot
              *** 2009-08-13 10:24:00.842 60680 kcrr.c
              Standby database ID mismatch [0x1222483553:0x1222042911]
              ORA-16012: Archive log standby database identifier mismatch
              • 4. Re: Problems with dataguard on primary and standby db
                Pavan DBA
                ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
                some problem with the connectivity. try tnsping from both ends and make sure it is successful.

                check this metalink doc 106707.1 (which may be helpful)
                • 5. Re: Problems with dataguard on primary and standby db
                  340744
                  12514 is not the problem, this was due to dynamic service registration, which i do not recommend to use
                  in data guard environments for the log_archive_dest_n services.

                  Thu Aug 13 10:09:00 2009
                  Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
                  ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

                  PINGARCm: Heartbeat failed to connect to standby 'orcl1'. Error is 12514.
                  Thu Aug 13 10:14:00 2009
                  Errors in file c:\oracle\product\10.2.0\admin\orcl\bdump\orcl_arcm_3296.trc:
                  ORA-16012: Archive log standby database identifier mismatch

                  12514 was solved after 5 minutes (default REOPEN time), and then the archiver got the ORA-16012
                  which is the real problem.

                  Mathias
                  • 6. Re: Problems with dataguard on primary and standby db
                    Pavan DBA
                    oops, i overlooked it.
                    • 7. Re: Problems with dataguard on primary and standby db
                      user10182692
                      I search the error but the fix dont work.
                      • 8. Re: Problems with dataguard on primary and standby db
                        340744
                        Please explain:
                        how does this changed dbid comes into play?
                        What have you done when trying to fix it?
                        Error Messages?

                        Mathias
                        • 9. Re: Problems with dataguard on primary and standby db
                          user10182692
                          I think, maybe going to start over all again, i use a tuto from Alejandro Vargas to create step by step dataguard..
                          • 10. Re: Problems with dataguard on primary and standby db
                            340744
                            sorry this guide ..
                            for instance does not tell you that it is possible create a standby from backup without stopping the primary.
                            if you want to go on with this .. resetup your standby.
                            Begin from Page "Standby Database Steps".

                            Mathias
                            • 11. Re: Problems with dataguard on primary and standby db
                              user10182692
                              I have been reinstalled all again, and now the alert_log from the primary db show this:

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                              Mon Aug 17 02:20:11 2009
                              Error 12154 received logging on to the standby
                              Mon Aug 17 02:20:11 2009
                              Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                              ORA-12154: TNS:could not resolve the connect identifier specified

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                              Mon Aug 17 02:25:11 2009
                              Error 12154 received logging on to the standby
                              Mon Aug 17 02:25:11 2009
                              Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                              ORA-12154: TNS:could not resolve the connect identifier specified

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                              Mon Aug 17 02:30:11 2009
                              Error 12154 received logging on to the standby
                              Mon Aug 17 02:30:11 2009
                              Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                              ORA-12154: TNS:could not resolve the connect identifier specified

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                              Mon Aug 17 02:35:11 2009
                              Error 12154 received logging on to the standby
                              Mon Aug 17 02:35:11 2009
                              Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                              ORA-12154: TNS:could not resolve the connect identifier specified

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                              Mon Aug 17 02:40:11 2009
                              Error 12154 received logging on to the standby
                              Mon Aug 17 02:40:11 2009
                              Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                              ORA-12154: TNS:could not resolve the connect identifier specified

                              PING[ARCo]: Heartbeat failed to connect to standby 'orcld'. Error is 12154.

                              If I make a tnsping the response of the primary and standby is ok, but when start up the standby db this error came up:

                              ORA-16004: backup database requires recovery
                              ORA-01194: file 1 needs more recovery to be consistent
                              ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLC\SYSTEM01.DBF'

                              I make a recovery with: alter database recover managed by standby database disconnect from session;

                              It shows: Database Altered, then launch alter database open and the error that show is:

                              SQL> alter database open;
                              alter database open
                              *
                              ERROR at line 1:
                              ORA-01154: database busy. Open, close, mount, and dismount not allowed now

                              Can some with big experience can help me?, thanksssssssssssssssssss.
                              • 12. Re: Problems with dataguard on primary and standby db
                                704810
                                If I make a tnsping the response of the primary and standby is ok, but when start up the standby db this error came up:

                                ORA-16004: backup database requires recovery
                                ORA-01194: file 1 needs more recovery to be consistent
                                ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCLC\SYSTEM01.DBF'

                                I make a recovery with: alter database recover managed by standby database disconnect from session;


                                It looks like you didnt restore it properly for this

                                1)Take a new rman Backup and create new standby control file and create pfile and copy all the files to standby db location
                                2)Restore that backup in the standby db and recover it by using RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL
                                3)Then keep standby db in MRM mode.


                                Ravi
                                • 13. Re: Problems with dataguard on primary and standby db
                                  sreekanth-2034528
                                  Hey,

                                  Did you got the following error resolved ? I am facing the same problem now. Please let me know if there is any work around for this error.



                                  PINGARCo: Heartbeat failed to connect to standby 'orcld'. Error is 12154.
                                  Mon Aug 17 02:25:11 2009
                                  Error 12154 received logging on to the standby
                                  Mon Aug 17 02:25:11 2009
                                  Errors in file c:\oracle\product\10.2.0\admin\orclc\bdump\orclc_arco_3952.trc:
                                  ORA-12154: TNS:could not resolve the connect identifier specified


                                  Thanks,
                                  Sreekanth
                                  • 14. Re: Problems with dataguard on primary and standby db
                                    ADaniel
                                    check that you are trying to send the archive logs to the actual standby server and not to primary. I had the same issue when I configured wrong the parameters fal_server and fal_client. I got all sorts of errors on both databases.
                                    So, check that archive_log_dest_2 is correctly configured, check fal_ paramters that they are ok.