Bug 27092508  Flashback Queries Fails with ORA-08181 and/or ORA-01466 Due to Corrupted Timestamp Mappings in SYS.SMON_SCN_TIME

This note gives a brief overview of bug 27092508.

 The content was last updated on: 03-NOV-2021

Click here for details of each of the sections below.

Affects:

Product (Component)Oracle Server (Rdbms)Range of versions believed to be affectedVersions >= 12.1 but BELOW 18.1Versions confirmed as being affected

  • 12.2.0.1 (Base Release)
  • 12.1.0.2 (Server Patch Set)

Platforms affectedGeneric (all / most platforms affected)

Fixed:

The fix for 27092508 is first included in

  • 18.1.0
  • 12.2.0.1.190716 (Jul 2019) Database Jul2019 Release Update (DB RU)
  • 12.1.0.2.200114 (Jan 2020) Database Patch Set Update (DB PSU)
  • 12.1.0.2.191015 (Oct 2019) Database Proactive Bundle Patch
  • 12.2.0.1.190530 (May 2019) Bundle Patch for Windows Platforms
  • 12.1.0.2.200114 (Jan 2020) Bundle Patch for Windows Platforms

Interim patches may be available for earlier versions - click here to check.

Symptoms:

Related To:


  • ORA-08181 / ORA-01466




Description

This bug is only relevant when using Flashback Data Archive (Oracle Total Recall)

Memory corruption can occur in PDB as a result of corrupted timestamp mappings in SYS.SMON_SCN_TIME, causing one of two errors:

ORA-08181: specified number is not a valid system change number ORA-01466: unable to read data - table definition has changed

Rediscovery Notes If ORA-01466 or ORA-08181 is seen while running flashback queries this bug might be encountered.

Workaround NONE

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.

References

Bug:27092508​ (This link will only work for PUBLISHED bugs)Note:245840.1 Information on the sections in this article