JADE now provides an SDS secondary commit‑consistent (coherent) backup mechanism, which enables you to create a backup of a secondary that when recovered, stops tracking and is in a commit‑consistent (coherent) state.
Error 3221
A new error message 3221 (SDS primary not connected) occurs when an operation is initiated that cannot proceed because the secondary is not connected to the primary. If this exception is raised, establish the connection between the secondary and the primary.
JadeDatabaseAdmin Class commitCoherentBackup Method
The JadeDatabaseAdmin class now provides the commitCoherentBackup method, which has the following signature.
commitCoherentBackup();
This method signals the successful completion of a database backup transaction on an SDS secondary. It arranges a database quiet point on the primary to establish commit‑consistent end backup recovery state that is stored in the database control file, which is then backed up to the default backup directory specified in the beginBackup method. Backup recovery stops tracking at end backup, saving replay state.
The commit‑consistent checkpoint processing on the primary performs a checkpoint within a database quiet point. The primary MaxWaitForQuietPoint value specified in the [PersistentDb] section of the JADE initialization file is used when waiting for the quiet point.
You may encounter an exception 3077 (Maximum time to wait for a quiet point was exceeded), in which case, the backup remains active and you can retry the commitCoherentBackup method call or you can call the abortBackup method. The backup terminates with the exception if it is unhandled. Other errors (for example, the 3221 (SDS primary not connected) or 3212 (SDS a response was not received within a reasonable timeframe) error) terminate the backup with that exception.