What about specifying partition
A reader, October 13, 2019 - 4:23 pm UTC
This video does not answer the very question.
What if my merge include the FOR PARTITION key?
Eg Merge into T partition for (myKey) tgt....
This will avoid ora-08103?
October 21, 2019 - 7:05 am UTC
I'm curious as to why you are joining on *rowid*. That is not necessarily immutable - rowid's can and do change, which can lead to your issue.
What about specifying partition
A reader, October 13, 2019 - 4:23 pm UTC
This video does not answer the very question.
What if my merge include the FOR PARTITION key?
Eg Merge into T partition for (myKey) tgt....
This will avoid ora-08103?
Not relevant to the question
A reader, October 21, 2019 - 8:46 am UTC
"
I'm curious as to why you are joining on *rowid*"
the is no such word in my question.
When a merge start to do some update and another session say try to delete some partitions that NOT concerning the one of the Merge then we can encounter such error. My question is could we avoid it by SPECIFYING the FOR PARTITION ?
October 21, 2019 - 11:36 am UTC
and another session say try to delete some partitions
Well...isn't it nice that you decide to suddenly share THAT piece of information.
If *any* part of your merge processing touches a partition that has been relocated/dropped/etc, then you run the risk.
This could be the *target* or the *source*