Re: Using DBMS_METADATA/DBMS_REDFINITION to move all objects to another TS

> Question: why are you moving data from your production database to
> another database? Could you use Partitioning + Compression + read-only
> tablespaces etc to accomplish the same goals?

Oh...to dream. :) The logic necessary to archive data from JDEdwards doesn't lend itself well to partitioning for archiving. For example, we need to archive a business work order if and only if its status is greater than a certain value and there has been no business activity on any of the work order lines for three years. This logic spans at least a few tables and several otherwise unrelated columns. And that's an easy case!

That being said, even if we could use them for our EE DB, those options are priced out of our budget. I would love the AC option, which would allow me to retire the deprecated export in favor of DataPump. But since the on-the-fly compression that can be used in export is not an option in DataPump without the AC option, I'm investigating using alternate methods. The $11.5K/Proc list price can buy a lot of disk and RAM. Not my preference, but... :|

Thanks!
Rich

--
http://www.freelists.org/webpage/oracle-l