Restoring database with NOARCHIVELOG

After several failed attempts at trying to get Enterprise Manager to work with my database, I decided to uninstall the Enterprise Edition completely and then to install it from scratch. I did and found, as expected, that my database files were still intact, on another drive. However, what I didn't expect was that uninstalling Oracle also removed the init*.ora files I had for the different databases, and so the DBCA showed no databases at all. So I figured I would create new databases with the same settings, and then copy all the files from the old locations to the new ones. That went well, except for with one database.
When trying to open that database, I get a ORA-00280 and the suggested file that should contain the sequence, is not at that location. In fact I could not find it anywhere on my disks, even after using a program to undelete content. However I know for a fact that I ran my old databases in NOARCHIVELOG mode, yet the name of the suggested file hinted at it being an archive log.
I have been googling all day long, and tried out several different methods, restoring, recovering, RESETLOGS, NORESETLOGS, what to do when not having neither archive logs or possibly redo logs (as I don't know what the ONLINELOG files are specifically), but they all ended up with me being at the same point, needing that .arc file which I should've never had, due to NOARCHIVELOG mode.
So here is where I'm at. I have a CONTROLFILE folder with 1 control file, a DATAFILE folder with the usual tablespace files, and an ONLINELOG folder with 3 log files. I even tried using those 3 log files for recovering the database, but to no avail. I have all the data, and while I guess the ORA-00280 means that there has been a change in the database since the data files were written, I haven't changed much data so I could easily add whatever little data is missing from the tablespace USERS. So I need some instructions, some help on how to open and mount the database and avoid getting the ORA-00280 or being able to ignore it and still open the database. As I created a new database, there are no archive logs backed up, so I can't recover any files that way, I only have the data files, control files and log files to work with.

You're not in as bad as shape as you think.
If you have the data files and one control file, you can recover/restore the database. First thing to do is get a working init.ora file and get the instance up and running. Then, work on the control file (so you can at least mount the database). Fix what you need to in terms of paths/file locations. It may take several iterations. You can also bypass the existing controlfile and create your own. Eventually, you'll be able to have a successful "alter database open" step.
http://www.databasejournal.com/features/oracle/article.php/3738736/Recovering-from-Loss-of-All-Control-Files.htm
Number one precaution: take a copy of what you have now and put it somewhere else, just in case. You don't want to make the situation worse.

Similar Messages

Error while restoring database with different name on subscriber

Hi all,
I am using merge replication in sql server 2008R2. Yesterday I wanted to create a test environment, so
I did:
1. on publisher I restored from backup production db with another name ( lets call it TEST and new files
.mdf, .ldf and no switch KEEP_REPLICATION). After this step original replication between production
dbs worked fine.
2. on subscriber I did the same: restore as new db TEST with new
files .mdf, .ldf and no switch KEEP_REPLICATION.
Unfortunately I noticed, that after second step replication stopped. SQL agent replication job on Subscriber
is gone.
Why restoring db with new name did affect original replication?
Finally the most important: replication was set up by external company and I have to bring it to live now
but I don't know this subject so good. How can I do it?
Assuming, that there is no data change on subscriber in replicated tables is it enough when I select ‘reinitialize’
on Publisher and Subscriber?
Thanks in advance
Artur

Hello,
Sorry for late response, but I was out of the office during last week.
Regarding problem 1: restoring replication. I contacted guy who made originally our replication and he recreated subscription agent. So this is solved.
problem 2: why did it happen?
Lydia, in link which you provided I found only info about restoring db in replication, but I didn't want to restore replication.
I checked SQL Server and Server Agent logs and there were no entries on that time. The only entries are regarding db restoring. Below:
09/11/2014 12:45:59,Backup,Unknown,Database was restored: Database: Logik_ATData_TEST<c/> creation date(time): 2012/04/27(13:55:41)<c/> first LSN: 21392:66:267<c/> last LSN: 21392:227:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\MSSQLBackup\Dzienny\Logik_ATData_PROD\Logik_ATData_PROD_backup_2014_09_10_231001_6391536.bak'}). Informational message. No user action required.
09/11/2014 12:45:59,Backup,Unknown,Restore is complete on database 'Logik_ATData_TEST'. The database is now available.
09/11/2014 12:45:59,spid72,Unknown,CHECKDB for database 'Logik_ATData_TEST' finished without errors on 2012-04-26 22:50:05.490 (local time). This is an informational message only; no user action is required.
09/11/2014 12:44:53,spid72,Unknown,Recovery is writing a checkpoint in database 'Logik_ATData_TEST' (13). This is an informational message only. No user action is required.
09/11/2014 12:44:53,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
09/11/2014 12:44:51,spid72,Unknown,The database 'Logik_ATData_TEST' is marked RESTORING and is in a state that does not allow recovery to be run.
09/11/2014 12:44:51,spid72,Unknown,Starting up database 'Logik_ATData_TEST'.
In Windows application log there were also no other entries, besides these above.
I also could not check job history, because the job was gone in SSMS jobs list, while the subscription was present in SSMS Replication with info, that last successful synchronization was at 12:42 (there is a 5 min. sync period).
I also don't understand how the job was deleted, because according this manual (http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/) I have 2 triggers in sysjobs table and every time, when
job is deleted/disabled I got @ notification. In this case I got no @.
My SQL Server version:
Product_Version Product_Level Edition
10.50.2550.0 SP1 Standard Edition (64-bit)
Any idea what happened?
Thanks,
Artur

Backup/restore database with dump file

Hi everybody,
I would like to backup/restore my database with Oracle Utility commands(exp/imp) but I can only execute these commands in the machine where database server is being installed. When I use Oracle client to connect to DB server to execute these commands, DB server can not understand these commands.
Is there any method to do this?
Please help me.

My workout for you is as follows (assuming, you configured tnsnames pointing to the listener concern with your database)...
SQL> select * from example;
ITEM STORE STARTDATE ENDDATE
1 10 01-JAN-06 19-JAN-06
1 10 03-JAN-06 20-JAN-06
1 10 01-FEB-06 20-FEB-06
2 10 01-JAN-06 15-JAN-06
SQL>
C:\>exp scott/[email protected] tables=example query=\"where item=1\" file=example.dmp
Export: Release 9.2.0.1.0 - Production on Fri Dec 15 08:06:16 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
server uses US7ASCII character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table EXAMPLE 3 rows exported
Export terminated successfully without warnings.
C:\>
-aijaz

Restore database with new DB name

I'm trying to restore a database from a hot backup with a new database name. I'm trying to use the backup control file with the SET DATABASE in the control file. That works ok, but when I run RECOVER DATABASE USING BACKUP CONTROLFILE I get errors such as
ORA-00279: change 1516911820 generated at 09/08/2006 17:14:43 needed for thread 1
and ORA-00308: cannot open archived log
Can anyone help me? I'm not using RMAN currently with the DUPLICATE command because I'm running on NetApp filers and it would be much faster to duplicate the database this way. Also, I'm duplicating on the same server so I need to use a different instance name.
Thanks,
Michael Cunningham

Assuming source is in Archive Log mode.
Your scenario is :-
Cloning Database in the same server using OS copy.
I believe you are stuck with recovery issues, what you need to do is feed the archive log that the database is asking for. You can also try giving it the redo logs.
RECOVER DATABASE USING BACKUP CONTROLFILE;
feed it the archive/redo logs. Till you get a Media recovery complete message.

How restore database with duplicate command where backuppiece moved

hello
i have 2 hosts
on the host 1 my production database and on host2 my developlment database
i would like to duplicate the first one on the host2 i have created an auxiliary database
all seems ok expect 1 not small problem :
on host1 my backuppiece are in F:\oracle\backup_%d_%u
and i don't have a F drive on my host2 i have copy all the rman backup in : e:\oracle\backup
but i don't find how tell to rman to take my backuppiece in E: and not in F:
this is my result of my rman script :
RMAN> run {
2> set newname for datafile 1 to 'e:\oracle\oradata\dpbsdev2\SYSTEM01.DBF' ;
3> set newname for datafile 2 to 'e:\oracle\oradata\dpbsdev2\UNDOTBS01.DBF' ;
4> set newname for datafile 3 to 'e:\oracle\oradata\dpbsdev2\SYSAUX01.DBF' ;
5> set newname for datafile 4 to 'e:\oracle\oradata\dpbsdev2\USERS01.DBF' ;
6> set newname for datafile 5 to 'e:\oracle\oradata\dpbsdev2\CIF.ORA' ;
7> set newname for datafile 6 to 'e:\oracle\oradata\dpbsdev2\DEVELOPMENT.ORA' ;
8> set newname for datafile 7 to 'e:\oracle\oradata\dpbsdev2\COMPLIANCE.ORA' ;
9> set newname for datafile 8 to 'e:\oracle\oradata\dpbsdev2\COMPLIANCE_EOM.ORA'
10> set newname for datafile 9 to 'e:\oracle\oradata\dpbsdev2\CWMLITE.ORA' ;
11> set newname for datafile 10 to 'e:\oracle\oradata\dpbsdev2\DADIC.ORA' ;
12> set newname for datafile 12 to 'e:\oracle\oradata\dpbsdev2\DRSYS.ORA' ;
13> set newname for datafile 13 to 'e:\oracle\oradata\dpbsdev2\DUW_LAN_ENCRYPT.O
14> set newname for datafile 14 to 'e:\oracle\oradata\dpbsdev2\ERASE.ORA' ;
15> set newname for datafile 15 to 'e:\oracle\oradata\dpbsdev2\EXPRIM.ORA' ;
16> set newname for datafile 16 to 'e:\oracle\oradata\dpbsdev2\EXPRIM_EOM.ORA' ;
17> set newname for datafile 17 to 'e:\oracle\oradata\dpbsdev2\EXPRIM_EOY.ORA' ;
18> set newname for datafile 18 to 'e:\oracle\oradata\dpbsdev2\IDX_COMMON.ORA' ;
19> set newname for datafile 19 to 'e:\oracle\oradata\dpbsdev2\IDX_DWH.ORA' ;
20> set newname for datafile 20 to 'e:\oracle\oradata\dpbsdev2\IDX_EXPRIM.ORA' ;
21> set newname for datafile 21 to 'e:\oracle\oradata\dpbsdev2\IDX_IMPORT.ORA' ;
22> set newname for datafile 22 to 'e:\oracle\oradata\dpbsdev2\IDX_SPECIAL.ORA'
23> set newname for datafile 23 to 'e:\oracle\oradata\dpbsdev2\IDX_WINDEKIS.ORA'
24> set newname for datafile 24 to 'e:\oracle\oradata\dpbsdev2\IMPORT.ORA' ;
25> set newname for datafile 25 to 'e:\oracle\oradata\dpbsdev2\IMPORT_EOM.ORA' ;
26> set newname for datafile 26 to 'e:\oracle\oradata\dpbsdev2\IMPORT_EOY.ORA' ;
27> set newname for datafile 27 to 'e:\oracle\oradata\dpbsdev2\INDX.ORA' ;
28> set newname for datafile 28 to 'e:\oracle\oradata\dpbsdev2\ODM.ORA' ;
29> set newname for datafile 29 to 'e:\oracle\oradata\dpbsdev2\OMS_REPOSITORY.OR
30> set newname for datafile 31 to 'e:\oracle\oradata\dpbsdev2\OWB_REPOSITORY.OR
31> set newname for datafile 32 to 'e:\oracle\oradata\dpbsdev2\OWB_REPOSITORY_ID
32> set newname for datafile 34 to 'e:\oracle\oradata\dpbsdev2\SECURITY.ORA' ;
33> set newname for datafile 35 to 'e:\oracle\oradata\dpbsdev2\SIMS.ORA' ;
34> set newname for datafile 36 to 'e:\oracle\oradata\dpbsdev2\TOOLS.ORA' ;
35> set newname for datafile 37 to 'e:\oracle\oradata\dpbsdev2\TRANSTAT.ORA' ;
36> set newname for datafile 38 to 'e:\oracle\oradata\dpbsdev2\UTILS.ORA' ;
37> set newname for datafile 39 to 'e:\oracle\oradata\dpbsdev2\WINDEKIS.ORA' ;
38> set newname for datafile 40 to 'e:\oracle\oradata\dpbsdev2\WINDEKIS_EOM.ORA'
39> set newname for datafile 41 to 'e:\oracle\oradata\dpbsdev2\WINDEKIS_EOY.ORA'
40> set newname for datafile 42 to 'e:\oracle\oradata\dpbsdev2\XDB.ORA' ;
41> set newname for datafile 43 to 'e:\oracle\oradata\dpbsdev2\CHANGE_MGT_PACK.D
42> set newname for datafile 44 to 'e:\oracle\oradata\dpbsdev2\DWH.ORA' ;
43> set newname for datafile 46 to 'e:\oracle\oradata\dpbsdev2\DEXIA_JOBS.ORA' ;
44> duplicate target database to DPBSDEV2
45> logfile
46> group 1 ('E:\oracle\oradata\dpbsdev2\redo01.log' ) size 500M ,
47> group 2 ('E:\oracle\oradata\dpbsdev2\redo02.log' ) size 500M ,
48> group 3 ('E:\oracle\oradata\dpbsdev2\redo03.log' ) size 500M ;
49> }
executing command: SET NEWNAME
using target database control file instead of recovery catalog
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
executing command: SET NEWNAME
Starting Duplicate Db at 06-FEB-08
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=157 devtype=DISK
contents of Memory Script:
set until scn 2519944319;
set newname for datafile 1 to
"E:\ORACLE\ORADATA\DPBSDEV2\SYSTEM01.DBF";
set newname for datafile 2 to
"E:\ORACLE\ORADATA\DPBSDEV2\UNDOTBS01.DBF";
set newname for datafile 3 to
"E:\ORACLE\ORADATA\DPBSDEV2\SYSAUX01.DBF";
set newname for datafile 4 to
"E:\ORACLE\ORADATA\DPBSDEV2\USERS01.DBF";
set newname for datafile 5 to
"E:\ORACLE\ORADATA\DPBSDEV2\CIF.ORA";
set newname for datafile 6 to
"E:\ORACLE\ORADATA\DPBSDEV2\DEVELOPMENT.ORA";
set newname for datafile 7 to
"E:\ORACLE\ORADATA\DPBSDEV2\COMPLIANCE.ORA";
set newname for datafile 8 to
"E:\ORACLE\ORADATA\DPBSDEV2\COMPLIANCE_EOM.ORA";
set newname for datafile 9 to
"E:\ORACLE\ORADATA\DPBSDEV2\CWMLITE.ORA";
set newname for datafile 10 to
"E:\ORACLE\ORADATA\DPBSDEV2\DADIC.ORA";
set newname for datafile 12 to
"E:\ORACLE\ORADATA\DPBSDEV2\DRSYS.ORA";
set newname for datafile 13 to
"E:\ORACLE\ORADATA\DPBSDEV2\DUW_LAN_ENCRYPT.ORA";
set newname for datafile 14 to
"E:\ORACLE\ORADATA\DPBSDEV2\ERASE.ORA";
set newname for datafile 15 to
"E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM.ORA";
set newname for datafile 16 to
"E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM_EOM.ORA";
set newname for datafile 17 to
"E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM_EOY.ORA";
set newname for datafile 18 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_COMMON.ORA";
set newname for datafile 19 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_DWH.ORA";
set newname for datafile 20 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_EXPRIM.ORA";
set newname for datafile 21 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_IMPORT.ORA";
set newname for datafile 22 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_SPECIAL.ORA";
set newname for datafile 23 to
"E:\ORACLE\ORADATA\DPBSDEV2\IDX_WINDEKIS.ORA";
set newname for datafile 24 to
"E:\ORACLE\ORADATA\DPBSDEV2\IMPORT.ORA";
set newname for datafile 25 to
"E:\ORACLE\ORADATA\DPBSDEV2\IMPORT_EOM.ORA";
set newname for datafile 26 to
"E:\ORACLE\ORADATA\DPBSDEV2\IMPORT_EOY.ORA";
set newname for datafile 27 to
"E:\ORACLE\ORADATA\DPBSDEV2\INDX.ORA";
set newname for datafile 28 to
"E:\ORACLE\ORADATA\DPBSDEV2\ODM.ORA";
set newname for datafile 29 to
"E:\ORACLE\ORADATA\DPBSDEV2\OMS_REPOSITORY.ORA";
set newname for datafile 31 to
"E:\ORACLE\ORADATA\DPBSDEV2\OWB_REPOSITORY.ORA";
set newname for datafile 32 to
"E:\ORACLE\ORADATA\DPBSDEV2\OWB_REPOSITORY_IDX.ORA";
set newname for datafile 34 to
"E:\ORACLE\ORADATA\DPBSDEV2\SECURITY.ORA";
set newname for datafile 35 to
"E:\ORACLE\ORADATA\DPBSDEV2\SIMS.ORA";
set newname for datafile 36 to
"E:\ORACLE\ORADATA\DPBSDEV2\TOOLS.ORA";
set newname for datafile 37 to
"E:\ORACLE\ORADATA\DPBSDEV2\TRANSTAT.ORA";
set newname for datafile 38 to
"E:\ORACLE\ORADATA\DPBSDEV2\UTILS.ORA";
set newname for datafile 39 to
"E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS.ORA";
set newname for datafile 40 to
"E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS_EOM.ORA";
set newname for datafile 41 to
"E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS_EOY.ORA";
set newname for datafile 42 to
"E:\ORACLE\ORADATA\DPBSDEV2\XDB.ORA";
set newname for datafile 43 to
"E:\ORACLE\ORADATA\DPBSDEV2\CHANGE_MGT_PACK.DBF";
set newname for datafile 44 to
"E:\ORACLE\ORADATA\DPBSDEV2\DWH.ORA";
set newname for datafile 46 to
"E:\ORACLE\ORADATA\DPBSDEV2\DEXIA_JOBS.ORA";
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
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 06-FEB-08
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to E:\ORACLE\ORADATA\DPBSDEV2\SYSTEM01.DBF
restoring datafile 00002 to E:\ORACLE\ORADATA\DPBSDEV2\UNDOTBS01.DBF
restoring datafile 00003 to E:\ORACLE\ORADATA\DPBSDEV2\SYSAUX01.DBF
restoring datafile 00004 to E:\ORACLE\ORADATA\DPBSDEV2\USERS01.DBF
restoring datafile 00005 to E:\ORACLE\ORADATA\DPBSDEV2\CIF.ORA
restoring datafile 00006 to E:\ORACLE\ORADATA\DPBSDEV2\DEVELOPMENT.ORA
restoring datafile 00007 to E:\ORACLE\ORADATA\DPBSDEV2\COMPLIANCE.ORA
restoring datafile 00008 to E:\ORACLE\ORADATA\DPBSDEV2\COMPLIANCE_EOM.ORA
restoring datafile 00009 to E:\ORACLE\ORADATA\DPBSDEV2\CWMLITE.ORA
restoring datafile 00010 to E:\ORACLE\ORADATA\DPBSDEV2\DADIC.ORA
restoring datafile 00012 to E:\ORACLE\ORADATA\DPBSDEV2\DRSYS.ORA
restoring datafile 00013 to E:\ORACLE\ORADATA\DPBSDEV2\DUW_LAN_ENCRYPT.ORA
restoring datafile 00014 to E:\ORACLE\ORADATA\DPBSDEV2\ERASE.ORA
restoring datafile 00015 to E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM.ORA
restoring datafile 00016 to E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM_EOM.ORA
restoring datafile 00017 to E:\ORACLE\ORADATA\DPBSDEV2\EXPRIM_EOY.ORA
restoring datafile 00018 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_COMMON.ORA
restoring datafile 00019 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_DWH.ORA
restoring datafile 00020 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_EXPRIM.ORA
restoring datafile 00021 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_IMPORT.ORA
restoring datafile 00022 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_SPECIAL.ORA
restoring datafile 00023 to E:\ORACLE\ORADATA\DPBSDEV2\IDX_WINDEKIS.ORA
restoring datafile 00024 to E:\ORACLE\ORADATA\DPBSDEV2\IMPORT.ORA
restoring datafile 00025 to E:\ORACLE\ORADATA\DPBSDEV2\IMPORT_EOM.ORA
restoring datafile 00026 to E:\ORACLE\ORADATA\DPBSDEV2\IMPORT_EOY.ORA
restoring datafile 00027 to E:\ORACLE\ORADATA\DPBSDEV2\INDX.ORA
restoring datafile 00028 to E:\ORACLE\ORADATA\DPBSDEV2\ODM.ORA
restoring datafile 00029 to E:\ORACLE\ORADATA\DPBSDEV2\OMS_REPOSITORY.ORA
restoring datafile 00031 to E:\ORACLE\ORADATA\DPBSDEV2\OWB_REPOSITORY.ORA
restoring datafile 00032 to E:\ORACLE\ORADATA\DPBSDEV2\OWB_REPOSITORY_IDX.ORA
restoring datafile 00034 to E:\ORACLE\ORADATA\DPBSDEV2\SECURITY.ORA
restoring datafile 00035 to E:\ORACLE\ORADATA\DPBSDEV2\SIMS.ORA
restoring datafile 00036 to E:\ORACLE\ORADATA\DPBSDEV2\TOOLS.ORA
restoring datafile 00037 to E:\ORACLE\ORADATA\DPBSDEV2\TRANSTAT.ORA
restoring datafile 00038 to E:\ORACLE\ORADATA\DPBSDEV2\UTILS.ORA
restoring datafile 00039 to E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS.ORA
restoring datafile 00040 to E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS_EOM.ORA
restoring datafile 00041 to E:\ORACLE\ORADATA\DPBSDEV2\WINDEKIS_EOY.ORA
restoring datafile 00042 to E:\ORACLE\ORADATA\DPBSDEV2\XDB.ORA
restoring datafile 00043 to E:\ORACLE\ORADATA\DPBSDEV2\CHANGE_MGT_PACK.DBF
restoring datafile 00044 to E:\ORACLE\ORADATA\DPBSDEV2\DWH.ORA
restoring datafile 00046 to E:\ORACLE\ORADATA\DPBSDEV2\DEXIA_JOBS.ORA
channel ORA_AUX_DISK_1: reading from backup piece F:\ORACLE\BACKUP\BACKUP_DPBSPR
ORA-19870: error reading backup piece F:\ORACLE\BACKUP\BACKUP_DPBSPRD1_BLJ7VKO3
ORA-19505: failed to identify file "F:\ORACLE\BACKUP\BACKUP_DPBSPRD1_BLJ7VKO3"
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
failover to previous backup
thanks for your help
Regards

can you post your connection string to the source and auxillary databases please. with a duplicate you don't need to copy any files, rman does the whole process for you.
regards
Alan

Restore Database with Oracle 9i with a New Host using RMAN

Gurus,
I am trying to restore a database from some RMAN created files on a new host with a new directory structure for some testing. I do not have access to the source database.
The database is Oracle 9i.
The files that have been created are the following:
'C-2995630462-20110214-00' is the control file and SP file backup.
'B_ABM4KAJ5_1_1' is the database backup.
B_ACM4KARS_1_1 and B_AAM4KAIV_1_1 are archived redo logs
Here is the RMAN listing from when the files were created:
BS Key Size Device Type Elapsed Time Completion Time
329 56M DISK 00:00:02 14/FEB/11
BP Key: 329 Status: AVAILABLE Tag: TAG20110214T050015
Piece Name: D:\BACKUPS\CRYSTAL\B_AAM4KAIV_1_1
List of Archived Logs in backup set 329
Thrd Seq Low SCN Low Time Next SCN Next Time
1 184 4602414767 13/FEB/11 4602533494 14/FEB/11
BS Key Type LV Size Device Type Elapsed Time Completion Time
330 Full 13G DISK 00:04:33 14/FEB/11
BP Key: 330 Status: AVAILABLE Tag: TAG20110214T050021
Piece Name: D:\BACKUPS\CRYSTAL\B_ABM4KAJ5_1_1
List of Datafiles in backup set 330
File LV Type Ckp SCN Ckp Time Name
1 Full 4602533509 14/FEB/11 D:\ORACLE\ORADATA\CRYSTAL\SYSTEM01.DBF
2 Full 4602533509 14/FEB/11 D:\ORACLE\ORADATA\CRYSTAL\UNDOTBS01.DBF
3 Full 4602533509 14/FEB/11 D:\ORACLE\ORADATA\CRYSTAL\USERS01.DBF
BS Key Size Device Type Elapsed Time Completion Time
331 37K DISK 00:00:01 14/FEB/11
BP Key: 331 Status: AVAILABLE Tag: TAG20110214T050500
Piece Name: D:\BACKUPS\CRYSTAL\B_ACM4KARS_1_1
List of Archived Logs in backup set 331
Thrd Seq Low SCN Low Time Next SCN Next Time
1 185 4602533494 14/FEB/11 4602533686 14/FEB/11
BS Key Type LV Size Device Type Elapsed Time Completion Time
332 Full 3M DISK 00:00:01 14/FEB/11
BP Key: 332 Status: AVAILABLE Tag:
Piece Name: D:\BACKUPS\CRYSTAL\C-2995630462-20110214-00
SPFILE Included: Modification time: 23/NOV/10
I am new to using RMAN and I'm hoping someone could point me in a direction of some documentation to assist with the scenario described above. I've looked at several Oracle documents but have been unable to find a way to separate out the spfile from the control file.
Any help you can provide would be greatly appreciated.
Thanks.

Thanks Meeran.
I have attempted to follow the directions from the RMAN document that you posted and have run into the following error:
C:\>rman target / nocatalog
Recovery Manager: Release 9.2.0.6.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: DUMMY (not mounted)
using target database controlfile instead of recovery catalog
RMAN> startup force nomount
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file 'C:\ORACLE\ORA92\DATABASE\INITCRYSTAL.O
RA'
trying to start the Oracle instance without parameter files ...
Oracle instance started
Total System Global Area 97591104 bytes
Fixed Size 454464 bytes
Variable Size 46137344 bytes
Database Buffers 50331648 bytes
Redo Buffers 667648 bytes
RMAN> RESTORE SPFILE TO 'C:\oracle\admin\crystal\pfile\init.ora' from 'C:\oracle
\ora92\CRYSTALbk\C-2995630462-20110214-00';
Starting restore at 30-MAR-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 03/30/2011 11:30:07
ORA-00600: internal error code, arguments: [1866], [0x41AA450], [6144], [0x41BAD
B4], [], [], [], []
RMAN>
Am I not correctly connected to the target?
It looks like it correctly tried to create a dummy spfile, but when attempting the restore from the file it breaks.
Any suggestions? Thanks.

SQL Server 2012 restoring database from backup file

Hi All,
1. I was restoring the database from PROD box to DEV box with the deferent name.
For Ex: Both PROD and DEV boxes are having "A" database. Now I am refreshing database"A" from PROD bot to DEV box with name "B". Now while restoring in SQL server 2012 I used GUI and took database name as "A" by default.
by mistake I executed the request. before completing I notice that "A" database in DEV Box went to restoring mode.
Now, in middle I stopped the query but still I am seeing database "A" is in restoring state.
Please guide me is there any way to bring database online with current data?
2. Why sql server 2012 takes tail log backup of the existing database while restoring database with different name?

Hi,
check this link for the same issue and solutions:
http://stackoverflow.com/questions/520967/sql-server-database-stuck-in-restoring-state
Ronen Ariely
[Personal Site] [Blog] [Facebook]

Restore using incremental backup with noarchivelog mode

Hello experts,
We are running SAP on Oracle databse(IN NOARCHIVELOG MODE) for which we are having full offline backup on every sunday and post which incremental backups on rest of the days. We have scenario to do restore db to the state till last friday's incremental backup.
Please let us know the procedure for restoring till that point. If possible using brtools utility(which is SAP specific).
Thank You
Regards,
Venkateshwar

If you do not want to read the whole doc This is the snippet for you.
Recovering a NOARCHIVELOG Database with Incremental Backups
Restoring a database running in NOARCHIVELOG mode is similar to restoring a database in ARCHIVELOG mode. The main differences are:
Only consistent backups can be used in restoring a database in NOARCHIVELOG mode.
Media recovery is not possible because no archived redo logs exist.
You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. The incremental backups must be consistent, like all backups of a database run in NOARCHIVELOG mode, so you cannot make backups of the database when it is open.
When you are recovering a NOARCHIVELOG database, specify the NOREDO option on the RECOVER command to indicate that RMAN should not attempt to apply archived redo logs. Otherwise, RMAN returns an error.
To recover a NOARCHIVELOG database with incremental backups:
After connecting to the target database and the recovery catalog, place the database in a mounted state:
STARTUP FORCE MOUNT
Restore and recover the database.
For example, you can perform incomplete recovery with the following commands:
RESTORE DATABASE
FROM TAG "consistent_whole_backup";
RECOVER DATABASE NOREDO;
Open the database with the RESETLOGS option.
For example, enter the following command:
ALTER DATABASE OPEN RESETLOGS;

Restore database noarchivelog to another server in ASM

I have to migrate a database 10g with noarchivelog with filesystem to another server with ASM.
Could you help me to do it?
Thanks.

ok, I put the database in archivelog but I don`t understando the link "http://www.oracleflash.com/10/How-to-migrate-Oracle-datafiles-to-ASM-storage-via-RMAN.html".
First, I have moved the database to the new server, now I have the database with filesystem but in the final server with archivelog. OK.
The steps are:
first, I have to modify the parameters of db_create_file_dest, etc, to +ASM.
I hve to shutdown the database, open nomount, restore controlfile and backup as copy.
Is it correct?,
one question, the restore controlfile, I suppose that I have to have a previous backup with filesystem of controlfile?
Thanks.

Problem with restore database in sql server 2008

hi,,,when i want to restore database from a .bak file i see this error
TITLE: Microsoft SQL Server Management Studio
Restore failed for Server 'ALI-PC'. (Microsoft.SqlServer.SmoExtended)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1447.4+((KJ_RTM).100213-0103+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The database was backed up on a server running version 10.50.4000. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a
backup that is compatible with this server. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1447.4+((KJ_RTM).100213-0103+)&LinkId=20476
BUTTONS:
OK
i checked overwrite the existing database(WUTH REPLACE) in option,but i cant restore again,,,please help me

Hi,
You need to install SQL Server 2008 R2 Service Pack 2
Download
http://www.microsoft.com/en-us/download/details.aspx?id=11093, you are currently running the RTM and the backup was from Version 10.50.4000 and your attempting to restore to version 10.00.1600.
To find your current SQL Version open a New Query and paste the following then execute
SELECT @@VERSION AS 'SQL Server Version
Reference:
http://sqlserverbuilds.blogspot.com/
http://support.microsoft.com/kb/321185
http://technet.microsoft.com/en-us/library/ms177512.aspx
Cheers,
-Ivan

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

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.

Problem with restoring database from backupset

Hello,
I'm newie in working with RMAN and I have problem with restoring database from backup set in my testcase.
I've restored controlfile, but I couldn't restore database - it fails with:
RMAN-00571: =============================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =============================================
RMAN-03002: failure of restore command at 08/31/2006 12:06:47
ORA-01180: can not create datafile 1
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\LOCA10G2\SYSTEM01.DBF'
List of backupsets from restored controlfile
(I restored controlfile by command: restore controlfile from 'C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP'; -- I have disabled controlfile autobackup, therefore I couldn't restore from autobackup);
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
36 Full 6.98M DISK 00:00:02 29-AUG-06
BP Key: 36 Status: AVAILABLE Compressed: NO Tag: 01_CTL
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCNNF_01_CTL_2H82NDQT_.BKP
Control File Included: Ckp SCN: 578469 Ckp time: 29-AUG-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
37 Full 322.96M DISK 00:00:27 29-AUG-06
BP Key: 37 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113622
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NNNDF_TAG20060829T113622_2H82NQ58_.BKP
List of Datafiles in backup set 37
File LV Type Ckp SCN Ckp Time Name
1 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\SYSTEM01.DBF
2 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\UNDOTBS01.DBF
3 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\SYSAUX01.DBF
4 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\USERS01.DBF
BS Key Size Device Type Elapsed Time Completion Time
38 650.50K DISK 00:00:00 29-AUG-06
BP Key: 38 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113804
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_ANNNN_TAG20060829T113804_2H82QYOV_.BKP
List of Archived Logs in backup set 38
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 577277 29-AUG-06 578529 29-AUG-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
39 Full 7.02M DISK 00:00:00 29-AUG-06
BP Key: 39 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113622
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP
Control File Included: Ckp SCN: 578493 Ckp time: 29-AUG-06
SPFILE Included: Modification time: 28-AUG-06
I can successfully crosscheck backup sets (by command crosscheck backup), but I couldn't restore database.
Path C:\ORACLE\ORADATA\LOCA10G2\ exists and I have right privileges.
Output of command restore database validate:
RMAN> restore database validate;
     Starting restore at 31-AUG-06
     allocated channel: ORA_DISK_1
     channel ORA_DISK_1: sid=102 devtype=DISK
     data file 1 will be created automatically during restore operation
     data file 2 will be created automatically during restore operation
     data file 3 will be created automatically during restore operation
     data file 4 will be created automatically during restore operation
     restore not done; all files readonly, offline, or already restored
     Finished restore at 31-AUG-06
What's wrong?
Thanks
     Paul

Hi,
I think, that everything seems to be OK.
Commands which I use to validation of existence backup:
RMAN> crosscheck backup;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=102 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCNNF_01_CTL_2H82NDQT_.BKP recid=36 stamp=599744172
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NNNDF_TAG20060829T113622_2H82NQ58_.BKP recid=37 stamp=599744183
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_ANNNN_TAG20060829T113804_2H82QYOV_.BKP recid=38 stamp=599918805
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP recid=39 stamp=599918805
Crosschecked 4 objects
RMAN> list backup summary;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
36 B F A DISK 29-AUG-06 1 1 NO 01_CTL
37 B F A DISK 29-AUG-06 1 1 NO TAG20060829T113622
38 B A A DISK 29-AUG-06 1 1 NO TAG20060829T113804
39 B F A DISK 29-AUG-06 1 1 NO TAG20060829T113622
RMAN> list backup;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
36 Full 6.98M DISK 00:00:02 29-AUG-06
BP Key: 36 Status: AVAILABLE Compressed: NO Tag: 01_CTL
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCNNF_01_CTL_2H82NDQT_.BKP
Control File Included: Ckp SCN: 578469 Ckp time: 29-AUG-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
37 Full 322.96M DISK 00:00:27 29-AUG-06
BP Key: 37 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113622
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NNNDF_TAG20060829T113622_2H82NQ58_.BKP
List of Datafiles in backup set 37
File LV Type Ckp SCN Ckp Time Name
1 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\SYSTEM01.DBF
2 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\UNDOTBS01.DBF
3 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\SYSAUX01.DBF
4 Full 578481 29-AUG-06 C:\ORACLE\ORADATA\LOCA10G2\USERS01.DBF
BS Key Size Device Type Elapsed Time Completion Time
38 650.50K DISK 00:00:00 29-AUG-06
BP Key: 38 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113804
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_ANNNN_TAG20060829T113804_2H82QYOV_.BKP
List of Archived Logs in backup set 38
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 577277 29-AUG-06 578529 29-AUG-06
BS Key Type LV Size Device Type Elapsed Time Completion Time
39 Full 7.02M DISK 00:00:00 29-AUG-06
BP Key: 39 Status: AVAILABLE Compressed: NO Tag: TAG20060829T113622
Piece Name: C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP
Control File Included: Ckp SCN: 578493 Ckp time: 29-AUG-06
SPFILE Included: Modification time: 28-AUG-06
RMAN> restore database validate;
Starting restore at 04-SEP-06
using channel ORA_DISK_1
data file 1 will be created automatically during restore operation
data file 2 will be created automatically during restore operation
data file 3 will be created automatically during restore operation
data file 4 will be created automatically during restore operation
restore not done; all files readonly, offline, or already restored
Finished restore at 04-SEP-06
Is something wrong? After crosscheck backup set with system datafile is AVAILABLE.
If i tried to test existence of backup pieces on disk and permissisons - everything is OK too:
C:\>dir C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\
Volume in drive C has no label.
Volume Serial Number is E003-9FC6
Directory of C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29
29.08.2006 11:38 <DIR> .
29.08.2006 11:38 <DIR> ..
29.08.2006 11:38 666 624 O1_MF_ANNNN_TAG20060829T113804_2H82QYOV_.BKP
29.08.2006 11:36 7 340 032 O1_MF_NCNNF_01_CTL_2H82NDQT_.BKP
29.08.2006 11:37 7 372 800 O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP
29.08.2006 11:36 338 657 280 O1_MF_NNNDF_TAG20060829T113622_2H82NQ58_.BKP
4 File(s) 354 036 736 bytes
2 Dir(s) 56 865 202 176 bytes free
C:\>copy C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\ C:\ORACLE\ORADATA\LOCA10G2\
C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_ANNNN_TAG20060829T113804_2H82QYOV_.BKP
C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCNNF_01_CTL_2H82NDQT_.BKP
C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NCSNF_TAG20060829T113622_2H82OW77_.BKP
C:\ORACLE\FLASH_RECOVERY_AREA\LOCA10G2\BACKUPSET\2006_08_29\O1_MF_NNNDF_TAG20060829T113622_2H82NQ58_.BKP
4 file(s) copied.
Thanks
Pavel

AUto-renaming mdf & ldf filenames when restoring a database with SQL Management Studio

Hi!
I am using SQL Management Studio 2014 and I am experiencing some problems when restoring a database backup.
I have a SQL Server 2008R2 & SQL Server 2012 instances.
On the 2012 instance, when I restore a database and rename it into a new name, the mdf and ldf files get automatically renamed into the new database name : Great, this is the behavior that I expect.
On the 2008R2 instance, the mdf and ldf files don't automatically get renamed to match the new database name and I have to perform the renaming manually - pretty annoying.
Has anybody experienced this problem ? If yes, do you know of a fix ?
Thank you
Frederic

Hi,
You are using an external tool (SSMS GUI interface) which give you some behaviors like default names. this is very simple, just use a simple query to restore the database and dont use the GUI if you dont like its behavior
(this behavior might change from time to time). You can use the profiler to make sure what is
the real query that the SSMS sent to the server.
>> How to: Restore a Database to a New Location and Name (Transact-SQL)
http://technet.microsoft.com/en-us/library/ms190447(v=sql.105).aspx
-- use any name that you want in the restore
RESTORE DATABASE MyNewAdvWorks
FROM AdventureWorks2008R2_Backup
WITH RECOVERY,
MOVE 'AdventureWorks2008R2_Data' TO 'D:\MyData\MyNewAdvWorks_Data.mdf',
MOVE 'AdventureWorks2008R2_Log' TO 'F:\MyLog\MyNewAdvWorks_Log.ldf'
GO
Ronen Ariely
[Personal Site] [Blog] [Facebook]

Attempting to restore database to same server with different name.

I have just restored my production database to an earlier backup to recover from a major application error.
I now need to reatore a second copy of the database to recover some data which was lost as a result of the restore. The only place I can do this is on the same server.
I can't use duplicate database because the time I want is before the resetlogs time of the current version.
I don't think I can use recover using backup controlfile because restoring the control file will have the old database name. Can I restore the control file, rename the database and still use the rman backups of the original database?
If so how?
Can use set incarnation to get round the resetlogs issue without affecting the current database?
10gR2
Windows 2008 64-bit
Edited by: Jim Smith on Oct 27, 2011 8:54 PM

Hi
Database name can be the same ORACLE_SID must be unique on the machine and in specific ORACLE_HOME.
So effectively you can have 2 databases with the same name but instance names must be unique.
Paul

Restoring database with NOARCHIVELOG

Similar Messages

Maybe you are looking for