My Oracle Support Banner

A Custom Concurrent Request Is Failing With Emsg:was Terminated By Signal 6 (Doc ID 3011852.1)

Last updated on MARCH 27, 2024

Applies to:

Oracle Concurrent Processing - Version 12.2.9 and later
Information in this document applies to any platform.


Customer migrated EBS instance to OCI with Exadata.

But one concurrent program is failing on the migrated instance with following errors where it is working on source instance.
Customer tried to generate the session trace but the trace file was not created.

stat_low = 86
stat_high = 0
emsg:was terminated by signal 6
Enter Password:
REP-0004: Warning: Unable to open user preference file.
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0xfad3dea4, pid=18632, tid=13
# JRE version: Java(TM) SE Runtime Environment (7.0_85-b33) (build 1.7.0_85-b33)
# Java VM: Java HotSpot(TM) Client VM (24.85-b07 mixed mode solaris-sparc )
# Problematic frame:
# C [] caupzsearch+0x4
# Core dump written. Default location: $NE_BASE/ inst/<CONTEXT_NAME>/logs/appl/conc/log/core or core.18632
# An error report file with more information is saved as:
# $NE_BASE/ inst/<CONTEXT_NAME>/logs/appl/conc/log/hs_err_pid18632.log
# If you would like to submit a bug report, please visit:
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Report Builder: Release - Production on Mon Mar 4 14:36:17 2024

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Program was terminated by signal 6


 EBS instance was migrated to OCI with Exadata.


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

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