My Oracle Support Banner

Global Transaction Identifier hash collision risk with very similar Global Transaction ID (Doc ID 2016166.1)

Last updated on DECEMBER 20, 2022

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

The alert.log has multiple occurrences of the following messages:

Global transaction identifier hash collision detected.
in_gti:  57415344.0000014C1163D2510000000230AF8B3CDE0C8BC0A6F313F4B7C369F845C0F62CB53A47D7
dx_gti: 57415344.0000014C1163D2510000000230AF8B2CDE0C8BC0A6F313F4B7C369F845C0F62CB53A47D7

And the difference in the Global Transaction ID is only 1 or 2 characters

Changes

 

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
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.