1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

Error in datapump import (impdp)

Discussion in 'Security, Backup and Recovery' started by Mike617, Aug 12, 2014.

  1. Mike617

    Mike617 Active Member

    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    55
    Hi All,
    I was trying to duplicate our database server by doing a full database importt of a full data export from our my source db.
    However, I always get this error: ora-39125 and ora-28031.
    I have attached portion of the logfile below:


    Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
    Processing object type DATABASE_EXPORT/RESOURCE_COST
    Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
    ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling KUPP$PROC.CHANGE_USER [DB_LINK:"PARS"."FMISTEST.WORLD"]
    ORA-31625: Schema SYSTEM is needed to import this object, but is unaccessible
    ORA-28031: maximum of 148 enabled roles exceeded
    ORA-06512: at "SYS.KUPW$WORKER", line 5168
    ORA-06512: at "SYS.KUPW$WORKER", line 12639
    ORA-31625: Schema SYSTEM is needed to import this object, but is unaccessible
    ORA-28031: maximum of 148 enabled roles exceeded
    ORA-31625: Schema SYSTEM is needed to import this object, but is unaccessible
    ORA-28031: maximum of 148 enabled roles exceeded
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 116
    ORA-06512: at "SYS.KUPW$WORKER", line 6248
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    0x10a1a8420 14916 package body SYS.KUPW$WORKER
    0x10a1a8420 6300 package body SYS.KUPW$WORKER
    0x10a1a8420 12279 package body SYS.KUPW$WORKER
    0x10a1a8420 3279 package body SYS.KUPW$WORKER
    0x10a1a8420 6889 package body SYS.KUPW$WORKER
    0x10a1a8420 1262 package body SYS.KUPW$WORKER
    0x10a195400 2 anonymous block
    Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 09:26:05

    Please guide me on how to get rid of the above errors.

    Thanks and invance....

    Mike
     
  2. zargon

    zargon Community Moderator Forum Guru

    Messages:
    2,346
    Likes Received:
    347
    Trophy Points:
    1,430
    Location:
    Aurora, CO
    An export does NOT replicate the SYS and SYSTEM objects; you need to create a 'blank' database first, then import into that.


    You could do this with RMAN but that's an actual backup, not an export.
     
  3. Mike617

    Mike617 Active Member

    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    55
    Hi David,
    Thanks for the reply. I have actually created a blank database by creating the tablepaces and datafiles as in the original database before trying to make the import.
    The problem is that on the original database, user 'System' has only 138 enabled roles well below the max enabled roles of 150. However, as the import starts, it seems that user System on the new database receives the roles of the user System on the source database, that is why maybe the error "exceeds the max enable roles".
    What other parameters does impdp need so as not to bloat the roles granted to the user System as the import runs.

    Thanks and best regards,

    Mike
     
  4. Mike617

    Mike617 Active Member

    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    55
    Hi All,
    Solved my problem by granting DBA role to a user and used that user to make the import.
    By that, was able to do the import without problems.
    Thanks and best regards to all,
    Mike