システム・メッセージ: CMDTUXカタログ1100-1199
|
1110 |
エラー: TUXDIR環境変数が設定されていません | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1111 |
エラー: TPINIT型付きバッファを割当てできませんでした | |
|
説明 |
シャットダウン中に、内部データ構造体のメモリーを割り当てられませんでした。 |
アクション |
物理メモリーを独占している可能性があるプロセスを削除し、アプリケーションのipcキーが正しいことを確認し、UNIX | |
1112 |
エラー: ユーザー用のエントリを見つけられませんでした | |
|
説明 |
|
アクション |
ログインを検証してシステム管理者に連絡してください。 | |
1113 |
エラー: このコマンドは管理者用です | |
|
説明 |
アプリケーションのroot(システム管理者)以外のユーザーが、起動またはシャットダウンのリクエストを実行しようとしています。 |
アクション |
これらのコマンドを発行するユーザーは、システム管理者(root)であることが必要です。 | |
関連項目 |
| |
1126 |
警告: サーバーをシャットダウンできません。メモリーの割当てに失敗しました | |
|
説明 |
シャットダウン処理に使用するサーバー・グループ情報を保持するための領域を割り当てられません。 |
アクション |
無関係なプロセスを強制終了して | |
関連項目 |
| |
1130 |
ERROR: Argument arg_value to option -e is not numeric | |
|
Description |
The |
Action |
Correct the arguments to the | |
See Also |
| |
1133 |
ERROR: Cannot determine authentication level | |
|
Description |
The |
Action |
Attempt to determine why the | |
See Also |
| |
1134 |
ERROR: Unable to get user id | |
|
Description |
The |
Action |
Have the UNIX System administrator correct any problems related to the entry of the user invoking | |
See Also |
| |
1135 |
ERROR: Unable to obtain application password | |
|
Description |
The |
Action |
If the | |
See Also |
| |
1138 |
ERROR: Can't process a message with an unknown release, relnum | |
|
Description |
The Oracle TUXEDO system provides a means for converting a message from one release to another. It will convert messages from a previous release to the current one and vice versa. For example, Oracle TUXEDO system Release 4.1.x will interoperate with Release 4.2.x and vice versa. The message received was not one from the current release or the previous one but from release relnum. |
Action |
Verify that the releases of the Oracle TUXEDO system software installed are valid. | |
See Also |
Oracle TUXEDO Administrator's Guide | |
1139 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing client information when forwarding unsolicited messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1140 |
WARN: WSH (pid) should not be ignoring unsolicited messages | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process has found a Workstation handler (WSH) that will not accept unsolicited messages on behalf of its /WS clients. The process id of the WSH is pid. /WS clients connected to this WSH will not be able to receive unsolicited messages regardless of the notification method they will have selected. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1141 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing Workstation handler (WSH) information when forwarding unsolicited messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1142 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase the size of an internal table. This table was to be used for storing client information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1143 |
ERROR: Unable to find WSH (pid) | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to locate the Workstation handler (WSH) that was going to be used to forward a broadcast messages to one or more Workstation clients. |
Action |
The | |
1144 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase of size of an internal table. This table was to be used for storing client information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1145 |
エラー: システム・リソースの不足のために、ブロードキャストを送信できません | |
|
説明 |
ブロッキング状態のため、Oracle TuxedoシステムのBulletin Board Liaison (BBL)管理プロセスが、ワークステーション・ハンドラへの任意通知型メッセージの転送に失敗しました。BBLによってこのエラー・メッセージがユーザー・ログに書き込まれ、エラーが戻されます。複数のブロッキング状態が発生した場合のみ、BBLによってこのエラー・メッセージが記録されます。それ以外の場合は、ユーザー・ログに警告メッセージが書き込まれます。 |
アクション |
アプリケーション管理者は、UNIXシステム上に使用可能なプロセス間通信(IPC)リソースが十分あるかどうかを確認する必要があります。UNIXコマンド | |
1146 |
WARN: Unable to send broadcast to WSH (pid), tperrno = tperrno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to forward the unsolicited message to a Workstation handler with a process id of pid. The BBL will write this message to the user log and attempt to send the unsolicited message to the next targeted Workstation handler, or native client. |
Action |
Check tperrno_val against the error numbers in the Oracle TUXEDO system header file | |
1149 |
ERROR: Unable to send broadcast due to lack of system resources, tperrno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client process due to a blocking condition. The BBL will write this error message to the user log and return an error. The BBL will only return an error if several blocking conditions have occurred. Otherwise a warning message is posted in the user log. |
Action |
The application administrator will need to determine whether or not there are sufficient inter-process communication (IPC) resources available on the machine. The UNIX command | |
1150 |
WARN: Unable to send broadcast to client (pid) tperrno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client with a process id of pid. The BBL will write this message to the user log and attempt to send the unsolicited message to the next targeted client. |
Action |
Check tperrno_val against the error numbers in the Oracle TUXEDO system header file | |
1158 |
ERROR: Unable to send unsolicited message to client (pid) | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client with a process id of pid. The BBL failed due to a Oracle TUXEDO system error. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1159 |
エラー: 掲示板のUSIGNALパラメータが無効です | |
|
説明 |
Oracle TuxedoシステムのBulletin Board Liaison (BBL)管理プロセスは、ワークステーション・ハンドラまたはネイティブ・クライアントに対して、2つのシグナル( |
アクション |
Oracle Tuxedoシステム・アプリケーションの管理者は、構成ファイルの | |
1160 |
ERROR: Unable to send signal to client, pid = pid | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send a signal to process pid. Clients that have selected |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1161 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing Workstation handler (WSH) information when forwarding unsolicited messages. |
Action |
Check tperrno_val against the error numbers in the UNIX header file | |
1162 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The Oracle TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase the size of an internal table. This table was to be used for storing Workstation handler information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX header file | |
1163 |
ERROR: invalid option - argument to -u not n, u, or j | |
|
Description |
The command option |
Action |
Re-execute the command using a valid -u argument. | |
See Also |
| |
1165 |
ERROR: Machine name must be a valid identifier. | |
|
Description |
An invalid identifier was used as a symbolic name for a machine. |
Action |
Use a valid identifier as a symbolic name for that machine. This name cannot contain a period or comma, and must be 30 characters or less. | |
See Also |
| |
1166 |
ERROR: MAXWSCLIENTS value (val) exceeds system limit (lim) for this site | |
|
Description |
|
Action |
Reset | |
See Also |
| |
1168 |
ERROR: UID is not effective user ID | |
|
Description |
The |
Action |
Verify that the effective user id of the user invoking | |
1171 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
Oracle Tuxedoシステムの |
アクション |
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
関連項目 |
| |
1175 |
WARN: *RESOURCES SYSTEM_ACCESS setting cannot be overridden in *SERVERS section | |
|
Description |
An attempt was made to override the setting of the RESOURCES section |
Action |
Check the | |
See Also |
| |
1176 |
WARN: *RESOURCES SYSTEM_ACCESS setting cannot be overridden in *SERVERS section | |
|
Description |
An attempt was made to override the setting of the RESOURCES section |
Action |
Check the | |
See Also |
| |
1178 |
エラー: 接続しているBRIDGEのUID/GIDが適切ではありません | |
|
説明 |
4.2より前のOracle Tuxedoシステムの |
アクション |
| |
関連項目 |
| |
1183 |
ERROR: Group name grpname must not contain *, comma, or colon | |
|
Description |
A group name specified starting in the first column of a line in the |
Action |
Verify that the configuration file has the proper syntax. If necessary, choose a new name for the group which meets the syntax restrictions. | |
See Also |
| |
1186 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1188 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1190 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1191 |
ERROR: *ROUTING entry routing_name has more than one default range | |
|
Description |
The ROUTING table entry routing_name was specified with more than one default range specification. This is not allowed. A default range specification is one which has the meta-character "*" (wild-card) in the position of a range. |
Action |
Recode the | |
See Also |
| |
1193 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
| |
1196 |
ERROR: *ROUTING entry entry_name lacks a single quote at the end of a character string or lacks a backslash to escape a double quote | |
|
Description |
The routing entry entry_name lacks a single quote at the end of a character string, or lacks a backslash to escape a double quote within a character string. |
Action |
Examine the routing field flagged as being in error. Make sure that the | |
See Also |
| |
1197 |
ERROR: or a backslash to escape a double quote. | |
|
Description |
The routing entry entry_name lacks a single quote at the end of a character string, or lacks a backslash to escape a double quote within a character string. |
Action |
Examine the routing field flagged as being in error. Make sure that the | |
1198 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
| |
1199 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
|