Cold backup restore to a different bit level

Hi all. I am planning for a coldback restore between two databases. The source db is 10.2.0.3 on 32-bit server Windows 2003 and the destination db is 10.2.0.4 on windows 64-bit. Is it possible to perform this restore? Also is RMAN restore possible? Thanks for any responses.

Hi, I performed a restore of cold backup from 10.2.0.3 database to 10.2.0.4 database on another server. I am receiving this error:
ORA-01503: CREATE CONTROLFILE failed
ORA-01159: file is not from same database as previous files - wrong database id
I am restoring only the schema specific datafiles from the old database and not system, sysaux files .. I understand that there is a mismatch here because the source datafiles are not compatible with the new system files. Any idea what can be done here to get around this error? I am trying to perform a clone of the database into another server. The database name is same.

Similar Messages

Cold backup restore on fail safe environment.

Hi,
The setup:
Windows 2008 with 2 node MSCS cluster in active/passive configuration.
Oracle Database 11.1.0.6 .
Oracle Failsafe 3.4.2
Database :test database; 2 in no. ,both Single instance. Both database are created with cold backup from production.
The Requirement:
To refresh both the test database with cold backup from the same production database as before. And then with the same cold backup create a physical standby database of the newly recreated testing database.
The Plan:
1.take all dbfile,controlfile,redologfiles,standbyredologfiles,tempfiles backup from production.
2.after taking the testing database offline from failsafe and normaly starting on node1; restore dbfile,controlfiles,redologs,srl,tempfiles to testing server. spfile should be properly pointing the new controlfile.
3.startup mount.
4.directory structure for control,redo,srl,dbfiles,tempfiles are diffrent.so,rename file for all dbfiles,redologs,srl,tempfiles.
5.creating a standby controlfile for creating physical standby db of this testing database.
6.open the database.
7.shutdown immediate.
8.start with failsafe.
The doubt:
1. is this plan ok for refresh of the test databases?
2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
Please note, the production database is only in picture while taking backup.
Please guys help me for clearing the said doubts.
regards.
g

The doubt:
1. is this plan ok for refresh of the test databases?
2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
Please note, the production database is only in picture while taking backup. You are taking cold backup, So the mentioned procedure you can follow. But ensure all the services/background processes related to database are not running.
Once you prepare Primary database, even from that database you can create standby control file, so that it will be used for standby database.
But i'm not aware of how fail safe it works, As per the core database part whatever the steps you mentioned, it looks fine.
Thank You.

Backup & restore catalog on different versions

Does anyone know if I can restore a catalog, made using File> Backup Catalog in PSE8, onto a PSE6 machine?
(I'd try it, except it's two hours drive away).

99jon wrote:
This will not work, at least on Windows, where the two versions have different file paths in ProgramData.
The catalog in PSE6 uses a PSEDB file stored in the Photoshop elements folder.
The catalog in PSE8 uses a PSE8DB file stored differently in the Elements Organizer folder.
Folder location of the catalog file is irrelevant here. The problem is that you cannot convert PSE8 catalog to PSE6. There is no function to do so in the PSE software.

Cold backup Restoration

Hi,
OS: IBM AIX
Oracle 10g.
My database is running in Archivelog mode.
I have to take coldbakup and restore in the new location.
I will use the following steps.
1. Shutdown immediate
2. tar (.dbf, ctr, redolog and archivelog)
Here I have doubt while restoring the database.
Is that necessary to apply archivelog while restoring the backup ( I hope it is not required)
Please suggest me.
Please provide me steps for backup and restore and recovery using coldbackup.
Thanks in advance
KSG

Hi, it is not necessary to restore archived redo logs if you only want to restore to the point of backup, otherwise it is necessary. Why are you using this method anyway and not using RMAN which would be far simpler ?
regards,
graham

RMAN backup restoration on a different server under ASM .

Hello Experts,
This is regarding new installation of Oracle RAC 11gR2 on AIX 6.1 . Its a two node cluster setup , using ASM . As i am newbie for RMAN , I would like to know how i can restore my rman backup to another uat server which has standby database again cofigured under asm .
Thanks for your kind help .

Hi ,
Thanks for reply
1) I performed the full database backup on source .
2) Source (prod) and target remote database (uat) are in ASM and have same DG for datafiles .
3) I have transfered the backup from production to UAT . I have already running uat database
do i need to drop it before i start the restoration ? My final purpose is just to refresh target with production backup . Kindly advice the steps from here to proceed with .
Thank you

Cold backup restore error

Hi,
i tried to restore coldbackup on solaris.while starting instance i got this error.
LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
ORA-01078: failure in processing system parameters
now in this path init file is there.
$ cd /oracle/app/oracle/product/9.2.0.8/dbs
$ ls
c-2448946487-20090420-00 init.ora initcdmsv1.ora lkCDMSP1 snapcf_cdmsp1.f spfilecdmsv1.ora
c-2448946487-20090421-00 initcdmsp1.ora initcdmsv1_bkup.ora lkCDMSV1 snapcf_cdmsv1.f
c-2448946487-20090422-00 initcdmsp1_bkup.ora initdw.ora orapwcdmsv1 spfilecdmsp1.ora
$
even tried with giving init path
SQL> startup pfile='/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora';
LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
ORA-01078: failure in processing system parameters
SQL> exit
but error is still there.on this server one db is there.for which it giving same error.
pls help me early as possible
Nareshs

s they are there
root@CDM-PRDR-OCLD-1 # cd cdmsp1
root@CDM-PRDR-OCLD-1 # ls
arch dcm.dbf ocl_dcmq.dbf ocl_li.dbf portal.dbf tms_clob1.dbf
attrs1_oid.dbf discopltc1.dbf ocl_dcmq_idx.dbf ocl_li_idx.dbf ptldoc.dbf tms_data1.dbf
b2b_dt.dbf discopltm1.dbf ocl_def.dbf ocl_lr.dbf ptlidx.dbf tms_idx1.dbf
b2b_idx.dbf drsys01.dbf ocl_def_idx.dbf ocl_lr_idx.dbf ptllog.dbf tools01.dbf
b2b_lob.dbf gcats1_oid.dbf ocl_des.dbf ocl_resp.dbf redo01_a.log uddisys01.dbf
b2b_rt.dbf gdefault1_oid.dbf ocl_des_idx.dbf ocl_resp_idx.dbf redo01_b.log undotbs01.dbf
bam.dbf ias_meta01.dbf ocl_disc.dbf ocl_temp1.dbf redo02_a.log users01.dbf
battrs1_oid.dbf indx01.dbf ocl_disc_idx.dbf ocl_test_data.dbf redo02_b.log wcrsys01.dbf
bc4j_internal_data.dbf oca.dbf ocl_disc_rep_data.dbf ocl_test_index.dbf redo03_a.log xdb01.dbf
control01.ctl ocl_app.dbf ocl_dx_index_data.dbf ocl_vrv.dbf redo03_b.log xdb02.dbf
control02.ctl ocl_app_idx.dbf ocl_dx_table_data.dbf ocl_vrv_idx.dbf svrmg1_oid.dbf
control03.ctl ocl_dcd.dbf ocl_glib.dbf orabpel.dbf system01.dbf
cwmlite01.dbf ocl_dcd_idx.dbf ocl_glib_idx.dbf oss_sys01.dbf temp01.dbf

COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

제품 : ORACLE SERVER
작성날짜 : 2002-04-09
COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
======================================================================
PURPOSE
COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
과정을 TEST로 확인하여 본다.
Examples
No Archive log mode.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> select count(*) from emp3 ;
COUNT(*)
0
SQL> select count(*) from emp4 ;
COUNT(*)
0
Cold backup을 받은후 Archive log mode 변경한 경우
SVRMGR> startup mount
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
SVRMGR> alter database open ; => archive log mode 변경.
SQL> select * from tab ;
TNAME TABTYPE CLUSTERID
EMP TABLE
EMP1 TABLE
EMP2 TABLE
EMP3 TABLE
EMP4 TABLE
10 rows selected.
SQL> insert into emp3 select * from emp ;
14 rows created.
SQL> commit ;
Commit complete.
SQL> insert into emp4 select * from emp1 ;
71680 rows created.
SQL> commit ;
Commit complete.
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
## log switch 발생.
SVRMGR> alter system switch logfile ;
SQL> insert into emp3 select * from emp ; -- current log에 반영.
14 rows created.
SQL> commit ;
SQL> select count(*) from emp3 ;
COUNT(*)
28
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# ALL DATABASE CRASH #
# recover 과정... #
1. Restore Cold-backup
2. modify initSID.ora
log_archive_start = true
log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
3. svrmgrl
Statement processed.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> archive log list
Database log mode No Archive Mode
Automatic archival Enabled
Archive destination D:\Oracle\oradata\SNAP\archive
Oldest online log sequence 26
Current log sequence 28
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
ORA-00280: change 340421 for thread 1 is in sequence #28
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
ORA-00280: change 340561 for thread 1 is in sequence #29
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
ORA-00280: change 340642 for thread 1 is in sequence #30
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
ORA-00280: change 340723 for thread 1 is in sequence #31
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
Log applied.
ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
ORA-00280: change 340797 for thread 1 is in sequence #32
ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
r needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SVRMGR> alter database open resetlogs ;
Statement processed.
SVRMGR>
SQL> connect scott/tiger
SQL> select count(*) from emp3 ;
COUNT(*)
14
SQL> select count(*) from emp4 ;
COUNT(*)
71680
# 결론...... #
따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
가능하다.
# 주의 사항 #
cold backup을 restore한 후 database open후 shutdown 한 다음 archive
log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
주의하여야 한다.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
Database opened.
SVRMGR> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SVRMGR> startup mount
ORACLE instance started.
Total System Global Area 40703244 bytes
Fixed Size 70924 bytes
Variable Size 23777280 bytes
Database Buffers 16777216 bytes
Redo Buffers 77824 bytes
Database mounted.
SVRMGR> alter database archivelog ;
Statement processed.
SVRMGR> recover database using backup controlfile until cancel ;
ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
ORA-00280: change 339542 for thread 1 is in sequence #3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00283: recovery session canceled due to errors
ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
240], [], []
SVRMGR> exit
Server Manager complete.
Rederence Documents
---------------------

Partition Restore Cold Backup Different System and Different Version DB

Is it possible, can we restore the cold backup at different database version and different operating system(but same ENDIAN_FORMAT) ????????
My original system HP-UX (64-bit) and database version 10.2.0.3.0 i have cold backup and i want to partion restore on Linux Redhot 5.5 (64-bit), database version 10.1.0.4.0 .
If it is possible. How can i do this.

My original system HP-UX (64-bit) and database version 10.2.0.3.0 i have cold backup and i want to partion restore on Linux Redhot 5.5 (64-bit), database version 10.1.0.4.0 .1. AFAIK you can not do it i mean wiht cold backup move from HP to linux
2. You can try to use exp-imp if you want to change db version.
See below notes:
Master Note For Oracle Database Upgrades and Migrations [ID 1152016.1]
Different Upgrade Methods For Upgrading Your Database [ID 419550.1]
Regard
Helios

Problem with restoring a database from cold backup

All,
I've got a 10.2.0.4 database that we perform a cold backup on every night with RMAN. On Sunday 2/21, we have level 0 backup. On Monday-Wednesday nights, we take a cold level 1. We also perform a controlfile auto backup each night.
On a second server where I want to restore the database (same version of Oracle 10.2.0.4), I've copied the control file auto backups, the level 0 and the most recent level 1. I now want to restore. I use an RMAN script similar to the following to restore the control files:
connect target /;
set dbid 1973354860;
# Restore the controlfile from the tag that auto backed up the controlfile at the end of the level 0
run
startup nomount;
allocate channel c1 type disk;
restore controlfile to '/u01/app/oracle/oradata/ORADB1/control01.ctl' from AUTOBACKUP;
restore controlfile to '/u02/app/oracle/oradata/ORADB1/control02.ctl' from AUTOBACKUP;
restore controlfile to '/u03/app/oracle/oradata/ORADB1/control03.ctl' from AUTOBACKUP;
release channel c1;
shutdown immediate;
After the control files restore successfully, I perform some RMAN checks to ensure that all of the files I need for a recovery are there. The RMAN> list backup of database; command shows all of my backup savesets as AVAILABLE for the level0 and level1 backups.
I then try a restore database command; and get the following errors:
RMAN> run
2> {
3> allocate channel c1 type disk;
4> allocate channel c2 type disk;
5> allocate channel c3 type disk;
6> allocate channel c4 type disk;
7> restore database from tag='TAG20100221T200045';
8> }
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=74 devtype=DISK
allocated channel: c2
channel c2: sid=70 devtype=DISK
allocated channel: c3
channel c3: sid=166 devtype=DISK
allocated channel: c4
channel c4: sid=168 devtype=DISK
Starting restore at 25-FEB-10
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2010 13:33:19
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN>
But I know from the RMAN crosscheck and list backup commands that the savesets are available on disk. For example:
RMAN> list backup of datafile 1;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4875 Incr 0 4.37G DISK 00:22:53 21-FEB-10
BP Key: 4875 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185
List of Datafiles in backup set 4875
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 5086110241948 21-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4894 Incr 1 1.92G DISK 00:13:46 24-FEB-10
BP Key: 4894 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434
List of Datafiles in backup set 4894
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 5086113791743 24-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
RMAN> list backup of datafile 44; (the first one in the list above)
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4872 Incr 0 7.15G DISK 00:35:17 21-FEB-10
BP Key: 4872 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4927_piece_1_date_20100221_711576046
List of Datafiles in backup set 4872
File LV Type Ckp SCN Ckp Time Name
44 0 Incr 5086110241948 21-FEB-10 /u04/app/oracle/oradata/ORADB1/NETINSIGHT_INDEXES_03.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4893 Incr 1 4.06G DISK 00:26:52 24-FEB-10
BP Key: 4893 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4947_piece_1_date_20100224_711835238
List of Datafiles in backup set 4893
File LV Type Ckp SCN Ckp Time Name
44 1 Incr 5086113791743 24-FEB-10 /u04/app/oracle/oradata/ORADB1/NETINSIGHT_INDEXES_03.dbf
As you can see, the level 0 and level 1 backups are showing as available. To double check, I perform a crosscheck backup of database;
RMAN> crosscheck backup of database;
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=74 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4927_piece_1_date_20100221_711576046 recid=4872 stamp=711576046
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4928_piece_1_date_20100221_711576046 recid=4873 stamp=711576046
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4930_piece_1_date_20100221_711578189 recid=4874 stamp=711578189
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185 recid=4875 stamp=711578186
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4932_piece_1_date_20100221_711579570 recid=4876 stamp=711579570
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4931_piece_1_date_20100221_711579392 recid=4877 stamp=711579393
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4934_piece_1_date_20100221_711580369 recid=4878 stamp=711580370
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4935_piece_1_date_20100221_711580535 recid=4879 stamp=711580535
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4933_piece_1_date_20100221_711580122 recid=4880 stamp=711580123
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4948_piece_1_date_20100224_711835237 recid=4892 stamp=711835238
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4947_piece_1_date_20100224_711835238 recid=4893 stamp=711835238
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434 recid=4894 stamp=711836436
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4950_piece_1_date_20100224_711836866 recid=4895 stamp=711836866
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4951_piece_1_date_20100224_711837267 recid=4896 stamp=711837268
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4952_piece_1_date_20100224_711837971 recid=4897 stamp=711837972
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4953_piece_1_date_20100224_711837989 recid=4898 stamp=711837989
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4955_piece_1_date_20100224_711838522 recid=4899 stamp=711838522
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4954_piece_1_date_20100224_711838520 recid=4900 stamp=711838521
Crosschecked 18 objects
RMAN>
So I'm unclear as to why RMAN believes the backups of these files don't exist when I attempt to restore the database. Anyone have a clue?
NOTE: I've also tried to restore spcifically with the tag= clause but I get the same results:
RMAN> restore database from tag='TAG20100221T200045';
Starting restore at 25-FEB-10
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2010 13:41:04
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 44 found to restore
RMAN-06023: no backup or copy of datafile 43 found to restore
RMAN-06023: no backup or copy of datafile 42 found to restore
RMAN-06023: no backup or copy of datafile 40 found to restore
RMAN-06023: no backup or copy of datafile 39 found to restore
RMAN-06023: no backup or copy of datafile 38 found to restore
RMAN-06023: no backup or copy of datafile 37 found to restore
RMAN-06023: no backup or copy of datafile 36 found to restore
RMAN-06023: no backup or copy of datafile 35 found to restore
RMAN-06023: no backup or copy of datafile 34 found to restore
RMAN-06023: no backup or copy of datafile 33 found to restore
RMAN-06023: no backup or copy of datafile 32 found to restore
RMAN-06023: no backup or copy of datafile 31 found to restore
RMAN-06023: no backup or copy of datafile 30 found to restore
RMAN-06023: no backup or copy of datafile 29 found to restore
RMAN-06023: no backup or copy of datafile 28 found to restore
RMAN-06023: no backup or copy of datafile 27 found to restore
RMAN-06023: no backup or copy of datafile 26 found to restore
RMAN-06023: no backup or copy of datafile 25 found to restore
RMAN-06023: no backup or copy of datafile 24 found to restore
RMAN-06023: no backup or copy of datafile 23 found to restore
RMAN-06023: no backup or copy of datafile 22 found to restore
RMAN-06023: no backup or copy of datafile 21 found to restore
RMAN-06023: no backup or copy of datafile 20 found to restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 18 found to restore
RMAN-06023: no backup or copy of datafile 17 found to restore
RMAN-06023: no backup or copy of datafile 16 found to restore
RMAN-06023: no backup or copy of datafile 15 found to restore
RMAN-06023: no backup or copy of datafile 14 found to restore
RMAN-06023: no backup or copy of datafile 13 found to restore
RMAN-06023: no backup or copy of datafile 12 found to restore
RMAN-06023: no backup or copy of datafile 11 found to restore
RMAN-06023: no backup or copy of datafile 10 found to restore
RMAN-06023: no backup or copy of datafile 9 found to restore
RMAN-06023: no backup or copy of datafile 8 found to restore
RMAN-06023: no backup or copy of datafile 7 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 5 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore

Just as a follow on to my last post, after the RMAN-06023 messages, I list backups of the three datafiles and as you can see RMAN thinks that they are available. If I exit RMAN and list them at the OS level, they are where RMAN things they should be:
RMAN> restore database;
Starting restore at 25-FEB-10
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2010 16:17:39
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN> list backup of datafile 4;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4880 Incr 0 1.36G DISK 00:08:57 21-FEB-10
BP Key: 4880 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4933_piece_1_date_20100221_711580122
List of Datafiles in backup set 4880
File LV Type Ckp SCN Ckp Time Name
4 0 Incr 5086110241948 21-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4890 Incr 1 934.82M DISK 00:09:42 22-FEB-10
BP Key: 4890 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4943_piece_1_date_20100222_711664989
List of Datafiles in backup set 4890
File LV Type Ckp SCN Ckp Time Name
4 1 Incr 5086111401249 22-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4898 Incr 1 947.57M DISK 00:08:49 24-FEB-10
BP Key: 4898 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4953_piece_1_date_20100224_711837989
List of Datafiles in backup set 4898
File LV Type Ckp SCN Ckp Time Name
4 1 Incr 5086113791743 24-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
RMAN>
RMAN> list backup of datafile 3;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4874 Incr 0 2.65G DISK 00:19:50 21-FEB-10
BP Key: 4874 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4930_piece_1_date_20100221_711578189
List of Datafiles in backup set 4874
File LV Type Ckp SCN Ckp Time Name
3 0 Incr 5086110241948 21-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4885 Incr 1 1.95G DISK 00:15:54 22-FEB-10
BP Key: 4885 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4940_piece_1_date_20100222_711663910
List of Datafiles in backup set 4885
File LV Type Ckp SCN Ckp Time Name
3 1 Incr 5086111401249 22-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4895 Incr 1 1.97G DISK 00:18:13 24-FEB-10
BP Key: 4895 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4950_piece_1_date_20100224_711836866
List of Datafiles in backup set 4895
File LV Type Ckp SCN Ckp Time Name
3 1 Incr 5086113791743 24-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
RMAN>
RMAN>
RMAN> list backup of datafile 1;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
4875 Incr 0 4.37G DISK 00:22:53 21-FEB-10
BP Key: 4875 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185
List of Datafiles in backup set 4875
File LV Type Ckp SCN Ckp Time Name
1 0 Incr 5086110241948 21-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4884 Incr 1 1.93G DISK 00:12:34 22-FEB-10
BP Key: 4884 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4939_piece_1_date_20100222_711663601
List of Datafiles in backup set 4884
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 5086111401249 22-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
4894 Incr 1 1.92G DISK 00:13:46 24-FEB-10
BP Key: 4894 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434
List of Datafiles in backup set 4894
File LV Type Ckp SCN Ckp Time Name
1 1 Incr 5086113791743 24-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
RMAN> exit
$ ls -ltr /u03/oracle_backups/ORADB1/offline
total 59743688
-rwx------ 1 oracle oinstall 7677960192 2010-02-25 11:13 ORADB1_level0_set_4927_piece_1_date_20100221_711576046
-rwx------ 1 oracle oinstall 7980834816 2010-02-25 11:24 ORADB1_level0_set_4928_piece_1_date_20100221_711576046
-rwx------ 1 oracle oinstall 4691853312 2010-02-25 11:29 ORADB1_level0_set_4929_piece_1_date_20100221_711578185
-rwx------ 1 oracle oinstall 2847391744 2010-02-25 11:34 ORADB1_level0_set_4930_piece_1_date_20100221_711578189
-rwx------ 1 oracle oinstall 3530924032 2010-02-25 11:39 ORADB1_level0_set_4931_piece_1_date_20100221_711579392
-rwx------ 1 oracle oinstall 1566449664 2010-02-25 11:41 ORADB1_level0_set_4932_piece_1_date_20100221_711579570
-rwx------ 1 oracle oinstall 1459781632 2010-02-25 11:43 ORADB1_level0_set_4933_piece_1_date_20100221_711580122
-rwx------ 1 oracle oinstall 561774592 2010-02-25 11:44 ORADB1_level0_set_4934_piece_1_date_20100221_711580369
-rwx------ 1 oracle oinstall 58753024 2010-02-25 11:44 ORADB1_level0_set_4935_piece_1_date_20100221_711580535
-rwx------ 1 oracle oinstall 4364124160 2010-02-25 11:56 ORADB1_level1_set_4947_piece_1_date_20100224_711835238
-rwx------ 1 oracle oinstall 2971877376 2010-02-25 12:01 ORADB1_level1_set_4948_piece_1_date_20100224_711835237
-rwx------ 1 oracle oinstall 2066546688 2010-02-25 12:03 ORADB1_level1_set_4949_piece_1_date_20100224_711836434
-rwx------ 1 oracle oinstall 2119360512 2010-02-25 12:06 ORADB1_level1_set_4950_piece_1_date_20100224_711836866
-rwx------ 1 oracle oinstall 1003356160 2010-02-25 12:06 ORADB1_level1_set_4951_piece_1_date_20100224_711837267
-rwx------ 1 oracle oinstall 1637105664 2010-02-25 12:08 ORADB1_level1_set_4952_piece_1_date_20100224_711837971
-rwx------ 1 oracle oinstall 993607680 2010-02-25 12:08 ORADB1_level1_set_4953_piece_1_date_20100224_711837989
-rwx------ 1 oracle oinstall 1130496 2010-02-25 12:09 ORADB1_level1_set_4955_piece_1_date_20100224_711838522
-rwx------ 1 oracle oinstall 283344896 2010-02-25 12:09 ORADB1_level1_set_4954_piece_1_date_20100224_711838520
-rwx------ 1 oracle oinstall 4344365056 2010-02-25 16:01 ORADB1_level1_set_4937_piece_1_date_20100222_711662448
-rwx------ 1 oracle oinstall 2959015936 2010-02-25 16:05 ORADB1_level1_set_4938_piece_1_date_20100222_711662448
-rwx------ 1 oracle oinstall 2067202048 2010-02-25 16:07 ORADB1_level1_set_4939_piece_1_date_20100222_711663601
-rwx------ 1 oracle oinstall 2089304064 2010-02-25 16:08 ORADB1_level1_set_4940_piece_1_date_20100222_711663910
-rwx------ 1 oracle oinstall 955711488 2010-02-25 16:09 ORADB1_level1_set_4941_piece_1_date_20100222_711664370
-rwx------ 1 oracle oinstall 1623564288 2010-02-25 16:11 ORADB1_level1_set_4942_piece_1_date_20100222_711664872
-rwx------ 1 oracle oinstall 980238336 2010-02-25 16:12 ORADB1_level1_set_4943_piece_1_date_20100222_711664989
-rwx------ 1 oracle oinstall 280952832 2010-02-25 16:12 ORADB1_level1_set_4944_piece_1_date_20100222_711665385
-rwx------ 1 oracle oinstall 1130496 2010-02-25 16:12 ORADB1_level1_set_4945_piece_1_date_20100222_711665521

Can rman backups be used to restore to a different server

We are using R12 with 10gr2 database
If i take Rman backups, can they be used to restore on some other test server for cloning and bringing that test server upto date like the production.
I am confues and dont know and This is the only reason i dont use rman for backups, instead take cold backups manually every night as they are used every week to clone some other server for testing purpose
Please advice
Thanks

Hi..
1. Copy the pfile to the new server.
2. startup nomount the database using the pfile.
3. Open a new RMAN session and connect to this database
4. Restore the controlfile, this will bring the database in mount stage
5. Once step 4 is completed, restore and recover the database.
NOTE:-- These are the steps for restoring the database when the RMAN backup pieces are copied to the same location as they are on the main server.If you copy the rman backup to some different location, then you will have to use the CATALOG BACKUPPIECE 'location' command before restoring the database.
Go through [http://download.oracle.com/docs/cd/B10500_01/server.920/a96566/rcmdupdb.htm]
HTH
Anand
Edited by: Anand... on Dec 23, 2008 8:13 PM Added link

Cold backup tablespace restore

From a cold backup can you restore a tablespace to a different database.
A datafile was created and dropped and now we are recieving ORA-1186, ORA-1157 cannnot/identify lock datafile
We know that if our database goes down it won't come back up. The table space has about 250 tables and its huge about 100g in size. Does anyone know of what steps needs to be taken?
Edited by: user10767182 on Jan 6, 2009 8:35 PM

I couldn't quite workout what you were saying, but I think you were suggesting that copies of the lost tables and data are sitting in a second database somewhere, and you would like to pull them out of that database and plug them into the broken database. Is that right?
If so, you cannot take a datafile from one database and plug it into another, unless you use the transportable tablespace option.
Basically, on your broken database, you'd shut it down, bring it back to the mount state and then say alter database datafile X offline drop
That will let you issue an alter database open followed by a drop tablespace X, and your broken database will at least be open, minus the important tablespace
You then get your second database open and make the important tablespace read-only
You'd drop to the command line and do an export using the TRANSPORT_TABLESPACE option -the command is too susceptible to the specifics to show you here. Check the documentation at http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta063.htm
You then copy the datafile and the export dump file to the server where your broken database is running
You then run an import, again specifying the TRANSPORT_TABLESPACE option
Effectively, the datafile copy gets 'plugged in' to the broken database and gets adopted as a native, brand new tablespace, complete with contents. You finish off by making the tablespace read-write in both databases once more.
Obviously, you lose data using this sort of process: the data comes back into your 'broken' database in the same state it was in your second database, and you can't apply redo to it to recover it to a more recent state. But that's going to be the best you can do if you don't have proper physical backups of the file. Your subject mentioning cold backups confused me a little on that score too.
So I won't go into any more detail for now. It may be that I misunderstood the reference to 'restore a tablespace to a different database' and your requirements completely. But if this sounds like what you are after, and if you are stuck on any of the details, then you can always post a follow-up.

Restoring inconsistent cold backup

Hello all.
Here's the scenario: I have a 9.2.0.1 database, in noarchivelog mode, running on Windoze XP. While the database is running, I took a backup of all the datafiles, control files and online logs using copy and paste on windoze. After the copy was done, I have shut down the database. I copied back into the original location the backup of the datafiles I made earlier.
My question is: How I go about to restore this database ? I dont care wether it is consistent or not, I just want to open it to make an export out of it
Things I have tried so far unsuccessfully:
allowresetlogs_corruption
allowreadonly_corruption
If you could shed some light on it on the steps I would need to make, that would be appreciated.
Thanks

What have you tried to far (specifics please, not general statements)?
I have done something close to what you want do a couple of years ago for an Oracle 9.2.0.4 DB on Linux and am looking for my notes. One key thing I found was to not try to change anything but just get a DB up and running that would let me get the data out. That means don't try to use different file paths or anything other changes.
It involved creating a new minimal database from scratch by hand that has the same name, paths, block size as the old one. In my case this minimal DB only had the system_01.dbf, undotbs_01.dbf and users_01.dbf data files even though I ultimately needed access to about 40 others.
The idea is to get a template DB in place that refers to the same paths, then shut it down and replace the minimal system_01.dbf file with the one from your backup. It turned out for me that Oracle could open, load and use my old system tablespace even though it referred to tablespaces that didn't exist yet in the new minimal system; obviously I couldn't use them yet but they didn't cause Oracle to fail to start.
1. You can toss the redo logs since there is nothing in them you need or can use and you will never be able to read them anyway.
2. You will need to create the instance and DB using the same version of Oracle that you had. There were key differences between the early Oracle 9 versions and I wasn't able to get around them.
3. Create an instance for the correct DB version if you don't have one. The easiest way to create a new one is to do a default installation from the original set up files but DO NOT create a database. When given choices use the same values (character set, paths, etc) as your old DB.
4. You will need a text version of the init.ora file in the same location (name and path) where it was before - the character set and block size have to match what you had before. If you have a copy of this file you can try it first. If you don't then create a minimal file; that is, no entries that are not necessary. Oracle comes with a sample with a lot entries commented out.
    a. use the same db_name= parameter in the init.ora file
    b. use a db_files= parameter that is large enough for all of the data files that you will later need access to
    c. use a compatible- parameter that is 9.2.0 and no later
5. You won't be able to use your old, copied, control files since they are binary files and the content won't match the new database; trying to use them will not get you anywhere.
6. Once you can bring up this new DB the first thing you should do is shut it down and take a cold backup.
7. Replace the new system_01.dbf and users_01_dbf files with the ones you copied from the old DB. The new control file can mount and open the old tablespace file and users file since the control file (old Oracle systems only, mind you) have NAME and PATH information but do not care about actual content (how many users, etc).
8. Make sure you can now open and access the DB with your swapped system and user tablespaces. You won't be able to access objects from the system tables that refer to data files that aren't known to the control file so don't even try to yet.
9. You can add your other data files to the DB by doing a CREATE CONTROLFILE command, when unmounted, that adds the other data files that you will want access to. Obviously don't add them all at once; add one and then test to make sure that things are ok. You won't be
It turns out that the control file has the list of datafiles including their names and paths but does not have the sizes; the system tables have the size info and physical info. So you can add a datafile to the control file by path and name without needing to know how big it was supposed to be; that size info will still be in your old system tablespace.I may have missed something and if I fiind my notes will repost with anything else I think of.

RMAN Restore from cold backup ?

Hi ,
I am trying to restore the database from production db using the RMAN cold Backup. Both the prod and test(Restore database) are on the same machine. And also I wanted to have the restore db name should be different.
And the restore db name should be different. What are the options I have ?

refer the thread:-
RMAN Restore using RMAN COLD Backup!!
RMAN Restore using RMAN COLD Backup!!

Restore 11g rman cold backup on same server.

Hi All,
I have a requirement , where we have to clone one development database's to other database's sitting on the same host.
I have taken the cold rman backup and copy it different database's local folder.
I changed the db_name in target pfile and did the nomount , but when I tries to restore the controlfile , it throws me below errors.
Just to add to to it, I was ale to restore the controlfile to the location specified in pfile.
now , when I tries to mount the database , it throws me following errors
Snippet from target database's
SQL> startup mount pfile=/db/epmtrain/oracle/11.1.0/dbs/initepmtrain.bkp
ORACLE instance started.
Total System Global Area 1.3696E+10 bytes
Fixed Size                  2132152 bytes
Variable Size            6173202248 bytes
Database Buffers         7516192768 bytes
Redo Buffers                4362240 bytes
ORA-00205: error in identifying control file, check alert log for more info
RMAN> run {
2> restore controlfile from '/db/epmtrain/export/rman/EPMDEV_06ogm377.bkp';
3> }
Starting restore at 07-AUG-13
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/07/2013 07:12:21
ORA-19870: error while restoring backup piece /db/epmtrain/export/rman/EPMDEV_06ogm377.bkp
ORA-19504: failed to create file "/db/epmtrain/oracle/11.1.0/dbs/db/epmtrain/data1/epmtrain/control01.ctl'"
ORA-27040: file create error, unable to create file
HPUX-ia64 Error: 2: No such file or directory
Regards

940856 wrote:
I restored the controlfile to the path mentioned in pfile. after that , when I tries to mount the database , it throws me the following errors.
---------- Snippet from alert.log ------
ORA-00210: cannot open the specified control file
ORA-00202: control file: '/db/epmtrain/data1/epmtrain/control01.ctl''
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
ORA-205 signalled during: ALTER DATABASE   MOUNT...
------------ controlfile location in pfile ---------
*.control_files=/db/epmtrain/data1/epmtrain/control01.ctl','/db/epmtrain/data1/epmtrain/control02.ctl'
--------------- show parameter control output -------------
SQL> show parameter control
NAME                                 TYPE                             VALUE
control_file_record_keep_time        integer                          7
control_files                        string                           /db/epmtrain/data1/epmtrain/co
                                                                      ntrol01.ctl', /db/epmtrain/dat
                                                                      a1/epmtrain/control02.ctl
control_management_pack_access       string                           DIAGNOSTIC+TUNING
Regards
So present proof that "/db/epmtrain/data1/epmtrain/control01.ctl" actually exists .....

Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '14.0.0.6106' or later

while Restoring a Site Collection from a different server i got below error in SharePoint 2010.
Kindly let me know , which patch i have to install along with the download link please. i am unable to find the correct patch to download..
Thanks in Advance,
Tarun
TARUN

Hi,
According to your post, my understanding is that you get an error when you restore a site collection from a different server in SharePoint 2010.
I recommend that you can try to click the “KB2536599” for SharePoint 2010 version 14.0.0.6106 to download the patch from the following links and install the patch in your environment.
http://blogs.technet.com/b/moss_it/archive/2011/08/15/lista-di-versioni-di-sharepoint-server-2010-o-sharepoint-foundation-2010-wss-4-0.aspx
http://support.microsoft.com/kb/2536599
After the installation, you need to run the Configuration Wizard. Later you should be able to restore this site collection successfully.
For more information, you can refer to:
https://ammarfassy.wordpress.com/2012/11/29/restore-spsite-your-backup-is-from-a-different-version/
https://social.technet.microsoft.com/Forums/en-US/cb9fb524-2a65-4a59-8f09-fc86366dd1c2/restore-errorversion-of-14006106-in-power-shell?forum=sharepointdevelopmentprevious
http://blogs.technet.com/b/stefan_gossner/archive/2011/07/12/june-2011-cu-for-sharepoint-2010-has-been-re-released.aspx
http://www.sharepointdesignerstepbystep.com/blog/SitePages/SharePoint%20versions.aspx
Best Regards,
Yumi Fu

Cold backup restore to a different bit level

Similar Messages

Maybe you are looking for