While the table is in nologging mode, all inserts into the table will not be logged, therefore no redo is generated. Lools like some sort of an I/O problem with the archiving of the redo log files. Check for "heavy" transactions in the db. I wonder if bouncing the db might help??!!