Re: Question on NEXT_CHANGE#

From: Riyaj Shamsudeen <>
Date: Mon, 30 Dec 2013 11:56:02 -0800
Message-ID: <>

AFAIK, there are numerous actions that can allocate new SCNs, SCNs can be allocated with no redo records as well, and multiple redo records can be created at an SCN. Majority of those actions (that do not have redo associated) centered around control file accesses (as Jonathan pointed out). As a test, watch 'calls to kcmgas' statistics of a session and execute 'select * from v$database' from that watched session. You will see that every execution will increase that statistics.

BTW, kcmgas is the internal function to allocate new SCN. Another test would be compare the increase in the 'calls to kcmgas' statistic and number of unique SCNs in the archivelog file. In RAC, SCN allocation rate is higher to maintain cluster coherency.

SCN allocation rate increases sharply during hot backup too.


Riyaj Shamsudeen
Principal DBA,
Ora!nternals - - Specialists in Performance, RAC and EBS
Blog: Oracle ACE Director and OakTable member <>

Co-author of the books: Expert Oracle
Practices<> , Pro Oracle SQL, <> <>Expert
RAC Practices 12c. <> Expert PL/SQL practices <>


On Mon, Dec 30, 2013 at 9:00 AM, Phil Jones <> wrote:

> All,
> I think this all boils down to the usual question we're all asked when
> designing software/DB schemas.
> Do you want the numbers to be unique (with possible gaps) or truly
> sequential?
> The database is working correctly, probably using the missing scn numbers
> internally - it doesn't matter, but it would be interesting to know why.
> Cheers,
> Phil
> --

Received on Mon Dec 30 2013 - 20:56:02 CET

Original text of this message