> During our analysis we get aware that the 40% of the data area (16 Gb) were filled with temporary data, we assuming resulting from the user sessions temporary data.
>
> I didn't found much information regarding this behaviour and our possibilities to adjust some parameters regarding this issue.
> My intention would be to advice MaxDB to release temporary data before reaching 100% filling of data area.
Hello Hannes,
in fact there isn't much so setup or tune here.
The temp. pages required to execute queries will always be automatically removed after the cursor is closed or the command was aborted. With 7.7 and before this unfortunately can take very long times due to the single-block-access-through-the-data-buffer implementation that was used for releasing the temp pages.
However, in case the DB runs full because of temp. page allocation the statement that wanted to allocate more pages will be cancelled and the already allocated pages will be released ... one by one
This has been improved with the most current release of 7.8.
Anyhow, if you regularly see that much temp. space allocated, I highly recommend to review your execution paths - looks like there are too many intermediate result sets beeing build.
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.