How to solve "errorCode": "2200", "message": "Failure happened on 'Sink' side. Parameter 13

Question

Hello.

We are trying to move information from an on-premise SQL database to an Oracle database in the cloud through Microsoft Synapse Analytics, our batch is 10,000 records and it always falls on record 20,000 with the error:

{     "errorCode": "2200",     "message": "Failure happened on 'Sink' side. ErrorCode=UserErrorOdbcOperationFailed,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][ODBC Oracle Wire Protocol driver]Data type for parameter 13 has changed since first SQLExecute call.,Source=Microsoft.DataTransfer.ClientLibrary.Odbc.OdbcConnector,''Type=Microsoft.DataTransfer.ClientLibrary.Odbc.Exceptions.OdbcException,Message=ERROR [HY000] [Microsoft][ODBC Oracle Wire Protocol driver]Data type for parameter 13 has changed since first SQLExecute call.,Source=msora28.dll,'",     "failureType": "UserError",     "target": "BI_SINIESTROS_PRUEBA",     "details": [] }

Answer 1

The error message "Data type for parameter 13 has changed since first SQLExecute call" from ODBC Oracle Wire Protocol driver indicates an inconsistency in the data types of the records for a particular field (parameter 13 in this case) between different batches. Here are some steps you could take to diagnose and potentially fix the issue: Check Data Consistency: Inspect your input data, especially the column corresponding to parameter 13. The data type should be consistent across all rows. If some fields change data types partway through, that would cause this error. Cast Column Types: Ensure that the columns in your data pipeline have explicit and correct data types defined. You can do this by adding a 'Select' transformation in your Synapse pipeline and cast the column to the desired type. Ingestion Settings: Consider adjusting the batch size, reducing it from 10,000 to a smaller number might avoid the issue if there is some limitation or constraint on the Oracle side. Update Drivers: Ensure that your Oracle drivers are up-to-date. This could be applicable if there was a known bug with the version of the ODBC driver that you're using.

Please note that these suggestions are based on general practices and may not directly solve your problem without further diagnosis. If your problem persists after taking these steps into consideration, I recommend reaching out to Microsoft Support, providing them with the error message, and detailing the steps you've taken so far to resolve the issue. They should be able to provide more targeted assistance for your specific setup and situation.