05-27-2011
Hi,
as your system still seems to be up, try just a simple rm /dev/asm_diskx (on the device that has the same major/minor number as your hdisk0). If the disk is afterwards empty (what may happen as the asm header is using the same header as the volumegroup definition) than try to unmirror and reduce the 'missing' disk from rootvg like you would do it with a dead disk - you can run rmdev -Rdl hdisk0 as well ....
Just for my curiosity - how did you manage to do this in first instance - as volumegroups and asm devices exclude each other ... so we had destroyed our asm databases several times by doing the opposite - assigning asm devices mistakenly to volumegroups
Regards
zxmaus
8 More Discussions You Might Find Interesting
1. Solaris
I'm running solaris, with solstice disksuite.
With other systems, i run veritas volume manager.
My dba want to implement ASM with oracle 10g.
Is it possible to create volumes with disksuite for ASM.
Oracle want a volume name ex: vol1
My question is, what is the best STANDARD solution.
... (5 Replies)
Discussion started by: simquest
5 Replies
2. Red Hat
Perhaps someone here has some experience with this.
machine os RHE 4 6
oracle 10g RAC
disk is SAN attached clariion.
I have presented new disks to the host, so the machine sees all needed LUNS. powermt shows them, they are labeled and i have fdisk'd them.
They are visible across all RAC... (5 Replies)
Discussion started by: Eronysis
5 Replies
3. Solaris
Hi,
Can any one please provide the command to format an Oracle Raw Disk in Solaris 10.
I have been used the following commands:
dd if=/dev/zero of=<raw disk path>
Thanks
---------- Post updated at 12:20 PM ---------- Previous update was at 10:11 AM ----------
Well this didn't give... (0 Replies)
Discussion started by: Mack1982
0 Replies
4. Programming
I am novice to perl. Can someone guide me on the below query. We have an existing perl script which connects to database to check the disk group status which i wanted to retieve directly from ASM rather than database.
This is because, a cluster has more than 4 databases running and a check on... (0 Replies)
Discussion started by: sai_rsk
0 Replies
5. Shell Programming and Scripting
I am novice to perl. Can someone guide me on the below query. We have an existing perl script which connects to database to check the disk group status which i wanted to retieve directly from ASM rather than database.
This is because, a cluster has more than 4 databases running and a check on... (1 Reply)
Discussion started by: sai_rsk
1 Replies
6. Solaris
Hi
I am new to this forum & oracle DBA also, I would like to know that can we add Oracle ASM in failover mode in sun cluster 3.3 or 4.0 means that if suppose oracle is running along with ASM on node1 & this node went down due to hardware issue then both oracle along with ASM must move to... (1 Reply)
Discussion started by: hb00
1 Replies
7. UNIX for Advanced & Expert Users
Hi all,
Could anyone please share ideas or logic on how to automate add/resize datafile in Oracle ASM Storage for Oracle RAC/Single Node databases when any tablespace space alert is trigerred by OEM?
Thanks for your help and time on it!
Thanks®ards,
a1_win
Please DON'T use CODE tags... (0 Replies)
Discussion started by: a1_win
0 Replies
8. Solaris
Hi Folks,
I've just built a Solaris 11.3 server with a number of LDOM's, all good and well and not any serious issues so far.
On our older Solaris 10 systems we ran Oracle 11g using ASM disks, these disks were the raw device meta disks and came in very nicely as "/dev/md/rdsk/dnn" all worked... (4 Replies)
Discussion started by: gull04
4 Replies
HD(4) Linux Programmer's Manual HD(4)
NAME
hd - MFM/IDE hard disk devices
DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major
device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave
hdd.
General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the
partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order
the partitions are discovered, and only non-empty, non-extended partitions get a number. However, partition numbers 1-4 are given to the
four partitions described in the MBR (the `primary' partitions), regardless of whether they are unused or extended. Thus, the first logi-
cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions
on an IDE disk.
For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS `primary' partition on the
second one.
They are typically created by:
mknod -m 660 /dev/hda b 3 0
mknod -m 660 /dev/hda1 b 3 1
mknod -m 660 /dev/hda2 b 3 2
...
mknod -m 660 /dev/hda8 b 3 8
mknod -m 660 /dev/hdb b 3 64
mknod -m 660 /dev/hdb1 b 3 65
mknod -m 660 /dev/hdb2 b 3 66
...
mknod -m 660 /dev/hdb8 b 3 72
chown root:disk /dev/hd*
FILES
/dev/hd*
SEE ALSO
mknod(1), chown(1), mount(8), sd(4)
Linux 1992-12-17 HD(4)