Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 54 Oracle Analytics and AI Sharing Center
- 26 Oracle Analytics and AI Lounge
- 314 Oracle Analytics and AI News
- 58 Oracle Analytics and AI Videos
- 16.4K Oracle Analytics and AI Forums
- 6.7K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 119 Oracle Analytics and AI Trainings
- 24 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
Add BICC extract job id in MANIFEST.MF filename
When submitting multiple BICC extract offerings in parallel via the ESSWebService (submitRequest), each completed job produces a MANIFEST.MF file in UCM under the OBIAImport security group. However, there is no reliable way to associate a specific MANIFEST.MF file with its corresponding request.
Business Impact:
When building an automated data extraction pipeline that submits multiple BICC offerings concurrently. Without a reliable way to correlate the manifest file to a specific ESS request ID, we cannot:
- Verify data integrity (MD5 checksums) per run
- Ensure complete file downloads per offering
- Safely clean up UCM files after processing
Current Workaround:
We are forced to run offerings sequentially instead of in parallel, which significantly increases the total extraction time.
Refer the following thread about this issue
https://community.oracle.com/customerconnect/discussion/952861/bicc-extract-no-way-to-correlate-manifest-mf-file-to-specific-request?utm_source=community-search&utm_medium=organic-search&utm_term=manifest.mf