Oracle 9i standby database error

Hi all,
I am getting this error on my standby DB while it's archiving a log...and I've even restarted the DB and media recovery.Also, it's not a disk space issue.
Errors in file f:\oracle\admin\xxxprd\bdump\xxxprd_pmon_5224.trc:
ORA-16145: archival for thread# 1 sequence# 19113 in progress
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Any ideas ?
Much appreciated

Hi;
Please see below notes which could be helpful for your issue
https://support.oracle.com/CSP/main/article?cmd=show&type=COMMUNITIES&doctype=COMTHREAD&id=75725
http://download.oracle.com/docs/cd/B19306_01/server.102/b14219/e12700.htm#sthref4916
OERR: ORA-16145 archival for thread# %s sequence# %s in progress [ID 172871.1]
Regard
Helios

Similar Messages

  • ORACLE 8I: STANDBY DATABASE는 STANDARD와 ENTERPRISE EDITION에서 사용이 가능한가?

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-31
    ORACLE 8I: STANDBY DATABASE는 STANDARD와 ENTERPRISE EDITION에서 사용이 가능한가?
    =====================================================================
    Problem Description
    원격의 Standby 데이터베이스 구성을 고려하지만, standby 사이트로
    고려하는 장비에는 Oracle8i Standard Edition이 동작을 하고 있는 반면
    primary 사이트에는 Oracle8i Enterprise Edition이 동작을 하고 있다.
    이러한 경우 다음의 질문을 하게 된다:
    Primary 사이트에서는 Oracle8i Enterprise Edition을 standby 사이트에서는
    Oracle8i Standard Edition을 사용하는 것은 가능한가?
    Oracle8i Standard Edition database가 Standby 모드로 동작을 하면서
    Oracle8i Enterprise Edition database의 log들을 유효하게 받아들일 수
    있는가?
    Solution Description:
    Basic Standby 데이터베이스 기능은 Oracle7,Release 7.3.x, Oracle8, 그리고
    Oracle8i Standard Edition에서 사용이 가능하다.
    Enterprise Edition과 Standard Edition 모두 Standby 데이터베이스 기능을
    사용하기 위하여 구성할 수 있다. 그렇지만, Non-managed Standby 환경에서
    Stabdby 데이터베이스에 적용하여 복구를 하기 위한 추가적인 작업이 필요하다.
    a) Standby 데이터베이스 상에서 수동 또는 스크립트에 의한 복구가 필요하다.
    b) 저장되어진 Redo Log들을 Standby 사이트로 옮기기 위한 방법이 필요하다.
    Explanation:
    ===========
    Standard edition에서 사용할 수 없는 Standby 데이터베이스 특징의 유일한 점은
    Log의 원격 이동 능력이다. 다시말하면, Oracle8i의 Log 원격 이동 기능은
    Enterprise Edition에만 있는 특징중의 하나이다. 이 이외의 Standby 데이터베이스
    특징들은 Oracle8i Standard Edition이나 Oracle8i Enterprise Editio 모두
    동일하다.
    자동 Log 이동은 Managed Standby 환경으로 Standby 데이터베이스를 운영하기
    위해서 필요하다.
    Reference Ducumment
    <Note:111678.1> Oracle8i: Is Standby Database Available For Standard And
    Enterprise Edition?

  • Standby database error

    Hi Guys..
    I am using oracle 10.2.0.4.0 on windows 2003 server. I created a physical standby database successfully.
    On standby database, I fired the following query
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#
    SEQUENCE# FIRST_TIM NEXT_TIME
    10715 02-AUG-10 02-AUG-10
    10716 02-AUG-10 02-AUG-10
    10717 02-AUG-10 03-AUG-10
    10718 03-AUG-10 03-AUG-10
    10719 03-AUG-10 03-AUG-10
    10720 03-AUG-10 03-AUG-10
    10721 03-AUG-10 03-AUG-10
    10722 03-AUG-10 03-AUG-10
    10723 03-AUG-10 03-AUG-10
    10724 03-AUG-10 03-AUG-10
    10725 03-AUG-10 03-AUG-10
    SEQUENCE# FIRST_TIM NEXT_TIME
    10726 03-AUG-10 03-AUG-10
    10727 03-AUG-10 03-AUG-10
    10728 03-AUG-10 03-AUG-10
    10729 03-AUG-10 03-AUG-10
    I then did alter system switch logfile on primary database
    Then on standby I fired the above query
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#
    SEQUENCE# FIRST_TIM NEXT_TIME
    10715 02-AUG-10 02-AUG-10
    10716 02-AUG-10 02-AUG-10
    10717 02-AUG-10 03-AUG-10
    10718 03-AUG-10 03-AUG-10
    10719 03-AUG-10 03-AUG-10
    10720 03-AUG-10 03-AUG-10
    10721 03-AUG-10 03-AUG-10
    10722 03-AUG-10 03-AUG-10
    10723 03-AUG-10 03-AUG-10
    10724 03-AUG-10 03-AUG-10
    10725 03-AUG-10 03-AUG-10
    SEQUENCE# FIRST_TIM NEXT_TIME
    10726 03-AUG-10 03-AUG-10
    10727 03-AUG-10 03-AUG-10
    10728 03-AUG-10 03-AUG-10
    10729 03-AUG-10 03-AUG-10
    *10730 03-AUG-10 03-AUG-10*
    My question is everytime I do alter systyem switch logfile on primary , two trace files are generated on primary database which are:
    stutest_lns1_5764.trc
    Dump file c:\oracle\admin\stutest\bdump\stutest_lns1_5764.trc
    Tue Aug 03 15:50:35 2010
    ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU : 8 - type 8664, 2 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:8414M/16378M, Ph+PgF:10750M/17814M
    Instance name: stutest
    Redo thread mounted by this instance: 1
    Oracle process number: 43
    Windows thread id: 5764, image: ORACLE.EXE (LNS1)
    *** SERVICE NAME:(SYS$BACKGROUND) 2010-08-03 15:50:35.996
    *** SESSION ID:(213.29604) 2010-08-03 15:50:35.996
    *** 2010-08-03 15:50:35.996 60512 kcrr.c
    LNS1: initializing for LGWR communication
    LNS1: connecting to KSR channel
    Success
    LNS1: subscribing to KSR channel
    Success
    *** 2010-08-03 15:50:35.996 60565 kcrr.c
    LNS1: initialized successfully ASYNC=1
    Destination is specified with ASYNC=61440
    Redo shipping client performing standby login
    *** 2010-08-03 15:50:36.043 68145 kcrr.c
    Logged on to standby successfully
    Client logon and security negotiation successful!
    Archiving to destination STUSTDBY ASYNC blocks=20480
    Allocate ASYNC blocks: Previous blocks=0 New blocks=20480
    Log file opened [logno 2]
    *** 2010-08-03 16:00:58.344
    Archiving to destination STUSTDBY ASYNC blocks=20480
    Log file opened [logno 1]
    *** 2010-08-03 16:04:44.383
    Archiving to destination STUSTDBY ASYNC blocks=20480
    Log file opened [logno 3]
    *** 2010-08-03 16:07:36.794
    Archiving to destination STUSTDBY ASYNC blocks=20480
    Log file opened [logno 2]
    stutest_lgwr_4092.trc
    Dump file c:\oracle\admin\stutest\bdump\stutest_lgwr_4092.trc
    Fri Jul 30 17:01:59 2010
    ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU : 8 - type 8664, 2 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:13601M/16378M, Ph+PgF:10927M/17814M
    Instance name: stutest
    Redo thread mounted by this instance: 1
    Oracle process number: 6
    Windows thread id: 4092, image: ORACLE.EXE (LGWR)
    *** 2010-07-30 17:01:59.622
    *** SERVICE NAME:() 2010-07-30 17:01:59.606
    *** SESSION ID:(221.1) 2010-07-30 17:01:59.606
    Maximum redo generation record size = 156160 bytes
    Maximum redo generation change vector size = 150676 bytes
    *** 2010-07-30 22:01:00.446
    Warning: log write time 770ms, size 2KB
    *** 2010-07-30 22:08:37.586
    Warning: log write time 1120ms, size 9KB
    *** 2010-07-30 22:08:41.258
    Warning: log write time 680ms, size 7KB
    *** 2010-07-30 22:09:58.244
    Warning: log write time 660ms, size 1KB
    *** 2010-07-30 22:11:21.388
    Warning: log write time 860ms, size 6KB
    *** 2010-07-30 23:42:11.203
    Warning: log write time 580ms, size 1KB
    *** 2010-07-31 00:04:13.917
    Warning: log write time 980ms, size 8KB
    *** 2010-07-31 00:06:40.422
    Warning: log write time 930ms, size 22KB
    *** 2010-07-31 00:08:11.940
    Warning: log write time 1800ms, size 23KB
    *** 2010-07-31 21:13:33.694
    Warning: log write time 1460ms, size 40KB
    *** 2010-07-31 21:13:39.522
    Warning: log write time 2790ms, size 87KB
    *** 2010-07-31 21:13:46.054
    Warning: log write time 4940ms, size 69KB
    *** 2010-07-31 21:13:50.038
    Warning: log write time 3980ms, size 81KB
    *** 2010-07-31 21:13:55.616
    Warning: log write time 5580ms, size 61KB
    *** 2010-07-31 21:14:01.726
    Warning: log write time 6110ms, size 77KB
    *** 2010-07-31 21:14:08.258
    Warning: log write time 3530ms, size 140KB
    *** 2010-07-31 21:14:19.508
    Warning: log write time 1500ms, size 3KB
    *** 2010-07-31 22:07:49.954
    Warning: log write time 930ms, size 1KB
    *** 2010-07-31 23:16:01.054
    Warning: log write time 1080ms, size 103KB
    *** 2010-07-31 23:17:52.854
    Warning: log write time 1360ms, size 3KB
    *** 2010-07-31 23:23:26.631
    Warning: log write time 710ms, size 2KB
    *** 2010-08-01 00:04:58.476
    Warning: log write time 690ms, size 13KB
    *** 2010-08-01 00:06:51.980
    Warning: log write time 590ms, size 20KB
    *** 2010-08-01 00:07:38.153
    Warning: log write time 1540ms, size 28KB
    *** 2010-08-01 00:08:02.748
    Warning: log write time 770ms, size 64KB
    *** 2010-08-01 00:11:04.628
    Warning: log write time 1140ms, size 43KB
    *** 2010-08-01 17:05:49.886
    Warning: log write time 780ms, size 3KB
    *** 2010-08-01 21:00:46.571
    Warning: log write time 910ms, size 365KB
    *** 2010-08-01 21:09:22.447
    Warning: log write time 2910ms, size 22KB
    *** 2010-08-01 21:09:27.932
    Warning: log write time 4430ms, size 62KB
    *** 2010-08-01 21:09:34.010
    Warning: log write time 6060ms, size 74KB
    *** 2010-08-01 21:09:40.088
    Warning: log write time 3080ms, size 150KB
    *** 2010-08-01 21:09:45.495
    Warning: log write time 2410ms, size 99KB
    *** 2010-08-01 21:09:50.370
    Warning: log write time 4870ms, size 40KB
    *** 2010-08-01 21:09:55.401
    Warning: log write time 5030ms, size 82KB
    *** 2010-08-01 21:09:59.151
    Warning: log write time 3610ms, size 65KB
    *** 2010-08-01 23:05:40.560
    Warning: log write time 720ms, size 4KB
    *** 2010-08-01 23:06:05.030
    Warning: log write time 1670ms, size 21KB
    *** 2010-08-01 23:17:55.537
    Warning: log write time 1540ms, size 116KB
    *** 2010-08-01 23:23:35.891
    Warning: log write time 600ms, size 1KB
    *** 2010-08-02 00:05:52.363
    Warning: log write time 1340ms, size 48KB
    *** 2010-08-02 00:06:43.427
    Warning: log write time 1060ms, size 24KB
    *** 2010-08-02 00:06:50.177
    Warning: log write time 1730ms, size 209KB
    *** 2010-08-02 00:07:08.256
    Warning: log write time 950ms, size 17KB
    *** 2010-08-02 00:11:25.436
    Warning: log write time 1690ms, size 8KB
    *** 2010-08-02 00:12:11.313
    Warning: log write time 850ms, size 45KB
    *** 2010-08-02 00:13:55.754
    Warning: log write time 560ms, size 3KB
    *** 2010-08-02 11:27:52.686
    Warning: log write time 1440ms, size 46KB
    *** 2010-08-02 11:27:58.780
    Warning: log write time 3790ms, size 54KB
    *** 2010-08-02 11:28:02.546
    Warning: log write time 3760ms, size 70KB
    *** 2010-08-02 11:28:08.483
    Warning: log write time 5940ms, size 74KB
    *** 2010-08-02 11:28:13.812
    Warning: log write time 2330ms, size 139KB
    *** 2010-08-02 11:28:18.796
    Warning: log write time 1980ms, size 79KB
    *** 2010-08-02 11:28:25.093
    Warning: log write time 3360ms, size 88KB
    *** 2010-08-02 11:28:29.421
    Warning: log write time 4330ms, size 38KB
    *** 2010-08-02 16:10:45.927
    Warning: log write time 590ms, size 3KB
    *** 2010-08-02 22:08:57.806
    Warning: log write time 700ms, size 37KB
    *** 2010-08-02 23:07:22.262
    Warning: log write time 1750ms, size 234KB
    *** 2010-08-02 23:13:44.993
    Warning: log write time 1410ms, size 17KB
    *** 2010-08-03 00:04:08.387
    Warning: log write time 670ms, size 6KB
    *** 2010-08-03 00:07:44.347
    Warning: log write time 1890ms, size 1024KB
    *** 2010-08-03 00:08:14.395
    Warning: log write time 1680ms, size 1024KB
    *** 2010-08-03 00:08:26.817
    Warning: log write time 570ms, size 36KB
    *** 2010-08-03 00:08:39.427
    Warning: log write time 1540ms, size 1024KB
    *** 2010-08-03 00:08:50.818
    Warning: log write time 1810ms, size 1025KB
    *** 2010-08-03 00:08:58.990
    Warning: log write time 1640ms, size 942KB
    *** 2010-08-03 00:09:21.303
    Warning: log write time 1580ms, size 1024KB
    *** 2010-08-03 00:09:33.710
    Warning: log write time 1790ms, size 1025KB
    *** 2010-08-03 00:09:42.382
    Warning: log write time 1860ms, size 1024KB
    *** 2010-08-03 00:09:50.945
    Warning: log write time 1590ms, size 1024KB
    *** 2010-08-03 10:28:34.753
    Warning: log write time 2330ms, size 47KB
    *** 2010-08-03 10:29:44.440
    Warning: log write time 810ms, size 1KB
    *** 2010-08-03 10:32:27.392
    Warning: log write time 890ms, size 1KB
    *** 2010-08-03 10:36:02.536
    Warning: log write time 2070ms, size 8KB
    *** 2010-08-03 10:44:34.174
    Warning: log write time 740ms, size 7KB
    *** 2010-08-03 12:04:46.687
    Warning: log write time 2850ms, size 86KB
    *** 2010-08-03 12:04:52.656
    Warning: log write time 2970ms, size 85KB
    *** 2010-08-03 12:04:54.547
    Warning: log write time 1810ms, size 45KB
    *** 2010-08-03 14:06:20.827
    Warning: log write time 500ms, size 0KB
    *** 2010-08-03 14:13:46.404
    Warning: log write time 820ms, size 0KB
    *** 2010-08-03 15:50:32.996
    *** 2010-08-03 15:50:32.996 57052 kcrr.c
    Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
    Initializing PGA storage for Netserver communication
    LNSb is not running anymore.
    Check if new Async LNS1 needs to be started..
    .. yes it needs to be started
    Starting LNS1 ...
    Subscribing to KSR Channel [id=1]
    success!
    Indicating recv buffer for KSR Channel [id=1]
    success
    Waiting for LNS1 to initialize itself
    *** 2010-08-03 15:50:36.012 57343 kcrr.c
    Netserver LNS1 [pid 5764] for mode ASYNC has been initialized
    Performing a channel reset to ignore previous responses
    Connecting as publisher to KSR Channel [id=1]
    Successfully started LNS1 [pid 5764] for dest STUSTDBY mode ASYNC ocis=0x00000000144AE5B0
    *** 2010-08-03 15:50:36.012 57846 kcrr.c
    Making upiahm request to LNS1 [pid 5764]: Begin Time is <08/03/2010 15:50:32>. NET_TIMEOUT = <10> seconds
    *** 2010-08-03 16:00:58.266
    *** 2010-08-03 16:00:58.266 57052 kcrr.c
    Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
    LNSb is not running anymore.
    Check if new Async LNS1 needs to be started..
    Previous Async LNS1 [pid 5764] is running .. no need to start another one
    LGWR detected that Async LNS1 [pid 5764] is already running
    *** 2010-08-03 16:04:44.289
    *** 2010-08-03 16:04:44.289 57052 kcrr.c
    Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
    LNSb is not running anymore.
    Check if new Async LNS1 needs to be started..
    Previous Async LNS1 [pid 5764] is running .. no need to start another one
    LGWR detected that Async LNS1 [pid 5764] is already running
    *** 2010-08-03 16:07:36.747
    *** 2010-08-03 16:07:36.747 57052 kcrr.c
    Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
    LNSb is not running anymore.
    Check if new Async LNS1 needs to be started..
    Previous Async LNS1 [pid 5764] is running .. no need to start another one
    LGWR detected that Async LNS1 [pid 5764] is already running
    *** 2010-08-03 16:13:06.633
    Warning: log write time 570ms, size 0KB
    Did I miss something while creating standby.???
    Thanks for the help

    are these databases on same server.
    BTW These are not errors, they are warning ... I have also seen these kind of warning many times. they can be ignored if ur shipping and recovery on standby is Preperly happening.
    Regards
    jasbir

  • Physical standby database error

    Hi,
    I try to create physical standby in my local machine using oracle 10g
    version :10.2.0.1.0
    Os: windows xp.
    I followed steps and parameter files
    on primary :-
    sql>alter database force logging;
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\oracle\product\10.2.0/admin/orcl/adump'
    *.background_dump_dest='D:\oracle\product\10.2.0/admin/orcl/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\oracle\product\10.2.0\oradata\orcl\control01.ctl','D:\oracl
    e\product\10.2.0\oradata\orcl\control02.ctl','D:\oracle\product\10.2.0\orad
    ata\orcl\control03.ctl'
    *.core_dump_dest='D:\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'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\oracle\product\10.2.0/admin/orcl/udump'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'
    *.log_archive_dest_2='SERVICE=stby LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
    *.log_archive_format=%t_%s_%r.arc
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    On standby
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\stby\adump'
    *.background_dump_dest='D:\stby\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\stby\ctrl.ctl'
    *.core_dump_dest='D:\stby\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_unique_name='stby'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='NONE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\stby\udump'
    *.db_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
    *.log_archive_dest_2='SERVICE=orcl LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=orcl'
    *.standby_archive_dest='D:\stby\archive'
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    *.standby_file_management='AUTO'
    *.fal_server='orcl'
    *.fal_client='stby'
    SQL> conn / as sysdba
    Connected to an idle instance.
    SQL> startup pfile=D:\stby\initstby.ora nomount;
    ORACLE instance started.
    Total System Global Area 247463936 bytes
    Fixed Size 1248332 bytes
    Variable Size 79692724 bytes
    Database Buffers 159383552 bytes
    Redo Buffers 7139328 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01154: database busy. Open, close, mount, and dismount not allowed now
    SQL> recover managed standby database cancel;
    Media recovery complete.
    SQL> alter database open read only;
    Database altered.
    SQL> select sequence#,first_time,next_time from v$archived_log order by sequence
    no rows selected
    No archive s generated in standby ..
    what i mistake.
    Reagrds
    S.Azar

    Anand... wrote:
    Firstly you can use "*select sequence#,first_time,next_time from v$archived_log order by sequence#;"* command in mount stage itself.No need to open the standby database in ready only mode.
    No rows selected in mount stage also.
    The V$ARCHIVED_LOG fixed view on the physical standby database shows all the archived redo log files received from the primary database.
    sql> select * from v$archived_log;
    no rows selected.
    and No archived logs received from primary database to physical standby . i think here i wrongly configure parameter file.
    sql> RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; -- > start Redo Apply
    When you do log switch on the primary are the archive logs getting transferred to the standby database???Is there some error in the alert log file in the primary database.
    No..
    >
    [http://advait.wordpress.com/2007/06/12/setting-up-oracle-dataguard-for-10g/]
    Regards
    S.Azar

  • Standby database errors - Alter database open read only

    alter database open read only
    AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
    Signalling error 1152 for datafile 1!
    Beginning standby crash recovery.
    Serial Media Recovery started
    Managed Standby Recovery starting Real Time Apply
    Media Recovery Waiting for thread 1 sequence 216
    Mon Dec 20 11:58:18 2010
    Standby crash recovery need archive log for thread 1 sequence 216 to continue.
    Please verify that primary database is transporting redo logs to the standby database.
    Wait timeout: thread 1 sequence 216
    Standby crash recovery aborted due to error 16016.
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!
    Completed standby crash recovery.
    Signalling error 1152 for datafile 1!
    Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    ORA-10458 signalled during: alter database open read only...
    Mon Dec 20 12:13:46 2010
    ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    Attempt to start background Managed Standby Recovery process (MDM2)
    Mon Dec 20 12:13:46 2010
    MRP0 started with pid=23, OS id=18974
    MRP0: Background Managed Standby Recovery process started (MDM2)
    started logmerger process
    Mon Dec 20 12:13:51 2010
    Managed Standby Recovery starting Real Time Apply
    Parallel Media Recovery started with 2 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Media Recovery Waiting for thread 1 sequence 216
    Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
    The above lines are from alert log of standby database.
    Standby standbase
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
    Parameters set on primary are
    log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
    log_archive_dest_state_1 ENABLE
    log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
    log_archive_dest_state_2 ENABLE
    dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
    dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
    fal_server MDM2
    standby_file_management AUTO
    log_archive_config dg_config=(MDM1,MDM2)
    db_file_name_convert MDM2, MDM1
    ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
    Standby pfile
    *.archive_lag_target=900
    *.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
    *.audit_trail='db'
    *.compatible='11.2.0.0.0'
    *.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='+MDMDG1'
    *.db_domain=''
    *.db_file_name_convert='MDM1','MDM2'
    *.db_name='MDM'
    *.db_recovery_file_dest='+MDMDG2'
    *.db_recovery_file_dest_size=10485760000
    *.db_unique_name='MDM2'
    *.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
    *.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
    *.fal_server='MDM11','MDM12'
    *.instance_name='MDM2'
    *.log_archive_config='dg_config=(MDM1,MDM2)'
    *.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
    *.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='MDM_%t_%s_%r.arc'
    *.log_file_name_convert='MDM1','MDM2'
    *.memory_target=838860800
    *.nls_language='ENGLISH'
    *.nls_territory='UNITED KINGDOM'
    *.open_cursors=300
    *.processes=500
    *.remote_login_passwordfile='exclusive'
    *.sessions=555
    *.standby_file_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    On standby ASM
    ASMCMD [+] > find * *
    +MDMDG1/ASM/
    +MDMDG1/ASM/ASMPARAMETERFILE/
    +MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
    +MDMDG1/MDM/
    +MDMDG1/MDM2/
    +MDMDG1/MDM2/CONTROLFILE/
    +MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
    +MDMDG1/MDM2/CONTROLFILE/current.265.738243333
    +MDMDG1/MDM2/DATAFILE/
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
    +MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
    +MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
    +MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
    +MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
    +MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
    +MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
    +MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
    +MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
    +MDMDG1/MDM2/DATAFILE/USERS.278.738243347
    +MDMDG1/MDM2/ONLINELOG/
    +MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
    +MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
    +MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
    +MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
    +MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
    +MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
    +MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
    +MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
    +MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
    +MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
    +MDMDG2/MDM/
    +MDMDG2/MDM/DG_CONFIG/
    +MDMDG2/MDM2/
    +MDMDG2/MDM2/AUTOBACKUP/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
    +MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
    +MDMDG2/MDM2/CONTROLFILE/
    +MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
    +MDMDG2/MDM2/CONTROLFILE/current.271.738243335
    +MDMDG2/MDM2/ONLINELOG/
    +MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
    +MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
    +MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
    +MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
    +MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
    +MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
    +MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
    +MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
    +MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
    +MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
    +MDMDG3/MDM/
    +MDMDG3/MDM/ARCH/
    +MDMDG3/MDM2/
    +MDMDG3/MDM2/ARCH/
    -- Please can I know how to open read only standby database.

    user5846399 wrote:
    ORA-16016: archived log for thread 1 sequence# 216 unavailable
    Recovery interrupted!archived log for thread 1 sequence# 216
    This file is needed for recovery, Find it and move it to the standby database side.

  • Standby database Error in applying archives

    Hi All
    Environment:
    Oracle 8i
    Platform- HP-UX
    I have production database on HPUX box and standby database on anothe HPUX box.
    I am applying archive to standby everyday manually.
    In last week, I have added ney datafile webapp03 in Production database tablespace.
    When I apply archive to standby database. It says archive apply sucessfully but give below warning:
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 25 needs more recovery to be consistent
    ORA-01110: data file 25: '/u06/oradata/vestcom/webapp03.dbf'
    Yesterday I have copied datafile from production to standby database.
    But still I am getting same warning:
    Please let me know in detail, I am totally new in this admin field.
    Please help me out for this issue:
    Thanks in Advance.
    R M

    Absolutely. First place the tablespace space in backup mode, then copy over the datafile and then end the backup mode - applying the log files should be fine now.
    HTH
    Thanks
    Chandra

  • Rman standby database error

    Hi All,
    I am getting the following error when trying to CONFIGURE STANDBY database using rman,db version 10.2.0.2(HP-UX 11.2),library link seems to be fine.
    do i have to relink the library to oracle on the stanby db host too? any suggestion please.
    connect target / catalog rman@xx auxiliary sys@aux
    RMAN> run {
    allocate channel c1 device type 'sbt_tape';
    ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE 'SBT_TAPE';
    duplicate target database for standby dorecover;}2> 3> 4>
    allocated channel: c1
    channel c1: sid=164 instance=WWPODSP1 devtype=SBT_TAPE
    channel c1: Data Protector A.06.00/331
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on aux1 channel at 05/09/2007 16:57:07
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 11
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'control_file_%F';
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_WWPODSP1.f'; # default

    sorry here is the exact commands.
    rman TARGET / AUXILIARY sys/xxx@WWPODSS catalog rman@rman
    Recovery Manager: Release 10.2.0.2.0 - Production on Wed May 9 17:29:37 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: WWPODSP (DBID=669261963)
    recovery catalog database Password:
    connected to recovery catalog database
    connected to auxiliary database: WWPODSP (not mounted)
    RMAN> run
    2> {
    3> duplicate target database for standby dorecover;}
    Starting Duplicate Db at 09-MAY-07
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/09/2007 17:33:35
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27211: Failed to load Media Management Library
    Additional information: 11
    RMAN>

  • Oracle manually standby database with standard edition

    Hi, I want to have a plan for disaster. I'm triying with two virtual machines with oracle database 10g on suse linux. I follow these URLs
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    http://oramdq.blogspot.com/2009/05/como-configurar-un-sistema-de-alta.html
    and it look that work all right.
    I know that with manually standby database we applied archived logs, and so, we don't propagate any physical changes to secondary database (standby), for example, if I create a new tablespace, or adding a new datafile to an existing tablespace, it don't work in the secondary database.
    Anyone does know how is the better way to apply the physical changes??
    Anyone have any scripts to do that?
    Thanks in advance.

    HI,
    Add the STANDBY_FILE_MANAGEMENT = AUTO to the primary parameter file, it will solve it.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams209.htm]
    Reagds,
    Vijayaraghavan K
    Edited by: Vijayaraghavan Krishnan on Feb 24, 2010 7:19 PM

  • Oracle 8i Standby Database

    Hi Guys,
    Need your help.
    Can I create a standby database with two different machine operating system? like windows and linux?
    Regards,
    Benjo

    This is not possible with Oracle 8i but is only possible with Oracle 11g in some specific cases: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/standby.htm#i72053.

  • Recover standby database error

    Hi
    here is the error message i got when i run this command
    09:30:35 SYS@MOZAI> alter database recover standby database until cancel;
    alter database recover standby database until cancel
    ERROR at line 1:
    ORA-00279: change 126425376421 generated at 02/26/2012 09:26:00 needed for thread 2
    ORA-00289: suggestion : +ARCH
    ORA-00280: change 126425376421 for thread 2 is in sequence #312362
    Any suggestion is highly apprciated .
    Thanks

    Hello;
    You probably started the recovery ( to apply redo from the Primary )
    Cancel this before doing the command you trying :
    alter database recover managed standby database cancel;Then issue your command again.
    Best Regards
    mseberg

  • Error in mounting the standby database

    Hi All,
    OS:Solaris
    DB:10G
    I am facing the below mentioned error while i am trying to create a standby database on the same server.
    Following are the steps that i have followed for the same.
    1.Checked the connectivity.
    2.Created the pfile for primary DB as mentioned below:
    *.DB_BLOCK_SIZE=8192
    *.OPEN_CURSORS=300
    *.CURSOR_SHARING=FORCE
    *.BACKGROUND_DUMP_DEST='/11g/oradata/admin/ettest/bdump'
    *.CORE_DUMP_DEST='/11g/oradata/admin/ettest/cdump'
    *.USER_DUMP_DEST='/11g/oradata/admin/ettest/udump'
    *.CONTROL_FILES=("/11g/oradata/admin/data/controlfiles/control01.ctl","/11g/oradata/admin/data/controlfiles/control02.ctl")
    *.DB_NAME=ettest
    *.PROCESSES=150
    *.UNDO_MANAGEMENT=AUTO
    *.UNDO_TABLESPACE=undotbs
    *.compatible='10.2.0.1.0'
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.LOG_ARCHIVE_DEST_1='Location=/11g/oradata/archives/'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.DB_FILE_NAME_CONVERT='/11g/oradata/admin/data/datafiles/','/11g/oradata_dr/ettestdr/datafiles/'
    *.LOG_FILE_NAME_CONVERT='/11g/oradata/admin/data/logfiles/','/11g/oradata_dr/ettestdr/redologs/'
    *.STANDBY_ARCHIVE_DEST='/11g/oradata_dr/ettestdr/dr_archives/ettestdr'
    *.LOG_ARCHIVE_DEST_2='SERVICE=ettestdr'
    *.FAL_SERVER='ETTESTDR'
    *.FAL_CLIENT='ETTEST'
    3. Created the pfile for DR:
    *.DB_UNIQUE_NAME=ettestdr
    *.DB_BLOCK_SIZE=8192
    *.OPEN_CURSORS=300
    *.CURSOR_SHARING=FORCE
    *.BACKGROUND_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/bdump'
    *.CORE_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/cdump'
    *.USER_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/udump'
    *.CONTROL_FILES=("/11g/oradata_dr/ettestdr/controlfiles/standbycontrolfile.ctl")
    *.DB_NAME=ettestdr
    *.PROCESSES=150
    *.UNDO_MANAGEMENT=AUTO
    *.UNDO_TABLESPACE=undotbs
    *.compatible='10.2.0.1.0'
    *.FAL_SERVER='ETTEST'
    *.FAL_CLIENT='ETTESTDR'
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.LOG_ARCHIVE_DEST_1='Location=/11g/oradata/archives/'
    *.STANDBY_ARCHIVE_DEST='/11g/oradata_dr/ettestdr/dr_archives/ettestdr'
    *.LOG_ARCHIVE_DEST_2='SERVICE=ettestdr'
    *.LOG_ARCHIVE_DEST_STATE_2='DEFER'
    *.DB_FILE_NAME_CONVERT='/11g/oradata_dr/ettestdr/datafiles/','/11g/oradata/admin/data/datafiles/'
    *.LOG_FILE_NAME_CONVERT='/11g/oradata_dr/ettestdr/redologs/','/11g/oradata/admin/data/logfiles/'
    4.In the mean time i have backed up the database and transferd the same on the DR location and then i ahve created the standbycontrolfiel using the command on priamary server with sys login using the command:
    alter databse create standby controlfile as '/path';5.My Primary was up using the said pfile.
    6.I was also able to put my DR in nomount stage using the above pfile
    7.I transfered the controlfile at the appropriate location of the DR server and when i am trying to mount the DR db using:
    alter database mount standby database;I am getting the below mentioned error
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'ETTEST' in control file is not 'ETTESTDR'
    Kindly suggest...BR
    Sphinx
    Edited by: $phinx19 on Dec 12, 2012 5:29 AM

    Hi,
    You must create pfile for Standby side with parameter DB_UNIQUE_NAME = ettestdr but DB_NAME is same with primary as DB_NAME = ettest.
    *.DB_UNIQUE_NAME=ettestdr
    *.DB_BLOCK_SIZE=8192
    *.OPEN_CURSORS=300
    *.CURSOR_SHARING=FORCE
    *.BACKGROUND_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/bdump'
    *.CORE_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/cdump'
    *.USER_DUMP_DEST='/11g/oradata_dr/ettestdr/admin/udump'
    *.CONTROL_FILES=("/11g/oradata_dr/ettestdr/controlfiles/standbycontrolfile.ctl")
    *.DB_NAME=ettest
    *.PROCESSES=150
    *.UNDO_MANAGEMENT=AUTO
    *.UNDO_TABLESPACE=undotbs
    *.compatible='10.2.0.1.0'
    *.FAL_SERVER='ETTEST'
    *.FAL_CLIENT='ETTESTDR'
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.LOG_ARCHIVE_DEST_1='Location=/11g/oradata/archives/'
    *.STANDBY_ARCHIVE_DEST='/11g/oradata_dr/ettestdr/dr_archives/ettestdr'
    *.LOG_ARCHIVE_DEST_2='SERVICE=ettest'
    *.LOG_ARCHIVE_DEST_STATE_2='DEFER'
    *.DB_FILE_NAME_CONVERT='/11g/oradata_dr/ettestdr/datafiles/','/11g/oradata/admin/data/datafiles/'
    *.LOG_FILE_NAME_CONVERT='/11g/oradata_dr/ettestdr/redologs/','/11g/oradata/admin/data/logfiles/' And in pfile for standby *.LOG_ARCHIVE_DEST_2='SERVICE=ettest' - after switchover logs transport to primary (ettest)
    Regards
    Mahir M. Quluzade
    www.mahir-quluzade.com
    Edited by: Mahir M. Quluzade on Dec 12, 2012 5:44 PM

  • Creation of Standby database on same host

    Hi All,
    I am using oracle 9.2.0.1.0 on windows XP machine.
    *I want to create the standby database for my primary database on same machine.
    But both tha data base is heaving diff instance as well as the diff database name say "ASHU" for primary & "TEST" for standby database.
    I took the backup of all datafile and copied it in the standby location.
    Generate the standby control file also and copied to the standby location.
    But when i am going to start the standby database it is giving the below error:
    SQL> startup nomount;
    ORACLE instance started.
    Total System Global Area 135338868 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 667648 bytes
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'ASHU' in controlfile is not 'TEST'
    How to rectify it? Please help me
    (* This is only for learning pupose , that's why i am going to create both on same host"

    >
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'ASHU' in controlfile is not 'TEST'
    How to rectify it? Please help me
    >
    You do not change the dbname of the physical standby database. They always must have the same name as the primary.
    Here is a snippet from my standby initialization file for a 9i installation. Notice the parameter LOCK_NAME_SPACE that was replaced in 10g with DB_UNIQUE_NAME
    db_file_name_convert=('E:\PRIMA','E:\PHYST')
    db_name='PRIMA'
    instance_name='PHYST'
    service_names='PHYST'
    lock_name_space='PHYST'
    log_archive_dest_1='LOCATION=E:\PHYST\ARCHIVE'
    log_archive_start=TRUE
    log_archive_format='%t_%s.arc'
    log_file_name_convert=('E:\PRIMA','E:\PHYST')Kind regards
    Uwe
    http://uhesse.wordpress.com
    Edited by: Uwe Hesse on 27.07.2009 13:36

  • MANAGED RECOVERY AT STANDBY DATABASE REQURING OLD ARCHIVELOGS ORA-00308

    Oracle 9.2.0.4
    HP-UX 11.11i
    The database in Archivelog mode, single standby database in managed recovery
    mode.
    keeping standby in sync with manual applying the ARCHIVELOG from primary to
    standby database.
    primary database was 3 REDO log members of 100 MB with 1 member each.
    what i did, 1 drop and re-create the INACTIVE REDO group for all three, and
    make them
    5 REDO logs of 200 MB with 1 member each,
    then in order to keep fresh copy of primary database onto standby database, i
    send the cold backup after 15 days (last week) with standby controlfile.
    now, with that standby controlfile and the database, i can mount the database
    but while to open the database, receives messages as , it requiring the
    ARCHIVELOGS generated log time ago.
    changes the REDO groups from 3 to 5 and size 100 to 200 MB at INACTIVE state
    ### Workarounds Used ###
    SQL> alter database mount standby database;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
    SQL> alter database recover automatic standby database;
    alter database recover automatic standby database
    ERROR at line 1:
    ORA-00279: change 1655989696 generated at 08/12/2005 12:46:25 needed for thread
    1
    ORA-00289: suggestion :
    /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
    ORA-00280: change 1655989696 for thread 1 is in sequence #16849
    ORA-00278: log file
    '/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf' no longer needed
    for this recovery
    ORA-00308: cannot open archived log
    '/user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf'
    ORA-27037: unable to obtain file status
    HP-UX Error: 2: No such file or directory
    Additional information: 3
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /user02/oracle9i/oradata/iobasprd/archive
    Oldest online log sequence 53052
    Next log sequence to archive 53056
    Current log sequence
    53056
    -----------------------AlertIOBASPRD.log----------------------------
    alter database mount standby database
    Mon Oct 24 12:05:05 2005
    Successful mount of redo thread 1, with mount id 3283884781.
    Mon Oct 24 12:05:05 2005
    Standby Database mounted.
    Completed: alter database mount standby database
    Mon Oct 24 12:05:12 2005
    alter database open read only
    ORA-16004 signalled during: alter database open read only...
    Mon Oct 24 12:05:23 2005
    alter database recover automatic standby database
    Mon Oct 24 12:05:23 2005
    Media Recovery Start
    Starting datafile 1 recovery in thread 1 sequence 52617
    Datafile 1: '/user01/oracle9i/oradata/iobasprd/system01.dbf'
    Starting datafile 2 recovery in thread 1 sequence 52617
    Datafile 2: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_005.dbf'
    Starting datafile 3 recovery in thread 1 sequence 52617
    Datafile 3: '/user01/oracle9i/oradata/iobasprd/drsys01.dbf'
    Starting datafile 4 recovery in thread 1 sequence 52617
    Datafile 132: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_002.dbf'
    Starting datafile 133 recovery in thread 1 sequence 52617
    Datafile 133: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_003.dbf'
    Starting datafile 134 recovery in thread 1 sequence 52617
    Datafile 134: '/user01/oracle9i/oradata/iobasprd/TBMS_TS_004.dbf'
    Media Recovery Log
    Media Recovery Log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf
    Errors with log /user02/oracle9i/oradata/iobasprd/archive/archive_16849.dbf.
    ORA-279 signalled during: alter database recover automatic standby database...
    Mon Oct 24 12:06:01 2005
    Restarting dead background process QMN0
    QMN0 started with pid=9
    The snap of alertIOBASPRD.log can understand me that it requiring the
    ARCHIVELOG 52617 only
    and its lying in LOG_ARCHIVE_DET location also as
    $ pwd
    /user02/oracle9i/oradata/iobasprd/archive
    $ ls archive_5261*.dbf
    archive_52610.dbf archive_52613.dbf archive_52616.dbf archive_52619.dbf
    archive_52611.dbf archive_52614.dbf archive_52617.dbf
    archive_52612.dbf archive_52615.dbf archive_52618.dbf
    $
    now, even the files are lying , why ORACLE requing the old archive logs ?????

    You haven't given any usefuly information on your problem.
    show parameter log_archive_dest
    show parameter fal
    show parameter dg
    What errors are in your alert logs ?
    What command are you using to recover ?
    Check the contents of v$archived_log
    # run on primary to detect failures :-
    select destination, status, fail_date, valid_now
    from v$archive_dest
    where status != 'VALID' or VALID_NOW != 'YES';
    # run on standby to get exact position of rollforward :-
    select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
    to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
    to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;
    Are you using dataguard broker ?

  • Physical Standby - Recovery error

    Hi,
    Windows XP, 10.2.0.1.0
    I m getting the error like
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'PRIM' in control file is not 'STBY'
    Please suggest me
    Thanks
    KSG
    Edited by: KSG on Jun 15, 2010 1:15 PM

    Hi,
    Hope I have some issue with the parameter file. Please find my parameter files
    initPRIM.ora
    PRIM.__db_cache_size=411041792
    PRIM.__java_pool_size=4194304
    PRIM.__large_pool_size=4194304
    PRIM.__shared_pool_size=163577856
    PRIM.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/PRIM/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\PRIM\control01.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control02.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='PRIM'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=PRIMXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=197132288
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=591396864
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/udump'
    *.log_archive_dest_1='location=C:\oracle\archiveprim'
    *.log_archive_format='ARCH_%r_%t_%s.ARC'
    initstby.ora
    stby.__db_cache_size=411041792
    stby.__java_pool_size=4194304
    stby.__large_pool_size=4194304
    stby.__shared_pool_size=163577856
    stby.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/stby/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/stby/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\CONTROL_SB01.CTL'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/stby/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='stby'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=stbyXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=197132288
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=591396864
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/stby/udump'
    *.log_archive_dest_1='location=C:\oracle\archivestby'
    *.log_archive_format='ARCH_%r_%t_%s.ARC'
    *.standby_archive_dest='C:\oracle\archiveprim'
    *.db_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
    *.log_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
    *.standby_file_management=AUTO
    *.remote_archive_enable=TRUE

  • Difference between physical standby database and Data Guard

    Hi guys,
    Today I attended one interview. They asked me a difference between the Oracle Physical Standby database and Oracle Dataguard?
    Upto my knowledge Oracle Physical Standby Database is one type of Standby Database can be configured using Oracle Databaguard Feature.
    Can you people calrify me on this.
    Regards,
    Vijayaraghavan K

    hello,
    yes you are right upto some extent...here is para form oracle doc
    Oracle Data Guard is the most effective and comprehensive
    data availability, data protection, and disaster recovery solution
    for enterprise databases. It provides the management, monitoring,
    and automation software infrastructure to create and maintain one
    or more synchronized standby databases to protect data from failures,
    disasters, errors, and corruptions.
    Data Guard standby databases can be located at remote disaster
    recovery sites thousands of miles away from the production data center,
    or they may be located in the same city, same campus,
    or even in the same building. If the production database
    becomes unavailable because of a planned or an unplanned outage,
    Data Guard can switch any standby database to the production role,
    thus minimizing downtime and preventing any data loss.oracle data guard is maximum availiblity solution which maintain physical standby databases and in case of failure of production can switch production role to and standby database.
    read it here
    http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
    thanks and regards
    VD
    Edited by: Dixit on Aug 31, 2009 1:35 AM
    Edited by: Dixit on Aug 31, 2009 1:36 AM

Maybe you are looking for

  • About the new "8-core"

    Hi! i'm in the mood of a new mac... my old G4 is to slow to handle the new studio 6. is it worth to buy the new 8-core? will the applications use 8-core? thanks

  • Can New mac mini supports SATA III harddisk?

    The new mac mini is used "Hitachi HTS545050B9A302" as harddrive.  I don't know it is a SATA II or SATA III harddisk. Can anyone tell me. Thanks.

  • Cont Acq to File (scaled) results in unexpected behavior

    I am writing an application based on the "Cont Acq to File(scaled).vi example". The DAQ card on my system is the PCI-MIO-16E-4. I am acquiring only 1-chanel with the following data acquisition parameters: Scan Rate = 30000, Buffer Size = 300000, Numb

  • After Effects 7.0 cs2

    Hi I'm having a problem with After Effects 7.0, when i go to use it , a window pops up and asks me to personalize it and asks for the serial #, when i enter the serial # , I get a invalid serial # message, I've used After Effects before, Its been a f

  • Role Expert - Compliance Clibrator -Question

    hi, 1. I Design My roles using the Role Expert. 2. I see that there are no confliciting roles in the in this creation. Now, this being so Why Do I need the compliance calibrator ?? I understand that to make sure that the organisaton ids complaint. bu