Next_change# In V$log View Has Value Bigger Than Documented in 12.2
(Doc ID 2293471.1)
Last updated on JANUARY 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
On : 12.2.0.1 version, RDBMS
ACTUAL BEHAVIOR
---------------
next_change# in v$log view has value bigger than documented
According to the documentation for Oracle Database 12cR2, the NEXT_CHANGE# column in the V$LOG view is:
Highest change number (SCN) in the log. When
STATUS=CURRENT, NEXT_CHANGE# is set to the highest possible
SCN, <nnnnnnnnnnnn>.
However when we query the same view in an Oracle 12.2.0.1 database, the NEXT_CHANGE# was showing a value of 1.8447E+19. So either the documentation is wrong or the view is returning wrong value. Here's the output of v$version and v$log from our 12c database:
SQL> select BANNER from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
PL/SQL Release 12.2.0.1.0 - Production
CORE 12.2.0.1.0 Production
TNS for Linux: Version 12.2.0.1.0 - Production
NLSRTL Version 12.2.0.1.0 - Production
SQL> select FIRST_CHANGE#, NEXT_CHANGE#, STATUS from v$log;
FIRST_CHANGE# NEXT_CHANGE# STATUS
------------- ------------ ----------------
17517344 1.8447E+19 CURRENT
17247879 17407986 INACTIVE
17407986 17517344 INACTIVE
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |