Timeout error

[Former Member]

Hi,

I am doing a select statement and its throwing a timeout error. How can i fix it?.

Thanks,

Sandeep

[Former Member]

hello,

run it in the background and see if it works, there is a time limit for foregroung jobs.

Thanks,

Thirumal

[Former Member]

hi,

which table are u using select?/

try to use all the key fields in in where condition

If possible create secondary index for the fields in where condition

[Former Member]

Basically time out error is due to the fact that it is taking lots of time while processing..

The reasons can be you are fetching huge amount of data or the select needs to be performance tunning.

Regards

Anurag

<b>From the SELECT it looks that it is breaking as it trying to fetch huge amount of data. Only solution is to reduce and try and filter as much as possible.</b>

Message was edited by: Anurag Bankley

[Former Member]

Hi,

The time_out depends on the settings in RZ10 for running the program in foreground. .I think your select statement is not optimized to use indexes or you are querying from cluster table. Tune your select statement to have index fields and it will improve.

Hope this helps.

[Former Member]

I am processing the job in BDC session. This is where it breaks.

SELECT * FROM HRP1001 CLIENT SPECIFIED |

103	INTO TABLE B1001
104	WHERE MANDT EQ RHDB_CLIENT
105	AND PLVAR EQ PLVAR
106	AND OTJID IN RANGE
107	AND SUBTY IN SUBTY_RANGE
108	AND ISTAT IN ISTAT_RANGE
109	AND BEGDA LE ENDDA

| 110| AND ENDDA GE BEGDA.

Sorry, the formatting is not good. But no syntax errors. Disregard line numbers.

Thanks

[Former Member]

Sorry. Its breaking in the foreground.

[Former Member]

Hi Sandeep,

Try changing the order of the where clause like this and run in the background:

SELECT * FROM HRP1001 CLIENT SPECIFIED

INTO TABLE B1001

WHERE MANDT EQ RHDB_CLIENT <b>"key field</b>

AND PLVAR EQ PLVAR <b>"key field</b>

AND ISTAT IN ISTAT_RANGE <b>"key field</b>

AND BEGDA LE ENDDA <b>"key field</b>

AND ENDDA GE BEGDA <b>"key field</b>

AND OTJID IN RANGE

AND SUBTY IN SUBTY_RANGE.

Regards,

Vivek

[Former Member]

1.

the WHERE Condition fields order should be the same sequence as it appears in the table.

in your case

ISTAT is appearing before SUBTY etc.. in the table.

its not advisable to use.

2. check you have any available index for that table for the fields you are sending with WHERE.

Regards

Srikanth

[Former Member]

Fine tune the select query and execute the program in background.