Mark, I think if he runs export remotely from another client node - it might not have those settings in sqlnet.ora and that's why it runs fast. Traces cannot be generated on a node different from one where dump file is produced as both dump file and sql net trace file are written on the client. Right? Alex 2006/1/31, Bobak, Mark <Mark.Bobak@xxxxxxxxxxxxxxx>: > It's possible that the combination of the SQL*Net trace writes and the exp > writes are killing your I/O. When the export runs remotely, the SQL*Net > trace writes still happen, but the export writes are on another host..... -- //www.freelists.org/webpage/oracle-l