| Author |
Message
|
| VivekMeshram |
 Posted: Mon Nov 18, 2002 8:51 pm Post subject: The attempt to put the message into SAP failed(Inbound IDOC |
 |
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi Guys,
I've got a situation where my R/3 Inbound server is getting down throwing error "SMQ4187: The attempt to put the message into
SAP failed. The call to RfcIndirectCall for INBOUND_IDOC_PROCESS failed"
This happens when MQ message get formatted using the NEONFormaters at MQSI box and passes it in MQ Queue, from
MQ Queue the R/3 takes the IDOC to SAP and while putting the message into SAP failes for the Inbound IDOC.
This happens when MQSI puts the formated IDOC into MQ Queue and from MQ Queue to R/3 Link to put the IDOC messages
to SAP R/3 throgh SAP RFC.This problem happens sometime only let say once a every day.
Softwares:
AIX 4.3.3
MQSI 2.0.2 + CSD
MQ 5.2 + CSD
DB2(UDB) 7.1
R/3 Link 1.2.
If anyone has come accors this problem??
I Will approciate for the kind help if you can share some suggestions or guidence for the same.!!!
_________________
Thanks
Vivek S Meshram.
·IBM Certified Specialist – IBM WebSphere MQ v5.3 / v5.2 |
|
| Back to top |
|
 |
| migstr |
| Posted: Thu Nov 21, 2002 6:16 am Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
| Hi, After you receive the error are you then able to reprocess the same message and it works fine? |
|
| Back to top |
|
|
| VivekMeshram |
| Posted: Fri Nov 22, 2002 12:40 am Post subject: |
|
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi migstr,
Yes only R/3 Links goes down, the moment i start the R/3Link again, Messages are flowing correctly, since I have defined in the Inbound Ini file terminateonbadmessage=Yes, I know if i change this paramter with No then the R/3 Link wont be go down...but if there is any bad message then it will route to Bad Queues...i guess this is not the right
way to do this way...and again i have to write some code to get the messages from bad Queue. Do you ever have been across
this condition. If so i will approciate your suggestions...
_________________
Thanks
Vivek S Meshram.
·IBM Certified Specialist – IBM WebSphere MQ v5.3 / v5.2 |
|
| Back to top |
|
|
| ballplayer |
| Posted: Sun Nov 24, 2002 9:31 pm Post subject: |
|
|
Novice
Joined: 25 Jan 2002
Posts: 12
Location: Toronto
|
I've seen this problem before!! Each Inbound Server opens a gateway in SAP. It could be that the gateways (check SMGW) are closing on you at random times. In this case, the Inbound Server aborts when it receives the next IDOC. If that's the case, then your SAP Kernel needs to be upgraded. There are OSS notes documenting this problem.
My advice is to closely monitor the gateways as soon as you start the Inbound Server. When it terminates, go back to the gateway log and check for error messages. If this is the problem, then notify the BASIS people and have them upgrade the Kernel.
A possible workaround is to strip the bad message header of the IDOC and put the message back in the Inbound Queue. |
|
| Back to top |
|
|
| VivekMeshram |
| Posted: Mon Nov 25, 2002 4:56 am Post subject: |
|
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi ballplayer,
Thanks for the valuable reply, Actually whenever the Inbound Server terminates/aborts, i used to starts manually again, once it started the IDOC's follows smothly, none of messages goes into badmessages Queue.
Since you have suggested about gateway, the gateway parameter is set for the Outbound Server in ini file as gatewayservice=sapgw88 and gatewayhost=CDBXYZ. The R/3 Link goes down frequently for the Inbound Server, where there is no parameter pointing towards getway.If you would like to have a look of the Inbound as well as Outbound Server, i may send you as well.
I will check the getway whether it is closing down or not when the R/3 link downs.More ever i will look forward to hear from you..i hope you wont mind to suggest / guide me for the same.
Following are the Errors when R/3 Links goes down, i tried to put a trace for the R/3 link as well but i didnt got any trace content in the dev_rfc file at /r3link directory.
-------------------------------------------------------------------------------
11/20/02 14:05:12 SMQ4174: Inbound IDoc number received from queue.
EXPLANATION: None
ACTION: None.
-------------------------------------------------------------------------------
11/20/02 14:05:12 SMQ4197: Lock table overflow
EXPLANATION: The above text details an error that occurred in a SAP R3 Rfc function.
ACTION: None.
-------------------------------------------------------------------------------
11/20/02 14:05:12 SMQ4187: The attempt to put the message into SAP failed.
EXPLANATION: The call to RfcIndirectCall for INBOUND_IDOC_PROCESS failed.
ACTION: For more information re-run the server with trace and RFC trace enabled.
-------------------------------------------------------------------------------
11/20/02 14:05:12 SMQ4173: The server is terminating because an invalid message was received.
EXPLANATION: See previous messages to find out why the message is invalid.
ACTION: To prevent the server from terminating when bad messages are received, set
the terminateonbadmessage parameter in the ini file to N.
-------------------------------------------------------------------------------
11/20/02 14:07:12 SMQ4175: Outbound IDoc number 0000000002768280 received from SAP.
EXPLANATION: None
ACTION: None.
-------------------------------------------------------------------------------
_________________
Thanks
Vivek S Meshram.
·IBM Certified Specialist – IBM WebSphere MQ v5.3 / v5.2 |
|
| Back to top |
|
|
| ballplayer |
| Posted: Mon Nov 25, 2002 7:07 am Post subject: |
|
|
Novice
Joined: 25 Jan 2002
Posts: 12
Location: Toronto
|
Unlike the Inbound Server, the Outbound Server actually registers with the Gateway. This means that the Outbound Server can recover from gateway crashes. Usually, if this is the case, the Gateway Log will have entries such as "Conversation XXXXXXXXX Lost".
But looking at your log, it looks like the problem is the "Lock Table Overflow". That looks like an SAP specific problem pertaining to the underlying database...so this might still mean that the kernel needs to be updated or maybe the database is corrupted.
From here, I would call IBM support and ask them to interpret the message -- they will probably tell you that it's an SAP problem. At the same time, search for the Lock Table Overflow error in OSS notes. And have a look at the Gateway Log, there should be a corresponding error message there. |
|
| Back to top |
|
|
| migstr |
| Posted: Mon Nov 25, 2002 11:18 am Post subject: |
|
|
Apprentice
Joined: 05 Jun 2002
Posts: 34
Location: New York
|
Hi,
ballplayer that was some good info. We use the method of just writing to bad message queue then stripping off bad message header and reprocessing.
do you guys have any insight into how to 'tune' the R/3 Link to SAP Post process. We post all of our IDOCs to 64 status first because we receive large numbers of them at one time and don't want to process them immediately. We've tried batching the inbound idocs together and running multiple instances of the inbound servers which has helped but not enough. Are there any other items that can be'tuned' to quicken this process? Thanks in advance. |
|
| Back to top |
|
|
| ballplayer |
| Posted: Mon Nov 25, 2002 3:10 pm Post subject: |
|
|
Novice
Joined: 25 Jan 2002
Posts: 12
Location: Toronto
|
From my experience, inbound IDOCs get posted by MQLink into SAP much faster than they get processed. To speed the processing up, some configuration might need to be done in SAP to process the 64 status IDOCs in parallel. I don't know exactly how to do this, but I know it can be done.
Although parallel processing will speed this up, the IDOCs are not guaranteed to be processed in the order which they arrive. This may be a problem if business requires first-in first-out. |
|
| Back to top |
|
|
| VivekMeshram |
| Posted: Mon Nov 25, 2002 9:25 pm Post subject: |
|
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi ballplayer,
Thanks again for the valuable info as well as attending ..I have pointed that for the Inbound IDOC , i encounters with "Lock table overflow" Error Followed by the same, while the following is for the Outbound IDOC as follows.
R/3 Link Error For Outbound IDOC :
-------------------------------------------------------------------------------
11/20/02 14:52:02 SMQ4175: Outbound IDoc number 0000000002761848 received from SAP.
EXPLANATION: None
ACTION: None.
-------------------------------------------------------------------------------
11/20/02 14:53:04 SMQ4197: Time limit exceeded.
EXPLANATION: The above text details an error that occurred in a SAP R3 Rfc function.
ACTION: None.
-------------------------------------------------------------------------------
11/20/02 14:53:04 SMQ4187: The attempt to put the message into SAP failed.
EXPLANATION: The call to RfcIndirectCall for INBOUND_IDOC_PROCESS failed.
ACTION: For more information re-run the server with trace and RFC trace enabled.
-------------------------------------------------------------------------------
11/20/02 14:53:04 SMQ4173: The server is terminating because an invalid message was received.
EXPLANATION: See previous messages to find out why the message is invalid.
ACTION: To prevent the server from terminating when bad messages are received, set
the terminateonbadmessage parameter in the ini file to N.
-------------------------------------------------------------------------------
11/20/02 14:56:59 SMQ4175: Outbound IDoc number 0000000002761849 received from SAP.
EXPLANATION: None
ACTION: None.
-------------------------------------------------------------------------------
Having checked the SAP Gateway Error Log, which is as follows.
Mon Nov 25 16:42:54 2002
***LOG S23=> GwDisconnectClient, client disconnected (244) [gwxxrd.c 9809]
***LOG S74=> GwDisconnectClient, client disconnected ( CMQAXP01) [gwxxrd.c 9820]
***LOG S0R=> GwDisconnectClient, client disconnected () [gwxxrd.c 9836]
***LOG S0I=> GwDisconnectClient, client disconnected ( SAPCPIC) [gwxxrd.c 9857]
*****************************************************************************
*
* LOCATION SAP-Gateway on host CAPAXP03
* ERROR connection to client SAPCPIC on host CMQAXP01 broken (read)
*
* TIME Mon Nov 25 16:42:54 2002
* RELEASE 46D
* COMPONENT SAP-Gateway
* VERSION 2
* RC 223
* MODULE gwxxrd.c
* LINE 9863
* COUNTER 70736
*
*************************************************************
I hope you might help to trace to problem, in fact i am trying to increase the
table size at the SAP side and looking at the SAP Gateway error log
_________________
Thanks
Vivek S Meshram.
·IBM Certified Specialist – IBM WebSphere MQ v5.3 / v5.2 |
|
| Back to top |
|
|
| VivekMeshram |
| Posted: Thu Dec 19, 2002 2:43 am Post subject: |
|
|
Voyager
Joined: 25 Mar 2002
Posts: 83
|
Hi ,
Those we are interested to know about the above problem, Actually at the SAP side there is LOCK table parameter called enque/table_size which we have to incresed becos this Lock Tables gets full when there are lots of user hitting and back ground job are running a log and once it crosses the limit the RFC (Remote Function Call) fails and the MQ R/3 goes down throwing the "LOCK Table OverFlow".
Another findings is that we might need to check the time limit parameter for the RFC gateway (gw/gateway) and if possible increased it according to requirments this parameter as well, otherwise if the specified time is over and if other application server is not available at SAP to handle this RFC request call, it will throw error "Time Limit Exceeded".
_________________
Thanks
Vivek S Meshram.
·IBM Certified Specialist – IBM WebSphere MQ v5.3 / v5.2 |
|
| Back to top |
|
|
|
|
