I am doing a batch update which updates around 100,000 rows. While this updating is in progress, the system slows down all in a sudden for few minutes before it continue to work normally.
The archive log is enabled and I have 5 online groups with each 10 MB size. If I check the V$log while updation in progress, I find the status is in ACTIVE even after the archive file written for that log. This sequence continues until all the log files except current one in ACTIVE state. After couple of minutes all the ACTIVE status getting changed to INACTIVE.
Any Idea what could be the reason for this? I got 8.1.6 undex solaris.
ACTIVE: Indicates the log is needed for crash/instance recovery
INACTIVE: Indicates log is not needed for instance recovery but, may be in use for media recovery.
CURRENT: Indicates the current log where the redo is written.