ODI Integration Interface That Loads Data Into Essbase Aborts On Error While MAXIMUM_ALLOWED_ERRORS IS SET TO 0
(Doc ID 817064.1)
Last updated on JUNE 16, 2022
Applies to:Oracle Data Integrator - Version 10.1.3.4.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.
An Interface is set up to load a text file's data to Essbase using LKM File to SQL and IKM SQL to Essbase (Data). When Rules_File option is used, the Interface seems to abort as soon as it hits the first error from the file though MAXIMUM_ALLOWED_ERRORS is set to 0 which should ignore the errors and continue on and finish the load. (This is working as expected when not using Rules_File option. )
Also only the one error hit is logged in the log file, the rest of the errors are skipped.
In ODI operator report statistics step, the number of rows successfully processed will usually be greater than 1 while Essbase Application log shows no file is loaded.
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