Skip to Content


Dear SAP'ies

Any opinion on the topic REORG/RUNSTATS of table DYNPLOAD.

Should it be done? Will I gain any benefits by doing it?
Question arise because og some 5 min hang-up on the table DYNPLOAD.

Looking forward hearing from you :-)

Teddy Løv

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 01, 2018 at 11:58 AM


    Table DYNPLOAD is initially empty and grows after generating more and more dynpros. However queries on this table are usually very simple and straight forward. So the Db2 optimizer should find a good access plan even it the statistics is not current. The DB2 registry setting

    DB2_REDUCED_OPTIMIZATION=4,INDEX,... [DB2_WORKLOAD] usually ensures that an index access is chosen.

    if you observed problems on table DYNPLOAD, it is most likely caused by lock wait situations ( check LOCK_WAIT_TIME column in SQL cache ) or due to the fact that BLOB columns are fetched and the prefetchers or prefetch queues are overloaded ( DB CFG parameter NUM_IOSERVERS should be set to 104; if you use DB2 10.5 you should use FP8 or higher ).

    Which DB2 version are you using?



    Add comment
    10|10000 characters needed characters exceeded

  • Apr 11, 2018 at 02:19 PM

    Hello Experts!

    I have the same problem as the topic starter. In a one moment our system got stuck, and in db2top I can see lots of queries on DYNPLOAD, REPOSRC and etc. I have a test query on DYNPLOAD and when i execute it during the problem it also runs long. But in 5-15 min all becomes OK. It is very strange. Our db version is DB2 LUW 10.5 FP 5. IO_NUMSERVERS=AUTOMATIC(36). As I see above NUM_IOSERVERS >=104 doesn`t resolve the problem. Any ideas? Only upgrade to FP 8?

    Add comment
    10|10000 characters needed characters exceeded