Question:
When the automatic purging of our Oracle database occurs, the purge fails with the following error:
ERROR An error occurred while purging the audit logs for service 'FTP'
com.linoma.dpa.dao.DAOException: ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS1'
at com.linoma.dpa.dao.rdbms.GFTPAuditLogDAOImpl.purge(Unknown Source)
at com.linoma.dpa.scheduler.AuditLogMonitor.purgeGFTPLog(Unknown Source)
at com.linoma.dpa.scheduler.AuditLogMonitor.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Answer:
Oracle databases contain an UNDO tablespace, which contains necessary information to rollback changes to the database. Detailed information about the UNDO tablespace can be found here: https://docs.oracle.com/cd/B19306_01/se ... 1/undo.htm
Purging of the GoAnywhere database usually occurs in smaller increments over a larger period of time. However, if the purge is large enough, the UNDO tablespace will run out of room thus throwing the above error. You will need to allocate additional resources to the UNDO tablespace in order to accommodate the size of the purge.
Database Explanation:
https://stackoverflow.com/questions/432 ... tablespace
Auto extend the UNDO tablespace:
http://www.dba-oracle.com/t_undo_tables ... extend.htm