# Database Integration Extraction Error Reference When Stitch replicates data from a database integration, it will check for the required user permissions and database server settings. If permissions or server settings aren’t properly defined, you may receive an error during the Extraction phase of the replication process. These errors will surface in the integration’s [Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs). In this reference: * [Common extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#common-error-reference) * [Amazon DynamoDB extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#amazon-dynamodb-server-error-reference) * [Microsoft SQL Server extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#microsoft-sql-server-error-reference) * [MongoDB extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) * [MySQL extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) * [Oracle extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) * [PostgreSQL extraction errors](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#postgresql-error-reference) ## Common extraction errors Information note **Looking for SaaS integrations?** Refer to the [Common SaaS Extraction Error Reference](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/common-saas-extraction-error-reference). The following errors are applicable to all database integrations that support Extraction Logs: * [Stitch has discovered more than the maximum supported limit of 10,000 tables in your integration.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#10k-table-limit) * [The process was terminated. Most often this occurs because the job has exceeded its allotted runtime. The next job will...](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#time-limit) * [A single record is larger than the Stitch API limit of 20MB](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#record-size-limit) ### Maximum discoverable table limit exceeded ``` Stitch has discovered more than the maximum supported limit of 10,000 tables in your integration. ``` `Stitch has discovered more than the maximum supported limit of 10,000 tables in your integration.`Stitch has discovered more than the maximum supported limit of 10,000 tables in your integration. | **Applicable to** | All database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | Discovery job limits | | **Potential cause(s)** | Stitch discovered more than the maximum limit of 10,000 tables for the integration. | | **Suggested action(s)** | Decrease the number of discoverable tables by limiting the Stitch database user’s access only to tables you want to replicate. You can accomplish this by altering the Stitch database user’s privileges in the database.

Refer to the [documentation for your database](https://help.qlik.com/en-US/stitch/integrations/databases/#all-database-integrations) for instructions. | [Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Extraction job time limit exceeded ``` The process was terminated. Most often this occurs because the job has exceeded its allotted runtime. The next job will run based on the integration's schedule. ``` `The process was terminated. Most often this occurs because the job has exceeded its allotted runtime. The next job will run based on the integration's schedule.`The process was terminated. Most often this occurs because the job has exceeded its allotted runtime. The next job will run based on the integration's schedule. | **Applicable to** | All integrations | | --- | --- | | **Level** | Info

the Success icon

Everything is working. | | **Category** | Extraction job limits | | **Potential cause(s)** | The extraction exceeded the maximum 24 hours limit set for individual extraction jobs.

Stitch sets a maximum limit of 24 hours for individual extraction jobs. This is done to balance resource usage across Stitch, and to help prevent unexpected or unintended continuations of connections against integrations. | | **Suggested action(s)** | To help decrease the runtime of extraction, we recommend de-selecting unneeded tables and columns. This will reduce the amount of data being replicated.

Stitch will automatically retry extraction based on the integration’s schedule. | [Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Maximum record size exceeded ``` A single record is larger than the Stitch API limit of 20MB ``` `A single record is larger than the Stitch API limit of 20MB`A single record is larger than the Stitch API limit of 20MB | **Applicable to** | All integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | Extraction job limits | | **Potential cause(s)** | A single record exceeded the maximum size limit of 20MB. This limit is imposed by the [Import API](https://help.qlik.com/en-US/stitch/getting-started/basic-concepts-system-overview#system-architecture), which Stitch uses as part of the replication process. | | **Suggested action(s)** | Locate the record in the source and, if possible, modify it to be less than Stitch’s limit. You can also try de-selecting columns in the table containing the record. | [Back to Common error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## Amazon DynamoDB extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * Amazon DynamoDB * [An error occurred (ValidationException) when calling the Scan operation: Invalid ProjectionExpression: Syntax error; token: """, near: ""\[FIELD_NAME\]"](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#quote-projection-expression-error) ### Projection expression contains double quotes ``` An error occurred (ValidationException) when calling the Scan operation: Invalid ProjectionExpression: Syntax error; token: """, near: ""[FIELD_NAME]" ``` ` An error occurred (ValidationException) when calling the Scan operation: Invalid ProjectionExpression: Syntax error; token: """, near: ""[FIELD_NAME]" `An error occurred (ValidationException) when calling the Scan operation: Invalid ProjectionExpression: Syntax error; token: """, near: ""[FIELD\_NAME]" | **Applicable to** | Amazon DynamoDB v1 database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Projection expressions](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-dynamodb/field-selection-using-projection-expressions) | | **Potential cause(s)** | A projection expression entered in Stitch contains double quotes. | | **Suggested action(s)** | Remove double quotes from any projection expression and ensure they adhere to [Stitch’s other requirements for projection expressions](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-dynamodb/field-selection-using-projection-expressions#projection-query-stitch-requirements). | [Back to Amazon DynamoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#amazon-dynamodb-server-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## Microsoft SQL Server extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * Amazon Microsoft SQL Server RDS * Microsoft Azure SQL Database * Microsoft SQL Server * [Cannot sync stream: \[TABLE_NAME\] using log-based replication. Change Tracking is not enabled for database: \[DATABASE_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#ct-not-enabled-for-database) * [Cannot sync stream: \[TABLE_NAME\] using log-based replication. Change Tracking is not enabled for table: \[TABLE_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#ct-not-enabled-for-table) * [CHANGE_TRACKING_MIN_VALID_VERSION has reported a value greater than current-log-version. Executing a full table sync.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#log-aged-out) ### Change tracking isn't enabled for a database ``` Cannot sync stream: [TABLE_NAME] using log-based replication. Change Tracking is not enabled for database: [DATABASE_NAME] ``` `Cannot sync stream: [TABLE_NAME] using log-based replication. Change Tracking is not enabled for database: [DATABASE_NAME]`Cannot sync stream: [TABLE\_NAME] using log-based replication. Change Tracking is not enabled for database: [DATABASE\_NAME] | **Applicable to** | Microsoft SQL Server v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | Change Tracking is not enabled for the named database, which contains tables that are set to replicate and use Log-based Incremental Replication in Stitch. | | **Suggested action(s)** | Enable Change Tracking for the database referenced in the error message. To use Change Tracking, you must enabled it both at the database and table level.

To enable Change Tracking for the database, log into your database and run the following statement, replacing `` with the name of the database:

```
ALTER DATABASE
SET CHANGE_TRACKING = ON
(CHANGE_RETENTION = 3 DAYS, AUTO_CLEANUP = ON)
``` | [Back to Microsoft SQL Server error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#microsoft-sql-server-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Change tracking isn't enabled for a table ``` Cannot sync stream: [TABLE_NAME] using log-based replication. Change Tracking is not enabled for table: [TABLE_NAME] ``` `Cannot sync stream: [TABLE_NAME] using log-based replication. Change Tracking is not enabled for table: [TABLE_NAME]`Cannot sync stream: [TABLE\_NAME] using log-based replication. Change Tracking is not enabled for table: [TABLE\_NAME] | **Applicable to** | Microsoft SQL Server v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | Change tracking is not enabled for the named table, which is set to replicate and use Log-based Incremental Replication. | | **Suggested action(s)** | Enable change tracking for the table referenced in the error message. To use Change Tracking, you must enabled it both at the database and table level. Microsoft SQL Server requires that Change Tracking be enabled for every table you want to use Log-based Incremental for.

To enable Change Tracking for the table, log into your database and run the following statement, replacing `.` with the names of the schema and table:

```
ALTER TABLE .
ENABLE CHANGE_TRACKING
WITH (TRACK_COLUMNS_UPDATED = ON)
```

Run the statement for every table you want to replicate using Log-based Incremental Replication. | [Back to Microsoft SQL Server error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#microsoft-sql-server-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Insufficient log retention settings ``` CHANGE_TRACKING_MIN_VALID_VERSION has reported a value greater than current-log-version. Executing a full table sync. ``` `CHANGE_TRACKING_MIN_VALID_VERSION has reported a value greater than current-log-version. Executing a full table sync.`CHANGE\_TRACKING\_MIN\_VALID\_VERSION has reported a value greater than current-log-version. Executing a full table sync. | **Applicable to** | Microsoft SQL Server v1-backed database integrations | | --- | --- | | **Level** | Info

the Success icon

Everything is working. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The log retention settings for the database are insufficient, causing log files to age out before Stitch can replicate them. When this occurs, Stitch will clear the saved log position ID for any affection table(s) and re-replicate them in full. | | **Suggested action(s)** | Increase the database’s `CHANGE_RETENTION` setting. Stitch recommends a minimum of 3 days, but 7 days is preferred. This ensures that you have time to resolve any issues that arise before logs age out and are purged. Refer to [Microsoft’s documentation](https://docs.microsoft.com/en-us/sql/relational-databases/track-changes/enable-and-disable-change-tracking-sql-server?view=sql-server-ver15) for more info about this setting.

In addition, make sure you resolve any connection or replication issues quickly. This will reduce the likelihood that binary log files will age out and cause this error. | [Back to Microsoft SQL Server error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#microsoft-sql-server-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## MongoDB extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * MongoDB * MongoDB Atlas * [\[DATA_TYPE\] is not a supported replication key type](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#unsupported-rep-key-type) * [Clearing state because Oplog has aged out Must complete full table sync before starting oplog replication for \[COLLECTION_NAME\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oplog-age-out-full-table-replication) * [not authorized on local to execute command { \[COMMAND\] }](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#local-not-authorized) * [Projection blacklists key property id](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#projection-blacklisted-id) * [Projection cannot have a mix of inclusion and exclusion.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#projection-inclusion-exclusion) * [The projection: \[PROJECTION_QUERY\] for stream \[COLLECTION_NAME\] is not valid json](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#projection-invalid-json) ### Incompatible data type for Replication Key ``` [DATA_TYPE] is not a supported replication key type ``` `[DATA_TYPE] is not a supported replication key type`[DATA\_TYPE] is not a supported replication key type | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Replication Keys](https://help.qlik.com/en-US/stitch/replication/mongo-replication-keys) | | **Potential cause(s)** | A Replication Key field contains an incompatible data type.

[Stitch requires MongoDB Replication Key fields](https://github.com/singer-io/tap-mongodb/blob/master/tap_mongodb/sync_strategies/common.py#L77) to be one of the following data types:

  • DATETIME

  • FLOAT

  • INT64

  • INTEGER

  • OBJECTID

  • TIMESTAMP

  • UUID

| | **Suggested action(s)** |
  • Select a different Replication Key for the collection, or
  • Convert the data to a supported Replication Key data type, if possible
| [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Insufficient maximum OpLog size ``` Clearing state because Oplog has aged out Must complete full table sync before starting oplog replication for [COLLECTION_NAME] ``` `Clearing state because Oplog has aged out Must complete full table sync before starting oplog replication for [COLLECTION_NAME]`Clearing state because Oplog has aged out Must complete full table sync before starting oplog replication for [COLLECTION\_NAME] | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Info

the Success icon

Everything is working. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--log-retention) | | **Potential cause(s)** | The OpLog’s maximum size is insufficient, causing log files to age out before Stitch can replicate them. When this occurs, Stitch will clear the saved log position ID for any affection collection(s) and re-replicate them in full. | | **Suggested action(s)** | Increase the maximum size of the OpLog using the [replSetResizeOplog](https://docs.mongodb.com/v4.0/reference/command/replSetResizeOplog/#dbcmd.replSetResizeOplog) command.

**Note**: As the maximum size you need depends on your database, it may take some experimentation to identify the best setting. Mongo doesn’t currently recommend an OpLog size. | [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Insufficient privileges on local database ``` not authorized on local to execute command { [COMMAND] } ``` `not authorized on local to execute command { [COMMAND] }`not authorized on local to execute command { [COMMAND] } | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | Database user privileges | | **Potential cause(s)** | The Stitch MongoDB database user isn’t authorized to execute commands on the `local` database. This is required to successfully replicate data. | | **Suggested action(s)** | Grant the Stitch MongoDB database user `read` access to the `local` database. Refer to the guide for your MongoDB type for instructions:

| [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Projection query excludes the collection's \_id field ``` Projection blacklists key property id ``` `Projection blacklists key property id`Projection blacklists key property id | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Projection queries](https://help.qlik.com/en-US/stitch/integrations/databases/mongodb/field-selection-using-projection-queries) | | **Potential cause(s)** | A projection query for a collection set to replicate is excluding the collection’s `_id` field.

For example:

```
{ "_id": 0 }
``` | | **Suggested action(s)** | Modify the collection’s projection query to remove the exclusion of the `_id` field. Stitch requires the `_id` field for replication; excluding it in projection queries is not supported.

Refer to the [Selecting MongoDB Fields Using Projection Queries guide](https://help.qlik.com/en-US/stitch/integrations/databases/mongodb/field-selection-using-projection-queries) for more info. | [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Projection query contains inclusion and exclusion statements ``` Projection cannot have a mix of inclusion and exclusion. ``` `Projection cannot have a mix of inclusion and exclusion.`Projection cannot have a mix of inclusion and exclusion. | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Projection queries](https://help.qlik.com/en-US/stitch/integrations/databases/mongodb/field-selection-using-projection-queries) | | **Potential cause(s)** | A projection query for a collection set to replicate includes both inclusion and exclusion statements. MongoDB doesn’t currently support inclusion and exclusion statements in the same projection query.

The following projection query is an example of including both types of statements:

```
{ "name": 1, "type": 0 }
``` | | **Suggested action(s)** | Modify the collection’s projection query to use only inclusion or only exclusion statements. For example:

```
{ "name": 1, "type": 1 }
```

```
{ "name": 0, "type": 0 }
```

Refer to the [Selecting MongoDB Fields Using Projection Queries guide](https://help.qlik.com/en-US/stitch/integrations/databases/mongodb/field-selection-using-projection-queries) for more info and examples of projection queries. | [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Projection query contains invalid JSON ``` The projection: [PROJECTION_QUERY] for stream [COLLECTION_NAME] is not valid json ``` `The projection: [PROJECTION_QUERY] for stream [COLLECTION_NAME] is not valid json`The projection: [PROJECTION\_QUERY] for stream [COLLECTION\_NAME] is not valid json | **Applicable to** | MongoDB v1+-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Projection queries](https://help.qlik.com/en-US/stitch/integrations/databases/mongodb/field-selection-using-projection-queries) | | **Potential cause(s)** | A projection query for a collection set to replicate isn’t valid JSON. A projection query is a JSON object; keys within the object must be enclosed in double quotes (`"`).

For example: The following projection queries are invalid JSON:

```
{ 'name': 1, 'type': 1 }
```

```
"name: 1, "type": 1
``` | | **Suggested action(s)** | Modify the collection’s projection query to be valid JSON. For example:

```
{ "name": 1, "type": 1 }
```

You can use [JSONFormatter](https://jsonformatter.curiousconcept.com/) to validate the projection query before entering it into Stitch. | [Back to MongoDB error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mongodb-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## MySQL extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * Amazon Aurora MySQL RDS * Amazon MySQL RDS * Google CloudSQL MySQL * Magento * MariaDB * Microsoft Azure MySQL * MySQL * [A slave with the same server_uuid/server_id as this slave has connected to the master](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#server-id-not-unique) * [binlog_format is not set to 'ROW': \[MIXED or STATEMENT\].](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#binlog-format-row) * [binlog_row_image is not set to 'FULL': \[MINIMAL or NOBLOB\].](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#binlog-row-image-full) * [binlog_row_image system variable does not exist. MySQL version must be at least 5.6.2 to use binlog replication.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#version-requirement) * [Error persisting data for table "\[table_name\]": Record 0 did not conform to schema](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#schema-violation) * [It is a view.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#binlog-unsupported-views) * [Misconfigured master - server id was not set](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#master-server-id-not-set) * [MySQL binary logging is not enabled.](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#binlog-not-enabled) * [No max value for PK found for table \[table_name\].](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#empty-table-binlog) * [Requested position (\[log_file_position_from_state\]) for log file \[binary_log_file_name\] is greater than current position (\[current_log_file_position_on_server\]).](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#binlog-current-position) * [Unable to replicate binlog stream because the following binary log(s) no longer exist: \[binary_log_file_name\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#log-retention-purge) ### MySQL server ID isn't unique ``` A slave with the same server_uuid/server_id as this slave has connected to the master ``` `A slave with the same server_uuid/server_id as this slave has connected to the master`A slave with the same server\_uuid/server\_id as this slave has connected to the master | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The server ID of the instance Stitch is connected to is not unique.

When using Log-based Replication, the ID of the server Stitch connects to must be unique. This is because MySQL doesn’t allow replication to occur using the same server ID simultaneously across multiple connections. | | **Suggested action(s)** | If you’re using Log-based Replication and any of the following are true, you’ll need to define a unique server ID in the integration’s **Settings** page in Stitch:

  1. You connected one or more read replicas
  2. You connected multiple databases that are all on the same server
  3. You added a new MySQL-based Stitch integration, and the database is on the same server as other previously-connected databases


To do this, refer to the instructions for the database you’re connecting:

| [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Unsupported value for binlog\_format server parameter ``` binlog_format is not set to 'ROW': [MIXED or STATEMENT]. ``` `binlog_format is not set to 'ROW': [MIXED or STATEMENT].`binlog\_format is not set to 'ROW': [MIXED or STATEMENT]. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The `binlog_format` server parameter is not set to `ROW`, which Stitch requires for MySQL Log-based Replication. | | **Suggested action(s)** | Change the `binlog_format` parameter to `ROW`. This ensures that binary replication is “row-based”, meaning that events affecting individual rows are captured.

The steps for changing this parameter will vary depending on the type of MySQL database you’re using. Click the links below to view instructions for that database.

| [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Unsupported value for binlog\_row\_image server parameter ``` binlog_row_image is not set to 'FULL': [MINIMAL or NOBLOB]. ``` `binlog_row_image is not set to 'FULL': [MINIMAL or NOBLOB].`binlog\_row\_image is not set to 'FULL': [MINIMAL or NOBLOB]. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The `binlog_row_image` parameter is not set to `FULL`, which Stitch requires for MySQL Log-based Replication. | | **Suggested action(s)** | Changing the `binlog_row_image` parameter to `FULL`. This ensures that when a row is updated in the source database, the entire row is captured versus only the updated values.

The steps for changing this parameter will vary depending on the type of MySQL database you’re using. Click the links below to view instructions for that database.

| [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### MySQL version is insufficient for Log-based Incremental Replication ``` binlog_row_image system variable does not exist. MySQL version must be at least 5.6.2 to use binlog replication. ``` `binlog_row_image system variable does not exist. MySQL version must be at least 5.6.2 to use binlog replication.`binlog\_row\_image system variable does not exist. MySQL version must be at least 5.6.2 to use binlog replication. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The `binlog_row_image` parameter doesn’t exist in the version that the source MySQL database is running.

The version of the MySQL database is less than 5.6.2, which is the minimum version that supports binlog replication. Versions prior to 5.6.2 don’t support the binlog replication feature, which is required to use Log-based Incremental Replication in Stitch. | | **Suggested action(s)** | The source MySQL database must be running MySQL version 5.6.2 or greater to use binlog replication. If you can upgrade your database version, you may be able to use binlog replication. | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Schema violation ``` Error persisting data for table "[table_name]": Record 0 did not conform to schema ``` `Error persisting data for table "[table_name]": Record 0 did not conform to schema`Error persisting data for table "[table\_name]": Record 0 did not conform to schema | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--structural-changes) | | **Potential cause(s)** | The data replicated for a table does not match the expected schema. This occurs when the structure of a table changes in the source and Stitch is unable to verify its schema.

This occurs due to how Log-based Incremental Replication works, and how log messages are structured in database binary files. Refer to the [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/en-US/stitch#limitation-4--structural-changes) documentation for more info and examples.

This can occur when:

  • The table’s schema is altered by removing a column, adding a new column to the middle of the table, or changing the order of columns
  • The data type of a column is changed
  • The Stitch database user doesn’t have access to all the columns in the table
| | **Suggested action(s)** | To resolve the error, you’ll need to perform a table-level reset. To do this, open the **Table Settings** page for the table and click the **Reset Table** button. This will clear the table’s Replication Key value and queue a full re-replication of the table.

To prevent this error in the future:

  • When adding or removing columns, or changing data types, perform the table-level reset in Stitch immediately after the modification

  • Ensure the Stitch user has access to all the columns in the table. Although Stitch will be limited to the columns you specify while using SELECT during the initial replication job, values for restricted columns will still appear in binary log files.

    Because these values are in the binary log files but not in the initial SELECT replication, Stitch will interpret this as columns being reordered. Ensuring that the Stitch database user has access to all columns at the start can avoid this error.

| [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### A view is using an unsupported Replication Method ``` It is a view. ``` `It is a view.`It is a view. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--views-are-unsupported) | | **Potential cause(s)** | The source object is a database view. Binary logging doesn’t track events that occur in database views, so Stitch is unable to use Log-based Replication for views. | | **Suggested action(s)** | Update the view’s Replication Method to either [Key-based Incremental](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental) or [Full Table](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table). | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### MySQL server ID not set ``` Misconfigured master - server id was not set ``` `Misconfigured master - server id was not set`Misconfigured master - server id was not set | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | The server ID for the MySQL server hasn’t been set.

The [likely cause of this error is setting server parameters](https://dba.stackexchange.com/questions/76089/error-1236-from-master-after-restored-replication) on the master server without rebooting the master, which is required for server parameter changes to take effect. | | **Suggested action(s)** | Reboot the master instance to ensure the server parameters for enabling binlog are applied. | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Binary logging isn't enabled ``` MySQL binary logging is not enabled. ``` `MySQL binary logging is not enabled.`MySQL binary logging is not enabled. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | Binary logging isn’t enabled for the MySQL server. | | **Suggested action(s)** | Enable binary logging on your MySQL server. This is done by defining the `log_bin` parameter.

The steps for enabling binary logging will vary depending on the type of MySQL database you’re using. Click the links below to view instructions for that database.



**Note**: [Amazon MySQL RDS](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-rds-mysql#configure-database-parameter-group) and [Amazon Aurora RDS](https://help.qlik.com/en-US/stitch/integrations/databases/amazon-aurora#configure-database-parameter-group) databases should have binary logging enabled by default. If you receive this error for either of these databases, verify that the rest of the required server settings are defined correctly. | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### There are no Primary Keys in the table. ``` No max value for PK found for table [table_name]. ``` `No max value for PK found for table [table_name].`No max value for PK found for table [table\_name]. | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#historical-replication-jobs) | | **Potential cause(s)** | The table is empty. For Log-based Incremental Replication there must be Primary Keys in the table, as it’s the only way to identify unique records. If the table is empty, there are no Primary Key values, resulting in this error.
**Note**: Remaining tables will not be replicated if this error occurs, even if they contain valid data. | | **Suggested action(s)** | Use Key-based Incremental Replication to continue replication, or add Primary Keys to the table so that Log-based Incremental Replication can be used. | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Unavailable log file position ``` Requested position ([log_file_position_from_state]) for log file [binary_log_file_name] is greater than current position ([current_log_file_position_on_server]). ``` `Requested position ([log_file_position_from_state]) for log file [binary_log_file_name] is greater than current position ([current_log_file_position_on_server]).`Requested position ([log\_file\_position\_from\_state]) for log file [binary\_log\_file\_name] is greater than current position ([current\_log\_file\_position\_on\_server]). | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | When Stitch replicates data using Log-based Replication, it will “bookmark” its place by saving a position in the log file. When the next replication job begins, Stitch will use this value to identify the place in the log where it should begin reading data.

This error means that the log position Stitch has is “ahead” of the server. To summarize, the log position Stitch is attempting to use is greater than the log position that the MySQL database has available.

Typically this will be an issue only if the server uses a very small [`max_binlog_size`](https://dev.mysql.com/doc/refman/8.0/en/replication-options-binary-log.html#sysvar_max_binlog_size) value. | | **Suggested action(s)** | Perform an integration-level reset. To do this, open the **Integration Settings** page and click the **Reset This Integration** button. This will clear the integration’s Replication Keys and queue a full re-replication of the integration.

We also recommend checking the value of the `max_binlog_size` server parameter and increasing it if it’s too small. By default, this is set to MySQL’s maximum of 1 GB (1073741824 bytes). | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Insufficient log retention settings ``` Unable to replicate binlog stream because the following binary log(s) no longer exist: [binary_log_file_name] ``` `Unable to replicate binlog stream because the following binary log(s) no longer exist: [binary_log_file_name]`Unable to replicate binlog stream because the following binary log(s) no longer exist: [binary\_log\_file\_name] | **Applicable to** | MySQL v1-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--log-retention) | | **Potential cause(s)** | The requested binary log file has been removed from the server. When a binary log file is removed before Stitch can read from it, replication will be unable to proceed.

This can be caused by:

  • Insufficient log retention settings, which define how long log files remain on a server before they’re automatically purged.

  • Binary log files being purged before historical replication completes or critical errors that prevent Stitch from replicating data. When this occurs, it means Stitch was unable to proceed to the binary log file before the retention period passed and the log was purged.

| | **Suggested action(s)** | To resolve the error, you’ll need to perform an integration-level reset. To do this, open the **Integration Settings** page and click the **Reset This Integration** button. This will clear the integration’s Replication Keys and queue a full re-replication of the integration.

To prevent this error in the future, verify your server’s log retention settings and update them if needed. Stitch recommends a minimum of 3 days, but 7 days is preferred. This ensures that you have time to resolve any issues that arise before logs age out and are purged.

The steps for changing this parameter will vary depending on the type of MySQL database you’re using. Click the links below to view instructions for that database.



In addition, make sure you resolve any connection or replication issues quickly. This will reduce the likelihood that binary log files will age out and cause this error. | [Back to MySQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#mysql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## Oracle extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * Amazon Oracle RDS * Oracle * [CONTINUOUS_MINE is desupported for use with DBMNS_LOGMNR.START_LOGMNR](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#unsupported-version-for-logminer) * [LogMiner is NOT supported for views. Please change the replication method for \[table_name\]](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#logminer-views-not-supported) * [ORA-01291: missing logfile](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#missing-logfile) * [ORA-01292: no log file has been specified for the current LogMiner session](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#no-logfile-current-session) * [Unable to replicate with logminer for stream(\[table_name\]) because supplmental_log_data is not set to 'ALL' for either the table or the...](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#supplemental-logging-incorrect) ### The database is using a version that doesn't support LogMiner ``` CONTINUOUS_MINE is desupported for use with DBMNS_LOGMNR.START_LOGMNR ``` `CONTINUOUS_MINE is desupported for use with DBMNS_LOGMNR.START_LOGMNR`CONTINUOUS\_MINE is desupported for use with DBMNS\_LOGMNR.START\_LOGMNR | **Applicable to** | All Oracle-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--views-are-unsupported) | | **Potential cause(s)** | The database is using a version that doesn’t include support for Oracle’s LogMiner package, which Stitch uses to perform Log-based Incremental Replication.

The database must be using a version from 8.0 through 18c. | | **Suggested action(s)** | To resolve this error, you have two options:

  1. Modify the database to use a version that supports LogMiner
  2. Use either Full Table or Key-based Incremental Replication instead
| [Back to Oracle error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### A database view is using Log-based Incremental Replication ``` LogMiner is NOT supported for views. Please change the replication method for [table_name] ``` `LogMiner is NOT supported for views. Please change the replication method for [table_name]`LogMiner is NOT supported for views. Please change the replication method for [table\_name] | **Applicable to** | All Oracle-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--views-are-unsupported) | | **Potential cause(s)** | The source object is a database view. Binary logging doesn’t track events that occur in database views, so Stitch is unable to use Log-based Replication for views. | | **Suggested action(s)** | Change the view’s Replication Method to [Key-based Incremental](https://help.qlik.com/en-US/stitch/replication/replication-methods/key-based-incremental) or [Full Table](https://help.qlik.com/en-US/stitch/replication/replication-methods/full-table). | [Back to Oracle error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Missing log files and insufficient RMAN retention policy settings ``` ORA-01291: missing logfile ``` `ORA-01291: missing logfile`ORA-01291: missing logfile | **Applicable to** | All Oracle-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental#limitation--log-retention) | | **Potential cause(s)** | The requested log file has been removed from the server. When a log file is removed before Stitch can read from it, replicaiton will be unable to proceed.

This error typically arises due to [insufficient RMAN retention policy settings](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#configure-rman-backups), which define how long log files remain on a server before they’re automatically purged.

It can also be caused by log files being purged before historical replication completes or critical errors that prevent Stitch from replicating data. When this occurs, it means Stitch was unable to proceed to the log file before the retention period passed and the log was purged. | | **Suggested action(s)** | To resolve the error, you’ll need to perform an integration-level reset. To do this, open the **Integration Settings** page and click the **Reset Table** button. This will clear the integration’s Replication Keys and queue a full re-replication of the integration.

To prevent this error in the future, verify your RMAN retention policy settings and update them if needed. Stitch recommends a minimum of 3 days, but 7 days is preferred. This ensures that you have time to resolve any issues that arise before logs age out and are purged. Refer to the [Oracle documentation](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#configure-rman-backups) for more info.

In addition, make sure you resolve any connection or replication issues quickly. This will reduce the likelihood that log files will age out and cause this error. | [Back to Oracle error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Unavailable SCNs and RMAN retention window settings ``` ORA-01292: no log file has been specified for the current LogMiner session ``` `ORA-01292: no log file has been specified for the current LogMiner session`ORA-01292: no log file has been specified for the current LogMiner session | **Applicable to** | All Oracle-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | LogMiner is unable to locate the System Change Number (SCN) value Stitch has saved. SCNs are used to identify data in log files for Log-based Incremental Replication.

  • No new data is logged for the length of the RMAN retention window. For example: If the RMAN retention window is set to 2 days and no new data is created for two consecutive days, this error may occur.

  • The integration is paused for longer than the RMAN retention window. For example: If the RMAN retention window is set to 2 days and the integration is paused in Stitch for longer than two days, this error may occur.

| | **Suggested action(s)** |
  1. Verify the current RMAN retention window length.
  2. Increase the RMAN retention window. For example: Increase the window from 2 days to 7.
  3. Perform an integration level reset. To do this, open the Integration Settings page and click the Reset This Integration button. This will clear the integration’s Replication Keys and queue a full re-replication of the integration.
| [Back to Oracle error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Supplemental logging is incorrectly defined ``` Unable to replicate with logminer for stream([table_name]) because supplmental_log_data is not set to 'ALL' for either the table or the database. Please run: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS; ``` `Unable to replicate with logminer for stream([table_name]) because supplmental_log_data is not set to 'ALL' for either the table or the database. Please run: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;`Unable to replicate with logminer for stream([table\_name]) because supplmental\_log\_data is not set to 'ALL' for either the table or the database. Please run: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS; | **Applicable to** | All Oracle-backed database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | Supplemental logging is incorrectly defined either for the database or the table. Supplemental logging is required by Oracle to use LogMiner, which Stitch uses to perform Log-based Incremental Replication. | | **Suggested action(s)** | Stitch supports supplemental logging at the database and table level:

  • If enabled at the database level, tables do not need to be individually configured:

     ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS

  • If enabled at the table level, tables need to be individually configured. Run the following for every table you want to replicate through Stitch:

     ALTER TABLE <SCHEMA_NAME>.<TABLE_NAME> ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS


Refer to the [Oracle documentation](https://help.qlik.com/en-US/stitch/integrations/databases/oracle#enable-supplemental-logging) for more info. | [Back to Oracle error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#oracle-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ## PostgreSQL extraction errors Information note **The extraction errors in this section are applicable to the following database integrations:** * Amazon Aurora PostgreSQL RDS * Amazon PostgreSQL RDS * Google CloudSQL PostgreSQL * Heroku * PostgreSQL * [Fatal Error Occured - FATAL: connection requires a valid client certificate](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#ssl-required-error) * [Unable to find replication slot 'stitch' nor 'stitch_\[name\]' with wal2json](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#missing-replication-slot) ### SSL connections can't be required ``` Fatal Error Occured - FATAL: connection requires a valid client certificate ``` `Fatal Error Occured - FATAL: connection requires a valid client certificate`Fatal Error Occured - FATAL: connection requires a valid client certificate | **Applicable to** | Google CloudSQL PostgreSQL v2 database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | SSL configuration | | **Potential cause(s)** | The Google CloudSQL PostgreSQL instance is configured to require SSL to connect. This configuration isn’t currently supported, as it requires the database to expect client certifications. | | **Suggested action(s)** | Verify that the instance isn’t set to require SSL in Google Cloud. If it is, disable the setting and re-try the connection in Stitch. | [Back to PostgreSQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#postgresql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#) ### Missing replication slot ``` Unable to find replication slot 'stitch' nor 'stitch_[name]' with wal2json ``` `Unable to find replication slot 'stitch' nor 'stitch_[name]' with wal2json`Unable to find replication slot 'stitch' nor 'stitch\_[name]' with wal2json | **Applicable to** | PostgreSQL v2 database integrations | | --- | --- | | **Level** | Critical

the Remove icon

Data can't be replicated and intervention is required. Stitch will continue to re-try extraction based on the integration's schedule, but replication will not be successful until the issue is resolved. | | **Category** | [Log-based Incremental Replication](https://help.qlik.com/en-US/stitch/replication/replication-methods/log-based-incremental) | | **Potential cause(s)** | Stitch is unable to find a replication slot that adheres to [Stitch’s naming requirements](https://help.qlik.com/en-US/stitch/integrations/databases/postgresql/v2#create-replication-slot). | | **Suggested action(s)** | Verify that a replication slot exists for the database you’re trying to connect, and that it adheres to [Stitch’s naming requirements](https://help.qlik.com/en-US/stitch/integrations/databases/postgresql/v2#create-replication-slot). | [Back to PostgreSQL error list](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#postgresql-error-reference) [Back to top](https://help.qlik.com/en-US/stitch/troubleshooting/integrations/oracle-database-extraction-errors#)