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


Using Messages With Identifiers : KF: DOB Commit Task

KF: DOB Commit Task
S6BKF000E
INVALID TDS REQUEST
DOB Commit Task
Internal TDS server error. An unsupported request for service was received by the supervisory code. The transaction is aborted.
Contact TIBCO Support.
S6BKF001W
NO INLINE WRITES ALLOWED
DOB Commit Task
A request was received to write a page, but the request is illogical, reflecting an internal TDS server error.
Contact TIBCO Support
S6BKF003W
NO MESSAGES ALLOWED FROM SYNCH POINT
DOB Commit Task
Object Service Broker protocol error. A commit process is not permitted to have a dialog with an Object Service Broker user.
Contact TIBCO Support.
S6BKF004W
INVALID PAGE NUMBER SPECIFIED
DOB Commit Task
An invalid page number was requested. The transaction is aborted. Associated information is displayed through a generalized abort message.
Contact the Object Service Broker System Administrator. The error may indicate internal data corruption errors within certain index pages. Alternatively, several administrator-only tools do allow data access that bypass normal Object Service Broker navigation. The error may represent keying errors by the System Administrator.
S6BKF005W
PAGE POOL BUFFER ERROR
DOB Commit Task
Object Service Broker failed to obtain transient storage for this transaction.
Contact the Object Service Broker System Administrator and verify that Object Service Broker was configured to handle the current level of concurrency. Refer to the Installation and Operations manual for details.
S6BKF006W
ILLEGAL GET LOCK DURING SYNCH
DOB Commit Task
Protocol error. The COMMIT process is not allowed to acquire additional logical locks.
Contact TIBCO Support.
S6BKF008W
NO PAGE BUFFERS AVAILABLE
DOB Commit Task
No more page buffers are available.
Do one of the following:
Refer to the Installation and Operations manual for configuration options
S6BKF009W
NO FREE PAGES AVAILABLE IN SEGMENT
DOB Commit Task
The underlying Pagestore does not have any more free pages. Consequently new data cannot be stored in this segment.
Object Service Broker Pagestores must be regularly administered to ensure that sufficient space is available for the anticipated workload. Numerous tools are available to the System Administrator to manage the Pagestores and extend the public space available. Review the relevant documentation in the Application Administration manual.
S6BKF011W
PAGE NOT FOUND IN HOLD LIST
DOB Commit Task
Object Service Broker logic error. A page to be written was not held by the current transaction. The transaction is aborted with a snap dump.
Contact TIBCO Support.
S6BKF012E
ATTEMPT TO WRITE PAGE ZERO
DOB Commit Task
Object Service Broker logic error. The commit process attempted to overwrite a reserved page. The transaction is aborted with a snap dump.
Contact TIBCO Support.
S6BKF013W
TDS PAGE CONTROL VIOLATION
DOB Commit Task
Object Service Broker logic error. The commit process attempted to write invalid data. The transaction is aborted with a snap dump.
Contact TIBCO Support.
S6BKF014W
CTABLE SLOTS IN USE
DOB Commit Task
Refer to message S6BKA021W.
No action required.
S6BKF016W
TOO MANY BUFFERS REQUIRED
DOB Commit Task
The users exceeded the maximum number of buffers allowed for a session.
Do one of the following:
If the WORKINGSET Data Object Broker parameter is not at a maximum, consider increasing it to allow for more data and index pages to participate in the transaction.
S6BKF017W
INVALID FREE BUFFER ATTEMPT
DOB Commit Task
An attempt to free a buffer failed.
Contact the Object Service Broker System Administrator.
S6BKF018W
PAGE POOL BUFFER ERROR
DOB Commit Task
An attempt to free a page buffer failed.
Contact the Object Service Broker System Administrator.
S6BKF019E
INVALID HOLD LIST MANAGEMENT DIRECTIVE
DOB Commit Task
An invalid request was made of the routine that manages pages held for update. The transaction executing at the time this error is encountered abends.
This is an internal processing error and should be reported to TIBCO Support.
S6BKF020E
PAGE TO BE ADDED TO HOLD LIST ALREADY EXISTS
DOB Commit Task
The page being added to the list of pages held for update by this transaction was already in the list. The transaction executing at the time this error occurred will be aborted.
This is an internal processing error and should be reported to TIBCO Support.
S6BKF021E
DATA PAGE UPDATE LIMIT EXCEEDED, TRANSACTION ABORTED
DOB Commit Task
The current transaction attempted to access more Data pages then were permitted based on the DATAPAGELIMIT run time parameter.
The transaction is aborted. To avoid the problem either add an intermediate commit to the application or increase the DATAPAGELIMIT parameter value.
S6BKF025W
UNABLE TO OBTAIN HOLD LIST BUFFER
DOB Commit Task
While processing a commit request, the Data Object Broker was not able to obtain a buffer to contain the list of held pages. The failing transaction is aborted, and processing continues normally.
This problem will only occur when processing very large transactions which utilize external buffers for the held page list. The problem is that these buffers are a finite resource, and there are too many large transactions executing concurrently. Retry the failing transaction.
S6BKF026E
CANNOT UPDATE - REQUIRED SEGMENT IS IN READ ONLY MODE
DOB Commit Task
One or more of the segments required by this commit are in read only mode and cannot make the requested updates. The transaction is aborted.
If possible, change the mode of the required segment to read/write and rerun the failed transaction.
S6BKF028E
ATTEMPTED TO READ A PAGE THAT IS CURRENTLY FREE, SEG=____, PAGE=__
DOB Commit Task
The processing routine that services page reads determined that the requested page is indicated as a free page. These problems tend to be the results of dirty reads that occur when a query is accessing pages via an index where the index is in the process of being changed by another transaction.
Depending on your preceding actions, do one of the following:
If you were doing an administration function to view a page image, such as using option U from the Administration Menu, no action is required.
In all other situations, this message means that you have a corrupted segment. Do the following:
1.
2.
3.
Run S6BBRPTR (Batch Pointer Check utility) with the HDR option.
4.
Contact TIBCO Support, supplying the output from Pointer Check.
S6BKF029W
PAGESTORE SEGMENT NOT AVAILABLE
DOB Commit Task
The system requested a segment that is currently unavailable.
Contact the Object Service Broker System Administrator because the segment may be offline.
S6BKF030W
INVALID SEGMENT SPECIFIED
DOB Commit Task
A GETPAGE request was received with a segment number greater than the maximum number of segments defined.
Contact TIBCO Support.
S6BKF032W
DEADLOCK AVOIDANCE FAILED
DOB Commit Task
Deadlock avoidance logic was invoked and a request redriven. The redriven request was again intercepted by deadlock avoidance, and aborted as a result.
Requests are interfering with one another. Retry the request and contact TIBCO Support.
S6BKF033W
PAGE READ IS NOT PAGE REQUESTED
DOB Commit Task
Internal error.
Contact TIBCO Support.
S6BKF034W
TRANSACTION PAGE READ LIMIT EXCEEDED
DOB Commit Task
The transaction currently being processed by the Data Object Broker has read more pages from the Pagestore data sets than permitted by the Object Service Broker System Administrator. The transaction is aborted.
Contact the System Administrator to determine a method by which the transaction can be executed within the constraints of the Object Service Broker system. If needed, the TRXREADLIMIT can be adjusted to allow more pages to be read by a transaction.
S6BKF035W
RETRY LIMIT EXCEEDED, USER ________ BLOCK BY USER ________ ON TABLE
DOB Commit Task
During the processing of a transaction, an attempt to gain exclusive rights to a resource failed and the retry limit was exceeded. The transaction was not able to wait because it retained resources needed directly or indirectly by other transactions that held the resource the transaction was trying to obtain.
The transaction fails.
S6BKF036W
DBOFFLINE REQUEST DEFERRED, SEGMENT IN USE
DOB Commit Task
While validating a request to take a segment offline it was determined that one or more CTABLEs (table definition blocks) for tables resident on segment were still in use.
Segment offline processing is deferred until the CTABLEs are no longer required.
S6BKF037E
UNABLE TO OPEN SEGMENT, CACHE CAPACITY EXCEEDED
DOB Commit Task
The actions required to bring a segment online requires enough output processing to exceed the available space remaining in the checkpoint write-ahead log (CACHE). The segment online attempt was requested twice without success.
Try your request again. You should review your configuration; your cache may be too small.
S6BKF038W
PAGESWEEP LIMIT EXCEEDED, -user---, --- table name -,commarea, trx#
DOB Commit Task
The site specified a Page Sweep Limit to identify transactions that access more than a "threshold" number of pages. This message attempts to identify the user and transaction that exceeded the coded limit.
No action is required.
S6BKF039E
PAGE NOT FOUND IN HOLD LIST DURING PAGE FREE PROCESS
DOB Commit Task
When attempting to change a previously used page to a free page, it was determined that the page was not properly recorded in the internal control tables.
Contact TIBCO Support.
S6BKF041E
UNEXPECTED RESIDENT PAGE MANAGEMENT RESULT, TRANSACTION TERMINATED
DOB Commit Task
When processing a transaction the return code from the Resident Page Manager was unexpected in the given scenario. There is a very good chance that the cause of the problem is temporary.
Re-invoke the transaction after the abnormal transaction termination has completed.
S6BKF042E
RTUQTASK LOAD FAILED, INITIALIZATION TERMINATED
DOB Commit Task
During Data Object Broker initialization, a subtask (RTUQTASK) was not able to perform its initialization successfully. The Data Object Broker will fail during startup.
Review the joblog and contact TIBCO Support.
S6BKF043A
SYSTEM IS FROZEN AND CHECKPOINT REQUIRED FOR %
DOB Commit Task
During this period when the Object Service Broker system named is frozen, sufficient commit activity has occurred for a checkpoint to be necessary. No more commit processing will be performed until the system is UNFROZEN.
Verify that the system should remain frozen. To resume normal Object Service Broker processing, use the Unfreeze command.
S6BKF044I
LONG RUNNING TASK(S) IN PROGRESS FREEZE DELAYED 10 SECONDS FOR %
DOB Commit Task
A Freeze command was issued for the named Object Service Broker system. This command cannot execute until tasks that may span a checkpoint boundary are complete. Examples of such tasks are Clear Table, Building Secondary Indices, and Deleting Secondary Indices while the data is online.
The Freeze request will be retried in 10 seconds. You may list the long running tasks using the Status command.
S6BKF045A
FREEZE REQUEST CANCELLED FOR %
DOB Commit Task
The Freeze request has been delayed by long running tasks, but no work buffers are available to reschedule the request.
Contact the system administrator.
S6BKF046W
SYSTEM IS FROZEN AND CHECKPOINT % IS %% COMPLETE FOR %
DOB Commit Task
The system is FROZEN and the next checkpoint has completed to the indicated percentage. The commit will stop when this reaches 100%.
If possible, use the Unfreeze command to enable checkpoint processing to continue. Commit processing will stop when this checkpoint is full.
S6BKF047E
UNEXPECTED BWO STATE %
DOB Commit Task
During an attempt to open either a journal data set or a page data set, the BWO status was not one of the expected values.
Use IDCAMS to determine the BWO status and then find the reason for this status in the IBM DFSMS documentation. If you are still unable to resolve the problem, contact TIBCO Support.
S6BKF048E
BWO STATUS READ FAILED (%-%) %
DOB Commit Task
During an attempt to open a journal data set or a page data set, the read of the BWO failed with the indicated return/reason code for the indicated data set.
Use the IBM DFSMS documentation to determine the cause of the read failure. If you are still unable to resolve the problem, contact TIBCO Support.
S6BKF049E
BWO STATUS SET TO % FAILED (%-%) %
DOB Commit Task
While processing either a journal data set or a page data set, a request to set the BWO status failed with the indicated return/reason code for the indicated data set.
Use the IBM DFSMS documentation to determine the cause of this failure. If you are still unable to resolve the problem, contact TIBCO Support.
S6BKF050E
LOAD FAILED FOR BWO INTERFACE MODULE IGWABWO
DOB Commit Task
On a system with BWO support, the load for the BWO interface module IGWABWO failed.
Using the IBM documentation, determine the cause of the load failure and rectify it.
S6BKF051I
CURRENT BWO STATUS % % (%-%) %
DOB Commit Task
As a result of a BWOSTATUS command, this message is issued for online page and journal data sets that support BWO. The BWO status value appears, followed by the last action requested, with the return/reason code from this action, followed by the data set name. Where:
BWO_Status - is the BWO 3-byte status field maintained by IBM DFSMSdfp Advanced Services module IGWABWO. The contents of this field, bwo_flags, is described in the IBM DFSMSdfp documentation, part of the DFHSMS library.
BWO_Last_Action - this is an internal Object Service Broker BWO request function. Values are:
(return-reason code from this action) - see the IBM DFSMSdfp documentation for interpretation of IGWABWO Return and Reason Codes.
No action is required.
S6BKF052E
REDOLOG-1 USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATED
DOB Commit Task
The Redolog-1 user exit returned a nonzero return code in GPR 15. The Data Object Broker is terminated with a U320 abend.
Contact the Object Service Broker system administrator.
S6BKF053E
REDOLOG-2 USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATED
DOB Commit Task
The Redolog-2 user exit returned a nonzero return code in GPR 15. The Data Object Broker is terminated with a U320 abend.
Contact the Object Service Broker system administrator.
S6BKF054E
FILECHPT USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATED
DOB Commit Task
The File Management Checkpoint user exit returned a nonzero return code in GPR 15. The Data Object Broker is terminated with a U320 abend.
Contact the Object Service Broker system administrator.
S6BKF055E
TABLE @CRITICALMSGS IS NOT CORRECTLY DEFINED
DOB Commit Task
During Data Object Broker initialization, table @CRITICALMSGS was found to be incorrectly defined.
Contact the Object Service Broker system administrator to rectify the definition of @CRITICALMSGS.
S6BKF056E
@CRITICALMSGS IS NOT EMPTY
DOB Commit Task
During Data Object Broker initialization, table @CRITICALMSGS was found to contain critical system messages.
Contact the Object Service Broker system administrator, who should review the messages in table @CRITICALMSGS, take any action required, and then delete the messages from the table.
S6BKF057I
BWO NOT SUPPORTED FOR %
DOB Commit Task
As a result of a BWOSTATUS command, this message is issued for online page and journal data sets that do not support BWO where % is the data set name.
No action is required unless BWO should be supported for this data set. If BWO is required check that the data set is correctly allocated on a DASD device that supports BWO and is managed by DFSMS.
S6BKF099I
TRANSACTION REQUEUED
DOB Commit Task
Deadlock avoidance logic has been invoked and a request redriven. The transaction is rolled back and retried with the expectation that any deadlock will be resolved on the subsequent attempt.
No action required.

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