[QUOTE][i]Originally posted by macswell [/i]
[B]I agree that the export/import should work. Just a reminder that the export utility does NOT export data from the SYS or SYSTEM schemas (even if you do a FULL export). Therefore, the roles, privileges and users you have defined will not be part of your export. You can generate the role/privilege/user create scripts by querying the original database, then execute them against your target before you do your import. The plus doing it this way (rather than recreating from scratch) is that your users will not have to reset their database passwords (assuming their not "identified externally").

Tim [/B][/QUOTE]
Just a small correction: schema SYSTEM *will be* exported with full exp just like any other user (that is what it realy is: a normal user with DBA privileges). Also all the roles, users, privileges *will be* exported (and also imported). In fact, this is the only way to transfer the users from one database to the others without changing their passwords and without actually knowing their passwords. (If you should try to precreate them with the scripts gathered from your source database dictionary you should use "... IDENTIFIED BY VALUES '....' ...." trick that export uses internaly, but this is another story.)

Sreddy made a good point: you should precreate the tablespaces before importing, because the directory paths are expresed differently on NT and Unix (backslash and slash characters...), so import will fail that part on NT.

Another frequently mistake when transfering .dmp from one machine to the other vith ftp: don't forget to transfer it in binary mode!