OFSAA Processes (ex. Allocations) Continue to Fail with ORA-01017 After Updating Sqlnet.ora for Oracle 12.2 / 19.x (Doc ID 2650284.1)

Last updated on JUNE 06, 2024

Applies to:

Symptoms

In an OFSAA environment with an Oracle 12.2 or 19.x database, when executing a Batch with Allocations, FTP Processes, or ALM Processes, all of the processes fail immediately and do not generate logs.

When you check the nohup.out in $FIC_DB_HOME/bin, the following ORA-01017 exists:

Sucssefully Connected to Config schema.
Error(Oracle Financial Services Application error) (203105) Oracle drv_oci error: 

OCI Function: [0] - olon(), orlon()
Oracle Error: [1017] - ORA-01017: invalid username/password; logon denied

Driver Function: drv_oci::Connect()

MB(AttachDB()) Error attaching to database: <atomic dbname>
FATAL : Failed Connecting to Atomic Schema.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f8528ea5661, pid=113198, tid=140209912963520
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libdbmem.so+0x33661] TTSCDBMem<CATALOG_OF_LEAVES, io_id_catlv, short>::GetPtr(int)+0x1

Since the environment uses an Oracle 12.2 / 19.x database, the DBA already updated the client and server sqlnet.ora with the following entries:

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

However, after following the instructions in Document 2412630.1 "ORA-01017 and Fatal Failed Error Connecting to Atomic Schema When Running Batches on DB 12", the error continues to occur.

Cause

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