System Messages: CMDDES Catalog 0-99
|
3 |
ERROR: program_name: Could not open file_name for recording | |
|
Description |
The filename specified with the |
Action |
Check the path and filename for permissions and reenter the | |
See Also |
| |
11 |
ERROR: Access to the initial mask is not permitted | |
|
Description |
According to the settings of the environment variables |
Action |
Modify the setting of the environment variables | |
See Also |
| |
12 |
ERROR: Could not find initial mask | |
|
Description |
The initial mask specified with the |
Action |
Check the settings of the | |
See Also |
| |
13 |
ERROR: Initial mask not found | |
|
Description |
The initial mask specified with the |
Action |
Check the settings of the | |
See Also |
| |
14 |
WARN: login cannot print the initial form | |
|
Description |
The initial system mask cannot be printed and an attempt was made to print using the |
Action |
No action required. | |
See Also |
| |
15 |
ERROR: login you are not allowed to enter mask_name transactions | |
|
Description |
The mask indicated by mask_name has been selected by the input to the current form. However, mask_name is not allowed to be accessed by this user according to the settings of the |
Action |
Modify the setting of the environment variables | |
See Also |
| |
16 |
ERROR: login could not find form mask_name | |
|
Description |
The next form to be displayed, indicated by mask_name, could not be found. |
Action |
Check the settings of the | |
See Also |
| |
17 |
ERROR: Non-existent transaction | |
|
Description |
The menu option selected maps to a choice with no mask/form associated. |
Action |
Check your mask file to be sure the menu choice that resulted in this error is fully specified. | |
See Also |
| |
18 |
ERROR: Form mask_name not found | |
|
Description |
The next form to be displayed, indicated by mask_name, could not be found. |
Action |
Check the settings of the | |
See Also |
| |
19 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed allocating a screen image. Additional information about the problem is printed as part of the message. |
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. | |
23 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically 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. | |
See Also |
| |
24 |
WARN: SYSTEM BUSY ... PLEASE WAIT A FEW SECONDS | |
|
Description |
The application and/or operating system is busy to the point that the requested service cannot be satisfied immediately. |
Action |
Wait a few seconds and try the transaction again. If the problem persists, then contact your Oracle TUXEDO system Technical Support. | |
See Also |
| |
25 |
ERROR: NO SERVER AVAILABLE FOR THIS FORM | |
|
Description |
The service associated with the selections made on this form is currently not offered or is suspended. |
Action |
Contact your Oracle TUXEDO system Technical Support. They will need to administer the application to make the service available. This can be done by booting a new server, unsuspending a suspended service, or by advertising a new service on an existing server. | |
See Also |
| |
26 |
ERROR: MEMORY ALLOCATION FAILURE | |
|
Description |
An attempt to dynamically 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. | |
See Also |
| |
27 |
ERROR: CANNOT SEND TO SERVER | |
|
Description |
The service requested by the selections made on the current form could not be satisfied because the queue associated with the server or the local BRIDGE process has been abnormally removed from the system. |
Action |
Contact your Oracle TUXEDO system Technical Support. This error indicates an abnormal removal of UNIX System IPC resources that should be investigated. In any case, the service can be retried after the system restarts the server (abnormal removal of a queue results in a server exit) or after the administrator boots a new instance of the server. | |
See Also |
| |
28 |
ERROR: unknown send failure | |
|
Description |
A UNIX System message send or receive error was encountered while attempting to satisfy the service request selected on the current form. The error is something other than |
Action |
Contact your Oracle TUXEDO system Technical Support. The UNIX message queue permissions should be checked for access rights. Additionally, memory access in application routines linked into | |
See Also |
| |
30 |
ERROR: FIELDED BUFFER ERROR | |
|
Description |
Internal system fielded buffer error indicating use of a non-fielded or misaligned buffer within |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
See Also |
| |
32 |
ERROR: internal failure-get_page | |
|
Description |
An error occurred while initializing a new form. |
Action |
See earlier messages that indicate the exact nature of the problem. | |
See Also |
| |
42 |
ERROR: VALIDATION FUNCTION valfunc NOT FOUND | |
|
Description |
The validation function valfunc could not be found in the version of |
Action |
The are two ways to resolve this problem. The first way is to change the definition of the form being used to use a different validation function or to use built-in validation rules such as regular expression matching. The second way is to build or rebuild a customized version of | |
See Also |
| |
54 |
ERROR: Unexpected End of File encountered | |
|
Description |
While reading input, end of file was reached before getting the entire message. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
See Also |
| |
57 |
ERROR: Error in file udfkfile describing user defined keys | |
|
Description |
|
Action |
Check that the UDFK file being used exists and conforms to the specifications described in the | |
See Also |
| |
62 |
ERROR: Screen/window too small: must be at least 24x80 | |
|
Description |
The window in which |
Action |
Expand your window or move to a larger window before running | |
See Also |
| |
66 |
ERROR: operation not allowed in release | |
|
Description |
|
Action |
Contact your Oracle TUXEDO system Technical Support. | |
See Also |
| |
67 |
ERROR: Transaction could not be committed | |
|
Description |
The transaction could not be committed by |
Action |
Depending on the situation that caused the transaction not to commit, a retry may be successful. If multiple retries over a period of time are not successful, then contact your database administrator(s) to see if they can identify the reason why your transactions cannot be completed. | |
See Also |
| |
68 |
ERROR: Service timed out - status unknown | |
|
Description |
The service associated with the current screen was requested and a timeout occurred in one of three places. Either the request could not be enqueued within the defined timeout interval (only applies if the |
Action |
Depending on the situation that caused the request to timeout, a retry may be successful. If multiple retries over a period of time are not successful, then contact your database administrator(s) to see if they can identify the reason why your request cannot be completed. | |
See Also |
| |
69 |
ERROR: Desired service does not take FML buffers | |
|
Description |
The service associated with the current form does not accept FML buffers as input. The set of buffer types accepted by a particular server is determined at compile time. This set may further be restricted by settings for the |
Action |
Contact your application administrator to determine why the requested service does not accept the FML buffer type. Possible actions are to rebuild the server with the FML buffer type included, or to update the configuration file to allow for FML buffer types sent to this service. | |
See Also |
| |
72 |
ERROR: Transaction could not be started | |
|
Description |
A global transaction could not be started prior to requesting the service associated with the current form. This may be caused by a full global transaction table on the local site or by some other system related problem. |
Action |
The request should be retried a number of times and then the application administrator should be contacted to examine the userlog file for the machine on which | |
See Also |
| |
73 |
WARN: Error allocating FML buffer for unsolicited processing | |
|
Description |
A memory allocation failure was encountered while attempting to generate a typed buffer to be used in processing unsolicited notification messages to the |
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. | |
See Also |
| |
74 |
ERROR: Disk Error while accessing mask form | |
|
Description |
An error was encountered on a disk operation while accessing a mask form that had not been cached. Possible errors include problems reading, problems seeking, and corrupted information in the mask form. The occurrence of this error will cause |
Action |
Regenerate the mask forms used by | |
See Also |
| |
77 |
ERROR: Cannot open temporary file file | |
|
Description |
|
Action |
Check the permissions on the | |
See Also |
| |
78 |
ERROR: Cannot open temporary file file | |
|
Description |
buildmio could not open one of the temporary files it needs to build a customized version of mio. |
Action |
Check the permissions on the | |
See Also |
| |
79 |
ERROR: Cannot open temporary file file | |
|
Description |
|
Action |
Check the permissions on the | |
See Also |
| |
80 |
WARN: Cannot open file file | |
|
Description |
file could not be opened for writing by |
Action |
Check the permissions on the directory and the file specified by file to make sure that the file can be created and/or written to. | |
See Also |
| |
81 |
WARN: Failed to execute nm nmflags files | |
|
Description |
The indicated invocation of the |
Action |
Attempt a manual invocation of the indicated | |
See Also |
| |
87 |
ERROR: ipckey is an illegal IPC key value (non-numeric) | |
|
Description |
The indicated InterProcess Communication (IPC) key, ipckey, contains non-numeric characters and is therefore invalid. |
Action |
Change the InterProcess Communication key to a completely numeric value and reenter the command. | |
See Also |
| |
89 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
This error may indicate that you are trying to include too many files in a single shared memory file cache. Try reducing the number of files being cached if you think this may be the problem. However, the problem may also result from system limitations outside the direct control of the user. 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. | |
See Also |
| |
92 |
ERROR: Failed to open filename for caching | |
|
Description |
The file filename could not be opened for reading by |
Action |
Check the permissions on the indicated file for read access. Correct the permissions or correct the input filename and reenter the command. | |
See Also |
| |
94 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
This error may indicate that you are trying to include too many files in a single shared memory file cache. Try reducing the number of files being cached if you think this may be the problem. However, the problem may also result from system limitations outside the direct control of the user. 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. | |
See Also |
| |
95 |
ERROR: Too many files in cache | |
|
Description |
The user has attempted to cache more than the system imposed limit on the number of files to be stored in the shared memory cache. |
Action |
Reduce the number of files to be entered into this shared memory cache to less than 1000 and reenter the command. | |
See Also |
|