Dump while setting a break point in ECC 6.0

[Former Member]

Dear Experts,

In ECC 6.0, when I try to put a break point in the program to stop the control there. I am not able to do so, it is going to dump. The dump message is also not very clear. Do anyone of you are facing the same problem. Any idea why is this happening and how do I fix it.

Can it be due to the improper installation? Please respond.

[Sm1tje]

So when is it dumping (when it is hitting the break-point, or when setting the break-point, before reaching the break-point) and what is the dump message saying (just an extract, do not post the whole dump)?

Is it a standard report/program, or custom developed? We need more info for a proper reply.

[Former Member]

Hi Micky...Here is the detailed description:

Issue: In ECC 6.0, when I write a simple ABAP program (e.g. 'Hello World' program). When I try to keep the cursor on any abap statement and click on the 'session break point' icon in the tool bar to set the break point, i get a status message 'Compling SAPLBREA in separate task and finally i get the dump.

Dump Detail :

Runtime Errors: DBIF_REPO_SQL_ERROR

Short Text : SQL error 1115 occurred when accessing program 'LNAVIDAT' part "SRC".

Program: SAPLBREA

Include: LBREATOP

Row: 41

There is a an include being called at line no 41, which is "Include LNAVIDAT".

Now when I click on the 'debugger' icon in the dump...It points to a functional module "RS_SET_BREAKPOINT"

Also, while double clicking on this include to see the code within, it issues an error message saying "SQL error occurred when accessing the table TRDIR".

Or

While trying to display the code of the include LNAVIDAT in se38 to see what is wrong with that i get another dump and this time it points to be SELECT query in the dump which is:

SELECT SINGLE * from PROGDIR WHERE name = rs38m-programm

and state = active.

Thereafter, i keep getting dumps when i try to go to any T.codes (e.g. se11, se38 etc.). until i log off and log in again. Hope this helps you guys understanding the problem. Being new to SAP, I have no clue why is this happening and how to fix it. Thanks in Advance.

[Former Member]

Hi...

i think d problem is related with your server...try to contact ur adminstrator....i have also gone through such type of error once....and tht time it was due to server malfunctioning....or may be 'coz of ur R/3 sys malfunctioning.

Regards.

Shrikant

[Former Member]

Hi Shrikant,

Can you tell me how did you get rid of this server malfunctioning issue?

Here is some more information from the dump which is suggesting how to correct this problem.

Database error text: "ORA-01115: IO error reading block from file 52 (block # 86435) # ORA - 01110: data file 52:

It is also pointing to a file in the local drive where database is residing:

D:\ ORACLE\DM0\SAPDATA1\SR3700_1\SR3700.DATA1 #ORA-27091 : Unable to queue , async read/write failed.

Triggering SQL statement: "LNAVIDAT"

Internal call mode: REPO/D/OPBR/SRC/ LNAVIDAT

After all, any transaction code which is calling the include LBAVIDAT internally is dumping. If anybody has the access to sapservices.com, can you please use the serch criteria "DBIF_REPO_SQL_ERROR" to find the cause of this problem.

Many Thanks.

[Sandra_Rossi]

As the problem is no more an abap problem, as per the [rules of engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement], you should close this thread, and search the answer in forum [SAP on Oracle|;. Then, if you don't find the answer, post to this forum.

[Former Member]

Please paste your code here so that we can analyse what exactly the error is...

Regards,

Nitin.

[Former Member]

Hi,

Is it ALV report? it is ALV report you just check coding part line length is must 72 charecters,otherwise it will goes to dump directly.

Regards,

Anki Reddy

[Former Member]

Hi,

Is it ALV report? it is ALV report you just check coding part line length is must line number 72 ,otherwise it will goes to dump directly.

Regards,

Anki Reddy

[sujeet2918]

Hello,

Welcome on SDN community.

please provide appropriate details while posting any thread on Forum, so that we people try to help you.

try to make one dynamic break point and see again.

or better you explian what you want to do with your code.

Have a Nice Day.

Regards,

Sujeet

[Former Member]

The dump might have been caused before the line on which the break point is set. Try debugging from the beginning of the report and find the actual cause of the dump.

[Former Member]

Hi,

first of check in ST22 transaction for short dump,what is the what is the error ,run the program in debugging mode where u r getting the short dump and the message .

for you r question u will not mention in what type of program generally we r getting the problem in programs ,interfaces .....

Regards,

Madhu

[Former Member]

Hello ,

Break point would be in middle of Select & Endselect.

[Former Member]

First of all thanks to Mickey, Nitin, Anki, Sujit, Red, Madhu, Vibin for the quick response...To be honest I did not expect such a response as a new member to the SDN community...I am sorry I could not mention the detail about the dump initially...Here is the detailed description..

Issue: In ECC 6.0, when I write a simple ABAP program (e.g. 'Hello World' program). When I try to keep the cursor on any abap statement and click on the 'session break point' icon in the tool bar to set the break point, i get a status message 'Compling SAPLBREA in separate task and finally i get the dump.

Dump Detail :

Runtime Errors: DBIF_REPO_SQL_ERROR

Short Text : SQL error 1115 occurred when accessing program 'LNAVIDAT' part "SRC".

Program: SAPLBREA

Include: LBREATOP

Row: 41

There is a an include being called at line no 41, which is "Include LNAVIDAT".

Now when I click on the 'debugger' icon in the dump...It points to a functional module "RS_SET_BREAKPOINT"

Also, while double clicking on this include to see the code within, it issues an error message saying "SQL error occurred when accessing the table TRDIR".

Or

While trying to display the code of the include LNAVIDAT in se38 to see what is wrong with that i get another dump and this time it points to be SELECT query in the dump which is:

SELECT SINGLE * from PROGDIR WHERE name = rs38m-programm

and state = active.

Thereafter, i keep getting dumps when i try to go to any T.codes (e.g. se11, se38 etc.). until i log off and log in again. Hope this helps you guys understanding the problem. Being new to SAP, I have no clue why is this happening and how to fix it. Thanks in Advance.

[Former Member]

Hi,

Check with Basis team.

Regards

Md.MahaboobKhan