システム・メッセージ: CMDTUXカタログ4700-4799
|
4700 |
ERROR: service-name received a badly formed message | |
|
Description |
The event broker service service-name received a message that does not contain the necessary information. |
Action |
Contact Oracle Customer Support. | |
See Also |
| |
4701 |
エラー: ユーザー・データをデコードまたは復号化できません | |
|
説明 |
|
アクション |
イベント・ブローカは、復号化鍵をオープンするために | |
関連項目 |
| |
4702 |
警告: プライマリ・イベント・サーバーがMIBデータを取得できませんでした | |
|
説明 |
MIBリクエストがプライマリ・イベント・サーバーに転送されました。このリクエストは暗号化されていますが、サーバーにメッセージを復号化するための適切な復号化鍵がありません。もしくは、メッセージのデコード中に問題が発生しました。 |
アクション |
イベント・ブローカは、復号化鍵をオープンするために | |
関連項目 |
| |
4711 |
ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_NAME field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4713 |
ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_NAME field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4715 |
ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_NAME field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4717 |
ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length | |
|
Description |
The SEC_PRINCIPAL_NAME field in the |
Action |
Ensure that the field is less than size characters. | |
See Also |
| |
4718 |
エラー: メッセージの形式が無効です | |
|
説明 |
BBLがメッセージを受信しましたが、必要な情報が含まれていません。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
4719 |
エラー: メッセージの形式が無効です | |
|
説明 |
BBLがメッセージを受信しましたが、必要な情報が含まれていません。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
4720 |
エラー: メッセージの形式が無効です | |
|
説明 |
BBLがメッセージを受信しましたが、必要な情報が含まれていません。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
4721 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
|
アクション |
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。 マシンのメモリー使用量を減らすか、マシンの物理メモリーまたはスワップ領域、あるいはその両方の量を増やしてください。 | |
4722 |
エラー: メモリーの割当てに失敗しました | |
|
説明 |
|
アクション |
マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。 マシンのメモリー使用量を減らすか、マシンの物理メモリーまたはスワップ領域、あるいはその両方の量を増やしてください。 | |
4723 |
ERROR: buildserver cannot open the temporary output file, srcfile. | |
|
Description |
The |
Action |
Check that the directory for the file exists and has write permissions, and the file system has sufficient resources for a new file. | |
See Also |
| |
4724 |
エラー: バックグラウンド・プロセスにすることはできませんでした | |
|
説明 |
通常、 |
アクション |
イベント・ログの他のメッセージを確認してください。使い果されたOSリソースがないか調べて解決した後、コマンドを再試行してください。 | |
関連項目 |
| |
4725 |
エラー: バックグラウンド・プロセスにすることはできませんでした | |
|
説明 |
通常、 |
アクション |
イベント・ログの他のメッセージを確認してください。使い果されたOSリソースがないか調べて解決した後、コマンドを再試行してください。 | |
関連項目 |
| |
4726 |
エラー: TUXCONFIGファイルのRESOURCESセクションを読み取れません | |
|
説明 |
|
アクション |
詳細は、ユーザー・ログを確認してください。必要であれば、Oracle Tuxedoシステムの管理者に連絡してください。 | |
4727 |
ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before DBBL lockout occurs | |
|
Description |
The system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. DBBL lockout will occur in indicated time. When DBBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4728 |
ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before DBBL lockout occurs | |
|
Description |
The system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. DBBL lockout will occur in indicated time. When DBBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4729 |
WARN: Reached 100% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
The system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4730 |
WARN: .SysLicenseWarn: Reached 100% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
The system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4731 |
INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
The system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4732 |
INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
The system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4733 |
ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout occurs, no new clients can join the application | |
|
Description |
DBBL lockout occurs because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle. |
Action |
Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4734 |
ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout occurs, no new clients can join the application | |
|
Description |
DBBL lockout occurs because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle. |
Action |
Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4735 |
INFO: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4736 |
INFO: .SysLicenseInfo: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4737 |
INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4738 |
INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4739 |
INFO: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4740 |
INFO: .SysLicenseInfo: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled | |
|
Description |
The system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4741 |
エラー: DBBLはすべてのBBLのO_LCKOUTメッセージをフォーマットできませんでした | |
|
説明 |
24時間の猶予期間にアクティブ・ユーザーの合計数がTUXEDO契約ユーザー数の110%を超えたとシステムが判断したため、DBBLのロックアウトが発生します。しかし、DBBLがロックアウトのメッセージを書式設定してすべてのBBLにブロードキャストするには問題があります。 |
アクション |
今後のシステムのロックアウトを回避するため、TUXEDOのライセンスをアップグレードしてユーザー数を増やしてください。Oracle Tuxedoシステムの管理者に連絡してください。 | |
4742 |
エラー: DBBLはすべてのBBLのO_UNLCKOUTメッセージをフォーマットできませんでした | |
|
説明 |
アクティブ・ユーザーの合計数がTUXEDO契約ユーザー数の110%未満に減ったとシステムが判断したため、DBBLのロックアウトが取り消されました。しかし、DBBLがロックアウト解除のメッセージを書式設定してすべてのBBLにブロードキャストするには問題があります。 |
アクション |
今後のシステムのロックアウトを回避するため、TUXEDOのライセンスをアップグレードしてユーザー数を増やしてください。Oracle Tuxedoシステムの管理者に連絡してください。 | |
4743 |
ERROR: Exceeded 110% of TUXEDO System Binary License User Count, BBL received LOCKOUT notice, no new clients can join the application | |
|
Description |
BBL received lockout notice from the DBBL because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle. |
Action |
Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4744 |
情報: BBLはLOCKOUTの取消を通知するメッセージが送信され、アプリケーションに新しいクライアントを参加させることができるようになります | |
|
説明 |
アクティブ・ユーザーの合計数がTUXEDO契約ユーザー数の110%未満に減ったとシステムが判断したため、BBLはDBBLからロックアウト取消しの通知を受信しました。この時点で、新しいクライアントがアプリケーションに参加できます。 |
アクション |
今後のシステムのロックアウトを回避するため、TUXEDOのライセンスをアップグレードしてユーザー数を増やしてください。Oracle Tuxedoシステムの管理者に連絡してください。 | |
4745 |
ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout occurs, no new clients can join the application | |
|
Description |
The BBL lockout occurs in SHM mode because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4746 |
ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout occurs, no new clients can join the application | |
|
Description |
The BBL lockout occurs in SHM mode because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4747 |
ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before BBL lockout occurs | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. The BBL lockout will occur in indicated time. When BBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4748 |
ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before BBL lockout occurs | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. The BBL lockout will occur in indicated time. When BBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4749 |
WARN: Reached 100% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4750 |
WARN: .SysLicenseWarn: Reached 100% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4751 |
INFO: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4752 |
INFO: .SysLicenseInfo: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4753 |
INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4754 |
INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val) | |
|
Description |
In SHM mode, the system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase. |
Action |
Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4755 |
INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4756 |
INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4757 |
INFO: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4758 |
INFO: .SysLicenseInfo: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled | |
|
Description |
In SHM mode, the system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent DBBL scan cycle. |
Action |
Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your Oracle TUXEDO System Administrator. | |
4760 |
ERROR: -t option cannot be used on a platform which does not support threads | |
|
Description |
The |
Action |
Re-run the command without the | |
See Also |
| |
4761 |
ERROR: the -t and -C options are mutually exclusive | |
|
Description |
The |
Action |
Re-run the command without the | |
See Also |
| |
4763 |
ERROR: -z (val) is larger than 56, but only the 56-bit package is installed | |
|
Description |
In |
Action |
Re-run the command with a lower encryption level or install the higher encryption level. | |
See Also |
| |
4764 |
ERROR: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed | |
|
Description |
In the |
Action |
Re-configure the link level encryption with a lower encryption level or install
the higher encryption level.
The encryption level is specified using the | |
See Also |
| |
4765 |
ERROR: MAXENCRYPTBITS parameter must be 0, 40, 56 or 128 | |
|
Description |
The |
Action |
Re-configure the parameter and reload the configuration. | |
See Also |
| |
4766 |
ERROR: Cannot open file filename for writing | |
|
Description |
The event server couldn't open file filename for writing the subscription database. |
Action |
The event server writes a new copy of the subscription database in the
temporary file file.
Then, it links this file to the control file specified
in the | |
4767 |
ERROR: Couldn't initialize the allocated memory as a fielded buffer, Ferror32=error | |
|
Description |
While processing a deletion record, the event server was unable to initialize an FML32 buffer. The Ferror32 error value is printed. |
Action |
Contact Oracle Customer Support. | |
4768 |
ERROR: Cannot write FML32 buffer in file val, Ferror32=error | |
|
Description |
While processing a deletion record, the event server was unable to write out an FML32 buffer. The Ferror32 error value is printed. |
Action |
Check the FML32 error. Most likely it is related to insufficient resources in the file system. Fix the problem and re-run the operation. | |
4769 |
エラー: セカンダリ・サーバーから受信したデータベースのバージョンが無効です | |
|
説明 |
認識されないイベント・データベースのバージョンをリクエストするメッセージが、セカンダリ・イベント・サーバーからプライマリに送信されます。 |
アクション |
Oracleカスタマ・サポートに連絡してください。 | |
4770 |
ERROR: Could not determine size of fielded buffer, Ferror32=error | |
|
Description |
The event server, while trying to expand an FML32 buffer, was unable to determine the buffer size. The Ferror32 error value is printed. |
Action |
Contact Oracle Customer Support. | |
4771 |
ERROR: MINDISPATCHTHREADS must be <= MAXDISPATCHTHREADS | |
|
Description |
|
Action |
Correct the entry and re-load the configuration. | |
See Also |
| |
4772 |
WARN: MAXDISPATCHTHREADS > system max, changing to val | |
|
Description |
|
Action |
No action required. | |
See Also |
| |
4774 |
ERROR: SIGNATURE_AHEAD parameter must be > 0 and < 2147483647. | |
|
Description |
The |
Action |
Specify a value that is between 1 and 2,147,483,646, inclusive. | |
See Also |
| |
4776 |
ERROR: SIGNATURE_BEHIND parameter must be > 0 and < 2147483647. | |
|
Description |
The |
Action |
Specify a value that is between 1 and 2,147,483,646, inclusive. | |
See Also |
| |
4777 |
ERROR: -z(val) must be 0, 40, 56 or 128 | |
|
Description |
The argument for the |
Action |
Re-configure the argument and re-run the command. | |
See Also |
| |
4778 |
ERROR: -Z(val) must be 0, 40, 56 or 128 | |
|
Description |
The argument for the |
Action |
Re-configure the argument and re-run the command. | |
See Also |
| |
4780 |
ERROR: 56-bit package installed. val bits minimum encryption is configured | |
|
Description |
In |
Action |
Re-configure the link level encryption with a lower encryption level for
the remote node or install
the higher encryption level.
The encryption level is specified using the | |
See Also |
| |
4782 |
ERROR: MINENCRYPTBITS parameter must be 0, 40, 56 or 128 | |
|
Description |
The value of |
Action |
Re-configure the parameter and re-load the configuration. | |
See Also |
| |
4784 |
WARN: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed | |
|
Description |
In the |
Action |
Re-configure the link level encryption with a lower encryption level or install
the higher encryption level.
The encryption level is specified using the | |
See Also |
| |
4786 |
ERROR: Couldn't initialize the allocated memory as a fielded buffer, Ferror32=val | |
|
Description |
While processing a database version record, the event server was unable to initialize an FML32 buffer. The Ferror32 error value is printed. |
Action |
Contact Oracle Customer Support. | |
4788 |
ERROR: Cannot write FML32 buffer in file val, Ferror32=val | |
|
Description |
While processing a database version record, the event server was unable to write out an FML32 buffer. The Ferror32 error value is printed. |
Action |
Check the FML32 error. Most likely it is related to insufficient resources in the file system. Fix the problem and re-run the operation. | |
4790 |
エラー: プライマリ・サーバーがサブスクリプション・データベースをファイルに移せません | |
|
説明 |
プライマリ・イベント・サーバーがサブスクリプション・データベースをファイルにアンロードできませんでした。 |
アクション |
問題の性質を明確に示すメッセージがログに前出していないか確認してください。 | |
4792 |
ERROR: Secondary Server can't set database version in the FML buffer. Ferror=val | |
|
Description |
The secondary event server can't add |
Action |
When the secondary event server polls the primary server for subscription database, it sends its version. This message states that the secondary server couldn't insert the version field to FML buffer. Contact Oracle Customer Support, and provide the Ferror errno. | |
See Also |
| |
4794 |
ERROR: Could not realloc fielded buffer, Ferror32=val | |
|
Description |
The event server, while trying to expand an FML32 buffer, was unable to determine the buffer size. The Ferror32 error value is printed. |
Action |
Make sure 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 and/or swap space on the machine. | |
4795 |
WARN: Job Description not found. Using default job attributes | |
|
Description |
The AS/400 Job Description for the BBL could not be found in the Job Description file AS400_JD. The default job attributes will be used. |
Action |
Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the BBL. | |
4796 |
WARN: Failure changing job attributes. Using default attributes | |
|
Description |
The job attributes for the BBL could not be set according to the Job Description in the AS400_JD file. The default job attributes will be used. |
Action |
Check the job log for the BBL to determine the cause of the failure. | |
4797 |
WARN: Job Description not found. Using default job attributes | |
|
Description |
The AS/400 Job Description for the DBBL could not be found in the Job Description file AS400_JD. The default job attributes will be used. |
Action |
Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the DBBL. | |
4798 |
WARN: Failure changing job attributes. Using default attributes | |
|
Description |
The job attributes for the DBBL could not be set according to the Job Description in the AS400_JD file. The default job attributes will be used. |
Action |
Check the job log for the BBL to determine the cause of the failure. | |
4799 |
WARN: Job Description not found. Using default job attributes | |
|
Description |
The AS/400 Job Description for the BRIDGE could not be found in the Job Description file AS400_JD. The default job attributes will be used. |
Action |
Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the BRIDGE. |