ORA-17500: ODM err:ODM ERROR V-41-3-2-180-2 Filesystem not mounted with ODM/QIO support

Article:TECH158234  |  Created: 2011-04-16  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH158234
Article Type
Technical Solution


Environment

Issue



 

[ ISSUE ]
Oracle ODM with error "ORA-17500: ODM err:ODM ERROR V-41-3-2-180-2 Filesystem not mounted with ODM/QIO support"
 

[ BACKGROUND HISTORY ]
1. Since VRTSodm was upgrade to RP3 (PHKL_39471), file systems and odm device(/dev/odm) were mounted correctly.
2. On the contrary, Oracle started to complain about the error as follows.
[ ISSUE ]
Oracle ODM with error "ORA-17500: ODM err:ODM ERROR V-41-3-2-180-2 Filesystem not mounted with ODM/QIO support"
 

[ BACKGROUND HISTORY ]
1. Since VRTSodm was upgrade to RP3 (PHKL_39471), file systems and odm device(/dev/odm) were mounted correctly.
2. On the contrary, Oracle started to complain about the error as follows.

Error



 

[ ERROR MESSAGES ]
-------------------------------------------------------------
ORA-00202: control file: '/symctst1/oradata/control01.ctl'
ORA-17503: ksfdopn:3 Failed to open file /symctst1/oradata/control01.ctl
ORA-17500: ODM err:ODM ERROR V-41-3-2-180-2 Filesystem not mounted with ODM/QIO support

-------------------------------------------------------------

Environment



 

[ VERSION OF OS/PACKAGE ]
- HPUX11v3
- SFHA5.0 for HPUX11v3

Cause



- The vxfs file system must be supported under ODM with "qio".


Solution



 

1. According to the technote, TECH126546.
- Stopped Oracle
- Tried to umount /dev/odm
- Mounted it again.
- Started Oracle
- However, it ended up failing to bring Oracle online.
 
 
 
2. Then looked up the difference between this file system and other file systems in /etc/fstab and at OS level.
It is because it was shown that Oracle complained on the file system, '/symctst1/oradata/control01.ctl'
----------------------------------------------------------------------------------------------------
# mount -v |egrep "symctst1|symctst2"
/dev/vx/dsk/SymcDg1/vol10 on /symctst1 type vxfs delaylog,cio                  <<< This is the problem!
/dev/vx/dsk/SymcDg2/vol11 on /symctst2 type vxfs delaylog,qio
 
 
# cat /etc/fstab |egrep "symctst1|symctst2"
/dev/vx/dsk/SymcDg1/vol10 /symctst1 vxfs suid,cio 0 0                                <<< This is the problem!
/dev/vx/dsk/SymcDg2/vol11 /symctst2 vxfs suid 0 2
----------------------------------------------------------------------------------------------------

 
 
3. Thereafter, it was able to find out the big difference between symctst1(abnormal) and other file system(normal)
-  The file system, symctst1  was mounted with "cio" option.
-  Whereas, the other file system were mounted with "qio" by default.
-  It is because most of all, the vxfs file system must be supported under ODM with "qio".
-  However, it seems that there should have been some change in the entry of /etc/fstab due to some reason by someone else, which is very severe and critical.
 
 
 
4. So therefore, /etc/fstab file was modified correctly on /symctst1 with qio option.
----------------------------------------------------------------------------------------------------
[ BEFORE ]
/dev/vx/dsk/SymcDg1/vol10 /symctst1 vxfs
suid,cio 0 0
 
[ AFTER ]
/dev/vx/dsk/SymcDg1/vol10 /symctst1 vxfs suid  0 2
----------------------------------------------------------------------------------------------------

 
 
5. Then Oracle DBA confimed Oracle engine got brought up without a file.
 




Article URL http://www.symantec.com/docs/TECH158234


Terms of use for this information are found in Legal Notices