OBIA 7964 'SIGSEGV (11) Error Message is Received During an ETL Failure Because the 'max_thread_proc' Parameter is set too Low
Last updated on JANUARY 31, 2017
Applies to:Business Intelligence Applications Consumer - Version 184.108.40.206 and later
Information in this document applies to any platform.
When running a BI Apps 220.127.116.11 Full Load for 'Finance_Procurement_Project: R1213' Execution Plan, some jobs failed with below error:
Increasing [Index Cache] size for transformation [MPLT_xxxxxxxxx.LKP_xxxxxxxx] from  to 
Failed to create thread due to operating system error [Resource temporarily unavailable].
*****FATAL ERROR : Caught a fatal signal or exception.******
*****FATAL ERROR : Aborting the DTM process due to fatal signal or exception.******
*****FATAL ERROR : Signal Received: SIGSEGV (11)******
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