Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
202 |
ERROR: Can not find DBBL on master and backup nodes. | |
|
Description |
The tmadmin is run in the administrative mode but there is no DBBL active on the Master or the Backup node. |
Action |
Check the network connectivity, and then run the | |
See Also |
| |
203 |
WARN: Error while retrieving the Bulletin Board parameters | |
|
Description |
An error was produced while obtaining the Bulletin Board parameters. An error message explaining the error already exists in the user log. |
Action |
Check the user log for an error message explaining why tmadmin was not able to obtain the Bulletin Board parameters. Also, check that the TUXCONFIG file is readable, and re-execute the tmadmin command. | |
See Also |
| |
204 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using malloc failed in tmadmin during its initialization. tmadmin will not start. |
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
See Also |
| |
205 |
ERROR: Error executing string | |
|
Description |
A command was given to tmadmin that was to be executed by the shell. An error was encountered by the shell in executing the command. |
Action |
Retry the command. If it continues to fail, refer to the | |
See Also |
| |
207 |
ERROR: Cannot advertise services for administrative processes | |
|
Description |
Either the queue or the server group and id pair match a System/T administrative process, such as the BBL. The services advertised by System/T processes cannot be changed by the administrator. |
Action |
Re-enter the advertise command making sure that the options given to the command match application servers instead of System/T administrative processes. | |
208 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using either malloc() or realloc() failed in tmadmin during the advertise command. The advertise command fails. |
Action |
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
See Also |
| |
209 |
WARN: service is already advertised on queue queue-id | |
|
Description |
The service named in the advertise command is already advertised on the server(s) matching the queue id or server group/id criteria. |
Action |
No action required. | |
See Also |
tpadvertise(3c) | |
210 |
ERROR: Error advertising service on queue queue-id | |
|
Description |
The service named in the tpadvertise command could not be advertised on the given queue. The two probable sources for this error are 1) an incorrect queue name, or 2) an incorrect service or function name. |
Action |
Check the queue name using the printqueue command. If it is correct, make sure that the server was built to be able to offer the specified service. Also, make sure that if a function is specified, that it indeed exists within the server. | |
See Also |
tpadvertise(3c), buildserver(1), servopts(5) | |
211 |
ERROR: Error advertising service on group group-id, server id server-id | |
|
Description |
The service named in the advertise command could not be advertised for the server matching the specified group and id. The two probable sources for this error are 1) an incorrect server group name or server id, or 2) an incorrect service or function name. |
Action |
Check the server group name and id using the printserver command. If they are correct, make sure that the server was built to be able to offer the specified service. Also, make sure that if a function is specified, that it indeed exists within the server. | |
See Also |
tpadvertise(3c), buildserver(1), servopts(5) |