My Oracle Support Banner

Data Transformation (DT) Tasks Fail With "java.sql.SQLException: Invalid column index" Error After OFSAAI Upgrade to 8.0.7.4 (Doc ID 2929737.1)

Last updated on JULY 29, 2024

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.7.4.0 to 8.0.7.7.0 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Data Transformation (DT)
Post Load Changes (PLC)

Symptoms

After OFSAAI upgrade to 8.0.7.4, "Invalid column index" error is received while executing Data Transformation (DT) tasks.

 

ERROR

Batch Param 1 : INFODOM_<NAME>_20221231_6
Batch Param 2 : 20221231
Runtime Param 3 :
Error executing Pre-Loading steps
java.sql.SQLException: Invalid column index

 

The failing DT used to expect two parameters only: Batch ID and MIS DATE. If user provides an additional parameter during batch execution, the DT executes successfully.

As per DT log from before upgrading to 8.0.7.4:

[05-10-22 07:02:04,605 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Run time parameters :,
[05-10-22 07:02:04,606 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Executing function :{ ? = call <function_name>(?,?) }, with...
[05-10-22 07:02:04,616 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Batch Param 1 : INFODOM_<NAME>_20221231_1
[05-10-22 07:02:04,617 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Batch Param 2 : 20221231
[05-10-22 07:02:04,690 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Function call returned : 1
[05-10-22 07:02:04,690 GMT AM] [INFO ] [BACKEND] [SYSADMN] [DMT] [PLCFunctionExecutorDAO]~[executeLoading]~Function executed successfully



Both Out Of The Box (OOTB) and custom functions executed through DT are failing.

Also, functions execute properly when triggered from back-end via sqlplus.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.