|Applies To||RSA Product Set: Identity Governance & Lifecycle|
|Issue||The RSA Identity Governance & Lifecycle database fails to start with the following errors:|
No changes have been made to the system.
The file /u01/app/oracle/diag/crs/nlxlum062/crs/trace/ohasd_oraagent_oracle.trc referred to in the error message shows the following messages:
The Oracle alert log /u01/app/oracle/diag/rdbms/avdb/AVDB/trace/alert_AVDB.log has the following errors:
|Cause||Oracle archived redo logging is enabled and the system has run out of space for writing the archived redo logs. |
|Resolution||Please note the supported backup method for RSA Identity Governance & Lifecycle is Oracle's database export utility expdb. That is because much of the database activity is temporary and does not need to be restored. For example, during a collection run, multiple temporary tables are created where data is inserted and then deleted. It is temporary work that never needs to be recovered. Enabling archived redo logging will log all of these inserts and deletes which will slow down performance and increase disk space usage.|
The resolution in this case would be to disable archived redo logging. Please contact your DBA for assistance with this resolution.
|Workaround||If your DBA requires archive log mode to be enabled, then the problem needs to be resolved another way.|
The Oracle parameter DB_RECOVERY_FILE_DEST_SIZE is used to limit the amount of disk space used for writing archived redo logs. Running out of disk space can cause serious and unexpected consequences. This parameter helps avert that possibility by stopping the process before it actually physically fills up the disk.
One way to resolve this error is to add more disk space and then increase the size of the DB_RECOVERY_FILE_DEST_SIZE parameter to allow Oracle to use the additional disk space for logging the archived redo logs.
If you need assistance on this error, please contact your DBA.