Re: Problems when importing on NT

Ernesto schrieb in Nachricht <3ba0cbb4.683397423_at_news.sarenet.es>...
>Hi!
>
>I'm attempting to migrating my database from Unix to NT.
>
>In Unix, my tablespaces are in '/u02/oradata/SID/rbs01.dbf'...
>But in NT I've got my DataBase in 'd:\orant\'.
>
>I succeed in export on Unix (I created a 'devexport.dmp' file), but
>when trying to import on NT, I get this error:
>
>----//----
>Connected to: Oracle8 Release 8.0.5.0.0 - Production
>PL/SQL Release 8.0.5.0.0 - Production
>
>Export file created by EXPORT:V08.00.04 via conventional path
>IMP-00017: following statement failed with ORACLE error 1119:
> "CREATE TABLESPACE "RBS" DATAFILE '/u02/oradata/SID/rbs01.dbf' SIZE
>15728640"
> " DEFAULT STORAGE (INITIAL 131072 NEXT 131072 MINEXTENTS 2
>MAXEXTENTS "
> "121 PCTINCREASE 0) ONLINE PERMANENT"
>IMP-00003: ORACLE error 1119 encountered
>ORA-01119: error in creating database file
>'/u02/oradata/SID/rbs01.dbf'
>ORA-27040: skgfrcre: create error, unable to create file
>OSD-04002: unable to open file
>....
>....
>
>Could anybody give any suggestion?
>
>Thank you very much

Hi Ernesto,

the file path´s of the tablespaces datafiles in the target database often differ from those of the source. You should create the tablespaces with the same names but other datafiles before you import the data. In this case the import utility will not create the tablespaces but will use the precreated tablespaces.

Another question. Did you try full database import ? Normally the target database should be ready configurated including the rollback segments, and there is no need to import the rollback tablespaces.

A full import is critical, because the data dictionary of the target database will be damaged.
It would be a better choice, to do an import by schema. (Dont you have an application owner in the source database ? )

Regs, Lothar Received on Fri Sep 14 2001 - 16:35:17 CEST