Restore database failed

Hello,
I was trying to restore a database but it says failed, very backup data says verified but the restoration fails, tried also by using the following query
restore filelistonly
from disk = 'D:\GrantApp.bak'
go
restore database GrantApp
from disk = 'D:\GrantApp.bak'
with move 'GrantApp' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf',
move 'GrantApp_log' to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'
but this gives me error as 
(2 row(s) affected)
Msg 3634, Level 16, State 1, Line 1
The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf'.
Msg 3156, Level 16, State 5, Line 1
File 'GrantApp' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp.mdf'. Use WITH MOVE to identify a valid location for the file.
Msg 3634, Level 16, State 1, Line 1
The operating system returned the error '5(Access is denied.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'.
Msg 3156, Level 16, State 5, Line 1
File 'GrantApp_log' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\GrantApp_log.ldf'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.

Did you try restoring to the same path but with different MDF and LDF names?  What was the outcome? 
Does the database currently exist and thus you are trying to overwrite it?  
Can you create a new database in the same folder using syntax similar to this:
CREATE
DATABASE[test]
ON 
PRIMARY
NAME=N'test',FILENAME=N'C:\Program
Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\test.mdf',SIZE=4096KB,MAXSIZE=UNLIMITED,FILEGROWTH=1024KB)
LOG
ON
NAME=N'test_log',FILENAME=N'C:\Program
Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\test_log.ldf',SIZE=1024KB,MAXSIZE=2048GB,FILEGROWTH=10%)
GO

Similar Messages

  • Restore database failed on Oracle 10g 10.2.0.1 linux 32 bit

    Hi,
    I am working on test database for testing database disaster recovery.
    1) i made full database backup by RMAN and ui also have archive log
    2) i noted DBID and all folders of database
    3)Turn on the Controlfile auto backup
    4) then i drop database
    5) then i follow all the steps , which include restoration of spfile and controlfile
    6)After that when i have mounted database and in RMAN WRITING RESTORE DATABASE, it is giving following error.
    Starting restore at 02-APR-08
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 04/02/2008 17:54:56
    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
    Please help me
    Regards,

    1) i made full database backup by RMAN and ui also
    have archive logWhat's the command used?
    2) i noted DBID and all folders of databaseWhat's inside the folders.
    ls -l <your folder>
    3)Turn on the Controlfile auto backup
    4) then i drop databaseHow did you drop it? delete files from OS? or DROP DATABASE statement?
    5) then i follow all the steps , which include
    restoration of spfile and controlfileWhat's the steps you followed? And from where you got the steps.
    6)After that when i have mounted database and in RMAN
    WRITING RESTORE DATABASE, it is giving following
    error.
    Starting restore at 02-APR-08
    using channel ORA_DISK_1
    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
    restoreOracle Error :: RMAN-06026
    some targets not found - aborting restore
    Cause
    Some of the files specified for restore could not be found. Message 6023, 6024, or 6025 is also issued to indicate which files could not be found. Some common reasons why a file can not be restored are that there is no backup or copy of the file that is known to recovery manager, or there are no backups or copies that fall within the criteria specified on the RESTORE command, or some datafile copies have been made but not cataloged.
    Action
    The Recovery Manager LIST command can be used to display the backups and copies that Recovery Manager knows about. Select the files to be restored from that list.

  • Restore database to azure blob failed

    Hi experts,
      I create a test db in SQL on Azure VM and backup to my storage account successfully. However, when I delete the database and restore using the T-SQL below, it failed. Please help.
    --- query ---
    USE [master]
    RESTORE DATABASE [test] FROM  
    URL = N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014/test_backup_2014_08_18_013128.bak' 
    WITH  CREDENTIAL = N'AzureCredential' ,  FILE = 1,  
    MOVE N'test' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf',  
    MOVE N'test_log' TO N'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf',  NOUNLOAD,  STATS = 5
    GO
    --- result ---
    Msg 3634, Level 16, State 1, Line 2
    The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'.
    Msg 3156, Level 16, State 8, Line 2
    File 'test' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test.mdf'. Use WITH MOVE to identify a valid location for the file.
    Msg 3634, Level 16, State 1, Line 2
    The operating system returned the error '50(The request is not supported.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'.
    Msg 3156, Level 16, State 8, Line 2
    File 'test_log' cannot be restored to 'https://sa1qcisapdr.blob.core.windows.net/tcd-sql2014//test_log.ldf'. Use WITH MOVE to identify a valid location for the file.
    Msg 3119, Level 16, State 1, Line 2
    Problems were identified while planning for the RESTORE statement. Previous messages provide details.
    Msg 3013, Level 16, State 1, Line 2
    RESTORE DATABASE is terminating abnormally.

    One has to install Azure Storage Explorer and add Read/Write permissions in Shared Access Key

  • "Error restoring Databases" SMS import failing!

    Hey all-
    I keep getting an "error restoring databases" message when trying to put all of the SMS texts from my Curve 8330 onto my World Edition.  I did this yesterday and it worked fine.  The problem is the screen on my curve is dead so until I get a new one, I have to keep making backup files and uploading them onto my world edition so I can see my texts/phone calls that I've been receiving on the curve.
    I managed to do this successfully yesterday morning but since then I keep getting this error message.  I have tried clearing the SMS on the World then pulling in just the SMS from the backup file, full deviced transfers and partial/full restores!   All of them are giving me the same "error restoring databases" and it may pull in a few of the 1334 texts I have to import.
    Both Blackberrys are up to date OS-wise and BB Desktop Manager is v5
    Any help would be appreciated!!!  THANKS

    Hi,
    The IMP indicates this this error is coming from the old imp. This dump file could be from the expdp utility, which would require you to use the impdp utility.
    Source
    OS : Solaris 10
    Oracle version : 11.2.0.2
    Export dump : exp_CAAU2.dmp.gz (Export taken by zipping)
    Target
    OS : Windows server 2003
    Oracle Version : 10.2.0.2.0
    While importing into windows env, it is failing..
    What really matters here is the compatibility level. If your source and target compatibility levels are the same, then with Data Pump, the dumpfile created on the source, would work on the target. If the compatibility levels are different, then use expdp with the version parameter set to the compatibility level of the target.
    Please let me know the reason why the import is failing?Check the suggestions above first.
    Can i upgrade the target oracle version to 11.2.0.2 to succeed the import?It could help, but first check to see if you are using the right utility and then check the compatibility versions.
    Dean

  • File name in msdb.dbo.backupset no longer matches the actual file name on the storage media. Error 3013 Restore Database is terminating abnormally.

    Thanks in advance for taking the time to read this and comment. Platform: Windows Server 2008 R2 Enterprise Edition SP1 (X64) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) Jun 17 2011 00:54:03 Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)Problem Description: The file name recorded in the msdb.dbo.backupset (sans the extension) no longer matches the actual file name written to the backup media which is
    in this case a NETAPP NAS storage share. Example:
    Mohave_backup_2014_03_14_233001_1158878.bak      (from NETAPP NAS filer)
    Mohave_backup_2014_03_16_233001_4167237             (from MSDB.dbo.backupset), as you can see, the last 7 digits (chars) of the file name are different, although the date and time are identical. The
    file names had previously been matching perfectly. The first occurance of this problem occured on 03/13/2014 at 5:00 AM MST. The error generated by the job was:
    Date  3/14/2014 10:29:23 AM
    Log  Job History (Refresh - Restore Mohave_93_DEV AD HOC)
    Step ID  1
    Server  OurDevServer
    Job Name  Refresh - Restore Mohave_93_DEV AD HOC
    Step Name  Restore Mohave_93_DEV
    Duration  00:00:01
    Sql Severity  0
    Sql Message ID  50000
    Operator Emailed  
    Operator Net sent  
    Operator Paged  
    Retries Attempted  0
    Message
    Executed as user: OurDomain\OurNetworkServiceLogin. Restore Mohave Prod to Mohave_93_DEV - ERROR: 3013 RESTORE DATABASE is terminating abnormally. [SQLSTATE 01000] (Message 50000).  The step succeeded.

    Olaf:
    Thanks for your reply. Sorry, my bad. I inadvertently copied wrong [name] form the msdb.dbo.backupset. On 3/13 and 3/14, the two file names did not match. In trying to select another example to show you this morning, I found that the names are now matching!
    What I was doing was to create dynamic t-sql to retrieve the latest prod backup of the database, and then restore it with move to the development server. This is an ad-hoc job that the developers can run by themselves whenever they require a refresh. Unfortunately,
    we only keep 3 days worth of backups for these databases, so the original disk file I was trying to use to restore no longer exists. Researching the original error, one of the error descriptions was that the restore could not find the file requested.
    I thought this very strange since I get the file name directly from the backupset table. Further research did indeed show that the file names were different, but unfortunately, I failed to save the details of the file names. Anyway, in looking for a new example
    to show you this morning, I have found that the file names are indeed matching exactly again. If this error pops up again, I will be sure to save all details and re-post.
    Thanks, regards and best wishes to you and yours, 

  • SharePoint Search Service Application Restore Is Failing

    Issue:
    When performing a Search Service restore with the CA UI, the restore is failing. The backup was generated from a Full level backup that is run nightly from the cmdlet Backup-SPFarm.  The Farm is running SharePoint 2013 SP1, Windows Server 2012 And SQL
    Server 11.0.3128. Both Production and the test environment have the same topology.
    The sprestore.log file shows the following error message:
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint id for this application is 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928'.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'b8b92dc6-38b3-49bf-90bc-d9ea64dcf928' to this application.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] The default endpoint has been found and set.  NOTE: The id of the default endpoint will be different than specified in the logs if
    the restore mode is not 'overwrite'.
    [12/17/2014 12:37:51 PM] Verbose: [Search Service Application] Re-parented endpoint 'bb456994-47ac-4bad-9197-9a4d5b39bf5c' to this application.
    [12/17/2014 12:37:55 PM] FatalError: Object Search Service Application failed in event OnPostRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory.
            SqlException: The database principal owns a database role and cannot be dropped.
    User does not have permission to perform this action.
    [12/17/2014 12:37:55 PM] Debug:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj,
    Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean
    asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout,
    Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
       at Microsoft.Office.Server.Data.SqlDatabaseManager.GrantAccess(String user)
       at Microsoft.Office.Server.Search.Administration.SearchDatabase.GrantAccess(String username, String role)
       at Microsoft.Office.Server.Search.Administration.SearchDatabase.SynchronizeAccessRules(SearchServiceApplication searchApp)
       at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.SynchronizeDatabases()
       at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision()
       at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPostRestore(Object sender, SPRestoreInformation info)
    A SQL Profile was run beginning at 12/18/2014 11:11.
    A SQL exception can be found at 11:20:03 with the error:
                   The database principal owns a database role and cannot be dropped.
    The issue has to do with the SQL statement just prior to the exception:
    declare @p4 int
    set @p4=NULL
    declare @p5 int
    set @p5=NULL
    exec sp_executesql N'declare @db_user_name sysname
    select @db_user_name = name from dbo.sysusers where sid = SUSER_SID(@user_name) and hasdbaccess = 1
    if (@db_user_name is null)
    begin
    if exists(select * from dbo.sysusers where name = @user_name)
    exec @revoke_result = sp_revokedbaccess @user_name
    exec @grant_result = sp_grantdbaccess @user_name, @db_user_name output
    end',N'@user_name nvarchar(128),@revoke_result int output,@grant_result int output',@user_name=N'----\sp2013uatfarmacct',@revoke_result=@p4 output,@grant_result=@p5 output
    select @p4, @p5
    I highlighted the row in red causing the issue. For some reason SharePoint during the Search Restore process try’s to delete the user “------\sp2013uatfarmacct” from the database Search_Service_Application_DB_60bb9889222841aa94f59aed71349a6b
    And re-add them again.  But the reason for the failure is because the user “------\sp2013uatfarmacct” is the owner of the database role “SPSearchDBAdmin”, so it cant.
    I checked all other Service databases that contain the role SPSearchDBAdmin and they all correctly have the owner as dbo
    NOT ------\sp2013uatfarmacct.
    Further checking the SQL trace log a SQL batch is executed at 12/18/2014 11:19:59.790 that states the following:
    -- Drop existing role members
    IF  EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
    Begin
        DECLARE @RoleMemberName sysname
        DECLARE Member_Cursor CURSOR FOR
        SELECT [name]
        FROM sys.database_principals
        WHERE
            principal_id IN
                SELECT member_principal_id
                from sys.database_role_members
                where role_principal_id in (
                select principal_id
                FROM sys.database_principals where [name] = N'SPSearchDBAdmin'  AND type = 'R' ))
        OPEN Member_Cursor;
        FETCH NEXT FROM Member_Cursor
        into @RoleMemberName
        WHILE @@FETCH_STATUS = 0
        BEGIN
            exec sp_droprolemember @rolename=N'SPSearchDBAdmin', @membername= @RoleMemberName
            FETCH NEXT FROM Member_Cursor
            into @RoleMemberName
        END;
        CLOSE Member_Cursor;
        DEALLOCATE Member_Cursor;
    End
    -- Drop/Create role
    IF  EXISTS (SELECT * FROM sys.database_principals WHERE name = N'SPSearchDBAdmin' AND type = 'R')
    DROP ROLE [SPSearchDBAdmin]
    CREATE ROLE [SPSearchDBAdmin]
    I highlighted the statement in red that is eventually causing the SP restore to fail. For some unknown reason to me when this statement is executed the new ROLE SPSearchDBAdmin owner is -----\sp2013uatfarmacct
    instead of dbo.
    As a test I executed via SQL Management Studio “CREATE ROLE [SPSearchDBAdmin]” and it correctly created the owner as dbo.
    So the problem and my question is why when the SP Search Service is restored is the ROLE SPSearchDBAdmin owner being set to “-----\ sp2013uatfarmacct”, which in turn seems to be causing the restore failure?

    Hi!
    I believe it is trying to delete a user who owns the schema of the database. You can try changing the schema owner to some other user like "dbo", and then drop the first user.
    Below are a few links that can help you with much more details.
    http://blogs.technet.com/b/mdegre/archive/2010/12/19/the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped.aspx
    http://littletalk.wordpress.com/2009/11/09/fix-for-the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped-error-in-sql-server-2005/
    http://dotnetgun.blogspot.com/2011/02/database-principal-owns-schema-in.html
    Thanks,
    Owens
    Owens G. Jesse

  • 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

  • Error during Restore Database

    Hello everyone!
    First of all, i'm sorry for posting another restore problem, but i read all threads related and i still have my problem.
    I have a fresh new install of oracleXE, but when i try to restore de database from a backup store in other disk install in the same computer, using the restore database option include with the application, the program show me these steps:
    STEP 1:
    This operation will shut down and restore the database. Are you sure [Y/N]?
    I write 'Y'.
    STEP 2:
    This operation will shut down and restore the database. Are you sure [Y/N]?y
    Restore in progress...
    El servicio solicitado ya ha sido iniciado.
    Puede obtener más ayuda con el comando NET HELPMSG 2182.
    Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:20:45 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    conectado a la base de datos destino: XE (DBID=2513092923)
    RMAN> set echo on;
    2> startup nomount pfile=C:\DOCUME~1\imgltda\CONFIG~1\Temp\rman_dummy.ora force;
    3>
    echo activado
    instancia Oracle iniciada
    Total del ┴rea Global del Sistema 285212672 bytes
    Fixed Size 1287016 bytes
    Variable Size 92277912 bytes
    Database Buffers 188743680 bytes
    Redo Buffers 2904064 bytes
    Recovery Manager terminado.
    Enter the flash recovery area location:
    I write this in my flash recovery area, where i have the backup files: D:\Respaldo.
    In this path i have de following folders: D:\Respaldo\XE; Inside this folder i have other folders: ARCHIVELOG, AUTOBACKUP, BACKUPSET, ONLINELOG.
    STEP 3 This is my problem:
    MAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
    RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destina
    tion string cannot be translated
    ORA-01263: Name given for file destination directory is invalid
    OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
    O/S-Error: (OS 21) El dispositivo no est┐ listo.
    Recovery Manager terminado.
    ==================== ERROR =============================
    Restore of the database failed.
    RMAN Error - See log for error .
    Log file is at C:\ORACLEXE\APP\ORACLE\PRODUCT\10.2.0\SERVER\DATABASE\OX
    E_RESTORE.LOG.
    ==================== ERROR =============================
    Presione una tecla para continuar . . .
    The OXE_RESTORE file show me this:
    Recovery Manager : Release 10.2.0.1.0 - Production on Vie Ago 31 10:23:58 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    Windows XP Version V5.1 Service Pack 2
    CPU : 2 - type 586
    Process Affinity : 0x00000000
    Memory (Avail/Total): Ph:1652M/2021M, Ph+PgF:3435M/3914M, VA:2003M/2047M
    Starting with debugging turned off
    conectado a la base de datos destino: xe (no montada)
    RMAN> set echo on;
    2> restore (spfile from autobackup db_recovery_file_dest='D:\Respaldo');
    3> startup nomount force;
    4> restore (controlfile from autobackup);
    5> alter database mount;
    6> configure controlfile autobackup off;
    7> restore database;
    8>
    echo activado
    Iniciando restore en 31/08/07
    se utiliza el archivo de control de la base de datos destino en lugar del catálogo de recuperación
    canal asignado: ORA_DISK_1
    canal ORA_DISK_1: sid=37 devtype=DISK
    destino del área de recuperación: D:\Respaldo
    nombre de base de datos (o nombre único de base de datos) utilizado para la búsqueda: XE
    canal ORA_DISK_1: se ha encontrado una copia de seguridad automática en el área de recuperación
    canal ORA_DISK_1: se ha encontrado la copia de seguridad automática: D:\RESPALDO\XE\AUTOBACKUP\2007_08_27\O1_MF_S_631711029_3F5TQOVT_.BKP
    canal ORA_DISK_1: restauración de SPFILE a partir de la copia de seguridad automática terminada
    restore terminado en 31/08/07
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: fallo del comando startup en 08/31/2007 10:24:10
    RMAN-04014: fallo al iniciar: ORA-01261: Parameter db_recovery_file_dest destination string cannot be translated
    ORA-01263: Name given for file destination directory is invalid
    OSD-04018: No se ha podido acceder al directorio o dispositivo especificado.
    O/S-Error: (OS 21) El dispositivo no est¿ listo.
    Recovery Manager terminado.
    I really do not know what is my problem and how to solve it. I hope you guys can help me. I'm under a big pressure to solve this soon.
    My Operating System is: WinXP Pro
    I'm using APEX 2.01
    When I create the backup I use ARCHIVELOG enable
    Things i try:
    1. Install fresh oracle XE database, and restore
    2. Install fresh oracle XE database, enable archivelog and restore
    3. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo'.
    4. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo', and execute: @?/sqlplus/admin/movelogs;
    5. Install fresh oracle XE database, enable archivelog, change path of DB_RECOVERY_FILE_DEST to 'D:\Respaldo';, and change DB_RECOVERY_FILE_DEST_SIZE to 20G;
    NOTE: sorry for my english it is not my native language. and sorry for using a spanish version of the database.
    Message was edited by:
    Minning

    Well,
    After a lot of reading, i try this using rman:
    SQL
    1. SQL> connect xx/xx as sysdba
    2. SQL> shutdown immediate
    RMAN
    1. RMAN> connect target XE
    2. RMAN> startup nomount;
    3. RMAN> restore spfile to 'C:\xe.ora' from 'D:\Respaldo\XE\AUTOBACKUP\2007_08_27\O
    1_MF_S_631711029_3F5TQOVT_.BKP';
    4. RMAN> alter database mount;
    5. RMAN> restore database;
    in point n°5 i have the following problem:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: fallo del comando restore en 09/06/2007 16:27:09
    RMAN-06026: no se han encontrado algunos destinos - abortando la restauraci¾n
    RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
    e datos 4 para restaurar
    RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
    e datos 3 para restaurar
    RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
    e datos 2 para restaurar
    RMAN-06023: no se ha encontrado ninguna copia de seguridad o copia del archivo d
    e datos 1 para restaurar
    I try this command to find what's going on:
    RMAN> list backup;
    with this result:
    Lista de Juegos de Copias de Seguridad
    ===================
    Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
    inalizaci¾n
    15 Full 736.04M DISK 00:00:19 24/08/07
    Clave BP: 15 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
    4938
    Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
    0824T124938_3DY3143F_.BKP
    Lista de Archivos de Datos en el juego de copias de seguridad 15
    Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
    1 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
    .DBF
    2 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
    BF
    3 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
    .DBF
    4 Full 2747434 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
    DBF
    Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
    inalizaci¾n
    16 Full 6.83M DISK 00:00:01 24/08/07
    Clave BP: 16 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T12
    5005
    Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631457405_
    3DY31Y0H_.BKP
    Archivo de Control Incluido: SCN de Punto de Control: 2747446 Hora de Pun
    to de Control: 24/08/07
    SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
    Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
    inalizaci¾n
    17 Full 736.04M DISK 00:00:20 24/08/07
    Clave BP: 17 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
    0028
    Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_24\O1_MF_NNNDF_TAG2007
    0824T170028_3DYKQGTC_.BKP
    Lista de Archivos de Datos en el juego de copias de seguridad 17
    Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
    1 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
    .DBF
    2 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
    BF
    3 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
    .DBF
    4 Full 2773728 24/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
    DBF
    Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
    inalizaci¾n
    18 Full 6.83M DISK 00:00:02 24/08/07
    Clave BP: 18 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070824T17
    0054
    Nombre de Parte: E:\RESPALDO\XE\AUTOBACKUP\2007_08_24\O1_MF_S_631472454_
    3DYKR7OZ_.BKP
    Archivo de Control Incluido: SCN de Punto de Control: 2773741 Hora de Pun
    to de Control: 24/08/07
    SPFILE Incluido: Hora de Modificaci¾n: 24/08/07
    Clave BS Tipo LV Tama±o Tipo de Dispositivo Tiempo Transcurrido Hora de F
    inalizaci¾n
    19 Full 740.95M DISK 00:00:20 27/08/07
    Clave BP: 19 Estado: EXPIRED Comprimido: NO Etiqueta: TAG20070827T11
    1642
    Nombre de Parte: E:\RESPALDO\XE\BACKUPSET\2007_08_27\O1_MF_NNNDF_TAG2007
    0827T111642_3F5TPWHN_.BKP
    Lista de Archivos de Datos en el juego de copias de seguridad 19
    Tipo de Archivo LV SCN Pto. Ctrl. Hora de Punto de Control Nombre
    1 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSTEM
    .DBF
    2 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\UNDO.D
    BF
    3 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\SYSAUX
    .DBF
    4 Full 2916556 27/08/07 C:\ORACLEXE\ORADATA\XE\USERS.
    DBF
    Where it says 'Estado' (Status in english) I found this: 'EXPIRED', it seems that my 4 dbf files have some problem, right now i'm looking for a way to solve this, but with no luck.
    I think i need a little help again...

  • 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

  • Attached database failed for sever "blah". (Microsoft.SqlServer.Smo)

    ===================================
    Attach database failed for Server 'DENR-HP'.  (Microsoft.SqlServer.Smo)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
    Program Location:
       at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
       at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabaseData.PrimaryFile.Attach()
       at Microsoft.SqlServer.Management.SqlManagerUI.AttachDatabase.SendDataToServer()
    ===================================
    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
    Program Location:
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection sqlCommands, ExecutionTypes executionType)
       at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection queries)
       at Microsoft.SqlServer.Management.Smo.Server.AttachDatabaseWorker(String name, StringCollection files, String owner, AttachOptions attachOptions)
       at Microsoft.SqlServer.Management.Smo.Server.AttachDatabase(String name, StringCollection files)
    ===================================
    The database 'PlanningDB' cannot be opened because it is version 655. This server supports version 611 and earlier. A downgrade path is not supported.
    Could not open new database 'PlanningDB'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)
    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=948&LinkId=20476
    Server Name: (local)
    Error Number: 948
    Severity: 20
    State: 1
    Line Number: 1
    Program Location:
       at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
       at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
       at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)

    Hi,
    As Olaf’s post, you cannot restore or attach a database which is created from a higher version of SQL Server to a lower version of SQL Server.
    However, there are some ways which can help you to move a database to a lower version of SQL Server. I recommend you to use Generate Scripts Wizard of SQL Server Management Studio (SSMS), you can script all the database objects in SQL Server 2008, then run
    the SQL scripts in SQL Server 2005, for more details, you can follow the steps in this blog:
    How to migrate a SQL Server database to a lower version. Also you can try to use the Import and Export Wizard to move database from SQL Server 2008 to SQL Server 2005,for more details, please review this article:
    How to: Run the SQL Server Import and Export Wizard.
    Thanks
    Lydia Zhang

  • Help me! cann't restore database using RMAN!!

    i've backuped database using RMAN,
    now datafile of system tablespace have lost,
    and i execute the command as following:
    run {
    allocate channel c1 type disk;
    restore database;
    these are errors:
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: restore
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: IRESTORE
    RMAN-06003: ORACLE error from target database: ORA-01843: not a
    valid month
    RMAN-06097: text of failing SQL statement: select decode(bitand
    (festa,(4096+128)
    ),128,fecps,4096,fecps,0) ,decode(bitand(festa,
    (4096+128)),128,281474976710655,4
    096,controlfile_change#,0) ,decode(bitand(festa,
    (4096+128)),128,SYSDATE,4096,con
    trolfile_time,to_date('JAN 01 1988','MON DD
    YYYY')) ,feofs ,feonc_scn ,to_date(n
    vl(feonc_tim,'01/01/88 00:01:01'),'MM/DD/RR HH24:MI:SS')
    into :b1,:b2,:b3,:b4,:b
    5,:b6 from x$kccfe ,v$database where (fenum=:b7 and fedup=1)
    RMAN-06099: error occurred in source file: krmk.pc, line: 21652

    Try setting the NLS_DATE_FORMAT at the command prompt.

  • RMAN Error - restore database validate

    Hi all
    I am trying to validate a full database backup taken on tape using 'restore database validate' command but for some reason this command spits out multi-page long PL/SQL code (below truncated output). I have searched all over for a solution but can't seem to figure out the problem.
    Any assistance will be appreciated.
    RMAN> allocate channel for maintenance type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
    2> crosscheck backup;
    3> restore database validate;
    4> release channel;
    5> exit;
    allocated channel: ORA_MAINT_SBT_TAPE_1
    channel ORA_MAINT_SBT_TAPE_1: SID=82 device type=SBT_TAPE
    channel ORA_MAINT_SBT_TAPE_1: Data Protection for Oracle: version 5.4.1.0
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=c-822607628-20101006-02 RECID=66 STAMP=731711718
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=DB_20101007_77_2dlpsj84_1_1.dbf RECID=67 STAMP=731794692
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=CF_20101008_116_3klpt5iv_1_1.ctl RECID=106 STAMP=731813472
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=c-822607628-20101008-01 RECID=107 STAMP=731813518
    Crosschecked 42 objects
    Starting restore at 08-OCT-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=110 device type=DISK
    DBGANY: CMD type=IRESTORE cmdid=1 status=NOT STARTED
    DBGANY: 1 STEPstepid=1 cmdid=1 status=NOT STARTED devtype=SBT_TAPE bs.stamp=731812991 step_size=0 Bytes
    DBGANY: 1 TEXTNOD = -- rsdf_start
    DBGANY: 2 TEXTNOD = declare
    DBGANY: 3 TEXTNOD = /* restoreStatus */
    DBGANY: 4 TEXTNOD = state binary_integer;
    DBGANY: 5 TEXTNOD = pieces_done binary_integer;
    DBGANY: 6 TEXTNOD = files binary_integer;
    DBGANY: 7 TEXTNOD = datafiles boolean;
    DBGANY: 8 TEXTNOD = incremental boolean;
    DBGANY: 9 TEXTNOD = device boolean;
    DBGANY: 10 TEXTNOD = /* restorebackuppiece */
    DBGANY: 11 TEXTNOD = done boolean;
    DBGANY: 12 TEXTNOD = currcf boolean;
    DBGANY: 266 TEXTNOD = sys.dbms_backup_restore.restoreCancel(FALSE);
    DBGANY: 267 TEXTNOD = exception
    DBGANY: 268 TEXTNOD = when others then
    DBGANY: 269 TEXTNOD = krmicd.writeMsg(1005,
    DBGANY: 270 TEXTNOD = 'c. dbms_backup_restore.restoreCancel() failed');
    DBGANY: 271 TEXTNOD = end;
    DBGANY: 272 TEXTNOD = sys.dbms_backup_restore.setRmanStatusRowId(rsid=>0, rsts=>0);
    DBGANY: 273 TEXTNOD = end;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: fatal error during execution of command
    RMAN-00600: internal error, arguments [6000] [] [] [] []

    Hi Sybrand
    So here's the deal:
    1) 'backup validate database;' is run before RMAN backup to check for any logical or physical corruption in datafiles or archivelogs.
    If the backup validation discovers corrupt blocks, then RMAN updates the V$DATABASE_BLOCK_CORRUPTION view with rows describing the corruptions.
    2)
    a- 'restore database validate;' is run after RMAN backup to check for any logical or physical corruption in backupsets.
    b- 'validate backupset <n>;' is also run after RMAN backup to check for any logical or physical corruption in backupsets. The difference being you have to run it for each individual backupset as opposed to the previous option (2a), which loops through all existing backupsets.
    I believe for now only option 2b is available for use in my case.
    Cheers.

  • RESTORE DATABASE USING SCRIPT

    Hi, I am using SQLEXPR 2008. I have take database Backup from 2008 SQL, Using Script and tried to restore the database on another machine having SQLEXPR 2012 Installed using SQL Script and getting Following  error 
    SQL Script :
    1.BACK UP :  BACKUP DATABASE
    test TO
    DISK='D:\SQLServerBackups\test.dat'
    2.RESTORE: RESTORE DATABASE test FROM DISK = 'D:\SQLServerBackups\test.dat' WITH REPLACE
    FOLLOWING ERROR
    1------------------------ 1 --- > WHY THIS ERROR -- THIS PATH WILL NOT BE THERE ON NEW MACHINE
    Directory lookup for the file "C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.APAYROLL\MSSQL\DATA\test.mdf" failed with the operating system error 3(The system cannot find the path specified.).
    2------------------------ 2
    File 'test' cannot be restored to 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.APAYROLL\MSSQL\DATA\test.mdf'. Use WITH MOVE to identify a valid location for the file.
    3------------------------ 3
    Directory lookup for the file "C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.APAYROLL\MSSQL\DATA\test_log.LDF" failed with the operating system error 3(The system cannot find the path specified.).
    4------------------------ 4
    File 'tran_BBLMS_Jan2015_Dec2015_log' cannot be restored to 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.APAYROLL\MSSQL\DATA\test_log.LDF'. Use WITH MOVE to identify a valid location for the file.
    Sandeep J. Sharma (eZee Technosys)

    SQL Server 2008 is product version 10.xxx and the default path used by a SQL Server 2008 has this as you can see in your example -
    C:\Program Files (x86)\Microsoft SQL Server\MSSQL10
    The backup includes this path for the files. This is where it will try to restore them unless you specify otherwise.
    The SQL Server 2012 is product version 11.xxx and it has \MSSQL11 mentioned in its path. Your SQL Server 2012 server does not have the MSSQL10 directory. So the backup restore fails.
    You need to use the MOVE keyword in the command.
    The REPLACE keyword that you are using means to overwrite an existing database with the same name in the SQL Server.
    Reference -
    Restore a Database to a New Location (SQL Server)
    https://msdn.microsoft.com/en-us/library/ms186390(v=sql.110).aspx
    - Aalamjeet Rangi | (Blog)

  • Can "Backup /  Restore Database " be ulized on two Different Platform

    I've been developing on Windows and now would lile port Database scheme/data /table
    "Everything" to a Linux Server.....
    Can I ftp the backup copy to Lunix were I just install same version of Oracle 10g express and run Restore Database...This would be easier then dumping application then tables then data ...etc and then importing
    CAN THIS WORK ..SHORT ON TIME
    Message was edited by:
    user518110

    Hello Hans,
    However, if you have environment-specific things,
    they will fail. I am not aware of any issues when moving Apex installations from one server to another. I have walked a user through this process of restoring an apex installation from a full database backup on a different server. There seem to be no server related references stored in the Apex repository.
    APEX seems to have some environment-dependant areas (OS file system mapping
    comes to mind) and that may cause grief. In a normal Apex installation (standalone) it has only references to the virtual directory /i/. This needs to be defined on the target server as well.
    This is even less a problem with regard to XE since the mapping it automatically available as the files are all stored in the XML DB.
    Regards,
    ~Dietmar.

Maybe you are looking for

  • Multi-server search failed on some of the servers

    Hi All, i am getting below error in our portal/advance search. Error during search occurred - com.sapportals.wcm.WcmException: multi-server search failed on some of the servers;error=2972,index=easywcmen;error=2972,index=itec_dept_indexen;error=2972,

  • How can I tell MDT to use the efisys_noprompt.bin as the bootloader used to create the litetouch.iso

    I would like to have an iso file that does not have the "press any key to boot from cd/dvd" prompt. I know how to do this manually but I would like to be able to set this somewhere so that MDT will use it whenever the iso is updated. Is there a scrip

  • Custom url resolving

    Hi, I have to migrate web application from tomee to weblogic. The problem is URL resolving.      In browser - url appears in the form : host:port/app/session_id/page  and weblogic then is trying to read a page under the directory: session_id/page in

  • Rookie Designer, please help

    I wanted to make a form that had a file attachment box, I set it up and installed it and tried it out but its only sending the name of the file and the root location and not the file itself, if you could assist me I would really appreciate it.

  • Ideas to Upgrade my Time Capsule hard drive

    I'm seeking specific help on HD selections to take my 0.5TB Time Capsule HD to at least 2.0TB.  I need help from those who've already upgraded.  Specifically, what brand and specific HD name did you use? Western Digital Caviar Green drives (WD20EARS)