I try to create a db2 schema in my application in eclipse, but connection fails [ERRORCODE=-4499, SQLSTATE=08001] I can access the db2 and run it directly but I need to establish the connection into my application to be able to insert from the client side. any advice?
Related
Whenever I attempt to connect to my PostgreSQL database as a data source, I get the error message below.
Other users have recommended using an odbc connection? Why does an odbc connection work rather than a PostgreSQL connection for a PostgreSQL database in Power BI?
Had attempted to connect to my PostgreSQL database with all the correct credentials, failed with the error message mentioned. I had connected to the same database with an odbc connection perfectly.
I am trying to connect a MySQL database via Google Cloud Data Fusion Wrangler. It's a very standard connection and I can connect and do every action with another tool (DBeaver). However, trying to connect with Wrangler, I am getting this message:
A server error occurred when testing the connection. Error: Exception occurred while handling request: string
Any suggestions? Thanks!
Please follow the instructions on https://cloud.google.com/data-fusion/docs/how-to/using-jdbc-drivers
Once done, you will be able to select the uploaded driver from the dropdown
For your requirement, you have to use JDBC Driver for connecting to MySQL database.You can use Public IP to setup connection to Wrangler.
Following are the steps to connect to MySQL database using Wrangler
Go to Hub in the Cloud Fusion instance and and select the required JDBC Driver.
Download the
driver and deploy it.
Go to Wranglers page and click on Add
Connection if you are connecting to MySQL for the first time.
Select
the MySQL database from the list of databases provided in Wrangler.
Add name and JDBC driver along with username, password and other connection arguments.
Click on test connection to check the connectivity.
For more details you can check this link.
Can you guide me about the connection between mongodb and power bi through ODBC driver. I have connection between them. but i got unexpected errors like:
"OLE DB or ODBC error: Exception from HRESULT: 0x80040E4E." , "OLE DB
or ODBC error: [DataSource.Error] ODBC: ERROR [42S22] [MySQL][ODBC
1.4(w) Driver][mysqld-5.7.12 mongosqld v2.14.3]Unknown column 'COD' in 'field list'."
and
"DataSource.Error: ODBC: ERROR [08S01] [MYSQL][ODBC 5.3(w) Driver Lost
conection to MySQL server at 'waiting for initial communication
packet', system error: 10060".
Can you tell me where the problem and how can I overcome on it?
I've had the same problem, try to go over the below steps and take a look at my advice under the fourth point (4).
Install mongosqld on your server based on your OS (first prerequisites).
LunchBI connector:
a) Make logs folder and mongosqld.log file in it.
b) Setup mongosqld.conf (IP:<your_server_ip>, PORT:3307)
Install mongosqld as a System Service link
Create a system DSN on your computer based on your OS, link.
Hint: On Windows (in ODBC data source) try to make both ANSI and UNICODE
connectors and do not forget to select a database in the dropdown menu.*
e.g. connect to Mongo via PowerBI via ODBC
a) Select a connector
b) Select the database, that you have selected in the previous dropdown menu.
For more information follow the official guide
you have to install mongosqld on your server and configure the .yalm file.
Inside it you have to uptade 'bind ip' field, by adding the remote ip.
We have an application on IBM WebSphere Application Server 7.x and it connects to a remote database on z/os DB2 10.x. For annual operation, DB2 shut down and restarted. After starting the database, we first get
com.ibm.websphere.ce.cm.StaleConnectionException
and then we get
The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated this particular request due to unexpected error conditions detected at the target system. ERRORCODE=-4499, SQLSTATE=58009
The connection between WebSphere and DB2 tested by 'test Connection' in WAS datasource. Both systems are up and running but there is no correct connection between them! There was no change in DB2, WAS, and JDBC driver.
Update: The JDBC driver version is 4.15.134, connection properties is IBM WebSphere default setting and the connection is direct to DB2. Another problem later showed that while the connection still has the problem, executing the query directly on z/OS's DB2 gets the same the error. The query consist of a select with a join on two different tables, selecting on each table is ok, but the final query does not work and gets ERRORCODE=-4499, SQLSTATE=58009.
Update 2
The detail of environment is: IBM WebSphere Application Server 7.0.0.45, DB2 10.1, Java version 1.6 SR16 and z/OS 1.13.
This specific query gets the error in all environments, on all application server, z/os SPUFI, database viewer, such as DBeaver.
Any help is greatly appreciated.
Finally, we found the solution, ran REORG and RUNSTATS on both tables and on all their partitions, and the error vanished both on the application and SPUFI. I guess something went wrong during restart and tables corrupted. Now everything is ok.
If I got you correctly, you complain on inability of the driver to reestablish the database connections after the DB2 for Z/OS restart.
If yes, then have you tried to set the corresponding connection properties described at the following link?
Configuration of Sysplex workload balancing and automatic client reroute for Java clients
My application server (say 192.168.100.1) and database server (say 192.168.100.2) both are on the same domain. I'm trying to create an ODBC connection from the application server to a SQL Server database on the database server, but at the time of login it generates this error:
Microsoft SQL Server Login
Connection failed:
SQL State: 'HYT00'
SQL Sever Error: 0
[Microsoft][ODBC SQL Server Driver]Login timeout expired
I've checked all configuration for SQL Server and tried possible solutions without resolving this issue.
Important:
A DSN can be successfully created from my own PC but when attempting this server to server as described above, ODBC is facing this problem.
OK, I have got the solution. Sometimes, if SQL Server can't be found on network by its name while creating DSN in windows, the logging in takes time more than usual which tells ODBC manager that Database Server we are looking for is not responding or responding too late.
Solution.
Instead of selecting server from the list while making dsn, use 'server-ip\SQLExpress'.
e.g 192.168.100.2\SQLExpress.
Thats All.