I"m getting these errors on various tables that have a time stamp. When you print out the transaction, instead of seeing the old value (as you do for all the other columns) it only shows "sys.timestamp". This implies to me that apply is not getting the actual timestamp value in the LCR so it has nothing to compare as it attempts to apply it on the target. Here's an example of transaction that got this error. You can set the old value for the REC_CRTN_DT just says sys.timestamp instead of an actual value. Has anybody seen this before? I know I can use dbms_apply_adm.compare_old_values, but don't want to have to do this for every table that has a timestamp column in it.