This message indicates that there are transactions in the redolog that were not part of a checkpoint, due to an abnormal termination of the Data Object Broker. The Data Object Broker will attempt to reapply these transactions to the Pagestore to recover the consistency of the database.
The redolog has become completely filled while waiting for a checkpoint to complete. The Data Object Broker has been quiesced and will no longer process updates. This may result from an excessive volume of updates (with respect to the current configuration parameters) or from a delay in checkpoint processing. Checkpoint processing may be delayed due to a sudden volume of updates or because a spin job has failed.
Ensure that the any spin jobs have completed successfully. If a spin job has failed you can attempt to run it again by directly executing either the spin01 or spin02 scripts. Once the spin job has completed successfully, request a checkpoint with the CHECKPOINT operator command. After the checkpoint has completed successfully, use the RESUME operator command to bring the Data Object Broker back online.
A request to commit/abort an in-doubt transaction specified a slot this is empty or in use by another transaction. The most likely cause of this problem is "stale" data on an administrator's display. The in-doubt transaction may have been resolved automatically, aborted by a previous request not yet reflected on the display, or aborted by another administrator.
At startup, one or more in-doubt transactions were present in the contingency logs. An attempt to reacquire logical locks for a contingent transaction failed. A previous message may indicate the specific problem that occurred processing the lock request. This message may also indicate a Data Object Broker internal problem.
If you suspect that this is a Data Object Broker internal problem, contact TIBCO Support. Be prepared to submit a copy of the Data Object Broker log file and any core file produced as a result of this problem.
At startup, one or more in-doubt transactions were present in the contingency logs. This message indicates how many in-doubt transactions were successfully able to reacquire logical locks.
When applying changes to a Data Object Broker during restart following an abnormal termination, a transaction failed. To ensure integrity the Data Object Broker terminates with an error.