|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_acall has returned a failure.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_connect has returned a failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_convsend has returned a failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_decode has returned a failure.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_encode has returned a failure.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_decode has returned a failure.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_encode has returned a failure.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to create a listener.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2.
|
The //host:port parameters as specified in the DMCONFIG and the CRM command line parameters in the UBBCONFIG do not agree
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GWSNAX is unable to send the SHUTDOWN command to CRM.
|
|
|
|
|
|
|
|
|
|
|
Examine the DMCONFIG to determine if the CODEPAGE for a remote domain is specified incorrectly. Correct and retry.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_getnxt_cd has returned a failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_init_env was unable to get needed information from shared memory.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_AllocNwCtx was unable to allocate memory needed.
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_empty_sndbuf was unable to allocate memory needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
gw_nw_TranCreateTCTXT failed to create the transaction tree node object. This can be caused by reaching the configured transaction limit or by a memory allocation failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An error has been returned by gw_tx_set_rdom. Several possibilities exist for this failure.
|
|
|
Examine the DMCONFIG and compare with the number of remote domains which might become involved in the same transaction. Update the DMCONFIG if necessary. Also examine the ULOG for more information concerning possible reasons for the failure.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Examine the DMCONFIG file for the MAXTRAN parameter, this number is the limit. If MAXTRAN is not specified, then examine the ubbconfig file for the MAXGTT parameter. In the later case MAXGTT is the limit. Modify the limit if necessary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Examine the configuration to determine if there has been a change of MAXTRAN in DMCONFIG and/or a change of MAXGTT in UBBCONFIG. This condition may occur if there is a decrease in the number of transactions allowed between boots while many transactions must be recovered. If no changes have been made, contact Oracle Customer Support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The STARTTYPE specified in the DMCONFIG must be AUTO or COLD.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Examine the application and the DMCONFIG and correct the problem.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact Oracle Customer Support.
|
|
|
|
|
|
|
|
Examine the application to determine if it has an error, examine the DMCONFIG definition for any errors in the buffer type specification. If no errors are found, contact Oracle Customer Support.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_Alloc was unable to allocate memory needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_proto_flow has detected a flow control callback from gp_send.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_SendEvent has returned an error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GWSNAX has received a SHUTDOWN request from the CRM and will shut down immediately.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected by gw_nw_crmrcv. Inbound ACALL request contained SEND_INVITE for function DPL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_shm_getbylink returned an error while getting the remote domain entry.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal error has been detected, gw_nw_Realloc was unable to allocate memory needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<taskname> timed out with failCode < failcode>
|
|
|
<taskname> may appear as:
OB-Conversation #nn ( <linkref>) tx # m <tranname>, or
IB-Conversation #nn (<linkref>) tx # m <tranname>
nn is an internal APPC conversation number and m is the transaction context where -1 signifies non-transactional.
Outbound Conversation nnnn Link (<linkref>) TCTXT (tctxt) Tran(<tranname>), or
Inbound Conversation nnnn Link (<linkref>) TCTXT (tctxt) Tran(<tranname>)
nnnn is the CRM Logical Task Number and tctxt is the transaction context, where FFFFFFFF indicates notn-transactional.
|
|
|
Examine stderr and the ULOG for additional information concerning the failure.
|
|
|
|
|
|
|
|
Check for additional messages in stderr. The shared library for the stack or the stack interface might not have been loaded due to an incorrect library path.
|
|
|
|
|
|
|
|
The <returncode> is the value returned by the SNA Stack software. Check the status of the stack, the configuration of the stack, and the gateway configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<taskname> may appear as:
Outbound Conversation nnnn Link <linkref> TCTXT (<tctxt>) Tran <tranname>, or
Inbound Conversation nnnn Link <linkref> TCTXT (<tctxt>) Tran <tranname>,
nnnn is the CRM Logical TAsk Number.
tctxt is the transaction context where FFFFFFFF signifies non-transactional.
|
|
|
Examine stderr and the ULOG for additional information concerning the failure. For failcode Input/Output, verify that the user starting the CRM process has the proper file permissions for the BLOBLOG and RSTRTLOG. If no apparent error is found, contact Oracle Customer Support.
|
|
|
|
|
A second GWSNAX is attempting to connect to the CRM as a master gateway. Only one master gateway is allowed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The stackref in the link configuration is incorrect.
|
|
|
Correct the stackref that is in error, run dmloadcf, and restart.
|
|
|
|
|
|
|
|
|
|
|
|
|
An internal state table failure has occurred. The <additional information> will be one of the following:
1.
|
From <oldstate> to <newstate> for <dir>-bound transaction TCTXT<tid>
|
2.
|
To <newstate> for inbound transaction TCTXT<tid>
|
3.
|
To <newstate> for outbound transaction TCTXT<tid>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<reason> is the description of the stack return code. Determine the cause and correct.
|
|
|
|
|
|
|
|
<reason> is the description of the stack return code. Determine the cause and correct.
|
|
|
|
|
|
|
|
|
|
|
|
|
Attempted to issue a request at sync level <level> on a link that does not support that level.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The specified <combination> is invalid. It will be one of the following:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
|
|
|
|
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
|
|
|
|
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
|
|
|
|
|
Check the ULOG for any additional messages.
|
|
|
|
|
|
|
|
|
|
Link <linkref> not configured for sync level 2
|
|
|
Link specified by <linkref> is not configured for sync level 2.
|
|
|
|
|
|
|
|
|
|
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
|
|
|
|
|
Run CRMLOGS to examine the CRM log file. Cold start the Tuxedo application.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|