|Applies To||RSA Product Set: RSA Identity Governance & Lifecycle|
RSA Product/Service Type: Appliance
RSA Version/Condition: 7.0.1 and above
|Issue||A Data Collection fails, where an examination of the aveksaServer.log shows the following error.|
As this error relates to the Oracle database, the Alert log for the Oracle database needs to be examined.
Around the same time the error is reported in the aveksaServer.log, there should also be a trace file generated for an Oracle Parallel process.
If we examine the Oracle Parallel process trace file, we can confirm that the errors that caused the process to fail.
Finally, as this error also involves the "ASMLIB", the Alert log for the Oracle ASM instance can also be examined.
So, around the same time the error is reported in the Alert log, the +ASM instance may report the following.
|Cause||A problem has occurred when writing to the Oracle database files, that are serviced by the Oracle ASM Storage Manager.|
If no specific Operating System or disk errors are reported, then the problem is likely to be caused by an underlying hardware problem, or if on a Virtual Machine, the disk emulation.
In some cases, no O/S error is reported because the problem is with the Linux software causing a hardware hang (for example Oracle Linux orabug 20561622).
If the problem is related to hardware, then one of more of the following messages may also appear in the Oracle database Alert log.
Finally, the errors can also be caused if access to the disks managed by Oracle ASM have the wrong permissions.
If this is the case, then the following errors may also be reported.
If you are running an RSA Appliance, please engage RSA Customer Support for further assistance, as the hard disk may need to be replaced.
If you are not running an RSA Appliance, please engage your local Linux System Administrator, to perform a hard disk review and replacement.
If the problem is permissions, then please check that the Oracle ASM disk used by RSA Identity Governance and Lifecycle has the correct permissions.
|Workaround||Re-start the whole Linux server, to see if the hardware failure is only temporary.|
You may want to gracefully bring down RSA Identity Governance and Lifecycle, first.