When you migrate to the current version of the workbench, you might have to edit database connections that you created by using previous versions of the workbench. This might happen because support for specific JDBC drivers and database vendors has changed. To fix this problem, edit the database connection to use one of the supported JDBC drivers.
If a database connection is canceled from outside of the workbench (for example, in DB2® by using the FORCE APPLICATIONS ALL command), the workbench cannot detect that the connection is dropped.
Some tasks you perform in this product require a live connection to the database. Any task that requires an active connection to the database (such as running an SQL statement in the SQL query builder) will not work properly if the connection is dropped. If a connection appears to be active in the workbench but is not active, first try to disconnect from the database and then reconnect.
If the database connection is still not active, then shut down the workbench and restart it.
If the connection to the database server fails, you might receive an error message similar to this one: IWAS0126E Problems encountered while trying to establish connection &1. Reason: '&2'. For more information about the reason code (&2), refer to the documentation that comes with your database server.
If you connect and disconnect from a Cloudscape™ 5.1 database multiple times, tables might display without columns in the Database Explorer. If this problem occurs, restart the workbench.
On Linux®, the workbench might shut down abnormally when you connect to DB2 for iSeries™ V5R1 by using the AS/400® Toolbox for Java™ JDBC Driver. The problem occurs when you enter an incorrect password or leave the password field blank. If this problem occurs, restart the workbench and connect again using the correct password.
You can verify that the iSeries database host server is running by running the NETSTAT *CNN command. When the Work with TCP/IP Connection Status screen is displayed, look for the as-database entry under the Local Port heading and ensure that the entry is in Listen status.