Quietpoints and Long Transactions
The database considers a user's transaction to be have two states. A kernel Begin Transaction instantiates a transaction for the user, marking the user as being in kernel transaction state. When the database processes the first activity for the transaction (for example, a put), the user is transitioned to being in database (DB) transaction state. It is when this transition from kernel transaction state to DB transaction state occurs that the Begin Transaction is audited, if auditing is enabled.
An active transaction is a transaction in which the user has transitioned to DB transaction state.
A database quietpoint is a point at which there are no active transactions. Database quietpoints are required when:
-
Starting a non‑updating reorganization
-
Starting a reorganization on an SDS Primary system
-
Relinquishing the Primary role in an SDE negotiated takeover
-
Establishing a rollback point
-
A JadeDatabaseAdmin class commitCoherentBackup method call
-
Activating Delta mode
-
Creating one or more file partitions
-
Marking a file partition offline
-
Moving a non-frozen file partition
-
Starting the partitioning of a file
A system quietpoint is a point at which there are no users with transactions. System quietpoints are required when:
-
Database mode is changed to archive by beginning a quiesced backup
-
Database mode is changed to archive with JadeDatabaseAdmin class changeDbAccessMode method or a call to the jomChangeAccessMode Jade Application Programming Interface (API).
-
Database usage is changed to no audit
The
