Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Rebuilding the Lookup Cache

Rebuilding the Lookup Cache

You can instruct the Integration Service to rebuild the lookup cache if you think that the lookup source changed since the last time the Integration Service built the persistent cache.
When you rebuild a cache, the Integration Service creates new cache files, overwriting existing persistent cache files. The Integration Service writes a message to the session log when it rebuilds the cache.
You can rebuild the cache when the mapping contains one Lookup transformation or when the mapping contains Lookup transformations in multiple target load order groups that share a cache. You do not need to rebuild the cache when a dynamic lookup shares the cache with a static lookup in the same mapping.
If the Integration Service cannot reuse the cache, it either recaches the lookup from the database, or it fails the session, depending on the mapping and session properties.
The following table summarizes how the Integration Service handles persistent caching for named and unnamed caches:
Mapping or Session Changes Between Sessions
Named Cache
Unnamed Cache
Integration Service cannot locate cache files. For example, the file no longer exists or the Integration Service runs on a grid and the cache file is not available to all nodes.
Rebuilds cache.
Rebuilds cache.
Enable or disable the Enable High Precision option in session properties.
Fails session.
Rebuilds cache.
Edit the transformation in the Mapping Designer, Mapplet Designer, or Reusable Transformation Developer.1
Fails session.
Rebuilds cache.
Edit the mapping (excluding Lookup transformation).
Reuses cache.
Rebuilds cache.
Change the number of partitions in the pipeline that contains the Lookup transformation.
Fails session.
Rebuilds cache.
Change database connection or the file location used to access the lookup table.
Fails session.
Rebuilds cache.
Change the Integration Service data movement mode.
Fails session.
Rebuilds cache.
Change the sort order in Unicode mode.
Fails session.
Rebuilds cache.
Change the Integration Service code page to a compatible code page.
Reuses cache.
Reuses cache.
Change the Integration Service code page to an incompatible code page.
Fails session.
Rebuilds cache.

0 COMMENTS

We’d like to hear from you!