Article Number
000033144
Applies To
RSA Product Set: RSA Identity Governance and Lifecycle
RSA Product/Service Type: Hard Appliance
RSA Version/Condition: 6.8.1, 6.9.1, 7.0.0, 7.0.1, 7.0.2, 7.1
Issue
The following error displays when starting the database using
acm startdb or
sudo aveksa_server startdb:
PRCR-1004 : Resource ora.asm is already running
PRCR-1079 : Failed to start resource ora.asm
CRS-5702: Resource 'ora.asm' is already running on 'hostname'
ASM is running on 'hostname'
PRCR-1079 : Failed to start resource ora.avdb.db
CRS-5017: The resource action "ora.DG01.dg start" encountered the following error:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "DG01" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "DG01"
. For details refer to "(:CLSN00107:)" in "/u01/app/11.2.0/grid/log/<hostname>/agent/ohasd/oraagent_oracle/oraagent_oracle.log".
CRS-2674: Start of 'ora.DG01.dg' on 'hostname' failed
Database is not running.
Oracle Enterprise Manager 11g Database Control Release 11.2.0.3.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
https://<FQDN>:1158/em/console/aboutApplication
Starting Oracle Enterprise Manager 11g Database Control ...... started.
Cause
There are many reasons why a database may fail to start. This article goes through one particular use case.
In this case the operating system kernel had been upgraded on the hard appliance outside of the RSA appliance updater. As a result, the ASMLib that ships with the appliance and that corresponds to the OS kernel version was no longer compatible with the upgraded kernel and the database failed to start as it failed to discover all the ASM diskgroups.
CAUTION: The OS that is provided by RSA on RSA appliances should only be upgraded using the RSA-provided appliance updater.
Resolution
Normally, you can install the corresponding kernel driver to make the ASMLib compatible, but this will put the system in an unsupported state.
The recommended and supported solution is to revert back the kernel upgrade and use the RSA Appliance updater to upgrade the kernel and OS packages.
Workaround
If you are unable to revert back the kernel upgrade, you will/may need to reinstall the operating system and RSA Identity Governance and Lifecycle and then restore the database from the most recent backup.
