Job run database logs are a common diagnostic artifact that RSA Identity Governance & Lifecycle Technical Support may request when diagnosing application job issues, most commonly collections. Job run database logs provide information regarding application jobs' database activity and/or errors.
The database logs referenced here are not the Oracle Database logs (also knwn as the Oracle alert_AVDB.log, the alert_+ASM.log, etc), but instead, are the logs associated with a particular job Run as seen in the RSA Identity Governance & Lifecycle User Interface Monitoring Page.
This page is accessed by logging into the application User Interface as an admin user, going to Admin > Monitoring > Data Runs tab and then selecting a specific job that needs further review or analysis.
There are three different ways to acquire database logs. Which one is appropriate depends on if the RSA Identity Governance & Lifecycle User Interface is accessible or not and is typically based off of the specific diagnostic situation.
1. Database logs from a job run
This is the most common situation in which database logs will be collected. A job run failed or completed with unexpected results. Example job runs include Data Collection, Unification, Change Verification, etc. In this situation, the database logs should be collected from the Monitoring job run page.
Log into RSA Identity Governance & Lifecycle as an administrator.
Navigate to Admin > Monitoring.
On the monitoring page, find the run ID that is associated with the issue, and click on the number for that run. In the right column there will a link for Database Logs for Run #.
Click on the link to bring up the database logs for the Run.
Save the logs by clicking the Save tab under Table Options in the top right corner.
The application job database logs are always specific to a unique job Run ID #, and list the complete database activity for that job.
There is typically more than one page associated with a job run, as shown in the above screen shot.
The data displayed on this page is in reverse order by default. This means that the last operation is shown at the top of the list on the first page displayed.
2. Database logs not associated with a job run
In the event that RSA Support requests database logs that are not associated with a job on the monitoring page, they can be acquired elsewhere.
Log into RSA Identity Governance & Lifecycle as an administrator, and navigate to Admin > System > Diagnostics tab.
There will be a link to open the full database logs under the second header.
Save the logs by clicking the Save tab under Table Options.
3. User Interface is unavailable
In the event that the User Interface is not available, database logs can be collected from the database. The database log is stored in table T_AV_JOB_STATS. The SQL queries noted below should be executed as avuser.
To get the log from a certain run, include a where statement on column AV_RUN_ID with the Run ID #. The below example will return the database logs for run #306:
SELECT * FROM t_av_job_stats WHERE AV_RUN_ID ='306' ORDER BY JOB# DESC;
Although not as commonly requested, the following SQL will extract the entire database log sorted as it would be seen in the User Interface when accessing the job run database logs from the Admin > System > Diagnostics page:
SELECT * FROM T_AV_JOB_STATS ORDER BY JOB# DESC;
The data returned by these queries can be quite large and difficult to read when using the operating system command line SQL tool. It is sometimes easier to acquire any database logs directly from the application database. using a GUI SQL tool (such as SQL Developer, toad, and squirrel to name a few) to acquire any database logs directly from the application database.