Journal Analyzer-generated reverse statements for insert and update statements are delete and update statements, with a “where” clause on all columns that can be accepted in a where clause (column types such as “long varchar” cannot).

If you need two identical rows in which all columns can be part of a where clause (SQL does not normally distinguished such rows), the Recover dialog has an option (selected by default) called “Don’t Recover if >1 Row is Affected by an Individual Statement”. Only when this option is explicitly disabled does the recover process work even if more than one row is affected by an individual recover statement.

In the case where no row is affected by an individual “recover” statement, Journal Analyzer provides an error anyway, and the recover operation fails. If the Scan Journals to End option has not been disabled, Journal Analyzer normally warns you that rows involved already have changed since the initial transaction (different warnings appear if journaling has been disabled after the initial transaction or in similar situations).