My Oracle Support Banner

12c alert log ORA-24962: Connect String Could Not Be Parsed, after upgraded the source database to 18C . (Doc ID 2543882.1)

Last updated on APRIL 17, 2023

Applies to:

Oracle Net Services - Version 18.1.0.0.0 to 18.3.0.0.0 [Release 18.1]
Information in this document applies to any platform.

Symptoms

Database link created from 18C to 12C and observed the below errors in 12C alert.log whenever dblink is using .

ORA-24962: connect string could not be parsed, error = 303
oracle@xxxxxx:/var/tmp/TSY#cat xxxxx_ora_120352.trc
Trace file /xxxxx/xxxx/oracle/diag/rdbms/xxxxx/xxxxx/trace/xxxx_ora_120352.trc
Oracle Database 12c Enterprise XXXX Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
ORACLE_HOME = /xxxxx/xx/oracle/product/12.1
System name: Linux
Node name: xxxxxxxx
Release: 3.10.0-862.3.3.el7.x86_64
Version: #1 SMP Wed Jun 13 05:44:23 EDT 2018
Machine: x86_64
Instance name: xxxxxxx
Redo thread mounted by this instance: 1
Oracle process number: 374
Unix process pid: 120352, image: oracle@xxxxxx


*** 2019-04-03 13:08:41.307
*** SESSION ID:(913.60414) 2019-04-03 13:08:41.307
*** CLIENT ID:() 2019-04-03 13:08:41.307
*** SERVICE NAME:(xxxxxx) 2019-04-03 13:08:41.307
*** MODULE NAME:(oracle@xxxxx (TNS V1-V3)) 2019-04-03 13:08:41.307
*** CLIENT DRIVER:() 2019-04-03 13:08:41.307
*** ACTION NAME:() 2019-04-03 13:08:41.307

ORA-24962: connect string could not be parsed, error = 303

Changes

This issue seems to be new to the version 18C database.

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
Changes
Cause
Solution
References


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