Error Codes

Error Codes

This appendix describes common error codes.

EXPR_00

Error message
EXPR_00("Invalid expression '{}': {}")
Issue
The expression used to define a stage or pipeline property failed to validate.
Troubleshooting and resolution
This error code typically displays when an expression includes a syntax error. To resolve the issue:
  • Verify that the expression fields are spelled correctly. For example, verify that you entered record:value and not record:values.
  • Verify that all required quotes are entered correctly, especially if the expression was copied and pasted. The only supported quote characters are " or '.
  • Verify that all the parentheses () and curly brackets {} are positioned correctly.
  • Verify that the expression is using supported functions.
  • Use expression completion in the property to verify that the expression you created is available for this property. Not all properties support all available functions.

HTTP_01

Error message
HTTP_01("Error fetching resource. HTTP-Status: {} Reason: {}")
Issue
The HTTP Client origin, HTTP Client processor, HTTP Client destination, or one of the orchestration stages encountered an unsuccessful status code, that is any non-2xx status code, while fetching the requested URL.
Troubleshooting and resolution
To resolve the issue:
  • Verify that the HTTP resource URL is correctly configured.
  • Verify that the HTTP resource URL is responsive. For example, use curl to access the URL.
  • Verify that pagination is correctly configured in the processor.
  • Review the returned HTTP status code to determine the type of failure.

JDBC_00

Error message
JDBC_00("Cannot connect to specified database: {}")
Issue

One of the stages that use JDBC connections, such as the JDBC Query Consumer origin, Oracle CDC Client origin, or JDBC Producer destination, could not connect to the database.

Troubleshooting and resolution
To resolve the issue:
  • Verify that you can access the server and connect to the database. You can use tools such as ping, netcat (nc), or telnet for this purpose.
  • Verify that the machine running Data Collector can connect to the database.
  • Verify that the correct database hostname and port number are configured in the stage.
  • Verify that the JDBC driver is correctly installed as an external library.

    To install an external library, add the external library to an external resource archive file for the deployment.

  • Verify that the user credentials are correctly entered in the Credentials tab for the stage.

JDBC_06

Error message
JDBC_06("Failed to initialize connection pool: {}")
Issue

One of the stages that use JDBC connections, such as the JDBC Query Consumer origin, Oracle CDC Client origin, or the JDBC Producer destination, could not connect to the database.

Troubleshooting and resolution
To resolve the issue:
  • Verify that you can access the server and connect to the database. You can use tools such as ping, netcat (nc), or telnet for this purpose.
  • Verify that the machine running Data Collector can connect to the database.
  • Verify that the correct database hostname and port number are configured in the stage.
  • Verify that the JDBC driver is correctly installed as an external library.

    To install an external library, add the external library to an external resource archive file for the deployment.

  • Verify that the user credentials are correctly entered in the Credentials tab for the stage.

JDBC_07

Error message
JDBC_07("Invalid column mapping from field '{}' to column '{}'")
Issue

One of the stages that use JDBC connections, such as the JDBC Tee processor or JDBC Producer destination, specifies a table column name that does not exist.

Troubleshooting and resolution
To resolve the issue:
  • Use preview mode to verify the field names in the Data Collector record.
  • Verify the column names in the database table.
  • Verify that the Field to Column Mapping property is correctly configured and that the specified table columns exist.

JDBC_16

Error message
JDBC_16("Table '{}' does not exist or PDB is incorrect. Make sure the correct PDB was specified")
Issue

The Oracle CDC Client origin has an incorrectly configured Oracle pluggable database (PDB).

Or, one of the stages that use JDBC connections specifies an incorrect{schema.tablename} value, or specifies a table that does not exist. This error can also occur when the user credentials configured for the stage do not have the correct permissions to query table metadata from the database.

Troubleshooting and resolution
To resolve the issue:
  • For an Oracle CDC Client origin, verify that configuring the PDB name is required. In most cases, it is not required. Or, if the origin reads the dictionary from redo logs, verify that the specified schema and table exist.
  • For other JDBC stages, verify that the specified schema and table exist.

JDBC_28

Error message
JDBC_28("Failed to create JDBC driver, JDBC driver JAR may be missing: {}")
Issue
One of the stages that use JDBC connections, such as the Oracle CDC Client origin or the JDBC Producer destination, encountered an error resolving the driver class for the database.
Troubleshooting and resolution
To resolve the issue:
  • Verify that the JDBC driver containing the driver class is correctly installed as an external library.

    To install an external library, add the external library to an external resource archive file for the deployment.

  • Verify that the correct class name for the driver is defined in the JDBC Class Driver Name property on the Legacy Drivers tab for the stage. JDBC-4 compliant drivers usually do not require defining this property.

JDBC_29

Error message

JDBC_29("Query must include '{}' in WHERE clause and in ORDER BY clause before other columns.")

Issue

The JDBC Query Consumer origin is configured to perform an incremental SQL query, but the offset column is not included in the WHERE or ORDER BY clause. Or, the offset column is not included as the first column in the WHERE or ORDER BY clause.

Troubleshooting and resolution
To resolve the issue:
  • Verify that the offset column is included in both the WHERE and ORDER BY clauses.
  • Verify that the offset column is included as the first column in both the WHERE and ORDER BY clauses.

JDBC_34

Error message
JDBC_34("Query failed to execute: '{}' Error: {}")
Issue

Pipeline validation encountered an error because the SQL query defined in the JDBC Query Consumer origin cannot be executed.

Troubleshooting and resolution
To resolve the issue, verify that the SQL query uses valid syntax and uses existing tables.
Review the guidelines to define a SQL query for the JDBC Query Consumer origin. In addition, review the guidelines to define SELECT statements in your database vendor documentation.

JDBC_37

Error message
JDBC_37("Unsupported type 1111 for column")
Issue

The JDBC Multitable Consumer origin, JDBC Query Consumer origin, or JDBC Lookup processor encountered an unsupported data type.

Troubleshooting and resolution
To resolve the issue, configure the stage to convert the data to string when possible by setting the On Unknown Type property to Convert to String on the Advanced tab.
Not all unsupported data types can successfully be converted to string. When using this option, verify that the data is converted to string as expected.

JDBC_38

Error message
JDBC_38("Query must include '{}' clause.")
Issue

Pipeline validation encountered an error because the SQL query configured for the JDBC Query Consumer origin does not include the required WHERE and ORDER BY clauses.

Troubleshooting and resolution
To resolve the issue:
  • Verify whether the origin should be running in incremental or full mode.
  • Verify that the SQL query includes both the WHERE and ORDER BY clauses and that they are correctly defined.
  • Verify that the offset column configured in the origin properties is included in the WHERE and ORDER BY clauses of the SQL query.

JDBC_51

Error message
JDBC_51("Invalid value: {}")
Issue

The JDBC Query Consumer origin is configured for incremental mode, but the Offset Column or Initial Offset property is not configured.

Troubleshooting and resolution
To resolve the issue:

JDBC_66

Error message

JDBC_66("No Tables match the configuration in the origin.")

Issue

One of the origins that use JDBC connections, such as the JDBC Multitable Consumer origin or the Oracle CDC Client origin, specifies a table in the table configuration that does not exist. Or, the origin does not specify the required table name.

Troubleshooting and resolution
To resolve the issue, verify that the origin has a correctly configured table configuration. For more information, see the Table Configuration topic for the origin.

JDBC_502

Error message
JDBC_502("Batch size greater than maximum batch size allowed in sdc.properties, maxBatchSize: {}")
Issue

The maximum batch size configured in the origin properties is greater than the Data Collector maximum batch size configured in the advanced engine configuration properties in the deployment.

Troubleshooting and resolution
To resolve the issue, decrease the origin maximum batch size property so that it is less than the Data Collector production.maxBatchSize property.
Modify Data Collector configuration properties by configuring the deployment. In Control Hub, edit the deployment. In the Configure Engine section, click Advanced Configuration. Then, click Data Collector Configuration.

KAFKA_41

Error message
KAFKA_41("Could not get partition count for topic '{}' : {}")
Issue

The Kafka Multitopic Consumer or MapR Multitopic Streams Consumer origin cannot retrieve the number of partitions in the topic based on its partition list. The partition list might be empty.

Troubleshooting and resolution
To resolve the issue:
  • Use another tool to verify that the machine running Data Collector can connect to the Kafka broker or to the MapR Streams cluster.
  • For the Kafka Multitopic Consumer origin, verify that the Kafka broker URI is correctly configured in the origin.
  • Verify that the topic is correctly configured in the Kafka or MapR Streams cluster.

RECORDFS_01

Error message
RECORDFS_01("Directory '{}' does not exist")
Issue

The pipeline is configured to write error records to file, but the specified directory for the error record files does not exist.

Troubleshooting and resolution
To resolve the issue, verify that the directory configured in the Error Records - Write to File tab in the pipeline properties exists.

SNOWFLAKE_16

Error message
SNOWFLAKE_16("{<Snowflake SQL command>} failed: {}")
Issue
The Snowflake destination encountered an error while running one of the following Snowflake SQL commands:
  • DESCRIBE FILE FORMAT
  • DESCRIBE TABLE
  • DESCRIBE PIPE
  • DESCRIBE STAGE
  • USE SCHEMA
Troubleshooting and resolution
To resolve the issue, verify that the Database, Schema, and Snowflake File Format properties are correctly configured for the destination. The Snowflake File Format property should not be used unless recommended by StreamSets customer support.

SPOOLDIR_12

Error message
SPOOLDIR_12("Directory '{}' does not exist")
Issue

The Directory origin is configured to read files from a local directory that does not exist.

Troubleshooting and resolution
To resolve the issue, verify that the local directory configured in the origin exists.

SPOOLDIR_37

Error message
SPOOLDIR_37("Batch size greater than maximum batch size allowed in sdc.properties, maxBatchSize: {}")
Issue

The maximum batch size configured in the origin properties is greater than the Data Collector maximum batch size configured in the advanced engine configuration properties in the deployment.

Troubleshooting and resolution
To resolve the issue, modify the origin maximum batch size property so that it is less than the Data Collector production.maxBatchSize property.
Modify Data Collector configuration properties by configuring the deployment. In Control Hub, edit the deployment. In the Configure Engine section, click Advanced Configuration. Then, click Data Collector Configuration.

TOERROR_00

Error message
TOERROR_00("Sent to error by previous stage")
Issue

The pipeline encountered an error while processing error records.

Troubleshooting and resolution
To resolve the issue, verify that the Error Records tab in the pipeline properties is correctly configured.