Standby Database  in Prod

Hi all,
BANNER----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
PL/SQL Release 10.2.0.2.0 - Production
CORE 10.2.0.2.0 Production
TNS for Solaris: Version 10.2.0.2.0 - Production
NLSRTL Version 10.2.0.2.0 - Production
OS Version
SecondaryDB>uname -a
SunOS 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
I am facing issue in Standby Database ,i had done all recovery from RMAN & morover i had used Primary controlfile as a standby controlfile in standby database . evrything is fine ,RFS is working archives are coming from primary to standby ,but the prblm with the MRP Process ,when i m fired the comm
SQL>Recover managed standby database disconnect from session ;
in the alert log file its show below errors:-
Fri Oct 7 09:03:26 2011
Completed: ALTER DATABASE RECOVER managed standby database disconnect from session
Fri Oct 7 09:04:44 2011
RFS[3]: No standby redo logfiles created
Fri Oct 7 09:04:55 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 100032-100131
DBID 3896382872 branch 684626292
FAL[client]: All defined FAL servers have been attempted.
SQL> select * from v$archive_gap;
no rows selected
SQL> select SEQUENCE#,ARCHIVED,APPLIED,STATUS from v$archived_log;
SEQUENCE# ARC APP S
102069 YES NO A
102067 YES NO A
102068 YES NO A
102070 YES NO A
102071 YES NO A
SQL> select process,status from v$managed_standby ;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
ARCH CONNECTED
ARCH CONNECTED
RFS IDLE
RFS IDLE
RFS IDLE
MRP0 WAIT_FOR_GAP
8 rows selected.
SQL> select error from v$archive_dest;
ERROR
11 rows selected.
SQL> select MAx(SEQUENCE#) from v$log_history;
MAX(SEQUENCE#)
102066
SQL>
i don;t know why MRP is not working properly and again & again showing this GAP Squence error .
Please Help me out i am waiting for your helpful answer.
Thanks

yes that 100032 is present in primary but in zip format ,when i extract and go for manul register its give me courputed archive.
after that i used incremental Rman strategy with the SCN . & i applied all process of rman
From Primary
SQL> Select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
102074
SQL>
from Physical Standby
SQL> Select max(sequence#) from v$archived_log where applied='YES' ;
MAX(SEQUENCE#)
SQL>
thanks

Similar Messages

  • Error while creating standby database for ebs prod database

    Hi,
    We are getting error while trying to create a standby database for EBS database by using RMAN DUPLICATE commands,
    Steps followed:
    1.) Backup the primary database (Ebs PROD db). This was done on 12-Mar-2012
    ***RMAN backups are scheduled to run @10:00 pm every night. Flash Recovery Area has been configured and backup is taken at this location
    everyday.
    2.) Tar the backupset, autobackup, archivelogs etc in FRA .... and copy this to the target server (STANDBY).
    *** Copy(oracle rdbms binaries and FRA) completed @12:00AM on 14-Mar-2012
    3.) Tried to create standby database by using RMAN duplicate on 14-Mar-2012
    RMAN> rman sys/sys@PROD auxiliary /
    RMAN> duplicate target database for standby dorecover nofilenamecheck;
    After, some time the RMAN DUPLICATE process errors out with,
    ORA-19563: header validation failed for file
    We are not sure about the cause of this error. While searching in Metalink, we got several notes (ex, 352074.1) but all the causes stated for this error
    are not applicable in our case. We double checked our instance to confirm this.
    We have also found that in PROD database there are 65 datafiles and after the RMAN DUPLICATE errors out in the targer server (STANDBY) the RMAN managed to restore 51 datafiles before erroring out.
    # Please note PROD database was also backed up on 13-Mar-2012. We have a suspicion that backup on 13-Mar may be a possible cause for this error but we are
    not sure.
    Need suggestions if there can be any other possible causes???
    We are in a fix and it would be appreciable if we get some quick suggestions..
    Regards,
    Rupdipt
    Edited by: orarup on Mar 14, 2012 12:29 AM

    When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, its header was not recognized as a valid file header for a file of the indicated type (data file, archived log, or control file) belonging to the current database.
    Kindly Ensure that the correct files are being specified for the copy or backup operation.
    Regs,
    Bhavi Savla.

  • Standby database on different version than prod.

    Is it possible to have a standby database running on a different version of Oracle than the production database?
    In this case I have production DB on the following version:
    7.3.4
    8.1.7.4.0
    9.2.0.4.0
    9.2.0.6.0
    Would it be possible to run the a stand by DB in 10g?

    From the docs posted previously, which you clearly didn't read
    Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition. It is not available with Oracle Database Standard Edition. This means the same release of Oracle Database Enterprise Edition must be installed on the primary database and all standby databases in a Data Guard configuration.
    Rhetorical question: Now what would same release mean?
    Sybrand Bakker
    Senior Oracle DBA

  • Error while trying to open physical standby database - (DATA GUARD)

    Hi Everyone,
    I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
    Primary Database spec: (2 Node Rac on ASM)
    Oracle Version : 10.2.0.3.0
    O/s : HP-UX B.11.23
    Standby Database spec: (Single Node)
    Oracle Version : 10.2.0.3.0
    O/s: HP-UX db01 B.11.23
    Error:
    alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database open
    2 ;
    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: '+DATA/dprod/datafile/system01.dbf'
    Parameters :
    log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
    FOR=(ONLINELOGFILES,PRIMARY_
    ROLE) DB_UNIQUE_NAME=PROD
    remote_archive_enable string true
    fal_client string DPROD
    fal_server string PROD1, PROD2
    Steps tried so far:
    Changed log_archive_dest_2 = DEFER on both the primary nodes
    Standby :
    startup nomount
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    alter database recover managed standby database cancel;
    alter database open/readonly (tried both)
    Same error.
    On Primary:
    SQL> select max(sequence#) from v$log_history;
    MAX(SEQUENCE#)
    55702
    on Standby:
    MAX(SEQUENCE#)
    33289
    Primary Database:
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    55700 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55702 13-JUN-11 13-JUN-11
    60824 rows selected.
    Standby Database:
    SEQUENCE# FIRST_TIME NEXT_TIME
    55698 13-JUN-11 13-JUN-11
    55699 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    15206 rows selected.
    Additional Information :
    There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
    Any help will be highly appreciated. Thanks in advance
    Sadiq

    Hi,
    Primary Database:
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    STATUS CHECKPOINT_COUNT
    ONLINE 57717
    ONLINE 57717
    57 rows selected.
    Standby Database;
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    STATUS CHECKPOINT_COUNT
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    STATUS CHECKPOINT_COUNT
    ONLINE 30723
    ONLINE 30723
    57 rows selected.
    Archieve log list :
    Primary database:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 49111
    Current log sequence 49111
    Standby Database:
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 0
    Current log sequence 49111
    I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

  • Resizing redo log files on a 3 node RAC with single node standby database

    Hi
    On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
    SQL> select group#,thread#,members,status from v$log;
    GROUP# THREAD# MEMBERS STATUS
    1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
    2 1 3 CURRENT & resized, switch logfile can change logfile group
    3 1 3 INACTIVE
    4 2 3 INACTIVE
    5 2 3 INACTIVE
    6 2 3 CURRENT
    7 3 3 INACTIVE
    8 3 3 INACTIVE
    9 3 3 CURRENT
    9 rows selected.
    SQL> alter database drop logfile group 1;
    Database altered.
    SQL> ALTER DATABASE ADD LOGFILE THREAD 1
    GROUP 1 (
    '/PROD/redo1/redo01a.log',
    '/PROD/redo2/redo01b.log',
    '/PROD/redo3/redo01c.log'
    ) SIZE 100M reuse; 2 3 4 5 6
    Database altered.
    However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
    SQL> select group#,member from v$logfile where type='STANDBY';
    GROUP#
    MEMBER
    10
    /PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
    11
    /PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
    12
    /PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
    Please let me know.
    Thanks
    Sumathy

    Hello;
    For Redo and Standby redo this won't help :
    standby_file_management is set to auto
    On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
    Then start recovery again.
    Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
    alter database add standby logfile group 4
    ('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
    ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
    Notes worth reviewing :
    Online Redo Logs on Physical Standby [ID 740675.1]
    Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
    Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
    Best Regards
    mseberg

  • Standby database config

    Hi everybody
    when i m configuring standby server
    using these command
    export ORACLE_SID=kk
    sqlplus /nolog
    conn / as sysdba
    create spfile from pfile='/u03/oracle/admin//initkk.ora' /*standby spfile*/
    startup nomount force
    alter database mount standby database ;
    alter database recover managed standby database disconnect from session;
    AND Next
    when i am using the command RECOVER STANDBY DATABASE ;
    Then the error will be occur
    ora 00283 recovery session cancelled due to errors
    ora 01110 '/u01/oracle/k/system .dbf'
    ora 01157 cannot identify/lock data file 1 - see DBWR trace file
    ora 01110 data file 'u01/oracle/k/system .dbf'
    but /u01/oracle/k/system.dbf path of the prod server and standby server path is /u03/oracle/oradata/kk/system.dbf'
    so pls help me

    hi aman
    another error will be occur at the time of reocvery of standby database ,
    when i fired the statement
    recover standby database ;
    then he want latest archive for recover ,then i make the latest archive destination
    but the last of the datafile will not be recover
    the error is
    ora 01547 waring recover succeded but OPEN RESETLOGSwould get error below
    ora 01152 file 12 is not restore from the sufficiently old backup
    ora 01110 data file /u03/abd.dbf'
    so what should i do for this
    thanks

  • StandBy database creation in oracle 10g

    Respected Sir's
    I have to create stand by database in oracle 10g i am working on (Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod) .Plz any body provide steps required for creating stand by database in oracle10g.Both the database db1 and db2 are running on archivelog.I am confuse how to set archivelog parameter that goes to db2(standby database) from db(primary database).Any one provide me steps to properly configuring the stand by database.
    Thanks

    Respected Sir
    These are the detailed steps that i performed on standby and primary database.
    On both the systems i install the oracle in E drive and the database i create in G drive and archive destination also in G drive.
    Like G:\prod1\(all the datafiles,logfiles and control file).
    G:\arch\(all the archive files).
    ON PRIMARY DATABASE(IP:192.168.2.14):
    1.First i create a database with DBCA and the database SID is prod1.
    2.Put the database in archive mode and also enable the force logging.
    3.Shutdown the Primary database and modify the following parameters in pfile.
    log_archive_dest_1='LOCATION=G:\ARCH'
    log_archive_dest_2 = "service=STDBY mandatory reopen=60"
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    log_archive_min_succeed_dest = 2
    4.Mount the primary database and create the standby controle file and create the spfile from the modified pfile.
    5.Shutdown the primary database and take the backup of all the datafile,logfile,standby controlfile ,passwordfile,pfile in a folder.
    6.Startup the primary database.
    Tnsname.ora Configuration.
    Create the connection string using the Net Manager with name STDBY and in host name i provide the IP address of the standby database.
    ON STANDBY DATABASE(IP 192.168.2.9):
    Listener.ora Configuration.
    Create a listener using the Net configuration Assistance.
    1.I copy the datafile,logfile and standby controle file in g:\prod1
    2.Copy the E:\oracle\product\10.2.0\admin\prod1 folder from primary database and past it on the same location on the standby database.
    3.On standby pfile i change only the standby_archive_dest parameter to g:\arch.
    4.Create the service with oradim -SID -NEW prod1 -STARTMODE manuall
    5.Start the standby database in nomount mode.
    6.Create the spfile from pfile and shutdown the database.
    7.Startup the database in nomount mode using spfile.
    8.ALTER DATABASE MOUNT STANDBY DATABASE;
    These are the occurs when i use tnsping stdby on primary database.
    C:\Documents and Settings\Administrator>TNSPING STDBY
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2009 12:03:55
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.2.9
    NECT_DATA = (SERVICE_NAME = prod1)))
    OK (20 msec)
    sqlnet.ora file on stand by database.
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, LDAP)
    BEQUEATH_DETACH=yes
    AUTOMATIC_IPC = ON
    NAMES.DEFAULT_DOMAIN = IDEVELOPMENT.INFO
    SQLNET.EXPIRE_TIME=2
    This occurs when i use tnsping prod1 on standby database.
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 04-FEB-2
    009 12:01:40
    Copyright (c) 1997, 2005, Oracle. All rights reserved.
    Used parameter files:
    E:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    TNS-03505: Failed to resolve name
    Please help me bec i have to create the stand database as soon as possible.Thanks Sir

  • Snapshot standby database in oracle 11g r2 RAC

    Folks,
    i am just wondering if the process is same for standalone and RAC snapshot standby database.
    We have a DR test
    1 / I just converted the standalone DR on 11g to snapshot standby database for users to do some testing and reverted back to physical standby after test was done. i folllowed metalink note ID 443720.1
    2/ now there is anotherDR test where we have 2 node prod and 2 node DR on oracle 11g rel2 RAC, so not sure we can follow the same process that i used for 11g standalone database. If somebody have done this on RAC, would you please provide the steps ?
    Thanks in advance
    SQL> select * from v$version;
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE 11.2.0.1.0 Production
    TNS for Linux: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    SQL> !uname -a
    Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

    I haven't done a Snapshot Standby (RAC or non-RAC). But I see no reason why it shouldn't work with a RAC Standby either.
    The command is a Database level command, not an Instance level command.
    Hemant K Chitale

  • Standby database in same computer

    I have made standby database in different computer then in production database in similar path and it is working.
    But whenever I try to make it in same computer it gives me error. I have gone through the oracle documentaion.
    But still I can't.
    Any suggestion on Node

    I still get the problem.
    I have created a prod database with archive log mode and archival enabled
    I shut down it and copyed the
    "oradata/prod to oradata/stdby",
    "admin/prod to admin/stdby",
    "initprod.ora to initstdby.ora" and
    "pwdprod.ora to pwdstdby.ora"
    Then I have added a service name "stdby" with net8 easy config
    Now I have created a new instance stdby with "oradim -new -sid stdby"
    now In "Prod init.ora" file I have added
    log_archive_start = true
    log_archive_dest_1 = "location=e:\Oracle\oradata\stdby\archive"
    log_archive_dest_state_1 = ENABLE
    log_archive_dest_2 = 'SERVICE=standby1'
    log_archive_dest_state_2 = ENABLE
    global_names = false
    Now I have started the prod database and created a standby controlfile
    alter database create standby controlfile '\oradata\stdby\stdby.ctl'
    now In "Stdby init.ora" file I have added
    db_name = "prod"
    instance_name = stdby
    service_names = stdby
    control_files = ("e:\Oracle\oradata\stdby\stdby.ctl")
    log_archive_start = true
    log_archive_dest_1 = "location=e:\Oracle\oradata\stdby\archive"
    log_archive_dest_state_1 = ENABLE
    standby_archive_dest = 'e:\Oracle\oradata\stdby\'
    db_file_name_convert = ('\prod\','\stdby\')
    log_file_name_convert = ('\prod\','\stdby\')
    lock_name_space = 'stdby'
    Now IN standby when I do
    SQL_stdby>>startup nomount pfile='E:\Oracle\Oracle8i\DATABASE\initstdby.ora';
    SQL_stdby>>alter database mount standby database;
    SQL_stdby>>RECOVER AUTOMATIC STANDBY DATABASE;
    Up to this it works
    Now when I start prod database
    SQL_prod>>startup
    it gives me the error
    ORA-01102: cannot mount database in EXCLUSIVE mode

  • Data Guard - Steps to install Physical standby database in an RHEL 5.6 x86

    HI Team,
    I need to install Physical standby database in a OS installed from factory with most basic packages. Please find the info in detail
    Standby Server :
    Database Version : 10g Release 2
    Operating System : Red Hat Enterprise Linux Server release 5.6 (Tikanga) , RHEL 5.6 x86_64
    swartis.dc$ free -m
    total used free shared buffers cached
    Mem: 34158 33847 311 0 558 28367
    -/+ buffers/cache: 4921 29237
    Swap: 10001 63 9937
    - Things i need to validate in the PROD server. Eg : Are the prod db version & standby db version should be the same, Do the OS need to be same ............ETC
    - Basic Linux rpm required for standby server & any other pre-requisites required at standby server
    - Verify connectivity speed btw servers to decide log file size
    - Please give me more detailed steps , where i need to start the steps in installation of Physical standby database.
    Thanks in advance.
    -- Rakesh
    Edited by: Rakesh on Jan 10, 2012 8:23 AM

    Hello again;
    Sorry for the Delay.
    To this question "Do i need to install 10.2.0.2.0 ORACLE_HOME & on top of it apply 10.2.0.3.0 patchset.?"
    Yes.
    All my Oracle 10 installs started with 10.2.0.1 and then I patched up from there. If I remember correctly 10.2.0.1 may bark on Red Hat 5.
    You can work around this by reviewing this file :
    /etc/redhat-releaseSave whatever is in there somewhere and replace it with :
    redhat-3After the install put back what was there and get rid of the "redhat-3".
    I extra RPM's I used were :
    rpm -ivh kernel-headers-2.6.18-164.el5.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh elfutils-libelf-devel*.x86_64.rpm glibc-devel-2* gcc-4*.x86_64.rpm gcc-c++-4*.x86_64.rpm libstdc++-devel-4*.x86_64.rpm glibc-headers*.x86_64.rpm libgomp*.x86_64.rpm
    rpm -ivh  compat-libstdc++-33* libaio-devel*.x86_64.rpm
    rpm -ivh sysstat*I searched my Red Hat Disks before hand and ran the RPM commands as shown. Adjust as needed.
    To verify that the required packages have been installed on your system, run the following command :
    pm -q --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" binutils \
    compat-libstdc++-33 elfutils-libelf elfutils-libelf-devel gcc gcc-c++ glibc \
    glibc-common glibc-devel-2.5 libaio libaio-devel libgcc libstdc++ libstdc++-devel \
    make sysstatThis document is for Oracle 11, but the OS part should be the same.
    http://www.visi.com/~mseberg/installing_oracle_11g_r2_64.html
    Currently I have 3 servers running both Oracle 10 and 11 ( In different homes ) using this OS.
    I have used Oracle 11 document with Oracle 10 also : ( Better once you are setup and a great standby recovery document )
    http://www.visi.com/~mseberg/duprman2.html
    Best Regards
    mseberg

  • Standby database with ASM disks?

    Has anyone successfully created a standby database when the primary database and the standby database are using ASM disks? If the answer is yes, how did you copy the files(database backup, control files, etc.) from the asm on primary to asm on standby?
    Note: I am using 10gR2 on HP-UX but the copy part should be platform independent so however you did it should help me.

    Hi d_carmichael2001,
    I had done database migration from Non-asm to ASM for single instance by RMAN.
    and i think mostly steps are same for create standby database on ASM.
    Have a Look.......
    1.create a ASM instance manually on new server.
    2.Take a backup of Prod database and controlfile.
    **backup of controlfile for Standby should be taken as
    BACKUP CURRENT CONTROLFILE FOR STANDBY;
    Backup database cmd will be same as Backup database plus archivelog;
    3. create standby database by using following cmd and set necessary parameter before execute it
    Diskgroup for standby should be define in standby spfile's.
    **Standby database should be in nomount stange
    **connect as % rman TARGET / AUXILIARY SYS/sys_pwd@sbdb1
    Use
    DUPLICATE TARGET DATABASE FOR STANDBY ;
    This command will copy the datafiles, archived redo log files and standby control file in the backup set to the standby database's storage area.
    Thanks
    Kuljeet Pal Singh

  • Standby database 10.2

    HI , I have problem with my standby database, all parameters are good work but in my alert log file have following error;
    ORA-16401: archivelog rejected by RFS, pls help me what the problem???
    On Primary: spfileORCL.ora
    *.control_files='/u01/oracle/oradata/orcl/control01.ctl','/u01/oracle/oradata/orcl/control02.ctl','/u01/oracle/oradata/orcl/control03.ctl'
    *.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
    *.db_unique_name='BAKI'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
    *.LOG_ARCHIVE_DEST_2='SERVICE=LONDON LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=LONDON'
    *.LOG_ARCHIVE_DEST_STATE_1=enable
    *.LOG_ARCHIVE_DEST_STATE_2=enable
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.FAL_SERVER=LONDON
    *.FAL_CLIENT=BAKI
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.SERVICE_NAMES=BAKI
    ON my standby database spfileORCL.ora
    *.control_files='/u01/oracle/oradata/orcl/stanctl.ctl'
    *.db_recovery_file_dest='/u01/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.remote_login_passwordfile='EXCLUSIVE'
    *.db_unique_name='LONDON'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(BAKI,LONDON)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=/u02 VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=BAKI'
    *.LOG_ARCHIVE_DEST_2='SERVICE=BAKI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=BAKI'
    *.LOG_ARCHIVE_DEST_STATE_1=enable
    *.LOG_ARCHIVE_DEST_STATE_2=enable
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.FAL_SERVER=BAKI
    *.FAL_CLIENT=LONDON
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.SERVICE_NAMES=LONDON
    all connections work well:
    SQL> conn sys/sys@BAKI as sysdba
    Connected.
    SQL>
    SQL> conn sys/sys@LONDON as sysdba
    Connected.
    SQL>
    SQL> select * from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    OS: SUSE 10

    Primary :
    alert_log:
    Errors in file /u01/oracle/admin/orcl/bdump/orcl_arc0_8465.trc:
    ORA-16401: archivelog rejected by RFS
    orcl_arc0_8465.trc:
    Error 16401 creating standby archive log file at host 'LONDON'
    ORA-16401: archivelog rejected by RFS
    kcrrwkx: work to do 0x2 (end)
    Error 16401 creating standby archive log file at host 'LONDON'
    ORA-16401: archivelog rejected by RFS
    kcrrwkx: nothing to do (end)
    kcrrwkx: nothing to do (end)
    kcrrwkx: nothing to do (end)
    *** 2009-09-08 12:32:06.342
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0xa)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0xa)
    tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x2)
    tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x2)
    kcrrwkx: work to do 0x2 (end)
    Error 16401 creating standby archive log file at host 'LONDON'
    ORA-16401: archivelog rejected by RFS
    kcrrwkx: work to do 0x2 (end)
    Error 16401 creating standby archive log file at host 'LONDON'
    ORA-16401: archivelog rejected by RFS
    kcrrwkx: nothing to do (end)
    kcrrwkx: nothing to do (end)
    kcrrwkx: nothing to do (end)
    Standby:
    alert_log
    Tue Sep 8 12:19:28 2009
    Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
    ORA-16401: archivelog rejected by RFS
    RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
    Tue Sep 8 12:19:28 2009
    Errors in file /u01/oracle/admin/orcl/udump/orcl_rfs_5463.trc:
    ORA-16401: archivelog rejected by RFS
    Tue Sep 8 12:19:31 2009
    ARC1: Archiving not possible: No primary destinations
    ARC1: Failed to archive thread 1 sequence 6 (4)
    orcl_rfs_5463.trc:
    ORA-16401: archivelog rejected by RFS
    *** 2009-09-08 12:20:28.159
    KCRRFLAS
    KCRRSNPS
    *** 2009-09-08 12:20:28.162 60679 kcrr.c
    RFS[4]: Archivelog thread 1 sequence 6 cannot be reused
    This problem can occur as the result of multiple primary and/or
    standby database(s) trying to archive to this standby database.
    This is not allowed, since successfully completed archivelogs
    would be overwritten.
    ORA-16401: archivelog rejected by RFS
    *** 2009-09-08 12:20:28.165 60679 kcrr.c
    RFS[4]: Archivelog thread 1 sequence 7 cannot be reused
    This problem can occur as the result of multiple primary and/or
    standby database(s) trying to archive to this standby database.
    This is not allowed, since successfully completed archivelogs
    would be overwritten.
    ORA-16401: archivelog rejected by RFS

  • Creating Standby database with Oracle 10gR2 SE (no dataguard). Procedure

    Hello,
    I have problems in creating a standby database without Dataguard (Oracle Standard Edition)
    -Oracle 10gR2 SE (No DataGuard !!!!)
    - SUSE Enterprise 10.
    Both primary and standby databases are running in Virtual machines (lab).
    I will describe the exact steps I followed :
    1.---------------------------------------------------
    Both primary and standby databases have exactly the same file / folder structure
    2.---------------------------------------------------
    I enabled archive log mode with a new destination : /opt/oracle/oradata/orcl/archive_logs.
    Also : SQL> alter database force logging;
    3.---------------------------------------------------
    I shut down the primary database (shutdown immediate)
    4.---------------------------------------------------
    I created a standby controlfile on the primary database:
    SQL> startup mount
    SQL> alter database create standby controlfile as '/tmp/standby.ctl'
    SQL> shutdown immediate
    5.---------------------------------------------------
    I did a cold backup from the primary db to the standby db
    (I copied all the db files, control files, redo log)
    6.---------------------------------------------------
    I copied from the primary db to the standby db the standby control file
    (from primary /tmp/standby.ctl)
    7.---------------------------------------------------
    I copied from the primary db to the standby db the standby control file
    (from primary /tmp/standby.ctl)
    8.---------------------------------------------------
    I created on the standby database a pfile from the spfile :
    SQL> create pfile from spfile;
    9.---------------------------------------------------
    I edited the pfile and changed the controlfile location (with the standby controlfile created in step 4)
    >>>>> *.control_files='/opt/oracle/oradata/orcl/standby.ctl'
    10.--------------------------------------------------
    I started the standby db
    SQL> startup mount pfile='/opt/oracle/product/10.2/db_1/dbs/initorcl.ora'
    SQL> alter database recover managed standby database disconnect from session;
    SQL> quit
    11.--------------------------------------------------
    I made some changes on the primary db on user scott
    SQL> update table set .......
    12.--------------------------------------------------
    I switched logfile on the primary db
    SQL> alter system switch logfile;
    13.--------------------------------------------------
    I manually copied the new archivelog to the standby db
    And then nothing !!!
    The db changes are not applied.
    Please help me fix the procedure !!!
    Thanks

    Hi
    Ref to your Oracle SE Standby issue, we were in similar situation couple of years ago to build an Automated Standby for our disaster recovery on Oracle SE. We finally got a solution provider Anbul Technologies , they have a one of their solutions based on Oracle SE which provided fully automated Standby in Oracle SE.
    We are successfully running that solution in our prod env for many years. You can visit their site www.anbultechnologies.co.uk or contact them for further details. They are Uk based but provides support and services all over Europe.
    Cheers

  • Manual Standby Database not in sync with missing archivelogs

    Hello,
    OS: Solaris
    DB: Oracle 11.2.0.1 EE
    Not Using ASM or RAC
    I have a Production database that is in archivelog mode and a Standby DR server.
    Both servers (Prod, Standby) have exact same structure and db name/version.
    We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
    We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
    I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
    Every time I try to apply a new archive log via recover standby, these are the errors:
    ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
    ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
    ORA-00280: change 211077622 for thread 1 is in sequence #69486
    ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-10879: error signaled in parallel recovery slave
    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: '/oradevices/PROD/oraPRODsystem1.dbf'
    When I check v$log_history, the new logs have not been applied.
    I've also tried the "Restore from incremental backup via SCN" method with same results.
    Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
    I would eventually like to get DataGuard in here, but that's not the case at the moment.
    Thanks for your suggestions.
    -Dav

    if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
    1. remove
    all the datafiles and controlfiles from the standby database.
    2. Create a new standby controlfile of the production for standby using the following cmd
    'alter database create standby controlfile as 'Location';'
    3. move the new controlfile to standby database server location as specified in initialization parameter file.
    4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
    5. startup nomount
    6. alter database mount standby database;
    7. recover standby database.
    scp the archive log sequence that is asked by the database, from production.
    You can try this steps.

  • 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

Maybe you are looking for