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.
201 |
ERROR: CLOPT parameter must be <= len characters in length | |
|
Description |
The value for |
Action |
Edit the configuration file such that all | |
See Also |
| |
203 |
ERROR: Group name must be <= len characters in length | |
|
Description |
The |
Action |
Edit the configuration file such that all | |
See Also |
| |
205 |
ERROR: Group name grpname not defined in *GROUPS section | |
|
Description |
The specified server group name grpname has not been defined in the GROUPS section of the configuration file. |
Action |
Edit the configuration file such that the server group name is defined in the GROUPS section. | |
See Also |
| |
207 |
ERROR: SRVID parameter must be >= 1 and <= 30000 | |
|
Description |
The value for |
Action |
Specify a value for | |
See Also |
| |
209 |
ERROR: RQADDR parameter must be <= len characters in length | |
|
Description |
The value for |
Action |
Specify a value for | |
See Also |
| |
211 |
ERROR: RQPERM parameter must be >= 1 and <= 0777 | |
|
Description |
The value for |
Action |
Specify a value for | |
See Also |
| |
213 |
ERROR: RPPERM parameter must be >=1 and <= 0777 | |
|
Description |
The value for |
Action |
Specify a value for | |
See Also |
| |
215 |
ERROR: MAXGEN parameter must be >= 1 and < 256 | |
|
Description |
The value given for |
Action |
Specify a value for | |
See Also |
| |
217 |
ERROR: GRACE parameter must be >= 0 | |
|
Description |
The value for |
Action |
Specify a value for | |
See Also |
| |
219 |
ERROR: SEQUENCE parameter must be > 0 and < 10000 | |
|
Description |
The value given for |
Action |
Specify a value for | |
See Also |
| |
220 |
ERROR: Duplicate *SERVICES section | |
|
Description |
There is more than one SERVICES section of the configuration file defined. |
Action |
Edit the configuration file such that there is only one SERVICES section. | |
See Also |
| |
221 |
ERROR: *GROUPS section must appear before *SERVICES section | |
|
Description |
The SERVICES section is defined before the GROUPS section in the configuration file. |
Action |
Edit the configuration file such that the GROUPS section is defined before the SERVICES section. | |
See Also |
| |
222 |
ERROR: Could not initialize sort of *SERVICES section | |
|
Description |
An internal error occurred while attempting to sort the SERVICES section during |
Action |
Attempt to load the configuration again via | |
See Also |
| |
223 |
ERROR: Could not turnaround sort of *SERVICES section | |
|
Description |
An internal error occurred while attempting to sort the SERVICES section of the configuration file during |
Action |
Attempt to load the configuration again via | |
See Also |
| |
224 |
ERROR: Couldn't retrieve data from *SERVICES sort | |
|
Description |
An internal error occurred while attempting to sort the SERVICES section of the configuration file during |
Action |
Attempt to load the configuration again via | |
See Also |
| |
226 |
ERROR: Service name must be <= len characters in length | |
|
Description |
The |
Action |
Specify a service name value that is less than or equal to 15 characters in length. | |
See Also |
| |
228 |
ERROR: Service service_name can't have two different ROUTING values | |
|
Description |
The indicated service name has two different routing criteria associated with it. |
Action |
Edit the configuration file such that if multiple ROUTING entries exist for the same service name but have different | |
See Also |
| |
229 |
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. | |
230 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Please refer to message 229 above. | |
231 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Please refer to message 229 above. | |
232 |
ERROR: Need different SRVGRP for the SERVICE svcname. | |
|
Description |
The same service has been specified more than once, but the |
Action |
Edit the | |
See Also |
| |
233 |
ERROR: SERVICE svcname can't have SRVGRP srvgrp on different entry. | |
|
Description |
The same service has been specified more than once, using the same |
Action |
Edit the | |
See Also |
| |
235 |
ERROR: Memory allocation failure | |
|
Description |
The |
Action |
Try running | |
See Also |
| |
237 |
ERROR: Failure during input to sort of *SERVICES section | |
|
Description |
The |
Action |
Check that there is available temporary disk space in | |
See Also |
| |
239 |
ERROR: The SRVGRP parameter must be <= len characters | |
|
Description |
The |
Action |
Choose a | |
See Also |
| |
241 |
ERROR: Group name group_name must match a name from the *GROUPS section | |
|
Description |
The |
Action |
Correct the | |
See Also |
| |
243 |
ERROR: BUFTYPE parameter must be <= len characters | |
|
Description |
The |
Action |
Shorten the | |
See Also |
| |
245 |
ERROR: TRANTIME parameter must be >= 0 and < 2147483648 | |
|
Description |
The |
Action |
Specify a value that is 0 or greater and less than 2,147,483,648. | |
See Also |
| |
247 |
ERROR: *ROUTING routingname must be <= len characters | |
|
Description |
The routingname of the ROUTING section of the configuration file must be <= 15 characters. |
Action |
Specify a value that is less than or equal to 15 characters. | |
See Also |
| |
249 |
ERROR: LOAD parameter must be >= 1 and <= 32767 | |
|
Description |
The |
Action |
Specify a value that is between 1 and 32,767. | |
See Also |
| |
251 |
ERROR: PRIO parameter must be >= 1 and <= 100 | |
|
Description |
The |
Action |
Specify a value that is between 1 and 100, inclusive. | |
See Also |
| |
252 |
ERROR: Duplicate *ROUTING section present | |
|
Description |
A second ROUTING section was encountered in the configuration file. Only one is allowed. |
Action |
Place all routing entries within a single ROUTING section. | |
See Also |
| |
253 |
ERROR: The *GROUPS section must appear before the *ROUTING section | |
|
Description |
The ROUTING section appeared in the configuration file before any GROUPS section appeared. This could be due to the sections being out of order or missing. |
Action |
Make sure that the GROUPS section appears before the ROUTING section. | |
See Also |
| |
255 |
ERROR: Routing name must be <= len characters | |
|
Description |
The |
Action |
Specify a value that is less than or equal to 15 characters. | |
See Also |
| |
256 |
ERROR: FIELD parameter missing in *ROUTING entry routingname | |
|
Description |
Each entry in the ROUTING section of the configuration file must have a |
Action |
Specify a | |
See Also |
| |
257 |
ERROR: RANGES parameter missing in *ROUTING entry routingname | |
|
Description |
Each entry in the ROUTING section of the configuration file must have a |
Action |
Specify a | |
See Also |
| |
258 |
ERROR: BUFTYPE parameter missing in *ROUTING entry routingname | |
|
Description |
Each entry in the ROUTING section of the configuration file must have a |
Action |
Specify a | |
See Also |
| |
260 |
ERROR: FIELD parameter must be <= len characters in length | |
|
Description |
The Field name in the |
Action |
Specify a | |
See Also |
| |
262 |
ERROR: RANGES parameter must be <= len characters | |
|
Description |
The |
Action |
Shorten the | |
See Also |
| |
264 |
ERROR: BUFTYPE parameter must be <= len characters | |
|
Description |
The |
Action |
Shorten the | |
See Also |
| |
265 |
ERROR: More than one NETWORK section is present | |
|
Description |
A |
Action |
Check the | |
See Also |
| |
266 |
ERROR: The *MACHINES section must precede the *NETWORK section | |
|
Description |
The NETWORK section of the |
Action |
Check if a MACHINES section is in the | |
See Also |
| |
272 |
ERROR: *NETWORK LMID lmid does not appear in *MACHINES section | |
|
Description |
The |
Action |
Make sure that the | |
See Also |
| |
274 |
ERROR: NADDR parameter missing in *NETWORK entry lmid | |
|
Description |
The entry for lmid in the NETWORK section has no |
Action |
Add a | |
See Also |
| |
276 |
ERROR: NADDR parameter must be <= len characters in length | |
|
Description |
The |
Action |
Shorten the | |
See Also |
| |
278 |
ERROR: There is an invalid hexadecimal digit in the NADDR parameter | |
|
Description |
The |
Action |
Enter hexadecimal characters in the | |
See Also |
| |
280 |
ERROR: NADDR parameter must contain an even number of hex digits. | |
|
Description |
The |
Action |
Correct the | |
See Also |
| |
282 |
ERROR: BRIDGE parameter must be an absolute pathname | |
|
Description |
The |
Action |
Replace the current | |
See Also |
| |
284 |
ERROR: NLSADDR parameter must be <= len characters | |
|
Description |
The |
Action |
Change the | |
See Also |
| |
286 |
ERROR: There is an invalid hexadecimal digit in the NLSADDR parameter | |
|
Description |
The |
Action |
Enter hexadecimal characters in the | |
See Also |
| |
288 |
ERROR: NLSADDR parameter must contain an even number of hex digits | |
|
Description |
The |
Action |
Correct the | |
See Also |
| |
290 |
ERROR: NETID parameter must be >=0 and <=256 | |
|
Description |
The |
Action |
Remove the | |
See Also |
| |
291 |
ERROR: Failure opening TUXCONFIG section sectionname (vtoc_error=vtoc_errno) | |
|
Description |
The While trying to update the |
Action |
If the echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message. | |
See Also |
| |
292 |
ERROR: Error writing *RESOURCES section of the TUXCONFIG file (vtoc_errno= vtoc_errno) | |
|
Description |
The An error occurred while trying to write to the RESOURCES section of the |
Action |
If the If the echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message. | |
See Also |
| |
293 |
ERROR: Failed to write the TUXCONFIG file (vtoc_errno=vtoc_errno). | |
|
Description |
The |
Action |
If the If the echo " " >$TUXCONFIG If the error persists, check for disk-type error conditions that might cause problems writing to files. Finally, contact BEA TUXEDO system Technical Support, making sure to have the vtoc_errno that was printed in the error message. | |
See Also |
|