Getting error "SQL error in the database when accessing a table."

[Former Member]

Hi All,

We are getting Dump Error SQL error in the database when accessing a table for the batch job EISSD/REQUISITION 14 / which includes program AQ20FD==========A2============. Please reply. The Dump error details are as follows

Short text

SQL error in the database when accessing a table.

How to correct the error

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

number 21 with name "_SYSSMU21$" too small"

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

Please check the entries in the system log (Transaction SM21).

Thanks

Padmakar Kudtarkar

Edited by: Rob Burbank on May 19, 2011 9:38 AM

[Former Member]

The query where we are getting error in Standard program AQ20FD==========A2============ for Job

EISSD/REQUISITION 14 / is as follows:

select VBRK_{BUKRS VBRK}FKART VBRK_{FKDAT VBRK}FKTYP VBRK_{GJAHR VBRK}KUNAG VBRK_{KUNRG VBRK}KURRF VBRK_{VBELN VBRK}WAERK VBRP~AUBEL

VBRP_{AUPOS VBRP}FKIMG VBRP_{KVGR2 VBRP}KZWI1 VBRP_{MATNR VBRP}MWSBP VBRP_{NETWR VBRP}PSTYV VBRP_{VBELN VBRP}VGBEL VBRP~VGPOS

VBRP_{VKBUR VBRP}VKGRP VBRP_{VRKME VBRP}WAVWR

into (VBRK-BUKRS , VBRK-FKART , VBRK-FKDAT , VBRK-FKTYP , VBRK-GJAHR , VBRK-KUNAG , VBRK-KUNRG , VBRK-KURRF , VBRK-VBELN

, VBRK-WAERK , VBRP-AUBEL , VBRP-AUPOS , VBRP-FKIMG , VBRP-KVGR2 , VBRP-KZWI1 , VBRP-MATNR , VBRP-MWSBP , VBRP-NETWR

, VBRP-PSTYV , VBRP-VBELN , VBRP-VGBEL , VBRP-VGPOS , VBRP-VKBUR , VBRP-VKGRP , VBRP-VRKME , VBRP-WAVWR )

from ( VBRK

inner join VBRP

on VBRP_{VBELN = VBRK}VBELN )

where VBRK~BUKRS in SP$00004

and VBRK~FKDAT in SP$00001

and VBRK~KUNAG in SP$00002

and VBRK~VBELN in SP$00006

and VBRP~MATNR in SP$00003.

%dbacc = %dbacc - 1.

if %dbacc = 0.

stop.

endif.

check SP$00004.

check SP$00001.

check SP$00002.

check SP$00006.

check SP$00003.

add 1 to %count-VBRK.

%linr-VBRK = '01'.

extract %fg01.

%ext-VBRP01 = 'X'.

extract %fgwrVBRP01.

endselect.

[Former Member]

Hi,

Use Select Single -

---

Regards

Dhiraj Dangore

[Former Member]

I've seen this, but not in a long time. It occurred when a SELECT statement ran for a long time during times when the database is up and being modified.

We either rant the program overnight or made the selection set smaller.

Rob

[Former Member]

Hi Rob,

Thanks for the useful information.

Regards,

Padmakar Kudtarkar