public class SecondaryIntegrityException extends SecondaryReferenceException
The Transaction
handle is invalidated as a result of this
exception.
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 DPL
.
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.
Database
handle, 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.
Constructor and Description |
---|
SecondaryIntegrityException(com.sleepycat.je.txn.Locker locker,
String message,
String secDbName,
DatabaseEntry secKey,
DatabaseEntry priKey)
For internal use only.
|
Modifier and Type | Method and Description |
---|---|
OperationFailureException |
wrapSelf(String msg)
For internal use only.
|
getPrimaryKey, getSecondaryDatabaseName, getSecondaryKey
addErrorMessage, addRethrownStackTrace, getMessage, getVersionHeader
addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
public SecondaryIntegrityException(com.sleepycat.je.txn.Locker locker, String message, String secDbName, DatabaseEntry secKey, DatabaseEntry priKey)
public OperationFailureException wrapSelf(String msg)
wrapSelf
in class OperationFailureException
Copyright (c) 2002, 2015 Oracle and/or its affiliates. All rights reserved.