Error Codes

• 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.

• 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.

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.

• 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 as an external resource for the deployment, as described in the Control Hub documentation.

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

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.

• 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 as an external resource for the deployment, as described in the Control Hub documentation.

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

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.

• 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.

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.

• 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.

• 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 as an external resource for the deployment, as described in the Control Hub documentation.

• 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("Query must include '{}' in WHERE clause and in ORDER BY clause before other columns.")

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.

• 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.

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

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.

• 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.

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

• Verify whether the origin should be running in incremental or full mode.
• If running in incremental mode, verify that the Offset Column and Initial Offset properties are correctly configured.

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

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.

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.

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.

• 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.

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

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

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.

The pipeline encountered an error while processing error records.