システム・メッセージ: TUXNTカタログ0-99
|
![]() |
![]() |
1 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
Oracle Tuexdoシステム内部のIPCエラーが発生しました。 |
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
2 |
ERROR: Cannot open semaphore 'name': error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
3 |
ERROR: Cannot wakeup proc pid: error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
4 |
ERROR: Cannot access ipc server (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
5 |
ERROR: Cannot access server pipe (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
6 |
ERROR: Cannot set pipe state (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
7 |
ERROR: Cannot contact ipc server (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
This function fails if the server did not create the pipe as a message-type pipe or if the pipe handle is not in message-read mode. Also, the function returns ERROR_MORE_DATA if the read buffer specified in the call is not large enough to hold the entire message. The extended error information is described in error by calling | |
8 |
ERROR: Invalid reply length from server (read/reply) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The reply buffer from the Oracle TUXEDO system IPC Server has invalid length after the |
Action |
Please check Microsoft documentation for details on | |
9 |
WARN: Reusing existing shared memory segment 'IPCSEG' | |
|
Description |
Existing shared memory segment will be reused. |
Action |
No action required. | |
10 |
WARN: Existing parameter value = configuration, cannot change to actual | |
|
Description |
When creating Oracle TUXEDO system IPC, warning messages are issued if existing values do not match with default configuration values for all parameters of the Oracle TUXEDO system IPC Helper service. |
Action |
Check your registry database for all your Oracle TUXEDO system IPC parameters. | |
11 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
Oracle Tuexdoシステム内部のIPCエラーが発生しました。 |
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
12 |
ERROR: Cannot initialize security descriptor (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
13 |
ERROR: Cannot set ACL to security descriptor (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
14 |
ERROR: Cannot create IPC mutex (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
15 |
ERROR: Cannot create shared memory 'IPCSEG' (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
16 |
ERROR: Cannot access Service Manager (error) | |
|
Description |
The |
Action |
The extended error information is described in error by calling | |
17 |
ERROR: Cannot access service 'process' (error) | |
|
Description |
The |
Action |
This error occurs usually because the Oracle TUXEDO system IPC Helper service does not exist. You need to initially run the setup program comes with the Oracle TUXEDO system distribution media to install the software. As part of the installation, the Oracle TUXEDO system IPC Helper service will be created. Restart the Oracle TUXEDO IPC Helper service. The extended error information is described in error by calling | |
18 |
ERROR: Cannot start service 'process' (error) | |
|
Description |
The |
Action |
This error occurs usually because the Oracle TUXEDO system IPC Helper service does not exist. You need to initially run the setup program comes with the Oracle TUXEDO system distribution media to install the software. As part of the installation, the Oracle TUXEDO system IPC Helper service will be created. It is possible that the Oracle TUXEDO system IPC Helper service binary (tuxipc.exe) could not be found. Check your path and registry values under \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Oracle TUXEDO system IPC Helper\ImagePath. It is also possible that another instance of the Oracle TUXEDO system IPC Helper is already running. Other possible errors are the service database is locked or the Oracle TUXEDO system IPC Helper service has been disabled. Restart your Oracle TUXEDO system IPC Helper service. The extended error information is described in error by calling | |
19 |
ERROR: Cannot query service 'process' (error) | |
|
Description |
The |
Action |
The extended error information is described in error by calling | |
20 |
WARN: Service 'TUXEDO IPC Helper' could not be started | |
|
Description |
The Oracle TUXEDO system IPC Helper service could not be started because Windows NT service manager could not be opened or the Oracle TUXEDO system IPC Helper service is inaccessible. The Oracle TUXEDO system IPC Helper (tuxipc.exe) will be started as a normal process rather than a service now. |
Action |
No action required. | |
21 |
警告: コンソール・ユーザーがログ・オフする際にすべてのアプリケーションが終了します | |
|
説明 |
Oracle TuexdoシステムのIPC Helper (tuxipc.exe)が、サービスではなく通常のプロセスとして起動しました。コンソール・ユーザーがログオフする際にすべてのアプリケーションが終了します。 |
アクション |
アクションは不要です。 | |
22 |
ERROR: Cannot create ipc server process 'tuxipc.exe' (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
23 |
ERROR: Cannot create sleep semaphore 'name' (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
24 |
ERROR: Cannot access ipc server pipe 'IPC_SERVER_PIPE' (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
25 |
WARN: Reopening existing segment 'shmid' | |
|
Description |
Unable to get a Oracle TUXEDO system shared memory segment. The |
Action |
No action required. | |
26 |
ERROR: shmat: Missing segment 'shmid' | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. Unable to attach a Oracle TUXEDO system shared memory segment. The |
Action |
Restart your Oracle TUXEDO system IPC Helper service or reboot your machine if the problem is persistent. | |
27 |
警告: shmdt: セグメントをアンマップできません | |
|
説明 |
Oracle Tuexdoシステムの共有メモリー・セグメントをデタッチできません。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
28 |
ERROR: Cannot release semaphore (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
29 |
ERROR: Cannot create timer event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
31 |
ERROR: Cannot create pause event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
32 |
ERROR: Cannot create timer start event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
33 |
ERROR: Cannot create timer thread (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
34 |
ERROR: Cannot wait on start event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
35 |
ERROR: Cannot send message to timer thread threadId (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
39 |
ERROR: Memory allocation error (line line_number) | |
|
Description |
An attempt to allocate memory from the operating system using |
Action |
Reduce the memory usage on the machine or increase the amount of physical memory on the machine. | |
40 |
ERROR: Cannot create watchdog start event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
41 |
ERROR: Cannot create watchdog thread (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
42 |
ERROR: Removing invalid process pid | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. Process pid is no longer alive, and it will be removed. |
Action |
Contact Oracle Customer Support. | |
43 |
ERROR: Watchdog wait failed (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. Waiting for the process to terminate has failed. |
Action |
The extended error information is described in error by calling | |
44 |
ERROR: Cannot create new process event (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
45 |
ERROR: Cannot create ipc data (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. Creating the Oracle TUXEDO system IPC data has failed. |
Action |
The extended error information is described in error by calling | |
46 |
ERROR: Cannot create server pipe 'IPC_SERVER_PIPE' (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
47 |
ERROR: Pipe connect failed (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
48 |
ERROR: Cannot read pipe (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
49 |
ERROR: Unexpected read size read/ipcop | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
Contact Oracle Customer Support. | |
50 |
ERROR: Unexpected request action | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. Invalid IPC request was given to the Oracle TUXEDO system IPC Helper. |
Action |
Contact Oracle Customer Support. | |
51 |
ERROR: Cannot write to pipe (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
52 |
ERROR: Unexpected write size write/reply | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
Contact Oracle Customer Support. | |
53 |
ERROR: Cannot flush pipe (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
54 |
WARN: Cannot disconnect pipe (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
55 |
ERROR: Cannot start IPC services (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
56 |
ERROR: Cannot set service status (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
57 |
ERROR: Cannot create worker thread (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
58 |
情報: IPCサーバーが終了します | |
|
説明 |
Oracle TuexdoシステムのIPC Helperサーバーが終了します。 |
アクション |
アクションは不要です。 | |
59 |
ERROR: Cannot start process in background mode, cmdline=val, errno=val2 | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. An attempt to start the current process in background mode failed. |
Action |
The extended error information is described in error by calling | |
60 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
Oracle Tuexdoシステム内部のIPCエラーが発生しました。 |
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
61 |
ERROR: Could not make pipe, errno=error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
62 |
ERROR: Could not fork, errno=error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
63 |
ERROR: Child dup error, rc=retcode, errno=error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The _open_osfhandle system function call failed. |
Action |
The extended error information is described in error by calling | |
64 |
ERROR: Parent dup error while saving stdout, errno=error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The _dup system function call failed. |
Action |
The extended error information is described in error by calling | |
65 |
WARN: pager: wait status 0xstatus, errno=error | |
|
Description |
The |
Action |
The extended error information is described in error by calling | |
66 |
ERROR: Cannot create process (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
67 |
ERROR: Could not allocate thread local storage, error number = error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
68 |
ERROR: Could not allocate thread local storage, error number = error | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling | |
71 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
|
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
72 |
エラー: TUXDIR環境変数が設定されていません | |
|
説明 |
Oracle Tuexdoシステムの環境変数 |
アクション |
環境変数 | |
関連項目 |
Oracle Tuexdoシステム・インストレーション・ガイド | |
73 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
オペレーティング・システムからbuildclientに対してメモリーを割り当てようとしましたが失敗しました。 |
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
74 |
ERROR: Unused arguments passed to command | |
|
Description |
Extra arguments were given to the buildclient command for building Oracle TUXEDO system clients. |
Action |
Consult your Oracle TUXEDO system documentation for valid arguments for | |
See Also |
| |
75 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
|
アクション |
マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
76 |
ERROR: Can't open tempfile filename | |
|
Description |
An attempt to open a temporary file using fopen failed. |
Action |
Check the permissions of the file and repeat the operation. | |
See Also |
fopen | |
77 |
ERROR: Can't execute cc_cmd | |
|
Description |
The buildclient command was unable to execute the C compiler command. The C compiler command that buildclient attempted to execute is given as part of this error message. |
Action |
Verify that the Microsoft Visual C++ compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in your PATH environment variable. | |
See Also |
buildclient(1) | |
78 |
ERROR: Can't execute cc_cmd | |
|
Description |
The buildclient command was unable to execute the C compiler command. The C compiler command that buildclient attempted to execute is given as part of this error message. |
Action |
Verify that the Microsoft Visual C++ compiler has been installed on the machine, that it is executable, and that the directory containing the compiler is included in your PATH environment variable. | |
See Also |
buildclient(1) | |
94 |
エラー: 登録キーをオープンできません | |
|
説明 |
Oracle Tuexdoシステムのパフォーマンス・モニター(\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\TUXEDO IPC Helper\\Performance)のレジストリ・キーをオープンできません。 |
アクション |
通常、このエラーの発生は、Oracle TuexdoシステムのIPC Helperサービスが存在しないか、正しく作成されなかったことに起因します。Oracle Tuexdoシステムの配布媒体に同梱されているsetupプログラムを最初に実行して、ソフトウェアをインストールする必要があります。インストールの過程で、Oracle TuexdoシステムのIPC Helperサービスおよびレジストリ・キーが作成されます。他のエラーとして考えられるのは、レジストリ・データベースがなんらかの理由でロックされたことです。問題が解決しない場合は、マシンを再起動する必要があります。 | |
95 |
エラー: 'First Counter'データを取得できません | |
|
説明 |
Oracle Tuexdoシステムのパフォーマンス・モニター(\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\TUXEDO IPC Helper\\Performance)のレジストリから"First Counter"データを取得できません。 |
アクション |
通常、このエラーの発生は、Oracle TuexdoシステムのIPC Helperサービスが存在しないか、正しく作成されなかったことに起因します。Oracle Tuexdoシステムの配布媒体に同梱されているsetupプログラムを最初に実行して、ソフトウェアをインストールする必要があります。インストールの過程で、Oracle TuexdoシステムのIPC Helperサービスおよびレジストリ・キーが作成されます。他のエラーとして考えられるのは、レジストリ・データベースがなんらかの理由でロックされたことです。問題が解決しない場合は、マシンを再起動する必要があります。 | |
96 |
エラー: 'First Help'データを取得できません | |
|
説明 |
Oracle Tuexdoシステムのパフォーマンス・モニター(\\HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\TUXEDO IPC Helper\\Performance)のレジストリから"First Help"データを取得できません。 |
アクション |
通常、このエラーの発生は、Oracle TuexdoシステムのIPC Helperサービスが存在しないか、正しく作成されなかったことに起因します。Oracle Tuexdoシステムの配布媒体に同梱されているsetupプログラムを最初に実行して、ソフトウェアをインストールする必要があります。インストールの過程で、Oracle TuexdoシステムのIPC Helperサービスおよびレジストリ・キーが作成されます。他のエラーとして考えられるのは、レジストリ・データベースがなんらかの理由でロックされたことです。問題が解決しない場合は、マシンを再起動する必要があります。 | |
99 |
ERROR: Cannot create process maintenance thread (error) | |
|
Description |
An internal Oracle TUXEDO system IPC error has occurred. The |
Action |
The extended error information is described in error by calling |
![]() |
![]() |
![]() |