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

Blaze Engine Logs

Blaze Engine Logs

You can find information about the mapping run on the Blaze engine in the LDTM log file.
The LDTM logs the results of the mapping run on the Blaze engine. You can view the LDTM log from the Developer tool or the Monitoring tool for a mapping job.
You can configure the Data Integration Service to log details about the mapping execution to the session log. To enable logging of LDTM mapping execution details, set the log tracing level to verbose initialization or verbose data. For optimal logging performance, avoid setting the tracing level to verbose data. You can set the tracing level to verbose data if you need to debug a mapping run.
Logical mapping execution details include the following information:
  • Start time, end time, and state of each task
  • Blaze Job Monitor URL
  • Number of total, succeeded, and failed/cancelled tasklets
  • Number of processed and rejected rows for sources and targets
  • Data errors, if any, for transformations in each executed segment
  • Number of healthy cluster nodes used by the Grid Manager
The mapping execution details include information about the Blaze engine run-time processing, such as the partition count for each executed segment.

0 COMMENTS

We’d like to hear from you!