My Oracle Support Banner

12c: Alert Log Errors: ORA-24962: Connect String Could Not Be Parsed, Error = 303 (Doc ID 2245576.1)

Last updated on JULY 10, 2018

Applies to:

Oracle Net Services - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

Symptoms

There are incident traces at the database server where the following error is being reported:

Node name: myhostname.mydomain.com
Release: 2.6.39-400.279.1.common.x86_64
Version: #1 SMP Mon May 23 13:39:48 PDT 2016
Machine: x86_64
Storage: Exadata
Instance name: mysid
Redo thread mounted by this instance: 3
Oracle process number: 81
Unix process pid: 198109, image: oracle@mysid.world

 
*** 2017-03-03 15:37:55.840
*** SESSION ID:(404.59753) 2017-03-03 15:37:55.840
*** CLIENT ID:() 2017-03-03 15:37:55.840
*** SERVICE NAME:(mysid.world) 2017-03-03 15:37:55.840
*** MODULE NAME:(JDBC Thin Client) 2017-03-03 15:37:55.840  <==JDBC thin client in this case.  Issue is not limited to THIN
*** CLIENT DRIVER:(jdbcthin) 2017-03-03 15:37:55.840
*** ACTION NAME:() 2017-03-03 15:37:55.840

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

Changes

 This is likely a new installation or a recent upgrade to 12c database.  This issue seems to be new to the version 12 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!


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