Disaster recovery with different ASM starts

Hi@all,

in fact, I'm testing a scenario of recovery after a disaster. To an Oracle Linux 6 Server with installed grid below 12 c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 instance of database) I'm doing a recovery after a disaster. But I'm unleashed by the restoration and recovery of the database. The problem here is that ASM diskgroup name has changed. As you read I also changed the physical server, but I think that should not be a problem.

To the old server, I have two ASM starts '+ DATA' and '+ FRA_1', to the new, they are called '+ DATA_SRVNAME' and '+ FRA_SRVNAME '. I already changed the startup in spfile parameter, but now after restoring the controlfile RMAN has directions to the old diksgroup:

RMAN> report schema;


using target database control file instead of recovery catalog
RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
Report of database schema for database with db_unique_name SID


List of Permanent Datafiles
===========================
File Size(MB) Tablespace           RB segs Datafile Name
---- -------- -------------------- ------- ------------------------
1    0        SYSTEM               ***     +DATA/SID/datafile/system.438.816606399

So I tried three ways. First was rename data file name:

ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';

Then had to set the newname in RMAN:

set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';

And the second was to recreate the controlfile with

CREATE CONTROLFILE REUSE DATABASE "SID" RESETLOGS ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 254
    MAXINSTANCES 1
    MAXLOGHISTORY 1815
LOGFILE
  GROUP 1 ('+DATA__SRVNAME', '+FRA_SRVNAME')  SIZE 1024M,
DATAFILE
  '+DATASRVNAME/SID/datafile/system.438.816606399',
CHARACTER SET AL32UTF8;

But the three methods gave me the error that the file data to the new location is not available (for example):

ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist

So now my question: how am I able to say the controlfile or the database to use the another diskgroup in ASM?

I know, the simplest way would be to create a diskgroup + DATA and do the restore / recovery, but on the new server, I have no more storage to assign to a new diskgroup, and because there are running other forums I would'nt change ASM starts.

Do you have anny solution?

A big thank you and best regards,

Dave

Please try this

RMAN > run

{

the value of newname for datafile 1 to "+ DATA_SRVNAME";

restore data file 1;

switch datafile 1;

recover datafile 1;

}

Did you create + diskgroup DATA_SRVNAME?

and

Tags: Database

Similar Questions

  • Problem with different ASM disaster recovery start - new

    Hello together,

    I had an old net here about it but now will not solve the problem with the points in the old thread. Here's the old: https://community.oracle.com/thread/3608049?start=0 & tstart = 0

    I'm doing a disaster recovery with the 'apex11A' on a new server database, which has an another ASM starts. The old man starts is '+ DGA112_1' and '+ FRA112_1', newcomers are called '+ DATA_QUM169' and '+ FRA_QUM169 '. I changed the settings in the spfile restored by writing in a pfile file and creating the spfile from pfile.

    I tried in several ways. First lay the new ASM with RMAN to the course:

    run
    {
    SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Then I tried it in RMAN by defining the new ASM for each data file:

    run
    {
    SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Then I tried the bot in one:

    run
    {
    SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
    SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
    restore database until LOGSEQ 24286;
    switch datafile all;
    switch tempfile all;
    recover database until LOGSEQ 24286;
    }
    

    Whenever I get one

    Starting restore at 03-FEB-16
    using channel ORA_DISK_1
    
    
    creating datafile file number=1 name=+DATA_QUM169
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/03/2016 16:20:41
    ORA-01180: can not create datafile 1
    ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
    

    The backuppiece which I bring are correctly defined with

    RMAN> catalog backuppiece '/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1', '/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1';
    
    
    cataloged backup piece
    backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1 RECID=3779 STAMP=902851052
    cataloged backup piece
    backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1 RECID=3780 STAMP=902851052
    
    
    RMAN> list backup;
    
    
    
    
    List of Backup Sets
    ===================
    
    
    
    
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    3779    52.61M     DISK        00:00:00     03-FEB-16
            BP Key: 3779   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145340
            Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1
    
    
      List of Archived Logs in backup set 3779
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    24285   11073415926066 03-FEB-16 11073416327345 03-FEB-16
      1    24286   11073416327345 03-FEB-16 11073416678326 03-FEB-16
    
    
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    ------- ---- -- ---------- ----------- ------------ ---------------
    3780    Full    813.86M    DISK        00:00:00     03-FEB-16
            BP Key: 3780   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145042
            Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1
      List of Datafiles in backup set 3780
      File LV Type Ckp SCN    Ckp Time  Name
      ---- -- ---- ---------- --------- ----
      1       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/system.1423.788355253
      2       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/sysaux.1422.788355259
      3       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/undotbs1.1359.788355263
      4       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/users.1362.788355273
      5       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4.1369.788356305
      6       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4_files.1366.788356317
      7       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms_archiv.1358.788357229
      8       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/planwerte.1357.788357243
      9       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_prod.1352.788456613
      10      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais.1353.788456763
      11      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms.1354.788456995
      12      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/externe_wirk.1355.788457525
      13      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2mt.1356.788458151
      14      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_read.1351.788458291
      15      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329
      16      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657
      17      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/macmon.1340.788458691
      18      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais_read.1339.788458725
      19      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2srm.266.788458799
      20      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859
      21      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/quickcheck.1338.788458887
      22      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/switch.1337.788459139
      23      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/veit_r.1333.788459167
      24      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/test-btdb.1298.795097725
      25      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11dev.986.874230931
      26      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11devbt.985.874230963
      27      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hrbew.1083.851007823
      28      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/optimadata.1032.865951029
    

    I also tried to put the new ASM SQL:

    SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 3 16:04:05 2016
    
    
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.
    
    
    
    
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
    With the Partitioning, Automatic Storage Management and OLAP options
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 1 - new file '+DATA_QUM169' not found
    ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 2 - new file '+DATA_QUM169' not found
    ORA-01110: data file 2: '+DGA112_1/apex11a/datafile/sysaux.1422.788355259'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 3 - new file '+DATA_QUM169' not found
    ORA-01110: data file 3: '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 4 - new file '+DATA_QUM169' not found
    ORA-01110: data file 4: '+DGA112_1/apex11a/datafile/users.1362.788355273'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 5 - new file '+DATA_QUM169' not found
    ORA-01110: data file 5: '+DGA112_1/apex11a/datafile/apex4.1369.788356305'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 6 - new file '+DATA_QUM169' not found
    ORA-01110: data file 6: '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 7 - new file '+DATA_QUM169' not found
    ORA-01110: data file 7: '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 8 - new file '+DATA_QUM169' not found
    ORA-01110: data file 8: '+DGA112_1/apex11a/datafile/planwerte.1357.788357243'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 9 - new file '+DATA_QUM169' not found
    ORA-01110: data file 9: '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 10 - new file '+DATA_QUM169' not found
    ORA-01110: data file 10: '+DGA112_1/apex11a/datafile/mais.1353.788456763'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 11 - new file '+DATA_QUM169' not found
    ORA-01110: data file 11: '+DGA112_1/apex11a/datafile/mms.1354.788456995'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 12 - new file '+DATA_QUM169' not found
    ORA-01110: data file 12:
    '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 13 - new file '+DATA_QUM169' not found
    ORA-01110: data file 13: '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 14 - new file '+DATA_QUM169' not found
    ORA-01110: data file 14: '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 15 - new file '+DATA_QUM169' not found
    ORA-01110: data file 15: '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 16 - new file '+DATA_QUM169' not found
    ORA-01110: data file 16: '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 17 - new file '+DATA_QUM169' not found
    ORA-01110: data file 17: '+DGA112_1/apex11a/datafile/macmon.1340.788458691'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 18 - new file '+DATA_QUM169' not found
    ORA-01110: data file 18: '+DGA112_1/apex11a/datafile/mais_read.1339.788458725'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 19 - new file '+DATA_QUM169' not found
    ORA-01110: data file 19: '+DGA112_1/apex11a/datafile/mais2srm.266.788458799'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 20 - new file '+DATA_QUM169' not found
    ORA-01110: data file 20:
    '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 21 - new file '+DATA_QUM169' not found
    ORA-01110: data file 21: '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 22 - new file '+DATA_QUM169' not found
    ORA-01110: data file 22: '+DGA112_1/apex11a/datafile/switch.1337.788459139'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 23 - new file '+DATA_QUM169' not found
    ORA-01110: data file 23: '+DGA112_1/apex11a/datafile/veit_r.1333.788459167'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 24 - new file '+DATA_QUM169' not found
    ORA-01110: data file 24: '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 25 - new file '+DATA_QUM169' not found
    ORA-01110: data file 25: '+DGA112_1/apex11a/datafile/apex11dev.986.874230931'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 26 - new file '+DATA_QUM169' not found
    ORA-01110: data file 26: '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 27 - new file '+DATA_QUM169' not found
    ORA-01110: data file 27: '+DGA112_1/apex11a/datafile/hrbew.1083.851007823'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    
    
    
    
    SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169';
    ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169'
    *
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01141: error renaming data file 28 - new file '+DATA_QUM169' not found
    ORA-01110: data file 28: '+DGA112_1/apex11a/datafile/optimadata.1032.865951029'
    ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
    ORA-15045: ASM file name '+DATA_QUM169' is not in reference form
    

    But my new database will not set the new ASM and I have no why.

    The db_create_file_dest parameter is set correctly, so I think that:

    NAME                                 TYPE        VALUE
    ------------------------------------ ----------- ------------------------------
    db_create_file_dest                  string      +DATA_QUM169
    

    I forgot something? Would be nice to get help ...

    A big thank you and best regards,

    David

    Your data checkpoint SCN file are in the LOW and HIGH range of the SNA for SEQUENCE 24286.

    Therefore, your UNTIL clause should be 24287 SEQUENCE up to THAT.

    Hemant K Collette

  • Disaster recovery with replication for VSphere

    Am just test VSphere 5 of replication. with a couple of test VMs

    The replication process works very well

    What I want to know is the process to recover a VM replicated to new hardware in the case of the complete failure of the original host and/or data store

    In essence, disaster recovery.

    Are there other parts (software), that I need to take the replica VMDK and files related to re - create a new virtual machine on a new host

    Steve

    Yes, because it will be all your hard and .vmx files.

  • Disaster recovery with Ghettovcb on EXSI

    Hello team,

    I started working with EXSI and the backup and restore of virtual machine through ghettoVCB successfully completed.

    But I got over a spot...

    situation is something like:

    1. what got esxi crashed then how to quickly recover the new esxi?

    2 and if the new exsi is created then the new deployment of the backup of virtual machine on exsi?

    The team please provide guidelines about this situation...








    Thank you

    Hi sumitanand,

    It is technically possible to clone partitions starting ESXi? Maybe you can, but you should never do that.

    As Phatsta mentioned already install a new host is done in a very short period of time (depending on your hardware you can minutes)

    In addition, you can indeed do a boot from the disk backup (or just install on USB and do that 2 times on different USB sticks) however...

    What happens if your host is completely dead? You get a new server with different hardware... and specific drivers from different vendors? Your cloned image does not work, then, as the excellent.

    In addition, using a cloned image of ESXi is completely supported.

    If you want to save configuration ESXi host using something like this:

    PowerCLI: ESXi 5.0 / 5.1 ESXi backup host & restore the usefulness of GUI - VI - Toolkit

    and then apply to your freshly installed ESXi host.

    --

    Wil

  • Disaster recovery with VM

    I saw that many people use VM to use as backups of physical servers and thinking of doing the same thing.  However, once I've virtualized all of my servers does make sense to keep the original servers at all?  Should I just move in a completely VM server environment?

    The only reason to keep the physical servers would be to conduct a v2P if you had a problem with an application or piece of software, and that the seller required that demonstrate you that occur the same problem on a physical server as opposed to a virtual machine.

    If you have verified that all your software is virtualized supported and/or you agree to the policies of support of suppliers such as MS and understand the implications of my first point, there is very little interest to maintain the servers.

    The other thing to consider is a virtual machine can still be fired using the VMware software, Quest, Veaam, doubletake... etc - so if you still need DR a virtual machine is a server easier to deal with and to bring to a physical server.

  • ASM diskgroup with different disc size

    Hello

    DB: 10.2.0.4
    Operating system: AIX 5.3 64-bit L

    I have installation on 10g RAC ASM with node 2. It has the only Eve on ASM.

    Total DB size is 250 GB.
    Total size of FRA is 700 GB.

    My FRA diskgroup to archivelog (also holds multiplex controlfile) each size of 50 GB drive. Even if I set the retention period for 1 day, backup to disk, rman getting failed, due to space issues. So I manually delete obsolete data report and rerun backup.

    I want to add the workspace to FRA diskgroup regarding adding disks to FRA diskgroup. But, I have 100 GB drives available , it's not the same waist size of current existing FRA disc (50 GB).

    Here's my question

    (1) that I can Add the size different to the same diskgroup disc ?. If I add, are there performance problems?
    My all data files are out of FRA diskgroup and there are someother diskgroup.

    (2) if FRA diskgroup 50 GB and 100 GB of disks, and then how the archivelog and backup data will be erased?
    Will the data stored up to 50 GB in all disks in FRA, even * 100 GB * disc is?.

    (3) while doing recovery with different size of disk at diskgroup, what kind of problems can I face in performance wise?

    (4) can I remove any diskgroup 50 GB disks and add the 100 GB drive, so that I can increase the size of the disk in the same diskgroup?. I'll remove it and add at the same time.

    (5) add disks redundant external diskgroup , I'm ok with the following query?

    ALTER DISKGROUP FRA add DRIVE ' </dev/rhdsk1 >', </dev/rhdsk2 > ', </dev/rhdsk3 > ';


    Please help me on my doubts above.

    Thank you and best regards,
    Therese

    Hi Sunand,

    (1) can I add different diskgroup disc even size?. If I add, are there performance problems?
    My all data files are out of FRA diskgroup and there are someother diskgroup.

    A minimum of four (Oracle ASM disks) LUNS of equal size and performance is recommended for each disk group

    (2) if FRA diskgroup 50 GB and 100 GB of disks, and then how the archivelog and backup data will be erased?
    Data are saved up to 50 GB in all disks of FRA, same 100 GB drive is it?

    Oracle ASM data distribution policy is based on the ability. Ensure that the Oracle ASM disks in a disk group have the same ability to maintain balance.

    (3) while doing recovery with different size of disk at diskgroup, what kind of problems can I face in performance wise?

    Ensure that all Oracle ASM disks in a disk group have similar performance characteristics and the availability of storage. In configurations of storage with dimmers of mixed speed, for example, 10 K and 15 K rpm, i/o performance is limited by the slow speed control.

    (4) can I remove any diskgroup 50 GB disks and add the 100 GB drive, so that I can increase the size of the disk in the same diskgroup?. I'll remove it and add at the same time.

    Yes. First, you add the 100 GB drive and then remove the drives from 50 GB.

    (5) to add disks to external redundancy diskgroup, I'm ok with the following query?
    ALTER DISKGROUP FRA ADD DRIVE ",", ";

    Redundancy is controlled by the diskgroup. Then simply add the disks.

    e.g ALTER DISKGROUP FRA ADD DISK '/dev/rhdsk1', '/dev/rhdsk2', '/dev/rhdsk3';
    

    See doc below... Here are all your anwser.

    http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/storeman.htm#i1014729

    Kind regards
    Levi Pereira
    http://levipereira.WordPress.com

  • Can we create a Vlan without SRM for disaster recovery testing

    We are working on plans for our recovery after disaster in our VMWare environment.  We have a recovery Site which has a NETAPP file server we reproduce our VM data warehouse and SQL data.   We have no RS, but must be able to test if possible disaster recovery with Production upwards.   Is it possible to configure a VLAN and do a test isolated Dr. without SRM?   Thank you

    Welcome to the VMware communities forum.

    You can create a VLAN without SRM.  You will need to properly set up your network hardware, and then you add new virtual machine port groups to your ESXi hosts.  You can then save the virtual machines by giving them a different name and starts in isolation.  When you attempt to save the virtual machines they will always have a reference for the port VM production group so you'll want to make sure you update you turn on.

  • Everything was fine until my Windows 10, lost the start feature, if I ever go back to Windows 7, in this process, I lost my Adobe Reader software, I tried about ten times with different versions and different locations, all with the same download error

    Please forgive me for not knowing how to use this forum, I am an old man and not good at computers, I called Adobe, they said it was my only hope!

    Sorry to repeat

    Everything was fine until my Windows 10, lost the start feature, so I had to go back to Windows 7, in this process, I lost my Adobe Reader software, I tried about ten times with different versions and different locations, all with the same error message that is download "the feature you are trying to use is on an unavailable network resource"... are looking for It seems that it does not find when I search there, and I no longer seem to have the AcroRead.msi... the most difficult file, I try, I get deeper and deeper into things I don't know... I am looking for a simple solution!

    When it gets to this point, it is probably better to start from scratch.

    First of all, download, install and run Adobe Reader cleaning tool to get rid of all remains little. Here is a link to the tool: Download Adobe Reader and Acrobat tool - Adobe Labs

    Then go to the following link to download the full installer for the reader.

    https://get.Adobe.com/reader/Enterprise/

  • LINKS on the different types of recoveries and disaster recovery

    Hello

    Can someone please give me the links on different types of recovery scenarios. And what is meant by disaster recovery and how to survive in the event of any disaster recovery and types of disaster recovery.

    Please help me gurus.

    Thank you and best regards,
    Poorna Prasad.

    Useful link.

    http://www.morganslibrary.com/reference/rman_demos.html

    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/recoscen.htm#BRADV229

    I hope this helps.

    Concerning
    Asif Kabir

  • Physical-TO-virtual disaster recovery

    Hi, what would you do in this scenario?

    • A heterogeneous set of physical servers (with Linux or Win) owned and operated by several customers in different locations.

    • A vSphere on a centralized site infrastructure.

    I wish I had in my infrastructure, a VM power off to each of the remote servers in physics and to keep the image of VM in phase with the remote disks.

    In the case of a remote site explodes, the corresponding virtual machines are started (automatically or manually) as a quick and effective disaster recovery solution...

    Forget the problems of network/IP of this scenario, is there a way or a 3rd party software to keep a VM'd synch with a remote server physical?

    Thank you!

    PlateSpin Protect will be repeated. You place the platespin on the physical server agent and you can replicate the server to an image file or a virtual machine. You can update the image or VM file on a regular basis. It comes from platespin powerrecon product.

    Check it out.

    http://www.PlateSpin.com/products/protect/

    Don't forget to leave some points for messages useful/correct.

  • Difference between disaster recovery (replace the user's machine) and material migration Assistant.

    Hi all

    I worked at different scenarios for customers supported the migration of material.

    I found "Disaster recovery (replace the user's machine)" will perform the same action as the 'migration Hardware' option Assistant in common.

    Please let me know if the two are same with operations or any difference is there?

    Essentially, they do the same for the different use cases. The only difference is the default option selected for the computer name in the wizard. Migration of HW, it is 'Set Name'. In the Assistant of Dr., is "to keep the name of CVD.

  • Procedures and guidelines for Disaster Recovery (DR)

    Hi all

    Our TI auditor asked me to submit/provide procedures for guidelines for disaster recovery.

    I tried Google, but the process docs seem so vast and complex.

    We have a dataguard configuration. Can I give him to the contrary the docs on how to recover/restore using Data Guard?

    Can you share me link to good documentation on the recovery?

    Thank you

    Petra k.

    > We have a dataguard configuration

    Generally, the documentation is created with the Setup program. Documentation describing the configuration.  Documentation detailing the procedures for different situations.  Documentation that lists the commands to use and the expected responses for commands. Documentation that indicates the error handling methods if you try the commands.

    Your dataguard configuration is incomplete without these documents.

    Hemant K Collette

  • Problems of recovery with satellite A30 303

    I launched the recovery utility, and then I selected the recovery mode in advance that my hard drive is partiotioned, and I didn't want to format the second partition where different data files were stored.
    The first recovery disc has been loaded and files have bben transferred, then when you are prompted to load the secondary drive an error message as single user are not allowed... has been shown.

    Abandonment of the utility and after rebooting I got following messages:

    Error reading registration MFT VOLUME FILE_
    Internal error 25030
    An internal inconsistency was detected
    Ok

    Then two pages of lines BACK describing the situation.
    The PC unbootable.

    Hello

    This first time that perform you the installation of recovery with comes from Toshiba Recovery CD? If this isn't the case, it is the first time that this problem occurred?

  • Recovery disk will not start on Satellite 1110

    I try to use the recovery on a Satellite 1110 CD. I want to just install fresh Windows. The necessary files are supposed to be on the Toshiba recovery CD that accompanies it.

    So I did what the brochure says, and booted up the laptop to the top with the correct CD in the drive, while pressing 'C '. The notebook ignored the CD ROM and loaded Windows as usual. I repeated three times, each time that the CD ROM whirs a bit but will not start and Windows loads as usual. I have replaced 'C' for F12, chose the CD ROM drive in the list and repeat the process several times. Yet once it wouldn't boot from the CD-ROM.

    I looked at the content of the CD ROM A single MB 447. File of the GHS. The file icon is that generic type "Windows does not know what program this icon is intended to" deals.

    Google believes it is a ghost file and must the ghost installed to run it. This bitch never came with Ghost.

    Anyone here knows a remedy to this problem?

    (NB - I tried clean Windows system restore option, but it just brings back me to September this year. Theres no option that was more early in life for portable computers)

    I am in the United Kingdom, and is a UK machine if that makes a difference.

    Hello Micha

    Is this your ODD works properly with the operating system?

    I put really know what exactly is happening here, but please make sure that you start with recovery CD number 1/2 2/2. The installation of recovery, you can just start with the first recovery CD. Also try please set CD-ROM as firs boot device in the BIOS.

  • error 0xC0000225, recovery partition does not start

    Hello

    I have a HP dv7 with Windows 7 Home premium 64-bit.

    A few months ago, I did a factory restore, the recovery partition start (I have no recovery disks). After that, I thought to divide my C: partition where Windows is installed, and I did it with Windows disk management.

    So my new scores were: C: D: with recovery, OS, E: HP_Tools and g.: the new partition.

    A few days ago the sistem ran very hard, so I thought I do another factory restore from the recovery partition. When I rebooted and you press F11, I got the "0xc0000225 error".

    I have a Windows 7 Home Premium 64-bit bootable drive and I tried Startup Repair tool and other repairs of sistem, checks HDD, but everything seems to be ok.

    I reinstalled the operating system, from the disk bootable on C: (OS starts and works well) and let the other partitions as they were... but it seems that the recovery partition still does not start if I can do a restore from the factory with all the drivers and utilities, as they were at the beginning.

    Any ideas on how I can do?

    Thank you!

    It seemed that it there was not much I could do about this problem. My disk is dynamic, there is no Recovery Manager from the Start Menu, there has not been any creation of HP with HP folder recovery support. I managed somehow to make a repair disk, I tried it but no results, the error kept popping out every time.

    I inserted the Windows 7 disc to try to delete all partitions, including the recovery and HP-tools and do a Windows Installer Cleanup, but the Format, New and Delete buttons are inactive.

    I did some scans disk and memory tests, everything was ok... I started with a disc of Hiren and accesed the HARD drive with a program based on linux and so I managed to delete the partitions.

    After I installed a new copy of Windows 7 to work with my SN and everything was ok. Unfortunately I lost partitions recovery and HP-tools, but at least it works well again.

    Thanks for your all your support.

Maybe you are looking for