Does anyone have any insight as to why taking an export w/ rows=n would take many, many hours? Details are as follows: Solaris 8, running Oracle 9.2.0.6, 64 bit Schema being exported has 2,451 tables. Parameter file being used is: userid=system/<password removed> file=proddta_jdeprd_nodata.dmp log=exp_proddta_jdeprd_nodata.log rows=n owner=proddta direct=y Yes, I'm aware that direct=y won't do anything w/ rows=n, but it ought to be harmless. Export session has been running for 18 hours. V$SESSION_WAIT shows db file sequential read waits, and some of the queries are: SELECT COLNAME, COLNO, PROPERTY FROM SYS.EXU9CCL WHERE CNO = :1 ORDER BY COLNO; SELECT SYNNAM, SYNNAM2, SYNTAB, TABOWN, TABNODE, PUBLIC$, SYNOWN, SYNOWNID, TABOWNID, SYNOBJNO FROM SYS.EXU9PTS WHERE SYNOBJNO IN ( SELECT SYNOBJNO FROM SYS.EXU9TYPT WHERE TABOBJNO = :1 ) ORDER BY SYNTIME Anyone have any ideas or clues why it would take 18+ hours to do a rows=n export of less than 2,500 tables? Thanks, -Mark -- Mark J. Bobak Senior Oracle Architect ProQuest Information & Learning For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. --Richard P. Feynman, 1918-1988