<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DB Connect using DB2 zOS - invalid license in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354087#M42831</link>
    <description>&lt;P&gt;Thank you ! Worked for me. db2jcc4.jar was already installed, adding db2jcc_license_cisuz.jar in directory had no effect until I reloaded config (&lt;A href="http://yoursplunk:8000/debug/refresh" target="_blank"&gt;http://yoursplunk:8000/debug/refresh&lt;/A&gt;)&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 19:28:59 GMT</pubDate>
    <dc:creator>Rouk</dc:creator>
    <dc:date>2020-09-29T19:28:59Z</dc:date>
    <item>
      <title>DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354081#M42825</link>
      <description>&lt;P&gt;Having problems with setting up DB Connect 3.0.1 to connect to DB2 on z/OS.  I know, is not supported by Splunk.&lt;/P&gt;

&lt;P&gt;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"&lt;/P&gt;

&lt;P&gt;-----------------------------error message (truncated)--------------------------------&lt;BR /&gt;
Internal server error, originalErrorMessage=[jcc][t4][10509][13454][4.19.66] Connection &lt;BR /&gt;
to the data server failed. The IBM Data Server for JDBC and SQLJ license was invalid &lt;BR /&gt;
or was not activated for the DB2 for z/OS subsystem. If you are connecting directly to &lt;BR /&gt;
the data server and using DB2 Connect Unlimited Edition for System z, perform the &lt;/P&gt;

&lt;H2&gt;activation step by running the activation program in the license activation kit. &lt;/H2&gt;

&lt;P&gt;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:  &lt;/P&gt;

&lt;P&gt;export CLASSPATH="/opt/splunk/etc/apps/splunk_app_db_connect/drivers/db2jcc_license_cisuz.jar"&lt;BR /&gt;
Restarting Splunk&lt;BR /&gt;
And verifying with:  echo $CLASSPATH&lt;/P&gt;

&lt;P&gt;Also tried the same process with the license file in:&lt;BR /&gt;
/opt/splunk/etc/apps/splunk_app_db_connect/bin/lib&lt;/P&gt;

&lt;P&gt;Hope somebody can help me see what I am missing&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 13:13:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354081#M42825</guid>
      <dc:creator>tlmayes</dc:creator>
      <dc:date>2020-09-29T13:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354082#M42826</link>
      <description>&lt;P&gt;Is there anybody out there that has Splunk DB Connect working using DB2 on zOS?&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2017 12:29:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354082#M42826</guid>
      <dc:creator>tlmayes</dc:creator>
      <dc:date>2017-03-15T12:29:23Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354083#M42827</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 12:17:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354083#M42827</guid>
      <dc:creator>john_dagostino</dc:creator>
      <dc:date>2017-05-03T12:17:55Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354084#M42828</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 03 May 2017 18:25:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354084#M42828</guid>
      <dc:creator>tlmayes</dc:creator>
      <dc:date>2017-05-03T18:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354085#M42829</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:03:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354085#M42829</guid>
      <dc:creator>john_dagostino</dc:creator>
      <dc:date>2020-09-29T15:03:31Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354086#M42830</link>
      <description>&lt;P&gt;Last answer doesn't work for us and we can't get connected.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Oct 2017 15:04:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354086#M42830</guid>
      <dc:creator>FrankBurns</dc:creator>
      <dc:date>2017-10-18T15:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354087#M42831</link>
      <description>&lt;P&gt;Thank you ! Worked for me. db2jcc4.jar was already installed, adding db2jcc_license_cisuz.jar in directory had no effect until I reloaded config (&lt;A href="http://yoursplunk:8000/debug/refresh" target="_blank"&gt;http://yoursplunk:8000/debug/refresh&lt;/A&gt;)&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 19:28:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354087#M42831</guid>
      <dc:creator>Rouk</dc:creator>
      <dc:date>2020-09-29T19:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354088#M42832</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jul 2018 15:37:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354088#M42832</guid>
      <dc:creator>Kieffer87</dc:creator>
      <dc:date>2018-07-26T15:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354089#M42833</link>
      <description>&lt;P&gt;this worked for us.&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2020 22:57:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/354089#M42833</guid>
      <dc:creator>aa70627</dc:creator>
      <dc:date>2020-05-13T22:57:11Z</dc:date>
    </item>
    <item>
      <title>Re: DB Connect using DB2 zOS - invalid license</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/518769#M63375</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/194725"&gt;@Kieffer87&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just wondering what version is your Splunk DB Connect?&lt;/P&gt;&lt;P&gt;And what version is your&amp;nbsp;&lt;SPAN&gt;JDBC 4.0 driver?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;S&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Sep 2020 22:28:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/DB-Connect-using-DB2-zOS-invalid-license/m-p/518769#M63375</guid>
      <dc:creator>season88481</dc:creator>
      <dc:date>2020-09-09T22:28:25Z</dc:date>
    </item>
  </channel>
</rss>

