Backup Physical Standby (Dataguard) using RMAN : Issues

Hello All,
I am running a RMAN backup on standby server using the command below. The RMAN backup is actually connecting to the primary database on another server, I found this very confusing and to reassure, i shutdown the primary database and ran the backup again. It fails with not able to conenct to target database. Can you please explain?
run {
allocate channel t1 type disk format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p';
allocate channel t2 type disk format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p';
recover copy of database with tag 'STDBY_PRODCDW';
backup as compressed backupset format '/backup/oracle/PRODCDW/RMAN/DBFILES_%d_t%t_s%s_p%p' tag 'STDBY_PRODCDW' incremental level 1 for recover of copy with tag 'STDBY_PRODCDW' database plus archivelog delete input;
}

I am not doing the image copy anymore, I am taking the RMAN incremental backups for the database. I am not getting any errors now but, Here is what I want to achieve:
I am running the RMAN backups on the standby database. I want to :
1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED/APPLIED to all my standby databases?
2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
Regards

Similar Messages

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

Backup physical standby database

Hi,
as for a backup & restore concept we are planning to implement a physical standby database using Oracle 10g on Sun Solaris.
The idea is to use the standby database as backup source.
What are the required steps and constraints, do i have to stop log apply during backups or change the database state from recovery mode ?
Thanks,
Robert

Hi,
Its a good way to reduce load of backup on Live node.
According to the your plan:
If the live node has failes Standby will be failed over or switched over to production.
Then through RMAN we can restore the standby database from It's backup , and the standby is back.
Is this correct/Feasible....?
Regards,
Ven.

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

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

Creating a Physical Standby Database using OEM GC

This Paper is about the creation of a physical Stanby Database using OEM GC.
You will see that there is really nothing to it and using the Data Guard Broker, performing a switchover is as easy as 1,2,3,.
BTW, this works in both OEM GC 10.2.0.5 and 11.1
http://oemgc.wordpress.com/2010/07/19/creating-a-physical-standby-database-using-oem-gc/

Thanks Rob for sharing this.
Regards
Rajesh

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

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 DB using RMAN in Oracle10.2 standard ediction

I am tring to create a standby DB in different host with different directory using RMAN. when I issued the command <duplicate target database for standby>, RMAN gave the error msg as follow:
Starting restore at 02-MAY-06
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=78 devtype=DISK
creating datafile fno=1 name=/export/database/oracle/HTS1/system01.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/02/2006 11:24:28
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/export/database/oracle/HTS1/system01.dbf'
Path '/export/database/oracle/HTS1' exists in the standby host and permission are granted, some initial parameter for standby DB was set to:
db_file_name_convert='/export/home/oracle/oradata/HTS1','/export/database/oracle/HTS1'
log_file_name_convert='/export/home/oracle/oradata/HTS1','/export/database/oracle/HTS1'
db_create_file_dest='/export/database/oracle/HTS1'
Can anyone shed some light on the cause of this error? Thanks
Jackson

I found the reason. it was because of the the backup set not available.
But after I prepare the backup set at hte primary host, rman still gave err msg:
RMAN> duplicate target database for standby;
Starting Duplicate Db at 02-MAY-06
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=78 devtype=DISK
contents of Memory Script:
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
Starting restore at 02-MAY-06
using channel ORA_AUX_DISK_1
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 /export/home/oracle/flash_recovery_area/HTS1/backupset/2006_05_02/o1_mf_ncnnf_TAG20060502T131953_25ftztpo_.bkp
ORA-19870: error reading backup piece /export/home/oracle/flash_recovery_area/HTS1/backupset/2006_05_02/o1_mf_ncnnf_TAG20060502T131953_25ftztpo_.bkp
ORA-19505: failed to identify file "/export/home/oracle/flash_recovery_area/HTS1/backupset/2006_05_02/o1_mf_ncnnf_TAG20060502T131953_25ftztpo_.bkp"
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
failover to previous backup

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

Data Guard - Physical Standby Setup by RMAN

I am trying to set up a physical standby using RMAN. After I brought up the standby db, I failed to turn on redo apply. I found out that the standby redo log files were not copied over to the standby.
The back up script I use is as follows.
run {
allocate channel ch2 type disk;
backup current controlfile for standby format '/backups/sitv/cf_%d_t%t_s%s_p%p';
backup format '/backups/sitv/%U.bkup' database;
sql 'alter system archive log current';
backup format '/backups/sitv/al_t%t_s%s_p%p.bkup' archivelog all;
release channel ch2;
What command should I use to be able to make a backup of the standby log files as well?
Thanks.

Hi Sybrand,
Thank for the reply. Let me give a little bit more detailed information on what I did.
I followed the documentation as follows to set up the physical standby
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I created the standby log files per section 3.1.3 on the primary db before the standby is created.
I used the following command to restore the standby on a different server.
run {
allocate auxiliary channel ch1 device type disk;
duplicate target database for standby dorecover nofilenamecheck;}
My question is the standby log files did not show up on the standby server. However, the log files showed in the v$logfile table. After I tured on the redo apply, the changes I made in primary db did not happen in the standby db.
Any idea on how to fix it?
Thanks.

Backup physical standby delete arch

Hi
I am scheduling hot backup for physical standby, the backup does backup database plus archivelog delete input...
my question is what if there is delay with apply process and the rman job back's up the archive log and removes them before they get aplplied to the standby?
is above described case a vlaid senario ? what can i do to avoid this ?
thanks

you said:
>
consider senario where logs are not shipped due to network issue ... so standby is couple of hours behind ....
and also we loss the primary !! how do you recover the gap between primary and stnadby ?
>
Let us just assume that:
1. Your Network Connection to the Standby interrupts
2. After a while, the Primary gets completely destroyed
Your solution to that would be to ship Archivelogs that you took on the Primary to the Standby? When where the Archivelogs taken?
Regardless of your concrete answer to that: You are encountering loss of transactional data with that 'solution' - the only question is: How much data do you lose?
In other words: This is not really a sensible solution to that assumed scenario.
Instead, the real solution would be to
a) Have multiple Standby Databases
b) Have at least redundant Network Connection to the one Standby
Instead of fixing your dysfunctional solution, you may better put your efforts on the implementation of a functional solution.
At least that is what I would recommend.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com
Edited by: Uwe Hesse on 30.07.2011 22:45
removed the Recover Primary part

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&#039;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

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?

To restore backup on different host using RMAN

Hi All,
Friend I need your help once again. I want to restore my database from the past backup to new HOST by keeping the original database intact using RMAN. Let me explain the scenario:-
Databas Version - 8.1.7
OS - Solaris 5.8
We are using RMAN with Tivoli as third party media management. I just need to restore the database from this tape library using RMAN with recovery catalog on new server. The only doubt I have is how I will make the backups of the production database whose backup has to be restored available on the new host where I have to create new database.
I will be using different file structure for the newly restored database. Do I have to create TDPO files seperately on the server on which I have to restore the database.
Please reply asap.
Regards
Harpreet Singh

You need to create a tdpo.opt file of source on the destination database. Then, allocate channel using this TDPO_OPTFILE and recover database.

Backup Physical Standby (Dataguard) using RMAN : Issues

Similar Messages

Maybe you are looking for