It's all about the answers!

Ask a question

When trying to run setup I am getting errors on connecting to the database - how do I troubleshoot this?

Michael Johnson (44318) | asked Jul 11 '17, 7:35 a.m.

I am getting the following error when trying to connect to the database:

"The server was unable to connect to the database because the database connection settings are invalid or because the database is unreachable.(SQLSTATE 08006, SQLCODE 17002).  Verify the connection settings in the file.....ID CRJAZ2654E

This is a Windows 2012 r2 Server running WAS connecting to Oracle on Redhat 6.8

Ping works,  Firewall is off,

I am getting an SSL handshake error in the JTS log.  I tried changing the protocol on WAS from SSL_TLS to SSL_TLSv2 with no luck. 

Thank you for your help


3 answers

permanent link
Grazielle Codogno (1536) | answered Jul 11 '17, 10:25 a.m.
edited Jul 11 '17, 10:29 a.m.
Hi Michael 

There's few reasons that might cause this error.
One of them is the configuration to reach the database isn't    correct configured. 
It can be reviewed in the
Another commom reason in Oracle databases, is the listener not able to be reached. 
You might also verify the listener and try to tnsping the database alias. Check this :
It might have some helpful information

permanent link
Donald Nong (14.5k414) | answered Jul 12 '17, 4:18 a.m.

You may have two issues there, depending on the SSL error is related to Oracle or not.

Check jts.log and ccm.log files, locate the message containing "SQLSTATE 08006, SQLCODE 17002", then go to the bottom of the stack trace and the last "Caused by" should give you some hints about what went wrong.

Only if the Oracle server is SSL enabled (usually it's not unless you have a strong reason to do so), the SSL handshake error should be taken into account for database connection issue.

The SSL setting in WAS affects the (incoming) connection from its clients (browsers and spawned threads). The DB connection is outgoing from WAS' point of view so it is not affected.

You need to look into the details of the SSL handshake error to figure out which application JTS was trying to connect when it failed.

permanent link
Michael Johnson (44318) | answered Jul 12 '17, 6:53 a.m.

The solution turns out to be a bit easier than expected. 

After we shut down iptables (Redhat firewall) for both ipv4 and ipv6 everything started working just fine. 

Note to all....The error logs showing the SSL protocol errors led us down the wrong path for a long time.  Had lots of people scratching their head over that one. 

The key was one individual that just happened to do a telnet to the ip and port.  This failed.  We had performed multiple pings and got back good connection signal, but it was the telnet that told us that the port was closed. 

Thanks to all that offered their solutions!



Your answer

Register or to post your answer.