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


Using Messages With Identifiers : UX: DOB Checkpoint Tasks

UX: DOB Checkpoint Tasks
S6BUX001I
Starting spin job '%'
DOB Checkpoint Tasks
The spin job identified by the message has been started.
No action required.
S6BUX002E
Unable to start spin job; %, errno = %
DOB Checkpoint Tasks
The Data Object Broker was unable to start a spin job. The specific reason for the failure is indicated by the errno value that is part of this message, as well as the name of the function call that failed The most likely cause of failure is a shortage of memory or process entries in the system. It may also be the result of a configured limit on the number of processes.
The system administrator may be needed to help understand and fix the problem. Exceeding the configured limit on the number of processes may require updates to the kernel configuration.
S6BUX003E
Spin job '%' ended with exit code %
DOB Checkpoint Tasks
This message indicates the exit status of a spin job. In this case, the spin job terminated due to a an error. In order for messages from spin jobs to be included in the Data Object Broker log, the parameter STDERRTRACE in the crparm file must have the value YES.
Rerun the spin job by simply starting the script (spin01 or spin02) from the command line. If the job still fails, you should see more information about the nature of the problem.
S6BUX004E
Spin job '%' ended with signal %
DOB Checkpoint Tasks
This message indicates the exit status of a spin job. In this case, the spin job was terminated by a signal. Spin jobs do not normally use or expect signals, so it is likely that the signal was sent explicitly from the Object Service Broker system administrator's account, or from a user with root authority. If there is no explanation for the signal, this may indicate an internal Data Object Broker problem.
Rerun the spin job by simply starting the script (spin01 or spin02) from the command line. If the job fails, you should see information about the nature of the 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.
S6BUX005I
Spin job '%' ended
DOB Checkpoint Tasks
This message indicates the exit status of a spin job. In this case, the spin job completed successfully.
No action required.
S6BUX006I
journal % full, switching journals
DOB Checkpoint Tasks
During a spin job the journal identified in the message reached its capacity and another journal is now being used.
No action required.
S6BUX007E
Unable to use journal %, not emptied by spin job
DOB Checkpoint Tasks
The Data Object Broker is not able to use the journal because it was not emptied by the spin jobs as anticipated. 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.
S6BUX008E
Unable to write checkpoint to either journal
DOB Checkpoint Tasks
The Data Object Broker is unable to write a checkpoint into either journal, even after successfully switching journals. This problem may indicate that the journals have been defined to be too small and that the size of the checkpoint exceeds the size of either journal. If this explanation does not seem likely and there are no other problems indicated, this may indicate a Data Object Broker internal problem.
Reformat the journals. Ensure that both journals are large enough to handle at least one checkpoint. That means that the number of pages in each journal should be greater than or equal to the value of RESIDENTPAGES in the crparm file. 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.
S6BUX009W
Checkpoint request ignored, %
DOB Checkpoint Tasks
A checkpoint request was received or generated internally, but no updates have been processed due to the specified reason.
No action required.
S6BUX010I
Checkpoint begin, id=%, pages=%
DOB Checkpoint Tasks
A checkpoint started. The checkpoint number and number of pages are given in the message.
No action required.
S6BUX011E
Unable to complete checkpoint, page=% undefined
DOB Checkpoint Tasks
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.
S6BUX012I
Checkpoint end, id=%
DOB Checkpoint Tasks
The checkpoint was successful. The checkpoint number is given in the message.
No action required.
S6BUX013E
Unable to use journal %, contains unrecovered data
DOB Checkpoint Tasks
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.
S6BUX015E
Unable to complete checkpoint, not all data sets confirmed
DOB Checkpoint Tasks
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.
S6BUX016I
Spinning journal % on operator's request
DOB Checkpoint Tasks
The operator has issued command SPINSUBMIT to activate journal spin.
No action required.
S6BUX017E
Journal switch cannot be completed, journal % cannot be used
DOB Checkpoint Tasks
Journal switch activated by operator's command SPINSUBMIT cannot be completed, due to the fact that the other journal has not been emptied and therefore cannot be used online
Upon receipt of this message, administrator should try to execute corresponding batch spin job IMMEDIATELY (from the OS command line). Successful spin will reset journal file and SPINSUBMIT could be reapplied
S6BUX018I
DOB is now online - Redolog available for processing
DOB Checkpoint Tasks
The Data Object Broker is now recovered from a quiesced state.
No action is required.
S6BUX019I
Checkpoint deferred, previous checkpoint still in progress
DOB Checkpoint Tasks
Only one checkpoint can be executed at a time.
Wait until the current checkpoint is done.
S6BUX020I
CHECKPOINT MAXIMUM PAGES = ____, TRANSACTIONS =
DOB Checkpoint Tasks
This message is provided for informational purposes only and is issued to confirm the thresholds set for the maximum size of a Checkpoint.
No action is required.
S6BUX021W
PAGE LIMIT REDUCED - EXCEEDS 15% OF RESIDENT PAGES
DOB Checkpoint Tasks
The value specified for the CHPAGELIMIT initialization parameter must not exceed 15% of the Resident Page Directory as defined by the RESIDENTPAGES initialization parameter. The value of CHPAGELIMIT has been automatically reduced so as to conform to this requirement.
Adjust the CHPAGELIMIT parameter or the RESIDENTPAGES parameter or both so that this condition is addressed.
S6BUX022W
Parameter '%' REDUCED - INSUFFICIENT SPACE IN %
DOB Checkpoint Tasks
The value specified for the initialization parameter indicated by this message is too large to be supported by the redolog.
Adjust the indicated initialization parameter to relieve this condition, or increase the amount of space available to the redolog. Consult the Installation and Operations manual for further information.
S6BUX023E
Unable to determine the status of the spin job, errno = %d
DOB Checkpoint Tasks
This message indicates that during a journal switch we cannot figure out the status of the previous spin job. We have to wait to check the actual status of the journal file.
No action is required.
S6BUX024E
Path % specified by parameter 'SPINSHELL' is not accessible, errno = %
DOB Checkpoint Tasks
The SPINSHELL parameter specifies a path to a shell that is not readable or executable.
Do one of the following:
S6BUX027E
Error encountered %; % failure, error %
DOB Checkpoint Tasks
An internal Data Object Broker failure occurred with respect to the capturing of spin job output.
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.

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