ASMDiskgroup ultimate data recovery solutions PRM-DUL tools

OracleASMDiskgroup data Recovery ultimate solution PRM-DUL tool download the latest PRM: paiprm User Manual: www. parnassusdata. comsitesdefafilefilesparnassusdata % 20 Recovery % 20 Manag

Oracle ASM Diskgroup data recovery ultimate solution PRM-DUL tool Download latest PRM: http://parnassusdata.com/sites/default/files/ParnassusData_PRMForOracle_3206.zip PRM User Manual: http://www.parnassusdata.com/sites/default/files/ParnassusData%20Recovery%20Manag

Oracle ASM Diskgroup ultimate data recovery solutions PRM-DUL tools

Download the latest PRM version:

Http://parnassusdata.com/sites/default/files/ParnassusData_PRMForOracle_3206.zip

PRM User Manual:

Http://www.parnassusdata.com/sites/default/files/ParnassusData%20Recovery%20Manager%20For%20Oracle%20Database%E7%94%A8%E6%88%B7%E6%89%8B%E5%86%8C%20v0.3.pdf

ORACLE's ASM automatic storage management technology is being adopted by more and more enterprises. Compared with traditional file systems, the use of ASM in databases has advantages such as high performance, cluster support, and convenient management. However, the problem with ASM is that for general users, the storage structure of ASM is too black. Once the internal data structure of a Disk Group in ASM is damaged, the Disk Group cannot be successfully mounted, this means that important user data is locked in the ASM black box. In this scenario, ORACLE engineers familiar with the internal data structure of ASM often need to manually repair the internal structure of ASM after arriving at the user's site; purchasing the ORACLE factory's on-site services is expensive and time-consuming for common users.

PRM-based R & D personnel (former ORACLE Senior Engineer) have an in-depth understanding of the internal data structure of oracle asm, and PRM has added data recovery functions especially for ASM.

Currently, PRM supports the following ASM data recovery functions:

1. Even if the Disk Group cannot be properly mounted, you can use PRM to directly read the available metadata on the ASM Disk and copy the ASM file in the Disk Group based on the metadata.

2. Even if the Disk Group cannot be properly mounted, you can use PRM to directly read the data files on the ASM and extract the data, supporting the traditional extraction and data bypass methods.

Support for ASM by PRM

Function	Supported
Data can be extracted directly from ASM without being copied to the file system.	YES
Supports copying data files from ASM	YES
Support for repairing ASM metadata	YES
Supports graphical display of ASM Black Box	Future

There are no restrictions on the ASM clone function in the Community edition. More free features will be added to the Community edition in the future.

Scenario 6: copy the database data file from the corrupted ASM Diskgroup

Company D began to adopt the ASM solution to replace the file system and bare devices. However, due to the large number of bugs on ASM in version 11.2.0.1, the asm diskgroup disk cannot be loaded with MOUNT, failure in repairing the ASM Disk Header through multiple parties.

In this scenario, you can use the ASM Files Clone function of PRM to copy database data Files from the damaged ASM Diskgroup.

1. Open the main interface, and select ASM File (s) Clone in the Tools menu bar:

1. Go to the ASM Disks page and click SELECT... Button to add still available ASM Disks such as/dev/asm-disk5 (linux); make sure to join all available Luns and click the ASM analyze button

2. ASM Files Clone analyzes the Disk headers of the specified ASM Disk to find out the Files in the Disk group and their distribution locations (File Extent Map ); this information will be recorded in the Derby database for future use. It can be said that PRM collects, analyzes, and stores all Metadata of ASM, the basic functions of PRM are improved in various forms and presented to users in a graphical manner.

3. After the ASM Analyze analysis is complete, the PRM will list the files found on the ASM. You can select the files to be cloned and specify the target folder to be cloned.

Then click the ASM Clone button to enter the file cloning stage.

In the File cloning phase, the cloning progress of the ASM File is listed. After cloning, click OK.

The progress log output in the clone phase is as follows:

Preparing selected files... Cloning + DATA2/ASMDB1/DATAFILE/tbs2.256.81_32369: .......................... 1024 MB ...................................... 2048 MB ...................................... 3072 MB ........................................ 4096 MB ...................................... 5120 MB ........................................ 6144 MB ..................................... 7168 MB ....................................... 8192 MB ....................................... 9216 MB ....................................... 10240 MB ....................................... 11264 MB ......................................... 12288 MB ........................................... 13312 MB .................................. 14336 MB ............................................ 15360 MB ..................................... 16384 MB ....................................... 17408 MB ....................................... 18432 MB .......................................................................................................... 19456 MB .......................................... Cloned size for this file (in byte): 21475885056 Cloned successfully! Cloning + DATA2/ASMDB1/ARCHIVELOG/2014_02_17/thread_eclipseq_47.257.81_32751: ...... Cloned size for this file (in byte): 29360128 Cloned successfully! Cloning + DATA2/ASMDB1/ARCHIVELOG/2014_02_17/thread_eclipseq_48.258.81_32751: ...... Cloned size for this file (in byte): 1048576 Cloned successfully! All selected files were cloned done.

4. You can use the dbv or rman validate command to verify the cloned data file. For example:

Rman target/ RMAN> catalog datafilecopy '/home/oracle/asm_clone/tbs2.256.8397322.16.dbf '; Cataloged datafile copy Datafile copy file name =/home/oracle/asm_clone/tbs2.256.820.322.16.dbf RECID = 2 STAMP = 839750901 RMAN> validate datafilecopy '/home/oracle/asm_clone/tbs2.256.8368322.16.dbf '; Starting validate at 17-FEB-14 Using channel ORA_DISK_1 Channel ORA_DISK_1: starting validation of datafile Channel ORA_DISK_1: including datafile copy of data file 00016 in backup set Input file name =/home/oracle/asm_clone/tbs2.256.81_322.16.dbf Channel ORA_DISK_1: validation complete, elapsed time: 00:03:35 List of Datafile Copies ====================================== File Status Marked upt Empty Blocks Examined High SCN ---------------------- 16 ?? OK ???? 0 ????????????? 2621313 ????? 2621440 ???????? 1945051 File Name:/home/oracle/asm_clone/tbs2.256.8397322.16.dbf Block Type Blocks Failing Blocks Processed --------------- Data ?????? 0 ????????????? 0 Index ????? 0 ????????????? 0 Other ????? 0 ????????????? 127 Finished validate at 17-FEB-14

How can we use PRM in the asmlib asm environment?

In fact, asmlib-related ASM disks are stored in the OS in ll/dev/oracleasm/disks format. For example: directly add the files under/dev/oracleasm/disks to the prm asm disk.

$ Ll/dev/oracleasm/diskstotal 0 Brw-rw --? 1 oracle dba 8 ,? 97 Apr 28 :20 VOL001 Brw-rw --? 1 oracle dba 8 ,? 81 Apr 28 :20 VOL002 Brw-rw --? 1 oracle dba 8 ,? 65 Apr 28 :20 VOL003 Brw-rw --? 1 oracle dba 8 ,? 49 Apr 28 :20 VOL004 Brw-rw --? 1 oracle dba 8 ,? 33 Apr 28 :20 VOL005 Brw-rw --? 1 oracle dba 8 ,? 17 Apr 28 :20 VOL006 Brw-rw --? 1 oracle dba 8,129 Apr 28 VOL007 Brw-rw --? 1 oracle dba 8,113 Apr 28 VOL008

Directly add the files under/dev/oracleasm/disks to the prm asm disk.

No related posts.

Source Address: ASM Diskgroup data recovery ultimate solution PRM-DUL tool, thanks to the original author to share.