Oracle unix export --> Windows import both versions the same 8.1.7

[Brian Crabtree]

What could be happening in this case is that the user does not have the appropriate roles on the export database to create the objects that it owns (possible if someone with CREATE ANY TABLE created the objects). You can verify this by running the import with the "log=" option, or creating the user manually and importing with a "fromuser=" and "touser=" to import only that user. The fromuser and touser will not create a user, while the "full=y" will create and modify users automaticlly.

Hope this helps,

Thanks,

Brian

[Steven E. Protter]

If by chance this has been a mirgration from a 32 bit to a 64 bit platform, there are word size issues. If not, ignore this post. Oracle document attached. Just in case.

SEP

[Yogeeraj_1]

hi,

As Brian said, you need to grant the user rights to create tables.

grant create table to coast;

should be OK.

However, the user coast may own other objects.

I would prefer to grant connect and resource system privileges that will give him more "powerful" rights...at least during the import period. (as in my previous post)

you can later revoke that and grant him "create session" and any other desired system privileges. e.g. create table, create procedure, etc.

Hope this helps!
Yogeeraj

[Indira Aramandla · Accepted solution]

When you are given the export dumpm file and you want to import into your database, you should know what schemas (users) exists in the export file, what roles and DB_LINKS. You can find all of these by doing a dummy import with SHOW=Y parameter.
eg: imp system/manager@sid fully=y show=y file=exp_dump_file log=log_file_name. THis command will not import the objects but create a log for you which will contain the users, roles and tables with the data.
Look in the log and then note down the users, roles in the import log. You can open the log file in winword and search for "USER" and "ROLE". This will give you users and roles from the export file. Then create the users and roles in the target database as
create identified by default tablespace temporary tablespace temp;

create role ;

Then do the import as
imp system/manager@sid buffer=1024000 full=y commit=y file=exp_file log=imp_log.log

When the import occurs the messages fly off on the screen, but they will be recorded in the log file. You can verify the log for any errors.

[PAVIC Thierry]

Hi
I'm not sure that you can make a simple operation of exp/imp with a different OS.
I think that you don't use the option compress=y.
Check this way on metalink.
I remeber have some trouble in using compress option with a situation similar as you.

Best regards Thierry

[exrational]

ok i solved it

for any one that has to do this in future here is the answer

create the user foouser that is the schema for the tablespace.

then create the table space

create tablespace foo datafile 'c:\oracle\foo.dbf' size 1000M;

then run the import as mentioned above

then the data and tables import :)

the table space can not be created becaue the dbf file was tying to be put in in foo/local/......

windows needs a c:\foo
and thats where it was messing up

[Yogeeraj_1]

hi,

glad to know that you managed to fix the problem.

again, Locally managed tablespaces would be recommended.

best regards
Yogeeraj