Message Reference > S Message Codes > SQL Messages
  

SQL Messages

SQL_50001 IOutputBuffer::setRowType() API has failed.

Explanation:
The Integration Service failed to generate an output row from the SQL transformation.
User Response:
Review previous error messages for more information.

SQL_50002 NULL DB Handle returned.

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.

SQL_50003 ScriptName is empty.

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.

SQL_50004 SetProperty failed.

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.

SQL_50005 Logical Connection Object Name is empty.

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.

SQL_50006 FlushOutRow failed.

Explanation:
The Integration Service failed to generate an output row from the SQL transformation.
User Response:
Review previous error messages for more information.

SQL_50007 ODL Error has occurred. Please see the pre-defined error port for detailed error message.

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.

SQL_50008 Number of columns in the select query is greater than the number of output ports in the SQL transformation.

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.

SQL_50009 Static Connection information is inappropriate to create a valid database handle.

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.

SQL_50010 Error: File handle could not be created.

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.

SQL_50011 The SQL Query entered through the Designer is empty.

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.

SQL_50013 Setting the data in target failed.

Explanation:
The Integration Service failed to write output data from the SQL transformation.
User Response:
See previous error messages for more information.

SQL_50014 Getting the data from source failed.

Explanation:
The Integration Service was unable to access the source data for the SQL transformation.
User Response:
See previous error messages for more information.

SQL_50015 Failed to connect to the database.

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.

SQL_50017 Failed to get the relational connection name attribute from repository.

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.

SQL_50018 Failed to get the 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.

SQL_50070 Error threshold reached.

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.

SQL_50071 Session failed because a connection failure occurred after the SQL transformation passed some of the output rows downstream.

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.

SQL_50072 An error occurred expanding a parameter or variable in the environment SQL <connection or transaction environment SQL> for the connection object <connection name>.

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.