We’ve encountered several instances with Sybase ASE Capture Support where errors prevent the capture job from progressing beyond a problematic page. These issues effectively halt the process, leaving no straightforward recovery path.

We’d like to propose an enhancement that mirrors the flexibility available on the Integrate side—specifically, the ability to step over a problematic transaction sequence. If similar functionality could be introduced on the Capture side, it would be highly beneficial. Ideally, this would include:

• Reporting the affected page
• Attempting partial or full translation of the record’s columns and data
• Enabling targeted resynchronisation of the impacted row

This approach would significantly reduce the need for full data resyncs and allow us to limit recovery to only the affected rows, improving operational outages.

As you’re aware, our estate operates with truncate log on checkpoint and no transaction log backups, whilst also maintaining minimal log sizes. Given this setup, a mechanism for rapid recovery from capture-side errors would be greatly appreciated