/dev/rdsk/c?t?d?p0 Device Presented to ASM Has Wrong Size
(Doc ID 845467.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 184.108.40.206 [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Solaris on x86-64 (64-bit)
Sun Solaris x86-64 (64-bit)
DBCA 10.2.0.1 -220.127.116.11 when viewing ASM candidate devices
On Solaris x86-64 it is possible to present to ASM p-partitions, i.e. partitions named
/dev/rdsk/c?t?d?p?, also known as fdisk or PC BIOS partitions.
However the device size showed by ASM is wrong. I.e. it doesn't match the physical device or disk size.
For example in case of c?t?d?p0 it would be assumed ASM would see the whole disk but a wrong size is showed by DBCA.
Enabling visibility of the /dev/rdsk/c?t?d?p0 device by changing the permissions on the Solaris device
it points to.
Consider a p0 device like:
ls -l /dev/rdsk/c0t3d0p0 lrwxrwxrwx 1 root root 77 Jul 14 2006 /dev/rdsk/c0t3d0p0
and by issuing
chown oracle:dba /devices/pci@0,0/pci8086,3595@2/pci8086,330@0/pci1028,16d@5/sd@3,0:q,raw
the device would become visible to ASM.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document