This documentation supports the 20.08 version of BMC CMDB, which is available only to BMC Helix subscribers (SaaS).

To view an earlier version, select the version from the Product version menu.

Auditing issues

If you do not see any audit history for your class definitions even though you have configured the correct audit options, verify the following points to troubleshoot the issue:

Related topics

Auditing changes to CIs

Knowledge Article 000395102 Open link (Support login ID required)

  • In Class Manager, on the Audit Information tab of a class, verify if Audit is enabled for the class and Audit Type is set to either Copy or Log .

  • In Class Manager, verify if a qualification is specified for the class. If yes, make sure that the qualification executes without errors.
  • In Class Manager, verify if Audit is enabled for the attributes and that the Audit Option set to either Audit or to Audit and Copy.
    If you encounter an error when saving an instance of the class, it means that the changes that you made to the class definitions are incorrect and auditing will not be performed for the class.
  • Log in to Remedy Developer Studio and verify if the audit form exists for the class.
    The naming convention of the form is <classFormName_AUDIT> . The audit form is created when you synchronize the class.
    For example, if Audit Type Copy is enabled for the BMC BaseElement and BMC_Person classes, the forms are generated:
    • BMC.CORE:BMC_BaseElement:AUDIT
    • BMC.CORE:BMC_Person_:AUDIT
    • BMC.CORE:BMC_Person:AUDIT
  • If Audit Type Log is enabled for a class, the log records are created in the CMDB:DefaultAuditLog form. 
  • In Remedy Developer Studio check the information in the following fields to verify any discrepancies with the audit information:
    • Audit Join Key — A GUID representing the specific audit entry.
    • Fields Changed (multiple) — A field is created for each Audit attribute and Audit and Copy attribute to specify whether that attribute value changed in the audited instance. If such an attribute changed value, its corresponding Fields Changed field in the audit form contains the value 1. If not, the field is empty. The name of each Fields Changed field is F_ fieldId _C, using the field ID of the attribute on its class form.
  • Verify audit records in CMDB:DefaultAuditLog with the GUID which is the InstanceId of the audited instance.
  • Enable API logging.
  • Examine the cmdbengdebug.log file for any errors.
    This log file is located in the <installation directory\ARSystem\Arserver\Db>.
  • In the log file, verify that a log form is specified for the class and that the audited values are saved in a Diary  field.
  • Enable Filter logging to save information about log auditing operations.
    If you enable API and SQL logging options, log files are created under 
    (Windows<installation directory\ARSystem\Arserver\Db>
    (UNIX) <serverInstallationDirectory>/db. 
    You can change their file names and location at any time.
  • If you enable auditing for an abstract class, the following error message is displayed:
    ERROR 120221: Operation not allowed. Setting audit on abstract class: class_name
    To audit the changes to an abstract class, enable audit for the immediate child class, and manually enable audit for each attribute in the abstract class. For more information, see the Knowledge Article 000412736 Open link (Support login ID required).


Was this page helpful? Yes No Submitting... Thank you

Comments