12c: Alert Log Errors: ORA-24962: Connect String Could Not Be Parsed, Error = 303
(Doc ID 2245576.1)
Last updated on MAY 29, 2024
Applies to:
Oracle Net Services - Version 12.1.0.2 to 19.5.0.0.0 [Release 12.1 to 19]Oracle Database - Enterprise Edition - Version 19.20.0.0.0 to 19.20.0.0.0 [Release 19]
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>
Release: 2.6.39-400.279.1.common.x86_64
...
Machine: x86_64
Instance name: <mysid>
Redo thread mounted by this instance: 3
Oracle process number: 81
Unix process pid: 198109, image: oracle@<mysid>
*** 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.domain>) 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 but issue is not limited to THIN only.
*** 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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |