Actually, that is the approach we are taking, however one tablespace is about 1.5 TB, so that one is out of the question... Guillermo Alan Bort DBA / DBA Main Team EDS, an HP company ITO Arias 1851 Ciudad Autonoma de Buenos Aires (C1429DXC) Argentina Tel: +54 11 4704-3132 E-mail: guillermo.bort@xxxxxxx We deliver on our commitments so you can deliver on yours. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Joerg Jost Sent: Friday, November 28, 2008 11:35 AM To: Oracle Mailinglist Subject: Re: 8i-10g upgrade Hi there, i do things like this very often because of my job. But i did not do this with databases so large. So please read my suggestions with this in mind :) But my suggestion is, do this Tablespace for Tablespace. If i got you, you have more than 2 or 3 of them. So do the datapump for one after the other. This will result in some possible positive sideeffects. You do not need the space of the hole database twice. You do not need so much downtime per Tablespace. You will have (probably) parts of the application online. (Depends on the architecture of SAP). In front of each import you can drop the old Tablespace to save the space. Maybe this is a way to solve this "timing" problem? bye Jörg Jost OCP 10gR2 -- //www.freelists.org/webpage/oracle-l ��i��0���zX���+��n��{�+i�^