One of my customers that recently upgraded to 12c hit a bug (22913528) that I think is good to be aware of. Note that as the title of this post states, the problem only occur in 184.108.40.206. At least, I wasn’t able to reproduce it in any other version.
To reproduce it you simply need a composite partitioned table with a non-partitioned or global-partitioned index. In other words, if all your indexes are local, you shouldn’t be impacted by the bug.
The SQL statements I use to prepare the schema to reproduce it are the following:
In the previous post in this series we provided some background context to our discussion of conflict handling in Dbvisit Replicate, by laying the platform for understanding how logical replication works. In this second instalment we will take a look at the options for manual resolution within the application, and then in the third, detail…