|
|
1300
|
エラー: セキュリティ・パスワード暗号化鍵を生成できませんでした |
|
|
説明
|
セキュリティ・キー情報をリモート・マシンに渡す際に、暗号化アルゴリズム・エラーが発生しました。
|
|
アクション
|
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
|
|
1301
|
エラー: セキュリティ・パスワード暗号化スケジュールを生成できませんでした |
|
|
説明
|
セキュリティ・キー情報をリモート・マシンに渡す際に、暗号化アルゴリズム・エラーが発生しました。
|
|
アクション
|
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
|
|
1302
|
エラー: アプリケーション・セキュリティ・キーを暗号化できませんでした |
|
|
説明
|
セキュリティ・キー情報をリモート・マシンに渡す際に、暗号化アルゴリズム・エラーが発生しました。
|
|
アクション
|
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
|
|
1307
|
ERROR: Unable to obtain application password |
|
|
Description
|
The tmconfig command was unable to obtain a value for the application password. This value is entered at the terminal if tmconfig is being invoked interactively, and is gotten from the APP_PW environment variable if the standard input to the tmconfig process is not a terminal.
|
|
Action
|
If the tmconfig command is being invoked in the background, be sure to set and export the APP_PW environment variable. If tmconfig is being invoked at a terminal, be sure that the user enters a value at the Enter Application Password: prompt.
|
|
See Also
|
tmconfig(1)
|
1308
|
ERROR: Must specify NLSADDR parameters in NETWORK entry machine |
|
|
Description
|
The NLSADDR parameter in the NETWORK section of the configuration file must be specified for every machine in the network, except the master machine. It is recommended but not required for the master machine.
|
|
Action
|
Add NLSADDR information to the configuration file.
|
|
See Also
|
ubbconfig(5), NETWORK section
|
1309
|
WARN: NLSADDR parameter not specified for NETWORK entry machine |
|
|
Description
|
The NLSADDR parameter in the NETWORK section of the configuration file is recommended but not required for the master machine. The master machine needs an NLSADDR and a tlisten process running in order for master migration to work.
|
|
Action
|
Add NLSADDR information for the master machine to the configuration file.
|
|
See Also
|
ubbconfig(5), NETWORK section
|
1316
|
ERROR: Can't find the tpadmin field table in dir |
|
|
Description
|
While executing tmconfig, the program was unable to get the field identifier for TA_SECTION from the field table $TUXDIR/udataobj/tpadmin.
|
|
Action
|
Make sure that the tpadmin field table exists and is readable. Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
tmconfig(1)
|
1317
|
エラー: 管理者にグループIDを設定できません |
|
|
説明
|
ユーザーID 0 (ルート)としてtmbootまたはtmshutdownを実行する場合、プログラムは、グループ識別子をTUXCONFIGファイルで指定されているアプリケーション管理者のグループ識別子に設定します。setgid()が失敗しました。
|
|
アクション
|
UBBCONFIGファイルのRESOURCESまたはMACHINESセクションで設定されているv値が有効であることを確認してください。Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
関連項目
|
tmboot(1)、tmshutdown(1)
|
1318
|
エラー: 管理者にユーザーIDを設定できません |
|
|
説明
|
ユーザーID 0 (ルート)としてtmbootまたはtmshutdownを実行する場合、プログラムは、ユーザー識別子をTUXCONFIGファイルで指定されているアプリケーション管理者のユーザー識別子に設定します。setuid()が失敗しました。
|
|
アクション
|
UBBCONFIGファイルのRESOURCESまたはMACHINESセクションで設定されているUID値が有効であることを確認してください。Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
関連項目
|
tmboot(1)、tmshutdown(1)
|
1319
|
INFO: Terminating tlisten process |
|
|
Description
|
The tlisten process will print this message to the standard error output when terminating. The only valid exit for the tlisten process is when it receives a SIGTERM termination signal.
|
|
Action
|
No action required.
|
|
See Also
|
tlisten(1)
|
1320
|
ERROR: Duplicate -l option specified |
|
|
Description
|
While executing tlisten, the -l option was specified more than once on the command line.
|
|
Action
|
Re-execute the command specifying the -l option only once with the network listening address.
|
|
See Also
|
tlisten(1)
|
1322
|
ERROR: Duplicate -u option specified |
|
|
Description
|
While executing tlisten, the -u option was specified more than once on the command line.
|
|
Action
|
Re-execute the command specifying the -u option only once with the user identifier or name for the configuration administrator.
|
|
See Also
|
tlisten(1)
|
1326
|
エラー: メモリーの割当てに失敗しました |
|
|
説明
|
malloc()を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、tmbootまたはtmshutdownで起動またはシャットダウンするプロセスのリストの保存中に失敗しました。
|
|
アクション
|
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。
|
|
|
|
1327
|
エラー: メモリーの割当てに失敗しました |
|
|
説明
|
malloc()を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、tmbootで起動するサーバーのリストの生成中に失敗しました。
|
|
アクション
|
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。
|
|
|
|
1328
|
エラー: メモリーの割当てに失敗しました |
|
|
説明
|
malloc()を使用してオペレーティング・システムから動的にメモリーを割り当てようとしましたが、tmshutdownでシャットダウンするサーバーのリストの生成中に失敗しました。
|
|
アクション
|
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。
|
|
|
|
1329
|
エラー: アプリケーション・パスワードにエラーがあります |
|
|
説明
|
UBBCONFIGファイルでSECURITYオプションが定義されている場合、tmloadcfはユーザーからパスワードを取得しようとします。標準入力が端末に接続されている場合、tmloadcfは対話形式でパスワードの入力を求めます。それ以外の場合は、APP_PW環境変数を調べます。
このエラーは、tmloadcfがプロンプト用のttyデバイスをオープンできない場合、またはAPP_PWが設定されていない場合に発生します。
|
|
アクション
|
スクリプトからtmloadcfを実行する場合は、tmloadcfが設定され、環境にエクスポートされていることを確認してください。それ以外の場合は、Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
関連項目
|
tmloadcf(1)、ubbconfig(5)
|
1335
|
ERROR: UID is not effective user ID |
|
|
Description
|
While tmloadcf is being run on the master machine, the UID parameter in the RESOURCES or MACHINES section of the UBBCONFIG does not match the effective user identifier of the person running the command.
|
|
Action
|
Change the UID parameter in the RESOURCES or MACHINES section of the UBBCONFIG file or run the command under that user identifier.
|
|
See Also
|
tmloadcf (1)
|
1336
|
ERROR: GID is not effective group ID |
|
|
Description
|
While tmloadcf is being run on the master machine, the GID parameter in the RESOURCES or MACHINES section of the UBBCONFIG does not match the effective group identifier of the person running the command.
|
|
Action
|
Change the GID parameter in the RESOURCES or MACHINES section of the UBBCONFIG file or run the command under that group identifier.
|
|
See Also
|
tmloadcf (1)
|
1341
|
ERROR: MAXACCESSERS parameter must be > 0 and < 32768 |
|
|
Description
|
The MAXACCESSERS parameter in the MACHINES section of the UBBCONFIG file must be greater than 0 and less than 32768.
|
|
Action
|
Correct the value for MAXACCESSERS as specified in the MACHINES section of the UBBCONFIG file to be greater than 0 and less than 32768.
|
|
See Also
|
tmloadcf (1), ubbconfig(5)
|
1343
|
ERROR: MAXGTT parameter must be >= 0 and < 32768 |
|
|
Description
|
The MAXGTT parameter in the MACHINES section of the UBBCONFIG file must be greater than or equal to 0 and less than 32768.
|
|
Action
|
Correct the value for MAXGTT as specified in the MACHINES section of the UBBCONFIG file to be greater than or equal to 0 and less than 32768.
|
|
See Also
|
tmloadcf (1), ubbconfig(5)
|
1344
|
ERROR: MAXCONV parameter must be > 0 and < 32768 |
|
|
Description
|
The MAXCONV parameter in the MACHINES section of the UBBCONFIG file must be greater than zero and less than 32768.
|
|
Action
|
Correct the value for MAXCONV as specified in the MACHINES section of the UBBCONFIG file to be greater than 0 and less than 32768.
|
|
See Also
|
tmloadcf (1), ubbconfig(5)
|
1351
|
ERROR: PERM parameter must be >= 1 and <= 0777 |
|
|
Description
|
The PERM parameter in the MACHINES section of the UBBCONFIG file must be greater than or equal to 1 and less than or equal to 0777.
|
|
Action
|
Correct the value for PERM as specified in the MACHINES section of the UBBCONFIG file to be greater than or equal to 1 and less than or equal to 0777.
|
|
See Also
|
tmloadcf (1), ubbconfig(5)
|
1352
|
ERROR: GROUP entry groupname has TMS specified and LMID lmid does not have TLOGDEVICE |
|
|
Description
|
A TMSNAME parameter is specified for group, groupname, but the primary LMID for the group, lmid, does not have a TLOGDEVICE specified in the MACHINES section.
|
|
Action
|
Either change the GROUPS entry to not have a TMSNAME parameter, or change the LMID value for the group, or change the MACHINES entry to have a TLOGDEVICE parameter.
|
|
See Also
|
tmloadcf (1), ubbconfig(5)
|
1356
|
ERROR: tpalloc() failed - tperrno_msg |
|
|
Description
|
An attempt dynamically to allocate a typed buffer using tpalloc() failed while the DBBL was broadcasting a message to a BBL running the prior release of the software. The message indicates the reason that tpalloc() failed.
|
|
Action
|
Most likely, the call was unable dynamically to allocate memory. Ensure that the 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. Contact your Oracle TUXEDO system Technical Support.
|
|
|
|
1358
|
エラー: サーバー情報を参照できません |
|
|
説明
|
-Rオプションを使用してtmshutdownを実行する際に、プログラムがサーバーのキュー情報を取得できませんでした。サーバーはシャットダウンされ、代替マシンに移行されません。
|
|
アクション
|
Oracle Tuxedoシステムのテクニカル・サポートに連絡してください。
|
|
関連項目
|
tmshutdown(1)
|
1359
|
ERROR: Server ID id in group groupname not marked as restartable. This server will not be restarted upon migration. |
|
|
Description
|
While executing tmshutdown with the -R option, the program determined that the server is not configured to be restartable. The server will be shut down and not migrated to the alternate machine.
|
|
Action
|
If you want to be able to migrate the server between the primary and backup machines, the GROUPS entry with which the server is associated must have a primary and backup LMID specified.
|
|
See Also
|
tmshutdown(1), ubbconfig(5)
|
1360
|
ERROR: configuration file not found |
|
|
Description
|
While executing tmboot or tmshutdown, the program was unable to get the Bulletin Board parameters from the TUXCONFIG configuration file.
|
|
Action
|
Check that the TUXCONFIG environment variable is set and exported. Check the userlog for prior messages that indicate the nature of the failure.
|
|
See Also
|
tmboot(1), tmshutdown(1)
|
1371
|
INFO: Connection received from machine |
|
|
Description
|
The BRIDGE process has received a connection from another machine, machine.
|
|
Action
|
No action required.
|
|
|
|
1372
|
INFO: Orderly disconnect from machine |
|
|
Description
|
The BRIDGE process has completed an orderly disconnect sequence with a remote BRIDGE. Orderly disconnections usually result from execution of the tmshutdown utility.
|
|
Action
|
No action required.
|
|
See Also
|
tmshutdown(1) and Messages 1370 and 1371 above.
|
1373
|
ERROR: Abnormal disconnect from machine |
|
|
Description
|
The BRIDGE process has experienced an abnormal disconnect from a remote BRIDGE. There may be networking problems, or the remote machine may have crashed.
|
|
Action
|
- Check that machine is up.
- Check network connectivity between the machines.
- Check that the Oracle TUXEDO system is running on machine.
- The
BRIDGE processes will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval.
- If desired, use
tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
|
|
See Also
|
tmadmin(1)'s reconnect command. Also check Messages 1370, 1371, 1374, 1375, and 1376 in this chapter.
|
1374
|
WARN: Reconnecting to machine |
|
|
Description
|
The BRIDGE process successfully reconnected to the BRIDGE on machine during recovery from a networking problem.
|
|
Action
|
No action required.
|
|
See Also
|
Message 1373 above
|
1375
|
ERROR: Unable to reconnect to machine |
|
|
Description
|
The BRIDGE process could not reconnect to machine during recovery from a networking problem.
|
|
Action
|
- Check that machine is up.
- Check network connectivity between the machines.
- Check that the Oracle TUXEDO system is running on machine.
- The
BRIDGE processes will automatically reestablish a connection between the machines on demand, when possible. To prevent thrashing, the link will be suspended for five minutes if an automatic reconnect attempt fails. No further automatic reconnection attempts are made during this interval.
- If desired, use
tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
|
|
See Also
|
Messages 1373 and 1374 above and tmadmin(1)'s reconnect command
|
1376
|
WARN: Suspending communication with machine |
|
|
Description
|
The BRIDGE process has suspended automatic reconnection attempts to machine for five minutes. This is to prevent thrashing caused by too many recovery attempts.
|
|
Action
|
Use tmadmin(1)'s reconnect command to initiate a reconnection attempt manually. Manual attempts are allowed during the five-minute suspension interval.
|
|
See Also
|
Messages 1373, 1374, and 1375 above and tmadmin(1)'s reconnect command.
|
1380
|
ERROR: Message queue blocking prevented delivery, Qaddr = qaddress |
|
|
Description
|
The BRIDGE process could not deliver a message it received from the network due to UNIX message queue blocking.
The process(es) associated with the full queue may be identified by looking up qaddress in output of tmadmin 's printserver command (verbose mode).
Another method of examining message queue status is the ipcs -aq command.
|
|
Action
|
- Check the machine's kernel parameters related to message queuing:
MSGMNB, MSGSEG, MSGSSZ, and MSGMAX.
- Boot more servers on the machine.
- Reduce the number of servers per multi-server single-queue (MSSQ) set.
- Check for performance problems causing overload on the machine.
- Update load factors so less work is sent to this machine.
|
|
See Also
|
Oracle TUXEDO Installation Guide, Oracle TUXEDO Administrator's Guide, ipcs(1) in UNIX system reference manuals, tmadmin(1)'s printqueue and printserver commands
|
1383
|
WARN: O_IMOK message could not be sent to DBBL, tperrno= tperrno_val |
|
|
Description
|
The BBL process experienced a memory allocation failure when attempting to send a message to the DBBL indicating that it is alive and OK. If this happens frequently, the BBL may become partitioned.
|
|
Action
|
Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
Message 1394 below
|
1384
|
WARN: O_IMOK message could not be sent to DBBL, tperrno= tperrno_val |
|
|
Description
|
The BBL process experienced a failure when attempting to send a message to the DBBL indicating that it is alive and OK. If this happens frequently, the BBL may become partitioned.
This message is often printed during migration of the DBBL.
|
|
Action
|
If you just migrated the DBBL from master to backup, this message can be ignored. If it continues, it may be necessary to shutdown and reboot the affected machine.
|
|
See Also
|
Message 1394 below
|
1385
|
INFO: BBL now unpartitioned, machine= machine |
|
|
Description
|
The BBL process on machine was partitioned, and now has rejoined the system. This information will be broadcast to all BBL processes, so that services provided by machine will be available again.
|
|
Action
|
No action required.
|
|
See Also
|
Message 1394 below
|
1386
|
ERROR: BBL broadcast send failure, machine= machine tperrno = tperrno_val opcode = 0xnumber |
|
|
Description
|
A broadcast message from the DBBL to all unpartitioned BBLs could not be sent. Machines that are not sent the broadcast message will be marked as partitioned.
|
|
Action
|
- Check for message queue blocking on the master machine. Perhaps the kernel parameters are set too low.
- Check for heavy CPU load on the master machine that might have prevented the
DBBL from completing its broadcast within DBBLWAIT * SCANUNIT seconds.
- Increase the
DBBLWAIT parameter in the RESOURCES section.
- If the problem is transient,
BBLs marked as partitioned should automatically recover.
|
|
See Also
|
Message 1394 below
|
1387
|
ERROR: BBL broadcast send timeout, machine= machine opcode = 0xnumber |
|
|
Description
|
Broadcast message(s) from the DBBL to all unpartitioned BBL s could not be sent because of a timeout. Machines that are not sent the broadcast message will be marked as partitioned.
|
|
Action
|
- Check for message queue blocking on the master machine. Perhaps the kernel parameters are set too low.
- Check for heavy CPU load on the master machine that might have prevented the
DBBL from completing its broadcast within DBBLWAIT * SCANUNIT seconds.
- Increase the
DBBLWAIT parameter in the RESOURCES section.
- If the problem is transient,
BBLs marked as partitioned should automatically recover.
|
|
See Also
|
Message 1394 below
|
1388
|
ERROR: Cannot get BBL broadcast reply buffer, opcode= 0xnumber |
|
|
Description
|
The DBBL could not allocate a buffer for broadcast message replies. All BBLs will be marked as partitioned, since the DBBL does not know the results of the broadcast.
|
|
Action
|
Contact your Oracle TUXEDO system Technical Support.
|
|
|
|
1389
|
ERROR: Cannot get BBL broadcast replies, tperrno= tperrno_val opcode= 0xnumber |
|
|
Description
|
The DBBL encountered an error while trying to receive replies for a broadcast message. All BBLs that have not yet replied will be marked as partitioned.
|
|
Action
|
- If this is a transient error, the partitioned
BBLs will automatically recover.
- Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
Message 1394 below
|
1390
|
ERROR: BBL broadcast service failure, machine= machine opcode= 0xnumber |
|
|
Description
|
The BBL on machine had a service failure for a broadcast request. It will be marked as partitioned.
|
|
Action
|
- The
BBL should automatically recover and become unpartitioned.
- Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
Message 1394 below
|
1391
|
ERROR: BBL broadcast RPC failure, machine=machine, opcode=0xnumber |
|
|
Description
|
The BBL was unable to process a request from the DBBL. A message will be sent back to the DBBL indicating a problem and requesting a new download of the Bulletin Board.
|
|
Action
|
If the download of the Bulletin Board is successful, no action is required. Otherwise, subsequent userlog messages will indicate further failures or actions to be taken.
|
|
|
|
1392
|
ERROR: BBL broadcast reply timeout, machine= machine opcode= 0xnumber |
|
|
Description
|
The BBL on machine did not respond to a broadcast message sent by the DBBL within DBBLWAIT * SCANUNIT seconds. As a result, its bulletin board may be out of date, and will be reloaded from the DBBL's copy.
|
|
Action
|
- Check for network failure or slowness.
- Check that machine is still up.
- Increase the
DBBLWAIT parameter.
- Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
ubbconfig(5), RESOURCES section
|
1393
|
ERROR: BBL upload request not sent, machine= machine tperrno= tperrno_val |
|
|
Description
|
An upload request for a new bulletin board could not be sent to the BBL on machine. This BBL will be marked as partitioned.
|
|
Action
|
Contact your Oracle TUXEDO system Technical Support.
|
|
See Also
|
Message 1394 below
|
1394
|
ERROR: BBL partitioned, machine= machine |
|
|
Description
|
The DBBL has determined that the BBL on machine has become partitioned from the master machine, and perhaps from other machines as well. Two likely causes are networking problems or failure of machine. The DBBL will notify all machines it can reach that machine is partitioned. This will prevent additional service requests from being sent to machine.
|
|
Action
|
- Verify that machine is still up.
- Verify that the Oracle TUXEDO system is still running on machine.
- Verify that machine has network connectivity to the master machine.
- After checking the above, use
tmadmin(1)'s pclean command to remove information about machine's servers from non-partitioned bulletin boards. Then run tmboot(1) to restart servers on machine.
|
|
See Also
|
tmadmin(1), tmboot(1), Message 1385 above
|
1395
|
WARN: Slow BBL response, machine= machine |
|
|
Description
|
The BBL on machine sends an I'm OK message to the DBBL every time it performs a sanity check of its machine. This check occurs every SANITYSCAN * SCANUNIT seconds, as specified in the RESOURCES section.
Similarly, every BBLQUERY * SCANUNIT seconds, the DBBL performs a sanity check of all BBLs. If an I'm OK message has not been received from machine during the previous BBLQUERY * SCANUNIT seconds, the DBBL prints this warning message. Then an explicit sanity check is done over the network. If this check also fails, machine will be considered partitioned.
|
|
Action
|
This message indicates that there may be network congestion or an overload on machine. There is a risk that machine will become partitioned.
- Check for networking problems between the two machines, or any cause of slow network response.
- Check for a CPU overload on machine that prevents the
BBL process from running.
- Check for a CPU overload on the master machine that prevents the
DBBL from processing messages in its queue.
- Adjust the
BBLQUERY parameter so that it is larger than the SANITYSCAN parameter. A difference of ten seconds or more should prevent spurious warnings under most circumstances.
|
|
See Also
|
Message 1394 above, ubbconfig(5), RESOURCES section
|
1398
|
エラー: TUXDIR環境変数が設定されていません |
|
|
説明
|
TUXDIR環境変数が設定されていませんでした。そのため、buildclientコマンドは失敗します。
|
|
アクション
|
TUXDIR環境変数をOracle Tuxedoシステム・ソフトウェアのベース・ディレクトリに設定し、この変数をエクスポートしてください。
|
|
関連項目
|
buildclient(1)
|
1399
|
ERROR: ACUCOBOL environment variable not set |
|
|
Description
|
The ACUCOBOL environment variable was not set. Because of this, the buildclient or buildserver command will fail.
|
|
Action
|
Set the ACUCOBOL environment variable to the base directory of the ACUCOBOL-GT system software, and export this variable.
|
|
See Also
|
buildserver(1), buildclient(1)
|
