When using the IPM SDK to Cache Objects, All Pages of the Document are not being Cached
(Doc ID 1582074.1)
Last updated on FEBRUARY 27, 2019
Applies to:Oracle Imaging and Process Management - Version 10.1.3.6 to 10.1.3.6 [Release 10gR3]
Information in this document applies to any platform.
When using the 10.1.3.6 IPM SDK to cache objects, all pages of the document are not being cached. Legacy applications (7.6) that used the OTCONTEXTLib.CacheService CacheObject function did work correctly. However, the new version will only cache the first page of document, regardless of value for 'PageNumber'. The objects are single page Group IV TIF files. Populating the OTACORDELib.DocumentID.ProviderID and OTACORDELib.DocumentID.MimeType with the proper values -or- leaving them empty has no effect on the issue. Caching the same document via TransAct CACHE command functions properly. CacheObject CacheDuration parameter does function properly.
The applications were creating using VB6 & VS2010. The SDK apps have been run directly on IPM Storage Server and also on an IPM workstation. Both results in the same outcome.
All multi-page documents affected regardless of size (tested 2-100+ pages).
Using '0' (zero) for the PageNumber value results in all pages for a given document being cached. However, this is not suitable because if a doc spans several platters, each platter's objects will be cached. If a 100 page document has 5 pages(objects) on each of 20 platters, all 20 platters must be moved, mounted, read from, returned, etc. The goal as it worked previously) is to limit the desired cache objects by platter. Then an entire platter's side can be cached in one pass.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document