Errors and solutions during the process of importing data from Oracle817 to Oracle10.2.0.4

1. Error 1: the RBS and TEMP tablespaces cannot be created.

IMP-00017: following statement failed with Oracle error 1119:
"Create tablespace" RBS "DATAFILE 'd: \ ORACLE \ ORADATA \ ORCL \ RBS01.DBF 'size 5"
"45259520 autoextend on next 5242880 MAXSIZE 16383 m default storage ("
"INITIAL 524288 NEXT 524288 MINEXTENTS 8 MAXEXTENTS 4096 PCTINCREASE 50) ONL"
"Ine permanent"
IMP-00003: ORACLE error 1119 encountered
ORA-01119: error in creating database file 'd: \ ORACLE \ ORADATA \ ORCL \ RBS01.DBF'
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) the system cannot find the specified path.
IMP-00017: following statement failed with ORACLE error 12913:
"Create tablespace" TEMP "DATAFILE 'd: \ ORACLE \ ORADATA \ ORCL \ TEMP01.DBF 'size"
"127270912 autoextend on next 655360 MAXSIZE 16383 m default storage"
"(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 )"
"Online temporary"
IMP-00003: ORACLE error 12913 encountered
ORA-12913: Cannot create dictionary managed tablespace

RBS is the tablespace of the rollback segment of oracle817, with no data in it. When it reaches 10 Gb, the rollback segment method has changed. It uses the UNDOTBS1 tablespace, which has been created, so it gives up.

TEMP is a temporary tablespace of oracle817 with no data, and the 10 Gb temporary tablespace no longer uses the dictionary management mode, but adopts the local management mode. This is outdated, so give up.

2. Error 2:
IMP-00017: following statement failed with ORACLE error 3249:
"Create tablespace" TOOLS "DATAFILE 'd: \ ORACLE \ ORADATA \ ORCL \ TOOLS01.DBF 'si"
"ZE 18481152 autoextend on next 327680 MAXSIZE 16383 m default storag"
"E (INITIAL 32768 NEXT 32768 MINEXTENTS 1 MAXEXTENTS 4096 PCTINCREASE 0) ONLI"
"Ne permanent"
IMP-00003: ORACLE error 3249 encountered
ORA-03249: Uniform. size for auto segment space managed tablespace shocould have atleast 5 blocks
TOOLS is the tool tablespace of oracle817. It mainly manages the default tablespace of the user SYSTEM. At oracle817, I cannot analyze whether there are data objects in the TOOLS tablespace, so it is better to import the table space, the reason is that the TOOLS tablespace has not been created. Therefore, when importing the table, the import program considers the table to be created, but the table cannot be created. An error is returned.
Solution: add TOOLS tablespace creation in the statement for creating a tablespace in oracle10g.

3. Error 3:
IMP-00017: following statement failed with ORACLE error 959:
"Alter user" SYSTEM "identified by values 'd4df7931ab130e37 'default tablesp"
"ACE" TOOLS "temporary tablespace" TEMP ""
IMP-00003: ORACLE error 959 encountered
ORA-00959: tablespace 'tool' does not exist
This error occurs because the default SYSTEM user tablespace of oracle817 is in TOOLS. Therefore, during the import, the creation of the TOOLS tablespace fails.
Solution: as long as the TOOLS tablespace is created, the error will disappear. :

4. Error 4:
IMP-00017: following statement failed with ORACLE error 1031:
"Create database link" DATA_LINK.WORLD "connect to" DATA "identified by" DATA ""
"USING 'ora7 '"
IMP-00003: ORACLE error 1031 encountered
ORA-01031: insufficient privileges
I imported a SYSTEM user. It seems that the SYSTEM user has insufficient permissions, but this is useless, so I gave up the creation. If I want to use it later, I can create it separately.

5. Error 5: This is the most critical record. I wrote this record because it may be hard to understand.
IMP-00017: following statement failed with ORACLE error 20005:
"Declare srec DBMS_STATS.STATREC; begin srec. MINVAL: = NULL; SREC. MAXVAL: ="
"NULL; SREC. EAVS: = 0; SREC. CHVALS: = NULL; SREC. NOVALS: = DBMS_STATS.NUMAR"
"RAY (0, 0); SREC. BKVALS: = DBMS_STATS.NUMARRAY (0, 1); SREC. EPC: = 2; DBMS_STAT"
"S. SET_COLUMN_STATS (NULL, '" DEF $ _ AQERROR "', '" prediction_queue "', NULL, NULL, NU"
"LL, 0, 0, 0, srec, 0, 2); END ;"
IMP-00003: ORACLE error 20005 encountered
ORA-20005: object statistics are locked (stattype = ALL)
ORA-06512: at "SYS. DBMS_STATS", line 1610
ORA-06512: at "SYS. DBMS_STATS", line 2120
ORA-06512: at "SYS. DBMS_STATS", line 5010
ORA-06512: at line 1
This error is a bit strange. The main error is the object statistics are locked (stattype = all). After query, it is found that the cause of this error is the database statistics. But the deeper reasons are unclear. For the moment, because the default import policy is statistics = always, this policy requires that the original database statistics be imported. This policy is still a bit problematic, database statistics. Because a new database version is used, the original statistics are about 80% incorrect, so why is the default Import Policy statistics = always. Therefore, I decided not to import or re-collect database statistics.
Solution: add the statistics = none parameter at the end of the imp command. This parameter requires that the database statistics be not imported or recalculated.

6. Error 6:
IMP-00017: following statement failed with ORACLE error 2270:
"Alter table" DEF $ _ CALLDEST "add constraint" DEF $ _ CALL_DESTINATION "FOREIGN"
"KEY (" DBLINK ") REFERENCES" DEF $ _ DESTINATION "(" DBLINK ") enable novalidate"
IMP-00003: ORACLE error 2270 encountered
ORA-02270: no matching unique or primary key for this column-list
This error is a bit comedy. After comparing the table structure of oracle817 and oracle10g in the same table, we found that oracle10g has this foreign key, and it seems better than oracle817. So I gave up.
Solution: Ignore.