コンテンツはここから始まります

システム・メッセージ: 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

ubbconfig(5)


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

ubbconfig(5)


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 RANGES string starts and ends with a double quote, and that the previous string in the configuration file was properly terminated with a double quote. Remember that any double quote character to be taken literally as part of a range limit must be preceded by a backslash. Examine each string range value within the RANGES field, and verify that it starts and ends with a single quote. Remember that any single quote character to be taken literally as part of a range limit must be preceded by two backslashes. Correct all errors in the format of the routing information, and reload the configuration file.

See Also

ubbconfig(5)


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 RANGES statement. This is not allowed.

Action

The values specified in the RANGES statement must be appropriate to the type of the field on which routing is being conducted. Look in the field tables to determine the type of the field listed for this routing entry and change any routing values which are inappropriate for this field type.

See Also

ubbconfig(5)


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 RANGES entry in which one part of a range is a numeric quantity and the other part of that range is a string category. This is not allowed.

Action

Modify the RANGES element flagged as being in error so that all range limits are of the same type and match the type defined for the field being routed on. Reload the configuration file.

See Also

ubbconfig(5)


1206


ERROR: *ROUTING entry entry_name contains an invalid group name grpname

Description

A group specified in the RANGES parameter for the specified ROUTING section entry was not defined in the GROUPS section.

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 tmloadcf that may have caused the corresponding entry in the GROUPS section to not be recognized.

See Also

ubbconfig(5)


1207


ERROR: *ROUTING entry entry_name contains an invalid "RANGES" value.

Description

The ROUTING entry specified contains a RANGES value that does not follow the required format.

Action

Fix the format of the flagged RANGES entry. Often, the format error is due to a range where the first value does not start with MIN, a number, a single quote, a range where the second value does not start with MAX, a number, a single quote, a range that is not followed by a colon, contains an invalid XPATH string, or a server group name that is not followed by a comma or a double quote to terminate the RANGES entry.

See Also

ubbconfig(5)


1208


ERROR: *ROUTING entry entry_name specifies an illegal BUFTYPE of ALL

Description

The ROUTING table entry flagged in the error message has a BUFTYPE of ALL. This is not allowed.

Action

Specify a specific buffer type for the routing table entry in error, and reload the configuration file.

See Also

ubbconfig(5)


1209


ERROR: Buffer types in section_name entry entry_name start with ',' or null

Description

The BUFTYPE list specified in an entry in the SERVICES section or in the ROUTING section of the UBBCONFIG file starts with a comma, or is equal to the null string. This is not allowed.

Action

Ensure that at least one valid buffer type is specified in the BUFTYPE string, and make sure that the string does not begin with a comma. When the error has been fixed, reload the configuration file.

See Also

ubbconfig(5)


1210


ERROR: section_name entry entry_name contains a null buffer type name

Description

The BUFTYPE parameter specified in the ROUTING section or SERVICES section contains one or more null buffer type names.

Action

Change the BUFTYPE entry flagged as being in error. Make certain that the beginning of the BUFTYPE string specifies a valid buffer type identifier, and that the string does not start with a punctuation mark. Also, make sure that each semicolon in the BUFTYPE string is followed by a valid buffer type identifier. Reload the configuration file.

See Also

ubbconfig(5)


1211


ERROR: section_name entry entry_name contains an unexpected comma

Description

The BUFTYPE parameter specified in the ROUTING section or SERVICES section of the UBBCONFIG file contains an unexpected comma.

Action

Change the BUFTYPE entry flagged as being in error. The only places where commas are allowed to occur in BUFTYPE entries are between entries of a list of multiple subtypes of a particular type. When the error has been fixed, the configuration file should be reloaded.

See Also

ubbconfig(5)


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 BUFTYPE parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file exceeds the maximum allowed length. The maximum allowed length of a buffer type name is 8 bytes.

Action

Change the buffer type name so that it is no longer than 8 bytes, and reload the configuration file.

See Also

ubbconfig(5)


1214


ERROR: section_name entry entry_name contains an unexpected colon or comma

Description

The BUFTYPE parameter specified in an entry in the ROUTING section or SERVICES section of the UBBCONFIG file contains an unexpected colon or comma.

Action

Examine the BUFTYPE entry flagged as being in error to determine the exact problem. A colon may occur only between a name of a type and the name of the first acceptable subtype. A comma may occur only between names of subtypes. When the error has been corrected, reload the configuration file.

See Also

ubbconfig(5)


1215


ERROR: section_name entry entry_name contains a null buffer subtype name

Description

The BUFTYPE parameter specified in an entry in the ROUTING section or SERVICES section of the UBBCONFIG file contains a null buffer subtype name. This may occur when a colon or comma is followed by another punctuation mark without any intervening subtype name.

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

ubbconfig(5)


1216


ERROR: section_name entry entry_name contains excessively long subtype name subtype_name

Description

One of the buffer subtype names specified in the BUFTYPE parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file exceeds the maximum allowed length. The maximum allowed length of a buffer subtype name is 16 bytes.

Action

Change the buffer subtype name so that it is no longer than 16 bytes, and reload the configuration file.

See Also

ubbconfig(5)


1217


ERROR: section_name entry entry_name specified both '*' and a specific subtype name

Description

A subtype list contained within the BUFTYPE parameter of a SERVICES section or ROUTING section entry of the UBBCONFIG file specified both the wild-card subtype "*" and a specific subtype name. This is not allowed.

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

ubbconfig(5)


1218


ERROR: *ROUTING entry entry_name specifies '*' where it is not allowed

Description

The BUFTYPE parameter of a ROUTING section entry of the UBBCONFIG file specified '*' as a buffer subtype. This is not allowed.

Action

If routing on a view, specify the specific buffer type to be routed on. If routing on an FML buffer, no buffer subtypes are allowed. Reload the configuration file once it has been modified.

See Also

ubbconfig(5)


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 BUFTYPE parameter of a SERVICES section entry or ROUTING section entry in the UBBCONFIG file specified duplicate type/subtype pairs. (For types without any subtype specified, the BUFTYPE parameter specified duplicate type pairs.)

Action

Modify the BUFTYPE parameter so that the same type/subtype pair is not specified more than once. Reload the configuration file.

See Also

ubbconfig(5)


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 SRVGRP parameters, the BUFTYPE parameter must be the same for all of the entries. This rule was violated for the service entry named in the error message.

Action

Specify the same BUFTYPE parameters for all instances of a particular service name. Then reload the configuration file.

See Also

ubbconfig(5)


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 SRVGRP parameters), all entries must have the same BUFTYPE parameter.

Action

Modify all entries for service so that the BUFTYPE parameter is consistent.

See Also

ubbconfig(5)


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:

  • Reduce the number of type/subtype combinations by using "*" for a subtype wildcard.

  • Have the server process call tptypes() on its input buffer, and enforce its own rules concerning allowed buffer type/subtype combinations.

See Also

tptypes(3c), ubbconfig(5)


1231


ERROR: Unable to get user id

Description

While executing tmconfig, the program was unable to get the password entry based on the current user identifier.

Action

Make sure that a password entry exists for the administrator who is running the tmconfig command. Contact your Oracle TUXEDO system Technical Support.

See Also

tmconfig(1)


1232


ERROR: tpchkauth failed - Uunixerr = code

Description

While executing tmconfig, an operating system error occurred while attempting to determine the level of authentication required by the application configuration. A code is printed indicating the specific UNIX System call which failed. These codes may be referenced in the header file <Uunix.h>.

Action

Attempt to determine why the UNIX System call is failing. Often, this error will occur if the TUXCONFIG shell variable is not set consistently in this process and the rest of the application.

See Also

tmconfig(1), tpchkauth(3c)


1233


ERROR: Cannot determine authentication level

Description

The tpchkauth() function returned an error when called by tmconfig to determine the level of authentication required by the application configuration.

Action

Attempt to determine why the tpchkauth() function call is failing. Often, this will be due to an incorrect setting of the TUXCONFIG shell variable.

See Also

tmconfig(1), tpinit(3c)


1237


ERROR: Can't open filename

Description

When writing out the current buffer values, tmconfig was unable to create and open a temporary file for writing (in the current directory for DOS, or /tmp for Oracle TUXEDO system).

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

tmconfig(1)


1267


エラー: サーバーを起動/停止できません。メモリーの割当てに失敗しました

説明

realloc()を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、TMSの起動またはシャットダウンに関連する内部データ構造体の作成中に失敗しました。

アクション

マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。一時的な回避策は、一度に1つのマシン、グループまたはサーバーを起動またはシャットダウンして、必要な領域を減らすことです。

関連項目

tmboot(1)


1268


ERROR: GROUP entry, group TMS specified and LMID, lmid does not have TLOGDEVICE

Description

If any group on a machine has a TMS specified, the TLOGDEVICE parameter in the MACHINES section must be set.

Action

Modify the configuration file.

See Also

ubbconfig(5)


1270


エラー: ネットワーク・アドレスを確立できませんでした。デバイスとアドレスを調べてください

説明

BRIDGEプロセスが、受信ネットワーク接続に対する独自のリスニング・アドレスを確立できませんでした。

アクション

構成ファイルのNETWORKセクションで、このマシンのNADDRおよびBRIDGEパラメータを確認してください。

関連項目

ubbconfig(5)、NETWORKセクション


1271


ERROR: Invalid BRIDGE device pathname

Description

The BRIDGE process' networking device pathname is set incorrectly, or the device does not exist.

Action

Modify the BRIDGE parameter for this machine in the configuration file's NETWORK section.

See Also

ubbconfig(5), NETWORK section


1273


ERROR: Invalid option string for SECURITY keyword

Description

The SECURITY parameter in the RESOURCES section of the configuration file is invalid.

Action

Modify the configuration file.

See Also

ubbconfig(5)


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 APPDIR exists, and that directory permissions will allow tmloadcf to create a subdirectory there. Verify that the APPDIR's file system has free disk blocks and inodes.

See Also

ubbconfig(5), MACHINES section


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 .adm in the APPDIR directory.

See Also

ubbconfig(5), MACHINES section


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 .adm in the APPDIR directory to the administrative UID.

See Also

ubbconfig(5), MACHINES section


1281


ERROR: Cannot open security key database file for writing, path pathname errno = errno_val

Description

tmloadcf could not open a file (for writing, with create option) necessary to hold encrypted security key information.

Action

Verify that the APPDIR 's file system has free disk blocks and inodes. In the APPDIR directory, remove a subdirectory named .adm and all files contained in it. Then run tmloadcf again.

See Also

ubbconfig(5), MACHINES section


1282


ERROR: Cannot write to security key database file path errno = errno_val

Description

tmloadcf could not write a file necessary to hold encrypted security key information.

Action

Verify that the APPDIR 's file system has free disk blocks and inodes. In the APPDIR directory, remove a subdirectory named .adm and all files contained in it. Then run tmloadcf again.

See Also

ubbconfig(5), MACHINES section


1283


エラー: セキュリティ・キー・データベース・ディレクトリを作成できませんでした

説明

tagentプロセスが、暗号化されたセキュリティ・キーの情報を保持するために必要なディレクトリを作成できませんでした。

アクション

  • APPDIRが存在し、tagentプロセスによるその場所でのサブディレクトリの作成がディレクトリ権限によって許可されることを検証してください。

  • APPDIRのファイル・システムのディスク・ブロックおよびiノードに空きがあることを検証してください。

関連項目

ubbconfig(5)、MACHINESセクション


1284


エラー: セキュリティ・キー・データベース・ディレクトリとして無効なファイル・タイプです

説明

tagentプロセスが、暗号化されたセキュリティ・キーの情報を保持するために必要なディレクトリを作成しようとしましたが、パス名が同じファイルが存在するためできませんでした。

アクション

APPDIRディレクトリの.admという名前のファイルを削除してください。

関連項目

ubbconfig(5)、MACHINESセクション


1285


エラー: セキュリティ・キー・データベース・ディレクトリの許可を変更できません

説明

tagentプロセスが、暗号化されたセキュリティ・キーの情報を保持するために必要なディレクトリの権限を変更できませんでした。

アクション

APPDIRディレクトリの.admという名前のサブディレクトリの所有権をUIDに変更してください。

関連項目

ubbconfig(5)、MACHINESセクション


1286


エラー: 書込みをするためにセキュリティ・キー・データベース・ファイルをオープンできません

説明

tagentプロセスが、暗号化されたセキュリティ・キーの情報を保持するために必要なファイルを(書込み用に、作成オプションを使用して)オープンできませんでした。

アクション

  • APPDIRのファイル・システムのディスク・ブロックおよびiノードに空きがあることを検証してください。

  • APPDIRディレクトリで、.admという名前のサブディレクトリおよびその中のすべてのファイルを削除してください。

関連項目

ubbconfig(5)、MACHINESセクション


1287


エラー: セキュリティ・キー・データベース・ファイルに書込みできません

説明

tagentプロセスが、暗号化されたセキュリティ・キーの情報を保持するために必要なファイルに書き込めませんでした。

アクション

  • APPDIRのファイル・システムのディスク・ブロックおよびiノードに空きがあることを検証してください。

  • APPDIRディレクトリで、.admという名前のサブディレクトリおよびその中のすべてのファイルを削除してください。

関連項目

ubbconfig(5)、MACHINESセクション


1288


エラー: セキュリティ・キーの暗号化エラー

説明

tagentによるセキュリティ・キー・データベース・ファイルの設定中に、暗号化の問題が発生しました。

アクション

Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。


 先頭に戻る 前 次