SAP S/4HANA Administration
Memory Management & Table Buffering
24 flashcards · answers and review in the app
What are the main SAP buffers, and which is the largest?
What SAP HANA performance functions does DBACOCKPIT's Performance node provide?
What is extended memory, and how does the roll mechanism use it across dialog steps?
What does the SQL plan cache do, and what happens when it fills up?
What does ST06 monitor, and why might its History view be empty?
What does ST02 show, and why does the instance startup time matter when reading it?
Why don't SAP buffer size changes take effect immediately, and where are they set?
What's the difference between SAP buffers and SAP memory areas?
Which parameters limit heap memory, and what does abap/heaplimit do?
In a multi-instance system, how are table buffers kept in sync, and what's the consequence?
What happens when extended memory is exhausted or a process hits its quota?
Which parameters set the extended memory total size and per-process quota?
How can you change extended/heap memory allocation dynamically despite the static parameters?
What does table buffering do, and how much can it speed up data access?
When a buffered table row is changed, what happens to the buffered data?
What four conditions qualify a table for buffering, and what's the read/write rule of thumb?
Where is a table's buffering configured, and what are the three options?
How do a table's size and access pattern determine which buffering type to choose?
Why might no expensive SQL statements be logged even when slow queries are running?
What does the SAP HANA allocation limit represent, and what happens when memory keeps hitting it?
What is a buffer object swap, and what's the target number of swaps?
Why are PRIV-mode work processes dangerous, and how does the system limit them?
What are the three table buffering methods?
Which transactions help identify buffering candidates and then confirm the right type?