ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
AW_AUDIT_REPORTS_TABLE stores invalid USER_NAME
Article ID: 88176
CA Automic Applications Manager (AM)
Error Message : N/A
AW_AUDIT_REPORTS_TABLE shows a different scheduled Job's User_Name. The column is showing a user, instead of the JDBC Thin Client which is what should be displayed.
When making an edit to a Job's schedule which qualifies to be recorded by the AW_AUDIT_REPORTS_TABLE, a different scheduled Job's User_Name column is showing a user, instead of JDBC Thin Client when the next run date is being updated.
This screenshot shows SQLOPER as the USER_NAME where is should be OSU=qa4 JDBC Thin Client.
<Please see attached file for image>
Cause type: Defect Root Cause: AM user is being written to the Audit table, the cleanup for the login username is missing.
OS Version: N/A
Update to a fix version listed below or a newer version if available as the missing cleanup for the login username was added and now auditing displays the correct user.
Fix Status: Released
Fix Version(s): Applications Manager 9.2.0 - Available