Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Content Management Service
  4. Data Integration Service
  5. Data Integration Service Architecture
  6. Data Integration Service Management
  7. Data Integration Service Grid
  8. Data Integration Service Applications
  9. Mass Ingestion Service
  10. Metadata Access Service
  11. Metadata Manager Service
  12. Model Repository Service
  13. PowerCenter Integration Service
  14. PowerCenter Integration Service Architecture
  15. High Availability for the PowerCenter Integration Service
  16. PowerCenter Repository Service
  17. PowerCenter Repository Management
  18. PowerExchange Listener Service
  19. PowerExchange Logger Service
  20. SAP BW Service
  21. Search Service
  22. System Services
  23. Test Data Manager Service
  24. Test Data Warehouse Service
  25. Web Services Hub
  26. Application Service Upgrade
  27. Application Service Databases
  28. Connecting to Databases from Windows
  29. Connecting to Databases from UNIX
  30. Updating the DynamicSections Parameter of a DB2 Database

Logical Data Object/Virtual Table Cache Properties

Logical Data Object/Virtual Table Cache Properties

The following table describes the data object and virtual table cache properties:
Property
Description
Cache Removal Time
The number of milliseconds that the Data Integration Service waits before cleaning up cache storage after a refresh. Default is 3,600,000.
Cache Connection
The database connection name for the database that stores the data object cache. Select a valid connection object name.
Maximum Concurrent Refresh Requests
Maximum number of cache refreshes that can occur at the same time. Limit the concurrent cache refreshes to maintain system resources.
Enable Nested LDO Cache
Indicates that the Data Integration Service can use cache data for a logical data object used as a source or a lookup in another logical data object during a cache refresh. If false, the Data Integration Service accesses the source resources even if you enabled caching for the logical data object used as a source or a lookup.
For example, logical data object LDO3 joins data from logical data objects LDO1 and LDO2. A developer creates a mapping that uses LDO3 as the input and includes the mapping in an application. You enable caching for LDO1, LDO2, and LDO3. If you enable nested logical data object caching, the Data Integration Service uses cache data for LDO1 and LDO2 when it refreshes the cache table for LDO3. If you do not enable nested logical data object caching, the Data Integration Service accesses the source resources for LDO1 and LDO2 when it refreshes the cache table for LDO3.
Default is False.

0 COMMENTS

We’d like to hear from you!