生成个addm报告，看看Oracle建议

1、如果是正常的业务增涨，增加日志组，我们生产的日志大小：500M,差不多10组。
2、是不是最近有新发布代码，排查是不是有代码BUG导致。

addm报告：

FINDING 3: 2.4% impact (77428 seconds)
--------------------------------------
Log file switch operations were consuming significant database time while
waiting for checkpoint completion.

RECOMMENDATION 1: DB Configuration, 2.4% benefit (77428 seconds)
ACTION: Verify whether incremental shipping was used for standby
databases.

RECOMMENDATION 2: DB Configuration, 2.4% benefit (77428 seconds)
ACTION: Increase the size of the log files to 2048 M to hold at least 20
minutes of redo information.

ADDITIONAL INFORMATION:
This problem can be caused by use of hot backup mode on tablespaces.
DML to tablespaces in hot backup mode causes generation of additional
redo.

SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Configuration" was consuming significant database
time. (2.5% impact [77959 seconds])

250M一个这也太小了，一般一个小时切换不要超过20-30次，你可以设置单个日志1G，设置6组，观察下。

另外，行锁等待也比较严重，看看是不是业务逻辑有问题，或者有事务没提交。

1、解决行锁问题

2、redo加到2G

3、查磁盘IO性能

思路，希望对你有所帮助，如果帮助请采纳

redo文件的大小 根据业务实际的需求调整，业务量大时就在调大redo日志文件的大小。