ESIC Batch Initialization Fails with 'Database Error or Invalid Batch Name' and EXIT STATUS = -4 (Doc ID 1629090.1)

Last updated on MARCH 03, 2023

Applies to:

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA), you get an error when trying to initialize a batch using the ESIC (External Scheduler Interface Component) command.  When running the command from $FIC_APP_HOME/icc/bin, you get the following message:

esic -JI -UUSER1 -Pxxxxxxxxxxxxxxx -RINFODOM73_Esic_Test_20131031_2 -IINFODOM73 -BINFODOM73_Esic_Test -D20131031 -F/tmp

[AESCryptorImpl.handleJVM]->INFO: JVM created successfully...
[LOG] Starting up.....
Host IP ...xx.xx.xx.xxx
EXIT STATUS = -4

The esic log file in $FIC_APP_HOME/icc/log contains the following:

INFORM::clsCommandLine::CallIntialize::Infodom
INFODOM73
INFORM::clsIccInterface::CallIccAPI::Message to be sent :
INFO::SocketClientImpl::Read : More than Zero bytes
00000116
INFO::SocketClientImpl::Read : More than Zero bytes
##ICC##I##-1##-28##Database error or Invalid batch name. Unable to initialize batch run for uid: INFODOM73_Esic_Test##
INFORM::clsIccInterface::ProcessReturnDataMessage received from ICC
##ICC##I##-1##-28##Database error or Invalid batch name. Unable to initialize batch run for uid: INFODOM73_Esic_Test##

A similar error is in the iccserver.log in the same directory:

[16:25:10,458] - Batch Name: INFODOM73_Esic_Test
[16:25:10,458] - Infodate: 20131031
[16:25:10,458] - Temp Path: /tmp
[16:25:10,458] - Executing request through handler.
[16:25:10,458] - Fetching batchrun object
[16:25:10,458] - Executing query to get batchrun object: SELECT a.v_task_id, a.v_task_description, a.v_component_id, b.v_parameter_name, b.v_parameter_value, b.i_parameter_order, c.v_parent_task_id FROM batch_task_master a, batch_parameter_master b, batch_task_precedence_master c WHERE a.v_batch_id = ? AND b.v_batch_id = ? AND b.v_task_id = a.v_task_id AND c.v_batch_id = ? AND c.v_task_id = a.v_task_id
[16:25:10,459] - Error. zero rows received.
[16:25:10,459] - Database error or Invalid batch name. Unable to initialize batch run for uid: INFODOM73_Esic_Test
[16:25:10,459] - Writing to native socket: ##ICC##I##-1##-28##Database error or Invalid batch name. Unable to initialize batch run for uid: INFODOM73_Esic_Test## with padding
[16:25:10,460] - Error writing to client.
java.net.SocketException: Socket is closed

If you run the SQL listed in the iccserver.log using the Batch Name value (ex. INFODOM73_Esic_Test), the query returns rows successfully.

This issue prevents you from initializing and running batches using ESIC.

Cause

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