|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
A path name, supplied as an argument for a command line option, is longer than the expected maximum length.Invalid parameter override, longer than % charactersThe length of a parameter override string exceeds the maximum length expected.Use abbreviated parameter names to shorten the length of the command line parameter override.An option encountered on the command line was not of the form -X, where X is a single character. The user may have attempted to combine options (not supported) or may have omitted the white space between the option and the option argument.Using the explanation as a guide, enter the option correctly.The option specified is not supported by this command.The option specified on the command line expects an argument to follow. The expected argument was missing from the command line.The user has specified more arguments on the command line than were expected.While scanning a configuration file or a command line argument, an invalid keyword was encountered. A subsequent message may identify where the problem occurred.The device is either full or otherwise unavailable.The system administrator should first check the status of the file and of the file system. If the problem recurs, contact Support.Invalid parameter value for '%', range for integer is % to %While scanning a configuration file or a command line parameter override, an integer value was encountered that was out of the expected range for that value. A subsequent message should identify where the problem occurred.Correct the value so that it falls within the expected range.Invalid parameter value for '%', must be % to % characters in lengthWhile scanning a configuration file or a command line parameter override, a parameter value was encountered that was shorter or longer than expected. A subsequent message should identify where the problem occurred.Correct the parameter value so that its length falls within the expected range.A problem was encountered while scanning a command line parameter override. A previous message should have identified the specific problem.Review the previous messages to determine the appropriate actions to take.A file system error occurred while attempting to open the file.Ensure that the file exists and that its access permissions enable it to be read.A file system error occurred while reading from the file.Verify that file is a valid text file and that it has not been damaged somehow.A line in the file was longer than the expected maximum length.Edit the file to ensure that the lengths of all the lines are within the limit specified.An error was encountered while scanning the file. A previous message should indicate the specific problem.A file system error occurred while closing the file.Unable to determine path from environment variable 'HURON' or '-h' optionThe HURON environment variable has not been set and no override was supplied on the command line.Ensure that the HURON environment variable is properly set, or indicate the installation path on the command line with the -h option.During the format of a page file, control information was written to the file but it cannot be read or it cannot be verified.A previous error may indicate a more specific problem. Otherwise this error would seem to indicate an I/O error on the disk.Upon opening a page file, the control information was unable to be read or unable to be verified. A previous message should indicate a more specific problem.Review previous messages to determine the appropriate actions to take.The system has a temporary shortage of real memory.If this problem occurs regularly, the system administrator needs to address the resource shortage in terms of system load, system configuration, and machine capacity.An attempt to lock a journal for formatting failed because the journal is already in use by the Data Object Broker or by another Object Service Broker utility.If the Data Object Broker is running it should be stopped to format either journal. If the journal is being used by another Object Service Broker utility then you must wait for the utility to finish.Unable to use journal %, control information unreadableAn attempt to open a journal failed because control information at the beginning of the journal is not valid. This is likely due to a loss of data on the disk.Refer to the Object Service Broker Backup and Recovery for Windows and Solaris manual.An attempt to open a journal failed because the journal is already in use by the Data Object Broker or by an Object Service Broker utility.If the Data Object Broker is running then the journal cannot be used until the Data Object Broker shuts down or a journal spin occurs. If the journal is being used by an Object Service Broker utility then you must wait for the utility to finish before starting the Data Object Broker or running another utility.An attempt to open a journal failed because the journal has not been formatted.The Resident Page/CTABLE Manager has run out of handles for pages/CTABLEs. 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.The Resident Page Manager has temporarily run out of buffers for pages. This is likely due to a burst of update activity that consumed buffers faster than they could be written to disk, or a transaction that attempted to update more buffers than the Resident Page Manager contained.Consider increasing the value for the RESIDENTPAGES Data Object Broker parameter. Consult the Backup and Recovery manual.Unable to begin checkpoint, previous checkpoint in progressAn internal Data Object Broker request to start a new checkpoint has failed because a checkpoint is already in progress. 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.Unable to create semaphore, IPC key=%, num=%, perm=%An attempt to create a semaphore failed. The specific reason for the failure is indicated by the error number value that should be part of this message.The most likely causes of failure are either a shortage of defined semaphores, or an IPC key conflict with another application.The system administrator may be needed to help understand and fix the problem. A shortage of defined semaphores will require updates to the Solaris kernel configuration. A conflict with another application may require that a new IPC key be chosen for this Data Object Broker and the HCS configuration file updated.An attempt to remove a conflicting but unused semaphore has failed. The specific reason for the failure is indicated by the errno value that should be part of the message. A likely cause of the problem is that the semaphore in question was created by a different userid.The system administrator may be needed to help understand and fix the problem. To remove a semaphore manually the ipcrm command can be used, assuming the user has the authority to do so.An attempt to remove a semaphore has failed. The specific reason for the failure is indicated by the errno value that should be part of this message.The system administrator may be needed to help understand and fix the problem. To remove a semaphore manually the ipcrm command can be used, assuming the user has the authority to do so.Unable to create shared memory, IPC key=%, size=%, perm=%An attempt to create shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of this message. The most likely causes of failure are either a shortage of defined shared memory, a size that exceeds system configured limits, or an IPC key conflict with another application.The system administrator may be needed to help understand and fix the problem. A shortage of defined shared memory or a size problem will require updates to the kernel configuration.A conflict with another application may require that a new IPC key be chosen for this Data Object Broker and the HCS configuration file updated.An attempt to remove conflicting but unused shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of the message. A likely cause of the problem is that the shared memory in question was created by a different userid.The system administrator may be needed to help understand and fix the problem. To remove shared memory manually the ipcrm command can be used, assuming the user has the authority to do so.Unable to attach shared memory, IPC key=%, address=%, flags=%An attempt to attach shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of the message. The likely causes of the problem are either an invalid value for the Data Object Broker parameter SHAREDMEMADDR, or two Data Object Brokers on the same system that are peers and that have the same value for SHAREDMEMADDR.The system administrator may be needed to help understand and fix the problem. If the problem is due to an invalid SHAREDMEMADDR value, consult the Installation and Operations manual.Normally the default for SHAREDMEMADDR works on any system. If the problem is related to peer Data Object Brokers on the same system, change the SHAREDMEMADDR parameter for one of the Data Object Brokers.Add a multiple of SHAREDMALIGN to generate a new SHAREDMEMADDR value.An attempt to use a semaphore has failed. The specific reason for the failure is indicated by the errno value that should be part of the message. A likely cause of the problem is a shortage of defined semaphore undo structures in the system.The system administrator may be needed to help understand and fix the problem. A shortage of defined semaphore undo structures will require updates to the kernel configuration. Otherwise the 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.An attempt to get shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of the message.The system administrator may be needed to help understand and fix the problem.Unable to attach shared memory, unrecognized header, IPC key=%Shared memory was attached but it was not identifiable as Object Service Broker shared memory. This problem may indicate an IPC key conflict with another application.The system administrator may be needed to help understand and fix the problem. If the problem is due to an IPC key conflict a new IPC key must be chosen for this Data Object Broker and the HCS configuration file updated.The specific reason for the failure is indicated by the errno value that should be part of the message.The system administrator may be needed to help understand and fix the problem.Unable to remove conflicting shared memory, in use by other processes, IPC key=%A shared memory remnant cannot be removed because one or more processes are still attached to it. This may indicate an IPC key conflict with another application. The most likely explanation, however, is that the Data Object Broker had been killed or had abended without the opportunity to clean up.Use the command "hrncr kill" to force a clean up of all Data Object Broker processes and shared resources. If the same problem occurs, use the ipcrm command to remove the conflicting shared memory manually.You are trying to use an Object Service Broker file formatted for one type of Object Service Broker data as the type of Object Service Broker data specified in the message (e.g., a Journal file is being accessed as if it were a page file of the segment).An attempt to detach shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of the message.The system administrator may be needed to help understand and fix the problem. Otherwise contact TIBCO Support.An attempt to detach shared memory has failed. The specific reason for the failure is indicated by the errno value that should be part of the message.The system administrator may be needed to help understand and fix the problem. Otherwise contact TIBCO Support.Unable to initialize page manager, check parameters 'RESAGE' and 'RESIDENTPAGES'The Resident Page Manager failed to initialize. The most likely problem is invalid values for the parameters mentioned. RESIDENTPAGES must be at least 3. RESAGE must not be greater than RESIDENTPAGES.Verify the parameter settings in the Data Object Broker parameter file. Adjust the values if necessary. If the parameter values are valid and the problem persists, contact TIBCO Support.Unable to initialize CTABLE manager, check parameters 'CTABLESIZE', 'CTABAGE', and 'CTABRESIDENT'The Resident CTABLE Manager failed to initialize. The most likely problem is invalid values for the parameters mentioned. CTABRESIDENT must be at least 3. CTABAGE must not be greater than CTABRESIDENT. CTABLESIZE must be a multiple of 4.Verify the parameter settings in the Data Object Broker parameter file. Adjust the values if necessary. If the parameter values are valid and the problem persists, contact TIBCO Support.An entry in the dbdef file is missing a required attribute like NAME or TYPE. A subsequent message should identify where the problem occurred.An entry in the dbdef file for the redolog or a journal contained an unnecessary attribute.Identifies the line at which an invalid entry was detected. A previous message should indicate the specific problem encountered.Maximum number of database definitions read (%) at line % of file '%'The dbdef file contains more than 260 entries. Since there can be 256 segments defined, a contingency log, a redo log, and two journals, there can be no more than 260 definitions in the dbdef file.Remove any extra or duplicate entries in the dbdef file.Two of the entries in the dbdef file have the same NAME attribute.Ensure that each entry in the dbdef file has a unique NAME attribute.Two of the segments defined in the dbdef file have the same ID attribute. If an ID is not explicitly assigned then it defaults to 0.Ensure that each segment defined in the dbdef file has a unique ID attribute and that only the MetaStor segment has ID 0.More than one redolog, contingency log, or set of journals has been defined in the dbdef file.A required database definition is missing in the dbdef file.The segment must be defined as TYPE=PAGE.Change the TYPE attribute of the database definition to PAGE.The segment must be defined with INIT=YES.Change the INIT attribute of the database definition to YES.The segment is not defined in the dbdef file. If the dbdef file has been changed while the Data Object Broker is running, it must be restarted before the changes take effect.The segment is not defined in the dbdef file. If the dbdef file has been changed while the Data Object Broker is running, it must be restarted before the changes take effect.Unable to vary segment '%' offline, segment required for system operationA request was made to vary segment 0 offline. Segment 0 is required to be online at all times while the Data Object Broker is running.An attempt to lock the redolog for formatting failed because the redolog is already in use by the Data Object Broker or by another Object Service Broker utility.If the Data Object Broker is running it should be stopped to format the redolog. If the redolog is being used by another Object Service Broker utility then you must wait for the utility to finish.The redolog contains an invalid checkpoint sequence and the Data Object Broker cannot determine the last valid commit. This is likely due to a loss of data on the disk.Consult the Backup and Recovery manual.Unable to use redo log, required page unreadableThe redolog cannot be read due to a loss of data on the disk.Consult the Backup and Recovery manual.An attempt to open the redolog failed because the redolog is already in use by the Data Object Broker or by an Object Service Broker utility.If the Data Object Broker is running then the redolog cannot be used until the Data Object Broker shuts down. If the redolog is being used by an Object Service Broker utility then you must wait for the utility to finish before starting the Data Object Broker or running another utility.An attempt to open the redolog failed because the redolog has not been formatted.Unable to read redo log, inconsistent page header infoThe redolog contains at one or more pages with invalid data and the Data Object Broker cannot determine the last valid commit. This is likely due to a loss of data on the disk.Consult the Backup and Recovery manual.The redolog contains a committed transaction that exceeds the maximum configured message size.Adjust the MSGSIZE parameter in the crparm file. Normally this value should be 32 (for 32 KB).The redolog contains a committed transaction that exceeds the maximum configured message size.Adjust the MSGSIZE parameter in the crparm file. Normally this value should be 32 (for 32 KB).Unable to write to redo log, message size exceeds % bytesAn attempt to write a transaction to the redolog has failed. The size of the transaction message exceeds the maximum configured message size.Adjust the MSGSIZE parameter in the crparm file. Normally this value should be 32 (for 32 KB).An attempt to write a transaction to the redolog has failed. There is insufficient space in the redolog to write the transaction.Unable to confirm checkpoint % in redo log, out of sequenceAn attempt to release transactions in the redolog has failed. If this problem occurs during start up then it likely indicates that the journals and the redolog are out of sync, i.e., the journals were formatted but not the redolog. If this problem occurs after the Data Object Broker is online then it indicates an internal logic error.If the problem is due to a journal/redolog mismatch then format the redolog using the hrntlfrl utility. Otherwise 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.An attempt to open a segment failed because the segment is already in use by the Data Object Broker or by an Object Service Broker utility.If the Data Object Broker is running then the segment cannot be used until the Data Object Broker shuts down. If the segment is being used by an Object Service Broker utility then you must wait for the utility to finish before starting the Data Object Broker or running another utility.An attempt to open a segment page file failed. A previous message should indicate the specific problem encountered.Review previous messages to determine the appropriate actions to take.The segment identified cannot be closed.Reenter the command when the segment becomes available.A problem occurred while attempting to close a page file in a segment. A previous message may indicate a more specific problem.No action required. If there are other related messages there may be actions indicated for these messages.An attempt to lock a segment page file for formatting failed because the page file is already in use by the Data Object Broker or by another Object Service Broker utility.If the Data Object Broker is running it should be stopped to format the page file. If the page file is being used by another Object Service Broker utility then you must wait for the utility to finish.The segment identified cannot presently be accessed.An attempt to access a page in a segment failed. The page number is larger than the number of pages in the page file.The problem may be caused by a request from a user (using either hrntladm or @PAGE) to see a page that is undefined, in which case it can be ignored. Otherwise the 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.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.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.An attempt to allocate a new page in a segment failed. The segment is completely full.The solution to this problem is to expand the size of the segment, either by adding additional page files, or expanding the existing page files. If this problem resulted from defining or adding data to a table, you may consider defining or moving the table to another segment that has sufficient space. Otherwise, refer to the Application Administration manual.Unable to complete checkpoint, segment '%' offline or in useThis 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.Unable to complete checkpoint, page=% undefinedThis 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.Review the previous messages in the Data Object Broker log to determine the appropriate actions to take.TDS used all the available working set buffers while processing a request.Increase the value for the WORKINGSET parameter in the crparm file.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.TDS used all its available heap while processing a request.Increase the value for the HEAPSIZE parameter in the crparm file.An error occurred during the construction of a CTABLE. A previous error message may indicate the specific problem. This error may indicate that certain critical tables have inconsistent or invalid data in them.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.An error occurred during the construction of a CTABLE. A previous error message may indicate the specific problem. This error may indicate that certain critical tables have inconsistent or invalid data in them.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.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.Unable to get free page during phase 1, segment=%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.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.A request to read a page from a page file has failed.Look for any previous error messages that may indicate the specific problem.Three or more transactions, proceeding in parallel, have shown signs of possible deadlock over physical page contention. During sync processing a transaction which holds pages that other transactions are waiting for, may not itself wait for pages. The transaction that fails is automatically retried once. If deadlock avoidance fails the transaction a second time then it is aborted. This problem should rarely occur under normal circumstances.If this message is seen frequently in the Data Object Broker log, it may require a change in one or more of the applications that may be running. Even an application with hot spots should experience this problem only while processing a high volume of transactions.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.Unable to put/free page, inconsistent header informationThis 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.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.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.A commit request could not be written to the redolog.Look for any previous error messages that may indicate the specific problem.Indicates that a transaction has been committed. The tracing of commits is controlled by the parameter SYNCTRACE in the Data Object Broker parameter file.Indicates that part of a transaction has committed. The tracing of commits is controlled by the SYNCTRACE parameter in the Data Object Broker parameter file.Unable to use Data Object Broker shared memory, abend or invalid state detectedA Data Object Broker process has attached to a running Data Object Broker, but the state of the Data Object Broker indicates that it is abending or is invalid.This message may simply indicate that a Data Object Broker process attempted to start up just as the Data Object Broker had failed. If the Data Object Broker is running and this problem occurs, the Data Object Broker may be "hung" while trying to stop or abend.Use the command "hrncr kill" to ensure that all Data Object Broker processes are stopped and that all shared resources are cleaned up.If the problem persists, 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.Unable to initialize IPC resources, node '%' is not local or has no defined IPC keyThe entry for this Data Object Broker in the HCS configuration file may be missing the IPCKEY or HOST attributes, and/or the host name specified may be wrong.Check that the NODENAME parameter in the crparm file is correct. If it is correct then verify that the NODE definition in the HCS configuration file (huron.dir) has valid IPCKEY and HOST attributes. The host name must be the host on which you are attempting to start the Data Object Broker or utility. NOTE: verify that the proper punctuation is in place, such as delimiting commas.The Fail Safe level specified in a PEERS parameter is invalid.A parameter assignment or operator command contained an invalid value.Verify the parameter or command syntax.A syntax error was detected while parsing a parameter assignment or operator command. The last valid token is included in the message to help identify the location of the problem. If the syntax error is in a file then a subsequent message should indicate which file and what line number.Verify the parameter or command syntax.A syntax error was detected while parsing a parameter assignment or operator command. The offending token is included in the message along with a description of what was expected. If the syntax error is in a file then a subsequent message should indicate which file and what line number.Verify the parameter or command syntax.A syntax error was detected while parsing a parameter assignment or operator command. The line ended while the parameter assignment or operator command was incomplete. If the syntax error is in a file then a subsequent message should indicate which file and what line number.Verify the parameter or command syntax.A syntax error was detected while parsing a parameter assignment or operator command. A string value was longer than the maximum allowed length. If the syntax error is in a file then a subsequent message should indicate which file and what line number.Verify the parameter or command syntax.Unable to add peer to table, maximum of % peers exceededThe maximum number of peers have been configured and an additional PEERS parameter is not accepted.Ensure that only the allowed maximum number of peers are configured.Error: %, function unsupported in batch environmentThis 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.An attempt to open one of the database files failed because the file was moved or an invalid link was created. Object Service Broker database files cannot be moved to different locations in the file system. Once they have been formatted with a certain name, they can only be used under that name.This feature protects against possible integrity problems.If the file was moved, it must be moved back to its original location. If it is necessary to move a segment, the segment must be backed up then restored to its new location.Number of connections specified for peer exceeds %The number of connections specified in a PEERS parameter exceeds the maximum number of connection allowable to one peer.Ensure that the number of connections is no more than the maximum stated value.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.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.The user is not allowed to perform the stated action based on his or her security level. The security level of the user is established by the parameters SYSADMIN, OPERATOR, and PRIVILEGED. By default a user is given a security level of general Object Service Broker user.Either the action must be performed while logged on with an authorized userid, or the Object Service Broker System Administrator may need to update the security parameters mentioned above.User '%' is not authorized to access Data Object Broker configuration filesThe user does not have permission to read the Data Object Broker parameter file. Any user that performs Object Service Broker administration or uses Object Service Broker utilities must have read access to the crparm file, the dbdef file, and the HCS configuration file.Ensure that the userid and group ownerships for the various Data Object Broker configuration files are correct and that the permissions allow read access to the necessary userids. Ensure that the user in question has the necessary group membership to access Object Service Broker.User '%' is not authorized to access Data Object Broker IPC resourcesThe user does not have permission to attach the Data Object Broker shared memory. Any user that performs Object Service Broker administration or uses Object Service Broker utilities must have permission to access to the Data Object Broker shared memory.Ensure that the SHAREDMEMPERM parameter in the crparm file allows read/write access to the necessary userids. Ensure that the user in question has the necessary group membership to access Object Service Broker.The userid supplied is greater than 8 characters.End-of-transaction was initiated with held pages in the working setAn internal error has occurred. NAM is notifying the Data Object Broker that it has completed commit processing but there are still held pages in the working set.This error is fatal and indicates a serious programming error. Development should be notified immediately.Unable to connect via IPC, Data Object Broker is offline, IPC key=%A connection could not be established to a Data Object Broker because it is not online.If the Data Object Broker is known to be online when this problem occurs, verify that the IPC key used by the Data Object Broker is the one that was used to attempt the connection (using the ipcs command). Ensure that the HURONDIR environment variable is properly set.Unable to connect via IPC, no free buffers in port pool, IPC key=%A connection could not be established to a Data Object Broker because the maximum number of IPC connections has already been reached. The maximum number of connections allowed via IPC is based mainly on the Data Object Broker parameter MAXUSERS.Increase the value of the MAXUSERS parameter in the crparm file.A connection could not be established to a Data Object Broker because the Data Object Broker is still initializing itself.Wait for the Data Object Broker to come online. Use the command "hrncr state" to determine when the Data Object Broker comes online.Unable to listen on IPC, no free buffers in port pool, IPC key=%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.Unable to send message via IPC, no free buffers in message pool, IPC key=%A message could not be sent via IPC due to a temporary shortage of message buffers. This problem should rarely occur under normal circumstances.If this problem occurs with any frequency then 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.Unable to send message, no free buffers in buffer pool, IPC key=%A message could not be sent via IPC due to a temporary shortage of message buffers. This problem should rarely occur under normal circumstances.If it occurs with any frequency then 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.Unable to send message via IPC, port is not active, IPC key=%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.Unable to communicate via IPC, Data Object Broker has gone offline, IPC key=%A connection could not be established or a message could not be sent via IPC because the Data Object Broker has gone offline.Unable to send message via IPC to '%', process not active, IPC key=%A message could not be sent via IPC because the recipient of the message has terminated without closing its ports. The recipient likely terminated due to an explicit kill request from a user or administrator.An attempt to lock the contingency log for formatting failed because the contingency log is already in use by the Data Object Broker or by another Object Service Broker utility.If the Data Object Broker is running it should be stopped to format the contingency log. If the contingency log is being used by another Object Service Broker utility then you must wait for the utility to finish.An attempt to open the contingency log failed because the contingency log is already in use by the Data Object Broker or by an Object Service Broker utility.If the Data Object Broker is running then the contingency log cannot be used until the Data Object Broker shuts down. If the contingency log is being used by an Object Service Broker utility then you must wait for the utility to finish before starting the Data Object Broker or running another utility.Unable to use Contingency Log, page file unformattedAn attempt to open the contingency log failed because the contingency log has not been formatted.A request to abort an in-doubt transaction specified a slot this is empty. 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 on the display.Unable to abort contingent transaction in active/retry state, slot=%, transaction=%A request to abort an in-doubt transaction failed because the Data Object Broker is currently trying to resolve the transaction. This problem may be caused by "stale" data on an administrator's display.Have the administrator refresh the data on the display.Unable to release contingent transaction in active/retry state, slot=%, transaction=%A request to release an in-doubt transaction failed because the Data Object Broker is currently trying to resolve the transaction. This problem is likely caused by peers and/or administrators resolving an in-doubt transaction simultaneously.Unable to format Contingency Log with % slots, maximum of % exceededThe maximum number of slots you can specify in the Contingency Log is 65535.Specify a number of slots within the allowed range.Insufficient number of pages to format a Contingency Log with % slots (3 pages are required for each slot)The number of pages you specified was too low.Specify the number of pages as at least three times the number of required slots.An attempt to read a contingency log slot failed because the slot contained invalid data. This is likely due to a loss of data on the disk.Consult the Backup and Recovery manual.An attempt to begin a distributed Fail Safe transaction failed because there is no more room in the contingency log. This may be due to a lack of slots (each distributed Fail Safe transaction requiring one slot) or to a lack of space on which to store the transaction intent list. A lack of slots may be due to a build up of in-doubt transactions due to connection outages.Either increase the number of slots in the contingency log or increase its overall size.Unable to complete checkpoint in recovery, segment '%' online or recovery not in progressThis 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.Unable to find message queue port, segment id=%, file=%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.Unable to initialize access control, 'SYSADMIN' parameter is requiredThe userid identified to the parameter named is not valid.Ensure the userid is defined to the system and respecify the parameter.The command was started with root authority, but it was unable to change its userid to the Object Service Broker system administrator's userid. You may require help from the system administrator to resolve this problem.Login as the Object Service Broker system administrator and retry the operation.Unable to add userid to access control list, maximum of % userids exceededThe maximum number of authorized userids has already been configured. An attempt to define another authorized userid has failed.Reduce the number of authorized userids defined in the Data Object Broker configuration file or on the command line.Unable to initialize access control, no more than one system administrator may be specified, check 'SYSADMIN' parameter(s)An attempt was made to initialize access control to more than one System Administrator at a time.Your segment is getting close to being full.You have succeeded in increasing the amount of free space in your segment.Insufficient number of pages for Journal. Required minimum is nnnnThe actual number of journal pages is less than the number of pages in the resident page manager, as defined by a parameter RESIDENTPAGES in the CRPARM file.Increase the number of actual pages in the journal or decrease the value in the RESIDENTPAGES parameter.This value shows the amount of memory in the shared region of the DOB. Data Object Broker.This value should be smaller than the amount of physical memory on the system in order to avoid thrashing. For systems with multiple Data Object Brokers, it is also used to determine what the value of the next SHAREDMEMADDR value should be.If your system is paging excessively, reduce the RESIDENTPAGES parameter.Segment <segmentName> file <pagefileName> too big - check 'MAXTDSEXTENTS' parameterThe size of the TDS file is limited by the number of TDS extents it can contain; this is a configurable value set by MAXTDSEXTENTS parameter in crparm file.Increase the value of the MAXTDSEXTENTS parameter.Unable to create semaphore <semaphoreName>, error = <errorNo>Internal error - indicates Object Service Broker inability to use operations system facilities; error number is coming from system API.See your system administrator for help in fixing this problem, which may require updates to the kernel configuration. Contact TIBCO Support.Unable to use semaphore <semaphoreName>, error = <errorNo>Internal error - indicates Object Service Broker inability to use operations system facilities; error number is coming from system API.See your system administrator for help in fixing this problem, which may require updates to the kernel configuration. Contact TIBCO Support.Internal error - indicates Object Service Broker inability to use operating system facilities; error number is coming from system API.See your system administrator for help in fixing this problem, which may require updates to the kernel configuration. Contact TIBCO Support.Unable to use mutex <mutexName>, error = <errorNo>Internal error - indicates Object Service Broker inability to use operating system facilities; error number is coming from system API.See your system administrator for help in fixing this problem, which may require updates to the kernel configuration. Contact TIBCO Support.This is an extreme error. Object Service Broker took this action to prevent a possible Pagestore corruption.Pages from the resident page pool could not be flushed to the page files. On UNIX the fdatasync system call failed and on Windows the FlushFileBuffers Windows API call failed.Review the error codes to determine what cause the error. A possible cause of the error is that a disk I/O error occurred. On Windows review the event log for system or hardware errors. Restart the DOB to determine whether the failures are persistent.The CTABLE Manager has temporarily run out of buffers for tables. This is likely due to a burst of update activity that consumed buffers faster than they could be written to disk.Consider increasing the value for the Data Object Broker parameter CTABRESIDENT. Consult the Installation and Operations manual.CompoundSynch internal failure, call '%' failed, error=%An unexpected error occurred with an internal synchronization object.The redo log has become full or is nearly full. A checkpoint will be requested that should result in the condition being resolved. Until the condition is resolved, sync processing is temporarily suspended.Increase the size of the redo log as it is not adequate for the current volume or frequency of sync requests.The redo log is no longer full or near-full after checkpoint processing and sync processing will be allowed to continue.
|
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |