000031637 - VIA L&G: How to monitor your ACM database and why it matters

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000031637
Applies ToRSA Product Set: Identity Management and Governance
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.x,7.x
Product Name: RSA-0018000
Product Description: Access Certification Manager
IssueDatabase issues often go undetected until a failure occurs, or an upgrade fails due to ignored Oracle ACM database errors.
This must and can be prevented.


Here are some reasons why you should monitor your Oracle ACM database and how:

1) Corruption.  

Corruption can be logical or physical.  For logical, one can't do much before it happens, for physical corruption, you should monitor the physical server that hosts the database.

2) Space issues in the database.

Your data volume grows, or the database needs large temporary space for specific statements,  the database might run out of space in a tablespace.  This will lead to either failure in work items in the database, or to a complete standstill of the database.

3) Other Oracle errors.

Like any software product, the ACM database might run into an Oracle issue that may or may not affect your database health. ANY ERROR MESSAGE in the database alert.log should be examined for its importance.

4) OS errors.

The Operating system will also alert to problems, which may in the end affect the health of your database.

How to monitor the database:

Oracle Enterprise Manager Database Control.

The Hardware Appliance, and the Software Appliance with local database are installed with the Oracle Enterprise Manager Database Console.
DBConsole is a light weight monitoring tool that comes with every Oracle database. It monitors just one database.  Your organization might have more Oracle databases, and the Database Administrator team might have the more extensive Enterprise Manager Cloud Control, into which your ACM database could be integrated for monitoring.
The console is automatically started with ACM, and is available at this url:  https://<acm-server>:1158/em/console
In the following example, you see in yellow the places where you would see errors and alerts show up.
Example of a DBConsole page
You can also specify to receive email notifications. Refer to the Oracle documentation here on how to set these up.

Database Alert Log

The database alert log can be physically found at the location indicated by this query:
oracle@acm-691:~> sqlplus / as sysdba
SQL*Plus: Release Production on Fri Oct 30 17:24:00 2015
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Release - 64bit Production
With the Automatic Storage Management option
SQL> show parameter background_dump
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
background_dump_dest                 string      /u01/app/oracle/diag/rdbms/avdb/AVDB/trace                                               b/AVDB/trace

It will show any errors that happen on the database, and each one should be carefully examined to determine if they can be ignored or measures should be taken to correct the issue.

Operating System Log

The Operating System Log for Hardware and Software Appliances is /var/log/messages
It will indicate any Hardware or OS issues. These should be carefully examined and mediated if necessary.  Special attention should be paid to any disk related error messages.  Disks are smart and can relocate bad blocks, however, a growing number of disk errors would be a good indication to have the disk swapped, if further diagnostics confirm a Hardware issue.


Any error in the database alert.log or the Operating System log should be detected in real time and reacted upon to prevent an outage to the ACM database.