BatchLoader utility run From Shared Location Is Not Updating Custom Siebel Entity Field Metadata Value
(Doc ID 2717385.1)
Last updated on OCTOBER 06, 2020
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
We have to do legacy content migration in WCC system and during POC found some different behavior of BatchLoader utility.
If I'm running the BatchLoader utility from shared path it's not updating the siebel custom entity field metadata value in wcc system while if I'm running the same Batchloader utility from individual node it will update the siebel entity field metadata value.
Kindly suggest whether it's a normal behavior as I'm bit curious about node load/performance impact during content migration.
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