-
I'm transporting 4 tablespaces from a 8.1.6.2 production DB to an 8.1.6.2 dev DB on another server. I've completed all the prep steps, exported the metadata, and remote copied the datafiles to the target server. However, when I attempt to import the metadata, I get the following:
Export file created by EXPORT:V08.01.06 via conventional path
About to import transportable tablespace(s) metadata...
import done in US7ASCII character set and WE8ISO8859P1 NCHAR character set
import server uses WE8ISO8859P1 character set (possible charset conversion)
. importing SYS's objects into SYS
IMP-00017: following statement failed with ORACLE error 1565:
"BEGIN sys.dbms_plugts.beginImpTablespace('TNT_DATA',10,'SYS',10,0,16384,2"
",211520805898,1,240,32,16,0,0,1,0,0,3042992015,1,0,32079,NULL,49,447319235,"
"NULL,NULL); END;"
IMP-00003: ORACLE error 1565 encountered
ORA-01565: error in identifying file '/d1u32/oracle/tntdev/datafiles/tnt_indx01.
dbf'
ORA-06512: at "SYS.DBMS_PLUGTS", line 1364
ORA-06512: at line 1
IMP-00000: Import terminated unsuccessfully
It looks as though dbms_plugts is saying either looking for the "tnt_indx" datafile in the tnt_data tablespace, or the metadata is saying that "tnt_indx" datafile belongs to the tnt_data tablespace - both of which is not true. If you need any additional info, plz let me know. Thanx!
-
have you check ??
OS, bock_size and other requirement are the same?? secondly the transport tablespace must be in read only before you tnansprot!!...
-
yes, all are the same between source and target. and yes, the tbs was in read-only mode. the only thing I can think of is that the char sets are supposed to be the same, yet our source export seems to have been done in US7ASCII whereas the target database import is using WE char set. the nat char sets are the same, though. also, I know that TTS has worked for these 2 DBs before. my source DB is no longer available (it was an EMC BCV mirror that's now been reestablished). looks like I'll haveta go with a regular export/import on this.