Can someone please explain what redo is generated by sqlldr direct path when unrecoverable is specified but archive logging is on. The sqlldr documentation seems to suggest that the amount of redo generated depends upon whether archive logging in set on or not. I have a scenerio where a sqlldr directp path load is taking far longer on a system with archive logging set on then one where archive logging is on...could archive logging be the problem? John -- //www.freelists.org/webpage/oracle-l