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

EXSORT_READ_ERROR

Former Member
0 Likes
832

Dear Collegues,

now and then we get a runtime error EXSORT_READ_ERROR with

error no. 22 and error text "Invalid argument". We get this

runtime error from different batch jobs: F110*, report painter queries, ...

It seems that the external sort tries to read a file and this

doesn't work properly.

Does anybody know what error number 22 means and how to fix the problem ?

From ST22:

The current ABAP program, "SAPF110S", had to be terminated because one of the

statements could not be executed at runtime.

...

The current ABAP/4 program was meant to sort a dataset (internal table

or extract). For reasons of capacity, this was not possible due to

insufficient main storage space. Therefore, the

external sort was called and resulted in the following error:

the following error:

An error occurred while reading the sorted file.

Error number: 22

Error text: "Invalid argument"

...

The termination occurred in the function "ReadBlock" of the SAP

Basis System, specifically in line 1198 of the module

"//bas/640_REL/src/krn/runt/abossort.c#1".

The internal operation just processed is "SORX".

The internal session was started at 20070810040037.

0 bytes of the sorted file were read. However, the system was

expecting 1196544 bytes.

Regards

Monika

4 REPLIES 4
Read only

Former Member
0 Likes
739

From your ST22 dump, it seems that , it tried to sort a dataset and it failed because of memory available was not sufficient.

may be ur queries are fetching a lot of data. Try submitting the jobs when the workload on the server is less.

Read only

0 Likes
739

Because of insufficient main storage the system was using external sort.

That's normal as far as I can see.

The error occured when using the external sort.

DIR_SORTTMP is correctly filled on all 4 application servers:

1. Server:
LDDVD101\saploc\VD1\DVEBMGS00\data

2. Server:
LDDVD102\saploc\VD1\D00\data

3. Server:
LDDVD103\saploc\VD1\D00\data

4. Server:
LDDVD104\saploc\VD1\D00\data

Nevertheless the external sort can't read the temporary file,

but says "invalid argument".

Does anybody have a documentation on the external sort ?

It runs in SAP-Kernel.

Regards

Monika

Read only

0 Likes
739

Hi Monika,

We have de same problem on transaction F110.

This is de error log:

"The termination occurred in the function "ReadBlock" of the SAP

Basis System, specifically in line 1192 of the module

"//bas/46D/src/krn/runt/abossort.c#14".

The internal operation just processed is "SORX".

The internal session was started at 20091202183003.

This is a C level error.

Reading the sorted file was buffered. The buffer contained 3092

bytes when the next block was read, even though a record contains

only 1454 bytes."

How did you sove the problem? Do you have any SAP Note about this problem?

Thank you!

Best regards,

Edy

Read only

0 Likes
739

hi, expert....

I have de same error.

The termination occurred in the function "FlushRun" of the SAP

Basis System, specifically in line 837 of the module

"//bas/640_REL/src/krn/runt/abossort.c#3".

The internal operation just processed is "SORX".

The internal session was started at 20110824190334.

The current ABAP/4 program was meant to sort a dataset (internal table

or extract). For reasons of capacity, this was not possible due to

insufficient main storage space. Therefore, the

external sort was called and resulted in the following error:

the following error:

The sytsem could not write the sorted file to the temporary file

"/usr/sap/LRP/DVEBMGS00/data/S0000F7Q" (file size 83191290 bytes).

Error number: 28

Error text: "No space left on device"

how resolve this issue ?

Tks.