Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
5300 |
ERROR: [caller] failed to malloc space for purpose - request discarded | |
|
Description |
An attempt to dynamically allocate memory from the operating system using |
Action |
Make sure the operating system parameters are set correctly for the amount of me mory on the machine and the amount of memory that can be used by a process. Redu ce the memory usage on the machine or increase the amount of physical memory on the machine. | |
5301 |
ERROR: Cannot send service state change to GWADM due to error (val) | |
|
Description |
The Domains Gateway library software detected this condition while trying to notify the Domains Gateway administration server, |
Action |
Take note of the specific error reported in the message. It may be necessary to increase the IPC queue size or the number of messages limit for this operating system, in order to accomodate the service state change notifications. | |
See Also |
| |
5302 |
WARN: unable to propagate the message priority, GLOBAL or LOCAL_ABSOLUTE | |
|
Description |
The message priority could not be set to GLOBAL or LOCAL_ABSOLUTE. |
Action |
Check the log for related messages. If the problem persists contact contact your BEA Customer Support | |
5303 |
WARN: unable to set the message priority locally, LOCAL_RELATIVE | |
|
Description |
The message priority could not be set to LOCAL_RELATIVE. |
Action |
Check the log for related messages. If the problem persists contact contact your BEA Customer Support | |
5304 |
ERROR: _dmcf_OLD_open failed: Can't open DM_TDOMAIN section | |
|
Description |
When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_TDOMAIN section. |
Action |
Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application. | |
5305 |
ERROR: _dmcf_OLD_open failed: Can't open DM_OSITPX section | |
|
Description |
When the GWADM server is booted, it requests the configuration for its domain from the DMADM server. The DMADM server then retrieves all the entries from the BDMCONFIG file that are pertinent to this domain. This message indicates that DMADM cannot open the BDMCONFIG file for reading the DM_OSITP section. |
Action |
Make sure that the BDMCONFIG file still exists and is accessible by the DMADM server, and re-start the application. | |
5306 |
INFO: Unable to send msg-type message - queue block condition, dropping message! | |
|
Description |
When GWTDOMAIN attempted to forward an incoming request/reply to a local server/client process, GWTDOMAIN encountered a full request/reply message queue. |
Action |
Monitor IPC message queues to identify server/client that is unable to keep up with the GWTDOMAIN's throughput. | |
5307 |
WARN: Secondary/Backup RDOM rdom in ON_DEMAND mode, removed from service service-name! | |
|
Description |
The GWTDOMAIN configuration of the connection policy for the remote TDomain is ON_DEMAND. When remote TDomain has connection policy set as ON_DEMAND it is not allowed to be the secondary or backup role for an imported service. |
Action |
Correct the configuration of the remote TDomain to have connection policy set to either ON_STARTUP or INCOMING_ONLY if the failover behavior is required. Otherwise remove the remote domain from the list supporting the imported service. | |
5308 |
ERROR: Cannot initialize synchronization structure for Timer Object! | |
|
Description |
The gateway failed to initialize the mutex and conditional variable that are required internally for accessing shared resources. |
Action |
Check the OS configuration, and make sure it supports thread. | |
5309 |
ERROR: Cannot initialize synchronization structure for Timer Object! | |
|
Description |
The gateway failed to initialize the mutex and conditional variable that are required internally for accessing shared resources. |
Action |
Check the OS configuration, and make sure it supports thread. | |
5310 |
ERROR: Failed to create timer object thread | |
|
Description |
The gateway failed to create a thread to handle timer object request. |
Action |
Check the OS configuration, make sure it not only support thread but also allows enough threads per process. | |
5311 |
ERROR: Internal Timer Object Manager already created! | |
|
Description |
Gateway initialization error and cause it to create timer object manager more than once. |
Action |
Internal error. Contact your BEA Customer Support. | |
5312 |
ERROR: Timer Object Memory allocation failure! | |
|
Description |
Memory allocation failure while creating timer object. |
Action |
Check you DMCONFIG configuration file, and the computer system configuration. Reduce number of remote domains that requires DMKEEPALIVE, or increase system memory. If problem persists, contact your BEA Customer Support. | |
5313 |
WARN: multiple RDOMs not allowed on REMOTE_SERVICES in ON_DEMAND mode | |
|
Description |
Multiple RDOMs for the REMOTE_SERVICES is for domain failover. Only when connection policy is either ON_STARTUP, or INCOMING_ONLY will the failover be allowed. The failover is not supported in ON_DEMAND mode. |
Action |
Correct the domain configuation. | |
5314 |
WARN: Only the first RDOM for service service-name will be used | |
|
Description |
The ON_DEMAND connection policy does not support failover. |
Action |
Remove the extra RDOMs from the RDOM list or change the connection policy to either ON_STARTUP or INCOMING_ONLY. | |
5315 |
ERROR: Internal Error, rdomp is | |
|
Description |
Gateway internal error, input parameter |
Action |
Contact your BEA customer support. | |
5316 |
WARN: Missing remote domain <rdom> gateway network configuration. | |
|
Description |
The remote domain rdom gateway network configuration information is missing from the |
Action |
Shutdown all the gateway groups of the | |
See Also |
| |
5317 |
WARN: Remote resource rsvc is removed, missing primary remote domain <rdom> network configuration | |
|
Description |
The remote resource rsvc will be removed from the gateway configuration information because the network configuration information of the primary remote domain rdom is missing. |
Action |
Shutdown the affected gateway groups, correct the error in the DMCONFIG configuration file, and reboot the those gateway groups. | |
See Also |
| |
5318 |
WARN: Remote resource rsvc is removed, missing secondary/backup remote domain <rdom> network configuration | |
|
Description |
The remote resource rsvc will be removed from the gateway configuration information because the network configuration information of the secondary or backup remote domain rdom is missing. |
Action |
Shutdown the affected gateway groups, correct the error in the DMCONFIG configuration file, and reboot the those gateway groups. | |
See Also |
| |
5319 |
ERROR: Incorrect input time format, the format has to be yyyy/mm/dd/hh:mm:ss. | |
|
Description |
The password start time and expiration time use this specific format; however, the user input did not follow this format. |
Action |
Correct the time format. | |
See Also |
| |
5320 |
ERROR: Incorrect input time value. | |
|
Description |
The input value for time and date is out of legal range. |
Action |
Correct the problem and redo the operation. | |
See Also |
| |
5321 |
ERROR: Failed to convert user input to time string, check the input value<val>. | |
|
Description |
Failed to convert input user input time string. |
Action |
Correct the problem. | |
See Also |
| |
5322 |
ERROR: Date exceed [GMT] 2038/1/19/03:14:07. | |
|
Description |
The time exceeded the limit, or after daylight saving time adjustment it no longer valid. |
Action |
Contact your BEA Tuxedo Customer Support. | |
See Also |
| |
5323 |
ERROR: _dmcf_OLD_open failed: Can't open DM_PASSWORDS section. | |
|
Description |
Failed to open the DM_PASSWORD section in the BDMCONFIG file. |
Action |
Shutdown all the gateway groups, use the original version of | |
See Also |
| |
5324 |
ERROR: Failed to convert LPWD from 3DES to DES. | |
|
Description |
Failed to convert encrypted local password in a password pair from Triple-DES encryption to DES encryption before send it to GWADM. The conversion occurred because the password pair is stored in a more secured Triple-DES format in BDMCONFIG, but the target GWADM is of an older version that does not support Triple-DES. |
Action |
Contact your BEA Tuxedo Customer Support. | |
See Also |
| |
5325 |
ERROR: Failed to convert RPWD from 3DES to DES. | |
|
Description |
Failed to convert encrypted remote password in a password pair from Triple-DES encryption to DES encryption before send it to GWADM. The conversion occurred because the password pair is stored in a more secured Triple-DES format in BDMCONFIG, but the target GWADM is in an older binary that does not support Triple-DES. |
Action |
Contact your BEA Tuxedo Customer Support. | |
See Also |
| |
5326 |
ERROR: Can't add PASSWORD entry (ent) into table | |
|
Description |
GWADM failed to add the password entry to shared memory table at boot time. |
Action |
Check the size of the configuration, if it is too large then may need to consider to modify it to be smaller. | |
See Also |
| |
5330 |
INFO: The overall action/task threshold(size) is enabled by <ldom>. | |
|
Description |
The threshold is enabled for printing out warning message about action/task capacity is getting close to maximum. |
Action |
No action required. | |
5331 |
WARN: configured overall threshold value(val) is greater than maximum limitation(lim) for <ldom>, threshold value ignored. | |
|
Description |
The threshold value is greater than maximum action/task table size. This is not valid so it is ignored. |
Action |
Correct the threshold value. | |
5332 |
WARN: Overall action/task threshold for <ldom> is exceeded. | |
|
Description |
The number of used action/task exceeded the threshold. |
Action |
User can restrict the access to this local domain gateway by remove some of the exported services. | |
5333 |
INFO: Maximum action/task is set to val for local gateway <ldom>. | |
|
Description |
The maximum number of action/task the local gateway |
Action |
No action required. | |
5334 |
WARN: The specified maximum pending action/task for <ldom> out of range, it is ignored. | |
|
Description |
The maximum pending action/task for local gateway |
Action |
Correct the maximum value. | |
5335 |
ERROR: Failure to calculate MAC for RESOURCES section. | |
|
Description |
Failure occurred while calculating MAC for RESOURCES section. |
Action |
Contact your BEA Tuxedo Customer Support. | |
5336 |
ERROR: Failed to get signature key. | |
|
Description |
Unable to retrieve signing key for signature. |
Action |
Contact your BEA Tuxedo Customer Support. | |
5337 |
ERROR: Failed to sign MAC. | |
|
Description |
The signing procedure failed during MAC generation. |
Action |
Contact BEA Tuxedo Customer Support. | |
5338 |
ERROR: Failed to get signature key. | |
|
Description |
Failed to get signing key while authenticate the MAC. |
Action |
Contact BEA Tuxedo Customer Support. | |
5339 |
ERROR: Failure occurred when decrypting MAC. | |
|
Description |
Failed to decrypt MAC. |
Action |
Contact BEA Tuxedo Customer Support. | |
5340 |
ERROR: Failed to generate signature. | |
|
Description |
Unable to generate signature while authenticate the MAC. |
Action |
Contact BEA Tuxedo Customer Support. | |
5341 |
ERROR: Corrupted or modified RESOURCES section detected! | |
|
Description |
The RESOURCES section of the BDMCONFIG is either corrupted or modified. The BDMCONFIG file can not be trusted when this happen. |
Action |
Use | |
See Also |
| |
5342 |
ERROR: Failed to get Ka. | |
|
Description |
Failed to get key generating hint for Domain Key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5343 |
ERROR: Failed to get encryption key. | |
|
Description |
Error occurred while retrieving the Domain Key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5344 |
ERROR: Failed to decrypt Kb. | |
|
Description |
Failure occurred during decryption of the hint for generating Domain Key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5345 |
ERROR: Failed to get Kc. | |
|
Description |
Failure occurred during generating hint for domain encryption key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5346 |
ERROR: Failed to get DM Key. | |
|
Description |
Failure occurred while retrieving domain encryption key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5347 |
ERROR: Failed to obfuscate key. | |
|
Description |
Failed to obfuscate domain encryption key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5348 |
ERROR: Failed to reconstruct key. | |
|
Description |
Reconstruction of Domain Key failed. |
Action |
Contact BEA Tuxedo Customer Support. | |
5349 |
ERROR: Failed to generate key. | |
|
Description |
Failed to generate encryption key to encrypt hint for Domain Key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5350 |
ERROR: Failed to encrypt Kb. | |
|
Description |
Failure occurred while encrypt hint for Domain key. |
Action |
Contact BEA Tuxedo Customer Support. | |
5351 |
WARN: Parsing -a option arguments for local gateway ldom: val | |
|
Description |
Failure occurred while parsing the |
Action |
Correct the input. | |
5352 |
ERROR: Thread creation failed | |
|
Description |
The threaded gateway failed to create a thread to handle message. |
Action |
Check the OS configuration, make sure it not only supports thread but also allows enough threads per process. | |
5353 |
ERROR: Failed coordinating thread shutdown | |
|
Description |
The threaded gateway encountered an internal error while coordinating (joining) its threads while shutting down. |
Action |
Check system thread resources and tunables. Contact BEA Customer Support with information about your environment. | |
5354 |
ERROR: Gateway internal thread error resource:operation:file:line | |
|
Description |
The threaded gateway encountered an internal error while using thread resources. |
Action |
Check system thread resources and tunables. Contact BEA Customer Support with information about your environment. | |
5355 |
ERROR: Network polling failed | |
|
Description |
The threaded gateway encountered an error while polling network event. |
Action |
Check network connection status. Contact BEA Customer Support with information about your environment. | |
5356 |
ERROR: Internal system error at (val.val). | |
|
Description |
An internal system error occurred. |
Action |
Contact BEA Customer Support. | |
5357 |
ERROR: Internal system error at (val.val). Set tperrno in message. | |
|
Description |
An internal system error occurred. The relative domain gateway message will be impacted. |
Action |
Contact BEA Customer Support. | |
5358 |
ERROR: Cannot generate empty buffer at (val.val). | |
|
Description |
Domain gateway failed to generate an empty buffer for a transaction. |
Action |
Contact BEA Customer Support. | |
5359 |
WARN: The number of connections for <domain_name> exceeds limit <val>, start to suspend for <second_value> seconds. | |
|
Description |
There are too many recent connect requests accepted and/or closed. GWTDOMAIN will stop accepting connect request for a specified time limit. |
Action |
Check if GWTDOMAIN is under attack. If it is not, adjust the GWTDOMAIN command line arguments to prevent suspension when there is no attack. | |
5360 |
INFO: Resume accepting connection request. | |
|
Description |
The suspended time limit has elapsed. GWTDOMAIN resumes polling and accepting connect request from network. |
Action |
N/A | |
5361 |
INFO: The connection limit for <domain_name> is set to 0. No incoming connection request will be accepted. | |
|
Description |
GWTDOMAIN is set to an outgoing-only domain gateway. |
Action |
N/A | |
5362 |
ERROR: Failed to get signature key. | |
|
Description |
The domain component was unable to retrieve the signature key needed to sign the current message. |
Action |
Contact your Tuxedo technical support organization. | |
5363 |
ERROR: Failure occurred when decrypting MAC. | |
|
Description |
An error occurred when decrypting the Message Authentication Code digest that is optionally included with domain messages to detect corrupted messages. |
Action |
Examine the network for signs of network errors or a network attack. | |
5364 |
ERROR: Failed to generate signature. | |
|
Description |
The domain component was unable to generate the signature needed to sign the current message. |
Action |
Contact your Tuxedo technical support organization. | |
5365 |
ERROR: Corrupted or modified RESOURCES section detected! | |
|
Description |
Corruption was detected in the RESOURCES section of the BDMCONFIG file as stored in shared memory. |
Action |
Shut down and restart the GWTDOMAIN, GWADM, and DMADM servers. If the problem persists, contact your Tuxedo technical support organization. | |
5366 |
ERROR: Failed to get encryption key. | |
|
Description |
The domain component was unable to retrieve the encryption key needed to encrypt the current password with 3DES. |
Action |
Contact your Tuxedo technical support organization. | |
5367 |
ERROR: Failed to decrypt Kb. | |
|
Description |
The domain component was unable to decrypt the current domain key using 3DES. |
Action |
Contact your Tuxedo technical support organization. | |
5368 |
ERROR: Failed to get Kc. | |
|
Description |
The domain component was unable to retrieve a value requird for 3DES encryption. |
Action |
Contact your Tuxedo technical support organization. | |
5369 |
ERROR: Failed to get DM Key. | |
|
Description |
The domain component was unable to get the domain key used for 3DES encryption. |
Action |
Contact your Tuxedo technical support organization. | |
5370 |
ERROR: Failed to get Ka. | |
|
Description |
The domain component was unable to retrieve a value requird for 3DES encryption. |
Action |
Contact your Tuxedo technical support organization. | |
5371 |
ERROR: Failed to convert LPWD from AES256 to DES. | |
|
Description |
The system was unable to convert the local domain password from AES256 encryption format to DES encryption format when attemting to transmit this password to a domain that understands only the DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5372 |
ERROR: Failed to convert RPWD from AES256 to DES. | |
|
Description |
The system was unable to convert the remote domain password from AES256 encryption format to DES encryption format when attemting to transmit this password to a domain that understands only the DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5373 |
ERROR: Failed to convert pair 1 LPWD from AES256 to 3DES. | |
|
Description |
The system was unable to convert the local domain password number 1 from AES256 encryption format to 3DES encryption format when attemting to transmit this password to a domain that understands only the 3DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5374 |
ERROR: Failed to convert pair 1 RPWD from AES256 to 3DES. | |
|
Description |
The system was unable to convert the remote domain password number 1 from AES256 encryption format to 3DES encryption format when attemting to transmit this password to a domain that understands only the 3DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5375 |
ERROR: Failed to convert pair 2 LPWD from AES256 to 3DES. | |
|
Description |
The system was unable to convert the local domain password number 2 from AES256 encryption format to 3DES encryption format when attemting to transmit this password to a domain that understands only the 3DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5376 |
ERROR: Failed to convert pair 2 RPWD from AES256 to 3DES. | |
|
Description |
The system was unable to convert the remote domain password number 2 from AES256 encryption format to 3DES encryption format when attemting to transmit this password to a domain that understands only the 3DES format. |
Action |
Contact your Tuxedo technical support organization. | |
5377 |
WARN: multiple RDOMs not allowed on REMOTE_SERVICES in domain-type domain | |
|
Description |
Multiple RDOMs for the REMOTE_SERVICES is for domain failover. The failover is not supported in this domain type. |
Action |
Correct the domain configuation. | |
5378 |
ERROR: Cannot find TDOMAIN defination for local domain local-domain | |
|
Description |
When the GWADM administrative server is booted, it fetches the configuration information for its domain from the DMADM administrative server. It then loads the entries into shared memory. This message indicates that it cannot load REMOTE SERVICEs into shared memory. This should only occur if the GWADM administrative server cannot find LOCAL DOMAIN defination in the existing shared memory segments. |
Action |
Check if the local-domain exists in DM_TDOMAIN section. Add it and then restart the application. | |
See Also |
|