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

Similar Messages

Question: 10gR2 database can not see the 11gR2 ASM diskgroup?

Hi there,
env:
uname -rm
2.6.18-92.1.22.el5xen x86_64
Single server(non-RAC)
note: we don't want to upgrade 10gr2 database into 11gR2 yet. But we created the 11gR2 ASM, then a 11gr2 database on ASM, and plan to migrate datafile in 10gR2 database to 11gR2 ASM
1. oracle 10gR2 installed first version: 10.2.0.3.0
2. then install 11gR2 Grid Infrastructure, and created ASM (version 11gr2)
$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Tue Oct 19 10:30:56 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Automatic Storage Management option
SQL> col name form a15
SQL> col COMPATIBILITY form a15
SQL> col DATABASE_COMPATIBILITY form a15
SQL> l
1* select name , STATE, COMPATIBILITY, DATABASE_COMPATIBILITY from v$asm_diskgroup
SQL> /
NAME STATE COMPATIBILITY DATABASE_COMPAT
ORCL_DATA1 MOUNTED 11.2.0.0.0 10.1.0.0.0
ORA_DATA MOUNTED 10.1.0.0.0 10.1.0.0.0
3. in 10gR2 database
sqlplus /
SQL*Plus: Release 10.2.0.3.0 - Production on Tue Oct 19 12:12:31 2010
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning and Data Mining options
SQL> select * from v$asm_diskgroup;
no rows selected
4. pin the node into css
# /u01/app/product/11.2.0/grid/bin/crsctl pin css -n mynodename
CRS-4000: Command Pin failed, or completed with errors.
Question: 10gR2 database can not see the 11gR2 ASM diskgroup?
please help
Thanks
Scott

What is the output of
olsnodes -t -n
Also, see unix error log and ohasd error log if you find anything in that

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

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

"Best" Allocation Unit Size (AU_SIZE) for ASM diskgroups when using NetApp

We're building a new non-RAC 11.2.0.3 system on x86-64 RHEL 5.7 with ASM diskgroups stored on a NetApp device (don't know the model # since we are not storage admins but can get it if that would be helpful). The system is not a data warehouse--more of a hybrid than pure OLTP or OLAP.
In Oracle® Database Storage Administrator's Guide 11g Release 2 (11.2) E10500-02, Oracle recommends using allocation unit (AU) size of 4MB (vs. a default of 1MB) for a disk group be set to 4 MB to enhance performance. However, to take advantage of the au_size benefits, it also says the operating system (OS) I/O size should be set "to the largest possible size."
http://docs.oracle.com/cd/E16338_01/server.112/e10500/asmdiskgrps.htm
Since we're using NetApp as the underlying storage, what should we ask our storage and sysadmins (we don't manage the physical storage or the OS) to do:
* What do they need to confirm and/or set regarding I/O on the Linux side
* What do they need to confirm and/or set regarding I/O on the NetApp side?
On some other 11.2.0.2 systems that use ASM diskgroups, I checked v$asm_diskgroup and see we're currently using a 1MB Allocation Unit Size. The diskgroups are on an HP EVA SAN. I don't recall, when creating the diskgroups via asmca, if we were even given an option to change the AU size. We're inclined to go with Oracle's recommendation of 4MB. But we're concerned there may be a mismatch on the OS side (either Redhat or the NetApp device's OS). Would rather "first do no harm" and stick with the default of 1MB before going with 4MB and not knowing the consequences. Also, when we create diskgroups we set Redundancy to External--because we'd like the NetApp device to handle this. Don't know if that matters regarding AU Size.
Hope this makes sense. Please let me know if there is any other info I can provide.

Thanks Dan. I suspected as much due to the absence of info out there on this particular topic. I hear you on the comparsion with deviating from a tried-and-true standard 8K Oracle block size. Probably not worth the hassle. I don't know of any particular justification with this system to bump up the AU size--especially if this is an esoteric and little-used technique. The only justification is official Oracle documentation suggesting the value change. Since it seems you can't change an ASM Diskgroup's AU size once you create it, and since we won't have time to benchmark using different AU sizes, I would prefer to err on the side of caution--e.g. first do no harm.
Does anyone out there use something larger than a 1MB AU size? If so, why? And did you benchmark between the standard size and the size you chose? What performance results did you observe?

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 diskgroup really full?

Hi gurus,
after install RAC (11.2.0.3 two nodes) on linux, a warning appears shown a diskgroup almost full:
SQL> select group_number, name, block_size, state, total_mb, free_mb, hot_used_mb from V$ASM_DISKGROUP WHERE NAME='VOL';
GROUP_NUMBER NAME                           BLOCK_SIZE STATE         TOTAL_MB      FREE_MB HOT_USED_MB
           4 VOL                          4096 MOUNTED          23838       284           0correctly, It's looks like almost full.
It is a new RAC database, if i check any file at asmcmd:
asmcmd> cd VOL
asmcmd> ls
asmcmd>no files appear, so i go to asmca and check:
ASM CLUSTER FILE SYSTEM
ACTIVE MOUNT POINT | STATE | ALL_MOUNT_POINTS | VOLUME DEVICE    | SIZE (GB) | VOLUME | DISK_GROUP | USED (%)
/backup                 MOUNTED   /backup           /dev/asm/vol-24   22.91      VOL VOL       4.19it's only 4.19% in use
what is happening? at filesystem is no files and have enough space, but asm shows that it is almost full

ASM and ACFS are related (an ACFS volume is part of an ASM diskgroup), but not the same
you have ASM diskgroup with 23 GB storage
you created an ACFS volume on it with ~23 GB size
from ASM point of view, the diskgroup is almost full, because of the ACFS volume
from ACFS point of view, its empty, because you didnt put anything yet on that volume
its similar as LVM
you create a volume group (ASM diskgroup in this analogy) with 23 GB size
then you create a volume (ACFS volume in this analogy) with nearly 23 GB size
volume group is almost "full", while volume is empty

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,

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

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,

Resize ASM Diskgroup

Hi All,
My exadata quarter rack machine has two asm diskgroups, DATA1 with 5TB and RECO with 3TB.
I'd like to resize RECO to 1TB and DATA1 to 7TB.
I know ALTER DISKGROUP RESIZE command, but my question is about resize RECO volume from 3 to 1 TB: is it supported by Oracle?? Let me know risks /issues with this resize?
Regards.
Giovanni

Ok, thanks.
My idea was:
step 1> resize from ASM by ALTER DISKGROUP RECO RESIZE ALL SIZE xxG REBALANCE POWER 11;
step 2> resize GRIDDISKs of RECO* on each cell for each griddisk by CellCLI> ALTER GRIDDISK griddisk_name size=xxG;
step 3> check griddisk detail for RECO
step 4> check size of a DATA griddisk
step 5> check free space on CELLDISKs
step 6> resize GRIDDISKs of DATA* on each cell for each griddisk by CellCLI> ALTER GRIDDISK griddisk_name size=new_sizeG;
step 7> resize from ASM by ALTER DISKGROUP DATA RESIZE ALL REBALANCE POWER 11;
step 8> check status of all asmdisks using "v$asm_disk"
step 9> check DB alert logs
step 10> check cell alert history on each cell
Now, I'm reading your suggested note #1245494, thanks very much

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

Expand ASM Diskgroup on RAC 11.2 online

Hi,
I am currently in search of an article or document which describes the following workflow:
Expand ASM Diskgroup on RAC 11.2 online:
Resize physical LUN (no Infos needed)
Resize Multipath
Resize Partition
Resize ASM Disk
Resize ASM DiskGroup ( I dont know if this is necessary?)
It is an Oracle Enterprise Linux 5.5 with 11.2 Clusterware. We use ISCSI Disk, ASMLib and Multipath (Linux -> multipathd).
The main goal is to do that online.
Does anyone know of such an article, or else has other tips regarding this scenario?
Kind Regards,
Richi

Below links may help.
http://www.hds.com/assets/pdf/hitachi-dynamic-provisioning-software-best-practices-guide-oracle.pdf
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101586
http://www.oracle.com/technetwork/database/oracle-automatic-storage-management-132797.pdf
Ta
Jag

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 用户建立新库一点问题都没有。

Is there a way to rename an ASM DiskGroup from the Disks in 11g ?

Hello,
I've been looking for that and I didn't find anything except that it may not have been possible with 10g.
I'd like to rename a diskgroup to reuse it in the same ASM instance from a netapp snapclone. Of course I would prefer to do it without any ASM instance accessing it but afterall, if there is a way... (even not supported; it's to enable a set of testing database all together) !
Thank you for your help.
Gregory

Hi Gregory,
since all information about ASM Disk, Diskgroup, etc. are stored directly on the disks there is no way to rename the diskgroup at the moment (hopefully in the future, like a way to change diskgroup redundance).
Only option you have is to create a new diskgroup and copy the datafiles over with either RMAN or DBMS_FILE_TRANSFER. Then rename the file to point to new location. (alter datafile).
But since you want to duplicate it into a different ASM Diskgroup, that will not help you. The option left is to change the Disk Header information directly. Unfortunately I do not have any information about the disk header itself...
Hopefully someone can give you a hint what all to change there if you would DD this to a file change it and store it back...
Regards
Sebastian

ASM diskgroups

Similar Messages

Maybe you are looking for