Handling runtime errors
We have an AS3 application made in Flash Builder that I would like to compile such that the script continues to execute after encountering a runtime error.
We made a simple AS3 test movie and compiled it with Flash CS3 and then Flash Builder.
The movie tries to evaluate a variable that does not exist, and then puts a yellow square on the stage.
Here is the core of the code:
if(this["d"] == 1){ } // this line throws a runtime error because d is not declared.
var s:Sprite = new Sprite();
s.graphics.beginFill(0xFFCC00);
s.graphics.drawRect(0,0,200,200);
addChild(s);
In the movie compiled in CS3 (with this code in a frame on the timeline) the runtime error seems to be ignored - and the square appears.
In the movie compiled in FB with this code wrapped in a simple Class, or if this class is used as the document class for a CS3 movie - then the resulting swf throws the runtime error and does not add the sprite to the stage.
Here is the simple Class:
package
import flash.display.MovieClip;
import flash.display.Sprite;
public class ErrorTest extends MovieClip
public function ErrorTest()
if(this["d"] == 1){ } // this line throws a runtime error because d is not declared.
var s:Sprite = new Sprite();
s.graphics.beginFill(0xFFCC00);
s.graphics.drawRect(0,0,200,200);
addChild(s);
Why does it ignore the error when I just publish this code on the timeline?
How can we compile a swf that will emulate this behavior using class files?
Does the timeline code extend a class that ignores runtime errors?
We read this http://livedocs.adobe.com/flex/3/html/help.html?content=11_Handling_er rors_03.html and it seems that the description in the documentation is inaccurate as is pointed out in the comment:
The following statement regarding uncaught exceptions seems to be either inaccurate or misleading:
"At run time, Flash Player ignores, by design, uncaught errors and tries to continue playing if the error doesn't stop the current SWF file"
Script execution does NOT continue when hitting an error - even in a non-debug player. Previous versions of AS/Flash Player used to continue. For the non-debug Player, this is arguably a better approach as it prevents small errors from bringing down an entire block of script.
Our experience confirms this. Is there any way to globally specify that the application should continue on uncaught errors?
We saw this class: http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/fla sh/events/UncaughtErrorEvents.html
It seems to be only available in 10.1 - which is higher than we would like to target.
Thanks Anirudh,
In Flash Builder, try doing
if(this.hasOwnProperty("d") && this["d"] == 1){ }
I was just throwing this error as an example of throwing an error, and not looking to fix it in particular. We have a large and complex application which is used by many people. Unfortunately, some of our users are experiencing runtime errors that are stopping the execution of the script - and we do not know exactly where those are. They may be easy to fix once we can locate them. Unfortunately, we have not been able to reproduce them locally.
If the flash player encounters an error in the constructor of the sprite/movieclip which is the main class, it will not be able to continue. If this error had occurred in an event handler, then you'd be able to continue.
Can you tell us more about the rules of uncaught runtime error handling? For example: when I compile this code - the sprite is not shown on the stage and the second trace is not executed - despite having moved the code to an event handler function.
package
import flash.display.MovieClip;
import flash.display.Sprite;
import flash.events.Event;
import flash.events.TimerEvent;
import flash.utils.Timer;
import org.osmf.events.TimeEvent;
public class ErrorTest extends MovieClip
public function ErrorTest()
var t:Timer = new Timer(100, 1);
t.addEventListener(TimerEvent.TIMER, eventHandler);
t.start();
protected function eventHandler(e:Event):void {
trace("1");
if(this["d"] == 1){}
trace("2");
var s:Sprite = new Sprite();
s.graphics.beginFill(0xFFCC00);
s.graphics.drawRect(0,0,200,200);
addChild(s);
I'd like to publish our application such that it would ignore all run time errors. Are there any compiler or other options to achieve that.
Ideally we'd like to collate the errors such that end users could open a hidden text field and copy the error messages and send them to us.
Similar Messages
-
How can I handle runtime errors in Java
Please some one tell me what are runtime errors and How can I handle them using java code
This is important
Thanks in Advance
Chowdary AKThe java equivalent of function pointers is the one-instance class, as used to pass handlers to swing components, for example. Often an anonymous class is used.
Put your function signature in an interface, and pass an object that implements that interface:
public Class1 {
public interface CallBack {
void myMethod(String arg1);
CallBack callb;
public Class1(CallBack callb) {
this.callb = callb;
callb.myMethod("A string");
class2 {
first = new Class1(new Class1.CallBack() {
public void myMethod(String arg1) {
... do something ... -
Handling runtime errors while recording a script.
When I record a script, I have a couple areas of the target website that throw an exception within the browser of e-Tester ( but not in any normal browser ). It is a runtime error, and complains about an unteriminated string constant. I'm not interested in trying to fix the cause, I just want to deal with the dialog. Here are my questions:
1. I want to first check to see IF the screen is present. It looks like a standard windows error dialog.
2. IF it's present, I then want to select the 'No' button, because I don't want to debug it, I just want to close the dialog and move on.
That's all I want to do. I've attached a screenshot of the windows dialog I want to handle.I'd love to be able to find out what is causing the crash, because then I could log a bug against the web page to have the unterminated string resolved. Any idea of how I could find this? Perhaps looking through the source of the page?
Until I find a way to determine exactly what the problem is with the web page ( sorry, it's proprietary, so I can't post the code up here ), I'm going to write a little app to watch for the box, then close it.
I just need to find a way to call an external app before I click on the web page. How do I call an external app from within e-Tester in such a way that the call is made, and the execution continues as normal? I do NOT want e-Tester to wait for the app to close before continuing. -
How to handle runtime error in PreUUT step when running in Parallel mode
I would like to run Test UUTS in parallel mode, and some actions are done in PreUUT such like read serial number and fixture control.
The process model won't goto PostUUT Step when runtime error occurs in PreUUT step, so i would like to add some actions to check if sequence error in cleanup and go back to setup in PreUUT step, but i find it skip all the actions in setup and main step?
What should i do if i want to go back to run PreUUT again as the first time to run when runtime error occurs?
Or, is there any good way to handle this kind of error withour restart program?
Solved!
Go to Solution.This question does not depend on PreUUT or ParallelModel at all.
First of all:
A Runtime Error is a situation where TestStand encounters a problem which makes further testing either impossible or senseless. So a Runtime Error always indicates a situation where proceeding the test sequence is not recommended.
Nevertheless, there are situation where you want to handle those errors without stopping the execution. A "traditional example" for this is initialising serial/GPIB devices. If the device does not reply, there might be different issues the operator can easily resolve and (if corrected) the sequence can proceed properly. The operators action could be:
- Check if device is switched on
- Check connection between PC and device
So the error state is used to inform the operator about the malfunctioning device and regarding of the actions the operator takes, the execution will either proceed or terminate.
When TestStand encounters a Runtime Error, it initially reacts with displaying a dialog. This behavior can be modified in the Station Options >> Preferences >> On Runtime Error.
Furthermore, you can install callback sequences which are called if an error occurs. Those would be either SequenceFilePostStepRuntimeError or ProcessModelPostStepRuntimeError (depending on the fact if you are changing the process model or simply working with client sequence file callback overrides). These are "normal" sequences you can use in order to get system information, loop on the step or....essentially do whatever you want. If you want to proceed though, you must not forget to reset the error flag.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it. -
Handle Runtime error: TSV_TNEW_PAGE_ALLOC_FAILED
Hi,
In my programme, some times I end up with handling of lots of data in internal table. And this results in a dump.
Category ABAP Server Resource Shortage
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Short text
No more memory available to extend an internal table.
I read few threads where they suggested to increase the internal memory of ths system. This is beyond my scope!
Is there anyway I can catch this exception and stop the programme from executing further?
Thanks in advance!
Cheers
KiranHello Kiran,
TSV_TNEW_PAGE_ALLOC_FAILED is a not catchable error. It happens if a program exceeds the system boundaries, typically ~2 GB. Requesting so much memory is a strong indication for a flaw in the archtecture.
Anyway these kind of errors require a change in the program or in the arguments given to them. In newer releases you may try S_MEMORY_INSPECTOR to analyse the endless need of memory. In older releases watch out for hughe internal tables in the ST22 dump.
Regards
Klaus -
Currently when there is runtime error
eg illegal argument exception, java npe error
The errors are written onto weblogic log.
How can we suppress the errors from appearing on the weblogic log but write to a different log?
Thanksc.kan,
You can set up the logger to log to a separate file if you like. http://blogs.oracle.com/groundside/entry/adventures_in_logging_index would be some interesting reading, followed by the WLS logging docs ([url http://download.oracle.com/docs/cd/E21764_01/web.1111/e13739/toc.htm]this, for a start).
john -
Enter name of file:
Exception in thread "main" java.io.IOException: The handle is invalid
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at crapo.main(crapo.java:15)
Tool completed with exit code 1
import java.io.*;
public class crapo{
public static void main(String[] args) throws IOException {
BufferedReader keys = new BufferedReader(
new InputStreamReader( System.in ));
System.out.println("Enter name of file: ");
String fileName = keys.readLine();
}Maybe I just figured something out:
First of all, most of the Functions, that cause the Error, are in Timer-Callbacks (at this state of development, ALL of them)
So I just added a Test-Function in a normal Button-Callback, which contains a "GetCtrlArrayItem"-Function, and this specific Line does NOT cause an Error... (Or at least it does not occur in the Error-List, when clicking "continue" in debugging-mode). Somehow the Timer-Callbacks seem to be called, when closing the Application...
BUT: this happens when I don't do anything in the Application, and the all Timers are Disabled, until some Buttons are pushed (so when I close the application right after opening it, they still should be disabled)
@ Wolfgang:
After discarding I do not want to use one of the handles, or at least I'm not doing that purposely
@ Roberto:
Actually I am only discaring the MainPanel-Handle in the Main.uir (and one other Panel, but the error occurred before implementing that other panel). Do all Handles (PanelHandles as well as ControlArrayHandles, TabPageHandles and so on) need to be discarded?
And no, I did not check the Variable Window, I was not aware of this possibility, I will try to figure that out. -
How To Handle Labview Runtime Error in Teststand
Hi,
I am working NI-CAN device to transfer CAN frames through the VI's using TestStand. Before transmission took place, we need to choose for the port, in case if the port is selected wrong, Labview take it as a runtime error and handles accordingly while teststand keeps on running i.e. if I have 7 steps that are calling that VI, the runtime error from the labview will appear that many times also. Is there any way to handle labview runtime errors directly through TestStand. I have a sequence that will take care of the Runtime Errors in my sequence file.
Please help me soon.
Thanks in Advance,
VivekHi Vivek,
If the LabVIEW VI is handling the error, then what you probably want to do is make the VI have an Error Out output terminal. You'd have to wire the appropriate error out wires to the terminal of course.
This way, when you call the VI from TestStand, you can check the value of the Error Out and decide in TestStand how to handle it (skip the remaining steps, popup a message, etc).
Jervin Justin
NI TestStand Product Manager -
Why am I getting so many runtime errors? (IO handling)
Here is what I am trying to do. The user of my GUI types a name in a text field an then presses a button. Then a file is created with that name, and with whatever he typed in the text field in it. Note: the extension is not typed!
But for some reason I get so many runtime errors in the prompt. I would list them except I can't see them all. Here is the important part of my code. Add is the button the user presses to add the file name; and it is located in the an actionEvent method. Here is the cod:
else if(e.getSource() == add){
String s;
try{
firstNameS = field.getText();
FileWriter Write = new FileWriter(s+".txt");
BufferedWriter write2 = new BufferedWriter(Write);
write2.write(firstNameS);
write2.flush();
Write.flush();
write2.close();
Write.close();
} catch(IOException exeption) {}
}Could someone please tell me what i am doing wrong? This code compiles perfectly.
Thanks.
VirumThanks abnormal! I have the full exception. I have no idea what it means but here it is:
Exception occurred during event dispatching:
java.lang.NullPointerException
at AddressBook.actionPerformed(AddressBook.java:236)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1450)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1504)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:378)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:250)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:216)
at java.awt.Component.processMouseEvent(Component.java:3715)
at java.awt.Component.processEvent(Component.java:3544)
at java.awt.Container.processEvent(Container.java:1164)
at java.awt.Component.dispatchEventImpl(Component.java:2593)
at java.awt.Container.dispatchEventImpl(Container.java:1213)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:2451)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:2216)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:2125)
at java.awt.Container.dispatchEventImpl(Container.java:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:2497)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:339)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)Does any one know what this means? -
WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"
Hi Experts,
While deleting a sales order giving run time error. PFB runtime error details.
If you know any OSS message, please let m know. I tried, but there is no luck.
Short text
Screen: Illegal message
What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the current
screen.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
The program attempted to issue a " " message during "Exit Command" processing.
This is an illegal operation.
The program was terminated.
Screen name.............. "SAPMV45A"
Screen number............ 4001
How to correct the error
The program must be modified to correct the error.
The modification must be made in "Exit Command" processing.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
Source Code Extract
Line SourceCde
1 *---------------------------------------------------------------------*
2 * FORM YVBEP_LESEN *
3 *---------------------------------------------------------------------*
4 * Lesen der Tabelle YVBEP (nicht sortiert) *
5 *---------------------------------------------------------------------*
6 FORM YVBEP_LESEN USING US_POSNR
7 US_ETENR
8 CHANGING CH_TABIX.
9
10 YVBEP = SPACE.
11 YVBEP-MANDT = VBAK-MANDT.
12 YVBEP-VBELN = VBAK-VBELN.
13 YVBEP-POSNR = US_POSNR.
14 YVBEP-ETENR = US_ETENR.
15 READ TABLE YVBEP.
16 IF SY-SUBRC > 0.
17 MESSAGE E506 WITH US_POSNR US_ETENR.
18 ENDIF.
>>>>> CH_TABIX = SY-TABIX.
20
21 ENDFORM.
Could you please help on this issue.
Thanks
SrinuHi Srinu,
it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
If only a single order causes this issue, maybe something was wrong during an update.
If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
Regards,
Klaus -
Portal runtime error while selecting page layout in WPC editor
Hello,
in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
The logfile shows the following :
#1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
[EXCEPTION]
#1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
usr
sap
EPD
JC00
j2ee
cluster
server0
apps
sap.com
irj
servlet_jsp
irj
root
WEB-INF
portal
portalapps
com.sap.netweaver.bc.util
lib
bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
(source unavailable)
1 error
I have the same by clicking on "check assignments"
Any help ?
ThanksHello Jego.
We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
Best regards,
Aliaksandr Zhukau -
Runtime Error in Portal Application
Can any body help me in resolving the following runtime error in portal application, (Netweaver Version : 7.0)
Full Message Text
03:21_21/09/11_0002_6275851
[EXCEPTION]
java.lang.NoClassDefFoundError: org.apache.commons.httpclient.methods.RequestEntity
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:69)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:131)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:152)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:271)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:316)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:387)
at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:488)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.ClassNotFoundException: org.apache.commons.httpclient.methods.RequestEntity
Found in negative cacheHi,
this exception seems caused by a missing interface org.apache.commons.httpclient.methods.RequestEntity. Please the following ones:
http://www.jarfinder.com/index.php/java/info/org.apache.commons.httpclient.methods.RequestEntity
Br,
Javier -
HI all.....
please look at this runtime error...... help me to solve this....
Table name:- ZRDSSTOCK.
Data class:- APPL1.
Size category:- 5.
Buffering not allowed .
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 26.11.2007 at 12:38:44
An SQL error occurred when accessing a table.
What happened?
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 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 "SAVE_DATA"
"(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:
How to correct the error
The exception must either be prevented, caught within the procedure "SAVE_DATA"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-01654: unable to extend index
SAPPRD.ZRDSSTOCK~0 by 128 in tablespace PSAPPRDUSR"
Internal call code.........: "[RSQL/INSR/ZRDSSTOCK ]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"YKSD010 " or "YKSD010 "
"SAVE_DATA"
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.............. "620"
Application server....... "venus"
Network address.......... "192.168.1.151"
Operating system......... "SunOS"
Release.................. "5.9"
Hardware type............ "sun4u"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "venus"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "en_US"
SAP kernel............... "620"
Created on............... "Nov 17 2004 01:43:57"
Created in............... "SunOS 5.8 Generic_108528-07 sun4u"
Database version......... "OCI_817_64 "
Patch level.............. "1732"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.."
SAP database version..... "620"
Operating system......... "SunOS 5.8, SunOS 5.9"
User, transaction...
Client.............. 400
User................ "MMUSER"
Language key........ "E"
Transaction......... "ZRDSEN "
Program............. "YKSD010 "
Screen.............. "YKSD010 0100"
Screen line......... 41
Information on where termination occurred
The termination occurred in the ABAP program "YKSD010 " in "SAVE_DATA".
The main program was "YKSD010 ".
The termination occurred in line 685 of the source code of the (Include)
program "YKSD010 "
of the source code of program "YKSD010 " (when calling the editor 6850).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "SAVE_DATA" "(FORM)" but was not handled locally, not declared in the
RAISING clause of the procedure.
The procedure is in the program "YKSD010 ". Its source code starts in line 662
of the (Include) program "YKSD010 ".
Source code extract
006550
006560
006570 *&----
006580 *& Form save_data
006590 *&----
006600 * text
006610 *----
006620 FORM SAVE_DATA.
006630 data: begin of lv_test occurs 0,
006640 werks type s886-werks,
006650 pkunag type s886-pkunag,
006660 end of lv_test.
006670 LOOP AT INDT1.
006680
006690 INDT1-WERKS = WERKS.
006700 INDT1-DAT1 = VDFRM.
006710 INDT1-DAT2 = VLDTO.
006720 * indt1-kunnr = kunnr.
006730
006740
006750 MODIFY INDT1.
006760
006770 ENDLOOP.
006780 *if indt1 is not initial.
006790 *select pkunag werks from s886 into corresponding fields of table
006800 *lv_test where pkunag = indt1-rdscode and werks = indt1-werks.
006810 *if sy-subrc = 0.
006820
006830 &----
changed by prajwal.k----
006840
INSERT ZRDSSTOCK FROM TABLE INDT1 ACCEPTING DUPLICATE KEYS.
006860 *loop at indt1.
006870 * INSERT ZRDSSTOCK FROM INDT1.
006880 *if sy-subrc <> 0.
006890 *message w013 WITH INDT1-MATNR.
006900 *endif.
006910 *endloop.
006920
006930
006940 &----
end----
006950 * MESSAGE I004.
006960 *else.
006970 *message 'Please chek the RDS Code' type 'W'.
006980 *endif.
006990 *endif.
007000 *endif.
007010 LOOP AT INDT1.
007020
007030 AT LAST.
007040
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 0 SY-DBCNT 1
SY-FDPOS 40 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY YINDENT
SY-UCOMM OPT1 SY-TITLE RDS Stock Entry Screen
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
3 FORM SAVE_DATA
YKSD010
YKSD010 685
2 MODULE (PAI) YINDENT_IN
YKSD010
YKSD010 233
1 EVENT START-OF-SELECTION
YKSD010
YKSD010 181
Chosen variables
3 FORM SAVE_DATA
YKSD010
YKSD010 685
INDT1[] Table IT_121[1738x121]
FFFF94120000000000020007000C00070000FFFF
FFFE7BD00000000000060009006A00090000FFFF
... + 40
00000005012B0000
40000058004C0000
INDT1 TNV0024 2007090120070930CH01C0100300
5453333222333333333333333344334333333322
4E60024000200709012007093038013010030000
... + 40 CAR####`#################`######
2222222244500006000000000000000006000000
0000000031200000C00000C00000C00000C00000
... + 80 #
0222222222222222222222222222222222222222
C000000000000000000000000000000000000000
... + 120
2
0
SY ###############Ê########################
000000000000000C000000000000000000000000
000000000000006A000000000000000000000000
... + 40 #######(###############################y
0000000200000000000000000000000000000007
0001000800010000000100000000000000000009
... + 80 ########################################
0000000000000000000900000000000000000000
0000000000000000001000000000000000000000
... + 120 ########################################
0000000000000000000000000000000000010009
00000000000000000000000000000000000B0000
... + 160 #######ÿ######MX C############# E0 0
0000000F00000045240000000000000222432223
0000000F000000D8030010000C0000C000500000
... + 200 100 ####__S 400
3332222222220000555222222222222222223332
1000000000000000FF3000000000000000004000
... + 240 00
222223322222222
000000000000000
MODIFY-CX ########MODIFY
0000000044444522222222222222222222222222
00020000DF496900000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 0101####
222222222222222222223333000022222222
000000000000000000000101000100000000
<%_L005>-SEL ???
OK_CODE SAVE
5454222222222222222222222222222222222222
3165000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
<%_TABLE_ZRDSSTOCK> ???
%_DUMMY$$
2222
0000
VLDTO 20070930
33333333
20070930
SY-REPID YKSD010
5454333222222222222222222222222222222222
9B34010000000000000000000000000000000000
SY-MSGID
22222222222222222222
00000000000000000000
SPACE
2
0
SY-MSGNO 000
333
000
2 MODULE (PAI) YINDENT_IN
YKSD010
YKSD010 233
SY-UCOMM OPT1
4553222222222222222222222222222222222222
F041000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
COUNT ########
00000000
0000000C
%_VLDTO_%_APP_% Valid To
566662562222222222222222222222
61C9404F0000000000000000000000
%_WERKS_%_APP_% Plant
566672222222222222222222222222
0C1E40000000000000000000000000
%_VDFRM_%_APP_% Valid From
566662476622222222222222222222
61C94062FD00000000000000000000
%B001000_BLOCK_1000 Enter Values
4676725667672222222222222222222222222222
5E452061C5530000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222
000
VALUE
222222222222222222
000000000000000000
SYST-REPID YKSD010
5454333222222222222222222222222222222222
9B34010000000000000000000000000000000000
SY-SUBRC 0
0000
0000
A 1
3
1
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
VARI
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40 ####00000000000000
2222222222222222222200003333333333333322
0000000000000000000000000000000000000000
... + 80 ####################################
2222000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 120 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 160 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 200 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 240 ###############
000000000000000
000000000000000
INDT[] Table IT_28[0x121]
FFFF958EFFFF940200010001000000070000FFFF
FFFE7B70FFFE74800007000C000000090000FFFF
... + 40
0000000E012B0000
40000048004C4000
INDT 0000000000000000
2222222222333333333333333322222222222222
0000000000000000000000000000000000000000
... + 40 #############################
2222222222200000000000000000000000000000
0000000000000000C00000C00000C00000C00000
... + 80 #
0222222222222222222222222222222222222222
C000000000000000000000000000000000000000
... + 120
2
0
1 EVENT START-OF-SELECTION
YKSD010
YKSD010 181
No dump information available
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "HandleRsqlErrors" of the SAP
Basis System, specifically in line 760 of the module
"//bas/620/src/krn/runt/absapsql.c#40".
The internal operation just processed is "SQLS".
The internal session was started at 20071126123440.
Internal call code.........: "[RSQL/INSR/ZRDSSTOCK ]"
Active calls in SAP kernel
DoStack2 ( 0xffffffff7fff6490, 0xffffffff7fff6370, 0x0,0x203ac00, >
> 0x100362d98, 0xffffffff7fff5b71 ), at 0x100362d98
CTrcStack2 ( 0x103519930, 0x0, 0x10008, 0x1018dc400, 0x0, 0x1 ), at 0x10036296c
__1cQrabax_CStackSave6F_v_ ( 0x1, 0x28e8400, 0x100000000, >
> 0x1028e8400, 0x0, 0x1 ), at 0x1007cccac
ab_rabax ( 0x1020c9a88, 0x4, 0x1018db3b6, 0x10355210c, 0x2000000, >
> 0x8550c017 ), at 0x1007c0e68
__1cKab_rsqlerr6Fpkcip0pnLRS_HEADER94_2pv_v_ ( 0x1018c7110, >
> 0x2f8, 0x1020c6a14, 0xffffffff7fff6cd8, 0x1018c7121, 0x0 ), at 0x10071aae8
__1cQHandleRsqlErrors6FnJRsqlError_nJCloseMode__v_ ( 0x8, >
> 0xfffffffe97470708, 0x6c8000, 0x100000000, 0x0, 0x1 ), at 0x1006c8764
__1cPSqlsExecuteCall6FCpnLDynCallInfo__v_ ( 0x100000000, >
> 0x6a, 0x20c6800, 0xe8, 0x1d, 0x1 ), at 0x1006ddd24
__1cIab_jsqls6F_v_ ( 0xfffffffe4a309e58, 0xfffffffe974707b0, >
> 0x1028c4f00, 0xe8, 0x1d, 0x100000000 ), at 0x1006c91e8
__1cIab_extri6F_i_ ( 0x103503ff8, 0xfffffffe4a309e44, 0x8a, >
> 0x0, 0x1, 0x100000000 ), at 0x1005364e8
__1cJab_xevent6Fpkc_i_ ( 0x0, 0x3416000, 0xfffffffe4c17f808, >
> 0x0, 0x1d6f, 0xfffffffe975420d8 ), at 0x10068df84
ab_dstep ( 0xd, 0xd, 0x46, 0x1, 0x103521a74, 0x103521800 ), at 0x1007d619c
dynpmcal ( 0xfffffffe9747e8c8, 0x10203a800, 0x1037d8110, >
> 0x101d2a000, 0x2660, 0x100000000 ), at 0x1003e2274
dynppai0 ( 0xfffffffe9747e8c8, 0x0, 0x0, 0xfffffffe97482c3f, >
> 0x0, 0x5 ), at 0x1003df680
dynprctl ( 0x0, 0xfffffffe9747e8c8, 0x203c400, 0x1024d0cf8, >
> 0x1020291c0, 0x1024d0c58 ), at 0x1003dd258
dynpen00 ( 0x0, 0x203c400, 0x1, 0x100000000, 0x203a800, >
> 0x10203a800 ), at 0x1003d9c24
TskhLoop ( 0x2, 0x2, 0x10203a8c0, 0x8, 0x0, 0x1 ), at 0x1001d2b18
tskhstart ( 0x100000000, 0x2028000, 0x102028000, 0x2028000, >
> 0x1, 0x4 ), at 0x1001c5ae0
DpMain ( 0x249a000, 0x26e3400, 0x10249a000, 0xffffffff7c755f44, >
> 0x0, 0x1 ), at 0x100111e60
List of ABAP programs affected
Type
Program
Gen. Date Time
Load Size
Prg
YKSD010
26.11.2007 09:44:15
55296
Prg
SAPMSSY0
18.12.2004 11:31:22
62464
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Prg
RSDBRUNT
18.12.2004 11:32:05
220160
Typ
RSSCR
. . : m:15
4096
Prg
RSDBSPBL
13.12.2002 12:24:35
58368
Prg
SAPDB__S
14.02.2002 14:22:47
16384
Typ
VARID
12.05.1997 16:51:30
4096
Prg
%_CSYDB0
14.02.2002 14:22:46
28672
Prg
RSDBSPVA
18.12.2004 11:18:02
108544
Typ
RSVAMEMKEY
07.05.1997 13:07:49
2048
Prg
RSDBSPMC
05.06.2002 17:09:26
66560
Typ
DDSHDESCR
03.09.1997 03:05:16
3072
Typ
SPPARAMS
07.05.1997 13:10:38
1024
Prg
SAPLICON
18.12.2004 09:37:13
23552
Prg
%_CICON
14.02.2002 14:22:46
57344
Prg
SAPLSABE
14.02.2002 14:22:47
11264
Prg
SAPLSECU
18.12.2004 11:16:36
63488
Prg
SAPLDSYA
14.02.2002 14:22:47
38912
Prg
SAPFSDS1
13.12.2002 12:14:34
46080
Typ
TDCLD
02.11.1998 09:51:35
4096
Prg
SAPLSDOD
18.12.2004 11:31:31
38912
Typ
DOKIL
12.05.1997 16:46:17
2048
Prg
SAPCNVE
14.02.2002 14:22:47
6144
Prg
SAPLLANG
14.02.2002 14:22:47
8192
Typ
T002
14.02.1998 10:24:58
2048
Typ
RSEXFCODE
13.08.1997 12:52:57
1024
Typ
RSPARINT
10.04.1995 09:58:38
1024
Prg
SAPLSCNT
14.02.2002 14:22:47
22528
Prg
SAPLSVSM
13.12.2002 12:16:46
22528
Prg
SAPLSGUI
13.12.2002 12:27:47
29696
Prg
SAPLSTTM
18.12.2004 11:36:10
73728
Prg
SAPLSBDC
13.12.2002 12:13:58
37888
Prg
CL_DATAPROVIDER===============CP
14.02.2002 14:22:46
38912
Prg
%_CCNTL
14.02.2002 14:22:46
13312
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSTUP
18.12.2004 09:34:15
62464
Prg
SAPLCNDP
18.12.2004 11:35:59
153600
Prg
SAPFGUICNTL
13.12.2002 12:30:03
20480
Prg
SAPLOLEA
18.12.2004 11:30:56
76800
Prg
SAPLSFES
18.12.2004 11:35:59
162816
Prg
SAPLSPLUGIN
14.02.2002 14:22:48
6144
Prg
SAPLGRFC
14.02.2002 14:22:47
13312
Prg
SAPSHDTV
19.06.2003 19:25:09
27648
Typ
SHDSTU
14.12.1998 23:15:34
2048
Typ
SHDSTCIU
14.12.1998 23:15:34
1024
Typ
SSCRTEXTS
03.09.1997 03:12:33
2048
Typ
SSCRFIELDS
13.05.1997 12:54:26
3072
Prg
CL_GUI_PROPS_CONSUMER=========CP
13.12.2002 12:11:27
27648
Prg
SAPLTHFB
18.12.2004 11:36:24
293888
Prg
CL_DYNAMIC_GUI_EXTENSIONS=====CP
14.02.2002 14:22:46
33792
Prg
CL_GUI_DATAMANAGER============CP
18.12.2004 09:49:48
69632
Prg
CL_ABAP_CHAR_UTILITIES========CP
13.12.2002 12:13:57
11264
Typ
MARD
15.11.2000 17:38:50
8192
Prg
RSDBSPVD
18.12.2004 09:35:18
73728
Typ
RVARI
30.03.1998 09:40:50
3072
Typ
RSVARIVDAT
04.04.1995 16:12:54
2048
Typ
ZLOCKPGM
11.02.2006 09:28:47
2048
Prg
%_CCXTAB
14.02.2002 14:22:46
6144
Typ
ZRDSSTOCK
26.11.2007 09:44:15
3072
Prg
SAPLGRAP
18.12.2004 11:36:25
350208
Prg
CL_GUI_FRONTEND_SERVICES======CP
18.12.2004 11:36:27
84992
Prg
CL_GUI_OBJECT=================CP
13.12.2002 12:13:57
348160
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
CL_GUI_CFW====================CP
05.06.2002 17:02:46
150528
Typ
TOLE
29.07.1998 19:56:01
2048
Prg
%_COLE2
14.02.2002 14:22:46
8192
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
SWCBCONT
15.11.2000 17:55:11
2048
Prg
SAPLCNTL
14.02.2002 14:22:47
270336
Prg
SAPLCNTH
14.02.2002 14:22:47
22528
Typ
FILE_TABLE
05.01.1999 10:23:11
1024
Prg
SAPLURFC
18.12.2004 10:30:34
16384
Prg
SAPLSRFC
18.12.2004 11:36:45
34816
Prg
SAPLSYST
14.02.2002 14:22:48
29696
Prg
SAPMSSY1
14.02.2002 14:22:48
18432
Typ
ARFCDATA
04.04.1995 15:40:32
3072
Typ
RFC_FIELDS
20.08.1998 10:56:34
2048
Typ
DPPROPS
09.07.1997 23:53:23
1024
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLCNT0
14.02.2002 14:22:47
30720
Typ
OLE_PA
04.04.1995 16:02:19
2048
Typ
ARFCRDATA
09.11.2000 14:04:16
4096
Typ
OLE_VERBS
04.04.1995 16:02:20
2048
Prg
CL_ABAP_TYPEDESCR=============CP
18.12.2004 10:20:56
22528
Prg
CL_ABAP_ELEMDESCR=============CP
18.12.2004 10:20:34
18432
Prg
CL_ABAP_DATADESCR=============CP
18.12.2004 10:20:34
14336
Prg
CL_ABAP_REFDESCR==============CP
18.12.2004 10:20:56
16384
Prg
CL_ABAP_STRUCTDESCR===========CP
18.12.2004 10:20:56
19456
Prg
CL_ABAP_COMPLEXDESCR==========CP
18.12.2004 10:20:34
13312
Prg
CL_ABAP_TABLEDESCR============CP
18.12.2004 10:20:56
17408
Prg
CL_ABAP_CLASSDESCR============CP
18.12.2004 10:20:56
23552
Prg
CL_ABAP_OBJECTDESCR===========CP
18.12.2004 10:20:56
26624
Prg
CL_ABAP_INTFDESCR=============CP
18.12.2004 10:20:34
19456
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
CL_ABAP_SOFT_REFERENCE========CP
29.03.2001 16:42:12
7168
Prg
CL_ABAP_REFERENCE=============CP
14.02.2002 14:22:46
6144
Prg
CL_IXML=======================CP
13.12.2002 12:12:08
210944
Prg
CL_IXML_UNKNOWN===============CP
13.12.2002 12:12:08
9216
Prg
SAPFGUICNTL_CFW
14.02.2002 14:22:47
12288
Prg
SAPLSPO1
18.12.2004 11:37:25
43008
Prg
SAPLCSTR
18.12.2004 11:21:47
63488
Typ
MAKT
28.08.1997 08:52:19
2048
Typ
KNA1
18.12.2004 14:35:36
22528
Typ
MARA
02.07.2002 16:31:17
19456
Typ
ZRDSSTOCK
26.11.2007 09:44:15
3072
Prg
CX_SY_OPEN_SQL_DB=============CP
14.02.2002 14:22:47
9216
Typ
SCX_SRCPOS
09.11.2000 14:12:15
1024
Prg
CX_SY_OPEN_SQL_ERROR==========CP
14.02.2002 14:22:47
8192
Prg
CX_SY_SQL_ERROR===============CP
14.02.2002 14:22:47
8192
Prg
CX_DYNAMIC_CHECK==============CP
14.02.2002 14:22:47
8192
Prg
CX_ROOT=======================CP
14.02.2002 14:22:47
9216
Prg
CX_NO_CHECK===================CP
14.02.2002 14:22:47
8192
Prg
CX_SY_NO_HANDLER==============CP
14.02.2002 14:22:47
8192
Typ
SYST
04.12.2000 14:54:51
24576
List of internal tables
PROGRAM=YKSD010DATA=INDT1[]
TABH+ 0(20) = FFFFFFFE974B1D20000000000000000000000026
TABH+ 20(20) = 00000079000006CA0000007900000000FFFFFFFF
TABH+ 40(16) = 0400000000000558001024BC00000000
store = 0xFFFFFFFE974B1D20
ext1 = 0x0000000000000000
id = 38 (0x00000026)
label = 121 (0x00000079)
fill = 1738 (0x000006CA)
leng = 121 (0x00000079)
lopc = 0 (0x00000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000015
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 7 (cmpManyEq)
occu0 = 1
collHash = 0
lock = 0
shrd = 0
visited = 0
unShareable = 0
wasShared = 0
iterIsValid = 0
isShareable = 0
>>>>> Shareable Table Header Data <<<<<
tabi = 0xFFFFFFFE974B1468
pghook = 0xFFFFFFFE975BCBF0
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2480 (0x000009B0)
lineAlloc = 1840 (0x00000730)
store_id = 20 (0x00000014)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
PROGRAM=YKSD010DATA=INDT[]
TABH+ 0(20) = FFFFFFFE975B87E0FFFFFFFE9744082000000017
TABH+ 20(20) = 0000001C000000000000007900000000FFFFFFFF
TABH+ 40(16) = 04000000000004E8001024BC04000000
store = 0xFFFFFFFE975B87E0
ext1 = 0xFFFFFFFE97440820
id = 23 (0x00000017)
label = 28 (0x0000001C)
fill = 0 (0x00000000)
leng = 121 (0x00000079)
lopc = 0 (0x00000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000013
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 7 (cmpManyEq)
occu0 = 1
collHash = 0
lock = 0
shrd = 0
visited = 0
unShareable = 0
wasShared = 0
iterIsValid = 0
isShareable = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0xFFFFFFFE975172E8
pghook = 0xFFFFFFFE975BCCB8
idxPtr = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 2480 (0x000009B0)
lineAlloc = 176 (0x000000B0)
store_id = 145 (0x00000091)
>>>>> 1st level extension part <<<<<
regHook = 0x0000000000000000
hsdir = 0x0000000000000000
ext2 = 0xFFFFFFFE974596A8
>>>>> 2nd level extension part <<<<<
tabhBack = 0xFFFFFFFE974A6B68
delta_head = 0000000000000000000000000000000000000000000000000000000000000000
Directory of Application Tables
Program
Name................ Contents....1........2........3........4........5....+....
YKSD010
SYST |00000000000000x06Ê000000000000
VARI |
T006A | |
SSCRFIELDS |
SSCRTEXTS |
RSDBRUNT
VARID |
SAPLICON
ICONT |
SAPFSDS1
TDCLD |RE DOKU 8R XX XXLIMUDOKUX x1E0XR3TRPROGX |
SAPLSDOD
DOKIL |
SAPLLANG
T002 |ES1EN|
SAPLOLEA
TOLE |SAP.DATAPROVIDER.1 {799104C5-04C5-11D0-
SAPSHDTV
SHDSTU | |
SHDSTCIU | |
CL_GUI_PROPS_CONSUMER=========CP
EUDB |%C0009900047492F0EC1BC16DDE1000000C0A80197 0000
CL_GUI_FRONTEND_SERVICES======CP
EUDB |FE0009900047492F0EC1BC16DDE1000000C0A80197 0000
Directory of Application Tables (Administrative Information)
Program
Name.......................... Time.......... Length...
CL_GUI_FRONTEND_SERVICES======CP
SYST 20010612125650 00002404
VARI 00002972
T006A 00000056
SSCRFIELDS 20000323224119 00000854
SSCRTEXTS 00000371
RSDBRUNT
VARID 00000132
SAPLICON
ICONT 00000065
SAPFSDS1
TDCLD 00000050
SAPLSDOD
DOKIL 00000076
SAPLLANG
T002 00000005
SAPLOLEA
TOLE 00000197
SAPSHDTV
SHDSTU 00000053
SHDSTCIU 00000050
CL_GUI_PROPS_CONSUMER=========CP
EUDB 00003940
CL_GUI_FRONTEND_SERVICES======CP
EUDB 00003940
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
YKSD010 667 LOOP AT INDT1.
1029 LOOP 05 36 37
1033 BRAN 05 Branch to 1043
YKSD010 669 INDT1-WERKS = WERKS.
1034 mvqk 04 178 946
YKSD010 670 INDT1-DAT1 = VDFRM.
1036 mvqk 08 162 982
YKSD010 671 INDT1-DAT2 = VLDTO.
1038 mvqk 08 170 1022
YKSD010 675 MODIFY INDT1.
1040 TMOD 04 36 37
YKSD010 677 ENDLOOP.
1042 BRAX 01 Branch to 1029
YKSD010 685 INSERT ZRDSSTOCK FROM TABLE IN
1043 SQLS 0B
1044 SQLS 00 107
1045 PAR1 00 131
1046 SQLS 39 1
1047 SQLS 39 37
>>>>> SQLS 1D 36
YKSD010 701 LOOP AT INDT1.
1049 LOOP 03 79 36 37
1053 LOOP 05 36 37
1057 BRAN 05 Branch to 1111
YKSD010 703 AT LAST.
1058 CNTL 04
1062 BRAN 03 Branch to 1080
YKSD010 705 MESSAGE I004.
1063 CATC 08
1064 MOVL 00 2 58 21
End of runtime analysis
Regards
Prajwal.KRefer Amit's reply -
Exception occurred which is assigned to the class 'CX_SY_OPEN_SQL_DB',
Regards,
Amit
Reward all helpful replies. -
Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC 018 500 AMRUKV BY O Deadlock occurred
10:41:53 BTC 018 500 AMRUKV BY 4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC 018 500 AMRUKV BY 0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC 018 500 AMRUKV AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC 018 500 AMRUKV AB 1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC 018 500 AMRUKV D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Date and Time 18.08.2008 10:41:54
Short text
SQL error in the database when accessing a table.
What happened?
The database system detected a deadlock and avoided it by rolling back
your transaction.
What can you do?
If possible (and necessary), repeat the last database transaction in the
hope that locking the object will not result in another deadlock.
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in procedure "WRITE_ICFACT" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The database system recognized that your last operation on the database
would have led to a deadlock.
Therefore, your transaction was rolled back
to avoid this.
ORACLE always terminates any transaction that would result in deadlock.
The other transactions involved in this potential deadlock
are not affected by the termination.
How to correct the error
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
"WRITE_ICFACT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.THi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep -
Hi guru's,
I have a genric data source with function module which feeds data to a genric ods in bw.
But at time of data upload i see quality status in manage of ods green saying (0 of 0 records extracted) but it asks me to check dump in st22 which is as follows
Runtime Errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 30.01.2008 at 10:41:31
An SQL error occurred when accessing a table.
What happened?
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 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
"STORAGE_LOC_GET" "(METHOD)"
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:
How to correct the error
The exception must either be prevented, caught within the procedure
"STORAGE_LOC_GET"
"(METHOD)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-04030: out of process memory when trying to
allocate 1332 bytes (callheap,qkkele)"
Internal call code.........: "[RSQL/READ/T001L ]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"SAPLMIGO" or "########################################"
"STORAGE_LOC_GET"
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.............. "620"
Application server....... "TOGR3PRD1"
Network address.......... "10.1.9.9"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "TOGR3PRD2"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPPRD"
Character set............ "Thai_Thailand.874"
SAP kernel............... "640"
Created on............... "Sep 19 2005 00:05:54"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "91"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 900
User................ 0060302
Language key........ "E"
Transaction......... "MIGO "
Program............. "SAPLMIGO"
Screen.............. "SAPLMIGO 0001"
Screen line......... 15
Information on where terminated
The termination occurred in the ABAP program "SAPLMIGO" in "STORAGE_LOC_GET".
The main program was "SAPLMIGO ".
The termination occurred in line 0 of the source code of the (Include)
program "########################################"
of the source code of program "########################################" (when
calling the editor 00).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "STORAGE_LOC_GET" "(METHOD)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "SAPLMIGO ". Its source code starts in line 158
of the (Include) program "LMIGOBU2 ".
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 4 SY-INDEX 1
SY-TABIX 0 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 1 SY-LINNO 1
SY-COLNO 1 SY-PFKEY MIGO_STATUS
SY-UCOMM MIGO_OK_TAKE_VALUE
SY-TITLE Goods Issue Others - 0060302 หน.แผนกและจนท.คลังสินค้า,คล
SY-MSGTY E SY-MSGID MICK
SY-MSGNO 004 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
7 METHOD STORAGE_LOC_GET
SAPLMIGO
LMIGOBU2 173
LCL_MIGO_BUFFER
6 METHOD LINE_CHECK
SAPLMIGO
LMIGOKL4 217
LCL_MIGO_KERNEL
5 METHOD LINE_MODIFY
SAPLMIGO
LMIGOKL1 123
LCL_MIGO_KERNEL
4 METHOD VALUECOPY
SAPLMIGO
LMIGOTV3 370
LCL_MIGO_TABLEVIEW
3 METHOD LIF_MIGO_FRAME~OKCODE_HANDLER
SAPLMIGO
LMIGOTV2 174
LCL_MIGO_TABLEVIEW
2 METHOD OKCODE_DISPATCH
SAPLMIGO
LMIGOFR2 171
LCL_MIGO_FRAME
1 MODULE (PAI) PAI_OKCODE_DISPATCH
SAPLMIGO
LMIGOPAI 11
Chosen variables
7 METHOD STORAGE_LOC_GET
SAPLMIGO
LMIGOBU2 173
I_PLANT
2222
0000
I_STORAGE_LOC 2031
3333
2031
E_STORAGE_LOC
222222222222222222
000000000000000000
%_FUN*TV_GOSPLIT <initial>
<initial>
<initial>
GOITEM-KZVBR
2
0
<%_TABLE_T001L> ???
%_SPACE
2
0
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SYST-REPID SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
<%_TABLE_TQSS1> ???
SY-REPID SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
%_DUMMY$$
2222
0000
GODYNPRO-DETAIL_ZEILE 0000
3333
0000
LCL_MIGO_GLOBALS=>KERNEL->S_CO WA
54
71
LS_T001L
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222
00000000000000000000000000000
OREF_DETAIL_MATERIAL
SY-SUBRC 4
0000
4000
GOITEM_TV 0017
3333222222222222222222222222222222222222
0017000000000000000000000000000000000000
... + 40 G152 Wh F SV U65 -025 -050
2222222222222243332562425525332233322333
0000000000000071520780603605650D0250D050
... + 80 X#######
2222222222222250000000222222222222222222
000000000000008000020C000000000000000000
... + 120 4020111650-002-005 9
2222222222233333333332333233322222222223
000000000004020111650D002D00500000000009
... + 160 03 ######
3322222222222222222222222222222222000000
0300000000000000000000000000000000000000
... + 200 # 0
0222222222222222222222222222222222222223
C000000000000000000000000000000000000000
... + 240 000000000000000
333333333333333
000000000000000
SY-XPROG SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
%_FL1*TV_GOFREIGHT 1
0000
1000
SY-XFORM CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
%_FUN*TV_GOSERIAL 1
0000
1000
6 METHOD LINE_CHECK
SAPLMIGO
LMIGOKL4 217
IS_OLD_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
CS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
LC_BATCH_CONVERSION_ACTIVE 1
3
1
LCL_MIGO_CURSOR=>VALUE FG Rework
4425676762222222222222222222222222222222
670257F2B0000000000000000000000000000000
... + 40
2222222222
0000000000
%_FL1*TV_GOSPLIT <initial>
<initial>
<initial>
LS_GOPLANT
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
22222222222222222222222222222
00000000000000000000000000000
GOITEM-EXVKW #######
0000000
000000C
ME->PS_GOHEAD+746(3) TH
542
480
LS_GOPLANT-LAND1
222
000
LS_GOT001L
222222222222222222
000000000000000000
SY ########################################
0000000000000000000000000000000000000000
1000100000001000000000000000000000000000
... + 40 ########################################
0000000000000000000000000000000000001000
100010001000000010000000000000000000A000
... + 80 ################<#######################
0000000000000000300000000000000000000000
0000000050004000C00000000000000000000000
... + 120 ####################################p###
0000000000000000000000000000000010007000
00000000000000000000000000000000A0000000
... + 160 ####<#######pb## C############# E1 0
0000300000007600240000000000000222432223
0000C00000000200030030000C0000C000510000
... + 200 0010001 ####D$S 900
3333333222220000425222222222222222223332
0010001000001000443000000000000000009000
... + 240 00
222223322222222
000000000000000
OREF_HEADER_GENERAL
LS_GOITEM-WERKS
2222
0000
LS_GOITEM-LGORT 2031
3333
2031
OREF_SPLIT_QUANTITY
ME
LS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
5 METHOD LINE_MODIFY
SAPLMIGO
LMIGOKL1 123
I_LINE 2
0000
2000
I_TABIX 0
0000
0000
I_INSERT
2
0
I_FORCE_CHANGE
2
0
I_AUTHORITY_CHECK
2
0
I_STATUS_DELAYED X
5
8
I_DEPENDENT_TABLES
2
0
IT_GOSERIAL Table[initial]
IT_GOFREIGHT Table[initial]
CS_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
ME
LS_OLD_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
LS_NEW_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
ABAP_FALSE
2
0
GODYNPRO-UMCHA
2222222222
0000000000
ME->PT_GOITEM Table IT_156[20x2752]
L_TABIX 2
0000
2000
4 METHOD VALUECOPY
SAPLMIGO
LMIGOTV3 370
LS_TARGET_GOITEM-GLOBAL_COUNTE 000002
333333
000002
L_CHECKFIELD GOITEM-LGOBE
444544244444222222222222222222
7F945DDC7F25000000000000000000
L_STATUS 1229932294
0
6
G_SUB_TAXES
2222
0000
LCL_MIGO_SCREENMODIFICATION=>C 960038918
0
6
L_FIELD_TARGET LS_TARGET_GOITEM-LGORT
4555454455444544244455222222222222222222
C3F412754F7F945DDC7F24000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
222222222222
000000000000
<L_VALUE_TARGET> 2031
3333
2031
<L_VALUE_SOURCE> 2031
3333
2031
LCL_MIGO_GLOBALS=>KERNEL
L_TARGETLINE 2
0000
2000
ABAP_TRUE X
5
8
LS_TARGET_GOITEM 00000002000000000000 X
2222222222333333333333333333332222252222
0000000000000000020000000000000000080000
... + 40 903H - 1 1 201
2223334222223222322222222233322222222222
0009038000D01000100000000020100000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
%_CX_GRID_ID 1
0000
1000
3 METHOD LIF_MIGO_FRAME~OKCODE_HANDLER
SAPLMIGO
LMIGOTV2 174
I_OKCODE MIGO_OK_TAKE_VALUE
4444544554445544542222222222222222222222
D97FFFBF41B5F61C550000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
GOSPLIT #######
2222222222222222222222222222000000022222
0000000000000000000000000000000000C00000
... + 40
222222222222222222222222222222
000000000000000000000000000000
LCL_MIGO_GLOBALS=>KERNEL
GOSEARCH_PO
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 0000000000
2222222222222222222222222222223333333333
0000000000000000000000000000000000000000
... + 200 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 000000
333333
000000
LS_CONTROL
222222222222222
000000000000000
%_CX_TABSTRIP_VERSION 0
3
0
GOSEARCH_ORD
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
222222222222
000000000000
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
ME
2 METHOD OKCODE_DISPATCH
SAPLMIGO
LMIGOFR2 171
I_OKCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
L_MSG_STRING
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
222222222222222222222222222222
000000000000000000000000000000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
3333333333
0000000000
L_OKCODE MIGO_OK_TAKE_VALUE
4444544554445544542222222222222222222222
D97FFFBF41B5F61C550000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
SCREEN OK_NEW_ITEMS
4454455454452222222222222222222222222222
FBFE57F945D30000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120 00001#10000 ####
2222222222222222222222223333303333320000
0000000000000000000000000000101000000000
1 MODULE (PAI) PAI_OKCODE_DISPATCH
SAPLMIGO
LMIGOPAI 11
LCL_MIGO_FRAME=>TRACE_INFOS
2
0
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000000000
3333333333
0000000000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 0000
3333
0000
LCL_MIGO_GLOBALS=>EXTERNAL_CAL 00000
33333
00000
OKCODE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "HandleRsqlErrors" of the SAP
Basis System, specifically in line 773 of the module
"//bas/640_REL/src/krn/runt/absapsql.c#16".
The internal operation just processed is "SQLS".
The internal session was started at 20080130103952.
Internal call code.........: "[RSQL/READ/T001L ]"
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=4832)
When : 1/30/2008 10:41:32.722
Threads : 2
Computer Name : TOGR3PRD1
User Name : SAPServicePRD
Number of Processors: 8
Processor Type: x86 Family 15 Model 2 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 14ac
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=003c61d4 edi=003c61a8
eip=7c82ed54 esp=03fedfb4 ebp=03fedfc4 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000216
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:03fedfb4=7c82ed5c
7c82ed5c 8d642400 lea esp,[esp] ss:07fdb4c7=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
03fedfc4 003c61a8 00000000 00000001 01d40b84 000014ac ntdll!KiFastSystemCallRet
00000000 00000000 00000000 00000000 00000000 00000000 <nosymbols>
State Dump for Thread Id 168c
eax=00000001 ebx=00000103 ecx=fffffffe edx=003c0000 esi=00000000 edi=00000000
eip=7c82ed54 esp=05fefeb0 ebp=05fefef4 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:05fefeb0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:09fdd3c3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
05fefef4 00fede51 00000eb0 00000000 00000000 003c7920 ntdll!KiFastSystemCallRet
05feff84 7c349565 00000000 00000000 00000000 003c79b8 disp+work!SigIMsgFunc >
> [signt.c (563)]
05feffb8 77e6608b 003c79b8 00000000 00000000 003c79b8 MSVCR71!endthreadex
05feffec 00000000 7c3494f6 003c79b8 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Type
Program
Gen. Date Time
Load Size
Prg
SAPLMIGO
22.09.2005 21:54:56
1226752
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Prg
CL_MMIM_USERDEFAULTS==========CP
06.05.2002 10:42:38
17408
Typ
ESDUS
01.03.1999 13:36:04
2048
Typ
GOHEAD
08.01.2003 16:15:40
9216
Typ
MKPF
08.01.2002 15:13:52
5120
Typ
KBEFU
26.03.1999 14:46:02
5120
Typ
LFA1
11.05.2004 11:32:44
19456
Typ
MIGO_CUST_ACTION
30.11.1999 10:19:14
2048
Typ
MIGO_CUST_REFDOC
30.11.1999 10:19:14
2048
Typ
X031L
15.11.2000 18:03:28
5120
Prg
SAPLSDIFRUNTIME
22.09.2005 21:42:36
81920
Typ
DFIES
09.11.2000 14:07:05
8192
Prg
SAPLSDNT
22.09.2005 21:55:13
201728
Prg
SAPLSUGS
22.09.2005 21:42:36
29696
Prg
SAPLV01D
11.05.2004 11:59:11
25600
Typ
IWRKZ
04.04.1995 15:56:46
1024
Typ
TCUCH
07.01.2002 15:50:54
3072
Typ
TCUBN
07.01.2002 15:50:53
2048
Typ
TCUWS
13.08.1997 13:57:58
2048
Typ
TCUDRV
07.01.2002 15:50:54
2048
Prg
CL_GUI_CFW====================CP
22.09.2005 21:14:53
154624
Prg
CL_GUI_PROPS_CONSUMER=========CP
07.01.2003 18:26:56
26624
Prg
%_CCNTL
14.02.2002 14:22:46
13312
Prg
SAPLTHFB
22.09.2005 22:08:44
304128
Prg
CL_EXITHANDLER================CP
16.06.2004 11:34:41Hello,
the problem is the following error:
>> ORA-04030: out of process memory when trying to allocate 1332 bytes (callheap,qkkele)
Take a look at sapnote #130140 and #335230 and follow the instructions.
Regards
Stefan
Maybe you are looking for
-
BAFF Format - Bank of America Format - Any SAP program to generate it
One of customers have a requirement to make electronic payments to vendors. The DME file should be in Bank of America format (BAFF). The guide reads : Welcome to the STP Guide for the BAFF Payment file format. This guide has been customized to provid
-
CarriageReturn and lineFeed in the File
Hello, This is my scenario. I am using the standard program RSEINB00 to convert a idoc flat file to xml and then passing it through the Interface. When the flat file is converted to XML, the End of line of the file is going as a special character int
-
Is it possible to get a new iPhone instead of an old iPhone 5 with paying the difference?
I have an iPhone 5 that recently has a problem with the battery, but today it stopped working. I am living in Lubbock, TX, and there is no Apple store near by. I would like to now about the possibilities of fixing the phone or replacing it with payin
-
How to create an annotation with respect to zoom?
Hi, Does anyone know how to create an annotation withrespect to the zoom of the pageview? I already tried this: ASFixed zoom = AVPageViewGetZoom(pageView); rect->top += ANNOT_HEIGHT; rect->top *= zoom; rect->bottom = rect->top - ANNOT_HEIGHT; rect->b
-
Connecting a Samsung monitor onto Ibook G4
I'm totally new to MAC so pardon my ignorance. I have an IBook G4 (inherited from my son) and I love it, but the monitor is small for all the time usage - hard on my eyes. I have a Samsung monitor that measures 20" across and would like to use it, if