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.
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.
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.
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.
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.
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
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 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.
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.