ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

ORA-24962: connect string could not be parsed, error = 303 in database alert log on the Symantec Data Loss Prevention Oracle server

book

Article ID: 213630

calendar_today

Updated On:

Products

Data Loss Protection Oracle Standard Edition Data Loss Prevention

Issue/Introduction

The client has noticed the error ORA-24962: connect string could not be parsed, error = 303 in database alert log

Cause

ORA-24962 means Connect string could not be parsed, there is a syntax error in the connect string.

Commonly when this error is prevalent we see in the jdbc.properties file: 

[email protected](description=(address=(host=FQDNorIP)(protocol=tcp)(port=1521))(connect_data=(service_name=protect))))

When it should be

[email protected](description=(address=(host=FQDNorIP)(protocol=tcp)(port=1521))(connect_data=(service_name=protect)))

one too many ) at the end of the string

Environment

This was found in 15.1 but could potentially happen in any version

Resolution

Remove the extra ) and restart services in the correct order.