ESIC Returns Wrong Exit Status When Process Fails in OFSAA 8.1 (Doc ID 2813988.1)

Last updated on MARCH 03, 2023

Applies to:

Symptoms

In OFSAAI 8.1, when executing ESIC batches, you can see the job is triggered in UNIX but you cannot find the batch in the OFSAA batch monitoring screen.

When checking the ESIC logs in $FIC_HOME/logs and the iccserver.log in $FIC_APP_HOME/icc/log, you find that the ESIC initialization failed and a batch was not created.  However, the ESIC command output an Exit Status = 0.  When ESIC fails, you expect to get an Exit Status = -4.  ESIC is outputting the wrong Exit Status  it fails in OFSAA 8.1.

8.1 example when there is an error:

$ ./esic -JI -U<USER> -P<ENCRYPTED PASSWORD> -R<INFODOM>_<BATCHNAME>_19991231_2 -I<INFODOM> -B<BATCHNAME> -D19991231 -F/tmp
[AESCryptorImpl.handleJVM]->INFO:JVM created successfully...
EXIT STATUS = 0

In prior versions, when there was an error, the Exit Status was 4:

$ ./esic -JI -U<USER> -P<ENCRYPTED PASSWORD> -R<INFODOM>_<BATCHNAME>_19991231_2 -I<INFODOM> -B<BATCHNAME> -D19991231 -F/tmp
[AESCryptorImpl.handleJVM]->INFO: JVM created successfully...
[LOG] Starting up.....
Host IP ...xx.xx.xx.xxx
EXIT STATUS = -4

You do not expected a failed ESIC command to return an Exit Status of 0.

Cause

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