I am trying to configure my project with IBM WAS 8.5.5.12 with J.D.K 1.8 and need type 4 driver for connection.
I'm assuming you are talking about DB2 for z/OS.
Then the answer can be found here. The important parts:
The db2jcc_license_cisuz.jar file is included in all DB2 Connect server editions including DB2 Connect Personal Edition. The license is also part the IBM Database Enterprise Developer Edition. If you already have one of these products, then please use the license file from the DB2 Connect Activation CD. If you have a Passport Advantage account, then remember to download the activation key from Passport Advantage for the DB2 Connect edition that you have purchased.
The db2jcc_license_cisuz.jar file is located in the /db2/license directory of the activation CD or activation file downloaded from Passport Advantage.
And:
I don't have a DB2 Connect product. Now what do I do?
If you do not have the file, then you must purchase a DB2 Connect product so that you may license the JDBC driver to connect to a mainframe.
Probably your DB2 administrators can provide you with the files...
Related
In order to connect to IBM DB2 from either Excel or a C# .net application, which driver do I need in order to also get the data acceleration? (set current query acceleration all;) Are there drivers that are portable (don't need admin rights to install)?
If they do need admin, I can always ask IT support to install it for me..
Have been using JDBC drivers for my Squirrel SQL client, and they support IBM IDAA (acceleration), but these won't work with Excel nor C#. Obviously.
Any pointers?
To access Db2-for-Z/OS from either Excel or C# .net you will need a CLI driver for Db2 with matching bitness.
Depending on how your Db2-for-Z/OS subsystems are licensed you may also need a license-file on the Microsoft-windows workstation, becase IBM supplied CLI drivers are not free for accessing Db2-fo-Z/OS. Speak with your Z-DBA or passport-advantage-coordinator to get the license-file (and the correct version of it to match your version of Db2-for-Z/OS) or to determine if the target subsystem has already db2connectactivate enabled ( meaning no workstation based licenses are required).
IBM and other companies offer CLI drivers for Db2 for various operating systems including Microsoft Windows.
IBM offers different sizes of CLI driver, depening on how much functionality you need.
Any of these should work with IDAA as long as they are "current", and the keywords needed for IDAA exploitation should be common between the IBM supplied CLI drivers.
The smallest footprint, minimal function, zero install CLI driver from IBM is the "ODBC and CLI" driver, which is a zipfile (just unzip and register it per the docs). Get it via this link, and then install it per this documentation. Note that this driver gets frequently updated, as it is used by all CLI/ODBC based tools (perl, python, r, c#, ruby, c++, ...). It's also possible to use wget to download it. google for that.
A larger driver is the "Db2 runtime client", which has more functionality and the clpplus interface. This is available via the IBM Passport Advantage website , or via fix central for latest fixpacks.
The full Db2 client is a large image, and has all functionality that IBM offers for client side use. Get this via the IBM Passport Advantage website, or via fix central for latest fixpacks.
I need to connect to an Oracle 9i server from my machine using SQLDeveloper. I already have a functioning version of SQLDeveloper 18.2 + Oracle Client 12 for more modern databases, but for this connection I want a separate older version of SQLDeveloper.
I've installed SQLDeveloper 3.2.20.09 in a separate folder on my machine and can launch it, but it defaults to finding the ojdbc6.jar file from Oracle Client 12. if I go to Help > About and select properties, the jdbc.library says jdbc.library /C:/app/client/product/12.1.0/client_1/jdbc/lib/ojdbc6.jar
and if I try to connect I get the error ORA-01460: unimplemented or unreasonable conversion requested
I tried putting the path to the SQL Developer 3.2 install first in the PATH variable, but no difference. Is there a way to tell SQL Developer which jdbc driver to use for Oracle ? (maybe in sqldeveloper.conf)
The official answer is:
use the jar (driver) we ship with the product OR
use a Thick Client, and we'll pull the jdbc driver from an Instant Client or Oracle HOME on your machine
The 2nd option will work so long as you don't try to go back back or forward in time to the point that the software will recognize/support the driver.
In other words, you can't tell SQL Developer 18.x to use a 9i Home, we have a hard dependency to require at least a 11gR2 client (I believe, it could actually be a 12c based client which is required).
You'd be better off getting your data out of that ancier 9i Database and into a modern 12 or 19c Oracle instance.
but it defaults to finding the ojdbc6.jar file from Oracle Client 12.
Sounds like you've managed to get a thick connection defined, go into preferences and disabled on the advanced page any reference to OCI or Thick, then it will use the jdbc driver shipped with SQLDev.
I am trying to connect Snowflake to Tableau Online, my question might seem stupid but I really don't know how to solve this.
The instructions are provided here but I struggle with the very first step,
Driver required
This connector requires a driver to talk to the
database. You might already have the required driver installed on your
computer. If the driver is not installed on your computer, Tableau
displays a message in the connection dialog box with a link to the
Driver Download page where you can find driver links and installation
instructions.
This led me to a page asking me this
Tableau Desktop & Tableau Server: 9.3 - 2019.4 Follow these steps to
get the Windows ODBC driver for Snowflake:
Sign in to your Snowflake instance. Select Help > Download > ODBC
Driver. Select the ODBC driver for your operating system to download
the latest version. For installation and configuration details, follow
the Snowflake Documentation link on the ODBC Driver page.
I found the link to download the driver, but I am not using Tableau Desktop so I don't see how installing this on my laptop will help, how am I supposed to install this with Tableau Online?
I have tried to skip this step and add a Snowflake data source, but I have the following error message
Can’t connect to Snowflake
Detailed Error Message
The username or password is not valid. Check the database name and credentials and
try again.
Thank you!
Tableau has already installed the necessary ODBC driver. You need Tableau Desktop software on your computer to create (locally) the TDS or TWB. It is here that you need to install the ODBC software so you can connect your Tableau Desktop software to Snowflake. Once you have created the connection and created the TDS, then you can use your Tableau Online account to publish this to Online.
If you are using the web authoring features of Tableau Online to create a new workbook or data source, then you don't need to download or install the drivers for Snowflake, as they are already installed in Tableau Online.
Is DB2 Connect installation and license installation during build/deploy a good way to ensure mainframe connectivity to IBM Blue zone? My PHP Cloud Foundry app is on w3ibm.bluemix.
If yes shall I update the forked PHP Buildpack on GIT, by adding DB2 Connect to it?
Or shall I use some sort of docker image for this?
Any other idea?
I found that there is no need to install a DB2 Connect. I could not install it anyway on Bluemix. There might be services for this, but at the end I had to use DB2 PHP extension of the PHP build-pack and after deploy I copied the license file to the license folder from PHP code. Details here.
Where can I find the redistributable version of the IBM DB2 Type 4 driver?
I suppose this is the driver I would use to connect from a Java app (on windows) to DB2 on the mainframe?
You will not be able to connect to the mainframe with any redistributable JDBC driver. The driver pack consists of the actual type 4 driver (db2jcc.jar) and any number of license files of the form:
db2jcc_license_cisuz.jar
where the cisuz bit is variable, indicating the platforms that you're allowed to run on (iSeries, pSeries, System z, LUW and so on).
You're only likely to get cu with any freely distributable pack. You need the z to access DB2 on the mainframe and that's jealously guarded so you'll need to purchase a specific edition of DB2 Connect to get it. I think both PE and EE, the personal and enterprise editions, have this licence file.
Without that license file, the type 4 driver won't even try to talk to the server, you'll get an exception.
IBM's Fix pack site has the "IBM Data Server Driver for JDBC and SQLJ" which is nothing but the JDBC type 4 driver. Though the page I pointed to above happens to be the windows page, it's the same type 4 driver for all platforms, as should be expected.
I don't think any user/password is required.
There is no need to download the JDBC driver separately it is already shipped with your DB2 product.
You can easily find it at this location : C:\Program Files\IBM\SQLLIB\java\db2jcc.jar
db2jcc.jar is the driver name
You can get the drivers from the IBM site. You will need to have IBM ID and password to login (which you can obtain here). Zip file is about 7 MBs, in contains DB2 9.5 JDBC (type 2/4) and SQLJ drivers. Type 4 drivers are in db2jcc4.jar.
However, you won't be able to connect to mainframes with this driver if mainframe is running DB2 for z/OS. To do so, you need at least to purchase DB2 Connect product, which will cost you about $500 minimum.
If you're running on an AS/400 (or iSeries, or whatever the heck IBM is calling it these days), you'll probably want to get it from JTOpen.
Their toolbox replaces the old Java Toolbox and includes the JDBC drivers.
If I need any IBM JARs for DB2 or MQ, I usually just add it to the instructions that DB2 or MQ needs to be installed as a prerequisite along with a URL to download it.
The same goes for Java and many other not easily redistributable products as well.
This eliminates the need to worry about licensing issues as it would be on the onus of the user rather than the vendor to obtain the proper licenses.