Conflict Resolution fails to resolve conflict with ORA-1403 on update conflict when target row does not exist.
software bug with basic conflict resolution - The problem appears to be that we don't have any exception handling in place to trap (and ignore) the ORA-1403 generated by select * into new from <table> where <key-cols> = <key-values>
WORKAROUND:
Use generic conflict resolution instead.
STATUS:
Waiting for fix in a future release of Shareplex for Oracle
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy