Originally posted by KenEwald
Here's another idea...

Upgrade to 10g (which should be available any day, right?) on your source database and use the transportable tablespace feature. The tablespaces will need to be off-line to transport and you'll need to use RMAN to convert the datafiles once they get to the target.

It's not real pretty, but it's an option we don't have in previous versions.

Again, best of luck.
Current limitations for Transportable Tablespace feature:

- The source and target databases must be on the same hardware platform
- The source and target databases must have the same block size
- The source and target databases must have the same character set.
- The transportable set must be self-contained.

And moving to 10g directly without testing ?? Hmmm... that would be one risk that i won't suggest.