OFSAA Concurrency of Jobs Fail when Running Via ESIC with Return Codes of 255 (Doc ID 1681783.1)

Last updated on JULY 03, 2017

Applies to:

Oracle Financial Services Funds Transfer Pricing - Version 6.0.3 and later
Oracle Financial Services Asset Liability Management - Version 6.0.3 and later
Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

OFSAA jobs fail when running via ESIC with return codes of 255.

Running both the FTP and ALM jobs concurrently. The thread count has been set at 12 and the shared memory setting has been increased from 128m to 255m. With FTP generally running 4–5 jobs at a time and ALM it is 6-8 jobs (one for a large dataset and size or so smaller dataset jobs). It is generally more stable (fewer job failures) if FTP jobs are running without any ALM jobs and becomes less stable when ALM jobs are introduced into the run. Running ALM jobs by themselves does not necessarily result in stability. Increased failures typically manifest themselves if increasing the concurrency of jobs (number of jobs running at the time) and/or increasing the thread count of the jobs. It is not always the same type of job that fails (LCR, NSTC, ESTC …).

ERROR
255,1

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms