System change number (SCN) not an internal timestamp for a committed version- Oracle Transaction

Q.  A system change number (SCN) is not an internal timestamp for a committed version of the database.
- Published on 19 Oct 15

a. True
b. False

ANSWER: False

Related Content

 

    Discussion

  • Nirja Shah   -Posted on 23 Sep 15
    - A system change number (SCN) is an internal timestamp for a committed version of the database.

    - The Oracle Database server uses the SCN clock value to guarantee transaction consistency.

    - For example, when a user commits a transaction, the database records an SCN for this commit in the redo log.

    - The database uses SCNs to coordinate distributed transactions among different databases.

    - For example, the database uses SCNs in the following way:

    1. An application establishes a connection using a database link.
    2. The distributed transaction commits with the highest global SCN among all the databases involved.
    3. The commit global SCN is sent to all databases involved in the transaction.

➨ Post your comment / Share knowledge


Enter the code shown above:

(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)
▲