SQL Caught Rabax

[i_only]

Dear All,
Please help for this problem,
pop-up always show when user access tcode

this what i got from sbwp

I am using SAP_BASIS 754

Thanks

[alex_frank]

Hi,

The dump occurs in a Z transaction, which means it's not part of the standard SAP shipment, but was created in your customer system. So you'll have to debug it on your side. Likely there's an SQL statement which is not selective enough and returns way too many rows.

BR,
Alex

[Sandra_Rossi]

Indexing of the question: SQL_CAUGHT_RABAX, TSV_TNEW_PAGE_ALLOC_FAILED.

[qwertie]

Hello,

it seems one buffer is not sufficient in your system (check st02) . Mostly it is the heap memory. you can adjust it with restart or on the fly with the following report RSMEMORY

br

[qwertie]

.

[S_Sriram]

Hi Alex,

Since it is a Z transaction you have to enable the ST12 trace to check the overall expense SQL statement with the help of ABAPer to fix or create the Z index for the expense SQL statement to avoid the dumps.

Regards

SS

[Sandra_Rossi]

No need to use ST12, the faulty SELECT is shown in the short dump, and it's not an index problem, the problem has been explained by @alex_frank.

[S_Sriram]

Hi 

1. Check the free disk space in the DB and SAP USR folders.

2. Share the full dumps as a text file attachment.

Regards

SS

[Sandra_Rossi]

It's not a database space problem, the problem has been explained by @alex_frank.

[S_Sriram]

Hi All, While executing the Z-transaction it is pulling a huge amount of data from the DB, the dump shows that the ABAP program error and TSV_TNEW_PAGE_ALLOC_FAILED, you have to enable the trace to analyze z transaction to fix the issue.

[qwertie]

hi there, you can also try to have a look in st02. there you should find the buffer which is not sufficient. furthermore you can then adjust it on the fly with rsmemory. mostly it is the heap buffer