AW_AUDIT_REPORTS_TABLE stores invalid USER_NAME

Document ID : KB000088176
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
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.

Investigation

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.
0EMb0000001QoiW.png
Environment:
OS Version: N/A
Cause:
Cause type:
Defect
Root Cause: AM user is being written to the Audit table, the cleanup for the login username is missing.
Resolution:
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
Additional Information:
Workaround :
N/A