invalid byte sequence for encoding "UTF8": 0x00 Call getNextException

  • KM03719032
  • 29-Sep-2020
  • 29-Sep-2020


This issue is not on troubleshooting guide from SDM Official documentation, and it is very strange one, so, due to this error is raised several cases today and no fix from product side, it is very helpful to pop it up for engineers to troubleshooting.


1.ERROR: current transaction is aborted, commands ignored until end of transaction block  Call getNextException to see other errors in the batch.

2.ERROR: invalid byte sequence for encoding "UTF8": 0x00  Call getNextException to see other errors in the batch.


There is a special invisible character in the string shown in the log file, in this case data has a field in a record (row) having an special character which extend the string long overpassing the limit.



Customer must check data out from table and field and rown being inserted given the issue, all taken from the log file you must to ask to customer for it.
Once you have that information, you look for the error and the table where process failed, there when the error is poped up, you will see the string having the errors, the error mention what is failing and the string having the issue, you send that information to customer in oder to review source data and take out avoiding special characters from that string and also good to check the all records in that table.
Your scope is determinate the record given the issue from run log file and let it to customer, customer will work it on with his DBA or with the right person origining data source in OLTP side.