DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: error during import dmp....

  1. #1
    Join Date
    Jul 2002
    Posts
    228

    error during import dmp....

    hi,
    I did these steps:
    CREATE TABLESPACE AFM_P1 DATAFILE 'c:\....\AFM_P01.dbf' SIZE 1700M EXTENT MANAGEMENT LOCAL UNIFORM;
    CREATE USER AFM_SECURE IDENTIFIED BY AFM DEFAULT TABLESPACE AFM_P1 TEMPORARY TABLESPACE TEMP;
    CREATE USER AFM IDENTIFIED BY AFM DEFAULT TABLESPACE AFM_P1 TEMPORARY TABLESPACE TEMP;
    GRANT CONNECT, RESOURCE, CREATE SYNONYM TO AFM;
    GRANT CONNECT, RESOURCE TO AFM_SECURE;

    imp system/manager@mydb fromuser=afm_secure touser=afm_secure file=C:\...\mydump.dmp log=C:\..\mylog.log

    BUT I GET THESE ERRORS:
    Connected to: Oracle9i Enterprise Edition Release 9.0.1.1.1 - Production
    With the Partitioning option
    JServer Release 9.0.1.1.1 - Production

    Export file created by EXPORT:V09.02.00 via conventional path
    import done in WE8DEC character set and AL16UTF16 NCHAR character set
    import server uses WE8MSWIN1252 character set (possible charset conversion)
    export client uses WE8MSWIN1252 character set (possible charset conversion)
    . importing AFM_SECURE's objects into AFM_SECURE
    IMP-00017: following statement failed with ORACLE error 6550:
    "BEGIN "
    "sys.dbms_logrep_imp.instantiate_schema(schema_name=>'AFM_SECURE', export_db"
    "_name=>'CENTOS.US.ORACLE.COM', inst_scn=>'809152');"
    "COMMIT; END;"
    IMP-00003: ORACLE error 6550 encountered
    ORA-06550: line 2, column 1:
    PLS-00201: identifier 'SYS.DBMS_LOGREP_IMP' must be declared
    ORA-06550: line 2, column 1:
    PL/SQL: Statement ignored
    IMP-00017: following statement failed with ORACLE error 922:
    "CREATE TABLE "AFM_GROUPS" ("GROUP_NAME" VARCHAR2(10) NOT NULL ENABLE, "GROU"
    "P_TITLE" VARCHAR2(128), "WW_PREFERENCES" VARCHAR2(2000)) PCTFREE 10 PCTUSE"
    "D 40 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 16384 FREELISTS 1 FREELIST GRO"
    "UPS 1) TABLESPACE "AFM_P1" LOGGING NOCOMPRESS"
    IMP-00003: ORACLE error 922 encountered
    ORA-00922: missing or invalid option
    IMP-00017: following statement failed with ORACLE error 922:
    "CREATE TABLE "AFM_USERS" ("USER_NAME" VARCHAR2(32) NOT NULL ENABLE, "GROUP_"
    "1" VARCHAR2(10), "GROUP_10" VARCHAR2(10), "GROUP_2" VARCHAR2(10), "GROUP_3""
    " VARCHAR2(10), "GROUP_4" VARCHAR2(10), "GROUP_5" VARCHAR2(10), "GROUP_6" VA"
    "RCHAR2(10), "GROUP_7" VARCHAR2(10), "GROUP_8" VARCHAR2(10), "GROUP_9" VARCH"
    "AR2(10), "USER_LEVEL" NUMBER(*,0), "USER_PWD" VARCHAR2(10)) PCTFREE 10 PCT"
    "USED 40 INITRANS 1 MAXTRANS 255 STORAGE(INITIAL 16384 FREELISTS 1 FREELIST "
    "GROUPS 1) TABLESPACE "AFM_P1" LOGGING NOCOMPRESS"
    IMP-00003: ORACLE error 922 encountered
    ORA-00922: missing or invalid option
    IMP-00008: unrecognized statement in the export file:
    yýu
    IMP-00008: unrecognized statement in the export file:
    R
    IMP-00008: unrecognized statement in the export file:

    What I wrong? or dmp file is corrupted??

    Thanks
    Raf

  2. #2
    Join Date
    Jun 2003
    Location
    India
    Posts
    118
    Hi

    Check two things

    1. Whether u have Granted IMP_FULL_DATABASE

    2. The Quota on default tablespace given to user.

    Vishal Sood
    vishal sood
    OCP 8

  3. #3
    Join Date
    May 2002
    Location
    England
    Posts
    78
    Hi There,

    You need to use the 9.0.1 export file utility to run your export instead of the 9.0.2 export file.

    See the information below from metalink.

    Cheers
    John


    Hi. In order to generate an export file from the 9.2 database that can be imported into a 9.0.1 database, you need to run the 9.0.1 export executable from the 9.0.1 $ORACLE_HOME against the 9.2 database connecting to it via Oracle Net.

    Please refer to information in Chapter 1 of the Oracle9i Utilities, Release 2 guide under the section titled: Using Different Releases and Versions of Export.

  4. #4
    Join Date
    Jul 2003
    Location
    Sofia, Bulgaria
    Posts
    91
    The wrong part is the option compress (new in 9.2). So if you cant export again, you can edit the dmp file with hex editor and to replace NOCOMPRESS with spaces. Or you can make export from lower version home as jperusco has sugested.
    For the first mistake - grant execute on SYS.DBMS_LOGREP_IMP to the user.
    Hope that helps

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width