ASM instance wont mount diskgroup..

HI, I have 10g release 2 installed on CENTOS 4.4, I use ASM striping with with 4 raw disks.
I had a system crash due to a power failure and now the the ASM wont mount the diskgroup.
export $ORACLE_HOME=+ASM
SQL> startup mount;
ASM instance started
Total System Global Area 130023424 bytes
Fixed Size 2071000 bytes
Variable Size 102786600 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> alter diskgroup RESEARCH1 mount;
alter diskgroup RESEARCH1 mount
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"RESEARCH1"
now when I use /etc/init.d/oracleasm listdisks I can see all my disks:
DISK1
DISK2
DISK3
DISK4
then i tried to change asm_diskstring to point the mounting point, here is my ora file:
*.asm_diskgroups='RESEARCH1'
+ASM.asm_diskgroups='RESEARCH1' #Manual Dismount
*.asm_diskstring='/dev/oracleasm/disks'
*.background_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/bdump'
*.core_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/cdump'
*.instance_type='asm'
*.large_pool_size=12M
*.remote_login_passwordfile='EXCLUSIVE'
*.user_dump_dest='/home/oracle/product/10.2.0/db_1/admin/+ASM/udump'
any ideas?
Thanks
Assaf

Hi,
by oracleasm lib utility you can configure as below
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Thanks

Similar Messages

How does 1 ASM instance in a 10 node RAC cause all 10 ASM instance to hang

Linux RHEL4
11.2.0.1.0 GI
11.2.0.1.0 RDBMS
11.1.0.7.0 RDBMS
10.2.0.4.4 RDBMS
Yesterday we had one of the ASM instance on our 10-node cluster hang with a latch "ASM file allocation latch". Oracle support has stated we are hitting a bug with is fixed in the latest PSU.
What I am trying to understand is how a latch on one ASM instance caused all 10 ASM instances to hang?
Oracle Supports explanation still does not answer how all 10 ASM instance were affected other then the faulty code that the patch fixes. Bellow is info out of the SAR.
Data Guard Site:
================
ARC1 PID 21508 reports ORA-240 'control file enqueue held for more than 120 seconds' at Thu Oct 28 11:35:54 2010. This message means ARC1 PID 21508 was holding the enqueue past the maximum tine limit of 120 seconds.
Next ARC0 PID 17398 reports ORA-16146: 'control file enqueue unavailable' at Thu Oct 28 11:36:52 2010. This means ARC0 PID 17398 tried to access the controlfile and it could get the lock.
ARC1 PID 21508 is then killed at Thu Oct 28 11:49:57 2010.
Killing enqueue blocker (pid=21508) on resource CF-00000000-00000000 by (pid=23078) by killing session 5.3
We see that RSM has been restarted by Broker. This matches to the alert.log and messages showing RSM being restarted several time. i.e. RSM0 started with pid=84, OS id=27915
Since this started happening around 11:14, the problem may have really started then instead of w/ the CF enqueue block.
The primary appears to be shipping redo to the standby using asynchronous mode. Unless there was a gap, I do no know if ARC1 should have been doing any remote network I/O. Because a log switch to thread 1 sequence 5235 had just happened at 11:33am, I suspect it was a local disk I/O that was started at least. The ORA-240 is reported at 11:35, exactly 120 sec (or 2min) from this log switch. Notice also the entry to show the log thread 1 sequence 5234 was registered to the controlfile didn't happen yet.
ASM Side:
============
From the systemstate dump on ASM, multiple processes are waiting on 'ASM file allocation latch' and we are kind of stuck on stack:
ksedsts()+461<-ksdxfstk()+32<-ksdxcb()+1782<-sspuser()+112<-0000003218E0C5B0<-kfuhInsert()+175<-kffilCreate()+601<-kfnsUFG()+3691<-kfnsBackground()+4382<-kfnDispatch()+527<-opiodr()+1149<-ttcpip()+1251<-opitsk()+1633<-opiino()+958<-opiodr()+1149<-opidrv()+570<-sou2o()+103<-opimai_real()+133<-ssthrdmain()+214<-main()+201<-__libc_start_main()+219
This caused the hang on the ASM side and hence ASM was not responding to the database. The CF Enqueue issue on the database was a side effect of this.
This is a direct <BUG:9232266> which is a duplicate of <BUG:8974548>

Thanks Murali,
I was little reluctent to open a tar since my experince says that its better to troubleshoot the issue yourself instead of spending time with the Oracle support :)
Well, I got some more information on this : the sql for the process id of ASM instance is :
Alter Diskgroup mount all;
It looks like it is unable to mount the diskgroup and get hunged at that point , is it due to the new disk added to the system or do we missed something after adding the new disk.
Also, the ASM process can not be killed from unix box while the ASM is down.
Will appreciate your time if we can move in any directions from here ..
Thanks ,
Ankur

Correct steps to reload ASM disks into a running ASM instance on Linux RHEL

Hi guys,
i hope this is the correct forum, awfully i did not found any document specifically talking abou this.
first of all let me explain quickly my goal: in my server (it contains the same data of 3 production RACs for reporting purposes) i would like to shutdown a single instance (i have 3) and realod his disks to refresh the data or because for some reason its mount into ASM is failed.
this is a mix of Oracle ASM and Linux stuff...
on this server there is a shell script that perform the following steps:
1) shutdown 3 instances of 11g (11.2.0.2.0 with patch for asm already installed for bug... dont remember)
2) shutdown ASM instance
3) stop ASMLIB
4) stop multipathd
5) remove all disks devices from linux
6) take a snapshot on the 3 production RACs
7) remap the disks to this server (SAN stuff)
8) rescan the disks
9) start ASMLIB
10) start ASM instance
11) mount the DiskGroups
12) start 3 oracle instances
this works fine... my problem is when i try to refresh the disks of just 1 of the 3 instances, i perform the following steps:
1) stop instance ABC
2) dismount ABC diskgroups related to ABC instance
3) wait 5 seconds (dont ask... if idid it without ASM still have the disks locked)
4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
5) remove mpaths related to the disks that need to be refreshed or correctly mounted oneagain
6) remove devices
7) unmap disks on SAN
8) take snapshot (clone disks)
9) map disks from SAN
10) delete bindings file
11) rescan devices
12) execute multipath command (to rebuild bindings file)
13) execute oracleasm scandisks
14) mount DiskGroups
15) start instance ABC
actually i dont understand why the OS (or specifically ASMLIB) do not recognize me anymore one of the ASMLIB disk
do you have any idea ? or im completly crazy doing that ?
best regards,
Luca

Hi,
well this step
4) delete the ASMLIB disks (oracleasm deletedisk XYZ) relate to such diskgroups
is not good. Because it will clear the ASM Header and as a result ASM will never again be able to detect the disks.
So it is clear that "scnadisks" later will not see the disks, because you wiped them.
Worse: You did the snapshot after deleting them... this gets tricky to get them "repaired" again.
However there is the possibility to relabel a dropped ASM disks. You need to open an SR for this, since the procedure to restore the lost ASM header is not that simple..
Regards
Sebastian

Status of ASM instance

Hi ,
when i fired
select status, instance_name from v$instance ;
started ASM+
my all diskgroups are mounted ...
from above input i have following consideration ...
1.ASM instance is always in NOMOUNT stage(as it is having only one stage to go ) but it mounts all the disks and it is available(Read,write) for database...
PLZ correct me if i m wrong.......

Santosh Pradhan wrote:
Hi ,
when i fired
select status, instance_name from v$instance ;
started ASM+
my all diskgroups are mounted ...
from above input i have following consideration ...
1.ASM instance is always in NOMOUNT stage(as it is having only one stage to go ) but it mounts all the disks and it is available(Read,write) for database...
PLZ correct me if i m wrong.......Hi, did you are using RAC? Or you are installed standalone?
ASM instance is mounted, it means all disk groups is mounted.
If diskgroups is mounted then ASM Instance is mount state.
Can you paste here result of ,
export ORACLE_SID=+ASM
sqlplus / as sysasm
sql> select instance_name, status from v$instance; Mahir

ASM instance status

Hi All,
I exported the ASM instance in one of our test environment. oracle 11g aix box
As we all know that asm instance can be brought to nomount and mount. but not in open mode.
now when i check the view v$instance, it show the asm instance status as 'STARTED', but not mounted? Is there any reason behind this?
Same way i checked for exporting a database , and brought it to
nomount state, instance status was nomount
mount state, instance status was mounted
open state, instance status was open.
but when i check the v$asm_diskgroup it showed the diskgroup is mounted.
so cant we check an asm instance is mounted or not apart from v$asm_diskgroup view and alert log file?
Regards

Read it:
/thread/2402674#10391232

使用AMDU工具从无法MOUNT的DISKGROUP中抽取数据文件

AMDU是ORACLE针对ASM开发的源数据转储工具，其全称为ASM Metadata Dump Utility(AMDU)
AMDU具体以下三个主要功能：
1. 将ASM DISK上的元数据转储到文件系统上以便分析
2. 将ASM文件的内容抽取出来并写入到OS文件系统，Diskgroup是否mount均可
3. 打印出块的元数据，以块中C语言结构或16进制的形式
这里我们将用到使用AMDU抽取ASM DISKGROUP中的数据文件； ASM作为近几年最流行的存储解决方案，大家对他的优缺点都有所了解，其中的问题之一就是ASM是个黑盒。一旦DISKGROUP无法MOUNT起来就意味着传统方法无法以磁盘为基础导出任何数据。
AMDU解决了这一问题，这里我们仅讨论在ASM DISKGROUP 无法MOUNT的情况下的范畴，不讨论RDBMS数据文件在ASM下讹误的处理。
注意 AMDU虽然是11g才发布的工具，但是实际对10g的ASM 也有效。
当前你可能遇到的场景是， ORACLE DATABASE的SPFILE、CONTROLFILE、DATAFILE均存放在ASM DISKGROUP中，而由于一些ASM ORA-600错误导致无法MOUNT该DISKGROUP，你需要的是使用AMDU将这些文件从ASM DISK中转储出来。
场景 1 丢失了包括SPFILE、CONTROLFILE、DATAFILE
恢复步骤：从备份中还原出SPFILE ，即便没有SPFILE的话PFILE也可以，总之你需要从参数文件中了解control_files的信息
SQL> show parameter control_files
NAME                                 TYPE        VALUE
control_files                        string      +DATA/prodb/controlfile/curren
                                                 t.260.794687955, +FRA/prodb/co
                                                 ntrolfile/current.256.79468795
                                                 5获得control_files 控制文件在ASM中的位置后事情就好办了，+DATA/prodb/controlfile/current.260.794687955 这里 260是这个控制文件在+DATA 这个DISKGROUP中的FILE NUMBER
此外我们还需要ASM DISK的DISCOVERY PATH信息，这完全可以从ASM的SPFILE中的asm_diskstring 参数获得
[oracle@mlab2 oracle.SupportTools]$ unzip amdu_X86-64.zip
Archive: amdu_X86-64.zip
inflating: libskgxp11.so
inflating: amdu
inflating: libnnz11.so
inflating: libclntsh.so.11.1
[oracle@mlab2 oracle.SupportTools]$ export LD_LIBRARY_PATH=./
[oracle@mlab2 oracle.SupportTools]$ ./amdu -diskstring '/dev/asm*' -extract data.260
amdu_2009_10_10_20_19_17/
AMDU-00204: Disk N0006 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0006: '/dev/asm-disk10'
AMDU-00204: Disk N0003 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0003: '/dev/asm-disk5'
AMDU-00204: Disk N0002 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0002: '/dev/asm-disk6'
[oracle@mlab2 oracle.SupportTools]$ cd amdu_2009_10_10_20_19_17/
[oracle@mlab2 amdu_2009_10_10_20_19_17]$ ls
DATA_260.f report.txt
[oracle@mlab2 amdu_2009_10_10_20_19_17]$ ls -l
total 9548
-rw-r--r-- 1 oracle oinstall 9748480 Oct 10 20:19 DATA_260.f
-rw-r--r-- 1 oracle oinstall    9441 Oct 10 20:19 report.txt以上转储出来的DATA_260.f 就是控制文件，我们使用该控制文件startup mount RDBMS实例：
SQL> alter system set control_files='/opt/oracle.SupportTools/amdu_2009_10_10_20_19_17/DATA_260.f' scope=spfile;
System altered.
SQL> startup force mount;
ORACLE instance started.
Total System Global Area 1870647296 bytes
Fixed Size                  2229424 bytes
Variable Size             452987728 bytes
Database Buffers         1409286144 bytes
Redo Buffers                6144000 bytes
Database mounted.
SQL> select name from v$datafile;
NAME
+DATA/prodb/datafile/system.256.794687873
+DATA/prodb/datafile/sysaux.257.794687875
+DATA/prodb/datafile/undotbs1.258.794687875
+DATA/prodb/datafile/users.259.794687875
+DATA/prodb/datafile/example.265.794687995
+DATA/prodb/datafile/mactbs.267.794688457
6 rows selected.startup mount实例后，可以从v$datafile中获得数据文件名，其中就包括了其在DISKGROUP中的FILE NUMBER
再使用./amdu -diskstring '/dev/asm*' -extract 命令即可导出数据文件到操作系统
[oracle@mlab2 oracle.SupportTools]$ ./amdu -diskstring '/dev/asm*' -extract data.256
amdu_2009_10_10_20_22_21/
AMDU-00204: Disk N0006 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0006: '/dev/asm-disk10'
AMDU-00204: Disk N0003 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0003: '/dev/asm-disk5'
AMDU-00204: Disk N0002 is in currently mounted diskgroup DATA
AMDU-00201: Disk N0002: '/dev/asm-disk6'
[oracle@mlab2 oracle.SupportTools]$ cd amdu_2009_10_10_20_22_21/
[oracle@mlab2 amdu_2009_10_10_20_22_21]$ ls
DATA_256.f report.txt
[oracle@mlab2 amdu_2009_10_10_20_22_21]$ dbv file=DATA_256.f
DBVERIFY: Release 11.2.0.3.0 - Production on Sat Oct 10 20:23:12 2009
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
DBVERIFY - Verification starting : FILE = /opt/oracle.SupportTools/amdu_2009_10_10_20_22_21/DATA_256.f
DBVERIFY - Verification complete
Total Pages Examined         : 90880
Total Pages Processed (Data) : 59817
Total Pages Failing   (Data) : 0
Total Pages Processed (Index): 12609
Total Pages Failing   (Index): 0
Total Pages Processed (Other): 3637
Total Pages Processed (Seg) : 1
Total Pages Failing   (Seg) : 0
Total Pages Empty            : 14817
Total Pages Marked Corrupt   : 0
Total Pages Influx           : 0
Total Pages Encrypted        : 0
Highest block SCN            : 1125305 (0.1125305)@@
如何在OTN中文技术论坛提一个问题？
论坛礼仪需知及学习oracle的方法论
Maclean Liu
Oracle Database Administrator
Oracle Certified 10g/11g Master
www.askmaclean.com

楼主，你好。我们现在也是按此方案正在进行，但有一个技术点
./amdu -diskstring '/dev/asm*' -extract data.260
asm 实例不能mount 起来
其中260 这个号是asm filenumber 有的数据文件是名字是这样的
+DG_ORA/mos5200/datafile/pm4h_db94.dbf
从文件名上不能看到260这样的number
可能是因为asm不能mount ,从v$asm_file 里也只能看到部分文件
oracle 提供了一个方案把extract 出来的文件对其block0 dump,可是asm 里的文件太多了归档也放在里面了，不太具有可行性
如何解决呢,ML想个办法,谢谢

Verify asm instance

Hi
What is the best way to verify that asm instance is mounted,up and ready ?
. oraenv
ORACLE_SID = [] ? +ASM
sqlplus "/ as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 11 14:30:38 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-01507: database not mounted

Ricardinho wrote:
Hi
What is the best way to verify that asm instance is mounted,up and ready ?
. oraenv
ORACLE_SID = [] ? +ASM
sqlplus "/ as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Feb 11 14:30:38 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-01507: database not mounted
Ricardo,
ASM instance has nothing to get it mounted or up. All what it has a spfile which just starts the instance. So it would never be mounted or open and will be always in the started status.
HTH
Aman....

Possible to create new ASM instance and "import" existing diskgroup?

This is my worst nightmare. Two days before a server was about to be shut down, it crashed on me, corrupting the filesystem where Oracle was installed. Setup was an HP-UX 11.11 server running Oracle 10g with ASM storage on a disk array. Both instances were in the filesystem that got corrupted, and amazingly, we don't have a backup, so I'm not able to restore the instance configs and restart the database. Presumably, my data is still sitting there on the disks that belong to the ASM diskgroup, but I don't know how to get at it. I started by creating a new ASM instance, but I can't figure out if there's a way to create a diskgroup out of those 16 disks without wiping out what's on them.
V$ASM_DISK shows all the disks as MEMBERs, with the CREATE_DATE that they were originally created, so I know at least the headers are intact. So is there any way I can manually recreate that diskgroup in my new instance so it will mount the disks and let me at the data?
I realize that not having backups is the height of stupidity, but that boat has sailed. My company also chose not to pay for Oracle Support this year, so I'm kind of on my own. If anybody can at least point me in the right direction or tell me that it's a lost cause, I'd appreciate it.

Well, a little progress. I was able to finally mount the disks in my new ASM instance, and using asmcmd, I can actually see my datafiles sitting there. So now I'm thinking I should try manually creating a new database instance pointing to the spfile that's in there and try starting that. I'm also going to try using RMAN and the XMLDB FTP trick to copy those datafiles somewhere else so I know I can play with them.

ORA-15077: could not locate ASM instance serving a required diskgroup

My cluster is gone...
due to restart of the network, the cluster fenced node2 from my configuration. Since the evicting, the cluster is not starting any more.
ocrcheck
PROT-602: Failed to retrieve data from the cluster registry
PROC-26: Error while accessing the physical storage
ORA-15077: could not locate ASM instance serving a required diskgroup
The OCR Disks are within ASM.
Oracleasm does see the disks
crsctl query css votedisk is also giving the correct information about the votingsdisks which are also in the same OCR diskgroup
crsctl query css votedisk
## STATE File Universal Id File Name Disk group
1. ONLINE 0eb6aaa85e5c4fd6bf9d0481cfd7d517 (ORCL:VOTE1) [OCR]
2. ONLINE 5a66449fbada4f34bf0c3be4574f03bc (ORCL:VOTE2) [OCR]
3. ONLINE 76ad295ebc054f07bfea124fb08da432 (ORCL:VOTE3) [OCR]
Located 3 voting disk(s).
Any ideas why the cluster is not starting anymore ? I am afraid of restarting node 1...
chris

Really would help to know what operating system you are using...
When you set up the disks for use with ASM, did you stamp them with ASMLIB? If not, did you configure device persistance with udev? Without using one of these methods, the disk identification can change when a node is restarted, and ASM is then unable to locate the disks.

ASM mount diskgroup

Hi All
I am using 11gR2 but when I start the grid infrastructure using "crsctl start crs" then the ASM instance get started but the disk group did not get mounted. My question how can I get the ASM disk groups get mounted when I start the grid infrastructure ?
Thanks

Hi,
by oracleasm lib utility you can configure as below
# /etc/init.d/oracleasm configure
Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Scanning system for ASM disks: [ OK ]
# /etc/init.d/oracleasm enable
Thanks

No member Disk displayed while creating Diskgroups for new ASM instance

Have installed CRS
Have installed DB software
Invoked dbca to create asm instance
Instance created
Disk members not displayed for creating disk groups
OS is Hp ux 11.23

The most likely reason on HP/UX is the permissions on the devices, all the devices to be used by ASM (including the devices for alternate paths) should be set to oracle:dba (or what ever user ASM is installed under) and chmod to 664.

Upgrade ASM instance database 10g to 11g

Hi,
In my environment, I have ASM instance database 10.2.0.3 running on solaris 10 (64-bit), I need to upgrade to ASM instance 11.1.0.6 database. please guide me an overview of steps...
thanks in advance

Thanks for the response,
Sorry, In my environment I know database (10.2.0.3) is mounted in ASM diskgroups, now i have a concern
1) If database is mounted in ASM diskgroups, could it be a database instance or it has to be only ASM instance connected to the database?
2) As in my upgrade from ASM instance (10.2.0.3) to ASM instance (11.1.0.6), do we need to upgrade asm instance as well as database? i mean to invoke DBUA twice for upgrading ASM instance then for upgrading database as well?
Sorry for some silly questions...please make me clear...
Regards

ASM instances on 2 node Oracle RAC 10g r2 on Red Hat 4 u1

Hi all
I'm experiencing a problem in configuring diskgroups under +ASM instances on a two node Oracle RAC.
I followed the official guide and also official documents from metalink site, but i'm stuck with the visibility of asm disks.
I created fake disks on nfs with Netapp certified storage binding them to block device with the usual trick "losetup /dev/loopX /nfs/disk1 " ,
run "oracleasm createdisk DISKX /dev/loopX" on one node and
"oracleasm scandisks" on the other one.
With "oracleasm listdisks" i can see the disks at OS level in both nodes , but , when i try to create and mount diskgroup in the ASM instances , on the instance on which i create the diskgroup all is well, but the other one doesn't see the disks at all, and diskgroup mount fails with :
ERROR: no PST quorum in group 1: required 2, found 0
Tue Sep 20 16:22:32 2005
NOTE: cache dismounting group 1/0x6F88595E (DG1)
NOTE: dbwr not being msg'd to dismount
ERROR: diskgroup DG1 was not mounted
any help would be appreciated
thanks a lot.
Antonello

I'm having this same problem. Did you ever find a solution?

Error while starting ASM instance

when i was trying to startup my ASM database , i was getting the following error.
SQL> startup
ASM instance started
Total System Global Area 125829120 bytes
Fixed Size 2019000 bytes
Variable Size 98644296 bytes
ASM Cache 25165824 bytes
ORA-15032: not all alterations performed
ORA-15003: diskgroup "DBDATA" already mounted in another lock name space"
thnx in advance

Hi,
i was not aware of ASM anymore, i can give some more details of this.
There was already an instance named +ASM in the host, which has the diskgroup 'DBDATA' created.
But now i have created a new instance and i was trying to connect to the same diskgroup.
I dont have permission of the root, but i have the oracle login.
could u pleaze help me in this regard...
i need to connect to the diskgroup, if i try to stop the other instance, i was not getting the error, but the diskgroup is getting dis-mounted.
thnx alot for the replies

Rebooting the server with ASM instance............

Hi folks
I have to go for reboot of the server as I am adding a RAW device for having one more mount and also will be adding a disk to disk group.
1) alter diskgroup diskgroupname add disk '/u09'; Is this correct to add a new disk to the diskgroup of ASM instance?
2) I will have to shutdown all the six instances within the ASM instance and shutdown the ASM instance? Is this correct
After a successfull Rebbot is done
3) I will have to startup the ASM instance first and one by one startup the other six instances? Is it the right sequence.
Please reply at the earliest.
Thanks
Shiva

Hi
If you want to shutdown the server to add the RAW device then:
1. Shutdown all instances but shutdown ASM instance in the end.
2. Shutdown server and add the RAW device.
3. Startup server
4 Add the diskgruop and also you can increase the value of rebalance parameter.
5. Start all the instances that are using this ASM instance.
Hope this Help
Regards

ASM instance wont mount diskgroup..

Similar Messages

Maybe you are looking for