Static Table Driver Allocations Fail With SIGSEGV Error on libstdc++.so.6.0.21 (Doc ID 2827066.1)

Last updated on MAY 06, 2023

Applies to:

Symptoms

All Static Table Driver Allocations fail when executed. When reviewing the Allocation Engine log, the log ends with multiple queries against OFSA_CATALOG_OF_LEAVES:

Module Logging OFS Access module data: SELECT
SELECT LEAF_NUM_ID, LEAF_FIELD
FROM OFSA_CATALOG_OF_LEAVES

Module Logging OFS Access module data: SELECT
SELECT LEAF_NUM_ID, LEAF_FIELD
FROM OFSA_CATALOG_OF_LEAVES

Module Logging OFS Access module data: SELECT
SELECT LEAF_NUM_ID, LEAF_FIELD
FROM OFSA_CATALOG_OF_LEAVES

There is nothing after these queries.

Additionally, when checking the nohup.out in $FIC_DB_HOME/bin, the following error exists:

Running allocations with: 217192, 0, <USER>, 20200901, 0.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xfffffffd11cdb244, pid=5143, tid=0x0000000000000001
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode solaris-sparc compressed oops)
# Problematic frame:
# C [libstdc++.so.6.0.21+0xdb244] std::basic_string<char, std::char_traits<char>, std::allocator<char> >::assign(const std::basic_string<char, std::char_traits<char>, std::allocator<char> >&)+0x2c

Note: Other Allocation types run successfully.

Cause

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