File Based Data Management Import Process Fail For 12 Million Records
(Doc ID 2587632.1)
Last updated on MAY 25, 2021
Applies to:Oracle Enterprise Planning and Budgeting Cloud Service - Version 19.01.31 and later
Information in this document applies to any platform.
Data import from file to EPBCS Essbase application fail with error: -
2019-08-13 15:33:27,280 INFO [AIF]: Data Rows Updated by Location Mapping
'zzzzzzz_*' (LIKE): 4573944
2019-08-13 15:33:27,430 INFO [AIF]:
Processing Mappings for Column 'UD7'
2019-08-13 15:40:33,919 FATAL [AIF]: Error in
Traceback (most recent call last):
File " ", line 1611, in updateTDATASEG_T_TDATASEGW
SQLException: java.sql.SQLException: ORA-00040: active time limit exceeded - call aborted
Error is reported during various operations intermittently. E.g either while applying the data load mappings mappings or during createLogicAccounts etc.
The load file has ~1M records. Since it is a multi column load this causes it to effectively become a ~6M record load.
Also, since logic group step exist that replicates the data being loaded into the working version into the AcctSign version, effectively making this a ~12M record load.
This is also applicable for the scenario when a single direct load is performed using 12 Million or more records.
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