Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Rules and Guidelines for Audits

Rules and Guidelines for Audits

Consider the following rules and guidelines when you configure an audit for a mapping:
  • You cannot configure an audit for an optimized mapping.
  • If you create an audit rule for a Write transformation that is created from an existing transformation, the ports of the Write transformation must be linked by name.
  • If you use a mapplet for the source or target in a mapping, you cannot select the mapplet as the transformation for an audit rule.
  • You cannot configure audit rules for a flat file target that has a footer command.
  • If you define an audit rule for a Write transformation that creates a target data object at run time and you set the
    Execution Override
    to
    Pre Mapping
    , the audit fails the first time the mapping runs. On subsequent runs, the audit results are calculated.
  • You cannot run a mapping with an audit when you configure the Data Integration Service to use operating system profiles.
  • If you configure JDBC connection storage and the resource table schema is not correct, the mapping and audit run, but the Data Integration Service does not write the results to the table. The audit logs contain the following error message:
    SEVERE: [WRT_8425] ERROR: Writer execution failed.