システム・メッセージ: IJINFRAカタログ0-99
|
2 |
INFO: Starting JVM | |
|
Description |
This is an informational message indicating that the server process is starting the Java Virtual Machine. |
Action |
None. | |
3 |
ERROR: Cannot create FML buffer for TMIB request | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
4 |
ERROR: Cannot call .TMIB: errnum | |
|
Description |
The server process was unable to call the |
Action |
Take corrective action based on the returned value of | |
5 |
ERROR: Cannot find default constructor for ServerInfo | |
|
Description |
The server process was unable to find the default constructor for the ServerInfo class. |
Action |
Make sure the | |
6 |
ERROR: Cannot create ServerInfo object | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
7 |
WARN: No server group info | |
|
Description |
The server process was unable to get any information about the server group. |
Action |
None. This may result in a more serious error, and a corresponding error message would be written to the user log. | |
8 |
ERROR: Cannot find m_srvgp field in ServerInfo | |
|
Description |
The server process was unable to find the |
Action |
Contact Oracle Customer Support. | |
9 |
ERROR: Cannot find m_srvid field in ServerInfo | |
|
Description |
The server process was unable to find the |
Action |
Contact Oracle Customer Support. | |
10 |
WARN: No server ID info | |
|
Description |
The server process was unable to get any information about the server ID. |
Action |
None. This may result in a more serious error, and a corresponding error message would be written to the user log. | |
11 |
ERROR: Cannot find m_grpno field in ServerInfo | |
|
Description |
The server process was unable to find the |
Action |
Contact Oracle Customer Support. | |
12 |
WARN: No group number info | |
|
Description |
The server process was unable to get any information about the group number. |
Action |
None. This may result in a more serious error, and a corresponding error message would be written to the user log. | |
13 |
WARN: No CLOPT info | |
|
Description |
The server process could not find any command line option information. |
Action |
None. This may result in a more serious error, and a corresponding error message would be written to the user log. | |
14 |
ERROR: Cannot find m_clopt field in ServerInfo | |
|
Description |
The server process was unable to find the |
Action |
Contact Oracle Customer Support. | |
16 |
ERROR: Cannot allocate reply buffer | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
17 |
ERROR: Reply failed with error: errnum | |
|
Description |
An attempt by the process to receive a reply failed. |
Action |
Take corrective action based on the value of | |
18 |
ERROR: Reply length is zero | |
|
Description |
An attempt by the process to receive a reply failed because the length of the receiving buffer was zero. |
Action |
Contact Oracle Customer Support. | |
19 |
ERROR: Out of memory. Cannot allocate space for internal data structure | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
20 |
ERROR: Unable to resolve in process or out process method invocation | |
|
Description |
The process was unable to determine if a particular request was an |
Action |
Contact Oracle Customer Support. | |
21 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
33 |
ERROR: Cannot allocate FML buffer for TMIB call | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
34 |
ERROR: Cannot access TMIB: errnum | |
|
Description |
The server process was unable to access the |
Action |
Take corrective action based on the returned value of | |
35 |
エラー: 掲示板をアタッチできません | |
|
説明 |
サーバー・プロセスが |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
36 |
エラー: 掲示板のロックとデタッチを実行できません | |
|
説明 |
サーバー・プロセスが |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
37 |
エラー: 掲示板をロックできません | |
|
説明 |
サーバー・プロセスが掲示板をロックできない場合、このメッセージがサーバー・プロセスで発生します。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
38 |
エラー: 掲示板をデタッチできません | |
|
説明 |
サーバー・プロセスが |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
40 |
ERROR: Cannot execute prog_nam | |
|
Description |
The |
Action |
If you are compiling executables to run on the same machine type, as is normally the case, verify that the | |
42 |
ERROR: Missing argument to -M option | |
|
Description |
The server process will not boot because no argument has been passed on the command line to the |
Action |
Make the appropriate changes in the | |
43 |
ERROR: Missing argument to -classpath option | |
|
Description |
The server process will not boot because no argument has been passed on the command line to the |
Action |
Make the appropriate changes in the | |
44 |
ERROR: Cannot create debugging pipe: errnum | |
|
Description |
The server process will not boot because it could not create a debugging pipe. Details about the error that was returned is specified by |
Action |
Take corrective action based on the value of | |
45 |
ERROR: Cannot reopen stdout for debugging info: errnum | |
|
Description |
The server process will not boot because it cannot reopen |
Action |
Take corrective action based on the value of | |
46 |
ERROR: Cannot create Java VM | |
|
Description |
The server process will not boot because it could not create the Java Virtual Machine. |
Action |
Contact Oracle Customer Support. | |
47 |
ERROR: No agent password info | |
|
Description |
The server process will not boot because it could not retrieve the agent password information. |
Action |
Contact Oracle Customer Support. | |
48 |
INFO: Debug password buffer: buf | |
|
Description |
This is an informational message with the debug password buffer specified in |
Action |
None. | |
58 |
ERROR: Cannot create Java VM | |
|
Description |
Execution of |
Action |
Contact Oracle Customer Support. | |
59 |
ERROR: Cannot find classname class | |
|
Description |
While executing |
Action |
Make sure the | |
60 |
ERROR: Cannot find buildjobjserver.main | |
|
Description |
While executing |
Action |
Contact Oracle Customer Support. | |
65 |
INFO: Server initialized | |
|
Description |
This is an informational message indicating that the server process has successfully initialized and is now ready to process incoming requests. |
Action |
None. | |
66 |
ERROR: Server initialization failed | |
|
Description |
The server process initialization has failed because of an internal error. |
Action |
Contact Oracle Customer Support. | |
70 |
INFO: Shutting down JVM | |
|
Description |
This is an informational message indicating that the server process is shutting down the Java Virtual Machine. |
Action |
Contact Oracle Customer Support. | |
73 |
WARN: pattern not found in file | |
|
Description |
This is a warning message that is output while executing |
Action |
None. This may result in a more serious error and a corresponding error message being written to the user log. | |
74 |
INFO: command: PostProcessing: writing file 'file' | |
|
Description |
This is an informational message that is output while executing the command specified by command. file gives the name of the file being written to during the postprocessing phase. |
Action |
None. | |
75 |
ERROR: Cannot open file: error | |
|
Description |
While executing |
Action |
Take corrective action based on the error returned. | |
76 |
ERROR: Cannot create temp file: error | |
|
Description |
While executing |
Action |
Take corrective action based on the error returned. | |
77 |
ERROR: Invalid ImplBase file file | |
|
Description |
While executing |
Action |
Contact Oracle Customer Support. | |
78 |
ERROR: Cannot create new file: error | |
|
Description |
While executing |
Action |
Take corrective action based on the error returned. | |
79 |
ERROR: command: idltojava option 'option' not supported | |
|
Description |
This error message is output while executing the command (specified by command) if an unsupported |
Action |
Do not use the corresponding option. It is not supported. | |
80 |
ERROR: command: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the process ran out of memory while executing the command (specified by command). |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
81 |
ERROR: command: Cannot execute sub-command: error | |
|
Description |
While executing the command (specified by command), the process was unable to execute a sub-command (specified by sub-command). error gives details of the error returned by the system. |
Action |
Take corrective action based on the error returned. | |
82 |
ERROR: Cannot access file file in APPDIR appdir | |
|
Description |
The server process will not boot because it cannot access the |
Action |
Make sure the | |
83 |
ERROR: Cannot copy request message | |
|
Description |
The request cannot be processed by the server because the request message cannot be copied. |
Action |
Notify Oracle Technical Support. | |
84 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
86 |
ERROR: Out of memory | |
|
Description |
An attempt to allocate space for internal data structures failed because the server process ran out of memory. |
Action |
This error may indicate that all available memory for the process has been exhausted. Ensure that 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. | |
91 |
ERROR: Cannot create registry table entry for context | |
|
Description |
An attempt to create a registry table entry for the new context failed. |
Action |
Either increase the value of the | |
92 |
ERROR: Context initialization failed | |
|
Description |
An attempt to initialize the server context failed. |
Action |
This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify Oracle Technical Support. | |
93 |
ERROR: Failed to allocate context | |
|
Description |
An attempt to allocate the server context failed. |
Action |
This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify Oracle Technical Support. | |