システム・メッセージ: CMDTUXカタログ1200-1299
|
![]() |
![]() |
1201 |
ERROR: *ROUTING entry entry_name does not meet the requirement that the lower limit of every range must be less than or equal to the upper limit | |
|
Description |
The value specified in the first part of a range entry must be less than or equal to the value specified in the second part of a range entry. The value specified in the first part of the range entry was greater than the value specified in the second part of a range entry. |
Action |
Recode the range entry so that the first value specified is less than or equal to the second value. | |
See Also |
| |
1202 |
ERROR: *ROUTING entry entry_name needs a single quote at the end of a character string | |
|
Description |
In a routing entry, a double quote was found after an odd number of non-escaped single quotes. |
Action |
Inspect the single quotes in the flagged routing entry to ensure the proper format. | |
See Also |
| |
1203 |
ERROR: or a backslash to escape a double quote. | |
|
Description |
This message is printed as the second part of message 1202. 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 |
This message is printed as the second part of message 1202. Examine the routing field flagged as being in error. Make sure that the | |
See Also |
| |
1204 |
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 |
| |
1205 |
ERROR: *ROUTING entry entry_name mixes a numeric value with a string value in a RANGES statement | |
|
Description |
The specified entry in the ROUTING section of the UBBCONFIG file contains a |
Action |
Modify the | |
See Also |
| |
1206 |
ERROR: *ROUTING entry entry_name contains an invalid group name grpname | |
|
Description |
A group specified in the |
Action |
Make sure that the grpname flagged as being in error is defined in the GROUPS section of the UBBCONFIG file. Check that the two names are spelled the same way. Also, examine any previous error reported by | |
See Also |
| |
1207 |
ERROR: *ROUTING entry entry_name contains an invalid "RANGES" value. | |
|
Description |
The ROUTING entry specified contains a |
Action |
Fix the format of the flagged | |
See Also |
| |
1208 |
ERROR: *ROUTING entry entry_name specifies an illegal BUFTYPE of ALL | |
|
Description |
The ROUTING table entry flagged in the error message has a |
Action |
Specify a specific buffer type for the routing table entry in error, and reload the configuration file. | |
See Also |
| |
1209 |
ERROR: Buffer types in section_name entry entry_name start with ',' or null | |
|
Description |
The |
Action |
Ensure that at least one valid buffer type is specified in the | |
See Also |
| |
1210 |
ERROR: section_name entry entry_name contains a null buffer type name | |
|
Description |
The |
Action |
Change the | |
See Also |
| |
1211 |
ERROR: section_name entry entry_name contains an unexpected comma | |
|
Description |
The |
Action |
Change the | |
See Also |
| |
1212 |
ERROR: section_name entry entry_name contains an excessively long type name type_name | |
|
Description |
One of the buffer type names specified in the |
Action |
Change the buffer type name so that it is no longer than 8 bytes, and reload the configuration file. | |
See Also |
| |
1214 |
ERROR: section_name entry entry_name contains an unexpected colon or comma | |
|
Description |
The |
Action |
Examine the | |
See Also |
| |
1215 |
ERROR: section_name entry entry_name contains a null buffer subtype name | |
|
Description |
The |
Action |
Fix any subtype list which ends in a comma. Specify one or more subtypes for any type which requires a subtype, and do not follow any type which does not accept subtypes with a colon. When done, reload the configuration file. | |
See Also |
| |
1216 |
ERROR: section_name entry entry_name contains excessively long subtype name subtype_name | |
|
Description |
One of the buffer subtype names specified in the |
Action |
Change the buffer subtype name so that it is no longer than 16 bytes, and reload the configuration file. | |
See Also |
| |
1217 |
ERROR: section_name entry entry_name specified both '*' and a specific subtype name | |
|
Description |
A subtype list contained within the |
Action |
If the application should accept all subtype names, specify "*" without specifying any specific subtype names. If the application should accept only specific subtype names, remove "*" from the list of subtype names. When the change has been made, reload the configuration file. | |
See Also |
| |
1218 |
ERROR: *ROUTING entry entry_name specifies '*' where it is not allowed | |
|
Description |
The |
Action |
If routing on a view, specify the specific buffer type to be routed on. If routing on an | |
See Also |
| |
1219 |
ERROR: *ROUTING entry %s contains duplicate group name (%s) in one RANGE entry. | |
|
Description |
There are duplicated server groups configured for a single range of values. |
Action |
Check the ROUTING entry and remove the duplicated server groups. | |
1220 |
ERROR: *ROUTING entry %s contains more than %d groups in one RANGE entry. | |
|
Description |
The number of server groups configured for a single range of values exceeds the upper limit. |
Action |
Check the ROUTING entry and reduce the number of server groups. | |
1221 |
ERROR: section_name entry entry_name contains a duplicate type(type_name)/subtype(subtype_name) pair | |
|
Description |
The |
Action |
Modify the | |
See Also |
| |
1225 |
ERROR: *SERVICES entry entry_name does not have the same BUFTYPE for all entries of this service. | |
|
Description |
If multiple entries exist in the SERVICES section with the same service name but with different |
Action |
Specify the same | |
See Also |
| |
1228 |
ERROR: section entry service must have the same BUFTYPE for all *SERVICE entries | |
|
Description |
If a service has multiple entries in the SERVICES section (for different |
Action |
Modify all entries for service so that the | |
See Also |
| |
1229 |
ERROR: section entry service too many buffer type/subtypes specified | |
|
Description |
The maximum number of type/subtype combinations that a service can accept was exceeded. |
Action |
This is a fixed limit that requires a recompiled Oracle TUXEDO system version to increase. Contact your Oracle TUXEDO system Technical Support. Other options are:
| |
See Also |
| |
1231 |
ERROR: Unable to get user id | |
|
Description |
While executing |
Action |
Make sure that a password entry exists for the administrator who is running the | |
See Also |
| |
1232 |
ERROR: tpchkauth failed - Uunixerr = code | |
|
Description |
While executing |
Action |
Attempt to determine why the UNIX System call is failing. Often, this error will occur if the | |
See Also |
| |
1233 |
ERROR: Cannot determine authentication level | |
|
Description |
The |
Action |
Attempt to determine why the | |
See Also |
| |
1237 |
ERROR: Can't open filename | |
|
Description |
When writing out the current buffer values, |
Action |
Check that the directory has write and execute permissions set correctly, and that the file system has the proper resources for creating and writing a file. | |
See Also |
| |
1267 |
エラー: サーバーを起動/停止できません。メモリーの割当てに失敗しました | |
|
説明 |
|
アクション |
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。一時的な回避策は、一度に1つのマシン、グループまたはサーバーを起動またはシャットダウンして、必要な領域を減らすことです。 | |
関連項目 |
| |
1268 |
ERROR: GROUP entry, group TMS specified and LMID, lmid does not have TLOGDEVICE | |
|
Description |
If any group on a machine has a |
Action |
Modify the configuration file. | |
See Also |
| |
1270 |
エラー: ネットワーク・アドレスを確立できませんでした。デバイスとアドレスを調べてください | |
|
説明 |
|
アクション |
構成ファイルのNETWORKセクションで、このマシンの | |
関連項目 |
| |
1271 |
ERROR: Invalid BRIDGE device pathname | |
|
Description |
The |
Action |
Modify the | |
See Also |
| |
1273 |
ERROR: Invalid option string for SECURITY keyword | |
|
Description |
The |
Action |
Modify the configuration file. | |
See Also |
| |
1275 |
エラー: 暗号化鍵を作成できません | |
|
説明 |
ランダムに生成される暗号化鍵を作成しようとしましたが、予期しないエラーが発生しました。 |
アクション |
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。 | |
1276 |
ERROR: Cannot create encryption schedule for application password | |
|
Description |
An unexpected error occurred when attempting to encrypt the application security password. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1277 |
ERROR: Unable to encrypt application password | |
|
Description |
An unexpected error occurred when attempting to encrypt the application security password. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1278 |
ERROR: Could not create security key database directory path error number | |
|
Description |
A directory to hold encrypted security key information could not be created. |
Action |
Verify that | |
See Also |
| |
1279 |
ERROR: Invalid file type for security key database directory path | |
|
Description |
A directory necessary to hold encrypted security key information could not be created because a file exists with the same path name. |
Action |
Remove a file named . | |
See Also |
| |
1280 |
ERROR: Cannot change permissions of security key database directory path errno = errno_val | |
|
Description |
The access permissions of a directory necessary to hold encrypted security key information could not be modified. |
Action |
Change ownership of the subdirectory named | |
See Also |
| |
1281 |
ERROR: Cannot open security key database file for writing, path pathname errno = errno_val | |
|
Description |
|
Action |
Verify that the | |
See Also |
| |
1282 |
ERROR: Cannot write to security key database file path errno = errno_val | |
|
Description |
|
Action |
Verify that the | |
See Also |
| |
1283 |
エラー: セキュリティ・キー・データベース・ディレクトリを作成できませんでした | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1284 |
エラー: セキュリティ・キー・データベース・ディレクトリとして無効なファイル・タイプです | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1285 |
エラー: セキュリティ・キー・データベース・ディレクトリの許可を変更できません | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1286 |
エラー: 書込みをするためにセキュリティ・キー・データベース・ファイルをオープンできません | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1287 |
エラー: セキュリティ・キー・データベース・ファイルに書込みできません | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1288 |
エラー: セキュリティ・キーの暗号化エラー | |
|
説明 |
|
アクション |
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。 |
![]() |
![]() |
![]() |