AWR analysis report questions for help: How can SQL be optimized from what aspects?

AWR analysis result: 1658798054849_bab.html

---

Other Answer 1:

Other Answer 2:

I hope it helps you

https://www.modb.pro/db/13170

Other Answer 3:

The provided AWR report, the time span is too large and has little reference value, it is recommended to take the awr and ash report information in the stuck time period

Other Answer 4:

Basically look at several key points of Load Profile.

Redo size to see if there is a lot of writing.Generally, the archive is full, and the disk is insufficient to see this.

Logical read See if the amount of data read is not large.Generally, in an environment where the hardware conditions meet the standard, the larger this value is, the busier the system is.(A poorly written SQL will also keep the database busy)

Block changes to see how much data is written.

Physical read to see if the SQL is well written, or if the hardware is not powerful (the memory is too small).

Executes (SQL): The number of SQL executed per second.See if the business is complicated

Transactions: The number of transactions performed per second.See if the system is busy

In fact, it is all SQL together, so I have controlled everything here, and there is no problem.