Excessive archvelog creation

	Redhat Linux 6.2
	Application (in case it matters Deltek Cobra)

I came into the office one morning a few weeks ago and discovered that the above application had devoured 500 gb of archivelog space in a period of about five hours over the previous night. Fortunately, this was on the development database server.

I ran an awr report for the time period in question and it listed the following statement executed 3740 times:

UPDATE PROCESSLOG SET DATA = CONCAT(DATA,:B2 ) WHERE ROW_UID = :B1 The DATA column is clob and, based on timestamps that the application writes to the table I located the row to which that data was being added. DBMS_CLOB.GETLENGTH shows the size of the clob in that row as 48 mb.

So my questions are: