Imp error: ORACLE error 1400 encountered
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Imp error: ORACLE error 1400 encountered

  1. #1
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322

    Imp error: ORACLE error 1400 encountered

    I am facing the following error repeatedly while doing import using imp:


    . . importing table "MAM_ASSETS"
    IMP-00019: row rejected due to ORACLE error 1400
    IMP-00003: ORACLE error 1400 encountered
    ORA-01400: cannot insert NULL into ("QUARKDMS"."MAM_ASSETS"."INDEX_SOURCE")
    Column 1 413212
    Column 2 65678
    Column 3 65780
    Column 4 21
    Column 5
    Column 6 2
    Column 7 0
    Column 8 1
    Column 9 1
    Column 10 1
    Column 11 0
    Column 12 412553
    Column 13 4
    Column 14
    Column 15 7 5 E 20 19
    Column 16 7 5 e 20 19
    Column 17
    Column 18
    Column 19 25902
    Column 20 2
    Column 21 30-AUG-2002:13:26:54
    Column 22
    Column 23 30-AUG-2002:13:26:54
    Column 24
    Column 25 10-SEP-2002:10:14:13
    Column 26 JPEG
    Column 27 14-OCT-2005:14:49:58
    Column 28 jpeg
    Column 29 8BIM
    Column 30
    Column 31 8bim
    Column 32 65780
    Column 33 65715
    Column 34 65874
    Column 35 65617
    Column 36 005400010108000000010000000100000009158700000A3C00...
    Column 37
    Column 38 14-OCT-2005:14:49:58
    Column 39 1
    Column 40 65874
    Column 41 02-SEP-2002:13:28:51
    Column 42
    Column 43
    Column 44 005400010208000000010000000100000025B2330008AA8200...
    Column 45 US
    IMP-00019: row rejected due to ORACLE error 1400



    I searched google, it's of no help in my case. I also disabled constraints import. Though constraints get enabled after importing rows, still I cleared my doubt. What else can be done?
    lucky

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    the error is perfectly clear

    cannot insert NULL into ("QUARKDMS"."MAM_ASSETS"."INDEX_SOURCE")

    stop trying to insert nullls into the column

  3. #3
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    Quote Originally Posted by davey23uk View Post
    the error is perfectly clear

    cannot insert NULL into ("QUARKDMS"."MAM_ASSETS"."INDEX_SOURCE")

    stop trying to insert nullls into the column

    It's import which is inserting. How can I control it. The column is BLOB type.

    Structure of mam_assets is:

    Code:
    ID                                        NOT NULL NUMBER(10)
     ACL_ID                                    NOT NULL NUMBER(10)
     ASSET_GROUP_XID                           NOT NULL NUMBER(10)
     NEW_VERSION_ASSET_ID                               NUMBER(10)
     CONTAINED_IN_COUNT                        NOT NULL NUMBER(6)
     CONTAINER_OF_COUNT                        NOT NULL NUMBER(6)
     RELATED_WITH_COUNT                        NOT NULL NUMBER(6)
     ARCHIVE_STATUS                            NOT NULL NUMBER(1)
     IS_CURRENT_VERSION                        NOT NULL NUMBER(1)
     STORAGE_CHANGE_REQUEST                    NOT NULL NUMBER(1)
     HAS_HISTORY                               NOT NULL NUMBER(1)
     FAMILY_ID                                 NOT NULL NUMBER(10)
     CHECKED_OUT_BY                                     NUMBER(10)
     NAME                                               VARCHAR2(255)
     LC_NAME                                            VARCHAR2(255)
     CHECKOUT_LOCATION                                  VARCHAR2(255)
     LC_CHECKOUT_LOCATION                               VARCHAR2(255)
     ASSET_SIZE                                         NUMBER
     REVISION                                           NUMBER
     FILE_DATE_LAST_MODIFIED                            DATE
     FILE_DATE_CREATED                                  DATE
     FILE_EXTENSION                                     VARCHAR2(255)
     FILE_TYPE                                          VARCHAR2(255)
     FILE_CREATOR_APPLICATION                           VARCHAR2(255)
     LC_FILE_EXTENSION                                  VARCHAR2(255)
     LC_FILE_TYPE                                       VARCHAR2(255)
     LC_FILE_CREATOR_APPLICATION                        VARCHAR2(255)
     DATE_CREATED                                       DATE
     DATE_LAST_MODIFIED                                 DATE
     DATE_CHECKED_OUT                                   DATE
     OWNER                                              NUMBER(10)
     CREATED_BY                                         NUMBER(10)
     LAST_MODIFIED_BY                                   NUMBER(10)
     DESTINATION_ID                                     NUMBER(10)
     LAST_ACTIVITY_ID                                   NUMBER(10)
     LAST_ACCESSED_BY                                   NUMBER(10)
     DATE_LAST_ACCESSED                                 DATE
     PREVIOUS_REVISION                                  NUMBER
     FIRST_VERSION_CREATED_BY                           NUMBER(10)
     FIRST_VERSION_DATE_CREATED                         DATE
     FTS_TEXT_MC                                        CHAR(1)
     FTS_TEXT_UC                                        CHAR(1)
     FTS_TEXT                                  NOT NULL CLOB
     FTS_LANG                                  NOT NULL VARCHAR2(3)
     INDEX_SOURCE                              NOT NULL BLOB
    lucky

  4. #4
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    Quote Originally Posted by mahajanakhil198 View Post
    INDEX_SOURCE NOT NULL BLOB[/CODE]
    Either fix the data or make column nullable - only you know if this is acceptable according to business rules.
    Pablo (Paul) Berzukov

    Author of Understanding Database Administration available at amazon and other bookstores.

    Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

  5. #5
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,333
    crikey - why cant you understand it - you are trying to insert nulls into a not null common

    this is very very basic

  6. #6
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    Dave and PAVB, I understood.

    I separately created the table MAM_ASSETS and removed NOT NULL from problematic columns. Then I used ignore=y option to import. But somewhere while importing, it creates NOT NULL constraints on these columns and I again start receiving the same error.

    What can I do here? How could I remove the code from import that creates NOT NULL constraints?

    Or as a workaround, I am able import only MAM_ASSETS table. But now the problem is that I don't want to import MAM_ASSETS while importing the rest of schema. IMP doesn't provide something like exclude as in IMPDP.
    Last edited by mahajanakhil198; 05-13-2010 at 10:12 AM.
    lucky

  7. #7
    Join Date
    Dec 2002
    Posts
    60
    Can you drop the existing table and let import create the table and import data.

  8. #8
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    IMP doesn't provide something like exclude as in IMPDP.
    Akhil - look into constraints=n and indexes=n imp options.

    how many tables you are trying to import? if you don't want to use constraints=n indexes=n then provide individual table names to imp excluding the one you have already imported.

    Thanks,
    Last edited by vnktummala; 05-13-2010 at 10:42 AM. Reason: added more info
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  9. #9
    Join Date
    Oct 2008
    Location
    Chandigarh, India
    Posts
    322
    Quote Originally Posted by vnktummala View Post
    Akhil - look into constraints=n and indexes=n imp options.

    how many tables you are trying to import? if you don't want to use constraints=n indexes=n then provide individual table names to imp excluding the one you have already imported.

    Thanks,

    Around 98 tables are there.

    Is there a way to import constraints only later on If I use constraints=no?

    I was thinking of some other workaround. Firstly import only MAM_ASSETS table with no constraints and indexes. Then, use import with ignore=n. When table MAM_ASSETS is reached, it will be skipped with error and its indexes and constraints should get imported. I wonder if it would work.
    Last edited by mahajanakhil198; 05-13-2010 at 11:30 AM.
    lucky

  10. #10
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    yes, you have multiple ways to do that.

    but, first place I am wordaring why imp is trying to insert null values. Because I am sure the NOT NULL constraint is there on the source table so no chance of having null values in source. Does it mean that the BLOB column data is not exported??

    as the other poster said, drop that table with cascade constraints and let imp create the table and see how it goes.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

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