Unable to create RFQ in ME41 transaction

Hi,
I have been trying to create RFQ in ME41 transaction after providing the requisite entries. After click on Save button, I get a message mentioning "Document Created <RFQNum> and immediately I get a popup "Express document Update was terminated recieved from author <username>. And the RFQ number is not available in Table EKKO.
Kindly suggest what should be the issue causing the RFQ created to be terminated.
Thanks in advance.
Thanks,
Guru

Hi,
That's the message you get from the workflow. I think the workflow of RFQ must be implemented in ur company. Sometimes it gives this message bcoz of some functional related issues. Ask the MM consultant for furthur clarifications.
Regards,
Jeet K Bhatt

Similar Messages

Unable to Create RFQ

Hi,
I have been trying to create RFQ in ME41 transaction after providing the requisite entries. After click on Save button, I get a message mentioning "Document Created <RFQNum> and immediately I get a popup "Express document Update was terminated recieved from author <username>. And the RFQ number is not available in Table EKKO.
Kindly suggest what should be the issue causing the RFQ created to be terminated.
Thanks in advance.
Thanks,
Guru

hi
I also have the same problem
but i solve it.
you should clean your spool from RSPO0041.
after u execute this program from se38 also u should click
- All request with min age
- complete request with min age
and just run it.
take care
Baki...
Edited by: Baki Ozeke on May 4, 2010 11:15 AM

Unable to create outbound delivery using transaction VL10B

Hello,
When I am trying to create an outbound delivery from refrencing a Purchase Order using transaction VL10B,
the item is not getting selected (In the VL10B , I entered the PO number and executed but in the next screen no items are displayed ).
Please let me know the reasons for this.
Please Note : I tried to change the PO delivery date ,but still the above problem persist.
Thanks & Regards,
Sumanta Deb

Hello Sumanta
Please check at item level in PO under 'delivery schedule' tab, what is the material staging date. If this date is in the future, VL10B will not show any line item in due list. VL10B will only show due list from today and backdated deliveries.
Let me know if u have any more issue related to this
Amol

Unable to create followup and view transaction types for InteractionRecord

Hi,
We are currently working in crm 7.0 environment.
we are not able to create followup transaction for Interaction Record -
Transaction Type - Business activity(0010).
We are not even able to view the standard transaction types available
when we select followup both in UI and GuI.
Any inputs in this regard are rewarded and appreciated.

Hi sreenicrm,
Have you configured anything in the "Allowed Channels for transaction types".
If not, it may be worth copying the standard transation type and then setting the values in the above screens.
if you set a values of "interaction Center"(IAC) and "CRM Server"(GUI) then you shoudl see the activity.
I am using CRM 5.0 but would imaging it is similar in 7.0.
HTH
Gaz

Unable to create a follow-up transaction in EP-PCUI - Urgent - Please help

Dear CRM experts,
Here is my EP/PCUI scenario:
I have created new PCUI related iviews from the EP. When i create a Follow up activity (Opportunity) from the Leads, it works absolutely fine and takes me to the Opportunity screen. But, when i try to create the Follow up activity( quotation) from the Opportunity, it takes me to a new page with an error message at the top "Page not found or not available". Same thing happens if i try to create a Follow up activity from Quotation to Quotation. Also, if i try to go to Accounts page from Leads, I get the same error page.
But the wierd part is that if i run the iview in the Preview mode (Content management) it asks me to fill in the user id/pwd and it works fine - Creates the Follow up activites.
I'm not sure if i need to make any changes in the EP or PCUI to make this work. Any Ideas ????
Thanks,
Raj

Any inputs please?

Unable to create a 'Z' for se16 transaction

Hi everyone,
we have a requirement where we are unable to create a Z for transaction SE16.
I went to se93 and checked it was a function pool so i went to SE80 to make a copy of standard function group SETB to ZSETB.
it made a copy of it anf I copied all the FM's and made a Z of those.
Once it is done. When I activate it it give a lot of errors , I have checked it and made sure that it is copying entire Function Group but all are fine.
My system is ECC6.0, earlier we had ZE16 which is a replica of SE16 and this had a lot of problem like ending in dumps , so we thought we would make a new Z transaction for SE16, but we get many error.
Please try it out once in ur system before U suggest me a change to be made.
Regards,
Raj

It is always best to minimize such issues by making a copy of programs or function modules where changes are needed to add new functionality. Also this would ensure any patches/notes added in future would have minimum impact on your clones.
-Cheers

Unable to create delivery using ADSUBCON

Hi Gurus,
I am unable to create delivery using ADSUBCON transaction for the PO which has material with different Order Unit. My base unit of measure is EA where as the Order unit is Roll. If I delete the order unit system allows me to create delivery where the PO.
Why the system does not allow me to create the delivery when the order unit is different than base unit of measure.
Thanks in advance,
Shashidhar
Edited by: Shashidhar on Jan 29, 2011 5:19 AM

HI,
Its already been maintained.
Shashi

Unable to create response to an RFQ

Hi all,
I am working on E-sourcing 5.0.When creating the response to an RFQ,i login as the vendor and aenter the price details and try to submit the response but get the following error "At least one of the items above is invalid. Mouse over the highlighted area for more details." under the QUESTIONS tab.
Has anybody faced this error??Is this a config issue or am i doing something wrong while creating the response to an RFQ.Please help.

Thanks Tridip for the reply.
As i explained earlier,I am unable to create response to any RFQ in the system using the vendor login.I get the error "At least one of the items above is invalid. Mouse over the highlighted area for more details." under the QUESTIONS tab in the RESPONSE screen.
The above mentioned error is in RED.Other then this there is no message which actually explains where exactly the info is missing because of which the erroris raised!
Also ,I can see the Plant details for the line item.
You have mentioned I need to enter the Incoterms....Can you tell me where exactly I need to enter the incoterms(as in under which tab)?
Any other suggestions???Please help ....

Finding BAPI/RFC/FM For ME41(Create RFQ)

Hi,
Plz help me for finding Bapi/Rfc/Fm for t-code ME41(Create RFQ).
Thanks,
Sunil Sahoo

hi
we have BAPI'S for many requirements like
BAPI_VENDOR_CREATE
BAPI_REQUISITION_CREATE.
BAPI_QUOTATION_CREATEFROMDATA
you try this BAPI
ME_CREATE_REQUISITION_EXT
hope this helps
regards
Aakash

Unable to create a transacted JMS Session

          We have some code that worked perfectly under wls7.0 and earlier, but refuses to
          work under wls8.1. In our situation, we are unable to create a JMS Session with
          internal transactions.
          The result of the following code
          System.out.println("transacted_=" + transacted_);
          tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          System.out.println("session.getTransacted()=" + tsession.getTransacted());
          is the following
          transacted_=true
          session.getTransacted()=false
          We have tried using xa true and false; but commonly use false.
          //from config.xml
          <JMSConnectionFactory JNDIName="corej2ee.jms.JMSConnectionFactory"
          Name="CoreJMSConnectionFactory" Targets="myserver"/>
          thanks,
          jim


An alternative is to modify the servlet code to use global (user)
          transactions instead of local (transacted session)
          transactions - the performance will likely be the same in your case -
          or may actually improve due to the activation of the pooling code.
          jim stafford wrote:
          > You were correct about us using the resource-ref. The documentation seemed to indicate
          > that our servlet code should have worked as initially developed, however the new
          > changes work
          >
          > //replace resource-ref lookup with env-entry to allow transacted JMS
          > //sessions. This is new with wls8.1
          > //tconFactory = (TopicConnectionFactory)
          > // ctx.lookup("java:comp/env/jms/topicFactory");
          > String factoryName =
          > (String)ctx.lookup("java:comp/env/jms/myConnectionFactory");
          > System.out.println("using global jndi name:" + factoryName);
          > tconFactory = (TopicConnectionFactory)
          > ctx.lookup(factoryName);
          > tcon = tconFactory.createTopicConnection();
          >
          > System.out.println("transacted_=" + transacted_);
          > tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          > System.out.println("session.getTransacted()=" + tsession.getTransacted());
          >
          > --- output
          > Looking up topic connection factory
          > using global jndi name:corej2ee.jms.JMSConnectionFactory
          > transacted_=true
          > session.getTransacted()=true
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Hi Jim,
          >>
          >>My first thought is that the app is running
          >>on the WL server and that the app is using EJB "resource
          >>references" to indirectly access its JMS resources.
          >>Stricter J2EE compliance in 8.1 causes JMS resources
          >>accessed via resource references to ignore the transacted flag.
          >>
          >>See "J2EE Compliance" under:
          >>http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
          >>
          >>The work-around is to directly specify the JNDI name
          >>of the CF in the app directly instead of looking it up
          >>via a resource reference.
          >>
          >>Please let me know if this helps.
          >>
          >>Tom
          >>
          >>jim stafford wrote:
          >>
          >>
          >>>We have some code that worked perfectly under wls7.0 and earlier, but
          >>
          >>refuses to
          >>
          >>>work under wls8.1. In our situation, we are unable to create a JMS
          >>
          >>Session with
          >>
          >>>internal transactions.
          >>>
          >>>The result of the following code
          >>>
          >>>System.out.println("transacted_=" + transacted_);
          >>>tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          >>>System.out.println("session.getTransacted()=" + tsession.getTransacted());
          >>>
          >>>is the following
          >>>
          >>>transacted_=true
          >>>session.getTransacted()=false
          >>>
          >>>We have tried using xa true and false; but commonly use false.
          >>>
          >>>//from config.xml
          >>><JMSConnectionFactory JNDIName="corej2ee.jms.JMSConnectionFactory"
          >>> Name="CoreJMSConnectionFactory" Targets="myserver"/>
          >>>
          >>>thanks,
          >>>jim
          >>
          >

Getting error when creating a RFQ in MM module" create rfq item overview"

Hi,
i am a beginer in SAP administration, users are getting this error message and i have done all my research and not able to resolve this issue.
This error i am getting when creating a RFQ in MM module and when trying to save the screen "create rfq item overview" then it gives me a pop up box message " SAP SYSTEM MANAGER: WORK PROCESS RESTARTED, SESSION TERMINATED".
Here are the details of teh system
SAP Version :ideas 4.7
Database :Oracle
OS : windows 2003
Module user is working on MM
user working on it is a Super user with all the permissions
SAP is configure to run under the European date and decimal format.
I have never done any database administration on it, it is a new install and has been rarely used.
User creates a RFQ and when he tries saving it , seems like for the first time after either restarting the macine or restarting the service it might work and at time it might not, this is a very sporadic error and most of the times it crashes out with the message "sap system manager:work process restarted, session terminated" and kicks the user out of the session.
Below are the details of the error message from ST22 :
name of the runtime error : system_core_dumped
below are the details of the error message and its resoltion as suggested by sap help :
========
Runtime Errors         SYSTEM_CORE_DUMPED
       Occurred on     01.02.2008 at 07:52:19
Process terminated by signal " ".
What happened?
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLCLSC" had to be terminated because the ABAP
processor discovered an invalid system state.
What can you do?
                                                                                Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An SAP System process was terminated by an operating system signal.
                                                                                Possible reasons for this are:
1. Internal SAP System error.
2. Process was terminated externally (by the system administrator).
           Last error logged in SAP kernel
                                                                                Component............ "Taskhandler"
Place................ "SAP-Server server1_DEV_00 on host server1 (wp 1)"
Version.............. 1
Error code........... 11
Error text........... "ThSigHandler: signal"
Description.......... " "
System call.......... " "
Module............... "thxxhead.c"
Line................. 9555
How to correct the error
The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
contains a file called 'core'.
Save this file under another name.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
                                                                                2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. " "
Application server....... " "
Network address.......... " "
Operating system......... " "
Release.................. " "
Hardware type............ " "
Character length......... " " Bits
Pointer length........... " " Bits
Work process number...... " "
Short dump setting....... " "
Database server.......... " "
Database type............ " "
Database name............ " "
Database owner........... " "
Character set............ " "
SAP kernel............... " "
Created on............... " "
Created in............... " "
Database version......... " "
Patch level.............. " "
Patch text............... " "
Supported environment....
Database................. " "
SAP database version..... " "
Operating system......... " "
User, transaction...
Client.............. " "
User................ " "
Language key........ " "
Transaction......... "ME41 "
Program............. "SAPLCLSC"
Screen.............. "SAPMM06E 0320"
Screen line......... 71
Information on where termination occurred
The termination occurred in the ABAP program "SAPLCLSC" in "EXECUTE_SELECT".
The main program was "SAPMM06E ".
The termination occurred in line 131 of the source code of the (Include)
program "LCLSCF2G"
of the source code of program "LCLSCF2G" (when calling the editor 1310).
=============
i even tried increasing the dialog processes but with no use.The same error occurs.
I appreciate every one of help i can get, i am working on a deadline which is tomorrow evening to resovle this issue, any kind of help is highly appreciated.
thanks
mudessir.

Hi Mudessir,
With the help of ABAP'er try the following.
1. open the program 'LCLSCF2G' from SE38.
2. Keep a break point at line no: 131.
There is 'END SELECT' statement which is getting failed at line no 131 in the program.
Try to analyse the SY-SUBRC at that point.
If your technical consultant can't solve this, write to SAP OSS (service.sap.com).
I have searched SAP OSS, there are other situations, but your case is not there. So write to SAP if technical consultant can't solve it by debugging the program.
Regards,
Madhu.

How to create RFQ s and use them to complete the program

hi,
how to create RFQ s and use them to complete the program
thanks in advance

Hi Santosh,
RFQ is created through transaction ME41.
You need to write down BDC for mass update of RFQ, because BAPI is not available.
Regards,
Tutun

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

Unable to create IDOCs after client copy

I'm unable to create IDOCs after a client copy. I receive a SAPSQL_ARRAY_INSERT_DUPREC or insert of duplicate rows ABAP dump.
Does anyone know what how to fix this. Thank you in advance.
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          22.10.2007 16:50:51
ShrtText
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLEDI1" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"F09_IDOC_INSERT_WITH_NUMBER" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLEDI1" or "LEDI1F09"
"F09_IDOC_INSERT_WITH_NUMBER"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
The exception must either be prevented, caught within the procedure
"F09_IDOC_INSERT_WITH_NUMBER"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "auaplxr3q"
Network address.......... "128.197.135.5"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "000B439ED600"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "auaplxr3q"
Database type............ "ORACLE"
Database name............ "Q63"
Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Mar 22 2007 20:48:46"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 4189928
Heap..................... 0
Page..................... 0
MM Used.................. 1469352
MM Free.................. 2718056
SAP Release.............. "640"
User and Transaction
Information on where terminated
The termination occurred in the ABAP program "SAPLEDI1" in
"F09_IDOC_INSERT_WITH_NUMBER".
The main program was "SAPMSSY1 ".
The termination occurred in line 108 of the source code of the (Include)
program "LEDI1F09"
of the source code of program "LEDI1F09" (when calling the editor 1080).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "F09_IDOC_INSERT_WITH_NUMBER" "(FORM)" but was not handled locally,
not declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLEDI1 ". Its source code starts in line 5
of the (Include) program "LEDI1F09 ".
Source Code Extract
Line
SourceCde
78
perform call_badi tables list_container_insert
79
using control
80
ident.
81
Aufruf des Badi's für das einstreuen neuer Segmente
82
perform call_insert_badi tables list_container_insert
83
using control
84
ident
85
changing maxsegnum.
86
87
   free list_container_insert
88
FREE_RETURN = 1.
89
ELSE. " no other IDoc is open in create-mode
90
LOOP AT LIST_CONTAINER_CREATE WHERE MANDT EQ SY-MANDT
91
AND   DOCNUM EQ IDENT.
92
LIST_CONTAINER_CREATE-DOCNUM = DOCNUM.
93
MODIFY LIST_CONTAINER_CREATE.
94
ADD 1 TO MAXSEGNUM.
95
ENDLOOP.
96
if control-mestyp eq c_mestyp.
97
CALL FUNCTION 'FUNCTION_EXISTS'
98
EXPORTING
99
funcname           = c_func
100
EXCEPTIONS
101
FUNCTION_NOT_EXIST = 1.
102
IF syst-subrc IS INITIAL. "Anwendungssystem
103
perform call_transform
104
tables list_container_create
105
using control.
106
ENDIF.
107
endif.
>>>>>
INSERT EDID4 FROM TABLE LIST_CONTAINER_CREATE.
109
Aufruf des Badi's für das Anwendungsmapping einzelner Felder
110
perform call_badi tables list_container_create
111
using control
112
ident.
113
perform call_insert_badi tables list_container_create
114
using control
115
ident
116
changing maxsegnum.
117
118
free list_container_create
119
FREE_RETURN = 0.
120
ENDIF.
121
122
insert status records
123
124
SYN_ERROR_IN = ' '.
125
CNTR_STATUS = 0.
126
REFRESH LIST_STATUS.
127
CLEAR LIST_STATUS.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
2
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
13 FORM         SAPLEDI1                            LEDI1F09                              108
F09_IDOC_INSERT_WITH_NUMBER
12 FUNCTION     SAPLEDI1                            LEDI1U19                               33
EDI_DOCUMENT_CLOSE_CREATE_TAB
11 FUNCTION     SAPLEDIR                            LEDIRU01                              273
IDOC_INBOUND_WRITE_TO_DB
10 FORM         SAPLEDIN                            LEDINF01                              457
ONE_IDOC_STORE
9 FUNCTION     SAPLEDIN                            LEDINU05                              234
IDOC_INBOUND_ASYNCHRONOUS
8 FORM         SAPLEDIN                            LEDINV05                               19
IDOC_INBOUND_ASYNCHRONOUS
7 FORM         SAPMSSY1                            SAPMSSY1                              254
XAB_RUN_DRIVER
6 FUNCTION     SAPLSXAB                            LSXABU01                                9
RFC_RUN_XAB_DRIVER
5 FUNCTION     SAPLERFC                            LERFCU01                               59
ARFC_EXECUTE
4 FUNCTION     SAPLERFC                            LERFCU02                              229
ARFC_DEST_SHIP
3 FORM         SAPLERFC                            LERFCV02                               28
ARFC_DEST_SHIP
2 FORM         SAPMSSY1                            SAPMSSY1                               69
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.      13 Ty.          FORM
Name F09_IDOC_INSERT_WITH_NUMBER
CONTROL-MESTYP
USERCLONE
554544444222222222222222222222
53523CFE5000000000000000000000
C_MESTYP
FIDCCH
444444222222222222222222222222
694338000000000000000000000000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
LIST_STATUS-STAPA2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
C_FUNC
IDOC_TRANSFORM
444455544544542222222222222222
94F3F421E36F2D0000000000000000
SYST-REPID
SAPLEDI1
5454444322222222222222222222222222222222
310C549100000000000000000000000000000000
SY-UNAME
Q63CLNT140
533444533322
1633CE414000
%_DUMMY$$
2222
0000
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
SYST-SUBRC
0
0000
0000
ALE_IDOC_TO_APL_OK
62
33
62
LIST_CONTAINER_CREATE[]
Table IT_20[9x1068]
FUNCTION-POOL=EDI1DATA=LIST_CONTAINER_CREATE[]
Table reference: 14
TABH+ 0(20) = 070000008036F5B8000000000000000000000000
TABH+ 20(20) = 0000000E00000014000000090000042CFFFFFFFF
TABH+ 40(16) = 0400002300000CA0000824C401000000
store        = 0x070000008036F5B8
ext1         = 0x0000000000000000
shmId        = 0     (0x00000000)
id           = 14    (0x0000000E)
label        = 20    (0x00000014)
fill         = 9     (0x00000009)
leng         = 1068 (0x0000042C)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000048
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x070000008036F610
pghook       = 0x07000000802D86D0
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 23    (0x00000017)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = Not allocated
hsdir        = Not allocated
ext2         = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack     = Not allocated
delta_head   = Not allocated
pb_func      = Not allocated
pb_handle    = Not allocated
LIST_CONTAINER_CREATE
1400000000000511747000000009E1BPADRML                     00000002#èXD63        070TST_QA140_1
3333333333333333333333333333434544544222222222222222222222333333330E54332222222233355555433353
14000000000005117470000000095120142DC0000000000000000000000000000238846300000000070434F11140F1
CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
G_MAXSYNERR
1
0000
0001
<%_TABLE_EDID4>
ALE_DISPATCH_ERROR
27
33
27
ALE_IDOC_READY_FOR_APL
64
33
64
%_SPACE
2
0
IDENT
0000000000000001
3333333333333333
0000000000000001
ALE_IDOC_TO_APL_ERROR
63
33
63
No.      12 Ty.          FUNCTION
Name EDI_DOCUMENT_CLOSE_CREATE_TAB
IDENTIFIER
0000000000000001
3333333333333333
0000000000000001
NO_DEQUEUE
X
5
8
SYN_ACTIVE
Y
5
9
IDOC_CONTROL
1400000000000511747640 64        2SAPQ63    LSQ63CLNT140
3333333333333333333333233222222223545533222245533444533322222222222222222222222222222222222222
14000000000005117476400640000000023101630000C31633CE414000000000000000000000000000000000000000
SYNTAX_RETURN
0
0000
0000
INT_EDIDD[]
Table IT_10[9x1062]
FUNCTION-POOL=EDINDATA=G_T_DATA_RECORDS[]
Table reference: 9
TABH+ 0(20) = 0700000080284B80070000008028530800000000
TABH+ 20(20) = 000000090000000A0000000900000426FFFFFFFF
TABH+ 40(16) = 0400000900000AA8000824C401000000
store        = 0x0700000080284B80
ext1         = 0x0700000080285308
shmId        = 0     (0x00000000)
id           = 9     (0x00000009)
label        = 10    (0x0000000A)
fill         = 9     (0x00000009)
leng         = 1062 (0x00000426)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000039
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x0700000080320D90
pghook       = 0x07000000802E1508
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 17    (0x00000011)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802852A8
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080284B30
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
NO_IGNORE
2
0
EDI_IDOC_SYNTAX_ERROR_IN
60
33
60
DOCNUM
0000000000511747
3333333333333333
0000000000511747
EXCLUSIVE
E
4
5
SYNCHRONOUS
S
5
3
APL_TESTIDOC_CHECK_OK
55
33
55
FREE_RETURN
0
0000
0000
INT_EDIDD
1400000000000000001000009E1BPADRML                  00000000##XD63        070TST_QA140_17 X00
3333333333333333333333333434544544222222222222222222333333330054332222222233355555433353322533
14000000000000000010000095120142DC0000000000000000000000000000846300000000070434F11140F1700800
SUB_INT_ACK_POSITIVE
14
33
14
G_INSERT_OK
2
0
LIST_CONTAINER_INSERT_TMP[]
Table[initial]
LIST_CONTAINER_INSERT_TMP
0000000000000000000000000                              00000000##
2223333333333333333333333333222222222222222222222222222222333333330022222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.      11 Ty.          FUNCTION
Name IDOC_INBOUND_WRITE_TO_DB
PI_DO_HANDLE_ERROR
X
5
8
PI_NO_DEQUEUE
X
5
8
PI_RETURN_DATA_FLAG
X
5
8
PI_RFC_MULTI_CP
0000
3333
0000
PI_STATUS_MESSAGE
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PE_IDOC_NUMBER
0000000000000001
3333333333333333
0000000000000001
PE_INBOUND_PROCESS_DATA
140BAPI                                                  6
3334454222222222222222222222222222222222222222222222222223222222222222222222222222222222222222
1402109000000000000000000000000000000000000000000000000006000000000000000000000000000000000000
PE_STATE_OF_PROCESSING
0
0000
0000
T_DATA_RECORDS[]
Table IT_10[9x1062]
T_LINKED_OBJECTS[]
Table IT_11[0x100]
FUNCTION-POOL=EDINFORM=ONE_IDOC_STOREDATA=LT_LINKED_OBJECTS[]
Table reference: 10
TABH+ 0(20) = 000000000000000007000000802853F000000000
TABH+ 20(20) = 0000000A0000000B0000000000000064FFFFFFFF
TABH+ 40(16) = 0400000900002BB00010249401000000
store        = 0x0000000000000000
ext1         = 0x07000000802853F0
shmId        = 0     (0x00000000)
id           = 10    (0x0000000A)
label        = 11    (0x0000000B)
fill         = 0     (0x00000000)
leng         = 100   (0x00000064)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000190
occu         = 16    (0x00000010)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 1
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = Not allocated
pghook       = Not allocated
idxPtr       = Not allocated
refCount     = Not allocated
tstRefCount = Not allocated
lineAdmin    = Not allocated
lineAlloc    = Not allocated
store_id     = Not allocated
shmIsReadOnly = Not allocated
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x0700000080285390
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x0700000080285340
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
PC_CONTROL_RECORD
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_VIASELSCR
0
4
%_SPACE
2
0
L_STATUS
64
33
64
L_ALE_SUCCESS_MESSAGE
B1                  S005                                                  No filters
4322222222222222222253332222222222222222222222222222222222222222222222222246266676772222222222
21000000000000000000300500000000000000000000000000000000000000000000000000EF069C45230000000000
ST_PREVIOUS_PARTNER_DATA-SYNCHK
X
5
8
C_TRUE
X
5
8
SYST-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
C_ELEMENT_UNPROCESSED_IDOCS
Unprocessed_IDocs
56776667766544667222222222222222
5E02F353354F94F33000000000000000
ST_PREVIOUS_STATE_OF_PROCE
0
0000
0000
ST_INBOUND_PROCESS_DATA-EDIVR2
6
3
6
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
L_SYN_ACTIVE
Y
5
9
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
L_SYNTAX_RETURN
0
0000
0000
%_DUMMY$$
2222
0000
SY-REPID
SAPLEDIR
5454444522222222222222222222222222222222
310C549200000000000000000000000000000000
No.      10 Ty.          FORM
Name ONE_IDOC_STORE
IDOC_NUMBER_IN
0000000000000000
3333333333333333
0000000000000000
STATE_OF_PROCESSING_IN
0
0000
0000
INBOUND_PROCESS_DATA_IN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS[]
Table[initial]
G_LAST_IDOC_NUMBER
0000000000000000
3333333333333333
0000000000000000
SYST-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
CURRENT_CONTROL_RECORD_IN-DOCNUM
0000000000000000
3333333333333333
0000000000000000
CONV_ERROR
2
0
C_TRUE
X
5
8
SY
0000000000000000000000000000000000000000000000000000000000000000000000000000000200000000000000
0002000000010009000000000000000000000000000100000001000000010000000000000000004C00000000000000
STATUS_MESSAGE_IN
000000000000000000000000000000000000000000000000000000000000
2223333333333333333333333333333333333333333333333333333333333332222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
C_IDOC_SELECT_AND_WRITE_TO_DB
5
3
5
SY-REPID
SAPLEDIN
5454444422222222222222222222222222222222
310C549E00000000000000000000000000000000
STATUS_MESSAGE_IN-STAMID
22222222222222222222
00000000000000000000
GT_NEW_IDOC_IDENTIFICATIONS
0000000000000000
3333333333333333222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
STATUS_MESSAGE_IN-STAMNO
000
333
000
RET_FLAG
X
5
8
G_RFC_CODEPAGE
0000
3333
0000
RSJOBINFO-JOBSUBRC
0
0000
0000
SY-XFORM
IDOC_INBOUND_ASYNCHRONOUS
444454444544545544454445522222
94F3F9E2F5E4F139E382FEF5300000
SY-LANGU
E
4
5
G_T_DATA_RECORDS[]
Table IT_10[9x1062]
LT_LINKED_OBJECTS[]
Table IT_11[0x100]
CURRENT_CONTROL_RECORD_IN
1400000000000000000    30        2          LSQ63CLNT140
3333333333333333333222233222222223222222222245533444533322222222222222222222222222222222222222
14000000000000000000000300000000020000000000C31633CE414000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
SWO_%OBJID
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No.       9 Ty.          FUNCTION
Name IDOC_INBOUND_ASYNCHRONOUS
IDOC_CONTROL_REC_40[]
Table IT_3[1x524]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_CONTROL_REC_40[]
Table reference: 3
TABH+ 0(20) = 07000000802D876007000000802D449000000000
TABH+ 20(20) = 0000000300000003000000010000020C000000E0
TABH+ 40(16) = 0400000900001FE0000A249001000000
store        = 0x07000000802D8760
ext1         = 0x07000000802D4490
shmId        = 0     (0x00000000)
id           = 3     (0x00000003)
label        = 3     (0x00000003)
fill         = 1     (0x00000001)
leng         = 524   (0x0000020C)
loop         = 224   (0x000000E0)
xtyp         = TYPE#000136
occu         = 10    (0x0000000A)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802DB9D8
pghook       = 0x0000000000000000
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 10    (0x0000000A)
lineAlloc    = 10    (0x0000000A)
store_id     = 9     (0x00000009)
shmIsReadOnly = 0     (0x00000000)
>>>>> 1st level extension part <<<<<
regHook      = 0x0000000000000000
hsdir        = 0x0000000000000000
ext2         = 0x07000000802D88A0
>>>>> 2nd level extension part <<<<<
tabhBack     = 0x07000000802D8710
delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func      = 0x0000000000000000
pb_handle    = 0x0000000000000000
IDOC_DATA_REC_40[]
Table IT_4[9x1063]
FUNCTION-POOL=EDINFORM=IDOC_INBOUND_ASYNCHRONOUSDATA=IDOC_DATA_REC_40[]
Table reference: 4
TABH+ 0(20) = 07000000802D880807000000802D896000000000
TABH+ 20(20) = 00000004000000040000000900000427FFFFFFFF
TABH+ 40(16) = 04000009000020500008249001000000
store        = 0x07000000802D8808
ext1         = 0x07000000802D8960
shmId        = 0     (0x00000000)
id           = 4     (0x00000004)
label        = 4     (0x00000004)
fill         = 9     (0x00000009)
leng         = 1063 (0x00000427)
loop         = -1    (0xFFFFFFFF)
xtyp         = TYPE#000138
occu         = 8     (0x00000008)
access       = 1     (ItAccessStandard)
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniqueNon)
keyKind      = 1     (default)
cmpMode      = 2     (cmpSingleMcmpR)
occu0        = 0
collHash     = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind       = 0
isUsed       = 1
>>>>> Shareable Table Header Data <<<<<
tabi         = 0x07000000802E1550
pghook       = 0x07000000802D8860
idxPtr       = 0x0000000000000000
refCount     = 0     (0x00000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 16    (0x00000010)
lineAlloc    = 16    (0x00000010)
store_id     = 12    (0x0000000C)
shmIsReadOnly = 0     (0x

Hi Rohan,
Welcome to SDN!
This error means that you're trying to duplicate a record on the DB... check the IDOC number ranges... it might help
Regards
Juan
Please reward with points if helpful

Unable to create temporary backing file

My program is throwing out the error:
temporary open: /var/tmp/BDB20825: Too many open files
unable to create temporary backing file
This happens after my program has been running for about 4 hours. The program appears to run out of file descriptors. The listing of /proc/<PID>/fd shows hundreds of lines naming the same file (/var/tmp/BDB20825), like this:
lrwx------ 1 zobell users 64 Jul 28 14:41 622 -> /var/tmp/BDB20825 (deleted)
That file does not exist. I suspect that someone is deleting but failing to close the file. A few open file descriptors with this deleted file occur slowly in the early hours, but not at a fast enough rate to bring the program down when it does. It looks like there is a sudden flood at the end.
The program repeats this error slowly, and is stuck inside the db code. Here is the gdb backtrace I am seeing every time I interrupt:
(gdb) where
#0 0x00e74410 in __kernel_vsyscall ()
#1 0x003d51dd in ___newselect_nocancel () from /lib/libc.so.6
#2 0x002e5d39 in __os_sleep () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#3 0x002e43f1 in __os_openhandle () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#4 0x002e52ad in __os_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#5 0x002c0357 in __db_tmp_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#6 0x002c006c in __db_appname () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#7 0x002d50c9 in __memp_bhwrite () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#8 0x002d4a27 in __memp_alloc () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#9 0x002d62ec in __memp_fget () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#10 0x00232003 in __bam_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#11 0x002abc79 in __db_new_file () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#12 0x002abaff in __db_open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#13 0x002a5d15 in __db_open_pp () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb-4.6.so
#14 0x0080644c in Db::open () from /devel/tfm/external/RH4_32/dbxml/latest/install/lib/libdb_cxx-4.6.so
#15 0x0053ebbe in DbXml::DbWrapper::open (this=0x405bbee0, txn=0x0, type=DB_BTREE, flags=65537, mode=0) at Transaction.hpp:62
#16 0x00549247 in CacheDatabase (this=0x405bbed8, env=0x9c5a848, type=DB_BTREE, compare=0) at CacheDatabase.cpp:28
#17 0x005497e2 in DocDatabase (this=0x405bbed8, env=0x9c5a848, compare=0) at CacheDatabase.cpp:46
#18 0x00584ced in DbXml::Manager::createDocDatabase (this=0x9c5a830, compare=0) at Manager.cpp:694
#19 0x00519467 in DbXml::CacheDatabaseMinderImpl::verify (this=0xfffffdfe, entry=@0x6ac2f790, cid=-514) at CacheDatabaseMinder.hpp:31
#20 0x00519398 in DbXml::CacheDatabaseMinderImpl::findOrAllocate (this=0x6ac5b4f0, cid=1, allocate=true) at CacheDatabaseMinder.cpp:71
#21 0x00518e59 in DbXml::CacheDatabaseMinder::findOrAllocate (this=0x6acd9fa0, mgr=@0x9c5a830, cid=1, allocate=true) at CacheDatabaseMinder.cpp:21
#22 0x0055b12d in LazyDIResults (this=0x6acd9f98, context=0x6acd9fa0, contextItem=0x4979abc0, expr=@0x9ce5de8, txn=0x0, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlManager.hpp:80
#23 0x0052f9cd in DbXml::QueryExpression::execute (this=0x9ce5de8, txn=0x0, contextItem=0x4979abc0, context=@0xbfcb0e04, flags=0) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlQueryContext.hpp:86
#24 0x00565a3a in DbXml::XmlQueryExpression::execute (this=0x0, contextItem=@0xfffffdfe, context=@0xbfcb0e04, flags=4294966782) at /devel/tfm/developers/szobell/berkeley-db-xml/dbxml-2.4.16/dbxml/include/dbxml/XmlValue.hpp:186
#25 0x0805af4b in XmlRecordWithCounts::ExtractQueryString (this=0xbfcb0dd0, select=@0xbfcb0e2c, result=@0xbfcac1d0, qDocument=0xbfcb0e14) at src/XmlRecordWithCounts.cpp:401
#26 0x080585f6 in OdRecord::GetRequiredContent (this=0xbfcb0dd0, name=@0xbfcac1e0, origin=@0xbfcac1d0, dest=@0xbfcac1c0, type=@0xbfcac1b0, dist=@0xbfcac198, totalCount=@0xbfcac194, route=@0xbfcac1a0, qDocument=0x0) at src/OdRecord.cpp:143
#27 0x0804d9c3 in ProcessOd (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20) at src/BuildFdDb.cpp:263
#28 0x0804f4c8 in ProcessOneDest (fpPrivate=0x8e11098, odDb=@0xbfcb0dd0, fdDb=@0xbfcb0d20, dest={static npos = 4294967295, _M_dataplus = {<std::allocator<char>> = {<No data fields>}, Mp = 0x9da758c "LAX"}, static Sempty_rep_storage = {0, 0, 69041, 0}}) at src/BuildFdDb.cpp:464
#29 0x080501cd in main (argc=6, argv=0xbfcb10c4) at src/BuildFdDb.cpp:589
At this time, the program is trying to extract fields out of an XmlDocument that is the result of a query. The program uses a pre-calculated XmlQueryExpression to extract a specific field. This may not be the best way to extract a field from a document, given the apparent overhead of needing a temporary file!
My program queries two database files (OD.dbxml and FD.dbxml.new), and uses the information to add records to the second file. The databases are rather big:
bash-3.2$ ls -l /tmp/*dbxml*
-rw-rw---- 1 zobell users 5233745920 Jul 28 14:42 /tmp/FD.dbxml.new
-rw-rw---- 1 zobell users 6539427840 Jul 13 10:16 /tmp/OD.dbxml
(I keep them in /tmp because everywhere else uses NFS and performance is awful with NFS.)
My environment:
Red Hat Enterprise Linux Client release 5.3 (Tikanga) 32 bit.
Berkeley DB XML 2.4.16, C++ interface.
Disk space should not be an issue:
bash-3.2$ df /tmp /var
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-tmp
28948572 13044384 14409968 48% /tmp
/dev/mapper/VolGroup00-root
144742920 5333544 131938272 4% /
I ran this program about a year ago and did not see this issue. I have made a few changes and linked to the newer version of the XML database since then. Any help is appreciated.

I have more information about this problem.
If I "disable" the routine __os_zerofill() in os_fzero.c, by having it always return (0), I no longer get an exception and my application appears to run smoothly. However, I have not determined what in this routine leads to the exception. And, I have no idea what the short and long term consequences of "disabling" this routine will be....
-Coralie

Unable to create RFQ in ME41 transaction

Similar Messages

Maybe you are looking for