datapump import errors, please help now, thanks
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6

Thread: datapump import errors, please help now, thanks

  1. #1
    Join Date
    Dec 2007
    Posts
    82

    datapump import errors, please help now, thanks

    Hi,

    could you plz help me to solve below errors which are coming while doing import with impdp command in oracle 10g 10.1.0.4.0 os: Red Hat Enterprise Linux ES release 4

    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    Job "DCA"."SYS_IMPORT_SCHEMA_01" stopped due to fatal error at 15:31

    i tried to restart job but the following errors coming

    UDI-00008: operation generated ORACLE error 39078
    ORA-39078: unable to dequeue message for agent KUPC$A_1_20081111155728 from queue "KUPC$C_1_20081111155728"
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 2356
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 3261
    ORA-06512: at line 1

    thanks in advance

  2. #2
    Join Date
    Jul 2002
    Location
    Lake Worth, FL
    Posts
    1,470

    Cool Characterset

    Check for characterset conversions (NLS_LANG environment variable).
    "The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb

  3. #3
    Join Date
    Dec 2007
    Posts
    82
    echo $NLS_LANG
    american_america.utf8

  4. #4
    Join Date
    Jul 2002
    Location
    Lake Worth, FL
    Posts
    1,470

    Talking Ethnic characters?

    Quote Originally Posted by mdvreddy
    echo $NLS_LANG
    american_america.utf8
    Did you check against the database characterset? this normally happens when the source data has "special" (read ethnic) characters that are translated into two character pairs on import and no longer "fit" into the original column size.
    "The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb

  5. #5
    Join Date
    Dec 2007
    Posts
    82
    Quote Originally Posted by LKBrwn_DBA
    Did you check against the database characterset? this normally happens when the source data has "special" (read ethnic) characters that are translated into two character pairs on import and no longer "fit" into the original column size.

    all nls_database parameter values are same on both source and destination db systems. any solutions to this problem?

  6. #6
    Join Date
    Mar 2007
    Location
    Ft. Lauderdale, FL
    Posts
    3,554
    Don't you have access to Metalink?

    This is related to small STREAMS_POOL_SIZE

    Set it to 100M then recycle the database and try again.
    Last edited by PAVB; 11-13-2008 at 10:48 AM.
    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.

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