We recently had a support call from a client that started having performance issues with their P6 database during the pre-work phase of their turnaround. We looked at the Oracle 18.104.22.168 enterprise database and found a massive amount of archive logs being chewed up. In fact, it was on a scale of 1-2 GB of logs within 2-5 minutes on average. With that kind of volume it would not take long for a server to receive the dreaded Oracle error message ORA-00257: archiver error. When this happens the database usually needs more space on the device where the archive log files are stored, which results in the database not allowing any more transactions until the issue is corrected.