topic Re: short dump? in Application Development and Automation Discussions

short dump?

Former Member — Thu, 03 Jan 2013 08:37:29 GMT

hi all,

could you help on this, why it comes and how to correct?

( Termination occurred in the ABAP program "RIAUFK20" - in "SELECTION_L".
The main program was "RIAUFK20 ".

In the source code you have the termination point in line 1099
of the (Include) program "RIAUFK20".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "SELECTION_L" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.

The procedure is in program "RIAUFK20 "; its source code begins in line
822 of the (Include program "RIAUFK20 ".)

for me it comes sometimes when no.of i/p records are more than 400 or 270. but lately it came when no.of i/p records are 79.

no clue about what it is....?

thanks &regards

satish chandra

Re: short dump?

RaymondGiuseppi — Thu, 03 Jan 2013 08:59:49 GMT

Check for message errors in system log (SM21) or in database system maneger. Did you apply any change/Patch to kernel or database. You could also try to generate the dump during a SQL trace (ST05) to look at actual SQL statement.

Regards,

Raymond

Re: short dump?

Former Member — Thu, 03 Jan 2013 09:30:26 GMT

it gets triggered in select statement of standard program. i cant understand why?

Re: short dump?

RaymondGiuseppi — Thu, 03 Jan 2013 13:00:12 GMT

What is the actual (database server) error message, usually can be found in SM21 where I already wrote to look for.

Most current reason is "too complex selection that goes beyond maximal allowed size of a SQL statement for the database manager", but other errors are possible.

Regards,

Raymond

Re: short dump?

Former Member — Fri, 04 Jan 2013 04:34:11 GMT

Raymond is this what you are asking for....

Database error text........: "POS(1) Too complicated SQL statement (too much

strategy data)"

regards

Re: short dump?

RaymondGiuseppi — Fri, 04 Jan 2013 08:27:37 GMT

Yes, are there many "OR" options in the where clause, can you remove some easily ?

-1106: Too complicated SQL statement (Too much strategy data)   
Explanation
The  search strategy used to process the SQL statement is greater than the space available.
User action
Delete some of the search strings containing an OR option.

Regards,

Raymond

Re: short dump?

Former Member — Fri, 04 Jan 2013 13:32:59 GMT

MY search is and search. and it is simillar to standard search like IH06, IH08, IP24, IW39 AND IW69 etc.

thanks & regards

satish chandra

Re: short dump?

Former Member — Fri, 04 Jan 2013 13:34:40 GMT

Ok what i did is, there are few searches in my code(and search) but i only use function location searches or equipment often.

Re: short dump?

RaymondGiuseppi — Fri, 04 Jan 2013 13:41:48 GMT

Remember list of values in a range result in OR statement, so as I wrote, use ST05 SQL trace, to get a look at the actual SQL generated statement. Else you will get some errors due to strategy or even generated statement too wide for technical reason related to SAP kernel and DB version.

Regards,

Raymond

Re: short dump?

Former Member — Sat, 05 Jan 2013 07:10:45 GMT

thanks raymond, yesterday i executed a custom report which fetches data from excel sheet and creates function locations in sap using bapi. there were some 50000 records, i got dump saying insufficiant memory. the error triggered in the bapi.

i keep getting such dumps, i dont know how to treat them?

Re: short dump?

RaymondGiuseppi — Sat, 05 Jan 2013 09:51:06 GMT

Try to keep memory usage ats low as possible

- FREE data no longer required

- Managet data by batch of 1000 records or so when related to reading complementary data into memory

- perform some test to identify best size of batch data and frequency of commit

- Negociate with Basis for maximal memory available (depends on exact error message in dump)

- you could also submit the treatment of each batch of data in a background job (but then insure correct lock management)

Regards,

Raymond