Troubleshooting Error messages Troubleshooting

13 If such an error is identified in the execution log, it is necessary to analyze the SQL code send to the database to find the source of the error. The code is displayed in the description tab of the erroneous task.

14.10.2 Common Problems and Solutions

This section describes common problems and solutions.

14.10.2.1 Connection Errors

■ UnknownDriverException The JDBC driver is incorrect. Check the name of the driver. ■ The application requester cannot establish the connection.name or IP address Cannot open a socket on host: name or IP address, port: 8471 Exception: java.net.UnknownHostException:name or IP address Oracle Data Integrator cannot connect to the database. Either the machine name or IP address is invalid, the DB2400 Services are not started or the TCPIP interface on AS400 is not started. Try to ping the AS400 machine using the same machine name or IP address, and check with the system administrator that the appropriate services are started. ■ Datasource not found or driver name not specified The ODBC Datasource specified in the JDBC URL is incorrect. ■ The application server rejected the connection.Signon was canceled. Database login failed, please verify userid and password. Communication Link Failure. Comm RC=8001 - CWBSY0001 - ... The user profile used is not valid. This error occurs when typing an invalid user name or an incorrect password. ■ Communication Link Failure An error occurred with the ODBC connectivity. Refer to the Client Access documentation for more information. ■ SQL5001 - Column qualifier or table 2 undefined. SQL5016 - Object name 1 not valid for naming convention Your JDBC connection or ODBC Datasource is configured to use the wrong naming convention. Use the ODBC Administrator to change your datasource to use the proper SQL or SYS naming convention, or use the appropriate option in the JDBC URL to force the naming conversion for instance jdbc:as400:195.10.10.13;naming=system . Note that if using the system naming convention in the Local Object Mask of the Physical Schema, you must enter SCHEMAOBJECT instead of SCHEMA.OBJECT. SQL should always be used unless your application is specifically designed for SYS. Oracle Data Integrator uses the SQL naming convention by default. ■ SQL0204 1 in 2 type 3 not found The table you are trying to access does not exist. This may be linked to an error in the context choice, or in the sequence of operations E.g.: The table is a temporary table which must be created by another interface. 14 Product TitleBookTitle as a Variable ■ Hexadecimal characters appear in the target tables. Accentuated characters are incorrectly transferred. The iSeries computer attaches a language identifier or CCSID to files, tables and even fields columns. CCSID 65535 is a generic code that identifies a file or field as being language independent: i.e. hexadecimal data. By definition, no translation is performed by the drivers. If you do not wish to update the CCSID of the file, then translation can be forced, in the JDBC URL, thanks to the flags ccsid=ccsid code and convert _ccsid_65535=yes|no. See the drivers documentation for more information. ■ SQL0901 SQL system error This error is an internal error of the DB2400 system. ■ SQL0206 Column 1 not in specified tables Keying error in a mappingjoinfilter. A string which is not a column name is interpreted as a column name, or a column name is misspelled. This error may also appear when accessing an error table associated to a datastore with a structure recently modified. It is necessary to impact in the error table the modification, or drop the error tables and let Oracle Data Integrator recreate it in the next execution.