Kettle database connection error: Erroroccuredwhiletryingtoconnect

1 Introduction erroccuredwhiletryingtoconnecttothedatabase Errors often occur during kettle development. However, when you carefully observe the logs, the causes of these errors are different. This error seems simple, but sometimes the simpler the error, the less patient it is to be changed. Especially when you are busy, you may accidentally enter a parameter

1 Introduction Error occured while trying to connect to the database often occurs during kettle development. However, the cause of this Error varies with the log carefully. This error seems simple, but sometimes the simpler the error, the less patient it is to be changed. Especially when you are busy, you may accidentally enter a parameter

1 Introduction

Error occured while trying to connect to the database often occurs during kettle development. However, the cause of this Error varies with the log carefully. This error seems simple, but sometimes the simpler the error, the less patient it is, especially when it is busy, it is the most annoying to accidentally enter a parameter that leads to this error, but you cannot run it if you feel it is okay. At this time, you need to calm down and check the Internet. The error may be solved happily. The following shows the details of the error.

2 Examples

There is a simple ktr script (current kettle version 3.0.4), such:

The normal configuration information entered in the table is as follows:

The kettle Installation File directory contains a jar package:

According to the above configuration, the ktr script can be executed normally.

1. First, let's look at the error that the ojdbc jar package is missing.

Is the case where the ojdbc package is deleted:

Log information:

Focus:

Exception while loading class oracle. jdbc. driver. OracleDriver. It means that an exception occurred while loading oracle. jdbc. driver. OracleDriver, which is probably caused by a jar package.

2. IP address input error

Error message in the log:

Io exceptions generally mean that the network adapter cannot establish a connection.

3 Database Name Error

Log errors:

An error occurred, processing will be stopped: Error occured while trying to connect to the database

23:34:40-table output. 0-ERROR (version 3.0.4, build 53 from 2008/06/24 18:14:00): Listener refused the connection with the following error:
ORA-12505, TNS: listener does not currently know of SID given in connect descriptor The Connection descriptor used by the client was: 127.0.0.1: 1521: orc

The listener rejects the connection due to the following error: The TNS (oracle server and client communication protocol) Listener does not know the current sid (the unique identifier of the database ), this sid is provided in the connection descriptor. The client that uses this descriptor is 127.0.0.1: 1521: orc.

4. The port number is incorrect.

Log status:

The error is the same as that of the IP Address:

5. incorrect user name or password

The user name or password is incorrect. The log information is as follows:

It indicates that the logon is rejected because the user name or password is invalid.

6. The running server does not have the permission to access the remote database.

Ping the ip address of the remote database machine from the running server:

Telnet the remote database port from the running server:

But the Script output from the table reports an error:

Logon rejected refused to log on. This error occurs because the machine running the script does not have the permission to access the database.

Here, the table output database is configured with a blacklist or whitelist, and the running server is not in its whitelist, leading to this error.

3. Conclusion

In case of such errors, You need to observe the logs calmly and carefully and use the exclusion method to quickly locate and solve the problem.