All Apps and Add-ons

DB Connect using DB2 zOS - invalid license

tlmayes
Contributor

Having problems with setting up DB Connect 3.0.1 to connect to DB2 on z/OS. I know, is not supported by Splunk.

Our dba provided the zOS driver and license file. With no modification to the Splunk environment (running on SuSE) the driver was recognized without issue. Proceed to create a connection. Continue to receive the error below, which believe to be a generic error response from the DB2 instance indicating that Splunk is not reading the provided license file "db2jcc_license_cisuz.jar"

-----------------------------error message (truncated)--------------------------------
Internal server error, originalErrorMessage=[jcc][t4][10509][13454][4.19.66] Connection
to the data server failed. The IBM Data Server for JDBC and SQLJ license was invalid
or was not activated for the DB2 for z/OS subsystem. If you are connecting directly to
the data server and using DB2 Connect Unlimited Edition for System z, perform the

activation step by running the activation program in the license activation kit.

I have tested the same setup using open source database clients, which all threw the same error, until I provided the path for the license file. Once the CLASSPATH was modified with the path to the license file, everything worked. So.... I did the same thing in Splunk, adding:

export CLASSPATH="/opt/splunk/etc/apps/splunk_app_db_connect/drivers/db2jcc_license_cisuz.jar"
Restarting Splunk
And verifying with: echo $CLASSPATH

Also tried the same process with the license file in:
/opt/splunk/etc/apps/splunk_app_db_connect/bin/lib

Hope somebody can help me see what I am missing

Kieffer87
Communicator

Not sure if you are still having issues but I came across this same issue and didn't have any luck with the answer either. What fixed it for me was switching from the JDBC 3.0 (db2jcc.jar) driver to JDBC 4.0 (db2jcc4.jar). No additional classpaths were needed.

0 Karma

season88481
Contributor

Hi @Kieffer87 ,

 

 

Just wondering what version is your Splunk DB Connect?

And what version is your JDBC 4.0 driver?

 

Many thanks,

S

0 Karma

john_dagostino
Path Finder

I was able to get this working with support. The answer ended up being in the documentation but we overlooked it. We had to create the folder $SPLUNK_HOME/etc/apps/splunk_app_db_connect/drivers/db2jcc4-libs and place the driver in there. I don't believe the folder name is relevant, however it does need to end in '-libs'. Once we did this we no longer received the license error.

aa70627
Communicator

this worked for us.

0 Karma

Rouk
Engager

Thank you ! Worked for me. db2jcc4.jar was already installed, adding db2jcc_license_cisuz.jar in directory had no effect until I reloaded config (http://yoursplunk:8000/debug/refresh)

0 Karma

FrankBurns
New Member

Last answer doesn't work for us and we can't get connected.

0 Karma

tlmayes
Contributor

Is there anybody out there that has Splunk DB Connect working using DB2 on zOS?

0 Karma

john_dagostino
Path Finder

Any solution to this? We're running into the same issue, however this was working in DB Connect v2.4. When we upgraded to 3.x we started seeing this error.

0 Karma

tlmayes
Contributor

Kind of. I finally got 2.4 working consistently in both Splunk 6.4.x and 6.5.x. Was unable to get 3.x working in any way. A response from support states it "may" be a JIRA issue that they are looking into.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...