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

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

Environment

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

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: 

jdbc.dbalias.oracle-thin=@(description=(address=(host=FQDNorIP)(protocol=tcp)(port=1521))(connect_data=(service_name=protect))))

When it should be

jdbc.dbalias.oracle-thin=@(description=(address=(host=FQDNorIP)(protocol=tcp)(port=1521))(connect_data=(service_name=protect)))

one too many ) at the end of the string

Resolution

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