Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Dump analysis ... DBIF_RSQL_SQL_ERROR

Former Member
0 Likes
1,034

Hi Experts,

Please look the dump occured and pointer showing the cause.

Runtime Errors DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB

Occurred on 10/31/2009 at 05:43:38

003360 SELECT OBJNR KSTAR VRGNG BLDAT BUDAT PERNR SGTXT MBGBTR WKGBTR

003370 BLART AWTYP BELNR

003380 REFBN

003390 INTO TABLE ITAB

003400 FROM COVP WHERE KOKRS EQ P_KOKRS

003410 AND WRTTP = '04'"actual costs

003420 AND WKGBTR 0 "cost ne 0

003430 AND GJAHR EQ P_FY

003440 AND KSTAR IN R_COSTEL

003450 AND CPUDT GE BEG_DATE

003460 AND CPUDT LE END_DATE

003470 AND BLART NE 'LT'

003480 AND BUDAT IN S_BUDAT

003490 AND OBJNR LIKE 'PR%'

003500 * and lednr = '00'

003510 AND PERIO IN S_PER

003520 AND VERSN = '000'.

003530

003540 *end of new code. "D11K924480

-


> DESCRIBE TABLE ITAB LINES COVP_RECS.

003560 MESSAGE I028 WITH 'Nbr covp recs' COVP_RECS.

003570 COMMIT WORK. "D11K924480

003580 ENDFORM. " GET_CO_RECORDS

003590

003600 *& * 003610 *& Form PROCESS_CO_RECORDS

003620 *& *

003630 * text 003640 * *

003650 * > p1 text 003660 * < p2 text 003670 * *

This is the dump occured.

Dump POINTER shows to DESCRIBE Statement.

my doubt is, Is the DESCRIBE statment caused the Dump or Select statement.

Please clarify me as one of my friend is saying it is because of Describe and I am saying it is because of Select Statment,

Regards,

Seenu.

9 REPLIES 9
Read only

Former Member
0 Likes
990

Do not post duplicate threads for the same issue. Please close this and continue with the one that is already opened

Read only

0 Likes
990

I didnt see the other one for the same issue which I posted. Please help me out to continue with the question.

Read only

Former Member
0 Likes
990

Hi

Probably the error is in the select, but it should be better if you posted what the dump log says too.

Max

Read only

0 Likes
990

Max, This is the info given under "how to correct the error"

The exception must either be prevented, caught within the procedure

"GET_CO_RECORDS"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Database error text........: "ORA-01555: snapshot too old: rollback segment

number 5 with name "PRS_5" too small"

Internal call code.........: "[RSQL/FTCH/COVP ]"

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

"ZLCP0101" or "ZLCP0101"

"GET_CO_RECORDS"

Edited by: Sreenivasulu N on Nov 6, 2009 11:54 AM

Read only

Former Member
0 Likes
990

Hi,

The order of fields in the SELECT statement and the order in ITAB structure should be same.

COVP_RECS. should be of ' type i '.

Regards,

Deeba

Read only

0 Likes
990

Deeba,

Thanks for the reply.

I have declared the field type as I only.

Importantly these program is executing fine in QA and PROD. Only giving dump in DEV recently. In QA and PROD it is executing from past few years.

Regards,

Seenu.

Edited by: Sreenivasulu N on Nov 6, 2009 11:56 AM

Read only

0 Likes
990

Hi

Database error text........: "ORA-01555: snapshot too old: rollback segment

It's a oracle problem, u should show this dump to your basis, it seems to be a problem on table space for the rollback

Max

Read only

Clemenss
Active Contributor
0 Likes
990

Hi sreenivasulu,

am I right that you did not even try to search for an answer?

This is against the rules of the forum.

You should have found this [ORA-01555: snapshot too old|http://www.google.co.jp/search?hl=en&source=hp&q=ORA-01555%3Asnapshottooold&btnG=GoogleSearch&aq=f&oq=ORA-01555%3Asnapshottoo+old&cad=h]

I assume that it took quite a long time before the error occurred. The SQL statement was selecting in a very inefficient way from a very large database table.

See the link I gave you and try to get an understanding of rollback segments.

Try to use full primary index for selects, try to use secondary index tbles first where applicable.

Regards,

Clemens

Read only

Clemenss
Active Contributor
0 Likes
990

... or try this

[COVP (key fields that bring back results quickly)|http://web.mit.edu/sapr3/dev/covp.htm]

Kind regards,

Clemens