Duplicate standby asm controlfile parameter

Hi
I want to create a standby database by using duplicate standby command.
Both primary and standby databases are on asm.
How should I set controlfile parameter in standby database spfile before initiating duplicate for standby clause ?
Primary:
SQL> show parameter control
NAME                                 TYPE        VALUE
control_files                        string      +DATA/orcl/controlfile/current.260.769439087Should I set the same controlfile parameter for standby spfile or should I just set "+DATA" ?
I tried setting just "+DATA", however during duplicate, the instance couldnt create a controlfile in ASM.

http://docs.oracle.com/cd/E11882_01/server.112/e25608/scenarios.htm#SBYDB4897 says:
>
If the primary database is configured to use OMF, then Oracle recommends that the standby database be configured to use OMF, too. To do this, set the DB_CREATE_FILE_DEST and DB_CREATE_ONLINE_LOG_DEST_n initialization parameters to appropriate values. Maintenance and future role transitions are simplified if the same disk group names are used for both the primary and standby databases.
>
So try to not set CONTROL_FILES parameter and set only DB_CREATE_FILE_DEST parameter:
DB_CREATE_FILE_DEST='+DATA';

Similar Messages

  • Creation of standby logical controlfile

    can anybody let me know how to create standby logical controlfile....
    i know how to create physical standby control file....
    when i created a logical standby controlfile and after mounting the logical standby database, i got an erorr database name is not a standby database...

    Hi,
    DB VERSION matters here!!
    apart from that just look at this...
    For 9.2
    On the primary database, create a backup copy of the control file for the standby database:
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO
    2> '/disk1/oracle/oradata/payroll/standby/payroll3.ctl';
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ls.htm#1060804
    and If possible Please search google or this forums!
    Regards!

  • Chanege ASM instance parameter

    PLease help ,
    How to change ASM instance parameter MEMORY_TARGET ?
    SQL> show parameter spfile
    NAME TYPE VALUE
    spfile string
    SQL>
    $ asmcmd spget
    +OCR_VOTE/c1se/asmparameterfile/registry.253.812471763
    SQL> alter system set MEMORY_TARGET=800M scope=both ;
    alter system set MEMORY_TARGET=800M scope=both
    ERROR at line 1:
    ORA-32001: write to SPFILE requested but no SPFILE is in use
    How to modify Oracle ASM instance parameters ?
    Thank's

    I think your response is not correct. The ASM instance will require a parameter file, just like any other Oracle instance. As of 11gR2, the ASM spfile is stored automatically in the first disk group created during the Grid Infrastructure installation.
    The trick is that ASM can read the spfile stored on ASM disks through the css cluster daemon and reading the ASM device header. People here in the forum and on the Internet have written good and detailed information about this, for instance:
    Where is my Oracle ASM Instance spfile
    http://aychin.wordpress.com/2011/01/22/oracle-11gr2-asm-spfile-eng/

  • Duplicate from ASM

    Hi all,
    I have had a request to do a duplicate from ASM on Solaris x86-64 (Little Endian) to a Windows 32 bit server (also Little Endian). I am thinking this would be a two step process.
    1. Take a rman 'backup as copy' then restore to a Solaris x86-64 file system.
    2. Then use the rman 'CONVERT DATABASE ON TARGET PLATFORM' to create the scripts to do the conversion to Windows 32-bit. Also run utlirp & utlrp to convert wordsize at the end of it.
    Has anybody done this before?
    Cheers
    VicC

    Hi,
    I assume that you are using database 10g or higher. One way to achieve this is to
    1. Create a database on Windows same Oracle version as on Solaris.
    2. use impdp to plug the tablespaces from Solaris.
    Regards,
    Edited by: gjilevski1 on Aug 13, 2010 7:40 AM

  • Error, creating physical standby ASM to ASM

    Greetings !!!!!!
    I am trying to create a single instance physical standby for 2 node RAC. I am getting the following error. The backup of standby controlfile exist and even RMAN can see it. Can someone tell me what I am missing?
    Regards
    dg01:/u01/app/oracle>rman
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun May 11 01:53:39 2008
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN> connect target sys/xxxx@RACDB
    connected to target database: RACDB (DBID=633531597)
    RMAN> connect auxiliary /
    connected to auxiliary database: RACDB (not mounted)
    RMAN> duplicate target database for standby dorecover;
    Starting Duplicate Db at 2008-05-11 01:54:36
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=156 devtype=DISK
    contents of Memory Script:
    set until scn 8620555;
    restore clone standby controlfile;
    sql clone 'alter database mount standby database';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 2008-05-11 01:54:38
    using channel ORA_AUX_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/11/2008 01:54:38
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    RMAN> list backup of controlfile;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    156 Full 15.11M DISK 00:00:11 2008-05-10 15:47:47
    BP Key: 156 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154736
    Piece Name: /software/backup/new_db_backup/c-633531597-20080510-09
    Control File Included: Ckp SCN: 8620566 Ckp time: 2008-05-10 15:47:36
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    157 Full 15.08M DISK 00:00:07 2008-05-10 15:48:08
    BP Key: 157 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154801
    Piece Name: +FLASH/racdb/backupset/2008_05_10/ncnnf0_tag20080510t154801_0.385.654494215
    Standby Control File Included: Ckp SCN: 8620602 Ckp time: 2008-05-10 15:48:01
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    158 Full 15.11M DISK 00:00:11 2008-05-10 15:48:20
    BP Key: 158 Status: AVAILABLE Compressed: NO Tag: TAG20080510T154809
    Piece Name: /software/backup/new_db_backup/c-633531597-20080510-0a
    Control File Included: Ckp SCN: 8620608 Ckp time: 2008-05-10 15:48:09
    RMAN>

    Check Metalink Note:466321.1
    -Amit
    http://askoracledba.wordpress.com/

  • ORA-00235 Standby Database Controlfile problem

    Dear fellow dbas,
    I am just starting to become acquainted with high availability and have to solve following problem.
    We have a RAC database with a standby database that is out of sync. In fact the standby database is running in async mode but archived redo logs are not applied.
    They are successfully forwarded from the primary instance to the standby db though. Looking at the alert.log I discovered an ORA-00235 error - control file fixed table inconsistent due to concurrent update.
    As a result of this I have a huge gap between the primary and standby database.
    Can you please give me a step to step tutorial, how I can resolve this issue?
    Any help is appreciated!
    Many thanks,
    Sebastian

    Hello Anand,
    I am using 11.1.0.7.0.
    My standby database is a cluster database as well. I shut both instances down using srvctl and created a standby controlfile from my primary instance, which I copied to the respective locations referred to in the spfile of my dataguard database. Afterwards I started up and issued a ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    The database does not open and the alert.log states ORA-01124 "cannot recover datafile 1 - file is in use or recovery".
    Next, the background media recovery process was shut down.
    What should I do, to get my standby back running?
    Should I place the primary database in backup mode and copy the datafiles to my standby db?
    Afterwards I would create a standby controlfile again and overwrite the standby ones.
    Maybe you assist in pointing at the next steps.
    Many thanks,
    Sebastian

  • Resume a rman duplicate on asm

    Hi folks,
    ASM, 11gr2
    My duplicate job failed after about 20 hours due to a tcp/ip failure to our tsm server.
    I read in the oracle documentation that it is possible to resume the job.
    So I did as described in the documentation and the duplicate was resumed.
    RMAN said "Using previous duplicated file...." for all the files allready restored, and it should only restore the remaining files. About 200Gb.
    But after 5 hours and 350Gb (tsm shows this amount) it is still not finished.
    I am duplicating from asm to asm.
    Why is this happening??
    Is it because I am on ASM fs? The oracle doc said nothing about resume would not work on asm.
    Thanks!

    Hello,
    This is half information, you are using ASM on production but what about Dev serve ASM or NON-ASMr? What's your Oracle version? Prod? Dev?
    Stepwise instructions
    See following Doc ID:  73912.1  : RMAN: Creating a Duplicate Database
    Regards
    Edited by: OrionNet on Mar 1, 2009 11:10 PM

  • How to control ASM related parameter RBAL and ASMB

    Hi,
    I used RMAN to clone a database using rman's "duplicate target database" option. The prdn database's rcat backup on tapes were used. The restore progressed and eventually kept on failing several times.( We tried some options, like executed it when the tape activity was least, created a tempfile for another db in this db's diskgroup, etc.,etc., but all attempts failed. Not every attempt failed at the same stage ). At every failure I found in alert log the following message :
    Wed Jul 19 15:36:19 2006
    NOTE: ASMB process exiting due to lack of ASM file activity
    Wed Jul 19 15:36:20 2006
    Stopping background process RBAL
    Wed Jul 19 15:37:59 2006
    Starting background process ASMB
    ASMB started with pid=16, OS id=4247
    Starting background process RBAL
    RBAL started with pid=17, OS id=4251
    Wed Jul 19 15:38:05 2006
    Errors in file /u03/app/oracle/admin/mydbname/bdump/mydbname_rbal_4251.trc:
    ORA-00600: internal error code, arguments: [kfkLibVersionPreCb01], [], [], [], [], [], [], []
    Wed Jul 19 15:38:05 2006
    Errors in file /u03/app/oracle/admin/mydbname/bdump/mydbname_rbal_4251.trc:
    ORA-00600: internal error code, arguments: [kfkLibVersionPreCb01], [], [], [], [], [], [], []
    Wed Jul 19 15:38:05 2006
    Errors in file /u03/app/oracle/admin/mydbname/udump/mydbname_ora_14773.trc:
    ORA-07445: exception encountered: core dump [kfddsGet()+22] [SIGSEGV] [Address not mapped to object] [0x000000278] [] []
    Wed Jul 19 15:38:05 2006
    Trace dumping is performing id=[cdmp_20060719153805]
    Wed Jul 19 15:39:02 2006
    ERROR: diskgroup MYDBNAME_DG was not mounted
    Wed Jul 19 15:43:51 2006
    From the alert log message it is obvious that those two processes in subject RBAL and ASMB are getting stopped and while getting restarted it is throwing the ORA-600 error. There is hit on metalink for this ORA-600.
    My question is, do we have a way to tell those processes not to stop at first place? If not how to get fix this issue.
    Thanks in advance.
    /KH

    I have never seen this before, I think it a good candidate of having a SR with oracle.
    There is hit on metalink for this ORA-600I think you mean There is NO hit on metalink...
    I couldn't find any
    Daljit Singh

  • Ora-1276 cannot add controlfile - rman duplicate asm database

    Hi,
    I am trying to duplicate an asm database olddb -> asm database dup in the same diskgroup. somehow got error 0ra-1276 Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.
    There is nothing in the asm directory +DISK1/dup/controllfile before I run the rman.
    in the initdup.ora
    control_files=+DISK1,+DISK1 <--- just the disk group, not the file name
    db_name='dup'
    db_file_name_convert=+DISK1,+DISK1/dup
    log_file_name_convert=+DISK1,+DISK1
    Recovery Manager: Release 10.2.0.5.0 - Production on Sat Jun 18 20:58:06 2011
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    RMAN> connect target sys/oracle@OLDDB
    connect auconnected to target database: OLDDB (DBID=1142960293)
    RMAN> xiliary /
    connected to auxiliary database: DUP (not mounted)
    RMAN> duplicate target database to dup
    logfile group 1 ('+DISK1/dup') size 200k ,
    group 2 ('+DISK1') size 200k;
    2> 3>
    Starting Duplicate Db at 2011/06/18 20:58:39
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=153 devtype=DISK
    WARNING: DB_FILE_NAME_CONVERT resulted in invalid ASM names; names changed to diskgroup only.
    contents of Memory Script:
    set until scn 1613638;
    set newname for datafile 1 to
    "+DISK1";
    set newname for datafile 2 to
    "+DISK1";
    set newname for datafile 3 to
    "+DISK1";
    set newname for datafile 4 to
    "+DISK1";
    set newname for datafile 6 to
    "+DISK1";
    restore
    check readonly
    clone database
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 2011/06/18 20:58:42
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to +DISK1
    restoring datafile 00002 to +DISK1
    restoring datafile 00003 to +DISK1
    restoring datafile 00004 to +DISK1
    restoring datafile 00006 to +DISK1
    channel ORA_AUX_DISK_1: reading from backup piece +DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731
    channel ORA_AUX_DISK_1: restored backup piece 1
    piece handle=+DISK1/OLDDB/backupset/2011_05_22/nnndf0_tag20110522t000530_0.1691.751766731 tag=TAG20110522T000530
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:06
    Finished restore at 2011/06/18 20:59:48
    sql statement: CREATE CONTROLFILE REUSE SET DATABASE "DUP" RESETLOGS ARCHIVELOG
    MAXLOGFILES 192
    MAXLOGMEMBERS 3
    MAXDATAFILES 1024
    MAXINSTANCES 32
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1 ( '+DISK1/dup' ) SIZE 200 K ,
    GROUP 2 ( '+DISK1' ) SIZE 200 K
    DATAFILE
    '+DISK1/dup/datafile/system.1674.754174727'
    CHARACTER SET WE8ISO8859P1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 06/18/2011 20:59:48
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.
    RMAN>
    thank you very much for your help.
    thanks
    andrew

    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
    ORA-01276: Cannot add file +DISK1/dup/controlfile/current.1669.754164181.  File has an Oracle Managed Files file name.Are you sure is it running under pfile?
    Ok, connect to auxiliary intance and post
    show parameter db_create
    show parameter control_filesIn your pfile, Have you mentioned single quotes?
    If your database with OMF then if you give it as below. as there is some work around
    Control_files='+DISK1/DUP/controlfile/control01.ctl','+DISK1/DUP/controlfile/control02.ctl'
    Check this too *Ora-1276 Error Recreating The Controlfile When Using +Asm [ID 303187.1]*

  • Standby Database with RMAN on ASM

    Hi,
    I am using redhat Linux AS 4 and my database is 10.2.0.1. This database used ASM for storage of data files, control files, online redo logs. Flash recovery area is also configured in the ASM.
    I want to create a physical standby database on a different machine by using RMAN. Can someone kindly point me to some easy to follow document? I have scoured the oracle docs, but am more confused than ever.
    regards

    Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
    Note: the examples in this document use regular filesystems but the process is the same regardless, ie, in db_file_name_convert use your diskgroup rather than a filesystem (db_file_name_convert=+DG_SOURCE,+DG_TARGET)
    another note to complement the first one:
    Step By Step Guide On Creating Physical Standby Using RMAN Duplicate In ASM Filesystem For ASM Primary [ID 837102.1]
    Edited by: rui_catcuddler on Sep 2, 2010 6:51 AM

  • DB_UNIQUE_NAME vs DB_NAME in standby databases of ASM file systems

    Question : Do we need to have the db_unique_name paramter set differently in standby database compared to db_name in standby .
    Problem we are facing :
    Here is the little background
    Primary Server     : SERVER1
    db_name          : VENKAT
    db_unique_name     : VENKAT
    Standby server     : SERVER2
    db_name          : VENKAT
    db_unique_name     : VENKAT_stb
    Sever          : Linux
    Database Version: 11.20.3
    File system type: ASM ( 11.2.0.3)
    stanby type     : Physical
    Disk group names: Identical on both primary and standby servers
    Data          : +DATA_OP01027_128
    FRA          : +FRA_VENKAT_128
    How datafiles are layed out on primary server:
    sample datafile name location : +DATA_VENKAT_128/VENKAT/datafile/venkat.277.789579565
    How standby was build : using Active duplicte command
    Once we have the standby database build we have the datafiles created under this location
    Sample datafile name location on standby server : +DATA_VENKAT_128/VENKAT_stb/datafile/venkat.280.789579597
    with this we have learnt that the directory VENKAT_stb is getting created in standby ASM off the db_unique_name that
    was given in the database , we have not seen this issue in the normal file system even we are using db_unique_name different that
    the db_name in standby database .
    Can you please help us how we can prevent this situation of having datafiles getting created under differnt direction in standby compared to prod.
    Can you also let us know what impacts we might be having if we don't specify the db_unique_name different than db_name in standby database.
    Hope this explains the problem what we are facing currently .
    What steps i follwed to fix this issues :
    I have db_unique_name set to the same name as db_name and when i did the restore all datafiles are in the identical location to prod standby server .
    Note : We do fully understand the need for having the db_unique_name set different to db_name in standby db in standby and primary db's are residing on the same physical server .
    Thanks
    Venkat

    first of all, this is not an issue or problem
    works as intended
    Question : Do we need to have the db_unique_name paramter set differently in standby database compared to db_name in standby .yes
    Sample datafile name location on standby server : +DATA_VENKAT_128/VENKAT_stb/datafile/venkat.280.789579597
    with this we have learnt that the directory VENKAT_stb is getting created in standby ASM off the db_unique_name that
    was given in the database , we have not seen this issue in the normal file system even we are using db_unique_name different that
    the db_name in standby database .
    Can you please help us how we can prevent this situation of having datafiles getting created under differnt direction in standby compared to prod.well, dont use OMF then
    OMF format for datafiles in ASM is: +DISKGROUP/DB_UNIQUE_NAME/DATAFILE/TABLESPACE_NAME.FILE.INCARNATION
    datafiles will be created this way no matter what you do
    the difference is, that if you dont use OMF, there will be an alias created referencing the file, with the path you gave
    for example:
    OMF:
    create tablespace test size 10M;
    a datafile is created: +DATA_VENKAT_128/VENKAT/DATAFILE/test.280.789581212 (i wrote some random numbers here)
    non-OMF:
    create tablespace test datafile '+DATA_VENKAT_128/dummy/test01.dbf' size 10M;
    what actually happens:
    a datafile is created: +DATA_VENKAT_128/VENKAT/DATAFILE/test.280.789581212 (i wrote some random numbers here)
    and an ASM alias is created: +DATA_VENKAT_128/dummy/test01.dbf
    and this alias is used by the database
    while OMF files have their specified path format, and their path (db_unique_name) and even name (numbers at the end) will change when duplicated, aliases dont necessarily do this
    however this is just extra work and administration, OMF is your friend

  • Standby controlfile

    Hi all,
    I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
    1. shutdown the standby database
    2. on the primary datbase:
    alter database create standby controlfile as 'filesname'
    3. move the control file created in the step 2 to the primary database
    4. startup nomount
    5. alter database mount standby database.
    so far so good, no erros yet. Therefore I try to apply the log:
    6. recover standby database until cancel
    I hit cancel
    and received the following:
    SVRMGR> recover standby database until cancel;
    ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
    ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
    ORA-00280: change 95713083 for thread 1 is in sequence #492
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    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: '/u01/oradata/ORCL/system01.dbf'
    Why this happend? Any suggestion?
    Thank you very much in advance!
    --yc                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Oh,
    I mean move the standby controlfile to the standby database.
    --yc
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Shuet Ying Choi ([email protected]):
    Hi all,
    I have created a standby database and is working propertly. I just drop the redo logs and recreated more and larger redo logs in the primary database. I followed the oracle documentation and try to refresh the standby database controlfile so that it reflects this change:
    1. shutdown the standby database
    2. on the primary datbase:
    alter database create standby controlfile as 'filesname'
    3. move the control file created in the step 2 to the primary database
    4. startup nomount
    5. alter database mount standby database.
    so far so good, no erros yet. Therefore I try to apply the log:
    6. recover standby database until cancel
    I hit cancel
    and received the following:
    SVRMGR> recover standby database until cancel;
    ORA-00279: change 95713083 generated at 02/16/2001 12:34:59 needed for thread 1
    ORA-00289: suggestion : /logs/ORCL/arch/ORCL_1_492.arc
    ORA-00280: change 95713083 for thread 1 is in sequence #492
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    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: '/u01/oradata/ORCL/system01.dbf'
    Why this happend? Any suggestion?
    Thank you very much in advance!
    --yc<HR></BLOCKQUOTE>
    null

  • ASM to non-ASM database duplicate-ORA17503:ksfdopn:2 Failed to open file

    Hi,
    I am trying to duplicate an ASM database in to non-ASM database.
    Having trouble when trying to start the duplicate database, it is looking for the redologs which are there in the ASM diskgroup in the production database, but the duplication database is non-ASM,
    The database version is 10.2.0.4 on HP-UX 11.31
    ORA-00313: open failed for members of log group 11 of thread 1
    ORA-00312: online log 11 thread 1: '+DATADG/orcl/onlinelog/group_11.302.670427231'
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/orcl/onlinelog/group_11.302.670427231
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    Sun Aug 21 14:20:14 2011
    Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_12482.trc:
    ORA-00367: checksum error in log file header
    ORA-00305: log 12 of thread 2 inconsistent; belongs to another database
    ORA-00312: online log 12 thread 2: '/oradbstg/oradata/orcl/redo01.log'
    Sun Aug 21 14:20:14 2011
    RESETLOGS after incomplete recovery UNTIL CHANGE 3632387878
    Resetting resetlogs activation ID 1179611173 (0x464f7025)
    Sun Aug 21 14:20:14 2011
    Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_12482.trc:
    ORA-00313: open failed for members of log group 7 of thread 1
    ORA-00312: online log 7 thread 1: '+DATADG/orcl/onlinelog/group_7.298.670427121'
    ORA-17503: ksfdopn:2 Failed to open file +DATADG/orcl/onlinelog/group_7.298.670427121
    ORA-15001: diskgroup "DATADG" does not exist or is not mounted
    ORA-15077: could not locate ASM instance serving a required diskgroup
    Sun Aug 21 14:20:14 2011
    Errors in file /u01/app/oracle/admin/orcl/udump/orcl_ora_12482.trc:
    ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
    ORA-600 signalled during:  alter database open RESETLOGS...Any help would be appreciated.

    When you are performing this task , is the ASM diskgroup "DATADG" mounted or existed.. try to figure out that first whether the diskgroup is mounted/existed or not .. And also when incomplete recovery is performed oracle creates the online redolog files when you start the db with resetlogs..
    you can go through the following link :
    http://oracleinstance.blogspot.com/2010/08/duplicatecloneconvert-asm-file-system.html
    Cheers!

  • Standby controlfile SCN ahead of datafile SCN

    Hello,
    Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
    Recovery interrupted!
    Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
    Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
    DB (stand-alone): 11.2.0.2
    Platform: Sun SPARC
    Thanks
    aBBy

    Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
    Recovery interrupted!
    Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
    Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
    Are you trying to perform Manual recovery from SQL? like recover standby database?
    Even if controlfile is new and datafiles are older, still you should able to perform recovery , But this will be a valid database to open when SCN's are in SYNC.
    SO perform recovery automated and then check synchronization.
    SQL> alter database recover managed standby database disconnect from session;
    Refer alert log file until it waits as " Media recovery waiting for thread# <no> sequence# <>"
    Then, check SYNC as follows
    Primary:-
    SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
    Standby:-
    SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
    SQL> select thread#, max(sequence#) from v$archived_log where applied='YES' group by thread#;
    Also you can try option of recreating standby controlfile as below from primary
    SQL> alter database create standby controlfile as 'loation';
    & restore it in standby database.

  • RMAN duplicate - instance parameters

    Hello all.
    I want to refresh the test environment with new production backup in oracle database 10g.
    we have standby configured and its in sync with prod. So we took standby database latest backup and going to use to refresh the test environment.
    prod is a 2 node rac and test is also a two node rac.
    prod use different asm disk group and test uses different asm disk group.
    so after taking backup, moved the backups to test environment.
    Took backup of test spfile.
    shut down the test both rac nodes after editing the parameter "cluster_database=false" parameter in spfile.
    i am little confused about the the parameters to be removed and not to be removed in pfile to start the auxiliary instance.
    we can remove parameters related to rac and these parameters also
    cluster_database_instances=2
    *.cluster_database=TRUE
    kindly let me know
    what value i can give for the parameters since the location is different in prod and test and how the duplicate command handle these parameter to duplicate the database
    control_files
    db_create_file_dest=
    db_create_online_log_dest_1
    db_create_online_log_dest_2
    and i am going to use duplicate target database to <aux_db_name>
    Regards

    Pradeep,
      Refresh rac database is not like refresh standalone database. You need to follow below steps
    Step 1)  Take the full backup of production database
                * Backup of database , controlfile and pfile to backup location
                * Comment the all rac related parameters and add change the control_files,db_file_name_convert,log_file_name_convert parameters as per test environment
                * scp all backupfiles to any of the server in test environment
      Step 2)  
                * connect to database which you want to refresh in test env
                * change the cluster_database=false (so that we can start the database exclusively for this instance only)
                * shutdown immediate and startup restrict nomount
                * drop dtabase
      Step 3)
               * Remove the database information from ocr file
                  srvctl remove database -d <db_name>
    Step 4)
              *  startup nomount pfile=<location>
              *  connect to  rman
                   rman auxiliary /
              *  use duplicate command to create a database
    Step 5)
             * shutdown the database and make changes in pfile as remove all comments for all rac related parameters then create spfile from pfile
             * and startup database
             * use srvctl add database -d <db_name>
             * create second instance in second node also

Maybe you are looking for