Allocation Fails With "Error, unable to open the security file for reading the config db password" After Configuring Oracle Wallet
(Doc ID 3046605.1)
Last updated on OCTOBER 10, 2024
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.1.0.0.0 and laterOracle Financial Services Profitability Management - Version 8.1.0.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Symptoms
After configuring the Oracle Wallet, when you try to run an Allocation, you get the following error in the nohup.out in $FIC_DB_HOME/bin or when running it command line:
./ofspa: line 30: 1296297: Abort(coredump)
Connecting to Host
Warning: iso88951 does not exist.
Connecting to Host
Picked up JAVA_TOOL_OPTIONS: -Djdk.util.zip.disableZip64ExtraFieldValidation=true
[AESCryptorImpl.handleJVM]->INFO:JVM created successfully...
ClsUSmsConnect::ClsUSmsConnect, Forming Login Info statement
ClsUSmsConnect::setFICPASSWORD(), Error, unable to open the security file for reading the config db password
ClsUSmsConnect :: FILEOPENING, Error, unable to open the security file for fetching the config DB password
ClsUSmsConnect::ClsUSmsConnect, Error, unable to retrive login information: 5
Sucssefully Connected to Config schema.
Error(Oracle Financial Services Application error) (203105) Oracle drv_oci error:
OCI Error: 12545
ORA-12545: Connect failed because target host or object does not exist
FAILED: create_oci_session() - error attaching to server using OCIServerAttach()...
FAILED: drv_oci8::Connect - create_oci_session() returned unsuccessfull...
MB(AttachDB()) Error attaching to database:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fa1b2ee0390, pid=1298099, tid=1298099
#
# JRE version: Java(TM) SE Runtime Environment 18.9 (11.0.18+9) (build 11.0.18+9-LTS-195)
# Java VM: Java HotSpot(TM) 64-Bit Server VM 18.9 (11.0.18+9-LTS-195, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libaccess.so+0x23390] session::GetProcess(int)+0x20
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e" (or dumping to /
u01/ofsa/ofsaai/ficdb/bin/pft/core.1298099)
#
# An error report file with more information is saved as:
# /u01/ofsa/ofsaai/ficdb/bin/pft/hs_err_pid1298099.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
./ofspa: line 30: 1298099: Abort(coredump)
As a result, users cannot run Allocations.
Cause
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
Symptoms |
Cause |
Solution |
References |