An example of solution to system downtime caused by full archiving logs of Oracle databases

An example of solution to system downtime caused by full archiving logs of Oracle databases

When the first downtime occurs, the system memory overflows. Therefore, the application server is restarted and an error is reported when the application server is started. The error is that the Oracle database cannot be connected. Connect to the database server, open EM, and the system reports an error.

The error message "archive log writing failed" is displayed. Check whether the disk space is full on the server. After the disk space is cleared, restart the database to solve the problem. Then, the server disk space is resized, and 1 TB of disk space is directly allocated to the oracle data disk. This problem occurs again for the second time. After careful check and confirmation with colleagues, it is found that the archive log of the ORACLE database is enabled, by default, the ORACLE database archiving function is not enabled. Run the SQL command to View Details: