Troubleshooting

This section provides troubleshooting tips for resolving common issues with the Micro-Integration for PostgreSQL.

Check Database Connection Settings

Ensure that the db.database-name, db.hostname, db.port-number, db.user, and db.password in your configuration (application.yml or your environment) are correct.

Check that you have provided the required and correct parameters for the authentication method you selected.

The database user must have the necessary privileges for the target schema and table.

Validate Schema and Table Names

The schema and table must not be blank and must exist in your PostgreSQL database. The error message "Schema cannot be null or blank" or "Table cannot be null or blank" indicates a misconfiguration.

If you use dynamic destinations, the table name must be correctly referenced, using the fully-qualified name in the format schema.table.

Required Configuration Parameters

Ensure that you have supplied all required configuration parameters.

Make sure that the PostgreSQL database, schema, and table exist.

Unrecognized parameters may be ignored or cause errors.

Workflow Bindings

Double-check the binder and destination values in your workflow bindings. For writing to PostgreSQL, use binder: pgjdbc and reference the correct destination.

Permissions and Network

Ensure network connectivity to your PostgreSQL server (host and port).

The PostgreSQL user you configured must have INSERT/UPDATE/SELECT privileges on the relevant tables.

Error Output and Logging

Review the application logs for specific error messages, such as connection errors, SQL exceptions, or authentication failures.

Enable debug or verbose logging for more detailed diagnostics.

Dependency and Build Issues

Make sure you are using JDK 17 or higher.

Hard Delete Not Applied

If a delete-flagged message does not resolve every primary key column (for example, a partial composite key), the delete is rejected and the row is not deleted. A warning is logged; no error is raised.

If the delete key header does not contain a valid JSON object, the delete is rejected and a warning is logged.

Delete Matched No Rows

If a hard delete does not match any row in the target table, a warning is logged and no error is raised.

Foreign Key Violation on Delete

If a hard delete violates a foreign key constraint, the delete is rolled back and an error is logged. Remove or update the dependent rows before retrying the delete.