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.
| 
 1  | 
 ERROR: Fielded buffer not aligned  | |
| 
 
  | 
 Description  | 
An FML function was called with a fielded buffer that is not properly aligned. Most machines require half-word alignment.  | 
| 
 Action  | 
 
Use   | |
| 
 See Also  | 
 
  | |
| 
 2  | 
 ERROR: Buffer not fielded  | |
| 
 
  | 
 Description  | 
A buffer was passed to an FML function that is not a fielded buffer, that is, that has not been properly initialized.  | 
| 
 Action  | 
 
Use   | |
| 
 See Also  | 
 
  | |
| 
 3  | 
 ERROR: No space in fielded buffer  | |
| 
 
  | 
 Description  | 
An attempt was made to add a field to a buffer, change a field to a larger value within a buffer, merge two buffers, or otherwise modify a buffer, and not enough space is available to complete the operation.  | 
| 
 Action  | 
 
Use   | |
| 
 See Also  | 
 
  | |
| 
 4  | 
 ERROR: Field not present  | |
| 
 
  | 
 Description  | 
When trying to find, change, or delete a field, the specified field identifier and/or field occurrence did not exist in the fielded buffer.  | 
| 
 Action  | 
 Check your request to make sure you have specified a field that is in the buffer.  | |
| 
 See Also  | 
 
  | |
| 
 5  | 
 ERROR: Unknown field number or type  | |
| 
 
  | 
 Description  | 
An invalid field identifier was specified for an FML function, or an invalid field number (0 or greater than 8192) was specified, or   | 
| 
 Action  | 
 Most of the FML functions can return this error; see the manual page associated with the function that returned this error. Check your code to make sure the field specified is valid.  | |
| 
 6  | 
 ERROR: Invalid field type  | |
| 
 
  | 
 Description  | 
An invalid (unknown) field type was specified to an FML function, or an invalid type was specified for a particular operation (for example, a non-string field was specified for a string operation).  | 
| 
 Action  | 
 Specify the proper field type or field identifier.  | |
| 
 See Also  | 
 
  | |
| 
 7  | 
 ERROR: UNIX system call error  | |
| 
 
  | 
 Description  | 
An error occurred during a UNIX system call when opening a field table file or view description file, or when reading or writing an FML buffer.  | 
| 
 Action  | 
 Check that the environment variables are set correctly for the field table and view files, and that the files have read permission.  | |
| 
 See Also  | 
 
  | |
| 
 8  | 
 ERROR: Unknown field name  | |
| 
 
  | 
 Description  | 
A field name could not be mapped into a field identifier.  | 
| 
 Action  | 
 Check that the environment variables are set correctly for the field table files and that the files have read permission.  | |
| 
 See Also  | 
 
  | |
| 
 9  | 
 ERROR: Memory allocation failed  | |
| 
 
  | 
 Description  | 
An attempt dynamically to allocate memory from the operating system using   | 
| 
 Action  | 
 Make sure 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.  | |
| 
 10  | 
 ERROR: Bad syntax in boolean expression  | |
| 
 
  | 
 Description  | 
The syntax of a boolean expression passed to   | 
| 
 Action  | 
 
Correct the format of the boolean expression being processed by   | |
| 
 See Also  | 
 
  | |
| 
 11  | 
 ERROR: Cannot find or open field table  | |
| 
 
  | 
 Description  | 
When processing the field tables, one of the field tables was not found.  | 
| 
 Action  | 
 Check that the environment variables are set correctly for the field table files and that the files have read permission.  | |
| 
 See Also  | 
 
  | |
| 
 13  | 
 ERROR: Invalid argument to function  | |
| 
 
  | 
 Description  | 
An invalid argument (other than an invalid fielded buffer, field identifier, or field type) was passed to an FML function. This can be a NULL parameter where a non-  | 
| 
 Action  | 
 See the manual page associated with the error return for the correct parameter values.  | |
| 
 14  | 
 ERROR: Destructive concurrent access to field table  | |
| 
 
  | 
 Description  | 
While reading the FML field tables, the program detected a concurrent change to the tables by another process.  | 
| 
 Action  | 
 Re-execute the program after the FML field tables have been updated.  | |
| 
 15  | 
 ERROR: Cannot find or get view  | |
| 
 
  | 
 Description  | 
A   | 
| 
 Action  | 
 Correct the view name and check that the environment variables are set correctly for the view files and that the files have read permission.  | |
| 
 See Also  | 
 
  | |
| 
 16  | 
 ERROR: Syntax error in viewfile  | |
| 
 
  | 
 Description  | 
A specified view file (suffixed with   | 
| 
 Action  | 
 Check that the environment variables are set correctly for the view files and that the view files are correctly compiled for the local machine.  | |
| 
 See Also  | 
 
  | |
| 
 17  | 
 ERROR: Cannot find or open viewfile  | |
| 
 
  | 
 Description  | 
When processing the view files, one of the view files was not found.  | 
| 
 Action  | 
 Check that the environment variables are set correctly for the view files and that the files have read permission.  | |
| 
 See Also  | 
 
  | |
| 
 18  | 
 ERROR: ACM contains negative value  | |
| 
 
  | 
 Description  | 
When executing   | 
| 
 Action  | 
 
Correct the structure   | |
| 
 See Also  | 
 
  | |
| 
 19  | 
 ERROR: Cname not found  | |
| 
 
  | 
 Description  | 
When executing   | 
| 
 Action  | 
 Check the view description and use the correct element name.  | |
| 
 See Also  | 
 
  | |