Migrated Allocation Rule Fails With [libstdc++.so.6+0xbf00c]
(Doc ID 2746134.1)
Last updated on JANUARY 29, 2021
Applies to:Oracle Financial Services Profitability Management - Version 8.0.7 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Enterprise Performance Management (EPM)
Migrated Allocation Rule fails with core dump. When checking the rule on the Allocation Definition window, found a user defined dimension is reset to ALL instead of a specific Leaf value.
After updating the allocation with the correct leaf and re-execute the allocation, it fails with error below.
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00007f89bf48b00c, pid=121862, tid=0x00007f89c28f11c0
# JRE version: Java(TM) SE Runtime Environment (8.0_221-b11) (build 1.8.0_221-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.221-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libstdc++.so.6+0xbf00c] std::string::assign(std::string const&)+0x2c
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
Aborted (core dumped)
Steps to Replicate:
1. Migrate Allocation Rules from Source to Target successfully without any error.
2. Post successful import, execute the Allocation Rule to check the successful migration, which got executed successfully.
3. Edit the Allocation Rule and found a user defined dimension selection is reset from a Leaf to ALL.
4. Correct the dimension to a correct leaf and save.
5. Execute the updated Allocation Rule and it failed with the above.
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