26-05-2020
10:48 AM
- last edited on
19-06-2020
03:26 PM
by
exa-Vandana
What does ist mean when there is a row with CONFLICT_TYPE = 'SCHEMA CONFLICT' in EXA_STATISTICS_VIEWS.EXA_DBA_TRANSACTION_CONFLICTS?
Solved! Go to Solution.
27-05-2020 09:35 AM - edited 27-05-2020 09:36 AM
Hi Evgeny,
that is something that should rarely happen. If you create a schema object like a table, others could do the same from other sessions. That's no problem as long as there is no attempt to create two objects with the same name. One possible scenario: You turn autocommit off in one session, then create table t there without commit. Another session creates table t in the same schema. Now you try to commit in the first session. That causes a schema conflict. If both session were on autocommit ON , the first create table t succeeds and the second fails with the normal error message.
27-05-2020 09:35 AM - edited 27-05-2020 09:36 AM
Hi Evgeny,
that is something that should rarely happen. If you create a schema object like a table, others could do the same from other sessions. That's no problem as long as there is no attempt to create two objects with the same name. One possible scenario: You turn autocommit off in one session, then create table t there without commit. Another session creates table t in the same schema. Now you try to commit in the first session. That causes a schema conflict. If both session were on autocommit ON , the first create table t succeeds and the second fails with the normal error message.
Then it's time to become part of a unique family! Discover helpful tips and support other Community members with your knowledge.
Sign In