DBIF_RSQL_SQL_ERROR error

[Former Member]

Hi,

I have a program which extracts data from MBEW table and the table is having around 80 lakhs ( 8 million) records.

and the extract is written to unix directory in application server.

this is extracted through a job periodically, this job was runnig fine and last week the job cancelled and the error it displays is.

Runtime Errors DBIF_RSQL_SQL_ERROR

Except. CX_SY_OPEN_SQL_DB

Short text

SQL error in the database when accessing a table.

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.

How to correct the error

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

number 138 with name "_SYSSMU138$" too small"

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

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"

the error also shows the area where it went wrong.at the select statement.

IF matvl NE 1 AND NOT p_mbew IS INITIAL.

PERFORM openfile USING t_matval.

IF sy-subrc IS INITIAL.

SELECT matnr bwkey bwtar lvorm lbkum salk3 verpr stprs peinh bklas

vmstp lfgja lfmon bwtty stprv laepr zkdat lplpr bwspa

FROM mbew

INTO wa_mbew

WHERE matnr IN mtnums.

it also shows one record.

WA_MBEW

0242-39238 5050 ###########H䄬##7900#H䄬200910 #H䄬2009080100000000#H䄬###H>

but this record doesnt have any # in the table MBEW.

Please help me in this regard,

the dump is because of the error in the data(i checked in the table but there are no has in the table ) or any other issue.

Thanks in advance.

Regards

[Former Member]

HI

Check the Contents for the Key field Matnr value displayed in dump for consitent data.

Check the Sequence of fields in the select query and the Target area( internal table or Work Area).

Cheers

Ram

[Former Member]

Hi krishna,

if that is the case, thej it should happen for all the records in the table.

this is happening for specific material,

if i rerun this job a different material is shown in the error. i guess the error is not with the order of fields.

Regards

[Former Member]

Hi Prashanth,

Check the Consistency of the data in SE11 for the following record

0242-39238 5050 ###########H䄬##7900#H䄬200910 #H䄬2009080100000000#H䄬###H>

This might be inconsitent.

Cheers

Ram

[Former Member]

Hi,

This generally occurs when your table has ran out of space. You may ask your basis team to increase the table space or try searching the OSS notes with the dump error you have got

Vikranth