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
LEARN ABOUT OPENDARWIN
mknod
MKNOD(8) BSD System Manager's Manual MKNOD(8)
NAME
mknod -- make device special file
SYNOPSIS
mknod [-F format] name [c | b] major minor
[-F format] name [c | b] major unit subunit
name [c | b] number
name [p]
DESCRIPTION
The mknod command creates device special files. Normally the shell script /dev/MAKEDEV is used to create special files for commonly known
devices; it executes mknod with the appropriate arguments and can make all the files required for the device.
To make nodes manually, the required arguments are:
name Device name, for example ``sd'' for a SCSI disk on an HP300 or a ``pty'' for pseudo-devices.
b | c | p
Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
type is b. All other devices are character type devices, such as terminal and pseudo devices, and are type c. To create named pipes
the type p can be used.
major The major device number is an integer number which tells the kernel which device driver entry point to use. To learn what major
device number to use for a particular device, check the file /dev/MAKEDEV to see if the device is known, or check the system depen-
dent device configuration file:
``/usr/src/sys/conf/device.architecture''
(for example device.hp300).
minor The minor device number tells the kernel which one of several similar devices the node corresponds to; for example, it may be a spe-
cific serial port or pty.
unit and subunit
The unit and subunit numbers select a subset of a device; for example, the unit may specify a particular SCSI disk, and the subunit a
partition on that disk. (Currently this form of specification is only supported by the bsdos format, for compatibility with the
BSD/OS mknod(8) .)
Device numbers for different operating systems may be packed in a different format. To create device nodes that may be used by such an oper-
ating system (e.g. in an exported file system used for netbooting), the -F option is used. The following formats are recognized: native,
386bsd, 4bsd, bsdos, freebsd, hpux, isc, linux, netbsd, osf1, sco, solaris, sunos, svr3, svr4 and ultrix.
Alternatively, a single opaque device number may be specified.
SEE ALSO
mkfifo(1), mkfifo(2), mknod(2), MAKEDEV(8)
HISTORY
A mknod command appeared in Version 6 AT&T UNIX. The -F option appeared in NetBSD 1.4.
NetBSD 1.4 September 11, 1998 NetBSD 1.4