How to restore to a particula ASM diskgroup

I have backed up the database to the local non-ASM disk. I need to restore the backup to a particular ASM diskgroup using RMAN. Oracle is 10.2.0.3. What should I do?

Are you creating a new database, or is there something wrong with the old database and you need to restore ?
Basically the process is :-
1. create pfile or restore spfile and startup nomount
2. restore controlfile then alter database mount
3. restore database
4. recover database
5. open the database
I strongly recommend that you read the rman documentation at tahiti.oracle.com

Similar Messages

  • How to identify ASM DiskGroup attached to which Disks ???

    Hi Guys,
    In 11gR2 RAC, How to identify which ASM Diskgroup is attached to which Disks...( OS is RHEL 5.4).
    We could list ASM Diskgroups by,
    *#oracleasm listdisks* but this command doesn't show the disks assigned to ASM DiskGroup.
    Even for checking location of OCR and Voting Disks only show Diskgroup name and not the actual disks.
    $ocrcheck
    $crsctl query css votedisk
    ( like in 10gR2 RAC, We do entry in /etc/rules.d/udev/60-raw-rules file for raw mapping of OCR, Voting Disk and Other ASM Diskgroup)
    Plz help me, As one of the client place, I could see so many LUNs assigned to the Server and not getting exact idea which Disks have been used for OCR, Voting Disk and DATA Diskgroup.
    Thanks,
    Manish

    Well for this you can use oracleasm querydisk.Using this you can identify which device as marked for asm or not. for example you can see this below example.
    [oracle@localhost init.d]$ sqlplus "/as sysdba"
    SQL*Plus: Release 10.2.0.4.0 - Production on Thu Jun 3 11:52:12 2010
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select path from v$asm_disk;
    PATH
    /dev/oracleasm/disks/VOL2
    /dev/oracleasm/disks/VOL1
    SQL> exit;
    [oracle@localhost init.d]$ su
    Password:
    [root@localhost init.d]# /sbin/fdisk -l
    Disk /dev/sda: 80.0 GB, 80000000000 bytes
    255 heads, 63 sectors/track, 9726 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1   *           1        1305    10482381   83  Linux
    /dev/sda2            1306        9401    65031120   83  Linux
    /dev/sda3            9402        9662     2096482+  82  Linux swap / Solaris
    /dev/sda4            9663        9726      514080    5  Extended
    /dev/sda5            9663        9726      514048+  83  Linux
    Disk /dev/sdb: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdb1               1        4859    39029886   83  Linux
    /dev/sdb2            4860        9729    39118275   83  Linux
    [root@localhost init.d]# ./oracleasm querydisk /dev/sdb1
    Device "/dev/sdb1" is marked an ASM disk with the label "VOL1"
    [root@localhost init.d]# ./oracleasm querydisk /dev/sdb2
    Device "/dev/sdb2" is marked an ASM disk with the label "VOL2"
    [root@localhost init.d]# ./oracleasm querydisk /dev/sda1
    Device "/dev/sda1" is not marked as an ASM disk
    [root@localhost init.d]#Also in windows :
    C:\Documents and Settings\comp>asmtool -list
    NTFS                             \Device\Harddisk0\Partition1           140655M
    ORCLDISKDATA1                    \Device\Harddisk0\Partition2             4102M
    ORCLDISKDATA2                    \Device\Harddisk0\Partition3             4102M
    NTFS                             \Device\Harddisk0\Partition4           152617M
    C:\Documents and Settings\comp>answered by chinar.
    refer:-how to identify which rawdevice Disk Is named as VOL1 IN ASM from os level
    Happy New Year.
    regards,

  • Linux RedHat 4 update 4: how to unbind  raw devices used by ASM diskgroups?

    How to unbind raw devices used by ASM diskgroup?
    I created ASM diskgroup using /dev/raw/rawn, after done my testing, I need to toss the raw devices to start a new testing. Here is the procedure:
    1. shutdown MYTEST database
    2. in ASM instance, remove disks from diskgroup 'rawtest'
    3. in ASM instance, "drop diskgroup rawtest including contents"
    4. in OS, issue: "raw /dev/raw/raw1 0 0"
    I got the following error:
    # raw /dev/raw/raw1 0 0
    Error setting raw device (Device or resource busy)
    But if I shutdown ASM instance, the above commmand will be successful.
    My question, how can I unbind raw devices without shutting down ASM instance(could be used by other databases at the same time)?
    Thanks,
    Jenny

    The installation guild will probably be were you will want to start.
    2.11 Preparing Disk Groups for an Automatic Storage Management Installation
    http://download.oracle.com/docs/cd/B19306_01/install.102/b15660/pre_install.htm#sthref457
    Specifically
    2.12 Configuring Raw Partitions or Raw Logical Volumes
    http://download.oracle.com/docs/cd/B19306_01/install.102/b15660/pre_install.htm#sthref591

  • How to create a new ASM Diskgroup in Oracle 10g RAC?

    Hi,
    Our env is Oracle 10g R2 RAC on HP-UX. I want to create a new ASM Diskgroup. Please let me know if the following steps are ok to create a new ASM Diskgroup.
    1. Ensure the new Disk is visible in both ASM instances in RAC (v$asm_disk) and the header_status is 'CANDIDATE'
    2. From Node 1 ASM Instance issue the create diskgroup command.
    SQL> create diskgroup DATA2 external redundancy disk '/dev/rdsk/c4t0d5';
    3. Query v$asm_diskgroup and make sure the Diskgroup is created.
    4. Mount the DATA2 Diskgroup from Node 2 ASM Instance.
    5. Query v$asm_diskgroup and make sure the Diskgroup is visible from Node2 ASM instance.
    6. Ensure the header_status is 'MEMBER'.
    Rgds,

    correct.
    instead of using device file '/dev/rdsk/c4t0d5' you can create an alternate device file using mknod, which is called "asm_disk_xg" for example.
    check here: http://download.oracle.com/docs/cd/B19306_01/install.102/b14202/storage.htm#CDEECIHI
    hth

  • How to rename ASM diskgroups after having cloned the original disks to the same server. ASMlib is used

    Linux RHE 6
    Oracle Grid single instance (Oracle Restart) 11.2.0.4 installed
    Oracle RDBMS 11.2.0.4 installed
    One 11.2.0.4 database single instance running
    Our ASM have DATA, REDO, FRA diskgroup mounted
    We need to do a storage snapshot for creating on THE SAME server a copy of the current ASM diskgroups DATA, REDO, FRA. Then we would rename the cloned diskgroups using renamedg command.
    We have done this operation several times when ASMlib is not used. The command used when ASMlib is not used is for example:
    renamedg dgname=FRA newdgname=FRA2 verbose=true phase=both asm_diskstring='/dev/oracle/fra*'
    With ASMlib in use I am not sure about the steps to follow
    First I am not sure about what to provide to the asm_diskstring parameter of the renamedg command. I need to provide an asm_diskstring which identifies the path pointing to the disks belonging to the cloned diskgroup (I do not want to rename the original diskgroup). Though in an ASM instance using ASMlib the parameter asm_diskstring is is ‘ORCL:*’.
    Second, I suppose after the diskgroup rename ASMlib would return an error because it would find duplicated disks.
    Could you please advise ?
    Thanks in advance
    Massi

    Hi,
    As you have OS level clone ,you have same ASMlib label.
    ASMlib always mount unique ASMLib label only.
    +you need to identify those newly cloned device.
    + Then rename those ASMLib label using force-renamedisk after taking 1Mb disk backup using dd read on one node .
    + Then run scandisks on other nodes .
    + Then validate newly labelled device is mounted or not on all nodes .
    $ ls -ltr /dev/oracleasm/disks/*
    + Then run renamedg command with asm_diskstring of /dev/oracleasm/disks/*
    Regards,
    Aritra

  • Disaster Recovery with different ASM diskgroups

    Hi@all,
    actually I'm trying to test a Disaster Recovery Scenario. At a Oracle Linux 6 server with installed Grid Infra 12c and Ora Database 11.2.0.4 (there is also a 12.1.0.2 database instance) I'm trying to do a disaster recovery. But I'm getting wild by restoring and recovering the database. The problem here is, that the ASM diskgroup name has changed. As you read out I also switched the physical server, but I think that shouldn't be any problem.
    At the old server I've two ASM diskgroups "+DATA" and "+FRA_1", at the new they're called "+DATA_SRVNAME" and "+FRA_SRVNAME". I've already changed the startup parameter in spfile, but now after restoring the controlfile RMAN has the 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've tried three ways. First was to rename the datafile name:
    ALTER DATABASE RENAME FILE '+DATA/SID/datafile/system.438.816606399' TO '+DATA_SRVNAME/SID/datafile/system.438.816606399';
    Second was to set the newname in RMAN:
    set newname for datafile 16 to '+DATA_SRVNAME/SID/datafile/mms_basic_tab.455.816617697/';
    And 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 all three methods gave me the error, that the datafile at the new location isn't available (example):
    ORA-15012: ASM file '+DATA_QUM169/cogn11/datafile/system.438.816606399' does not exist
    So now my question to you: How am I able to tell the controlfile or database to use the other ASM diskgroup?
    I know, easiest way would be to create a diskgroup +DATA and do the restore / recover, but at the new server I've no more storage to assign to a new diskgroup and because of there are running other instances I would'nt change the ASM diskgroups.
    Did you have anny solution?
    Thanks a lot and Regards,
    Dave

    Please  try this
    RMAN> run 
    set newname for datafile 1 to '+DATA_SRVNAME'; 
    restore datafile 1;
      switch datafile 1;
      recover datafile 1;
    Did you created +DATA_SRVNAME  diskgroup?
    and

  • ASM diskgroups

    Dear all,
    We have a Database server using ASM diskgroup to store the data files and a separate ASM diskgroup as Flash recovery area.
    The database server is currently damaged and we would like to reuse the ASM disk group with a completely new server installation (i.e. to make a clone of the current database using the existing ASM diskgroups.)
    Is is possible to do so ?
    thanks in advance

    Yes, if you have a rman backup of you database then you can recreate a ASM and production database on new machine and then you can restore and recover it.
    I would like to see any document specifying "how to redirect/connect one asm disk from one asm instance to another instance." As specified above by someone, I would appreciate if wither he can show us some documentation or detail explanation.
    thanks
    ~Keyur

  • How to restore a control file without having its backup

    Hi,
    Can any one please suggest me how to restore a control file without having its backup.
    Thanks

    To add to what SB said, in years past the instructions for re-creating the control file manually were contained in the DBA Administration manual. It used to be and may still be common to be taking and saving a "backup control file to trace" for this purpose.
    If you lost only the primary copy of the control file and it is an OS file then while the database is shutdown you can copy the secondary over the primary and then use if to start the database. If the control file is stored in ASM then there should be a way to perform the copy via ASM.
    If you use rman for backups then a copy of the control file should be part of the backup process and you can retrieve it from the backup set then perform recovery using the backup control file though I do note the OP said something to the effect no backup exists. Still, I have knows of instances where the DBA did not realize that the backup set contained the control file and the spfile so I think this is worth mentioning just in case.
    HTH -- Mark D Powell --

  • Find out the devices of an ASM Diskgroup in Oracle Linux

    Hi
    I want to drop an ASM Diskgroup and I want to find out what are the devices attached to that Disk group that I am going to drop.
    I am in RAC 10.2.0.4 on Oracle Linux
    When I query with this:
    SELECT name, header_status, path FROM V$ASM_DISK;
    The column path says:
    ORCL:FRA1
    ORCL:FRA2
    but really what I want to know what is the real device in the OS that represent that ASM Disk.
    How can i find out the name of my real devices ?
    Thanks

    I thought you were supposed to run this query when connected to the ASM instance, not the regular instance. But I tried it here and it works fine with my regular instances:
    SQL> SELECT name, header_status, path FROM V$ASM_DISK;
    NAME                           HEADER_STATUS PATH
    ASMDG01_0005                   MEMBER        /dev/raw/raw6
    ASMDG01_0004                   MEMBER        /dev/raw/raw5
    ASMDG01_0002                   MEMBER        /dev/raw/raw3
    ASMDG01_0003                   MEMBER        /dev/raw/raw4
    ASMDG01_0000                   MEMBER        /dev/raw/raw1
    ASMDG01_0001                   MEMBER        /dev/raw/raw2
                                   FORMER        /dev/raw/raw7
                                   FORMER        /dev/raw/raw8
                                   FORMER        /dev/raw/raw9Edited by: marcusrangel on Jun 26, 2012 6:05 PM

  • Unable to Create ASM Diskgroup ORA-15020 and ORA-15018

    Hello Team,
    Unable to create ASM diskgroup with following error:
    SQL> create diskgroup data_asm1 external redundancy disk '/dev/sdf*';
    create diskgroup data_asm1 external redundancy disk '/dev/sdf*'
    ERROR at line 1:
    ORA-15018: diskgroup cannot be created
    ORA-15020: discovered duplicate ASM disk "DATA_ASM1_0000"
    ASM Diskstring
    SQL> show parameter asm_diskstring
    NAME                                 TYPE        VALUE
    asm_diskstring                       string      /dev/oracleasm/disks/DISK*, /dev/sd*
    Please let me know how to i solve this issue
    Regards,

    Hi Tobi,
    I checked the status of the res GRID.dg ... it was offline on second node. Logged on second node and checked the status of it viz:v$asm_diskgroup, it was dismount. I mounted it and then try to add the newly added diskgroup(+GRID) with OCR and viola it worked....
    ========================================================
    ora.GRID.dg
                   ONLINE  ONLINE       rac3                                       
                   OFFLINE OFFLINE      rac4                                       
    SQL> select group_number,name,state,type from v$asm_diskgroup;
    GROUP_NUMBER NAME                           STATE       TYPE
               1 DATA                           MOUNTED     EXTERN
               0 GRID                           DISMOUNTED
    SQL> alter diskgroup grid mount;
    Diskgroup altered.
    SQL>  select group_number,name,state,type from v$asm_diskgroup;
    GROUP_NUMBER NAME                           STATE       TYPE
               1 DATA                           MOUNTED     EXTERN
               2 GRID                           MOUNTED     EXTERN
    ==============================================
    ora.GRID.dg
                   ONLINE  ONLINE       rac3                                       
                   ONLINE  ONLINE       rac4                                       
    ===============================================
    [root@rac3 bin]# ./ocrcheck
    Status of Oracle Cluster Registry is as follows :
             Version                  :          3
             Total space (kbytes)     :     262120
             Used space (kbytes)      :       2804
             Available space (kbytes) :     259316
             ID                       :   48011651
             Device/File Name         :      +DATA
                                        Device/File integrity check succeeded
             Device/File Name         :      +grid
                                        Device/File integrity check succeeded
                                        Device/File not configured
                                        Device/File not configured
                                        Device/File not configured
             Cluster registry integrity check succeeded
             Logical corruption check succeeded
    ==========================================================================================
    ASMCMD> lsdg
    State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
    MOUNTED  EXTERN  N         512   4096  1048576     20472    16263                0           16263              0             N  DATA/
    MOUNTED  EXTERN  N         512   4096  1048576      5114     4751                0            4751              0             N  GRID/
    ======================================================================================================
    Thank you very much, appreciated..
    Thank you Aritra .
    Guys you rock.
    Regards,

  • Recommended Number LUNs for ASM Diskgroup

    We are installation Oracle Clusterware 11g, Oracle ASM 11g and Oracle Database 11g R1 (11.1.0.6) Enterprise Edition with RAC option. We have EMC Clariion CX-3 SAN for shared storage (All oracle software will reside on locally). We are trying to determine the recommended or best practice number of LUNs and LUN size for ASM Diskgroups. I have found only the following specific to ASM 11g:
    ASM Deployment Best Practice
    Use diskgroups with four or more disks, and making sure these disks span several backend disk adapters.
    1) Recommended number of LUNs?
    2) Recommended size of LUNs?
    3) In the ASM Deployment Best Practice above, "four or more disks" for a diskgroup, is this referring to LUNs (4 LUNs) or one LUN with 4 physical spindles?
    4) Should the number of physical spindles in LUN be even numbered? Does it matter?

    user10437903 wrote:
    Use diskgroups with four or more disks, and making sure these disks span several backend disk adapters.This means that the LUNs (disks) should be created over multiple SCSI adapters in the storage box. EMCs have multiple SCSI channels to which disks are attached. Best practice says that the disks/luns that you assing to a diskgroup should be spread over as many channels in the storage box as possible. This increases the bandwidth and therefore, performance.
    1) Recommended number of LUNs?Like the best practice says, if possible, at least 4
    2) Recommended size of LUNs?That depends on your situation. If you are planning a database of 100GB, then a LUN size of 50GB is a bit overkill.
    3) In the ASM Deployment Best Practice above, "four or more disks" for a diskgroup, is this referring to LUNs (4 LUNs) or one LUN with 4 physical spindles?LUNs, spindles if you have only access to physical spindles
    4) Should the number of physical spindles in LUN be even numbered? Does it matter?If you are using RAID5, I'd advise to keep a 4+1 spindle allocation, but it might not be possible to realize that. It all depends on the storage solution and how far you can go in configuring it.
    Arnoud Roth

  • RMAN 恢复至ASM DISKGROUP 报错 ORA 19870 19504 15045 17502 15081

    问题简单描述：
    AIX 6, ORACLE 11.2
    1.替换原来存储，也就是说用新存储B 把原来的A 存储替换掉， 数据库原来是跑到A 存储上的。
    2.我把数据库shutdown 然后 startup mount 后做一致备份到本地磁盘/oracle/rman_bak1201/
    3.删除原来的ASM DISKGROUP ，然后删除磁盘（踢掉旧存储）
    4.新存储映射磁盘到主机，然后重新建立ASM DISKGROUP DATA 成功 （原来的DISKGROUP 名字也是 DATA, 所以新diskgroup_name 与旧 diskgroup_name 相同 。曾尝试建立数据库test 成功，查看diskgroup 状态为mounted 也正常）
    存储替换完毕
    5.把先前的备份尝试恢复到新建的 ASM DISKGROUP DATA
    6.用startup nomount pfile='/oracle/rman_bak1201/abc.ora' 启动，尝试恢复时报错 （pfile 是我从原库 create pfile='xxxx' from spfile 备份的）
    RMAN> restore controlfile from '/oracle/rman_bak1201/c_0jnrov15_1_1';
    Starting restore at 01-DEC-12
    using channel ORA_DISK_1     
    channel ORA_DISK_1: restoring control file
    RMAN-00571: ========================================================
    RMAN-00569: ==========ERROR MESSAGE STACK FOLLOWS===================
    RMAN-00571: ========================================================
    RMAN-03002: failure of restore command at 12/01/2012 17:50:54
    ORA-19870: error while restoring backup piece /oracle/rman_bak1201/c_0jnrov15_1_1
    ORA-19504: failed to create file "+DATA"
    ORA-15045: ASM file name '+DATA' is not in reference form
    ORA-17502: ksfdcre:5 Failed to create file +DATA
    ORA-15081: failed to submit an I/O operation to a disk
    网上搜了下说是rhdisk权限问题, 但我新的diskgroup 用DBCA 建库都正常，所以不解，请支招谢谢。

    问题解决，诊断思路是tail -f alert*.log，然后从新尝试restore controlfile 发现有关于/dev/rhdisk* permission deny ，故问题就是rhdisk* 权限的问题，修改权限后重启+ASM 实例后顺利恢复。
    后来我把rhdisk* 权限改成了 666 oracle dba 重启就好了（在此说明当初实施的人规划的grid和oracle用户同时属于oinstall 和dba组，两个用户其实是相同的权限，看样子比较混乱，我也没心思从头整理了简单666 解决）
    但现在还有个疑问就是：
    1. 为什么我设置跟人家原来的授权 crw-rw---- grid dba rhidk2 却不能恢复？ 但是通过dbca 用oracle 用户建立新库一点问题都没有。

  • DBFS ASM diskgroup

    Re: our new X3 machines (in the data centers, yet to be installed).
    I know that some of this was sort of covered in the earlier thread about DBFS. However, I do have slightly different questions...
    I understand that the DBFS ASM diskgroup is mandatory and, because of the nature of how its size is calculated, the ACS consultants configure it at its minimum size. However, is it possible to (preferably at configuration time) increase the ASM diskgroup? Or is it meant to have a set size, no matter what?
    Oracle have told me that I could put Flashback Logs into the DBFS ASM diskgroup (as long as I don’t configure DBFS to use it, obviously). I’m sure I read that Flashback Logs HAVE to be put into the db_recovery_file_dest (Fast Recovery Area or RECO diskgroup). Has anyone used DBFS (the ASM diskgroup) for such storage? I know it's not IDEAL given the fact it won't be spread across all storage cells, but I'm trying to figure out a way of separating the Flashback Logs from the Archive Logs because we monitor the Archive Log location for space usage (we get an alert if it gets too full and automatically kick off an archivelog backup/purge at a certain level of usage).
    Mark

    The first two Spinning Drives on each cell contain a 29 GB sized partition with the OS. The other 10 contain instead a 29 GB sized GridDisk from which the DBFS_DG diskgroup is built. In other words: The DBFS_DG diskgroup is also spread across all the cells but only on 10 drives (not 12 as DATA and RECO) on each cell.
    This way, the GridDisks that make up DATA and RECO can have the same size on all spinning drives. And the DBFS_DG diskgroup will consume about 300GB on each cell for that reason, which can't be changed reasonably, I suppose.
    You could set DB_RECOVERY_FILE_DEST='+DBFS_DG'  and turn on Flashback Database, so that Flashback Logs are being generated there, while you set LOG_ARCHIVE_DEST_1 to the RECO diskgroup, so that Archivelogs get stored there. And with RMAN backups, you specify FORMAT '+RECO' to get the backups not into the Recovery Area (DBFS_DG in that example).
    Kind regards
    Uwe Hesse

  • Restoring RMAN Backup from ASM RAC env to Non ASM standalone environment

    Hi,
    Can anyone please tell me how to restore database using RMAN in a Non ASM environment as my backup file with ASM RAC environment.
    i was also looking for some documentation which provides clear explanation about RMAN backup and Restore in ASM and Non ASM environment.
    Thanks

    You can set the parameter db_file_name_convert in init.ora in you new database with [ID 47325.1]
    or
    you can set parameter "set newname" in your script rman. [ID 549972.1]
    if you have one or two destinations of dbfiles in ASM I seggest to you set parameter db_file_name_convert in init.
    example:
    db_file_name_convert=('+DGDATA','/u01/oradata/');
    remenber you need set log_file_name_convert to.
    log_file_name_convert=('+DGREDO','/u01/redo/');
    if you use "set newname" commands you need set this lines in your script rman.
    set newname for datafile 1 to '/u01/oradata/system01.dbf';
    set newname for datafile 2 to '/u01/oradata/undotbs01.dbf';
    set newname for datafile 3 to '/u01/oradata/sysaux01.dbf';
    set newname for datafile 4 to '/u01/oradata/users01.dbf';
    and every datafiles you need set!
    Edited by: user1107977 on 21/07/2011 13:47

  • How to restore old prefs, etc after clean reinstall of 10.3.9?

    Due to a fiasco with Drive Genius I was forced to reformat and reinstall 10.3.9. Luckly, I was bright enough to manually copy over the entire contents of the drive to a firewire drive before I started the drive genius project.
    I was able to find directions on how to restore my users which worked perfectly.
    I've copied all the apps back. But all the apps were in the main drive rather than in users, so the prefs, registrations etc are, I assume, stored in the old library.
    Is there a way to replace the new library with the original to avoid several days work digging out the original packaging to get the serial numbers for re-entering so I can get back to work right away?

    The serial #s, etc were in fact in the original main library. I was able to restore the use of all the programs by manually replacing the missing items in each folder in the library. It took over an hour, but I got it all back and saved me from having to rummage through storage boxes for the original documentation to retrieve and re-enter all the info.

Maybe you are looking for

  • ITunes won't recognize any of my devices after latest update.

    This is pretty rediculous, none of my devices (iPad and iPod) will show up when connected to iTunes since the last update. They show up fine on my computer, why must I try to figure this out because Apple can't test their stuff before releasing it. I

  • Upload image into mysql database residing on  remote server is not working?

    hello to all, i need ur help,we hav online site . i have to upload image(which can b from any pc) into mysql database residing on remote server of which we (don't hav actual path of that server). the solution i'm using is working correctly on local b

  • [SOLVED] Unresponsive Internet Every Minute

    I recently installed Arch Linux on a new computer from the ISO image provided on the website and upgraded all of the packages to their recent versions. I am having a problem with my internet. The internet is sluggish and every 30 to 60 seconds just s

  • Getting project to recognize media on different disk

    on a project i've been working on, i have been storing all my media on a firewire drive and backing it up on a sata drive. i have also backed up the fcp document from my main drive to this sata drive. i now want to use the sata drive that i have been

  • Fuzzy photos in screensaver mode

    After installing iPhoto 6, some of the already existing photos in my library show up fuzzy when they come up on my screensaver?