Shulou(Shulou.com)05/31 Report--

Xiaobian to share with you what are the precautions for using different versions of exp/imp in the database. I hope you will gain something after reading this article. Let's discuss it together!

Use different versions of exp/imp

Whenever you migrate data between different versions of an oracle database, you must follow the following basic rules

1. The imp tool version must be the same as the target library version. For example, imp tool version 9.2.0.7 importing into database version 9.2.0.8 encounters errors.

2. The version of the exp tool must be the same as an earlier version in the source or target library.

For example, if you export data from a lower version of the source library exp and imp it into a higher version of the target library, the exp version must be the same as the source library. Similarly,

Export data from a higher-version source library exp, imp import to a lower-version target library, then exp version must be the same as the target library.

Constraints using different versions of exp/imp

1. Dmp files exported by exp tool can only be imported by imp tool. That is to say, exp/imp pairs are used, expdp/impdp pairs are used. Exp exported dmp files cannot be imported with impdp.

2. Any exp exported file can be imp into a higher version of the database. That is, exp/imp is backward compatible.

3. Older versions of the imp tool cannot read files exported by older versions of exp. For example, dmp files exported by 9.2 exp cannot be imported with imp tool version 9.0.1.

4. whenever a lower version of the Export utility runs with a later release of the Oracle database, categories of database objects that did not exist in the earlier release are excluded from the export.

Refer to Table 21-5 at the end of this article for migration data of different versions of exp/imp

Using Different Releases of Export and Import

This section describes compatibility issues that relate to using different releases of Export and the Oracle database.

Whenever you are moving data between different releases of the Oracle database, the following basic rules apply:

The Import utility and the database to which data is being imported (the target database) must be the same release. For example, if you try to use the Import utility 9.2.0.7 to import into a 9.2.0.8 database, then you may encounter errors.

The version of the Export utility must be equal to the release of either the source or target database, whichever is earlier.

For example, to create an export file for an import into a later release database, use a version of the Export utility that equals the source database. Conversely, to create an export file for an import into an earlier release database, use a version of the Export utility that equals the release of the target database.

In general, you can use the Export utility from any Oracle8 release to export from an Oracle9i server and create an Oracle8 export file.

Restrictions When Using Different Releases of Export and Import

The following restrictions apply when you are using different releases of Export and Import:

Export dump files can be read only by the Import utility because they are stored in a special binary format.

Any export dump file can be imported into a later release of the Oracle database.

The Import utility cannot read export dump files created by the Export utility of a later maintenance release. For example, a release 9.2 export dump file cannot be imported by a release 9.0.1 Import utility.

Whenever a lower version of the Export utility runs with a later release of the Oracle database, categories of database objects that did not exist in the earlier release are excluded from the export.

Export files generated by Oracle9i Export, either direct path or conventional path, are incompatible with earlier releases of Import and can be imported only with Oracle9i Import. When backward compatibility is an issue, use the earlier release or version of the Export utility against the Oracle9idatabase.

Examples of Using Different Releases of Export and Import

Table 21-5 shows some examples of which Export and Import releases to use when moving data between different releases of the Oracle database.

Table 21-5 Using Different Releases of Export and Import

Export from->Import toUse Export ReleaseUse Import Release

8.1.6 -> 8.1.6

8.1.6

8.1.6

8.1.5 -> 8.0.6

8.0.6

8.0.6

8.1.7 -> 8.1.6

8.1.6

8.1.6

9.0.1 -> 8.1.6

8.1.6

8.1.6

9.0.1 -> 9.0.2

9.0.1

9.0.2

9.0.2 -> 10.1.0

9.0.2

10.1.0

10.1.0 -> 9.0.2

9.0.2

9.0.2

After reading this article, I believe you have a certain understanding of "what are the precautions for using different versions of exp/imp in the database". If you want to know more about it, welcome to pay attention to the industry information channel. Thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.