Standby database using RMAN.

Hi All,
Please provide me complete steps to create standby database using RMAN.
Regards.

http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377

Similar Messages

  • I got the above error while i restore the standby database using RMAN backu

    Dear All,
    RMAN> crosscheck archivelog all;
    using target database controlfile instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=14 devtype=DISK
    specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
    Help need.i take the backup without catalog database.
    regards,
    DB

    rman> list backup;
    it shows lengthier but i showed only the corresponding
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3479    Full    17G        DISK        01:29:42     09-FEB-13
            BP Key: 3479   Status: AVAILABLE   Tag: 09FEB13_FULL_ESMSRV1_DB
            Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
      SPFILE Included: Modification time: 08-FEB-13
      List of Datafiles in backup set 3479
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
      2       Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
      3       Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
      4       Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
      5       Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
      6       Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
      7       Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
      8       Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
      9       Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
      10      Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
      11      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
      12      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
      13      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
      14      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
      15      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
      16      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
      17      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
      18      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
      19      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
      20      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
      21      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
      22      Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
      23      Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
      39      Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3480    Full    17G        DISK        01:21:30     09-FEB-13
            BP Key: 3480   Status: EXPIRED   Tag: TAG20130209T200021
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
      SPFILE Included: Modification time: 08-FEB-13
      List of Datafiles in backup set 3480
      File LV Type Ckp SCN    Ckp Time  Name
      1       Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
      2       Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
      3       Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
      4       Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
      5       Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
      6       Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
      7       Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
      8       Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
      9       Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
      10      Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
      11      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
      12      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
      13      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
      14      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
      15      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
      16      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
      17      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
      18      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
      19      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
      20      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
      21      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
      22      Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
      23      Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
      39      Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3481    Full    4M         DISK        00:00:03     09-FEB-13
            BP Key: 3481   Status: AVAILABLE   Tag: TAG20130209T212205
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
      Controlfile Included: Ckp SCN: 1759462488   Ckp time: 09-FEB-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3482    Full    0          DISK        00:00:01     09-FEB-13
            BP Key: 3482   Status: AVAILABLE   Tag: TAG20130209T212212
            Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
      SPFILE Included: Modification time: 08-FEB-13
    ls -l /oradatabkp
    root@drsrv1#ls -l /oradatabkp
    total 1108672
    drwxr-xr-x   2 ovsd       dba             96 Sep 27  2009 alert_bkp
    -rw-r--r--   1 oracle     dba            195 Mar 15  2007 create.sql
    drwxr-xr-x   2 oracle     dba           8192 Aug  7  2009 ctrl_bkp
    -rw-r--r--   1 root       sys        565114880 Apr 24  2007 drsrv1.tar
    drwxrwxrwx   2 root       sys             96 Jun 17  2011 drsrv2-ignitebkp
    drwxr-xr-x   4 root       sys             96 Apr 24  2007 esmsrv1
    -rw-r-----   1 root       sys        1613824 Feb 22  2007 esmsrv1stby.ctl
    -rw-r--r--   1 esmsrv1    dba           5120 Dec 31  2009 esmtables.dmp
    -rw-r--r--   1 esmsrv1    dba            538 Dec 31  2009 esmtables.log
    drwxrwxrwx   4 root       sys           8192 Mar 10  2009 export
    drwxr-xr-x   8 root       sys           8192 Apr 24  2007 finalbackup
    -rw-r--r--   1 oracle     dba           3820 Sep  5  2008 invalid.sql
    -rw-r--r--   1 esmsrv1    dba         303104 Dec 31  2009 kirdevports.dmp
    -rw-r--r--   1 esmsrv1    dba            591 Dec 31  2009 kirdevports.log
    drwxr-xr-x   2 root       root            96 Feb 12  2007 lost+found
    -rw-r--r--   1 oracle     dba          24954 Aug  9  2009 ovcontrol-090909.ctl
    drwxr-xr-x  22 root       sys           8192 Apr 24  2007 ovpi
    drwxr-xr-x   2 oracle     dba           8192 Aug  7  2009 pfile_bkp
    drwxrw-rw-   4 oracle     dba           8192 Feb 10 15:25 rman
    drwxr-xr-x  28 root       sys           8192 Feb  1 17:15 schedbkp
    drwxr-xr-x   2 oracle     dba           8192 Jul 11  2011 sdnnm
    -rw-r--r--   1 esmsrv1    dba           2196 Dec 31  2009 srirdevports.log
    drwxr-xr-x   2 oracle     dba             96 Mar 13  2009 statsreport
    -rw-r--r--   1 oracle     dba            966 Mar 15  2007 tbs.sql
    drwxr-xr-x   5 oracle     dba             96 Mar 16  2007 testov
    drwxr-xr-x   2 root       sys         442368 Mar 11  2009 trendadm_files
    root@drsrv1#ls -l /oradatabkp/rman
    total 37244448
    drwxr-xr-x   2 oracle     dba           8192 Feb 10 15:25 esmsrv1
    -rw-r-----   1 oracle     dba        19068198912 Feb  9 14:21 esmsrv1_full_db_09feb13
    drwxrw-rw-   2 oracle     dba           8192 Feb  9 21:36 openview
    -rw-r--r--   1 oracle     dba         920442 Feb  9 21:37 rmanbkp-all.log

  • Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

    Hi All,
    I am in confusion how to create logical standby database from primary database using rman active database command.
    What i did:-
    Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
    Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
    Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
    The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
    I done the creation of logical standby database by converting physical standby to logical standby database
    I am following the below mentioned doc for the same:
    Creating a physical and a logical standby database in a DR environment | Chen Guang's Blog
    Kindly guide me how to work over the same or please provide me the steps of the same.
    Thanks in advance.

    Thanks for your reply
    I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
    But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
    My primary database pfile is:
    pc01prmy.__db_cache_size=83886080
    pc01prmy.__java_pool_size=12582912
    pc01prmy.__large_pool_size=4194304
    pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01prmy.__pga_aggregate_target=79691776
    pc01prmy.__sga_target=239075328
    pc01prmy.__shared_io_pool_size=0
    pc01prmy.__shared_pool_size=134217728
    pc01prmy.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.fal_client='PC01PRMY'
    *.fal_server='PC01SBY'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='DEFER'
    *.log_archive_dest_state_3='DEFER'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    My logical standby pfile is:-
    pc01ls.__db_cache_size=92274688
    pc01ls.__java_pool_size=12582912
    pc01ls.__large_pool_size=4194304
    pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    pc01ls.__pga_aggregate_target=79691776
    pc01ls.__sga_target=239075328
    pc01ls.__shared_io_pool_size=0
    pc01ls.__shared_pool_size=125829120
    pc01ls.__streams_pool_size=0
    *.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
    *.audit_trail='db'
    *.compatible='11.1.0.0.0'
    *.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
    *.db_block_size=8192
    *.db_create_file_dest='/u01/app/oracle/oradata'
    *.db_domain=''
    *.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
    *.db_name='pc01prmy'
    *.db_unique_name='pc01ls'
    *.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.diagnostic_dest='/u01/app/oracle'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
    *.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
    *.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
    *.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
    *.open_cursors=300
    *.pga_aggregate_target=78643200
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=236978176
    *.undo_tablespace='UNDOTBS1'
    Kindly advice over the same

  • Problem creating standby database using RMAN

    I am preparing standby database on Windows environment. For the same..
    1. I have taken full database,archivelog and standby control file backup on primary database.
    2.Backup pieces have been moved to standby server.
    3.TNS configured on both the servers.
    4.connected to target as well as auxiliary database and trying to create the standby database using the below command...
    duplicate target database for standby;
    But I am getting the below error........
    channel ORA_AUX_DISK_1: starting datafile backupset restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
    ORA-19870: error reading backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
    ORA-19504: failed to create file "E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM\CONTROL01.CTL"
    ORA-27040: file create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    failover to previous backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 07/01/2009 10:35:48
    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
    Please provide me the solution for the same...
    Thanks in Advance.....
    Sukanta

    channel ORA_AUX_DISK_1: reading from backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
    ORA-19870: error reading backup piece E:\BACKUP\STNDBY_CF_AIRPRIM_T690931864_S25_P1
    ORA-19504: failed to create file "E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM\CONTROL01.CTL"
    ORA-27040: file create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    failover to previous backup
    Can you please confirm if the directory E:\ORACLE\PRODUCT\10.2.0\ORADATA\AIRPRIM is existing on standby box and rman can write to that location (free space & permissions)
    If the issue is still present provide us the control_files parameter from standby..
    - Ravi.M

  • Creating standby database using RMAN

    When I'm creating standby database with RMAN command
    'duplicate for standby' backups for creating standby database
    have to be accessible from host where standby database
    is created. I can copy the backups to standby host, or use
    NFS to share the disk with backups to standby host.
    But when I have backups in ASM diskgroup how can
    I achieve it would be accessible from standby host?
    Thanks a lot for advice,
    M.

    OK, thanks,
    I will create standby using Grid, but I have the following problem:
    database instance is running on the host where I want
    to create standby database. The running instance is for
    testing purposes and has the same db_name, db_unique_name, db_domain
    parameters as in primary database.
    I will change db_unique_name to be distinct from primary database one,
    should I also change instance SID not to be the same in
    testing database and standby on the same host, or when creating standby
    database I can specify distinct one for standby database?

  • Standby database using rman backup

    I'm using oracle11g on my work place and now i wont to create duplicate database using rman backup.
    at the time i installed only oracle 11g software.
    Pls guide me to overcome the problem. i'm newcomer to oracle.
    Pls give the steps.
    Edited by: user10444101 on Apr 30, 2010 2:17 AM

    user10444101 wrote:
    I'm using oracle11g on my work place and now i wont to create duplicate database using rman backup.
    at the time i installed only oracle 11g software.
    Pls guide me to overcome the problem. i'm newcomer to oracle.
    Pls give the steps.
    Edited by: user10444101 on Apr 30, 2010 2:17 AMSee the following link
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#i1008564

  • Create Standby Database using RMAN changing backuppiece location ID753902.1

    [https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 07/06/2011 13:50:40
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
    logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
    my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
    thanks
    Edited by: user9198889 on Jul 6, 2011 8:29 AM

    CKPT wrote:
    user9198889 wrote:
    [https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 07/06/2011 13:50:40
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
    logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
    my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
    thanks
    Edited by: user9198889 on Jul 6, 2011 8:29 AMHave you restored from the recent backup?
    validate the backup compeltion_time and then retry the operation, Are you restoring from tapes?yes its recent backup(last and only backup infact ) , the backup took couple of days to run..
    the backup was executing using this command BACKUP INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG 'LEV1_BCKP_2011-06-27_11_54' PLUS ARCHIVELOG DELETE INPUT
    there was no full backup so oracle must have taken full one and not incremental correct?
    first logseq that was back's up is : 35818
    primary uses local disk for its db and backup
    standby that i am trying to create is on asm. i have copied backup to FRA and restored to +data its recovery that is failing now                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • 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

  • 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

  • Issue in creating the standby database from Active database using RMAN

    Hi All,
    I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
    Version of Database:11g(11.2.0.1.0)
    Operating System:Linux 5
    Error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Primary Database Entries:
    Tnsentry:
    SONYPRD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)(UR=A)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listner Entry:
    SID_LIST_SONYPRD =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtproc)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = SONYPRD)
    (GLOBAL_DBNAME = SONYPRD)
    Auxiliary Details:
    Tns Entry:
    SONYPRD =
    (DESCRIPTION =
    # (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listener Entry in auxiliary:
    SID_LIST_SONYPRDSTBY =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = SONYPRDSTBY)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = SONYPRDSTBY)
    TNSPING from Primary DB:
    [oracle@oracle11g ~]$ tnsping sonyprdstby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
    OK (0 msec)
    TNSPING from Auxuliary server
    [oracle@oracle11gstby ~]$ tnsping sonyprd
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
    OK (10 msec)
    Script Used for duplicate:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'sonyprd','sonyprdstby'
    set db_unique_name='sonyprdstby'
    set db_file_name_convert='/sonyprd/','/sonyprdstby/'
    set log_file_name_convert='/sonyprd/','/sonyprdstby/'
    set control_files='/u01/app/oracle/oradata/control01.ctl'
    set log_archive_max_processes='5'
    set fal_client='sonyprdstby'
    set fal_server='sonyprd'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
    set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
    Tried the script from both Primary and auxiliary but no luck
    [oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: SONYPRD (DBID=3131093559)
    connected to auxiliary database: SONYPRD (not mounted)
    Listener Status from primary:
    [oracle@oracle11g ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-DEC-2012 17:42:17
    Uptime 1 days 0 hr. 26 min. 41 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
    Services Summary...
    Service "sonyprd.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    Service "sonyprdXDB.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Listener Status from Standby when database bring to Nomount state:
    [oracle@oracle11gstby admin]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 21-DEC-2012 16:13:47
    Uptime 0 days 1 hr. 58 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
    Services Summary...
    Service "sonyprdstby" has 1 instance(s).
    Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
    The command completed successfully
    Please provide any work arounds to proceed further in creating the standby database.
    Thanks,
    Ram.

    Pl do not post duplicates - Issue in configuring Standby Database from Active database in 11g by RMAN

  • Creating Standby for RAC ASM database using RMAN

    We are having a Primary Site of 3-Node RAC ASM and we takes daily RMAN backup with the following script
    run
    allocate channel c1 device type disk format 'g:\rmanbackup\%U';
    backup database;
    backup archivelog from time 'trunc(sysdate-1)' until time 'sysdate';
    We have configured 3-Node RAC Cluster in Standby site. We have copied the rman backup folder to one of the Nodes in the Standby site.
    Request your help to restore the RMAN backup. The backup size is around 200GB. We do not know how to use DUPLICATE DUPICATE option in RMAN as if it is restoring from the Primary Location, then transferring 200GB over the network will not be possible.
    We need a solution to restore it directly from the Backup folder available in the DR Server. We are not using catalog.
    OS : Windows IA 64-bit
    RDBMS : Oracle 10.2.0.4
    Storage : ASM
    DB Nodes at Primary Site, Node1, Node2, Node3
    DB instances at primary site : ORCL1, ORCL2, ORCL3
    DB Nodes at Standby Site, Node101, Node102, Node103
    DB instances at Standby site : ORCL1, ORCL2, ORCL3
    DB Name : ORCL on both the sites.

    When you create the standby, you can use catalogued backups, stored somewhere local to your standby servers.
    For that, they need to be copied to the standby server, or taken from production there, and after restoring the standby controlfile on the standby server, use rman to catalogue the backups to be used. Then, you can use DUPLICATE... and it will be reading your local backup files.
    The directory g:\rmanbackup of your rman script is local to standby servers ?
    The docs for this have a lot of details: http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
    Regards.

  • Standby database from RMAN backup

    I have been assigned to create a standby database from our RMAN backups in a different machine, as this is my first attempt at recovering, I am struggling a bit. I would appreciate if someone can throw any light on what dumb mistakeI am doing here. I ahve absolutely no control over the back up script which is done by my vendor, but can do anything in the reocvery portion. I did try going through the documentaiton and other help available for the last 2 days.
    Database : Oracle 10G R2
    OS : Windows Server 2003
    My backup script is
    configure channel device type disk format 'J:\RMAN\RMAN_df_%U' maxpiecesize 2048M;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup database;
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    SQL "ALTER SYSTEM SWITCH LOGFILE";
    backup current controlfile for standby FORMAT='J:\RMAN\RMAN_sc_%U';
    For recovery of a standby database,
    I have copied the the back up pieces and the archive logs to the standby server where I have just created an instance with the same name as production db.
    set ORACLE_SID=NGINPROD
    set dbid 820336652
    STARTUP NOMOUNT
    RESTORE STANDBY CONTROLFILE FROM 'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    CATALOG BACKUPPIECE 'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_5_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_6_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2RMIUIE4_7_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_2_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_3_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2SMIUJ88_4_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_DF_2TMIUJLN_1_1',
    'I:\TEMP\RMAN_Backup\RMAN\RMAN_SC_2UMIUJM1_1_1';
    RESTORE DATABASE;
    Till this step I do not encounter any issues, but when i try to recover the database I am hit with the below error.
    RMAN> recover database;
    Starting recover at 16-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    unable to find archive log
    archive log thread=1 sequence=253340
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/16/2011 09:31:57
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 253340 lowscn 4696173517
    ------------------------------------------------------------------------------------------------------------------------------------------------

    Here's the standard dcoumentation on the procedure :
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm#i636377
    Appendix "F Creating a Standby Database with Recovery Manager" of the "Oracle® Data Guard Concepts and Administration" guide.
    I don't see ArchiveLog backups being done by the vendor's script. How do you backup the ArchiveLogs ?
    In your post you state that you have copied the ArchiveLogs. Are they copied to the same log_archive_dest location ? RMAN needs to be "aware" of them. You can use the "CATALOG" command in RMAN to register them into the controlfile.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
    A Standby Database uses a Standby Controlfile which is created from the Primary (with the "ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'locaion';" command) and then copied over to the Standby server.
    Hemant K Chitale

  • Creating standby database using data guard.

    Current Env:
    Oracle 11.2.0.1
    ASM
    Size 1.7T and growing.
    I'm rebuilding a standby database and need to use rman because of a few factors. In the past, I did a file copy create a standby control file config init.ora and it always worked.
    We have a database and had the stanby build; but someone issued a flashback and corrupted the standby database.
    Because of the size 1.7T and growing and we are now using ASM.
    My research is only showing building standby through rman using dupicate database command.
    I would like to copy the cold backup to a external drive and ship it to the standby site where I'll do the restore. This is because of time and bandwith required to rebuild the standby will interfere with operaitions for the period the files are being copied.
    So what would be the high level steps.
    1) get the cold backup
    2) create the standby control file
    3) ship the data via corrier
    4) restore the database
    5) and this is where i'm not sure. recover the standby control file - but during the restore of the database the "normal" control file will open and perhaps do a checkpoint. therefore the standby controlfile will be usless.
    6) recover the standby database.
    Has anyone accomplished this?
    As much specifics will be helpful. This system is operational and needs to be done right the first time.
    thanks,
    -Rob

    Thank you.
    1) I'm going to off load the cold backup to an external drive and have a courier take it to the DR site.
    Why, we are replicating the SAN over to the DR site. When SAN replication backs up Oracle becomes non-responsive. Therefore; sending the data over the pipe is not an option for the standby rebuild. Yea' that's the easy way to do it. But this system is operational and critical to operations; so we will not risk saturating the pipe for any period of time. The pipe got saturated one time and it was not pretty.
    2) I'm running the test in my lab to make sure I can create the standby database using the cold backup and rman.
    3) In the past it was easy; I got a cold backup of the data files using the same ksh scripts that have been working for 20 years. Copy the files over to the standby site, and put it into managed recovery. This technique has been working fine sense Oracle 8i days. ASM through a huge monkey wrench in the ksh script backup and now I'm forced to use rman. Hey, I'm told it's an okay product but when it comes to backups I never get fancy; that just makes things more complicated. Okay I wont complain about asm anymore, i guess there is an advantage in there somewhere.
    -Rob

  • Creation of Standby Database through Rman.

    Hi Everybody,
    Oracle Ver: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    Os: Windows Xp
    I am trying to create a standby database with the help of Rman..
    but when i am trying to invoke the Rman Executable and connect to the primary and auxillary database ie:standby
    it's giving me the following error...........
    C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 09:28:08 2008
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: PRIMARY (DBID=1503515402)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04006: error from auxiliary database: ORA-12541: TNS:no listenerI have restarted my listener service but still getting the error...
    here is my Listener.ora entries...........
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1525))
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = PRIMARY)
          (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
    standby=
    (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = DPC-010420)(PORT = 1526))
    SID_LIST_standby =
      (SID_LIST =
        (SID_DESC =
          (SID_NAME = standby)
          (ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
      )any help appreciated
    Regards,
    Prosenjit Mukherjee

    Hi Hemant,
    It worked...when I i issued the command as mentioned by you it started the Listener..
    lsnrctl start standby
    Now I am able to connect to both the Database using Rman..
    C:\Documents and Settings\prosenjit>rman target system/manager@primary auxiliary system/manager@standby
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Oct 2 10:55:08 2008
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database: PRIMARY (DBID=1503515402)
    connected to auxiliary database: STANDBY (not mounted)
    RMAN>Thanks for the Input...
    Is there any way by which i can start both the Listener with "lsnrctl start"...........instead of manually starting individual listener's
    Regards,
    Prosenjit Mukherjee
    Edited by: Prosenjit on Oct 2, 2008 11:01 AM

  • How do I move databases using RMAN with minimal downtime ?

    How can I do the following using RMAN ?
    DB version 10.2.0.4
    Redhat 5.2
    I am not using an rman catalogIn the past I have moved large databases from 1 server to another with 5 minutes downtime using backups done the old way by putting tablespaces in backup mode and making copies of the datafiles.
    I used the following method :
    ========> Part 1
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE set DATABASE "VPMY" RESETLOGS ARCHIVELOG
    MAXLOGFILES 32
    MAXLOGMEMBERS 3
         ....etc
    LOGFILE
    ......... log file names
    DATAFILE
    ... list of datafiles
    CHARACTER SET US7ASCII;
    ========> Part 2
    Up until the scheduled downtime, I would copy the archive logs from the production server to the new and run the following to apply the latest archive logs:
    RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
    ->AUTO<-
    ========> Part 3
    After applying the last archive log while in restrict mode -
    ALTER DATABASE OPEN resetlogs;
    My question is, how do I do Part 2 in RMAN. I have managed to duplicate databases and restore databases using rman to a different server, but this obviously only covers the data upto the backup point. How can I do the above parts 1 -3 with downtime of about 5 minutes like I have done using old methods ?
    Any help is much appreciated/

    you should be able to recover as you go with rman as well..
    copy the archived logs from A to B and apply them as they come in.
    run
    set until sequence x thread 1;
    recover database;
    if you're not opening the database after recovery you can just increment the set until sequence as the logs come in and do a new recovery.

Maybe you are looking for