![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Internal TDS server error. An unsupported request for service was received by the supervisory code. The transaction is aborted.A request was received to write a page, but the request is illogical, reflecting an internal TDS server error.Object Service Broker protocol error. A commit process is not permitted to have a dialog with an Object Service Broker user.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.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.Protocol error. The COMMIT process is not allowed to acquire additional logical locks.
• Refer to the Installation and Operations manual for configuration options
• Change the Object Service Broker startup parametersThe 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.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.Object Service Broker logic error. The commit process attempted to overwrite a reserved page. The transaction is aborted with a snap dump.Object Service Broker logic error. The commit process attempted to write invalid data. The transaction is aborted with a snap dump.The users exceeded the maximum number of buffers allowed for a session.
• Shorten the transaction by issuing more intermediate commits.
• 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.Contact the Object Service Broker System Administrator.An attempt to free a page buffer failed.Contact the Object Service Broker System Administrator.INVALID HOLD LIST MANAGEMENT DIRECTIVEAn 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.PAGE TO BE ADDED TO HOLD LIST ALREADY EXISTSThe 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.DATA PAGE UPDATE LIMIT EXCEEDED, TRANSACTION ABORTEDThe 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.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.CANNOT UPDATE - REQUIRED SEGMENT IS IN READ ONLY MODEOne 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.ATTEMPTED TO READ A PAGE THAT IS CURRENTLY FREE, SEG=____, PAGE=__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:
2. Run S6BTLBPS (Back Up Page Data Sets utility).
3. Run S6BBRPTR (Batch Pointer Check utility) with the HDR option.
4. Contact TIBCO Support, supplying the output from Pointer Check.The system requested a segment that is currently unavailable.Contact the Object Service Broker System Administrator because the segment may be offline.A GETPAGE request was received with a segment number greater than the maximum number of segments defined.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.TRANSACTION PAGE READ LIMIT EXCEEDEDThe 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.RETRY LIMIT EXCEEDED, USER ________ BLOCK BY USER ________ ON TABLEDuring 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.DBOFFLINE REQUEST DEFERRED, SEGMENT IN USEWhile 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.UNABLE TO OPEN SEGMENT, CACHE CAPACITY EXCEEDEDThe 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.PAGESWEEP LIMIT EXCEEDED, -user---, --- table name -,commarea, trx#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.PAGE NOT FOUND IN HOLD LIST DURING PAGE FREE PROCESSWhen 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.UNEXPECTED RESIDENT PAGE MANAGEMENT RESULT, TRANSACTION TERMINATEDWhen 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.RTUQTASK LOAD FAILED, INITIALIZATION TERMINATEDDuring 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.SYSTEM IS FROZEN AND CHECKPOINT REQUIRED FOR %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.LONG RUNNING TASK(S) IN PROGRESS FREEZE DELAYED 10 SECONDS FOR %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.The Freeze request has been delayed by long running tasks, but no work buffers are available to reschedule the request.SYSTEM IS FROZEN AND CHECKPOINT % IS %% COMPLETE FOR %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.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.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.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.LOAD FAILED FOR BWO INTERFACE MODULE IGWABWOOn 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.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.
• {datasetname} - the Object Service Broker data set being processed.REDOLOG-1 USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATEDThe 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.REDOLOG-2 USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATEDThe 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.FILECHPT USER EXIT FAILURE DETECTED, DOB ABNORMALLY TERMINATEDThe 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.TABLE @CRITICALMSGS IS NOT CORRECTLY DEFINEDDuring 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.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.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.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.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |