Catbundle.sql in standby database

Hi
Just thought of checking with you all , I am trying to install the Jan 2012 patch . on a rac database which has standby as well .
Just not sure do i need to run the catbundle and the utlrep on the standby database after patching and before the logshipping is done.
Any suggestion is highly apprciated .
Thanks

Hello
No you do not run this on the Standby. This SQL will move from the Primary to the Standby as part of the Redo transport.
Just install the patch software only.
Stop apply on the Standby and shutdown the database.
Set it to Defer on the Primary. alter system set log_archive_dest_state_2=defer;
After the patch is installed on the Primary, install the software only on the Standby.
Then alter system set log_archive_dest_state_2=Enable; on the Primary.
Finally startup mount and restart apply on the Standby.
Best Regards
mseberg

Similar Messages

  • Do we need run catbundle.sql file for new databases.

    dear all,
    i have doubt over execution of catbundle.sql or not?
    scenario:
    i have insatlled 10gr2 on rhel5 and applied patchset 4 (10.2.0.5) and applied Oracle® Database Patch 10248542 - 10.2.0.5.2 Patch Set Update
    after this i have create fresh database.
    now,
    in Oracle® Database Patch 10248542 - 10.2.0.5.2 Patch Set Update document it has specified in belwo section
    3.4 Post Installation Instructions for Databases Created or Upgraded after Installation of PSU 10.2.0.5.2 in the Oracle Home
    These instructions are for a database that is created or upgraded after the installation of PSU 10.2.0.5.2.
    You must execute the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" for any new database only if it was created by any of the following methods:
    Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing)
    Using a script that was created by DBCA that creates a database from a sample database
    Cloning a database that was created by either of the two preceding methods, and if the steps in Section 3.3.2, "Loading Modified SQL Files into the Database" were not executed after PSU 10.2.0.5.2 was applied
    Upgraded databases do not require any post-installation steps.
    so do we need to run catbundle here or not.
    since i have created fresh database after applying 10.2.0.5 PSU2 why does it required.
    opatch output:
    [oracle@RG615 ~]$ opatch lsinventory
    Invoking OPatch 10.2.0.5.1
    Oracle Interim Patch Installer version 10.2.0.5.1
    Copyright (c) 2010, Oracle Corporation. All rights reserved.
    Oracle Home : /prd/crm/swbcrmdb/usr/oracle/product/10.2.0/db_1
    Central Inventory : /prd/crm/swbcrmdb/usr/oracle/oraInventory
    from : /etc/oraInst.loc
    OPatch version : 10.2.0.5.1
    OUI version : 10.2.0.5.0
    OUI location : /prd/crm/swbcrmdb/usr/oracle/product/10.2.0/db_1/oui
    Log file location : /prd/crm/swbcrmdb/usr/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2011-05-03_11-41-34AM.log
    Patch history file: /prd/crm/swbcrmdb/usr/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt
    Lsinventory Output file location : /prd/crm/swbcrmdb/usr/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/lsinv/lsinventory2011-05-03_11-41-34AM.txt
    Installed Top-level Products (2):
    Oracle Database 10g 10.2.0.1.0
    Oracle Database 10g Release 2 Patch Set 4 10.2.0.5.0
    There are 2 products installed in this Oracle Home.
    Interim patches (1) :
    Patch 10248542 : applied on Tue May 03 07:32:29 BST 2011
    Unique Patch ID: 13292123
    Created on 25 Dec 2010, 23:11:24 hrs PST8PDT
    Bugs fixed:
    6402302, 9713537, 8350262, 9949948, 8394351, 10327179, 8546356, 9711859
    9714832, 9952230, 10248542, 8544696, 9963497, 9772888, 8664189, 10249537
    7519406, 9952270, 8277300, 9726739
    OPatch succeeded.

    Pl post the output of view DBA_REGISTRY_HISTORY - see MOS Doc 605795.1 (Introduction To Oracle Database catbundle.sql)
    Was the database created using DBCA or manually using scripts ?
    Srini

  • ERROR in creating a Physical Standby Database

    Hello all,
    I am using a Windows Vista O/S and Oracle 10g Enterprise Edition. Both my primary and standby are on the same host. Created standby instance using oradim.
    I have followed instruction in the documentation and created a manual standby database.
    primary database is 'orcl'
    standby database is 'stby'
    My primary archives is not being copied to the the stby location as confirmed by an error shown:
    SQL> select dest_name, status from v$archive_dest_status
    DEST_NAME
    STATUS
    LOG_ARCHIVE_DEST_1
    VALID
    LOG_ARCHIVE_DEST_2
    ERROR
    Also my standby does not open in read only mode, error:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    ERROR at line 1:
    ORA-01153: an incompatible media recovery is active
    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
    I have copied both my prim and stby init.ora here for your reference
    PRIMARY INIT
    ============================================
    orcl.__db_cache_size=394264576
    orcl.__java_pool_size=20971520
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=184549376
    orcl.__streams_pool_size=0
    *.audit_file_dest='E:\oracle\product\10.2.0\admin\orcl\adump'
    *.background_dump_dest='E:\oracle\product\10.2.0\admin\orcl\bdump'
    *.compatible='10.2.0.3.0'
    *.control_files='E:\oracle\product\10.2.0\oradata\orcl\control01.ctl'
    *.core_dump_dest='E:\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_size=2147483648
    *.db_recovery_file_dest='E:\oracle\product\10.2.0\flash_recovery_area'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.nls_language='ENGLISH'
    *.nls_territory='UNITED KINGDOM'
    *.open_cursors=300
    *.pga_aggregate_target=203423744
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=611319808
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='E:\oracle\product\10.2.0\admin\orcl\udump'
    *.standby_file_management=AUTO
    *.log_archive_dest_1='location=E:\oracle\product\10.2.0\flash_recovery_area\orcl\archivelog valid_for=(all_logfiles,primary_role) db_unique_name=orcl'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_2='SERVICE=stby LGWR ASYNC valid_for=(online_logfiles,primary_role) db_unique_name=stby'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.db_file_name_convert='orcl','stby'
    *.fal_client='orcl'
    *.fal_server='stby'
    *.db_file_name_convert='E:\oracle\product\10.2.0\oradata\stby', 'E:\oracle\product\10.2.0\oradata\orcl'
    *.log_file_name_convert='E:\oracle\product\10.2.0\oradata\stby', 'E:\oracle\product\10.2.0\oradata\orcl'
    *.standby_file_management=AUTO
    ======================================
    STANDBY INIT.ora
    stby.__db_cache_size=423624704
    stby.__java_pool_size=4194304
    tby.__large_pool_size=4194304
    stby.__large_pool_size=4194304
    stby.__shared_pool_size=171966464
    stby.__streams_pool_size=0
    *.audit_file_dest='E:\oracle\product\10.2.0\admin\stby\adump'
    *.background_dump_dest='E:\oracle\product\10.2.0\admin\stby\bdump'
    *.compatible='10.2.0.3.0'
    *.control_files='E:\oracle\product\10.2.0\oradata\stby\CONTROL_SB01.CTL'
    *.core_dump_dest='E:\oracle\product\10.2.0\admin\stby\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='orcl','stby'
    *.db_name='orcl'
    *.db_recovery_file_dest_size=2147483648
    *.db_recovery_file_dest='E:\oracle\product\10.2.0\flash_recovery_area\STBY'
    *.db_unique_name='stby'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.fal_client='stby'
    *.fal_server='orcl'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.log_archive_dest_1='location=E:\oracle\product\10.2.0\flash_recovery_area\stby valid_for=(all_logfiles,primary_role) db_unique_name=stby'
    *.log_archive_dest_2='SERVICE=stby 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_file_name_convert='E:\oracle\product\10.2.0\oradata\orcl','E:\oracle\product\10.2.0\oradata\stby'
    *.nls_language='ENGLISH'
    *.nls_territory='UNITED KINGDOM'
    *.open_cursors=300
    *.pga_aggregate_target=203423744
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=611319808
    *.standby_archive_dest='USE_DB_RECOVERY_FILE_DEST'
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='E:\oracle\product\10.2.0\admin\stby\udump'
    =================================================
    Any help would be much appreciated. Apologies for my ignorance!
    Thanks!
    null
    null

    OK that solves part of the problem.
    Now this is very strange error I am getting. The path it looks to recover from archive is not right, it should point as per my actual archive log dest. See below.
    Standby:
    =================
    SQL> alter database open;
    alter database open
    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: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SYSTEM01.DBF'
    SQL> recover standby database until cancel;
    ORA-00279: change 619067 generated at 06/22/2008 13:20:14 needed for thread 1
    ORA-00289: suggestion :
    E:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00006_0658028298.001
    ORA-00280: change 619067 for thread 1 is in sequence #6
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    'E:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00006_0658028298.001'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SYSTEM01.DBF'
    ==================================================
    Why is not pointing to the destination below, where the above archives reside??
    =====================================
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination E:\oracle\product\10.2.0\flash_recovery_area\stby
    Oldest online log sequence 12
    Next log sequence to archive 0
    Current log sequence 14
    =================

  • ORA-10458: standby database requires recovery

    hi
    kindly help me... i got error when standby open in read only mode
    SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
    Copyright (c) 1982, 2011, Oracle. All rights reserved.
    Connected to an idle instance.
    SQL> startup mount
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.
    Total System Global Area 5344731136 bytes
    Fixed Size 2237776 bytes
    Variable Size 1275071152 bytes
    Database Buffers 4060086272 bytes
    Redo Buffers 7335936 bytes
    Database mounted.
    SQL> Alter Database Recover Managed Standby Database Disconnect;
    Database altered.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Database altered.
    SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 22 was not restored from a sufficiently old backup
    ORA-01110: data file 22: '/archive/data/undo01.dbf'

    hi CKPT
    I executed the action plan as you recommend and got below information;
    SQL> recover standby database;
    ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
    thread 1
    ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
    ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    '/archive/PROD_1_750568044_45400.ARC'
    ORA-00310: archived log contains sequence 45400; sequence 45027 required
    ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 22 was not restored from a sufficiently old backup
    ORA-01110: data file 22: '/archive/data/undo01.dbf'
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01666: control file is for a standby database
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    ---------------------------------- and some other activity but still not found any solution-------------
    RMAN> recover database until sequence
    2> 45026;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:42:47
    RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
    RMAN> recover database until sequence 45027;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:42:59
    RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
    RMAN> recover database until sequence 45025;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:43:09
    RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
    ORA-01666: control file is for a standby database

  • Opening a Standby Database in Read-Only mode

    Is there anyway to open a Standby database up to date as of a certain time? I'm currently using the 2 commands to get close to the time required.
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Such as, similar to this? RECOVER DATABASE UNTIL TIME '2012-01-25:15:00:00';
    We're on 11.1.0.7, which I'm currently very unhappy with.
    Thanks for any help, as my google-fu hasn't worked today.
    James

    Maybe
    I did a quick test :
    8:42 open the databases and start recovery
    8:43 check status from primary
    Shows sequence 75
    and "TO STANDBY" for switchover status
    Did log switches at 8:44, 8:45, and 8:46
    8:50
    SQL> alter database recover managed standby database cancel;
    SQL> RECOVER STANDBY DATABASE UNTIL TIME ' 2012-01-25:20:43:00';
    Media recovery complete.
    SQL>
    8:52
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    Check status
    TO STANDBY and sequence 78Still need to check alert logs and do another log switch. It checks out so the quick test works.
    However the quick test is incomplete since there was no before and after data in the test and the time period was very short.
    Andy may be right, but I would test, test test. ( if you do please let us know the results )
    Thanks Andy!
    Best Regards
    mseberg
    Later
    After sleeping on this I decided my first thought is probably correct. You cannot go back in time and still be in sync. While the test statement did not error or produce any alert log entries, it probably did nothing. Oracle is smart enough to know you cannot have your Cake and eat it too.

  • Cannot open standby database in read only....

    i do the following procedure on my standby database
    ORACLE 9.2.0.7
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 538412112 bytes
    Fixed Size 742480 bytes
    Variable Size 402653184 bytes
    Database Buffers 134217728 bytes
    Redo Buffers 798720 bytes
    SQL> lter database mount standby database;
    SP2-0734: unknown command beginning "lter datab..." - rest of line ignored.
    SQL> alter database mount standby database;
    Database altered.
    SQL> SQL> recover standby database until cancel;
    ORA-00279: change 4274363673 generated at 09/18/2006 11:25:08 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9135.arc
    ORA-00280: change 4274363673 for thread 1 is in sequence #9135
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 4275275613 generated at 09/18/2006 14:03:09 needed for thread
    1
    ORA-00289: suggestion : /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ORA-00280: change 4275275613 for thread 1 is in sequence #9136
    ORA-00278: log file '/u12/oradata/dbadmon/arch/dbadmon9135.arc' no longer
    needed for this recovery
    ORA-00308: cannot open archived log '/u12/oradata/dbadmon/arch/dbadmon9136.arc'
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    THEN i check in the alert...
    Errors in file /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc:
    ORA-00704: bootstrap process failure
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Mon Sep 18 13:59:16 2006
    Error 704 happened during db open, shutting down database
    USER: terminating instance due to error 704
    Instance terminated by USER, pid = 24028
    ORA-1092 signalled during: alter database open read only...
    followed by the trace file...
    /u00/oracle/admin/dbadmon/udump/dbadmon_ora_24028.trc
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    ORACLE_HOME = /u00/oracle/product/9.2.0.1
    System name: AIX
    Node name: eserver1
    Release: 1
    Version: 5
    Machine: 000651FA4C00
    Instance name: dbadmon
    Redo thread mounted by this instance: 1
    Oracle process number: 14
    Unix process pid: 24028, image: oracle@eserver1 (TNS V1-V3)
    *** SESSION ID:(11.1) 2006-09-18 13:58:57.859
    Start recovery at thread 1 ckpt scn 4274363673 logseq 9135 block 2
    *** 2006-09-18 13:59:00.215
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9135.arc
    *** 2006-09-18 13:59:11.868
    Media Recovery Log /u12/oradata/dbadmon/arch/dbadmon9136.arc
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 27062Kb in 13.99s => 1.86 Mb/sec
    Longest record: 8Kb, moves: 22/97639 (0%)
    Change moves: 43706/193539 (22%), moved: 4Mb
    *** 2006-09-18 13:59:14.688
    ksedmp: internal or fatal error
    ORA-00600: internal error code, arguments: [2652], [76], [76], [0], [0], [787456], [], []
    Current SQL statement for this session:
    select /*+ rule */ name,file#,block#,status$,user#,undosqn,xactsqn,scnbas,scnwrp,DECODE(inst#,0,NULL,inst#),ts#,spare1 from undo$
    where us#=:1
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp+0148 bl ksedst 1029170CC ?
    ksfdmp+0018 bl 01FD771C
    kgeriv+0118 bl _ptrgl
    kgesiv+0080 bl kgeriv FFFFFFFFFFEBEF0 ? 080000000 ?
    101A6C640 ? 000000000 ?
    FFFFFFFFFFEBE70 ?
    ksesic5+005c bl kgesiv 70000000E517A78 ?
    70000000E517748 ?
    Can anyone gie me a hand please???
    Thanks in advance.

    Doc ID: Note:1038418.6
    Please check permissions on dump desitnation directory.
    Also check if dual table is present.

  • Archive apply issue for standby database in Standard Edition.

    We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
    We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
    alter database recover managed standby database disconnect from session;
    ======================================================================================
    This is the status:
    SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
    OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
    MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

    The DB version is 10.2.0.5
    I can do this to apply at standby DB:
    SQL> set autorecovery on
    SQL> recover standby database;
    Then I tried to run this to leave the session:
    alter database recover managed standby database disconnect from session;
    Do not seen any apply.
    =============================
    Here is the last lines of alert log:
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
    Clearing online log 1 of thread 1 sequence number 10158
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Thu Sep 06 15:08:34 EDT 2012
    Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
    Clearing online redo logfile 1 complete
    Media Recovery Waiting for thread 1 sequence 10166
    Thu Sep 06 15:08:35 EDT 2012
    Completed: alter database recover managed standby database disconnect from session
    ======
    We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
    Thanks!

  • Recover standby database

    Our primary linux 10g db is in standard edition and we would like to manually create a standby database
    After copying the control and datafiles from primary to standby database, started the standby instance ..
    SQL> startup nomount pfile=/path/to/pfile/initSID.standby
    SQL> alter database mount standby database;
    SQL> recover standby database;
    ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
    ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
    ORA-00280: change 2342934 for thread 1 is in sequence #833
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00308: cannot open archived log
    '/opt/oracle/arch/SID/1_833_682861383.arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
    How do I resolve this problem? Log sequence 833 is the current log on the primary db, archive log haven't been written yet. When I try to "alter database open read only" on the standby db, I get an error "ORA-01156: recovery in progress may need access to file".
    I then went back to my primary database, which already had another log switch to 834, log 833 is now available, I then moved that archive log file to the standby db. Try to recover standby database again, but still got errors..
    SQL> startup nomount pfile=/path/to/pfile/initSID.standby
    SQL> alter database mount standby database;
    SQL> recover standby database;
    ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
    ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
    ORA-00280: change 2342934 for thread 1 is in sequence #833
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00317: file type 0 in header is not log file
    ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
    SQL> alter database open read only;
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
    Would something please explain this to me? What am I doing wrong? Thanks in advance.

    I copied the missing archive log over to standby db, still got the same error.
    1) SQL> recover standby database;
    ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
    ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
    ORA-00280: change 2342934 for thread 1 is in sequence #833
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00317: file type 0 in header is not log file
    ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
    I also tried..
    2) SQL> recover standby database using backup controlfile until cancel;
    ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
    ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
    ORA-00280: change 2342934 for thread 1 is in sequence #833
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00317: file type 0 in header is not log file
    ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
    Edited by: user10427867 on Aug 28, 2009 5:56 AM

  • Standby Database Creation problem

    Hi,
    I have setup Standby Database for our Primary DAtabae,
    I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
    SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
    ORACLE instance started.
    Total System Global Area 730931140 bytes
    Fixed Size 454596 bytes
    Variable Size 285212672 bytes
    Database Buffers 444596224 bytes
    Redo Buffers 667648 bytes
    SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
    Database altered.
    SQL> RECOVER STANDBY DATABASE;
    ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
    for threa
    1
    ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
    ORA-00280: change 7990686470 for thread 1 is in sequence #7032
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [3020], [8388681], [1],
    [7032],
    [137367], [16], [], []
    ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
    ORA-10564: tablespace UNDOTBS1
    ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
    ORA-10560: block type 'KTU SMU HEADER BLOCK'
    ORA-01112: media recovery not started
    Ramesh
    pls mail me : [email protected]
    +91 080 9341018616

    Hi,
    I have setup Standby Database for our Primary DAtabae,
    I am facing probel while applying redo logs, if somebody nows the solution, Please help me.
    SQL> startup nomount PFILE='E:\oracle\admin\fno\pfile\init.ora';
    ORACLE instance started.
    Total System Global Area 730931140 bytes
    Fixed Size 454596 bytes
    Variable Size 285212672 bytes
    Database Buffers 444596224 bytes
    Redo Buffers 667648 bytes
    SQL> ALTER DATABASE MOUNT STANDBY DATABASE;
    Database altered.
    SQL> RECOVER STANDBY DATABASE;
    ORA-00279: change 7990686470 generated at 04/01/2006 15:53:57 needed
    for threa
    1
    ORA-00289: suggestion : F:\ORACLE\ORADATA\FNO\ARCH\LOG_17032.ARC
    ORA-00280: change 7990686470 for thread 1 is in sequence #7032
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    AUTO
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [3020], [8388681], [1],
    [7032],
    [137367], [16], [], []
    ORA-10567: Redo is inconsistent with data block (file# 2, block# 73)
    ORA-10564: tablespace UNDOTBS1
    ORA-01110: data file 2: 'G:\ORACLE\ORADATA\FNO\UNDOTBS01.DBF'
    ORA-10560: block type 'KTU SMU HEADER BLOCK'
    ORA-01112: media recovery not started
    Ramesh
    pls mail me : [email protected]
    +91 080 9341018616

  • Auto specified any value after ran RECOVER STANDBY DATABASE;

    Dear all,
    When i ran the RECOVER STANDBY DATABASE command.It 's will prompt as
    below :
    SQL> RECOVER STANDBY DATABASE;
    ORA-00279: change 302927 generated at 09/10/2007 14:08:24 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\DB817\ARCHIVE\DB817T001S00021.ARC
    ORA-00280: change 302927 for thread 1 is in sequence #21
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Is there anyway to force specified "AUTO" automatically ?
    Because i will to create a scripts file for run automatic .
    Thanks for advance !
    Chara

    ORA-00289: suggestion : D:\ORACLE\ORADATA\DB817\ARCHIVE\DB817T001S00021.ARCFirst check if the required Archive / Redo log is present on your system under the directory "D:\ORACLE\ORADATA\DB817\ARCHIVE".
    For automatic recovery use:
    ALTER DATABASE RECOVER AUTOMATIC STANDBY DATABASE;
    or
    RECOVER AUTOMATIC STANDBY DATABASE;
    Cheers!

  • Restore standby database 10gR2 after crash

    The RMAN do a full backup of the physical standby of the DataGuard 10gR2 everyday.
    If the standby was dead, disks corrupted, and replaced with a new server.
    Can we restore the standby from the RMAN backup, apply the archivelogs or we have re-create the standby db from the primary ?
    If possible to restore the standby from the RMAN backup, what are the procedure exactly ?
    Is it like this:
         RMAN>     Startup force nomount;
         RMAN>     Restore spfile;
         RMAN>     Restore controlfile;
         RMAN>     Shutdown
         RMAN>     Startup mount
         RMAN>     Restore database
         SQL> Recover standby database until cancel;
    ## to start Redo Apply
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

    user565394 wrote:
    The RMAN backup of the standby db is not obsolete and the archivelogs are still available for the last 30 dayson the RMAN backup.
    I believe there is no need to re-create the standby db from the primary because the RMAN backup is still valid so it's must be possible to get the standby db back from the RMAN. If anyone who has experience and could confirm this with the procedure. That would be great.Why not test it by your own? Create a standby database and practice. You can check my video tutorial on creating standby database:
    http://kamranagayev.wordpress.com/2010/06/25/rman-video-tutorial-series-creating-duplicate-and-standby-database-using-rman/
    Moreover, read the "Backing Up a Standby Database with RMAN" of the following documentation:
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmbackp.htm#445993
    Use the RMAN BACKUP command to back up the standby database. A backup of the standby database is exactly the same as a backup of the primary database, except that the backup takes place on the standby site. The primary database has no influence on the backup of the standby database. Note that when you connect to the standby database to perform the backup, you connect using the TARGET keyword and not the AUXILIARY keyword.
    Whether the standby database backup is consistent or inconsistent depends on the state of the standby database when the backup is made. Only a consistent backup can be restored without performing media recovery.

  • Standby Database gives error ORA-03113:ORA-03114

    Hi
    I am using oracle 9iR2 on standby database when i recover it return errors like
    SQL> recover standby database;
    ORA-00279: change 8209765386 generated at 07/18/2008 12:10:41 needed for thread
    1
    ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
    ORA-00280: change 8209765386 for thread 1 is in sequence #86548
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 8209782309 generated at 07/18/2008 12:22:05 needed for thread
    1
    ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
    ORA-00280: change 8209782309 for thread 1 is in sequence #86549
    ORA-00278: log file 'J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC' no
    longer needed for this recovery
    ORA-03113: end-of-file on communication channel
    ORA-03114: not connected to ORACLE
    Alert log display
    Starting datafile 1 recovery in thread 1 sequence 86551
    Datafile 1: 'E:\ORANT\ORADATA\APR1\SYSTEM01.DBF'
    Starting datafile 3 recovery in thread 1 sequence 86551
    Datafile 3: 'E:\ORANT\ORADATA\APR1\CWMLITE01.DBF'
    Starting datafile 4 recovery in thread 1 sequence 86551
    Datafile 4: 'E:\ORANT\ORADATA\APR1\DRSYS01.DBF'
    Starting datafile 5 recovery in thread 1 sequence 86551
    Datafile 5: 'E:\ORANT\ORADATA\APR1\EXAMPLE01.DBF'
    Starting datafile 6 recovery in thread 1 sequence 86551
    Datafile 6: 'E:\ORANT\ORADATA\APR1\INDX01.DBF'
    Starting datafile 7 recovery in thread 1 sequence 86551
    Datafile 7: 'E:\ORANT\ORADATA\APR1\ODM01.DBF'
    Starting datafile 8 recovery in thread 1 sequence 86551
    Datafile 8: 'E:\ORANT\ORADATA\APR1\TOOLS01.DBF'
    Starting datafile 9 recovery in thread 1 sequence 86551
    Datafile 9: 'J:\ORACLE\ORADATA\APR1\USERS01.DBF'
    Starting datafile 10 recovery in thread 1 sequence 86551
    Datafile 10: 'E:\ORANT\ORADATA\APR1\XDB01.DBF'
    Starting datafile 11 recovery in thread 1 sequence 86551
    Datafile 11: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_E.DBF'
    Starting datafile 12 recovery in thread 1 sequence 86549
    Datafile 12: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_C.DBF'
    Starting datafile 13 recovery in thread 1 sequence 86550
    Datafile 13: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_D.DBF'
    Starting datafile 14 recovery in thread 1 sequence 86550
    Datafile 14: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_A.DBF'
    Starting datafile 15 recovery in thread 1 sequence 86548
    Datafile 15: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_B.DBF'
    Starting datafile 16 recovery in thread 1 sequence 86550
    Datafile 16: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_A.DBF'
    Starting datafile 17 recovery in thread 1 sequence 86550
    Datafile 17: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_B.DBF'
    Starting datafile 18 recovery in thread 1 sequence 86550
    Datafile 18: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_A.DBF'
    Starting datafile 19 recovery in thread 1 sequence 86549
    Datafile 19: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_B.DBF'
    Starting datafile 20 recovery in thread 1 sequence 86549
    Datafile 20: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_C.DBF'
    Starting datafile 25 recovery in thread 1 sequence 86550
    Datafile 25: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_A.DBF'
    Starting datafile 26 recovery in thread 1 sequence 86550
    Datafile 26: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_B.DBF'
    Starting datafile 27 recovery in thread 1 sequence 86550
    Datafile 27: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_C.DBF'
    Starting datafile 28 recovery in thread 1 sequence 86550
    Datafile 28: 'J:\ORACLE\ORADATA\APR1\APR_MVIEWS_A.DBF'
    Starting datafile 29 recovery in thread 1 sequence 86550
    Datafile 29: 'J:\ORACLE\ORADATA\APR1\BLOB_A.DBF'
    Starting datafile 30 recovery in thread 1 sequence 86549
    Datafile 30: 'J:\ORACLE\ORADATA\APR1\HR_DATA1_A.DBF'
    Starting datafile 31 recovery in thread 1 sequence 86548
    Datafile 31: 'J:\ORACLE\ORADATA\APR1\HR_DATA2_A.DBF'
    Starting datafile 32 recovery in thread 1 sequence 86550
    Datafile 32: 'J:\ORACLE\ORADATA\APR1\HR_INDX1_A.DBF'
    Starting datafile 33 recovery in thread 1 sequence 86550
    Datafile 33: 'J:\ORACLE\ORADATA\APR1\HR_INDX2_A.DBF'
    Starting datafile 34 recovery in thread 1 sequence 86548
    Datafile 34: 'J:\ORACLE\ORADATA\APR1\INVENTORY_A.DBF'
    Starting datafile 35 recovery in thread 1 sequence 86550
    Datafile 35: 'J:\ORACLE\ORADATA\APR1\INVENTORY_INDX_A.DBF'
    Starting datafile 36 recovery in thread 1 sequence 86550
    Datafile 36: 'E:\ORANT\ORADATA\APR1\SAMPLE_DATA1_A.DBF'
    Starting datafile 37 recovery in thread 1 sequence 86550
    Datafile 37: 'J:\ORACLE\ORADATA\APR1\VMS_DATA1_A.DBF'
    Starting datafile 38 recovery in thread 1 sequence 86550
    Datafile 38: 'J:\ORACLE\ORADATA\APR1\APR_MMS_A.DBF'
    Starting datafile 39 recovery in thread 1 sequence 86550
    Datafile 39: 'J:\ORACLE\ORADATA\APR1\AUDIT_DATA_A.DBF'
    Starting datafile 40 recovery in thread 1 sequence 86549
    Datafile 40: 'J:\ORACLE\ORADATA\APR1\UNDOTBS.DBF'
    Starting datafile 41 recovery in thread 1 sequence 86550
    Datafile 41: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_C.DBF'
    Starting datafile 42 recovery in thread 1 sequence 86549
    Datafile 42: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_E.DBF'
    Starting datafile 43 recovery in thread 1 sequence 86548
    Datafile 43: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_C.DBF'
    Starting datafile 44 recovery in thread 1 sequence 86550
    Datafile 44: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_E.DBF'
    Starting datafile 46 recovery in thread 1 sequence 86550
    Datafile 46: 'E:\ORANT\ORADATA\APR1\SYSTEM02.DBF'
    Starting datafile 47 recovery in thread 1 sequence 86550
    Datafile 47: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_A.DBF'
    Starting datafile 48 recovery in thread 1 sequence 86549
    Datafile 48: 'J:\ORACLE\ORADATA\APR1\APR_DATA4.DBF'
    Starting datafile 49 recovery in thread 1 sequence 86550
    Datafile 49: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_A.DBF'
    Starting datafile 50 recovery in thread 1 sequence 86548
    Datafile 50: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_B.DBF'
    Starting datafile 51 recovery in thread 1 sequence 86550
    Datafile 51: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_B.DBF'
    Starting datafile 52 recovery in thread 1 sequence 86550
    Datafile 52: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_A.DBF'
    Starting datafile 53 recovery in thread 1 sequence 86550
    Datafile 53: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_B.DBF'
    Starting datafile 54 recovery in thread 1 sequence 86550
    Datafile 54: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_C.DBF'
    Starting datafile 55 recovery in thread 1 sequence 86550
    Datafile 55: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_D.DBF'
    Starting datafile 56 recovery in thread 1 sequence 86549
    Datafile 56: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_C.DBF'
    Starting datafile 57 recovery in thread 1 sequence 86550
    Datafile 57: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_F.DBF'
    Starting datafile 58 recovery in thread 1 sequence 86550
    Datafile 58: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_A.DBF'
    Starting datafile 59 recovery in thread 1 sequence 86548
    Datafile 59: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_B.DBF'
    Starting datafile 60 recovery in thread 1 sequence 86549
    Datafile 60: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_C.DBF'
    Starting datafile 61 recovery in thread 1 sequence 86549
    Datafile 61: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_D.DBF'
    Starting datafile 62 recovery in thread 1 sequence 86550
    Datafile 62: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_A.DBF'
    Starting datafile 63 recovery in thread 1 sequence 86550
    Datafile 63: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_B.DBF'
    Starting datafile 64 recovery in thread 1 sequence 86550
    Datafile 64: 'E:\ORANT\ORADATA\APR1\USERS01_A.DBF'
    Starting datafile 65 recovery in thread 1 sequence 86550
    Datafile 65: 'J:\ORACLE\ORADATA\APR1\GMT1_DATA.DBF'
    Starting datafile 66 recovery in thread 1 sequence 86548
    Datafile 66: 'J:\ORACLE\ORADATA\APR1\GMT1_INDX.DBF'
    Starting datafile 67 recovery in thread 1 sequence 86550
    Datafile 67: 'J:\ORACLE\ORADATA\APR1\APR_DATA7.DBF'
    Starting datafile 68 recovery in thread 1 sequence 86550
    Datafile 68: 'J:\ORACLE\ORADATA\APR1\APR_INDX7A.ORA'
    Starting datafile 69 recovery in thread 1 sequence 86550
    Datafile 69: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_A.DBF'
    Starting datafile 70 recovery in thread 1 sequence 86550
    Datafile 70: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_B.DBF'
    Media Recovery Log
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Jul 23 11:26:24 2008
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Wed Jul 23 11:26:24 2008
    Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Jul 23 11:26:25 2008
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
    Wed Jul 23 11:26:53 2008
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    Wed Jul 23 11:26:53 2008
    ARC0: terminating instance due to error 472
    Instance terminated by ARC0, pid = 2100
    Tell me the solution.
    Thanks in advance

    I think your database is not going in begin backup mode...
    this is my standby database server Pratap is there any method to check backup mode .
    Thanks

  • SQL exception during creation of a physical standby database with EM

    Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
    I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
    =============
    2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
    2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
    2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
    2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    =========
    I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
    Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

    Can you please tell me how can i see data gaurd on EM..
    I have oracle 11gR1..i have implemmented primary as well standby database..
    I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
    You got error that means u did it using EM..how can i do it on EM

  • Sql Apply issue in logical standby database--(10.2.0.5.0) x86 platform

    Hi Friends,
    I am getting the following exception in logical standby database at the time of Sql Apply.
    After run the command alter database start logical standby apply sql apply services start but after few second automatically stop and getting following exception.
    alter database start logical standby apply
    Tue May 17 06:42:00 2011
    No optional part
    Attempt to start background Logical Standby process
    LOGSTDBY Parameter: MAX_SERVERS = 20
    LOGSTDBY Parameter: MAX_SGA = 100
    LOGSTDBY Parameter: APPLY_SERVERS = 10
    LSP0 started with pid=30, OS id=4988
    Tue May 17 06:42:00 2011
    Completed: alter database start logical standby apply
    Tue May 17 06:42:00 2011
    LOGSTDBY status: ORA-16111: log mining and apply setting up
    Tue May 17 06:42:00 2011
    LOGMINER: Parameters summary for session# = 1
    LOGMINER: Number of processes = 4, Transaction Chunk Size = 201
    LOGMINER: Memory Size = 100M, Checkpoint interval = 500M
    Tue May 17 06:42:00 2011
    LOGMINER: krvxpsr summary for session# = 1
    LOGMINER: StartScn: 0 (0x0000.00000000)
    LOGMINER: EndScn: 0 (0x0000.00000000)
    LOGMINER: HighConsumedScn: 2660033 (0x0000.002896c1)
    LOGMINER: session_flag 0x1
    LOGMINER: session# = 1, preparer process P002 started with pid=35 OS id=4244
    LOGSTDBY Apply process P014 started with pid=47 OS id=5456
    LOGSTDBY Apply process P010 started with pid=43 OS id=6484
    LOGMINER: session# = 1, reader process P000 started with pid=33 OS id=4732
    Tue May 17 06:42:01 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1417, X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
    Tue May 17 06:42:01 2011
    LOGMINER: Turning ON Log Auto Delete
    Tue May 17 06:42:01 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01417_0748170313.001
    Tue May 17 06:42:01 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1418, X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
    LOGSTDBY Apply process P008 started with pid=41 OS id=4740
    LOGSTDBY Apply process P013 started with pid=46 OS id=7864
    LOGSTDBY Apply process P006 started with pid=39 OS id=5500
    LOGMINER: session# = 1, builder process P001 started with pid=34 OS id=4796
    Tue May 17 06:42:02 2011
    LOGMINER: skipped redo. Thread 1, RBA 0x00058a.00000950.0010, nCV 6
    LOGMINER: op 4.1 (Control File)
    Tue May 17 06:42:02 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01418_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1419, X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01419_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1420, X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01420_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1421, X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
    LOGSTDBY Analyzer process P004 started with pid=37 OS id=5096
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01421_0748170313.001
    LOGSTDBY Apply process P007 started with pid=40 OS id=2760
    Tue May 17 06:42:03 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    LOGSTDBY Apply process P012 started with pid=45 OS id=7152
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1422, X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01422_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1423, X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01423_0748170313.001
    Tue May 17 06:42:03 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1424, X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
    LOGMINER: session# = 1, preparer process P003 started with pid=36 OS id=5468
    Tue May 17 06:42:03 2011
    LOGMINER: End mining logfile: X:\TANVI\ARCHIVE2\ARC01424_0748170313.001
    Tue May 17 06:42:04 2011
    LOGMINER: Begin mining logfile for session 1 thread 1 sequence 1425, X:\TANVI\ARCHIVE2\ARC01425_0748170313.001
    LOGSTDBY Apply process P011 started with pid=44 OS id=6816
    LOGSTDBY Apply process P005 started with pid=38 OS id=5792
    LOGSTDBY Apply process P009 started with pid=42 OS id=752
    Tue May 17 06:42:05 2011
    krvxerpt: Errors detected in process 34, role builder.
    Tue May 17 06:42:05 2011
    krvxmrs: Leaving by exception: 600
    Tue May 17 06:42:05 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    LOGSTDBY status: ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    Tue May 17 06:42:06 2011
    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_lsp0_4988.trc:
    ORA-12801: error signaled in parallel query server P001
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []
    Tue May 17 06:42:06 2011
    LogMiner process death detected
    Tue May 17 06:42:06 2011
    logminer process death detected, exiting logical standby
    LOGSTDBY Analyzer process P004 pid=37 OS id=5096 stopped
    LOGSTDBY Apply process P010 pid=43 OS id=6484 stopped
    LOGSTDBY Apply process P008 pid=41 OS id=4740 stopped
    LOGSTDBY Apply process P012 pid=45 OS id=7152 stopped
    LOGSTDBY Apply process P014 pid=47 OS id=5456 stopped
    LOGSTDBY Apply process P005 pid=38 OS id=5792 stopped
    LOGSTDBY Apply process P006 pid=39 OS id=5500 stopped
    LOGSTDBY Apply process P007 pid=40 OS id=2760 stopped
    LOGSTDBY Apply process P011 pid=44 OS id=6816 stopped
    Tue May 17 06:42:10 2011

    Errors in file x:\oracle\product\10.2.0\admin\tanvi\bdump\tanvi_p001_4796.trc:
    ORA-00600: internal error code, arguments: [krvxbpx20], [1], [1418], [2380], [16], [], [], []submit an SR to ORACLE SUPPORT.
    refer these too
    *ORA-600/ORA-7445 Error Look-up Tool [ID 153788.1]*
    *Bug 6022014: ORA-600 [KRVXBPX20] ON LOGICAL STANDBY*

  • Slow SQL Apply on Logical Standby Database in Oracle10g

    Hi,
    We are using Oracle 10g Logical Standby database in our production farm but whenever there is bulk data load (5-6 GB data) on the primary database, the logical standby seems to be hung. It takes days to apply the 5-6 GB data on the logical standby.
    Can anybody give me some pointers how can I make my SQL Apply fast on the logical standby for bulk data.
    Thanks
    Amit

    Hi there,
    I've a similar problem. I did an insert of 700k on a table. It takes me over 1 1/2 hours to see the data. Notice, I increased the "max_sga" to 300m and "max_servers" to 25" and didn't help the performance at all.
    My version is 10.2.0.3 with the patch 6081550.
    APPLIED_SCN APPLIED_TIME RESTART_SCN RESTART_TIME LATEST_SCN LATEST_TIME MINING_SCN MINING_TIME
    1015618 29-NOV-2007 18:28:51 1009600 29-NOV-2007 18:28:51 1017519 29-NOV-2007 19:54:07 1015656 29-NOV-2007 18:32:14

Maybe you are looking for