 
|  システム・メッセージ: CMDTUXカタログ4000-4099 | 
|   |   | 
| 4002 | ERROR: Syntax Error in the -g argument. | |
| 
 | Description | 
Each group specified by the  | 
| Action | 
Modify the  | |
| 4003 | ERROR: Syntax Error in the  | |
| 
 | Description | 
Each group specified by the  | 
| Action | 
Modify the  | |
| 4004 | ERROR: Could not retrieve group information. | |
| 
 | Description | 
When  | 
| Action | Try the command again. If it fails consistently, contact your Oracle Customer Support. | |
| 4005 | ERROR: Group number does not exist. | |
| 
 | Description | 
 | 
| Action | 
Add the desired group to the  | |
| 4006 | ERROR: Group groupname does not exist. | |
| 
 | Description | 
 | 
| Action | 
Add the desired group to the  | |
| 4008 | ERROR: type field is not valid. | |
| 
 | Description | 
The type field given via the  | 
| Action | 
Change the  | |
| 4010 | ERROR: name field is not valid. | |
| 
 | Description | 
The name given to  | 
| Action | Change the name given to the command in order to comply with the specifications. | |
| 4011 | ERROR: FML32 error error. | |
| 
 | Description | 
When adding or deleting a field from an FML buffer, the given error occurred. This error occurs when running  | 
| Action | Try running the command again. If it fails consistently, contact your Oracle Customer Support. | |
| 4012 | エラー: メモリー割当てエラーです。 | |
| 
 | 説明 | 
コマンド | 
| アクション | コマンドが実行されたシステムのメモリーを確認してください。この操作に対して十分なメモリーがある場合は、Oracleカスタマ・サポートに連絡してください。 | |
| 4014 | ERROR: TUXCONFIG is not set. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4018 | ERROR: Unknown executable name. | |
| 
 | Description | 
The given executable name is not known. This error can happen if the  | 
| Action | 
Do not rename the  | |
| 4019 | ERROR: MIB error number. | |
| 
 | Description | 
When running the  | 
| Action | 
Consult the  | |
| 4020 | ERROR: grpname field is not valid. | |
| 
 | Description | 
The group name given to  | 
| Action | Change the group name given to the command in order to comply with the specifications. | |
| 4021 | ERROR: MIB error number. | |
| 
 | Description | 
When running the  | 
| Action | 
Consult the  | |
| 4022 | ERROR: FML32 error error. | |
| 
 | Description | 
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running  | 
| Action | Try running the command again. If it continues to fail, contact your Oracle Customer Support. | |
| 4023 | エラー: メモリー割当てエラーです。 | |
| 
 | 説明 | 
コマンド | 
| アクション | マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
| 4024 | ERROR: MIB error number. | |
| 
 | Description | 
When running the  | 
| Action | 
Consult the  | |
| 4025 | ERROR: TUXCONFIG is not set. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4026 | ERROR: new group name is not valid. | |
| 
 | Description | 
The new group name given to  | 
| Action | Change the new group name given to the command in order to comply with the specifications. | |
| 4027 | ERROR: Could not retrieve group information. | |
| 
 | Description | 
When  | 
| Action | Try the command again. If the command fails consistently, contact your Oracle Customer Support. | |
| 4028 | ERROR: groupname group already exists. | |
| 
 | Description | 
In the  | 
| Action | Do not attempt to have two groups with the same name. Change the group name and re-run the command. | |
| 4029 | ERROR: Group groupname does not exist. | |
| 
 | Description | 
 | 
| Action | 
Use  | |
| 4030 | ERROR: FML32 error error. | |
| 
 | Description | 
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running  | 
| Action | Try running the command again. If it fails again, contact your Oracle Customer Support. | |
| 4031 | エラー: メモリー割当てエラーです。 | |
| 
 | 説明 | 
コマンド | 
| アクション | マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
| 4032 | ERROR: Could not retrieve group information. | |
| 
 | Description | 
When  | 
| Action | Try the command again. If it fails consistently, contact your Oracle Customer Support. | |
| 4033 | ERROR: Group number does not exist. | |
| 
 | Description | 
 | 
| Action | 
Add the desired group to the  | |
| 4034 | ERROR: Group groupname does not exist. | |
| 
 | Description | 
 | 
| Action | 
Add the desired group to the  | |
| 4038 | ERROR: Unknown executable name. | |
| 
 | Description | 
The given executable name is not known. This error can happen if the  | 
| Action | 
Do not rename the  | |
| 4039 | ERROR: TUXCONFIG is not set. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4040 | ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL. | |
| 
 | Description | 
In order to run  | 
| Action | 
Change the security level in the  | |
| 4043 | ERROR: username user already exists. | |
| 
 | Description | 
In the  | 
| Action | Do not attempt to have two users with the same numeric identification. Change the user name and re-run the command. | |
| 4044 | ERROR: User username does not exist. | |
| 
 | Description | 
 | 
| Action | 
Use  | |
| 4045 | ERROR: usrname field is not valid. | |
| 
 | Description | 
The user name given to  | 
| Action | Change the name given to the command in order to comply with the specifications. | |
| 4046 | ERROR: Invalid group specified. | |
| 
 | Description | 
The group name given to  | 
| Action | 
Use  | |
| 4047 | ERROR: User numbers must be between 1 and max | |
| 
 | Description | 
User numbers in the  | 
| Action | Change the user number to be within the allowable range and re-run the command. | |
| 4048 | ERROR: MIB error number. | |
| 
 | Description | 
When running the  | 
| Action | 
Consult the  | |
| 4049 | ERROR: A group with id number already exists. | |
| 
 | Description | 
In the  | 
| Action | Do not attempt to have two groups with the same numeric identification. Change the identification number and re-run the command. | |
| 4050 | ERROR: A user with id number already exists. | |
| 
 | Description | 
In the  | 
| Action | Do not attempt to have two users with the same numeric identification. Change the identification number and re-run the command. | |
| 4053 | ERROR: User username not added. | |
| 
 | Description | 
Due to an error processing the user password, this user has not been added to the system. This can happen when using  | 
| Action | Re-run the command that caused the error. If this error occurs consistently, call Oracle Customer Support. | |
| 4054 | ERROR: Passwords do not match. | |
| 
 | Description | 
The user passwords entered to  | 
| Action | Re-run the command and make sure that you enter the passwords correctly each time you are prompted. | |
| 4055 | ERROR: Unable to get host user id. | |
| 
 | Description | 
 | 
| Action | Make sure that the user id of the Oracle TUXEDO administrator is known to the system. If the user id is known to the system, contact your Oracle Customer Support. | |
| 4056 | ERROR: Unable to get host user id. | |
| 
 | Description | 
 | 
| Action | Make sure that the user id of the Oracle TUXEDO administrator is known to the system. If the user id is known to the system, contact your Oracle Customer Support. | |
| 4057 | ERROR: Unable to get host user id. | |
| 
 | Description | 
 | 
| Action | Make sure that the user id of the Oracle TUXEDO administrator is known to the system. If the user id is known to the system, contact your Oracle Customer Support. | |
| 4058 | INFO: .SysMachineState: val state change to ACTIVE | |
| 
 | Description | This message states that the specified machine changed to ACTIVE. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4059 | ERROR: SRVID parameter must be >= 1 and <= 30000 | |
| 
 | Description | 
The  | 
| Action | Specify a value that is between 1 and 30,000, inclusive. | |
| See Also | 
 | |
| 4060 | ERROR: Unknown executable name. | |
| 
 | Description | 
The given executable name is not known. This error can happen if the  | 
| Action | 
Do not rename the  | |
| 4062 | ERROR: MIB error number. | |
| 
 | Description | 
When running the  | 
| Action | 
Consult the  | |
| 4063 | INFO: .SysNetworkState: LMID1->LMID2 state change to INACTIVE | |
| 
 | Description | This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4064 | INFO: .SysMachineState: LMID state change to PARTITIONED | |
| 
 | Description | This message states that the specified machine changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4065 | INFO: .SysNetworkState: LMID1->LMID2 state change to ACTIVE | |
| 
 | Description | This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a new state as mentioned in the message. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4066 | INFO: .SysNetworkState: LMID1->LMID2 state change to SUSPENDED | |
| 
 | Description | This message indicates that the virtual circuit between machines LMID1 and LMID2 changed to a SUSPENDED state. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4068 | INFO: .SysServerState: servername, group srvgrp, id srvid state change to state | |
| 
 | Description | This message indicates that the server specified above changed to a new state. A complete listing of the server attributes are sent in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4069 | INFO: .SysClientState: User usrname on LMID state change to state | |
| 
 | Description | This message indicates that the client specified above changed to a new state. A complete listing of the current attributes of the client are sent in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4070 | ERROR: Application must be configured. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4071 | ERROR: Application must be configured. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4072 | ERROR: Application must be configured. | |
| 
 | Description | 
 | 
| Action | 
Configure the application (see  | |
| 4073 | INFO: .SysNetworkConfig: LMID1->LMID2 configuration change | |
| 
 | Description | This message indicates that the network link between the two machines specified changed to a new state. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4075 | INFO: .SysMachineState: LMID state change to INACTIVE | |
| 
 | Description | This message states that the specified machine changed to an INACTIVE state. A complete listing of the current parameters are sent along in the posted buffer. | 
| Action | This is an informational message. | |
| See Also | 
 | |
| 4076 | ERROR: .SysEventDelivery: System Event Monitor delivery failure on LMID | |
| 
 | Description | This message indicates that the event server failed to perform at least one notification for a posted event. | 
| Action | Check to make sure that the notifications specified in the subscriptions that match the posted events can be done. | |
| See Also | 
 | |
| 4077 | ERROR: .SysEventFailure: System Event Monitor subsystem failure on LMID | |
| 
 | Description | The system event server periodically sends a message to itself to detect blocking conditions on the message queues. This event is generated if the server can't put a message on the queue in no-block node. It can also be generated if the received message doesn't match what was sent out earlier. The second case will probably never happen. | 
| Action | Configure larger message queues or distribute the load in the application equally among all the machines. | |
| See Also | 
 | |
| 4078 | エラー: メモリーの割当てに失敗しました | |
| 
 | 説明 | イベント・サーバーでメモリーの割当てに失敗しました。 | 
| アクション | マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
| 4080 | エラー: 受信したメッセージが送信したメッセージと一致しません | |
| 
 | 説明 | 
イベント・サーバーは、 | 
| アクション | Oracleカスタマ・サポートに連絡してください。 | |
| 関連項目 | 
 | |
| 4081 | ERROR: FML32 error error. | |
| 
 | Description | 
When adding or deleting a field from an FML32 buffer, the given error occurred. This error occurs when running  | 
| Action | Try running the command again. If it fails consistently, contact your Oracle Customer Support. | |
| 4082 | エラー: メモリー割当てエラーです。 | |
| 
 | 説明 | 
コマンド | 
| アクション | マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。 | |
| 4083 | INFO: Line number not added because it is a comment. | |
| 
 | Description | 
The given line number in the user file was ignored by  | 
| Action | Be sure that the file which is being converting has the correct format. | |
| 4084 | INFO: User ID field field is not numeric. Line number not added. | |
| 
 | Description | 
If  | 
| Action | Be sure that the file which is being converted has the correct format. | |
| 4085 | INFO: User ID number is invalid. Line number not added. | |
| 
 | Description | 
User identification numbers are only valid within the range 1 to 131,071. If  | 
| Action | 
Any users which  | |
| 4086 | INFO: Group ID field number is not numeric. Line number not added. | |
| 
 | Description | 
If  | 
| Action | 
Any users which  | |
| 4087 | INFO: Line number not added. # is an illegal character. | |
| 
 | Description | 
The given line in the user file was not converted by  | 
| Action | 
Any users which  | |
| 4088 | INFO: Line number not added. error_string. | |
| 
 | Description | 
 | 
| Action | Examine the error code returned. This error can be used to determine the actual Oracle TUXEDO system error that occurred. | |
| 4089 | INFO: Line number user name not added. Error retrieving number of occurrences. | |
| 
 | Description | 
When  | 
| Action | 
Any users which  | |
| 4090 | INFO: Line number user username not added. User username already exists. | |
| 
 | Description | 
When  | 
| Action | 
You can add any user which  | |
| 4091 | INFO: Line number not added. error_string. | |
| 
 | Description | 
 | 
| Action | Examine the error code returned. This error can be used to determine the actual Oracle TUXEDO system error that occurred. | |
| 4092 | INFO: Line number user name not added. Error retrieving number of occurrences. | |
| 
 | Description | 
When  | 
| Action | 
Any users which  | |
| 4093 | INFO: Line number user usernumber not added. User usernumber already exists. | |
| 
 | Description | 
 | 
| Action | 
Any users which  | |
| 4094 | INFO: Line number user username not added. Error writing file. | |
| 
 | Description | 
 | 
| Action | Run a diagnostic on the disk to see whether the disk is corrupted. If it is corrupted, buy a new disk and run the command again. If it is not, contact Oracle Customer Support. | |
| 4095 | INFO: Line number not added because it is a comment. | |
| 
 | Description | 
The given line number in the group file was ignored by  | 
| Action | Be sure that the file which is being converted has the correct format. | |
| 4096 | INFO: Group ID field string is not numeric. Line number not added. | |
| 
 | Description | 
If  | 
| Action | 
Any groups which  | |
| 4097 | INFO: Line number not added. error_string. | |
| 
 | Description | 
 | 
| Action | Examine the error code returned. This error can be used to determine the actual Oracle TUXEDO system error that occurred. | |
| 4098 | INFO: Line number Group groupname not added. Error retrieving error. | |
| 
 | Description | 
 | 
| Action | If this error occurs consistently, contact Oracle Customer Support. | |
| 4099 | INFO: Line number Group groupname:error_string | |
| 
 | Description | 
 | 
| Action | Use the error_string returned from the MIB to determine exactly what error occurred. | |
|  |  |  |