cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect to Oracle 19c on STIG environment with Crystal Reports Java Runtime

dfarina
Explorer
0 Kudos
388

I'm having an issue connecting to Oracle 19c on a STIG environment. OS is Redhat. The software generally works on non-STIG'ed systems, so STIG bring the problem is just an assumption so far.

The application calling the Crystal Report Java Runtime (12.2.225) successfully obtains it's own connection to the database, but the runtime is unable to get it's own connection with the PropertyBag handoff. The PropertyBag given is:

{Trusted Connection=true, Database DLL=crdb_jdbc.dll, Connection URL=!oracle.jdbc.OracleDriver!jdbc:oracle:thin:@tnsname, Database Class Name=oracle.jdbc.OracleDriver, Server Type=JDBC, Use JDBC=true}

When attempting to create the connection, we get the following error:

com.businessobjects.reports.sdk.JRCCommunicationAdapter - detected an exception: Logon Error: IO Error: could not resolve the connect identifier "\#@tnsname" (CONNECTION_ID=2T5ufScBRb+DrAgCVGPmAg==)

I am concerned with why the tnsname comes back with a "#" inserted, but I don't know if this is the problem.

The calling application uses the same connect string (jdbc:oracle:thin:@tnsname) and is able to connect without issues. When running the application, we are passing the argument to the JVM:

-Doracle.net.tns_admin=/path/to/tnsnames

We also get very similar behavior if we don't use TNS at all and pass the host/port/sid.

Any thoughts appreciated!

DellSC
Active Contributor
0 Kudos

I changed the primary tag on your question to "SAP Crystal Reports, version for Eclipse", which the the tag for questions about Crystal's Java SDK. The "SAP Crystal Reports" tag is for questions about report design and the SDK tag that you used is old and not specific enough.

Accepted Solutions (0)

Answers (1)

Answers (1)

dfarina
Explorer
0 Kudos

Found that this error was caused by having @ and/or # in the password. Recommend a patch to properly escape these characters in the password if possible.

dfarina
Explorer
0 Kudos

Retract my comment about escaping characters in the Oracle connect string, it appears there is no supported escape sequence. The patch would have to change the construction of the connect string to not include the username and password, and find an alternative to passing that information.

In any case, just don't have those characters in your password.