ORA-39358: Export Dump File Version 12.1.0.2.0 Not Compatible With Target Version 11.2.0.4.0 (Doc ID 2121317.1)

 

To Bottom

---

Applies to: Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1] Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Information in this document applies to any platform. Symptoms After upgrading a database from  11.2.0.4 to 12.1.0.2, the following errors are reported executing a datapump import process: impdp <user>/<password> tables=<OWNER>.<TABLE NAME>   Import: Release 12.1.0.2.0 - Production on Mon Mar 28 09:52:37 2016 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Oracle Label Security, OLAP, Advanced Analytics and Real Application Testing options ORA-39002: invalid operation ORA-39358: Export dump file version 12.1.0.2.0 not compatible with target version 11.2.0.4.0   Changes  The importing database was migrated from 11.2.0.4 to 12.1.0.2.0 Cause The issue is because the COMPATIBLE parameter for the 12c importing database is still 11.2.0.4 (value before the upgrade).   It was confirmed based on the information provided: 1. Version of the exporting database 12c (12.1.0.2.0), compatible 12c (12.1.0.2.0) 2. Version of the importing database 12c (12.1.0.2.0), compatible 11g (11.2.0.4.0)   Solution In this case, there are next two solutions: Use the parameter VERSION during the export process. It need to be set equal to the COMPATIBLE parameter value in the target database where the import is going to be executed. Execute the export using parameter version equal to 11.2.0.4: $ expdp <user>/<password> tables=<OWNER>.<TABLE NAME> version=11.2.0.4    Then, execute the import process: $ impdp <user>/<password> tables=<OWNER>.<TABLE NAME> Using this option, the version of the dumpfile version will be matching the compatible parameter on target system (11.2.0.4). - OR - Set compatible to 12.1.0.2.0 on target system: sql> alter system set compatible='12.1.0.2.0' scope=spfile; sql> shutdown immediate; sql> startup; sql> show parameter compatible;