...
Panel | ||
---|---|---|
| ||
DELETE from SCOTT."REQUESTS" and NAMES_PACEID = 1 and STATUSLASTMODIFIEDSTATUS_LASTMODIFIED = to_timestamp('2013.0806.2312 1713:3940:3818.788000000360000000', 'yyyy.mm.dd hh24:mi:ss.ff') Error: Command affected 0 row(s). |
Then this query can be turned into a SELECT statement that can be run manually on the target database:
Panel | ||
---|---|---|
| ||
SELECT * from SCOTT."REQUESTS" where (1=1) and NAMES_PACEID = 1 and STATUSLASTMODIFIEDSTATUS_LASTMODIFIED = to_timestamp('2013.0806.2312 1713:3940:3818.788000000360000000', 'yyyy.mm.dd hh24:mi:ss.ff') |
This query will also return 0 rows when it is run on the target as it has the same conditions as the delete statement which caused the conflict.
...
Panel | ||
---|---|---|
| ||
SELECT * from SCOTT."REQUESTS" where (1=1) and NAMES_PACEID = 1 and STATUSLASTMODIFIEDSTATUS_LASTMODIFIED = to_timestamp('2013.0806.2312 1713:3940:3818.788000000360000000', 'yyyy.mm.dd hh24:mi:ss.ff') |
If this now returns a record on the target database, then the data conflict is due to predicate that has just been removed. In this case "ACCEPTEDDATETIME"
...