العبارة التالية تظهر عند عمل الامبورت من ملف دي ام بي .ارجو المساعد مع العلم ان النسخة المعمول بها النسخة الاحتياطية هي 9.2 بينما اقوم باستيرادها الى نسخة 9.0.1
"CREATE TABLE "YOUTH_HOUSING_PAYMENTS" ("DOC_NO" VARCHAR2(20), "REG_NO" NUMB" "ER(10, 0), "REG_CAT" VARCHAR2(1), "REG_STAGE" NUMBER(1, 0), "PAY_MONTH" NUM" "BER(2, 0), "PAY_YEAR" NUMBER(4, 0), "PAY_DATE" DATE, "AMOUNT" NUMBER(20, 4)" ", "LATE_INT_AMOUNT" NUMBER(20, 4)) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRA" "NS 255 STORAGE(INITIAL 65536 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE "USE" "RS" LOGGING NOCOMPRESS"IMP-00003: ORACLE error 922 encounteredORA-00922: missing or invalid optionIMP-00017: following statement failed with ORACLE error 922: "CREATE TABLE "ZIMMA" ("CLIENT_NO" NUMBER(10, 0), "DEC_NO" VARCHAR2(10), "DE" "C_DATE" DATE, "DEC_TEXT" VARCHAR2(80)) PCTFREE 10 PCTUSED 40 INITRANS 1 MA" "XTRANS 255 STORAGE(INITIAL 16384 FREELISTS 1 FREELIST GROUPS 1) TABLESPACE " ""USERS" LOGGING NOCOMPRESS"IMP-00003: ORACLE error 922 encounteredORA-00922: missing or invalid optionIMP-00017: following statement failed with ORACLE error 2248: "ALTER SESSION SET "_LOAD_WITHOUT_COMPILE" = PLSQL"IMP-00003: ORACLE error 2248 encounteredORA-02248: invalid option for ALTER SESSIONIMP-00015: following statement failed because the object already exists: "CREATE FUNCTION GET_PERIOD" " (NOF_BONDS NUMBER)" "RETURN NUMBER" "IS" " V_COUNT NUMBER ;" "CURSOR Invnt IS" " Select PERIOD_NO from Loan_Period Where" " Period_length>= NOF_BONDS" " Order by period_length DESC;" "BEGIN" "For Invnt_rec in invnt loop" "V_COUNT := Invnt_rec.PERIOD_NO;" "end loop ;" "RETURN V_COUNT ;" "END GET_PERIOD ;"IMP-00017: following statement failed with ORACLE error 2248: "ALTER SESSION SET "_LOAD_WITHOUT_COMPILE" = NONE"IMP-00003: ORACLE error 2248 encounteredORA-02248: invalid option for ALTER SESSIONImport terminated successfully with warnings.20/12/2008 06:56:10 ?: Done

Oracle can import only from old version to a newer version so you can import 9.0 dump to 9.2 dump not from 9.2 to 9.0 so you must a work around to solve your problem

1-upgrade your 9.0 database to be 9.2

or

2-use 9.0 EXP utility to export the dump file again of 9.2 database using the tnsnames service name of 9.2 database like this
EXP hr@orcl92 file=new.dmp log=new
at this moment your dump file (new.dmp) will be of the version 9.0 so you can import it on 9.0 database with the normal import utility

بداية شكر لك...وجدت التالي في احد المواقع:

Using Different Releases and Versions of Export

This section describes compatibility issues that relate to using different releases of Export and the Oracle database server.
Whenever you are moving data between different releases of the Oracle database server, the following basic rules apply:
• The Import utility and the database to which data is being imported (the target database) must be the same version.
• The version of the Export utility must be equal to the lowest version of the source or target database.
For example, to create an export file for an import into a higher release database, use a version of the Export utility that is equal to the source database. Conversely, to create an export file for an import into a lower release database, use a version of the Export utility that is equal to the version of the target database. The following information is for specific versions:
o When you create an Oracle version 6 export file from an Oracle7 database by running the Oracle version 6 Export utility against the Oracle7 database server, you must first run the catexp6.sql script on the Oracle7 database. This script creates the export views that make the database look, to Export, like an Oracle version 6 database.
o When you create an Oracle7 export file from an Oracle8i database by running the Oracle7 Export utility against the Oracle8i database, you must first run the catexp7.sql script on the Oracle8i database. This script creates the export views that make the database look, to Export, like an Oracle8i database.
________________________________________
Note:
The catexp6.sql and catexp7.sql scripts must be run by user SYS. These scripts only need to be run once.
________________________________________
o In general, you can use the Export utility from any Oracle8 release to export from an Oracle9i server and create an Oracle8 export file. See Creating Oracle Release 8.0 Export Files from an Oracle9i Database.
Restrictions When Using Different Releases and Versions 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 higher release of the Oracle database server.
• The Import utility can read export dump files created by Export release 5.1.22 and higher.
• The Import utility cannot read export dump files created by the Export utility of a higher maintenance release or version. For example, a release 8.1 export dump file cannot be imported by a release 8.0 Import utility, and a version 8 export dump file cannot be imported by a version 7 Import utility.
• The Oracle version 6 (or earlier) Export utility cannot be used against an Oracle8 or higher database.
• Whenever a lower version of the Export utility runs with a higher version of the Oracle database server, categories of database objects that did not exist in the lower version are excluded from the export. For example, partitioned tables did not exist in the Oracle database server version 7. So, if you need to move a version 8 partitioned table to a version 7 database, you must first reorganize the table into a nonpartitioned table.
• 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 Oracle9i database.
Examples of Using Different Releases of Export and Import
Table 1-6 shows some examples of which Export and Import releases to use when moving data between different releases of the Oracle database server.
Table 1-6 Using Different Releases of Export and Import
Export from->Import to Use Export Release Use Import Release
7.3.3 -> 8.1.6 7.3.3 8.1.6
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
8.1.7 -> 7.3.4 7.3.4Foot 1
7.3.4
9.0.1 -> 8.1.6 8.1.6 8.1.6
9.0.1 -> 9.0.2 9.0.1 9.0.2
1 If catexp7.sql has never been run on the 8.1.7 database, then you must do that first to create the Oracle7 data dictionary views. Only then can you successfully use Export release 7.3.4 on the release 8.1.7 database.



Creating Oracle Release 8.0 Export Files from an Oracle9i Database
You do not need to take any special steps to create an Oracle release 8.0 export file from an Oracle9i database. However, the following features are not supported when you use Export release 8.0 on an Oracle9i database:
• Export does not export rows from tables containing objects and LOBs when you have specified a direct path load (DIRECT=y).
• Export does not export dimensions.
• Functional and domain indexes are not exported.
• Secondary objects (tables, indexes, sequences, and so on, created in support of a domain index) are not exported.
• Views, procedures, functions, packages, type bodies, and types containing references to new Oracle9i features may not compile.
• Objects whose DDL is implemented as a stored procedure rather than SQL are not exported.
• Triggers whose action is a CALL statement are not exported.
• Tables containing logical ROWID columns, primary key refs, or user-defined OID columns will not be exported.
• Temporary tables are not exported.
• Index-organized tables (IOTs) revert to an uncompressed state.
• Partitioned IOTs lose their partitioning information.
• Index types and operators are not exported.
• Bitmapped, temporary, and UNDO tablespaces are not exported.
• Java sources, classes, and resources are not exported.
• Varying-width CLOBs, collection enhancements, and LOB-storage clauses for VARRAY columns or nested table enhancements are not exported.
• Fine-grained access control policies are not preserved.
• External tables are not exported.