public class SecondaryIntegrityException extends SecondaryReferenceException
Transaction handle is invalidated as a result of this
exception. In addition, the corrupt index (secondary database) is marked
as corrupt in memory. All subsequent access to the index will throw
SecondaryIntegrityException. To correct the problem, the
application may perform a full restore (an HA
NetworkRestore or restore from backup) or rebuild
the corrupt index.
Some possible causes of a secondary integrity exception are listed
below. Note that only the first item -- the use of a non-transactional
store -- is applicable when using the
All other items below do not apply to the use of the DPL, because the DPL
ensures that secondary databases are configured and managed correctly.
Databasehandle, or by truncating or removing primary database without also truncating or removing all secondary databases. When the DPL is not used, the application is responsible for managing associated databases correctly.
getExpirationTime, getPrimaryKey, getSecondaryDatabaseName, getSecondaryKey
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
Copyright (c) 2002, 2017 Oracle and/or its affiliates. All rights reserved.