Cloning with rman

Hi all,
cloning the database using rman.
i configure everything and finally executed
RMAN> duplicate target database to 'clone';
It have executed. but because of some problem with naming convention of directories it is cancelled.
I resoleved that and connected to target database
RMAN>connect target sys/oracle@sales;
and connected to auxiliary
RMAN> connect target sys/oracle@clone;
but it is connecting to sales instance only.
so when i executed
RMAN>duplicate target database to 'clone'
it is saying database name mismathes, auxiliary instance has sales, command specifies clone.
How can i resolve it. thank you!

RMAN> connect target sys/oracle@clone;the clone tns service is for auxiliary, then why you mentioned target again?
It should as below
rman target sys/oracle@sales auxiliary sys/oracle@clone;(or)
from auxiliary server
$ rman target sys/oracle@sales auxiliary /
RMAN> duplicate target database to 'clone';Always run duplicate from auxiliary/clone server, to avoid much pressure on target/primary.
Edited by: CKPT on Dec 12, 2011 1:51 PM

Similar Messages

Oracle Apps 11i Cloning with +ASM 10g Database

Hi,
Can somebody help Apps cloning on the issue facing. Please provide in detailed process Apps Cloning with +ASM.
Trying to Clone 11i Apps environment(11.5.10.2) and Db 10.2.0.4. The database is on +ASM.
1. Copied all the application files from SOURCE to TARGET ( source and target are different servers)
2. Database restored from source and the TARGET database is up and running( Database servers TARGET and SOURCE are 2 different servers.
3. As per doc id 230672.1 , preclone was successful in apps and db servers.
ISSUE:
=====
As per doc id 230672.1 , if we run adcfgclone on database server that messedup the database which is running already on the TARGET server, because adcfgclone recreate control files and all which is already intact for us in +ASM.
Question:
======
1. do we still need to do anything on the TARGER database server? if need to run , please provide the detailed steps
2. Do we need to run adcfgclone on apps server? please provide the detailed steps.
Thank You,
Dheeru.

Yes, restored and the database is up and running.
Then i ran adcfgclone dbtier on database which messedup whole database. Deleted all the file in ASM disk groups and try to restore the database threw RMAN.
Got new error, Please see below.
In the first run previously i got same error but fixed by creating control_files='+LASR','+FLASH' in pfile, again it's giving same error.
Also pasting PFILE.
Any idea on this.
Recovery Manager: Release 10.2.0.4.0 - Production on Wed Jan 5 17:15:12 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: LASRT (DBID=1482364021)
connected to auxiliary database: LASRX (not mounted)
RMAN>
RMAN> 2> 3> 4> 5> 6> 7> 8> 9>
executing command: SET until clause
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=872 devtype=DISK
allocated channel: aux2
channel aux2: sid=871 devtype=DISK
Starting Duplicate Db at 05-JAN-11
contents of Memory Script:
set until scn 11188183994442;
set newname for clone datafile 1 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 4 to new;
set newname for clone datafile 5 to new;
set newname for clone datafile 6 to new;
set newname for clone datafile 7 to new;
set newname for clone datafile 25 to new;
set newname for clone datafile 26 to new;
set newname for clone datafile 38 to new;
set newname for clone datafile 43 to new;
set newname for clone datafile 44 to new;
set newname for clone datafile 45 to new;
set newname for clone datafile 46 to new;
set newname for clone datafile 47 to new;
set newname for clone datafile 48 to new;
set newname for clone datafile 49 to new;
set newname for clone datafile 50 to new;
set newname for clone datafile 51 to new;
set newname for clone datafile 52 to new;
set newname for clone datafile 53 to new;
set newname for clone datafile 54 to new;
set newname for clone datafile 55 to new;
set newname for clone datafile 56 to new;
set newname for clone datafile 57 to new;
set newname for clone datafile 58 to new;
set newname for clone datafile 59 to new;
set newname for clone datafile 60 to new;
set newname for clone datafile 61 to new;
set newname for clone datafile 62 to new;
set newname for clone datafile 63 to new;
set newname for clone datafile 64 to new;
set newname for clone datafile 65 to new;
set newname for clone datafile 66 to new;
set newname for clone datafile 67 to new;
set newname for clone datafile 68 to new;
set newname for clone datafile 69 to new;
set newname for clone datafile 70 to new;
set newname for clone datafile 71 to new;
set newname for clone datafile 72 to new;
restore
check readonly
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 05-JAN-11
channel aux2: starting datafile backupset restore
channel aux2: specifying datafile(s) to restore from backup set
restoring datafile 00003 to +LASR
restoring datafile 00004 to +LASR
restoring datafile 00006 to +LASR
restoring datafile 00007 to +LASR
restoring datafile 00025 to +LASR
restoring datafile 00045 to +LASR
restoring datafile 00046 to +LASR
restoring datafile 00049 to +LASR
restoring datafile 00051 to +LASR
restoring datafile 00053 to +LASR
restoring datafile 00054 to +LASR
restoring datafile 00058 to +LASR
restoring datafile 00060 to +LASR
restoring datafile 00062 to +LASR
restoring datafile 00064 to +LASR
restoring datafile 00066 to +LASR
restoring datafile 00068 to +LASR
restoring datafile 00070 to +LASR
restoring datafile 00071 to +LASR
restoring datafile 00072 to +LASR
channel aux2: reading from backup piece /ora_export/lasrx/15m16kuo_1_1
channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +LASR
restoring datafile 00002 to +LASR
restoring datafile 00005 to +LASR
restoring datafile 00026 to +LASR
restoring datafile 00038 to +LASR
restoring datafile 00043 to +LASR
restoring datafile 00044 to +LASR
restoring datafile 00047 to +LASR
restoring datafile 00048 to +LASR
restoring datafile 00050 to +LASR
restoring datafile 00052 to +LASR
restoring datafile 00055 to +LASR
restoring datafile 00056 to +LASR
restoring datafile 00057 to +LASR
restoring datafile 00059 to +LASR
restoring datafile 00061 to +LASR
restoring datafile 00063 to +LASR
restoring datafile 00065 to +LASR
restoring datafile 00067 to +LASR
restoring datafile 00069 to +LASR
channel aux1: reading from backup piece /ora_export/lasrx/16m16kuo_1_1
channel aux1: restored backup piece 1
piece handle=/ora_export/lasrx/16m16kuo_1_1 tag=TAG20110103T144231
channel aux1: restore complete, elapsed time: 00:18:55
channel aux2: restored backup piece 1
piece handle=/ora_export/lasrx/15m16kuo_1_1 tag=TAG20110103T144231
channel aux2: restore complete, elapsed time: 00:21:20
Finished restore at 05-JAN-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "LASRX" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 2
MAXDATAFILES 72
MAXINSTANCES 1
MAXLOGHISTORY 7303
LOGFILE
GROUP 1 SIZE 20 M ,
GROUP 2 SIZE 20 M ,
GROUP 3 SIZE 20 M
DATAFILE
'+LASR/lasrx/datafile/system.331.739646133'
CHARACTER SET WE8ISO8859P1
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/05/2011 17:36:50
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01276: Cannot add file +LASR/lasrx/controlfile/current.332.739640887. File has an Oracle Managed Files file name.
=======================================================================
PFILE
====
*.aq_tm_processes=2
*.audit_file_dest='/10g/app/oracle/admin/lasrx/adump'
*.background_dump_dest='/10g/app/oracle/admin/lasrx/bdump'
*.compatible='10.2.0'
*.core_dump_dest='/10g/app/oracle/admin/lasrx/cdump'
*.control_files='+LASR','+FLASH'
*.db_block_size=8192
*.db_cache_size=318767104
*.db_create_file_dest='+LASR'
*.db_domain=''
*.db_file_multiblock_read_count=8
*.db_files=500
*.db_name='LASRX'
*.db_recovery_file_dest='+FLASH'
*.db_recovery_file_dest_size=5120M
*.dml_locks=5000
*.job_queue_processes=0
*.local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=hct431oractd002.mfia.state.mi.us)(PORT=1524))'
*.log_archive_dest_1='LOCATION=+FLASH/LASRX'
*.log_archive_format='%t_%s_%r.arc'
*.log_buffer=30551040
*.log_checkpoint_interval=100000
*.log_checkpoint_timeout=72000
*.log_checkpoints_to_alert=TRUE
*.max_dump_file_size='20480'
*.nls_comp='binary'
*.nls_date_format='DD-MON-RR'
*.nls_language='american'
*.nls_length_semantics='BYTE'
*.nls_numeric_characters='.,'
*.nls_sort='binary'
*.nls_territory='america'
*.O7_DICTIONARY_ACCESSIBILITY=FALSE
*.open_cursors=500
*.open_links=20
*.parallel_max_servers=12
*.parallel_min_servers=0
*.pga_aggregate_target=681574400
*.processes=800
*.query_rewrite_enabled='TRUE'
*.remote_login_passwordfile='EXCLUSIVE'
*.resource_manager_plan=''
*.session_cached_cursors=100
=============================

R12 clone with RMAN auxiliary db.

Hi all,
We require daily clone for our setup due to testing and other reason. Can we replace only database via RMAN Clone?
R12 clone with RMAN Auxiliary DB. Find below steps, if I am wrong correct me.
1.     run autoconfig on apps tier.
2.     perl <AD_TOP>/bin/admkappsutil.pl and Synchronize appsutil on db tier.
3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)
4.     adpreclone.pl dbTier
5.     adpreclone.pl appsTier
6.     copy source to target including db and apps tiers.
7.     perl adcfgclone.pl dbTechStack .
8.     create duplicate db (auxiliary db) from rman backup.
9.     sqlplus "/ as sysdba" @adupdlib.sql so
10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )
11.     exec FND_CONC_CLONE.SETUP_CLEAN;
12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)
13.     perl adcfgclone.pl appsTier
please correct my steps.
thanks in advance,
sandeep

Hi,
3.     Run autoconfig on dbtier or adconfig.sh <contextfile>) (which is correct? i am using autoconfig not with contextfile)Run $ORACLE_HOME/appsutil/bin/adconfig.sh contextfile=$CONTEXT_FILE appspass=apps -- See (Note: 603104.1 - Troubleshooting RapidClone issues with Oracle Applications R12) for details.
10.     perl adcfgclone.pl dbconfig <CONTEXT_NAME.xml> (This gives error, I am skipping this step. I have tried with perl adcfgclone.pl database but then also its give error. )What is the error?
12.     perl adcfgclone.pl dbTier (if we run perl adcfgclone.pl dbTechStack ,Is this step require?)After running "perl adcfgclone.pl dbTechStack", you need to run "perl adcfgclone.pl dbconfig <Database target context file> -- See (Note: 406982.1 - Cloning Oracle Applications Release 12 with Rapid Clone) and (Note: 799735.1 - Rapid Clone Documentation Resources, Release 11i and 12) for details.
Regards,
Hussein

Apps Cloning using RMAN

Hi,
I am doing Apps 11i cloning with rapidclone.
I have cloned the database using RMAN.
As per the metalink note 230672.1 I have to run following script on DB node.
perl adcfgclone.pl dbconfig <target context file>
However I dont have the context file for the new instance.
Should I copy the context file (for DB) from source instance , rename it and use it?
If I run the adcfgclone.pl using the source instance context file (present in the target db node), it throws
error for database connection.
Platform - Oracle Ebusiness Suite 11.5.10 on Oracle enterprise Linux 4 and Oracle 9i database.
Pls advice.
Thanks,
rane

However I dont have the context file for the new instance.Did you run "perl adcfgclone.pl dbTechStack" before issuing "perl adcfgclone.pl dbconfig <target context file>"? This should create the context file for you.
Should I copy the context file (for DB) from source instance , rename it and use it?No.
If I run the adcfgclone.pl using the source instance context file (present in the target db node), it throws
error for database connection.This is an expected behavior since the context file of the source node cannot be used on the target node.

Got error while recover controlfile with rman

Dear all,
My controlfile and some datafiles were crash and i tried to recover their with rman as the following step:
1. startup nomount;
2. restore controlfile from autobackup;
3. alter database mount;
4. restore database;
5.SELECT archivelog_change#-1 FROM v$database;
ARCHIVELOG_CHANGE#-1
1301671
6.run {
set until scn 1301671;
recover database;
executing command: SET until clause
Starting recover at 01 พ.ย. 2006
using channel ORA_DISK_1
starting media recovery
media recovery failed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 11/01/2006 15:38:01
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver if needed
start until change 1301671 using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-01190: controlfile or data file 1 is from before the last RESETLOGS
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\DB01\SYSTEM01.DBF'
What happend? Please give me some advise.
Thaks for advance !
Chara

After every resetlogs you have to take fresh backup.
It seems you have opened your database in resetlogs and your backup is prior to this resetlogs.So the controlfile is showing inconsistance with the other datafiles.

Migrating with RMAN from 10g to 11g

Hi gurus,
I am following the following procedure to migrate database from 10g to 11g using rman
Source side:
RMAN>connect target
RMAN>backup database;
RMAN>backup archivelog all;
RMAN>backup current controlfile;
SQL> create pfile from spfile;
Copied datafile, archivelog backup files and pfile and password files to target side. i.e. on 11g server side
Target side:
Set proper parameters for 11g
SQL>startup nomount;
RMAN>connect target
RMAN>set dbid=<source database id>
RMAN>catalog start with '<rman backup file location';
RMAN>restore controlfile;
RMAN>run
set newname for datafile 1 to '<target datafiles location with file name';
restore database;
switch datafile all;
finished
upto now it's success full when i am trying to recover
RMAN>recover database;
it is saying
rman 00571
rman 00569
rman 00571
rman 03002
ora - 19698
can you please suggest the solution for this.
thanks a lot.

I'm not sure what you're doing is supported.
You are taking a 10g database and restore and recover it using 11g software.
I think you are allowed to do that with 10g software only.

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

Logical Standby recover with RMAN

Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data Guard

Hello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg

How to start with RMAN as I am beginner?

Dear all,
How to start with RMAN as I am beginner? Any simple document or guide line for me.
Thanks,
Amy

How to start with RMAN as I am beginner? Any simple
document or guide line for me.go to yours oracle home directory /orahome/bin there is RMAN exe tool run it it will show you prompt RMAN
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
RMAN> connect target sys/sys
connected to target database: ORCL (DBID=1171886541)
RMAN> backup database
2> ;
Starting backup at 21-JAN-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\SYSAUX01.DBF
input datafile fno=00005 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\EXAMPLE01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\UNDOTBS01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.1.0\ORADATA\ORCL\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 21-JAN-08
channel ORA_DISK_1: finished piece 1 at 21-JAN-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NNNDF_TAG20080121T135924_3S8QQF74_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current controlfile in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 21-JAN-08
channel ORA_DISK_1: finished piece 1 at 21-JAN-08
piece handle=C:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2008_01_21\O1_MF_NCSNF_TAG20080121T135924_3S8QSSN4_.BKP comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 21-JAN-08
http://www.orafaq.com/faq/rmanKhurram

Auxiliary channel allocation in TSPITR with RMAN-managed instance

Hi,
I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
RMAN> RUN
2> {
3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
11> RELEASE CHANNEL c1;
12> RELEASE CHANNEL aux1;
13> }
allocated channel: c1
channel c1: sid=141 devtype=DISK
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
10.2.0.4, RHEL
Thanks,
Lukasz

What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
RUN
(new names, auxiliary parameter file)
RECOVER TABLESPACE ...
CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
Update:
Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
Thanks,
Lukasz
Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

Recovery with RMAN in case of complete lost of all files

Hi,
I am using RMAN in nocatalog mode to backup my databases to tape using the RMAN-Module for Legato.
I4ve read that in case of loosing all my controlfiles i cannot easily restore the controlfiles.
Lets assume the following scenario:
I am performing a daily full backup with RMAN in nocatalog mode. Approx. 2 hours after the completed backup my machine crashes and all files (i.e. OS-Files, Database, Controlfiles) are lost.
Now I have to reinstall the OS, reinstall Oracle and restore the backup.
Due to backups made with RMAN in nocatalog mode i have the restore the controlfies prior to restore the database. Metalink says restoring the controlfile from RMAN in nocatalog mode is not that easy.
Is there any way to restore the controlfile from RMAN in nocatalog mode in case of complete crash ??
Thanks.
Ronny.

RESTORE CONTROLFILE FROM 'filename...' doesn't appear to be supported in 8i.
What are the options for 8i?.
I have the backup sets with me from my previous installation before crash which also contains Control files.
However I am unclear as to how to proceed wit RMAN recovery with those files. There seems to be no way to point RMAN to those backupsets since RMAN apparently reads its information from catalog or the control file in case of nocatalog.
I think if there is a way to atleast restore the control file from the backup set, RMAN can proceed since it will find all the other backup details there.
Any help is greatly appreciated.
thanks
RP

Oracle 3113 creating a standby with rman

Hello,
environment is 11gR2 on Linux.
Tested on CentOS 5.5 as OS and local LAN as interconnect and the duplicate command terminates successfully in some minutes.
Same script but using oel 5.5 and a wan (3Mbit/s) and I keep getting 3113 errors after about 2h or 3h.
I suspect some timeout on wan (that is over vpn) but I would also like to trace something at my side.
I run a shell script with nohup and send it to background and this is the log, from which you can see the rman script:
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Sep 7 14:50:11 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN>
connected to target database: TESDB1 (DBID=11492743)
RMAN>
connected to auxiliary database: DUMMY (not mounted)
RMAN>
RMAN> run{
2> allocate channel prmy1 type disk;
3> allocate auxiliary channel stby1 type disk;
4> duplicate target database for standby from active database
5> spfile
6> parameter_value_convert 'TESDB1','TESDB1DR'
7> set db_file_name_convert='/TESDB1/','/TESDB1DR/'
8> set log_file_name_convert='/TESDB1/','/TESDB1DR/'
9> set 'db_unique_name'='TESDB1DR'
10> set control_files='/app/oradata/TESDB1DR/control01.ctl','/app/oradata/flash_recovery_area/TESDB1DR/control02.ctl'
11> set db_recovery_file_dest='/app/oradata/flash_recovery_area'
12> set DB_RECOVERY_FILE_DEST_SIZE='4977M'
13> nofilenamecheck;
14> }
using target database control file instead of recovery catalog
allocated channel: prmy1
channel prmy1: SID=12 device type=DISK
allocated channel: stby1
channel stby1: SID=135 device type=DISK
Starting Duplicate Db at 07-SEP-10
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /app/oradata/TESDB1DR/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting backup at 07-SEP-10
channel prmy1: starting datafile copy
input datafile file number=00003 name=/app/oradata/TESDB1/undotbs01.dbf
.. after about three hours (and 3.2Gb transferred) it continues with:
RMAN-03009: failure of backup command on prmy1 channel at 09/07/2010 17:53:49
RMAN-06136: ORACLE error from auxiliary database: ORA-03113: end-of-file on communication channel
Process ID: 3187
Session ID: 192 Serial number: 3
continuing other job steps, job failed will not be re-run
.. after 15 minutes:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/07/2010 18:09:35
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on clone_default channel at 09/07/2010 18:09:34
RMAN-10038: database session for channel clone_default terminated unexpectedly
RMAN> **end-of-file**
RMAN>
Recovery Manager complete.
the undo tbs is 3.2 Gb so I'm not sure if the 3113 happens at the end of copy... but the tablespace doesn't succeed
and the other jobs don't start even if it says "continuing other job steps"..
rman started at 14:50 and in listener at dr site I have:
Tue Sep 07 14:50:55 2010
07-SEP-2010 14:50:55 * service_update * TESDB1DR * 0
07-SEP-2010 14:50:55 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=oracle)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35240)) * establish * TESDB1DR * 0
Tue Sep 07 15:00:58 2010
07-SEP-2010 15:00:58 * service_update * TESDB1DR * 0
Tue Sep 07 16:35:04 2010
07-SEP-2010 16:35:04 * service_update * TESDB1DR * 0
Tue Sep 07 17:02:04 2010
07-SEP-2010 17:02:04 * service_update * TESDB1DR * 0
07-SEP-2010 17:02:10 * service_update * TESDB1DR * 0
Tue Sep 07 17:53:17 2010
07-SEP-2010 17:53:17 * service_update * TESDB1DR * 0
Tue Sep 07 18:09:00 2010
07-SEP-2010 18:09:00 * (CONNECT_DATA=(SERVICE_NAME=TESDB1DR)(CID=(PROGRAM=rman)(HOST=lb-orajde.boiron.ntm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=32610)) * establish * TESDB1DR * 0
In alert.log at dr site I have at 17:02 (about 50 minutes before error):
Tue Sep 07 15:05:01 2010
db_recovery_file_dest_size of 4977 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Sep 07 17:02:03 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:02:03
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.49.1.93)(PORT=35226))
some times (always at 17:02) and nothing more
In alert.log at primary site:
Tue Sep 07 14:50:36 2010
Clearing standby activation ID 11529351 (0xafec87)
The primary database controlfile was created using the
'MAXLOGFILES 16' clause.
There is space for up to 13 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;
Tue Sep 07 16:00:40 2010
Thread 1 advanced to log sequence 759 (LGWR switch)
Current log# 3 seq# 759 mem# 0: /app/oradata/TESDB1/redo03.log
Tue Sep 07 16:00:41 2010
Archived Log entry 528 added for thread 1 sequence 758 ID 0xafec87 dest 1:
In sqlnet.log of primary site:
Tue Sep 07 17:53:49 2010
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 07-SEP-2010 17:53:49
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.12.41)(PORT=1521))
and the same at 18:09
No other errors.
Any hints?
BTW: what is the minimum size of undo tbs? Can I have compression enabled also during duplication if transport service is configured with COMPRESSION=ENABLED, or does it count only when copying redo files?
Thanks in advance,
Gianluca

Thanks for your reply.
I will try your suggestion as it could come useful some time.
So with this alternate method at the end I would have standby aligned as of backup time, correct?
And after running something like this on standby:
SQL> alter database recover managed standby database disconnect from session;
It will begin to receive, archive and apply redo logs, correct?
Some answers regarding the original question. It was confirmed that there was a 2hours cut-off time at firewall level.
The first datafile that the rman session began to copy was 3.2Gb in size, taking more than 2 hours completing.
Monitoring with netstat on source and target I saw this at source during the duplicate process:
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
tcp 0 369240 10.49.1.93:50371 192.168.12.41:1521 ESTABLISHED
and the session bound to port 50371 was the only one pushing data (send queue not empty).
The other 3 ones I presume are for control of rman session. I get 3 sessions even if I open only one channel on primary side.
After the first datafile completes copy, a new session (with port 14871) is established substituting the other one.
The three initial ones instead remain for all the duplicate process.
tcp 0 487872 10.49.1.93:14871 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46626 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46627 192.168.12.41:1521 ESTABLISHED
tcp 0 0 10.49.1.93:46629 192.168.12.41:1521 ESTABLISHED
So after the copy of the first file, the session come back to one or more of the initial 3 ones, and they probably make a push-ack, got a 3113 as the firewall has silently cut them after 2 hours.... and the datafile, even if completed, is not marked as completed. A new run would copy again it...
Now the time has been put to 8hours, with 24hours being the maximum value set (no disable possible as far as the network guy said...).
And the duplicate completed correctly.
Would I have to fear any problems with this cut-off due to "normal" dataguard operations or not, in your opinion?
Thanks
Gianluca

Trying to restore a database with RMAN in new server

Hello,
Database: Oracle 10gR2
O/S: Windows Server 2003
My RMAN backuppieces are stored in a network drive:
\\old_location\FULL
and
\\old_location\INC
I'm trying to restore a whole database with RMAN in another server from my FULL backup.
For that, I copy all backuppieces files
from: \\old_location\FULL
to new server: D:\new_location\
Also I created the relevant folder hierarchy under <ORACLE_BASE> directory, as follows:
a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>\admin' directory
b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata' directory
c. pfile.ora and controlfile (CTL_MTDPROD_2308_20120401_1.CTL) are backup from original database and they are in D:\new_location\
d. I copied pfile.ora and controlfile to folder: C:\oracle\product\10.2.0\db_1\database\
I started creating an instance in new server from scratch:
C:\>oradim -new -sid MTDPROD -intpwd mtdprod
C:\> SET ORACLE_SID=MTDPROD
C:\> rman
RMAN> connect target sys
RMAN> SET DBID=21692876873
RMAN> STARTUP force nomount PFILE=C:\oracle\product\10.2.0\db_1\database\init_mtdprod.ora
RMAN> restore controlfile from 'C:\oracle\product\10.2.0\db_1\database\CTL_MTDPROD_2308_20120401_1.CTL';
RMAN> alter database mount;
#Since I want to read my backuppieces from D:\new_location and not from \\old_location\FULL then I catalog and restore like:
RMAN> catalog start with 'D:\new_location\';
RMAN> restore database;
Starting recover at 25/04/12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=541 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile copies to recover
recovering datafile copy fno=00003 name=D:\BD_MTDPROD\CONTROLFILES\SYSAUX01.DBF
recovering datafile copy fno=00004 name=D:\BD_MTDPROD\CONTROLFILES\USERS01.DBF
recovering datafile copy fno=00007 name=D:\BD_MTDPROD\DATAFILES_DATA\MSE.ORA
recovering datafile copy fno=00010 name=D:\BD_MTDPROD\DATAFILES_DATA\EXPEDIENTES2.ORA
channel ORA_DISK_1: reading from backup piece \\old_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: failover to piece handle=D:\new_location\FULL\FULL_MTDPROD_20120401_2304_1.BAK tag=TAG20120401T190004
.....(continues)
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\
Please, advice.

user521219 wrote:
Questions:
1. RMAN still reads from old_location. The only way to avoid that would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...." indicates that that file is not usefull? I just copy them from old_location to new_location... how can they get useless?
I suspect there is something in controlfile that redirects to \\old_location\FULL\ and doesn't let to read from D:\new_location\Is this a cold backup? Did you change the location of control file in your PFILE or is it still pointing to old location?
You may want to check the output of RESTORE DATABASE PREVIEW command, which will just report which backup files it uses without actually restoring thhe DB.

Physical Standby Database Creation with RMAN

Hi,
I'm in 10g on Linux. I want to create a standby database on another Linux server. I did not find a clear procedure to create it in Oracle® Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) Part Number B14191-02
and niether in Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-04
In the last one chapter 3 sends you to F appendix and F appendix says do nothing before having than all in chapter 3 :
In F.1.1 page F-2 it is said :
See Chapter 3 for a complete discussion of physical standby database preparation,including initialization parameter settings. You must perform all necessary preparation tasks described in these chapters before RMAN can successfully create the standby database files and mount the standby database.
Any way I'm looking for a procedure or clear article to create it.
Many thanks before.

Physical Standby Database Creation with RMAN
Use the DUPLICATE command.
Check out this metalink doc: Note:374069.1 and Note:118409.1
Message was edited by:
STW
Message was edited by:
STW

Duplicating DB with RMAN,DB mode:NOARCHIVE LOG?

Hello,
I want to get a duplicate database on a remote server machine with same file structure by using internet of VPN(virtual private network). My question is ...
can we duplicate the database to remote server if the Database is in NOARCHIVELOG MODE ??
I have surffed on net for the same i got the method to duplicated the database but not sure weather i can do that in noarchivelog mode !
Regarding the steps if anyone has some better ideas to perform duplication of Database with RMAN or any other tool let me know or any more optimized steps ....will be appreciated. But please keep this point that the database is in norachivelog mode.
ORACLE 10g R2
Windows server 2003 32bit
Thanks in advance....
Regards,
DBA4

If the database is in noarchivelog mode, then you can only take offline backup of database through RMAN in the mount state. Previously database shouldn't be shutdown
abnormally.
SQL> select LOG_MODE from v$database;
LOG_MODE
NOARCHIVELOG
1 row selected.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 209715200 bytes
Fixed Size                  1289748 bytes
Variable Size             138412524 bytes
Database Buffers           67108864 bytes
Redo Buffers                2904064 bytes
Database mounted.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
D:\Test>rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Mer. Mai 30 19:46:13 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: MIKA (DBID=1492747861, not open)
RMAN> backup database;Now move that backup to another machine, and restore this backup.
On the target machine, do the following steps:
D:\Test>rman target /
rman>RUN
STARTUP NOMOUNT FORCE;
allocate channel d1 type disk;
RESTORE SPFILE;
SHUTDOWN IMMEDIATE;
STARTUP NOMOUNT;
RESTORE CONTROLFILE;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
ALTER DATABASE OPEN RESETLOGS;
regardsregards

Cloning with rman

Similar Messages

Maybe you are looking for