gflewis
commented
1 year ago This message suggests that the code successfully counted the number of records in the u_esm_ci_assoc table (228446) and then got an JSON parsing error while trying to read the first block of data records. My recommendation would be to turn debugging on and reduce the pagesize to a very small number to try to determine which row is failing. In my experience, this error generally occurs when there is a corrupted field in one of the records. It is usually a very large text field (more than 4000 bytes). If you can determine the sys_id of the corrupted record then you can use a filter to exclude it from the extraction. Corrupted records are rare, but I have seen cases where a single table had multiple corrupted records. SNDML cannot recover from a corrupt JSON payload. Since it cannot parse the payload, it cannot display the sys_id of the corrupt record. Unless your pagesize is 1, the displayed sys_id is unlikely to be the sys_id of the corrupt record. It is probably the sys_id of a different record which appeared earlier. Usually if you try to view the corrupted field via the ServiceNow UI in a form then the UI will either hang or get an error. Corrupted records are difficult to find and difficult to deal with. Another approach is to use increasing narrow creation date ranges in SNDML to eventually zero in on the 5 second interval when the record was created -- however, this is very time consuming as you can imagine. Another approach is to use a background script (javascript) to search for the corrupted record. Sometimes you can find them by searching for fields that are unexpectedly large or contain non-printing characters. Once you find the corrupted record you will likely conclude that it is useless, and the easiest thing may be to delete it using javascript.
SamoSlaus
We get followin error in logs: RestTableAPI [main] u_esm_ci_assoc PROCESS: getStats count=228446 query= Exception in thread "main" com.fasterxml.jackson.core.JsonParseException: Unexpected character ('}' (code 125)): was expecting a colon to separate field name and value at [Source: (String)"{"result":[{"sys_id":"000a51868779355083d10f6e8bbb35ed","sys_created_on":"2023-10-11 19:47:28","sys_updated_on":"2023-10-11