patternMinor
Can two transactions share the same SCN?
Viewed 0 times
canthesametwoscnsharetransactions
Problem
Do all transactions have a unique SCN? Can two transactions share an SCN?
I'm confused by this statement in the Oracle Golden Gate manual:
The CSN is cross-checked with the transaction ID (displayed as XID in Oracle GoldenGate informational output). The XID-CSN combination uniquely identifies a transaction even in cases where there are multiple transactions that commit at the same time, and thus have the same CSN. For example, this can happen in an Oracle RAC environment, where there is parallelism and high transaction concurrency.
https://docs.oracle.com/goldengate/1212/gg-winux/GWUAD/wu_csn.htm#GWUAD752
Table D-1 in that document identifies the GoldenGate CSN as being the Oracle DB SCN:
I'm confused by this statement in the Oracle Golden Gate manual:
The CSN is cross-checked with the transaction ID (displayed as XID in Oracle GoldenGate informational output). The XID-CSN combination uniquely identifies a transaction even in cases where there are multiple transactions that commit at the same time, and thus have the same CSN. For example, this can happen in an Oracle RAC environment, where there is parallelism and high transaction concurrency.
https://docs.oracle.com/goldengate/1212/gg-winux/GWUAD/wu_csn.htm#GWUAD752
Table D-1 in that document identifies the GoldenGate CSN as being the Oracle DB SCN:
Oracle GoldenGate CSN Values Per Database
Oracle: system_change_number
Where: system_change number is the Oracle SCN value.Solution
For single node Oracle RDBMS installations, an SCN is never duplicated.
With older versions of Oracle RAC, Oracle 9i for example, it was possible that two transactions, running on separate RAC nodes, could end up with the same SCN. Duplicates happened only in rare situations where high transaction rates on the RAC nodes was coupled with a large value for MAX_COMMIT_PROPAGATION_DELAY.
In Oracle RAC installations of version 11gR2 and later, RAC nodes coordinate changes to the SCN via a broadcast mechanism by default, essentially eliminating the possibility of a duplicate SCN.
With older versions of Oracle RAC, Oracle 9i for example, it was possible that two transactions, running on separate RAC nodes, could end up with the same SCN. Duplicates happened only in rare situations where high transaction rates on the RAC nodes was coupled with a large value for MAX_COMMIT_PROPAGATION_DELAY.
In Oracle RAC installations of version 11gR2 and later, RAC nodes coordinate changes to the SCN via a broadcast mechanism by default, essentially eliminating the possibility of a duplicate SCN.
Context
StackExchange Database Administrators Q#130278, answer score: 7
Revisions (0)
No revisions yet.