Hi All,

II 10.0.0 (a64.lnx/132)NPTL + p14061

For God only knows what reason we have a database in which the system has decided to build a 2G journal file.

Trouble is that once the journal gets to 2147484160 (=2G + 512) bytes thearchiver fails.

The log is stuck on 79% full. A restart manages to kick the archiver off, but it builds another 2G journal and fails, and the transaction olog file doesn't shrink.

I've tried to force a journal swap on the database using alterdb but its locked out by the archiver.

Short of blowing away the log file is there anything else that an be done?

Note that according to infodb on the database in question...
Journal block size : 16384
Target journal size : 512

Martin Bowes