![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
A transaction was aborted because the Data Object Broker is offline.A transaction was aborted because the Data Object Broker is still in the process of starting up.A transaction was aborted because the Data Object Broker is quiesced.A transaction was aborted because the Data Object Broker is in the process of shutting down.A transaction was aborted because the Data Object Broker is abending.Peruse the Data Object Broker log for previously occurring messages that may more explicitly diagnose the nature of the error.The Data Object Broker was unable to initialize European code page support for TDS. 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 Data Object Broker was unable to initialize the Lock Manager. 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 name of the node identified in the message is not known to your local node.Check the spelling of the node name in the application. If it correctly matches the node name specified by the remote peer, the lookup failure indicates that initial connection from the local to the remote peer has not yet been established.A distributed transaction is unable to proceed because all connections to the specified peer are in use.If this problem occurs frequently, you may need to define more connections to the peer by updating the appropriate PEERS parameter in the crparm file.For more information, refer to the Object Service Broker Installation and Operations for Windows and Solaris manual.The user has attempted to acquire more than the allowable maximum number of distributed resources (gateways or peers) for the stream. The transaction is aborted.Change the application so that it involves no more than the maximum allowable number of service providers at each nesting of the transaction.A request for a gateway/server of the indicated type and Server ID has failed because of lack of availability. Either there are no gateways/servers of this type/ID combination logged on or they are all currently engaged in other transactions.Wait for the service to become available or, if the problem is chronic, ask the Object Service Broker system administrator to start more gateways/servers of the desired type/ID combination.Object Service Broker protocol error. The Execution Environment attempted to start a new transaction without terminating the current transaction that is using this stream. Logical resources remain locked by the previous stream.The user may have to log off to re-synchronize the session.A user (client) connection from the specified peer Data Object Broker has been established.An Execution Environment connection has been established and accepted from the specified terminal ID (tty) or remote machine name. An origin tag of UNKNOWN is displayed if the session is started locally from a shell script.A gateway of the specified type and ID has disconnected from the Data Object Broker and will thus no longer be available for work. The message indicates from which partner Execution Environment the gateway was logged on from.A gateway/server of the specified type and ID has connected to the Data Object Broker. The message indicates from which partner Execution Environment the gateway/server has logged on.The specified client (Peer Object Service Broker or Execution Environment) has disconnected from the Data Object Broker.A user (client) connection from the specified peer Object Service Broker Data Object Broker has been terminated.This message indicates that the gateway/server you requested to shutdown was not started. You may have specified the name incorrectly.Server shutdown request: Wildcard '*' must be preceded by at least one characterYou can use wildcards in the gateway/server shutdown request, as long as the gateway/server name in the request starts with a character.Peer to peer to peer transaction paths are not currently permitted in Object Service Broker. A message coming from a Peer Data Object Broker that is bound for a third Data Object Broker is rejected.A logon attempt from a client was rejected because all of the allocated user control tables are held by other users.Increase the MAXUSERS parameter in the crparm file and restart the Data Object Broker to allocate a greater number of user control tables. It is worth noting that native Execution Environments, inbound peer connections, and distributed gateway rule driver connections, all require user control tables and should be considered when setting the MAXUSERS parameter.An incoming gateway connection has been rejected by the Data Object Broker because all pre-allocated gateway control tables are occupied by other gateway connections.Increase the MAXDBMS parameter in the crparm file and restart the Data Object Broker to allocate a greater number of gateway spaces. It is worth noting that each expected gateway connection, be it a distributed gateway or a DBMS gateway, should be considered when setting the MAXDBMS parameter.Another Data Object Broker attempted to connect to this Data Object Broker. There is, however, no corresponding PEERS parameter for that Data Object Broker, therefore the connection is rejected.If two Data Object Brokers are to be peers then each must have a PEERS parameter to refer to the other. Either the PEERS parameter at the other Data Object Broker must be deleted, or a PEERS parameter must be added at this Data Object Broker. Restart any Data Object Broker at which a parameter change is made.This message, displayed when an operator session connects, indicates the userid of the session, the terminal or remote machine name, and the IP address from which it originates.This message, displayed when an operator session disconnects, indicates the userid of the session and the terminal or remote machine from which it originates.A distributed transaction operating at Fail Safe level 1 or 2 was aborted because there is no contingency log defined on the Data Object Broker.Have your Object Service Broker System Administrator format a contingency log using the hrntlfcl utility, add the definition to the $Huron/database/dbdef file, and restart the Data Object Broker.A transaction operating at Fail Safe level 1 or 2 was aborted because a request for a new contingency log entry (slot) was unable to be fulfilled.The contingency log is probably full. The Object Service Broker administrator should either manually commit or abort contingent transactions held in the log using the hrntladm administration utility. If this problem is a frequently recurring one, the contingency log should be reformatted with a greater number of slots.Each distributed gateway/server (API) must specify a rule driver (NEE) partner. The gateway/server connection is rejected if the partner cannot be uniquely identified and logically bound to the gateway/server connection.Start another distributed gateway/server. If the problem persists with this subsequent attempt, contact TIBCO Support.If a connecting distributed gateway/server (API) specifies as its partner a nonexistent userid, the gateway/server connection is rejected.Start another distributed gateway/server. If this subsequent attempt fails, contact TIBCO Support.Unable to support Fail Safe level % connection from '%', Contingency Log is undefinedYour request for Fail Safe level-1 or level-2 processing cannot be supported because there is no contingency log defined.Have your Object Service Broker system administrator format a contingency log using the hrntlfcl utility, add the definition to the $Huron/database/dbdef file, and restart the Data Object Broker.You requested that all service messages to the Data Object Broker on behalf of the specified user be recorded in the Data Object Broker log.You requested that all service messages to the Data Object Broker on behalf of the specified user no longer be recorded in the Data Object Broker log.Service trace for user %s cannot be enabled/disabled; userid not connected or ambiguousYou requested that messages to the Data Object Broker be recorded or stopped from being recorded. This cannot be done because the userid in the command is incorrect.An acquired service provider was unable to commit the requested updates and the transaction was subsequently aborted.An outstanding in-doubt transaction has been resolved and the pending TDS updates have been submitted for processing.An outstanding in doubt transaction has been resolved and the pending TDS updates have been rejected.Local TDS processing has failed and the transaction will be held in doubt until such time as the TDS updates can be committed.An updated service provider was lost during the commit phase. The transaction will be aborted.A transaction involving multiple service providers was aborted due to incompatible Fail Safe level specifications.Redesign the application to conform to Fail Safe restrictions as outlined in the Backup and Recovery manual.The peer tried to initiate too many inbound connections - the number of inbound connections defined for that peer in crparm table has been exceeded.Change crparm file on either side of connection - increase maxinbound on the PEER entry of the local crparm OR decrease outbound on the corresponding PEER entry of the Data Object Broker trying to connect.The logon command is rejected. The maximum number of external databases are already in use.Restart the Data Object Broker with an increased MAXDBMS parameter in the crparm file.You cannot log on because the maximum number of users are already logged on.Restart the Data Object Broker with an increased MAXUSERS parameter in the crparm file.'%' logon form '%' rejected - peer servers exceed total inbound peer connectionsNumber of peer server that can connect is limited to the number of all possible inbound peer connections.Decrease the number of peer servers defined for the Execution Environment or increase the maximum number of inbound peer connections.Your logon request is rejected because the maximum number of operators is already logged on.Restart the Data Object Broker with an increased MAXOPERATORS parameter in the crparm file.The connection to the Data Object Broker failed because of incorrect information in the connect message.Possible causes are a missing USERID parameter or an Object Service Broker ActiveX Adapter client, SDK (C/C++) client, or SDK (Java) client connecting directly to the Data Object Broker. Check whether the SDK (C/C++) client or the SDK (Java) client is using a Data Object Broker port instead of the osMon port.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |