Explanation: | The Integration Service failed to generate an output row from the SQL transformation. |
User Response: | Review previous error messages for more information. |
Explanation: | The Integration Service failed to connect to a database using a dynamic connection with an SQL transformation. |
User Response: | The source data contains invalid connection data. The database user name, database password, server, or connect string is not correct for the database. |
Explanation: | The SQL transformation is configured to run an external SQL script but the ScriptName port contains no data. |
User Response: | The ScriptName port must contain the name and path of the file containing an SQL script to run for each input row. Verify ScriptName port is connected and the source data contains the file name. |
Explanation: | The Integration Service failed to set database properties for an SQL transformation dynamic connection. |
User Response: | The dynamic connection contains Advanced Option name-value pairs. Verify that you spelled the options correctly and each option is valid for the database type. The Advanced Options are not case sensitive. |
Explanation: | The Integration Service failed to connect to a database for this row because the LogicalConnectionObject port of the SQL transformation contains no data. |
User Response: | Verify that the LogicalConnectionObject port is connected and the source data contains a valid connection object name in each row. |
Explanation: | The Integration Service failed to generate an output row from the SQL transformation. |
User Response: | Review previous error messages for more information. |
Explanation: | The Integration Service encountered a database error while processing an SQL query from the SQL transformation. |
User Response: | Review the error messages from the SQL transformation SQLError port. |
Explanation: | The SQL transformation does not have an output port for each column in the SQL SELECT statement. |
User Response: | Add the missing output ports to the SQL transformation. |
Explanation: | The Integration Service cannot connect to the database because the connection defined in Workflow Manager connections is not valid for the SQL transformation. |
User Response: | Use a relational database connection for the SQL transformation. Verify the database type in the connection is valid for the SQL transformation. |
Explanation: | The Integration Service could not find the script file for the SQL transformation. |
User Response: | Verify the script file exists and is accessible by the Integration Service. |
Explanation: | An SQL transformation is configured to run query mode. However, the transformation does not have an SQL query. |
User Response: | Add an SQL query to the transformation. |
Explanation: | The Integration Service failed to write output data from the SQL transformation. |
User Response: | See previous error messages for more information. |
Explanation: | The Integration Service was unable to access the source data for the SQL transformation. |
User Response: | See previous error messages for more information. |
Explanation: | The Integration Service could not connect to the database with the dynamic connection data from the source. |
User Response: | Verify the database user name, password, and connect string are correct for the database. |
Explanation: | The Integration Service failed to find the database connection name in the repository. |
User Response: | Verify that the database connection name is a valid connection name in Workflow Manager connections. |
Explanation: | The Integration Service could not connect to the database with the dynamic connection. |
User Response: | Verify that the database user name, password, and connect string are correct for the database. |
Explanation: | The row error count exceeded the error threshold. You can ignore SQL errors by enabling the Continue on SQL Error within a Row option. The Integration Service continues to run the rest of the SQL statements for the row. However, the session fails when the error count exceeds the error threshold. |
User Response: | Review SQL errors in the SQLError port. The SQLError port contains the failed SQL statements and error messages. |
Explanation: | A database connection failure occurred while the SQL transformation was executing a SELECT statement. Some database rows were already passed from the SQL transformation to the pipeline. The Integration Service could not re-connect to the database and continue processing without duplicating the output rows. |
User Response: | None. Informational message. |
Explanation: | The SQL transformation is using a connection object that is configured with connection or transaction SQL. The SQL contains a parameter or variable that the Integration Service cannot resolve. |
User Response: | Verify that the parameter or variable is defined properly in the parameter file and that its value in the parameter file matches the parameter or variable datatype. For example, you cannot set an integer mapping variable to a text string in the parameter file. |