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.
4102 |
ERROR: TUXCONFIG is not set. | |
|
Description |
|
Action |
Configure the application (see | |
4103 |
ERROR: Application must be configured. | |
|
Description |
|
Action |
Configure the application (see | |
4104 |
ERROR: Error retrieving application directory. | |
|
Description |
|
Action |
Configure the application (see | |
4105 |
ERROR: tpaclcvt cannot be run on an active application. | |
|
Description |
|
Action |
Bring the BEA TUXEDO system down using | |
4106 |
INFO: Converting filename... | |
|
Description |
|
Action |
Be patient. | |
4107 |
ERROR: Could not open filename. | |
|
Description |
|
Action |
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command. | |
4108 |
INFO: Converting filename... | |
|
Description |
|
Action |
Be patient. | |
4109 |
ERROR: Could not open filename. | |
|
Description |
|
Action |
Be sure the name of the file to be converted is correct and that this file exists. Re-run the command. | |
4110 |
ERROR: Could not create filename. | |
|
Description |
|
Action |
There are several kernel parameters which could cause this error. Two obvious ones include the maximum allowed size for files and the number of allowable open file descriptors. Disk space could also be a problem. Increase the appropriate kernel parameters or buy a new disk, then try the command again. | |
4111 |
ERROR: Could not get information on application. | |
|
Description |
When |
Action |
Make sure your | |
4113 |
ERROR: Only the TUXEDO administrator can run this command. | |
|
Description |
|
Action |
Log into the system as the BEA TUXEDO administrator and re-run this command. | |
4114 |
ERROR: Only the TUXEDO administrator can run this command. | |
|
Description |
|
Action |
Log into the system as the BEA TUXEDO administrator and re-run this command. | |
4115 |
ERROR: Only the TUXEDO administrator can run this command. | |
|
Description |
|
Action |
Log into the system as the BEA TUXEDO administrator and re-run this command. | |
4116 |
ERROR: Only the TUXEDO administrator can run this command. | |
|
Description |
|
Action |
Log into the system as the BEA TUXEDO administrator and re-run this command. | |
4117 |
INFO: User id -1 found for username. Generating valid unique id. | |
|
Description |
Under BEA TUXEDO system security, user identification numbers of |
Action |
In order to specify particular user identification numbers, use | |
4118 |
ERROR: Could not get appropriate user identification number. | |
|
Description |
User identification numbers are only valid within the range 1 to 131,071. If |
Action |
Delete users before calling | |
4119 |
ERROR: tpalloc() failed; tperrno=tperrno | |
|
Description |
The event server failed to allocate memory for an FML32 buffer. |
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 |
| |
4120 |
ERROR: tpcall() to svc failed. tperrno=tperrno | |
|
Description |
The event server couldn't call service svc. |
Action |
The event server periodically garbage collects stale subscriptions of clients that terminated without unsubscribing. It makes a call to svc to determine if a client is alive. This message states that the service call failed. | |
See Also |
| |
4126 |
ERROR: Authentication level must be USER_AUTH, ACL or MANDATORY_ACL. | |
|
Description |
The BEA TUXEDO system-supplied |
Action |
Change the | |
4127 |
ERROR: In ACL or MANDATORY_ACL levels, the password file must be filename | |
|
Description |
|
Action |
Change the | |
4128 |
ERROR: Unable to advertise AUTHSVC. | |
|
Description |
|
Action |
Increase the | |
4129 |
INFO: AUTHSVR terminating | |
|
Description |
The AUTHSVR is terminating normally. |
Action |
No action required. | |
4130 |
INFO: Authentication failed for user username/clientname | |
|
Description |
The given username/clientname attempted to log into the BEA TUXEDO system and was denied access by the |
Action |
Do whatever is appropriate for attempted security break-ins in the application. | |
4131 |
WARN: Wildcard username and/or clientname presented | |
|
Description |
The wildcard character "*" was presented as either the username or clientname in the |
Action |
If wildcard characters are appropriate for the security scheme to which your application adheres, then this warning can be ignored. Otherwise, do whatever is appropriate in the security scheme of your application. | |
4132 |
WARN: Duplicate id [username/clientname] in password file. | |
|
Description |
When generating the cache which the |
Action |
Use | |
4133 |
ERROR: Cannot open password file filename | |
|
Description |
|
Action |
If the password file cannot be found, then it is assumed that there are no users in the BEA TUXEDO system. When users are added via | |
4134 |
ERROR: Memory allocation error. | |
|
Description |
|
Action |
Make sure enough memory exists on the system running the | |
4135 |
ERROR: Cannot open file file for writing | |
|
Description |
The event server couldn't open file file for writing the subscription database. |
Action |
The event server writes a new copy of the subscription database in the temporary file file. Then, it links this file to the control file specified in the | |
4136 |
ERROR: .SysServerDied: servername, group srvgrp, id srvid server died | |
|
Description |
This message indicates that the server specified above died abnormally and the BBL detected this condition in its periodic scan of the BB. |
Action |
Debug the server and fix the problem before it is restarted again. | |
See Also |
| |
4137 |
INFO: .SysGroupState: Group name on lmid state change to newstate | |
|
Description |
A TMIB request to change the state of a group, name, to a new state, newstate its associated machine lmid completed successfully. |
Action |
No action required. | |
See Also |
| |
4138 |
ERROR: Cannot open file file for appending subscription | |
|
Description |
The event server appends new subscriptions to the end of the control file. This message states that the control file file was inadvertently removed while the server is running. |
Action |
Prevent such errors from happening by protecting the APPDIR directory. Since this file serves as a backup copy of subscriptions in an application running only a primary event server, it is important that this file be protected. | |
4139 |
ERROR: Could not find /etc/passwd | |
|
Description |
Under the authentication level |
Action |
Make sure that either the user file relative to | |
4143 |
ERROR: Subscription matches an already existing subscription | |
|
Description |
An attempt was made to subscribe to an entry that matches one in the event server's list. |
Action |
Check the | |
See Also |
| |
4144 |
ERROR: Fielded buffer access error Ferror32 | |
|
Description |
The event server failed to perform |
Action |
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32. | |
4145 |
ERROR: Fielded buffer access error Ferror32 | |
|
Description |
The event server failed to perform |
Action |
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32. | |
4146 |
ERROR: Fielded buffer access error Ferror32 | |
|
Description |
The event server failed to perform |
Action |
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32. | |
4147 |
ERROR: Fielded buffer access error Ferror32 | |
|
Description |
The event server failed to perform |
Action |
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32. | |
4148 |
ERROR: Fielded buffer access error Ferror32 | |
|
Description |
The event server failed to perform |
Action |
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 Ferror32. | |
4149 |
ERROR: Must specify TA_QCTL_DEQ_TIME if TA_QCTL_QTIME_ABS is set | |
|
Description |
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then |
Action |
Correct the error and re-issue the subscription. | |
See Also |
| |
4150 |
ERROR: Can't specify both TA_QCTL_QTIME_ABS and TA_QCTL_QTIME_REL | |
|
Description |
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then either |
Action |
Correct the error and re-issue the subscription. | |
See Also |
| |
4151 |
ERROR: Must specify TA_QCTL_DEQ_TIME if TA_QCTL_QTIME_REL is set | |
|
Description |
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then |
Action |
Correct the error and re-issue the subscription. | |
See Also |
| |
4152 |
ERROR: Value of TA_QCTL_PRIORITY is out of range | |
|
Description |
If the notification mechanism selected for a subscription is to place a message in a BEA TUXEDO system reliable queue, then |
Action |
Correct the error and re-issue the subscription. | |
See Also |
| |
4153 |
ERROR: No such subscription exists | |
|
Description |
An attempt was made to do a |
Action |
Correct the error and re-issue the subscription. | |
See Also |
| |
4154 |
ERROR: Failed to get generic request parameters | |
|
Description |
The event server couldn't translate the user-supplied FML32 buffer into a view representation. This can occur either due to view description files being inadvertently deleted or due to internal system error. |
Action |
If no view description files have been deleted from the | |
See Also |
| |
4155 |
ERROR: Invalid class specified | |
|
Description |
The event server received a request for subscribe/unsubscribe directly without either calling |
Action |
You can subscribe/unsubscribe by using | |
See Also |
| |
4156 |
ERROR: Memory allocation failure | |
|
Description |
Memory allocation failed for an FML32 buffer. |
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. | |
4157 |
ERROR: Invalid operation (operation) specified for /Admin request | |
|
Description |
The event server received a request for |
Action |
You can subscribe/unsubscribe by using | |
See Also |
| |
4160 |
ERROR: Could not initialize threaded BRIDGE | |
|
Description |
An attempt to initialize the networking software from the |
Action |
Make sure that the correct networking software is installed on the system and that the network is accessible. | |
4162 |
ERROR: Invalid -o option | |
|
Description |
|
Action |
Re-run the command without the | |
See Also |
| |
4163 |
ERROR: Can't open output file filename: system_error | |
|
Description |
|
Action |
Check that there is space in the file system associated with filename and re-run the command. | |
See Also |
| |
4171 |
ERROR: Current work directory path name is too long | |
|
Description |
The full pathname for the current directory in which |
Action |
Change the directory structure such that the pathname is less than 256 characters, and re-run the command. | |
4172 |
ERROR: Absolute path name of the output file is too long | |
|
Description |
The full pathname for a file generated by |
Action |
Change the directory structure such that the pathname is less than 256 characters, and re-run the command. | |
4174 |
ERROR: Could not initialize network | |
|
Description |
An attempt to initialize the networking software while trying to access the |
Action |
Make sure that the correct networking software is installed on the system and that the network is accessible. | |
4175 |
ERROR: Could not initialize network | |
|
Description |
An attempt to initialize the networking software from |
Action |
Make sure that the correct networking software is installed on the system and that the network is accessible. | |
4178 |
ERROR: can't fdopen yyout, system_error | |
|
Description |
On NetWare, the error output of |
Action |
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO system Technical Support. | |
4179 |
ERROR: can't fdopen output file, system_error | |
|
Description |
On NetWare, the error output of |
Action |
Ensure that there are enough file descriptors available. Try re-running the command, or contact your BEA TUXEDO system Technical Support. | |
4180 |
ERROR: can't execute command | |
|
Description |
The |
Action |
Verify that the compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in the | |
See Also |
| |
4181 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Ensure 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. | |
4182 |
ERROR: Cannot boot old release site (lmid) in non-interoperability mode | |
|
Description |
An attempt was made to boot a System 5 version of BEA TUXEDO system with a System 6 version of BEA TUXEDO system with the |
Action |
Shut down the application and unset the | |
4183 |
ERROR: Older release sites cannot join application in non-interoperability mode | |
|
Description |
An attempt was made to boot a System 5 version of BEA TUXEDO system with a System 6 version of BEA TUXEDO system with the |
Action |
Shut down the application and unset the | |
4186 |
ERROR: Cannot set TA_SUSPTIME without suspending connection | |
|
Description |
An /AdminAPI call accessing the |
Action |
Omit the | |
See Also |
| |
4187 |
ERROR: Cannot set TA_SUSPTIME for unsuspended connection | |
|
Description |
An /AdminAPI call accessing the |
Action |
Omit the | |
See Also |
| |
4188 |
WARN: server built without the -s option cannot advertise services. | |
|
Description |
The |
Action |
Re-run the command specifying services with the | |
See Also |
|