Import: Release 10.2.0.3.0 - Production on Mon Dec 3 13:01:09 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the Partitioning, OLAP and Data Mining options Export file created by EXPORT:V10.02.01 via conventional path About to import transportable tablespace(s) metadata... import done in AR8MSWIN1256 character set and UTF8 NCHAR character set import server uses AR8ISO8859P6 character set (possible charset conversion) export client uses AR8ISO8859P6 character set (possible charset conversion) . importing SYS's objects into SYS . importing SYS's objects into SYS IMP-00017: following statement failed with ORACLE error 721: "BEGIN sys.dbms_plugts.checkCompType('COMPATSG','10.2.0.3.0'); END;" IMP-00003: ORACLE error 721 encountered ORA-00721: changes by release 10.2.0.3.0 cannot be used by release 10.2.0.0.0 ORA-06512: at "SYS.DBMS_PLUGTS", line 2004 ORA-06512: at line 1 IMP-00000: Import terminated unsuccessfullyRegards
Tuesday, December 04, 2007
Issues with COMPATIBLE Initialization Parameter
Hello, I was trying to transport a tablespace from one database (Prod_A) to another (Prod_B), both of which are running on Oracle 10g Release 2 (10.2.0.3). I took metadata export and ftp'ed both export dump and datafiles to the destination database server. While trying to import into Prod_B, I received "ORA-00721: changes by release 10.2.0.3.0 cannot be used by release 10.2.0.0.0" error. I cross checked version of both the databases by querying V$VERSION and found that both were on 10.2.0.3, but still Oracle complains about different versions. Then, I had a look at COMPATIBLE initialization parameter of both the databases. This parameter was set to "10.2.0.3" on Prod_A, but on Prod_B it was "10.2.0". I changed this parameter on Prod_B and bounced database. Everything went fine and I was able to import tablespace into Prod_B. Following is the import log where import terminated unsuccessfully.