|Applies To||RSA Identity and Governance|
database logs, db logs, logs, artifacts, artifact, db, database, log, logs, diagnosis, diagnostics
|Issue||KB-1652 How to Access IMg (ACM, Aveksa) Job Run database Logs|
RSA Technical Support has requested a copy of the database logs for diagnosis of a support issue involving a application job, most commonly a collection. The 'database logs' referenced here are not the Oracle Database logs (aka the Oracle alert_AVDB.log, the alert_+ASM.log, etc), but instead are the logs associated with a particular job run as seen from the IMG (ACM or Aveksa) Monitoring page.
This page is accessed by logging into the application UI as an admin user and following the path of Admin->Monitoring, and then selecting a specific job that needs further review or analysis.
These job run database logs are a common diagnostic artifact that RSA (aka Aveksa) Technical Support may request during a support case. Database logs provide information regarding application jobs' database activity and/or errors.
|Resolution||There are three different ways to acquire database logs. Which one is appropriate depends on if the UI is accessible or not and is typically based off of the specific diagnostic situation. |
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 log should be collected from the Monitoring job run page.
Log into ACM as an administrator, and navigate to Admin->Monitoring. On the monitoring page, find the run that is associated with the issue, and click on the number for that run. In the first set of information presented on this page, on the right column there will an 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 Data button (looks like a blue floppy disk) in the top right corner. Note: On several versions the save icon is embedded in the table options.
Once the Monitoring page is accessed, a specific job is selected. In this example, we're investigating Run 68, an Entitlement Data Collection.
Accessing the details of Run#68, shows the very specific details about that job.
Also seen on this screen are links to access the 'database logs' for run 68.
The application job 'database logs' are always specific to a unique job run id #, and list the complete database activity for that job.
The are typically more than one page associcated with a job run, as shown in this screen shot:
The data displayed on this page are in reverse order, by default. This means that the last operation is shown at the top of the list on the first page displayed.
Database logs not associated with a job run
In the event that Support requests database logs that are not associated with a job on the monitoring page, they can be acquired elsewhere. Log into IMG (ACM) as an administrator, and navigate to Admin->System->Diagnostics. There will be a link to open the full database logs under the second header. Save the logs by clicking the Save Data button (looks like a blue floppy disk) in the top right corner.
UI is unavailable
In the event that the UI is not available, database logs can be collected from the database. The database log is stored in the table t_av_job_stats. The sql queries noted below should be executed as the application user avuser.
To get the log from a certain run, include a where statement on the column AV_RUN_ID. The below example will return the database logs for run #68:
select * from t_av_job_stats where AV_RUN_ID ='68' 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 UI when accessing the job run database logs from the System->Diagnostic page:
select * from t_av_job_stats order by JOB# desc;
Note: The data returned by these queries can be quite large. It is sometimes easier to access this data using GUI SQL tool (such as sqldeveloper, toad, squirrel to name a few) to acquire any database logs directly from the application database. The data returned can be difficult to read from the OS command line SQL tool.
|Legacy Article ID||a66682|