(Doc ID 1600325.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


1] v$asm_disk view returns no rows from RDBMS instance but it returns correct results from ASM instance

2]  truss output taken from not working env shows an access error on $GRID_HOME/dbs/ab_+ASM.dat file

2-1] Take truss output in the following way

$sqlplus sys as sysdba
SQL> select spid from v$process where addr= (select paddr from v$session where sid = (select sid from v$mystat where rownum = 1));
--To get the pid of this session
--Open one more putty session of the same node and trace this pid as "$truss -aef -o /tmp/truss.txt -p <PID>
--After the tracing started run the below statement from the previous sql session

SQL> select count(*) from v$asm_disk;

2-2] Portion of truss output taken from NOT WORKING env   

      30343278:       64290983: kwrite(6, " A C T I O N   : [ 3 1 ]".., 184) = 184
      30343278:       64290983: kwrite(6, "\n", 1)                    = 1
      30343278:       64290983: kopen("/oravol11/oragridhome/dbs/ab_+ASM.dat", O_RDONLY|O_LARGEFILE) Err#2  ENOENT              <<<<<<<<<-------------- There is an error accessing ab_+ASM.dat

2-3]  Portion of truss output taken from WORKING env     

       23658594:       40304829: kopen("/oravol11/orainggridbase/oragridhome/dbs/ab_+ASM.dat", O_RDONLY|O_LARGEFILE) = 12
       23658594:       40304829: statx("/oravol11/orainggridbase/oragridhome/dbs/ab_+ASM.dat", 0x0FFFFFFFFFFF5650, 176, 0) = 0     <<<<<<<<<-------------- No error accessing ab_+ASM.dat


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms