Database Administration (MOSC)

MOSC Banner

ORA-24962: Connect String Could Not Be Parsed, Error = 303

edited Feb 9, 2020 4:02AM in Database Administration (MOSC) 3 commentsAnswered

Hallo,

since we moved to 19c Database last week we observe a lot of this ORA-24962 errors in the alert log, but we are shure, that our centralised tnsnames.ora is correct. I tried the solution in Metalink Doc ID 2245576.1, but it won't help.

I observed this:

Using with TNS_ADMIN setted the centralised tnsnames.ora and connecting with sqlplus, no alert log entry is generated. As well when using TOAD.

But when we use our application (it's a Opentext Team Developer 6.3 application) each connect generates the error. So I enabled via sqlnet.ora the clientside trace facility, but within the trace, the error is not reported.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center