My Oracle Support Banner

TT16999 AND TT907 ERRORS on standby node if table has unique hash index (Doc ID 2423228.1)

Last updated on AUGUST 03, 2018

Applies to:

Oracle TimesTen In-Memory Database - Version 11.2.2.8.25 and later
Information in this document applies to any platform.

Symptoms

User has configured active standby pair replication using TT 11.2.2.8.25

If the create unique hash indexes on replicated table,they get 2 types of errors on standby Like this

TT16999: truncate table ctn=1507906950.1814548973

and like this :

TT16082: Table: ...Failed to update row <ID :            22707451> from master CACHEDB for 'End of transaction'

receiver.c(14719): TT907: TT0907: Unique constraint ... violated at Rowid<BMUFVUAAADetxQAEgd> -- file "hindex.c", lineno 2709, procedure"sbHixPushDupErr"

TT16187: Transaction: 1507906950.1815010471; Error: transient 0, permanent 1
state 2 error message :

The problem does not happen if they instead use unique range index.

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!


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