Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages With Identifiers : UR: DOB

UR: DOB
S6BUR001E
Unable to allocate % bytes from system heap
DOB
The system has a temporary shortage of real memory.
If this problem occurs regularly, your system administrator should address the resource shortage in terms of system load, system configuration, and machine capacity.
S6BUR002W
Redo recovery started
DOB
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.
No action is required.
S6BUR003E
Redo transaction out of sequence, checkpoint=%, commit=%
DOB
This message may indicate 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.
S6BUR004I
Redo recovery successful, commit=%
DOB
The transactions found in the redolog at startup have been reapplied to the Pagestore.
No action is required.
S6BUR005E
Redo recovery failed
DOB
A failure occurred while reading transactions from the redolog during redo recovery. A previous message should indicate the specific problem.
Review the previous messages to determine the appropriate actions to take.
S6BUR006I
Data Object Broker quiesced, redo log space shortage
DOB
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.
S6BUR008E
Unable to initialize European language support
DOB
This message may indicate 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.
S6BUR009E
Unable to initialize lock manager
DOB
This message may indicate 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.
S6BUR010E
Unable to free locks for contingent transaction, slot=%, transaction=%
DOB
This message may indicate 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.
S6BUR011W
Request to abort/commit contingent transaction ignored, transaction not found, slot=%, transaction=%
DOB
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.
Have the administrator refresh the data that is being displayed.
S6BUR012W
Unable to reacquire logical locks for contingent transaction, slot=%,transaction=%
DOB
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.
S6BUR013I
Logical locks reacquired for % contingent transactions
DOB
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.
No action required.
S6BUR014E
DOB restart processing failed due to redo transaction failure
DOB
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.
Contact TIBCO Support.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved