Comments on: Oracle is full! http://jfw.id.au/2005/03/26/oracle-is-full/ the mutterings of a part time nutcase. Sun, 20 May 2012 08:07:53 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Me. http://jfw.id.au/2005/03/26/oracle-is-full/comment-page-1/#comment-6 Me. Sun, 03 Apr 2005 10:17:49 +0000 http://www.jfw.id.au/2005/03/28/oracle-is-full/#comment-6 The processes that can be run manually to clean up the archive log destination and the catalogue can also be scheduled to run. Needless to say this has been done, and we should not see this problem repeat itself any time soon. The only exception would be if the volume of transactions reaches that of the boxes a friend of mine looks after. Currently they write approximately 2Gb of logs every 15 minutes. *eeeek* The processes that can be run manually to clean up the archive log destination and the catalogue can also be scheduled to run. Needless to say this has been done, and we should not see this problem repeat itself any time soon.

The only exception would be if the volume of transactions reaches that of the boxes a friend of mine looks after. Currently they write approximately 2Gb of logs every 15 minutes.
*eeeek*

]]> By: Alistair http://jfw.id.au/2005/03/26/oracle-is-full/comment-page-1/#comment-5 Alistair Fri, 01 Apr 2005 14:41:37 +0000 http://www.jfw.id.au/2005/03/28/oracle-is-full/#comment-5 I'm still surprised that when you moved the logs away, that Oracle didn't pick up that the catalogue and the file system were not in sync. What do you suppose a reasonable reason would be for not automatically cleaning the catalogue when logs are moved away? I appreciate that they have the functionality to manually do it, however at the same time; I'm not seeing an obvious reason for a catalogue to say 'Yes, we have 40Gb of logs present' when in fact the file system is saying 'No, we actually have 2Gb at the moment'. I’m still surprised that when you moved the logs away, that Oracle didn’t pick up that the catalogue and the file system were not in sync.

What do you suppose a reasonable reason would be for not automatically cleaning the catalogue when logs are moved away? I appreciate that they have the functionality to manually do it, however at the same time; I’m not seeing an obvious reason for a catalogue to say ‘Yes, we have 40Gb of logs present’ when in fact the file system is saying ‘No, we actually have 2Gb at the moment’.

]]>