000036042 - ORA-15001: diskgroup "DG01" does not exist error in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Mar 3, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036042
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Product/Service Type: Appliance and Software Only
RSA Version/Condition: 6.9.1 and above
IssueFor the RSA Identity Governance & Lifecycle application, the Oracle database is used to store data.
On an RSA Appliance, or a customer supported implementation of the Oracle database for RSA's Identity Governance & Lifecycle application, Oracle ASM can also be used to manage the file storage for the Oracle database.

However, the situation may occur, that when attempting to start ACM, the following error may be reported by the Oracle database on startup.

ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DG01/AVDB/spfileAVDB.ora'
ORA-17503: ksfdopn:2 Failed to open file +DG01/AVDB/spfileAVDB.ora
ORA-15056: additional error message
ORA-17503: ksfdopn:2 Failed to open file +DG01/avdb/spfileavdb.ora
ORA-15001: diskgroup "DG01" does not exist or is not mounted
ORA-06512: at line 4

CauseThese errors indicate that Oracle ASM is not running.
However, please note that these errors are not the only symptoms that can be observed, when Oracle ASM is not running.

One reason for Oracle ASM to be not running, is that the LINUX Operating System version may different to the Oracle ASM driver.

The following commands show that the version of the Red Hat Operating System is 423, but the version of the Red Hat oracleasm driver is 419.
This is a mismatch in versions that would cause Oracle ASM not to run.

$ uname -a 
Linux test9.rsabuild.local 2.6.18-423.el5 #1 SMP Fri Sep 22 14:26:40 EDT 2017 x8 6_64 x86_64 x86_64 GNU/Linux 

$ cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 5.11 (Tikanga) 

$ rpm -qa | grep asm 


ResolutionEngage the LINUX System Administrator, so that they can revert either the Operating System version or oracleasm version back to their original versions (i.e. when Oracle ASM was working).  Providing information about the various Linux software update tools (i.e. YaST or zypper) is beyond the scope of RSA Customer Support.



The "oracleasm" driver is written by the Operating System vendor.
On SUSE Linux Enterprise Server (SLES) the oracleasm driver is written by Novell (part of Micro Focus), and distributed with the SUSE Linux software.
On Red Hat Linux the oracleasm driver is written by Oracle, where Red Hat Linux is also referred to as Oracle Linux.
Therefore, any updates to this driver will be made available by the Operating System vendor.

However, for an RSA Appliance, updates to the oracleasm driver are controlled by the Appliance Updater.
This is why on an RSA Appliance, the following drivers are not installed;
  • oracleasm-support
  • oracleasmlib
These drivers allow the oracleasm driver to be updated automatically by the Linux System Administrator.
By not installing these drivers, RSA is able to maintain the compatibility of the Operating System version and the oracleasm driver version, and avoid problems such as that reported in this article.

For more information about the Appliance Updater, please go to the RSA Identity Governance & Lifecycle Appliance Updater web page.