Skip to end of metadata
Go to start of metadata

Use

Physical I/O for temporary pages: written: <count>, read: <count>, in use: <count>  

<number_of> temp pages used from task <task_id>, appl. pid <pid> on <node>


Explanation

In temporary data pages  intermediate results are saved.
A very high number of temporary pages may be an indicator that a command (f.e. a join) is not processed in the optimal way producing a lot of unnecessary data.


User Response

Find out if the high number of temporary pages is caused by a command running amok or if they have to be generated necessarily.


More Information

Relevant  DB-Analyzer Files
Helpful with ...

DBAN_FILLING.csv 

Find informaton about of memory use in column "TempUsed".
DBAN_IO.csv Find information about physical read/write operations in "Temp_PWrites",  "Temp_PReads"
SAP Note
Helpful with ...


Expert Sessions (Link to trainings)
Content / Helpful with ...
Session 15: SAP MaxDB No-Reorganization PrincipleFind (at the end of the presentation) some information how to define the relevant session in system view "files".
Documentation (links)
Helpful with ...


                            


  • No labels