Database problem is very large, as shown in figure:

CodePudding user response:

Redolog and archive logs on the same disk group, asm is the cause of the log file sync wait for events, in addition the db file sequential read wait event is also very serious

CodePudding user response:

1, optimize SQL
2, commit the frequency is too high or IO bottleneck, etc

CodePudding user response:

1, improper use index
2, most likely when submit frequently, IO slower (likely IO contention also cause?) , it is best to put REDO separate faster disks

CodePudding user response:

refer to the second floor sxq129601 response:

1, optimize SQL
2, commit the frequency is too high or IO bottleneck

Who runs AWR the SQL basic not running slow, a single execution are within 1 s

CodePudding user response:

The

reference 3 floor sych888 response:

1, improper use index
2, most likely when submit frequently, IO slower (likely IO contention also cause?) , best to REDO alone into the faster disks

Commit is very frequent, but is due to business needs, no single plate to the redolog redolog turned out to be a disk, and datafile finally change to disk archive logs, disk under the premise of not change what else

CodePudding user response:

Information is too little, if you want to analysis, complete who runs awr reports, business peak, a hour, send some to my mailbox inside, but I see
[email protected]

CodePudding user response:

refer to 6th floor xifenfei response:

information is too little, if you want to analysis, complete who runs awr reports, business peak, a hour, send some to my mailbox inside, but I see
[email protected]

Hello, I sent you a post and telecommunications, trouble you