Steps To Create Physical Standby Database In Windows 7

Hi All,
I want to create a physical standby database in my windows 7 system. I have created one service stdby in my machine with all your help and now I need your help to configure standby configuration.
I am using Oracle 10G version 10.2.0.1.0.
Please suggest.
Regards,
Arijit

[on primary]
step-1 check if archiving is enable
SQL> archive log list;
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /PGHProdDB/archive/paceview/
Oldest online log sequence     52
Next log sequence to archive   54
Current log sequence           54
step-2
sqlplus> ALTER DATABASE force logging;step-3
connect to rman
take an full backup
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
step-4
now copying initpfile,pwdfile on appropriate destination and rename it.
step 5
now create listener on standby db side::
and restart it by ----
lsnrctl reload
and login to primary db and register listener information in tnsfile.ora---
standby=
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.1.13)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = standby)Step 6 Startup the standby
SQL> startup nomount pfile='/u01/app/oracle/admin/PRIMARY/pfile/init.ora';step 7
though our primary db is ready to connect with standby db
[oracle@PGH-DB ~]$ rman target / auxiliary sys/tiger@standby
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Aug 6 12:16:08 2012
Copyright (c) 1982, 2007, Oracle.  All rights reserved.
connected to target database: primary (DBID=2092349485)
connected to auxiliary database (not started)
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}When this completes
Make sure you shutdown the database and then switch the ORACLE_SID=STANDBY
when you perform that much let me know :)
Edited by: abdul_ora on Sep 12, 2012 11:37 AM

Similar Messages

  • Creating physical standby database on same machine with dataguard

    hi every one
    i m new in oracle databases,
    i read documentation to create physical standby databases,
    now i install virtual machine (vmware) on my system,
    i install windows xp on this vm and oracle 9i
    now i want to create standby database on the same machine in some other drive configured with datagurd
    virtual machine
    OS windows xp
    database oracle 9i
    plz reply me how i do this
    explain clearly step by step.
    plz reply me in detail

    When you need to have the standby database on the same server as the master, use lock_name_space in the init.ora.
    This parameter permits this to occur without having to worry about changing the db_name.
    http://www.oug-ottawa.org/pls/htmldb/f?p=103:21:729607614317189728::::P21_TIP_NUM:821

  • Problem creating physical Standby database with RMAN

    Hi All
    I am trying to learn oracle dataguard and as part of the process learning creating standby database.
    Platform : Sun-Fire-V250 Sparc, Solaris 10
    Database Version - Oracle 11R2
    I am creating standby database on same server, so directory structure is different.
    Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
    1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
    2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
    On Primary Database:
    *.FAL_CLIENT='orcl11020' #Primary database unique name
    *.FAL_SERVER='stdby_11' #Standby database unique name
    db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
    log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
    standby_file_management=auto
    *.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
    *.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
    *.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    Copied same pfile for standby database and modified following-
    *.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
    *.db_name='orcl1102'
    *.db_unique_name='stdby_11'
    *.FAL_CLIENT='stdby_11'
    *.FAL_SERVER='orcl11020'
    db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
    log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
    standby_file_management=auto
    *.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
    *.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    db_unique_name=orcl11020'
    3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
    3. Created password file with same credential as primary database.
    4.Up-to-date RMAN backup of primary database available.
    5.Create standby controlfile with rman
    While primary database s open (I tried with primary database in mount mode as well)-
    $>rman catalog rman/paswd@rman target /
    RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
    6. Open a new terminal and startup standby database in nomount mode using parameter file created -
    $>ORACLE_SID=stdby_11
    $>export ORACLE_SID
    $>sqlplus / as sysdba
    SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
    SQL>quit
    $> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
    RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
    RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
    Error 1017 received logging on to the standby
    Check that the primary and standby are using a password file
    and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
    and that the SYS password is same in the password files.
    returning error ORA-16191
    FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
    Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    So on both primary and standby I confirmed
    SQL> show parameter remote_login_passwordfile
    NAME TYPE VALUE
    remote_login_passwordfile string EXCLUSIVE
    To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
    Password files are called - orapworcl11020 and orapwstdby_11
    Can someone guide me where thisngs are going wrong here please.

    Not sure if I understood it clearly.
    SELECT * FROM V$ARCHIVE_GAP;
    returns no rows so there is no gap.
    But could you please explain me the result of the previous query. To catch up again, on standby when I check
    SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    SEQUENCE# APPLIED
    75 NO
    74 NO
    76 NO
    77 NO
    I understand that though archive files have been copied across but they are not applied yet.
    On primary when I give your query -
    SELECT name as STANDBY,SEQUENCE#,applied, completion_time
    2 FROM v$archived_log
    3 where dest_id=2
    4 and sequence# BETWEEN 74 and 80;
    I get -
    STANDBY SEQUENCE# APPLIED COMPLETIO
    stdby_11 74 YES 28-JUN-11
    stdby_11 75 YES 28-JUN-11
    stdby_11 76 YES 29-JUN-11
    stdby_11 77 YES 29-JUN-11
    stdby_11 78 YES 29-JUN-11
    stdby_11 79 YES 29-JUN-11
    stdby_11 80 YES 29-JUN-11
    stdby_11 75 NO 07-JUL-11
    stdby_11 74 NO 07-JUL-11
    stdby_11 76 NO 07-JUL-11
    stdby_11 77 NO 07-JUL-11
    stdby_11 78 NO 07-JUL-11
    I have intentionally given
    sequence# BETWEEN 74 and 80
    because I know in the current incarnaion of the database, max sequence is 78.
    So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
    Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
    Then my final question is, when will these archives be applied to standby database?
    I am sorry to ask too many questions but I am just trying to understand how it all works.
    Thanks for your help again

  • Error while creating physical standby database using Oracle Grid 10.2.0.5

    Hi All,
    I am setting up data guard using oracle grid.
    Primary database version: - 10.2.0.4
    Standby database version: - 10.2.0.4
    Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
    Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
    I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
    Fatal NI connect error 12533, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 10.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
      Time: 17-AUG-2010 02:40:07
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12533
        TNS-12533: TNS:illegal ADDRESS parameters
        ns secondary err code: 0
        nt main err code: 0
        nt secondary err code: 0As we can see, address_list is empty.
    Can anyone suggest what could be the reason behind this?

    Dear user13295317,
    Here is the error explanation;
    Oracle Error :: TNS-12533
    TNS:illegal ADDRESS parameters
    Cause
    An illegal set of protocol adapter parameters was specified.
    In some cases, this error is returned when a connection cannot be made to the protocol transport.
    Action
    Verify that the destination can be reached using the specified protocol.
    Check the parameters within the ADDRESS section of TNSNAMES.ORA.
    Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
    Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
    Ogan

  • How to create physical standby database without dataguard

    Hi,
    Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
    Please find the specifications of my server :
    Database : Oracle 10.2.0.1(Standard Edition)
    Server : Linux 4.0(32 bit machine)
    As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
    Thanks in advance.
    Regards,
    Farooq

    Hello,
    I hope this link helps you out...
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    Thanks & Regards
    Pratik Lakhpatwala
    Jr Oracle DBA
    Edited by: Pratik.L on Dec 31, 2009 12:03 PM

  • URGENT:Diagnose The Steps for Creating a Standby Database

    Why Following Steps Can Not Succeed? What are the problems?
    The Steps of Creating a Physical Standby Database
    SQL>alter system set db_recovery_file_dest_size=2000m scope=both;
    SQL>alter system set db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area' scope=both;
    SQL> shutdown immediate
    SQL> startup mount
    SQL> alter database archivelog;
    SQL>alter system set db_flashback_retention_target=120 scope=both;
    SQL> alter database flashback on;
    SQL> alter database force logging;
    #The Primary Database Pfile after being edited
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # SGA Memory
    sga_target=370147328
    # Job Queues
    job_queue_processes=10
    # Shared Server
    dispatchers="(PROTOCOL=TCP) (SERVICE=orcl10XDB)"
    # Miscellaneous
    compatible=10.2.0.1.0
    # Security and Auditing
    audit_file_dest=C:\oracle\product\10.2.0/admin/orcl10/adump
    remote_login_passwordfile=EXCLUSIVE
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=122683392
    # Database Identification
    db_domain=""
    db_name=orcl10
    # File Configuration
    control_files=("C:\oracle\product\10.2.0\oradata\orcl10\control01.ctl", "C:\oracle\product\10.2.0\oradata\orcl10\control02.ctl", "C:\oracle\product\10.2.0\oradata\orcl10\control03.ctl")
    db_recovery_file_dest=C:\oracle\product\10.2.0/flash_recovery_area
    db_recovery_file_dest_size=2147483648
    # Cursors and Library Cache
    open_cursors=300
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_tablespace=UNDOTBS1
    # Diagnostics and Statistics
    background_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/bdump
    core_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/cdump
    user_dump_dest=C:\oracle\product\10.2.0/admin/orcl10/udump
    # Processes and Sessions
    processes=150
    # Cache and I/O
    db_block_size=8192
    db_file_multiblock_read_count=16
    DB_NAME=orcl10
    DB_UNIQUE_NAME=orcl10
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl10,stdby4)'
    LOG_ARCHIVE_DEST_1=
    'LOCATION=/arch1/orcl10/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=orcl10'
    LOG_ARCHIVE_DEST_2=
    'SERVICE=stdby4 LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=stdby4'
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=ENABLE
    REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
    LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    LOG_ARCHIVE_MAX_PROCESSES=30
    FAL_SERVER=stdby4
    FAL_CLIENT=orcl10
    DB_FILE_NAME_CONVERT='stdby4','orcl10'
    LOG_FILE_NAME_CONVERT=
    '/arch1/stdby4/','/arch1/orcl10/','/arch2/stdby4/','/arch2/orcl10/'
    STANDBY_FILE_MANAGEMENT=AUTO
    SQL> create spfile from pfile;
    RMAN> connect target
    RMAN> backup database;
    ###TheBackupHandle==C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL10\BACKUPSET\2007_11_06\O1_MF_NCSNF_TAG20071106T064915_3LZ7LRN8_.BKP
    RMAN> backup datafile1,2,3,4,5;
    C:\DocumentsandSettings\Administrator>mkdir C:\ORACLE\PRODUCT\10.2.0\ORADATA\temp\stdby4
    SQL> alter database create standby controlfile as '/temp/stdby4.ctl';
    SQL> create pfile='/temp/initstdby4.ora' from spfile;
    #Pfile Edited for The Physical Standby Database
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # SGA Memory
    sga_target=370147328
    # Job Queues
    job_queue_processes=10
    # Shared Server
    dispatchers="(PROTOCOL=TCP) (SERVICE=stdby4XDB)"
    # Miscellaneous
    compatible=10.2.0.1.0
    # Security and Auditing
    audit_file_dest=C:\oracle\product\10.2.0/admin/stdby4/adump
    remote_login_passwordfile=EXCLUSIVE
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=122683392
    # Database Identification
    db_domain=""
    db_name=orcl9
    # File Configuration
    control_files=("C:\oracle\product\10.2.0\oradata\stdby4\control01.ctl", "C:\oracle\product\10.2.0\oradata\stdby4\control02.ctl", "C:\oracle\product\10.2.0\oradata\stdby4\control03.ctl")
    db_recovery_file_dest=C:\oracle\product\10.2.0/stdby4/flash_recovery_area
    db_recovery_file_dest_size=2147483648
    # Cursors and Library Cache
    open_cursors=300
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_tablespace=UNDOTBS1
    # Diagnostics and Statistics
    background_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/bdump
    core_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/cdump
    user_dump_dest=C:\oracle\product\10.2.0/admin/stdby4/udump
    # Processes and Sessions
    processes=150
    # Cache and I/O
    db_block_size=8192
    db_file_multiblock_read_count=16
    DB_UNIQUE_NAME=stdby4
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl10,stdby4)'
    DB_FILE_NAME_CONVERT='orcl10','stdby4'
    LOG_FILE_NAME_CONVERT=
    '/arch1/orcl10/','/arch1/stdby4/','/arch2/orcl10/','/arch2/stdby4/'
    LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc
    LOG_ARCHIVE_DEST_1=
    'LOCATION=/arch1/stdby4/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=stdby4'
    LOG_ARCHIVE_DEST_2=
    'SERVICE=orcl10 LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=orcl10'
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=ENABLE
    REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
    STANDBY_FILE_MANAGEMENT=AUTO
    FAL_SERVER=orcl10
    FAL_CLIENT=stdby4
    C:\Documents and Settings\Administrator>oradim -new -sid stdby4 -startmode manual
    Create Listener and Network Service Name for Standby Database.Stop and start listener(not need)
    SQL>create spfile from pfile='/temp/initstdby4.ora';
    C:\Documents and Settings\Administrator>set oracle_sid=stdby4
    SQL> startup mount;
    ORA-01078: failure in processing system parameters
    LRM-00109: ???????????????? 'C:\ORACLE\PRODUCT\10.2.0\DB_10\DATABASE\INITSTDBY4.ORA'
    Message was edited by:
    frank.qian
    Message was edited by:
    frank.qian

    you have now two different pfiles: one in c:\temp\initstdby4.ora. and %ORACLE_HOME%\database\initstdby4.ora.
    You are using the latter, as you didn't specify pfile= in your startup mount.
    Also, if you are using a spfile, the only line in a pfile should be: spfile=....
    In your pfile you are mixing up Unix like file locations with \ and Windows file locations with /
    Could you please read the docs
    more closely
    more closely
    more closely
    and work
    more carefully
    more carefully
    more carefully
    It is very simple, but you must work carefully.
    Sybrand Bakker
    Senior Oracle DBA

  • Create physical standby database via grid control Errror

    Hi
    I wonder if anyone has seen the following problem
    I am creating a standby database using EM Grid Control wizard. It all configures fine and starts the job goes through all steps including copying datafiles etc. but when it hits the step CREATE STANDBY DATABASE it fails with no explanation. In the oms log all it says is an error about cant find the sid name
    EM Grid COntrol is 10.2.0.5 version
    Windows Primary is Windows 2003 server 10.2.0.4 db
    Trying to create on windows 2003 server with same oracle version
    Thanks
    D

    Did you search the same on Metalink ?
    please also cehck
    EM: Creation process for a physical standby DB failed with SQL Exception
    Regards
    Rajesh

  • 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

  • Creating physical standby databases with DG Broker & OEM

    Hi guys,
    I manage 8i, 9i & 10g databases through OEM 10.2.0.2.
    Today, I would like to create physical standby db for the most important applications. Because I'm a lazy guy, I'd like to do it the easiest way, with GUI and wizzards provided by OEM.
    1. Do you know any tutorial on the Internet that would help to do it easily ? My only source up to now is the official DB broker documentation (http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/toc.htm), which is 300 pages long like every Oracle doc. I'd appreciate any tutorial that could lead me straight to the essential. I've heard that is not so tricky to create a physical standby db
    2. Is the procedure really different to create (and then manage) a physical standby database on Oracle 8i, 9i and 10g ? Is it possible to do it through DB Broker and OEM for every version ?
    thank you for your help
    Antoine

    Antionio,
    Oracle Documentation is the best source of configuring any Oracle component.
    But, If you do not want to read the entire doc, and want to configure Dataguard Broker (without OEM), then here is the Link.
    http://www.oracledba.org/10g/dr/10gR2_dataguard_RAC_to_RAC.html#Configure_Dataguard_Broker:

  • DBhanging in open stage after creating physical standby database

    alter database open read only hanging after creating the standby database using rman.

    hi,
    when i starts the database in restricted mode it is asking resetlogs;
    when i openthe database using the
    alter database open resetlogs;
    it is showing following errors
    alter database open RESETLOGS
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00338: log 1 of thread 1 is more recent than control file
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    RESETLOGS after complete recovery through change 28393568059
    Resetting resetlogs activation ID 3821641494 (0xe3c99f16)
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 1 of thread 1 is not current copy
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    Thu Feb 24 20:05:42 2011
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00316: log 1 of thread 1, type 0 in header is not log file
    ORA-00312: online log 1 thread 1: '/dev/stage/oradev/db/apps_st/data/group_1.314.731945051'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 2 of thread 1 is not current copy
    ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 3 of thread 2 is not current copy
    ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_m000_348380.trc:
    ORA-00322: log 4 of thread 2 is not current copy
    ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 2 of thread 1 is not current copy
    ORA-00312: online log 2 thread 1: '/dev/stage/oradev/db/apps_st/data/group_2.313.731945057'
    Thu Feb 24 20:05:58 2011
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 3 of thread 2 is not current copy
    ORA-00312: online log 3 thread 2: '/dev/stage/oradev/db/apps_st/data/group_3.316.731945065'
    Errors in file /oracle/app/oradev/db/tech_st/11.2.0/admin/stdby_developmentDR/diag/rdbms/stdby/stdby/trace/stdby_ora_442500.trc:
    ORA-00367: checksum error in log file header
    ORA-00322: log 4 of thread 2 is not current copy
    ORA-00312: online log 4 thread 2: '/dev/stage/oradev/db/apps_st/data/group_4.315.731945069'
    thanks in advance

  • Creating physical standby database from another physical standby database

    hi,
    We have one production database and one physical standby of the production. Now we have situation where we need to create one database from either production or from standby. As production is loaded we can not do it using active database option. Now we have the only option to copy the database from standby.
    As of now we open the standby and copy it using rman duplicate database and again we put it back to standby mode.
    Is it possible to create standby database from standby database only?
    Oracle version : 11.1.0.7.0
    I have seen procedure allowing to do the same in version 11.2.0.3. I have tried searching for the difference but didn't find when this feature was introduced.
    Thanks,
    Ketul Patel

    Hello;
    Active duplicate should work when connected to Standby as source Database. However there's a bug 11715084 which is not fixed until version 11.2.0.4.
    If patch 11715084 is available for your version it may work, but all the 11.1.0 are gone so I have no way to test.
    RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET [ID 1343515.1]
    Understanding ORA-01671 error during controlfile creation / backup [ID 461121.1]
    Best Regards
    mseberg
    Edited by: mseberg on Feb 13, 2013 8:59 AM

  • Problem while creating Physical standby database on remote Server

    Hi
    I try to create a physical standby datbaase using OEM 10gr2, it is working when I create on same server. No issue but when I try to create same on remote server it is giving below warning and process failing. Please let me know what needs to be down in this senario...
    It is showing redo log information in v$log and v$log_file but not creating physically on PHYSICAL Standby instance..
    I appriciate your help and ur time too..
    These messages are from PRIMARY database alert*.log file
    There is space for up to 12 standby redo logfiles
    Use the following SQL commands on the standby database to create
    standby redo logfiles that match the primary database:
    ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
    ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;
    WARNING: OMF is enabled on this database. Creating a physical
    standby controlfile, when OMF is enabled on the primary
    database, requires manual RMAN intervention to resolve OMF
    datafile pathnames.
    NOTE: Please refer to the RMAN documentation for procedures
    describing how to manually resolve OMF datafile pathnames.
    Thanks and Regards,
    RK

    Well, it is simply warning that "Creating a physical
    standby controlfile, when OMF is enabled on the primary
    database, requires manual RMAN intervention to resolve OMF
    datafile pathnames.
    NOTE: Please refer to the RMAN documentation for procedures
    describing how to manually resolve OMF datafile pathnames"
    For instance, the path for the logfile name in "ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800" may need to be changed manually. It is advisable to check the mentioned documentation.

  • Step by step 10g Dataguard , physical standby database setup metalink notes

    On metalink i saw this note, but unable to find now if someone can help....

    Note:248382.1 Creating a 10g Data Guard Physical Standby on Linux

  • Problem While Creating Physical Standby Using RMAN

    Hi Guru's
    May be this incidence you all face while creating physical standby DB. I try to create Physical standby database Using RMAN Duplicate Command from one server
    (pri machine) to Standby Machine.
    The steps i followed to create the above are as follows:
    Step 1:- Enable Forced Logging
    SQL> ALTER DATABASE FORCE LOGGING;
    Step 2:- Configure a Standby Redo Log
    SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
      2> ('/oracle/dbs/log1c.rdo','/oracle/dbs/log2c.rdo') SIZE 500M;
    Step 3:- Set Primary Database Initialization Parameters
    SQL> create pfile='?/dbs/pfileorcl.ora' from spfile;
    Edit the pfile to add the standby parameters, here shown:
    db_unique_name='orcl'
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcl,orcldr)'
    LOG_ARCHIVE_DEST_2='SERVICE=orcldr LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcldr'
    *.fal_server=orcldr
    *.fal_client=orcl
    *.standby_file_management=auto
    Step 4:- Enable Archiving
    SQL> SHUTDOWN IMMEDIATE;
    SQL> STARTUP MOUNT;
    SQL> ALTER DATABASE ARCHIVELOG;
    SQL> ALTER DATABASE OPEN;
    Step 5:- Setup tnsnames for standby database
    This should be done on primary database by altering tnsnames.ora or using NetCA command, and create it by the name orcldr
    orcldr =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby-svr)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcldr)
    Step 6:- Backup database and copy it to standby
    This backup script should be run on primary and copied to standby on the same mount point, running this scripts using RMAN, all files under /rman_backup should be copied to /rman_backup on standby server.
    $rman target /
    RMAN> run
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    backup database format '/rman_backup/%U';
    backup archivelog all format '/rman_backup /%U';
    backup current controlfile for standby format '/rman_backup/%U';
    Step 7:- Standby Database Steps
    Installing Oracle Software
    This should be same release and patchset with exactly same ORACLE_HOME mount point.
    Setting Up listener
    Create and start a listener on standby database using NetCA, or creating listener.ora in $ORACLE_HOME/network/admin
    LISTENER =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = standby-svr)(PORT = 1521))
    Step 8:- Set Standby Database Initialization Parameters
    Copying the pfile created in primary database and renames it to initorcldr.ora, and changes these parameters:
    db_unique_name='orcldr'
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(orcldr,orcl)'
    LOG_ARCHIVE_DEST_2='SERVICE=orcl LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=orcl'
    *.fal_server=orcl
    *.fal_client=orcldr
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    Step 9:- Setup tnsnames for primary database
    This should be done on standby database by altering tnsnames.ora or using NetCA command, and create it by the name orcl
    orcl =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = primary-svr)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = orcl)
    Step 10:- Copy a Password File
    A password file must be created on the Primary and copied over to the Standby site. The sys password must be identical on both sites. Copy orapworcl to $ORACLE_HOME/dbs and rename file to orapworcldr
    Step 11:- Create mount points for Oracle
    Mount point should be created on standby server with the same convention used in primary, this includes the location for controlfiles, redo logs, datafiles, archive log destination and alert logs.
    $ mkdir -p /u01/app/oracle/oradata/orcl/
    $ mkdir -p /u01/app/oracle/flash_recovery_area/
    $ mkdir -p /u01/app/oracle/admin/orcl/adump
    $ mkdir -p /u01/app/oracle/admin/orcl/bdump
    $ mkdir -p /u01/app/oracle/admin/orcl/cdump
    $ mkdir -p /u01/app/oracle/admin/orcl/udump
    Step 12:- Use RMAN to restore backup and setup standby
    Connect to RMAN and execute the following command to create standby database, this should be performed on standby server after copying backup and setting tnsnames.
    $ export ORACLE_SID=orcldr
    $ rman target sys/tiger@orcl auxiliary sys/tiger@orcldr
    RMAN> duplicate target database for standby dorecover;
    Here i am getting problem as :
    While trying to connect to traget database and auxiliary database i notice that when RMAN is connect to both databases it shows
    orcl ( DBID xyz)
    orcl (not mounted)
    Here in my view the second database must be standby database name or auxiiary db name is standby db name which in my case is orcldr
    after this issue i am facing the second issues as :
    in command
    duplicate target database for standby dorecover;
    After modifying the command to
    RMAN> duplicate target database to "standby";
    rman-05520 database name mismatch
    Can u please let me know where i am mistaking

    ok for pri:
    db_name=orcl
    db_unique_name=orcl
    for standby:
    db_name=orcl 
    db_unique_name=sbyorcl ( i change orcldr to sbyorcl later)for new testing
    but now what i am getting on
      Verify connectivity
    On Primary Server:
    C:\> lsnrctl stop LISTENERI (working fine)
    C:\> lsnrctl start LISTENER (working fine)
    C:\> tnsping orcl (working fine)
    C:\> tnsping sbyorcl (working fine)
    C:\> sqlplus sys/xxxxx@orcl (working fine)
    C:\> sqlplus sys/xxxxx@sbyorcl (not working fine)
    ERROR:
    ORA-12514: TNS:listener does not currently know of service requested in connect
    descriptor
    On Standby Server:
    C:\>lsnrctl stop LISTENER
    C:\> lsnrctl start LISTENER
    C:\> tnsping orcl
    C:\> tnsping sbyorcl
    C:\> sqlplus sys/xxxxx@orcl
    C:\> sqlplus sys/xxxxx@sbyorcl
    My listner file for pri :-
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = orcl)
          (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
          (SID_NAME = ORCL)
    LISTENER =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
    tnsnames.ora file on pri is:
    sbyorcl =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
        (CONNECT_DATA =
          (SERVICE_NAME = sbyorcl)
    ORCL =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
        (CONNECT_DATA =
          (SERVICE_NAME = orcl)
    and listener file on standby :
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PLSExtProc)
          (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
          (PROGRAM = extproc)
        (SID_DESC =
          (GLOBAL_DBNAME = orcl)
          (ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
          (SID_NAME = orcl)
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    and tnsnames.ora file on standby:
    ORCL =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.128)(PORT = 1521))
        (CONNECT_DATA =
          (SERVICE_NAME = orcl)
    sbyorcl =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.202.129)(PORT = 1521))
    (CONNECT_DATA =
           SERVICE_NAME = sbyorcl)
    EXTPROC_CONNECTION_DATA =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
        (CONNECT_DATA =
          (SID = PLSExtProc)
          (PRESENTATION = RO)
    Kinldy guide me where i am mistaking it's urgent

  • Differences in creating a Standby database in RAC

    Hi All
       SO...: Solaris 11 SPARC 64
       DB...: 11.2.0.3.6 (64 bits)
       My experience regarding creating Physical Standby Databases is restricted in only single instances to single instances. I am reading the book "Oracle Database 11g Release 2 High Availability", but, in parallel, i would like to hear from the experienced DBAs here some opinions and recomendations in how to implement a RAC to RAC solution. Below are my doubts:
       1) In single instance, using RMAN Backup to create the Physical Standby, i have to create manually a static Listener Entry. But in a RAC env, the listener is a resource, so, i have to create that resource in the Clusterware manually, or there is other approach?
       2) I have to create a pfile and start the instance in NOMOUNT mode, but in RAC, i have to start all the nodes in NOMOUNT, or just one node is sufficient?
       3) The archives will be replicated from FRA to FRA. Is this the best approach?
       My main concern is with the Listener and SCAN questions... If you have any considerations, they will be most welcome.
       Thanks in advance.

    Following link might be helpful
    http://www.oracledba.org/11gR2/dr/11gR2_dataguard_RAC_to_RAC.html

Maybe you are looking for