Solution : https://service.sap.com/sap/support/notes/331366 (SAP Service marketplace login required)
Summary :
When using DB2B Buffer Pool Tuning-Transaction in SAP R/3 with 'Since startup' option, results may vary across different application servers. This issue arises due to the system's method of retrieving statistical data. To address this, ensure all relevant transports outlined in SAP Note 101217 are imported correctly according to the sequence specified, which helps maintain the system at the latest maintenance level. For specific fixes, refer to SAP Note 13719 and import corresponding transports for releases 4.6A to 4.6D as detailed in SAP Note 321751 or transports D6AK000041 and D6GK000032 for other designated releases. Ultimately, the system will compile statistics from all servers via RFC to establish buffer pool defaults.
Key words :
buffer pool tuning-transaction db2b, prerequisites uklösung solution make, additional key words db2, buffer pool defaults, latest maintenance level, remote function call, totals values form, active application servers, application server, additional note
Related Notes :
| 331608 | DB2/390: DB13: Maximum 400 DD statements per job step |
| 330900 | $</R3/RTF/46 /0330900/D/00/BC-DB-DB2 /Sabine Heider /42634 |
| 321751 | DB2/390: ST04 service level 1 |
| 313419 | DB2/390: Application server in upper case (ICLI) |
| 313400 | DB2/390:error COMPUTE_INT_TIMES_OVERFLOW in RSDB2B |
| 191215 | DB2/390: Transports for 4.6B |
| 166083 | DB2/390: Transports for 4.6A |
| 101217 | DB2 z/OS: Overview of transports and corrections |
| 13719 | Preliminary transports to customers (note for customers) |