I have downloaded and installed "HIVE ODBC 64-bit connector" form http://package.mapr.com/tools/MapR-ODBC/MapR_odbc_2.1.0_x64.exe. Since I have 64 bit m/c .
But When I try to launch “MapR Hive ODBC Connector on the web” it throws an error of “Incompatibility ”.
Can anyone suggest me what could be the issue ? how to resolved it
Related
I am working with dagster and dbt. I have a test repo that I use both on a Debian VM and on my Windows PC. On Debian everything works fine, here on Windows I receive the following Oracle error and can't fix it.
ERROR oracle adapter: Got an error when attempting to open an Oracle connection:
'DPI-1047: Cannot locate a 64-bit Oracle Client library:
"failed to get message for Windows Error 126".
See https://cx-oracle.readthedocs.io/en/latest/user_guide/installation.html for help'
INFO oracle adapter: Rolling back transaction.
I am receiving this error even after:
Downloading Oracle Instant client and unzipping it in my Oracle folder (C:\Program Files (x86)\Oracle\instantclient_21_6)
Setting the ORACLE_HOME and PATH.
Installing and importing cx_Oracle.
Initializing cx_Oracle.
In order to use db2 with node.js on my mac. I have installed the db2 drivers - DB2 v11.1.4.5.
I also configured my environment paths so that the correct config files will be used by unixODBC
I configured the odbcinst.ini, ODBC.ini , db2cli.ini, and the db2dsdriver.cfg files
The issue is that I get the error below when I run the iqsl command or the db2cli validate command
My Error
[S1000][unixODBC][IBM][CLI Driver] SQL10007N Message "0" could not be retrieved. Reason code: "3".
unixODBC isql command syntax
isql usrProd userid password
db2cli validate command syntax
db2cli validate -dsn alias -connect -user userid -passwd password
Environment path stored in file ~/.bash_profile
export PATH=$PATH:/usr/local/share/odbc_db2/clidriver/bin/
export DB2CLIINIPATH=/usr/local/share/odbc_db2/clidriver/cfg/
export DB2DSDRIVER_CFG_PATH=/usr/local/share/odbc_db2/clidriver/cfg/
I have been documenting the steps that I took to install the db2 command line drivers.
My documentation
locations of the IBM DB2 Drivers I have installed:
Client Version (level/bit): DB2 v11.1.4.5 (special_39510/64-bit)
Client Version (level/bit): DB2 v11.1.1.1 (s1703232000/64-bit)
UPDATE --- 20200413----
I got it to work on my Mac. I did get it to work with Node.js
I contacted a few IBM developers who are working directly on this project, and they gave me access to the proper "IBM i Access ODBC Driver" to connect to the as400 from the mac.
It is being beta tested now. At some point, it should be released. to the general public.
db2cli drivers are not needed, db2cli.ini is not needed:
IBM has specific odbc drivers for the iseries. I dont have permission
to share the drivers with the public, but do know that it will be
possible soon for everyone to connect to db2 installed on the iseries
I got it to work on my Mac and I did get it to work with Node.js
I contacted a few IBM developers who are working directly on this project, and they gave me access to the proper "IBM i Access ODBC Driver" to connect to the as400 from the mac. It is being beta tested now, i assume that at some point, it should be released to the general public.
Note : db2cli drivers are not needed, db2cli.ini is not needed, and setting environment paths are not needed:
IBM has specific odbc drivers for the iseries. I don't have permission
to share the drivers with the public, but do know that it will be
possible soon for everyone to connect to db2 installed on the iseries
For IBM DB2 Warehouse on the IBM CLoud you can go to this url
https://your_tenant.cloud.ibm.com/console/#connection/overview
In above replace your_tenant with your tenant id.
I am trying to connect to a Pervasive Sql Server which is running on Windows machine from my Ruby application which is on Ubuntu Machine. Can Someone please help me on same. Thanks in advance
Below is my configuration on linux machine
/etc/freetds/freetds.conf
[pserver]
host = XXX.XXX.XX.XXX
port = 1583
tds version = 8.0
Under /etc/odbcinst.ini, I have saved the driver info like below
[freetds]
Description=freetds Driver
Driver=/usr/lib/x86_64-linux-gnu/odbc/libtdsodbc.so
Setup=/usr/lib/x86_64-linux-gnu/odbc/libtdsS.so
Trace=Yes
TraceFile=/tmp/freetds.log
ForceTrave=Yes
UsageCount=10
fileusage=1
dontdlclose=1
TDS_Version = 8.0
In /etc/odbc.ini, client and database details
[pclient]
Description = Pervasive SQL Server
Driver = freetds
Trace = Yes
Servername = pserver
Port = 1583
Database = "MyDatabasename"
TDS_Version = 8.0
tsql -S pserver -U db_username -P db_password -d MyDatabasename
above cmd gives error saying
Error 20009 (severity 9):
Unable to connect: Adaptive Server is unavailable or does not exist
OS error 111, "Connection refused"
There was a problem connecting to the server
iodbctest ["DSN=pclient;UID=db_username;PWD=db_password"]
this results in
iODBC Demonstration program
This program shows an interactive SQL processor
Driver Manager: 03.52.0812.0326
(iodbctest:6672): Gtk-WARNING **: 20:40:38.693: cannot open display:
Not able to understand the above result and how to handle this. Please help
As far as I know, the only way to access Pervasive PSQL from Ruby would be through ODBC. You need to use the Pervasive Client ODBC driver. Don't use the FreeTDS driver. I've never heard of using the FreeTDS driver to connect to Pervasive PSQL. In fact, this question mentions that FreeTDS doesn't work to Pervasive PSQL. Pervasive PSQL and Microsoft SQL Server are not the same product and the client for one cannot connect to the server of the other.
The short answer would be to install the Pervasive PSQL client on the Ubuntu machine, create the ODBC Datasource name pointing to the database on the Windows machine and then use ODBC from within Ruby to access the data.
You'll want to be on at least Pervasive PSQL v11.30, preferably Actian PSQL v13 (current version as of December 2018). You'll need to download and install the client appropriate for the application. If the Ruby application is 32 bit, you need the 32 bit ODBC driver. If the application is 64 bit, you'll need the 64 bit driver. The 'bitness' of the OS is not as important. You need to use the same PSQL client version as server version. You cannot use the v13 client with a v11 server.
I'm having the same problem. Here is my setup...
Windows 10 64-bit
SQL Server Data Tools v10.0.40219.1 SP1
Attunity Oracle Connector for SSIS (32-bit and 64-bit) v2.0
Oracle client 64-bit installed v12.1.0
Oracle client 32-bit installed v12.1.0
Setup tnsnames.ora to point to dev and QA instance; verified connectivity via tnsping and sqlplus.
Setup ORACLE_HOME to point to 64-bit product directory
I've created a (MSORA) Microsoft Connector for Oracle by Attunity connection. I populate the connection with a tns-name, username, and password. I click the Test Connection button, and I see the following:
The full error is as follows:
===================================
Error at Export SingleFile [Connection manager "Sample"]: Oracle Home not found.
(Microsoft Visual Studio)
===================================
Test connection failed
===================================
Oracle Home not found.
(Export SingleFile)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.AcquireConnection(Object txn)
at Attunity.IntegrationServices.DataFlowUI.OracleUI.OraConnectionDialog.testConBtn_Click(Object sender, EventArgs e)
===================================
Oracle Home not found.
(Export SingleFile)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.AcquireConnection(Object txn)
If its not pulling oracle_home from my system variable, where does it pull it from?
Here is the ORACLE_HOME environment variable on my system:
There was an issue documented in the post Attunity Oracle Conenctor doesn't work after update, which identified a compatibility issue between version-5.0 of the Oracle connector and the latest version of SSDT (15.9.x as of 02/01/2019). Until the compatibility issue has been resolved, the de-facto solution is to deploy the 15.8.0-release of SSDT. This will install the 14.0.3002.113 Microsoft SQL Server Integration Services Designer.
Here were the steps I executed to resolve:
Install oracle 32-bit client from software center
Install oracle 64-bit client from software center
Deploy tnsnames.ora file to 32-bit install
Deploy tnsnames.ora file to 64-bit install
Microsoft SQL Server Data Tools release-15.8.0
Install (32-bit) SSIS Oracle Connector by Attunity version 5.0
Install (64-bit) SSIS Oracle Connector by Attunity version 5.0
Verify you have read and execute rights to items in both 32- and 64-bit client directory
Here are shots from my environment...
Cheers,
Adam
Glassfish version: GlassFish Server Open Source Edition 4.1 (build 13)
Oracle Database : 11.2.0.4
JDBC Driver obtained (ojdbc6.jar) obtained from Oracle download site w/c were copied into \glassfish-4.1\glassfish\domains\domain1\lib folder.
When I clink on "Ping" it throws error
Any help is highly appreciated.
Thanks,
Elmer