Solution : https://service.sap.com/sap/support/notes/805934 (SAP Service marketplace login required)
Summary :
SAP Note clarifies aspects of database time within the R3 environment, focusing on understanding, measuring, and optimizing this component. Database time comprises the periods during which SAP and Oracle servers, along with network communications, actively engage in processing database requests. Standard SQL commands contribute to this metric, excluding certain DDL commands and COMMIT/ROLLBACK operations, which are reflected separately in processing time within system statistics. For accurate analysis, real-time monitoring and specific diagnostic tools and methods like ORADEBUG or the snapshot method are recommended. Factors like network issues, resource bottlenecks, and Oracle client performance significantly influence database time. Moreover, although average database time can be observed, it's advised not to use it as a sole performance indicator due to its susceptibility to various extraneous factors, suggesting a more transaction-specific assessment for precise business process optimization.
Key words :
create operating system call traces, terms frequently asked questions, operating system dependent tools, transaction sm50/sm66 increases, database time apparently increases, analyze oracle client activities, operating system calls, operating system partner, structured query language, customer-specific development
Related Notes :
| 1130637 | Increase in average response time following upgrade |
| 1100926 | FAQ: Network performance |
| 881083 | Blocking factors on Oracle-based systems |
| 825653 | Oracle: Common misconceptions |
| 659856 | Analyzing blocking SAP operating system processes |
| 619188 | FAQ: Oracle wait events |
| 618868 | FAQ: Oracle performance |
| 613872 | Oracle traces with ORADEBUG |
| 562403 | FAQ: Oracle Net |
| 556764 | Upgrade hangs in phase ACT_<REL> |