In the REDO LOG Management category, you will find queries to verify the production of REDO LOG files within an hour over the course of a month. Additionally, there is one to view the threads, groups, names, sizes, and status of REDO LOG files.
The most important structure for recovery operations is the REDO LOG, which is composed of two or more preallocated files that store all modifications made to the database as they occur.
Once the REDO LOG is filled, a switch occurs to the next REDO LOG file in a cyclical manner. However, if there are too many switches, the database will experience performance issues.
Oracle recommends not exceeding 5 REDO LOG switches in an hour, and to comply with this rule, I have provided queries to verify the production of REDO LOG files within an hour over the course of a month.
In case we need to change the size to decrease or increase the switch frequency, I have provided another query to identify names, sizes, and status of REDO LOG files.
In the REDO LOG Management category, you will find queries to verify the production of REDO LOG files within an hour over the course of a month. Additionally, there is one to view the threads, groups, names, sizes, and status of REDO LOG files.
With the article “Query REDO LOG Switch Count,” we can quickly identify the time periods when the database is in full activity. Furthermore, in case you find numerous messages of “Checkpoint not complete” in the database’s alert log like the following message: Thu Nov 26 15:16:35 2019Thread 1 cannot allocate Read more…
In the article “Query REDO LOG file name and status,” we can see the names of the files composing the groups, their sizes, and the status of Oracle redo logs. Redo log files, essential for data recovery in case of corruptions, are sometimes not sized appropriately for the volume of Read more…