Forum Stats

  • 3,839,356 Users
  • 2,262,486 Discussions
  • 7,900,947 Comments

Discussions

Import pluggable database in Oracle 19c

User_R0EYL
User_R0EYL Member Posts: 7 Green Ribbon
edited Feb 3, 2022 6:38AM in Multitenant

Hi All,

I need to import a pluggable database (PDB) to another container database in Oracle 19c(Version 19.11.0.0.0) running on Linux (4.18.0-305.12.1.el8_4.x86_64). But it did not work when I use normal IMPDP. It is throwing errors like below,

Processing object type DATABASE_EXPORT/PRE_SYSTEM_IMPCALLOUT/MARKER

ORA-39342: Internal error - failed to import internal objects tagged with WMSYS due to ORA-20373: Unsupported version of Workspace manager detected

Any idea what is happening here and how can I import PDB from another exported from another CDB?

Thank you for your help in advance!

Regards,

Ram

Tagged:

Best Answer

  • Arturo Gutierrez
    Arturo Gutierrez Member Posts: 337 Bronze Badge
    Answer ✓

    Hello Ram,

    There must be some compatibility issue with the Work Space Manager component.

    Can you run this query on both DBs, source and target ?

    SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;

    See the version of Oracle Workspace Manager component to see any mismatch.

    Instead of doing a full expdp of the Pluggable Database, could you try a schema-level export?

    There are some notes in MOS, related to the ORA-20373 bug.

    If you need to do the export in full mode, I recommend you open an SR with Oracle support, so that they give you the solution.


    Regards

    Arturo

Answers

  • Arturo Gutierrez
    Arturo Gutierrez Member Posts: 337 Bronze Badge

    Hello Ram,

    Are source/target PDBs same Oracle version?

    Try to use at expdp phase the compatible=source_pdb_version.


    Regards

    Arturo

  • User_R0EYL
    User_R0EYL Member Posts: 7 Green Ribbon
    edited Feb 3, 2022 10:56AM

    Hi Arturo.

    No they are on different version. the source is on oracle 19c(Version 19.13.0.0.0) on Solaris and the target on oracle19c(Version 19.11.0.0.0) on Linux. Does it make any difference?

    Also do I have to create PDB manually on the target or the import will create it automatically for me?

    Thank you !

    Regards,

    Ram

  • Arturo Gutierrez
    Arturo Gutierrez Member Posts: 337 Bronze Badge

    Hi,

    You need create the Pluggable Database before import.

    Then use the compatible in the expdp process to :

    expdp .... compatible=19.11 ......

    And try....


    Regards

    Arturo

  • User_R0EYL
    User_R0EYL Member Posts: 7 Green Ribbon
    edited Feb 4, 2022 12:26AM

    Good Morning Arturo,

    Actually the parameter to be used is version=19.11 and not compatible.

    But even that did not help to import on the target.

    I have exported the source (19.13.0.0.0) with expdp ... version=19.11 and tried to import on the destination (19.11.0.0.0) where I created a PDB with the same name but still the import did not go through which failed with exactly the same error message like before where I have exported without version parameter,

    Processing object type DATABASE_EXPORT/PRE_SYSTEM_IMPCALLOUT/MARKER

    ORA-39342: Internal error - failed to import internal objects tagged with WMSYS due to ORA-20373: Unsupported version of Workspace manager detected

    Thank you for your time !

    Regards,

    Ram

  • Arturo Gutierrez
    Arturo Gutierrez Member Posts: 337 Bronze Badge
    Answer ✓

    Hello Ram,

    There must be some compatibility issue with the Work Space Manager component.

    Can you run this query on both DBs, source and target ?

    SELECT COMP_NAME, VERSION, STATUS FROM DBA_REGISTRY;

    See the version of Oracle Workspace Manager component to see any mismatch.

    Instead of doing a full expdp of the Pluggable Database, could you try a schema-level export?

    There are some notes in MOS, related to the ORA-20373 bug.

    If you need to do the export in full mode, I recommend you open an SR with Oracle support, so that they give you the solution.


    Regards

    Arturo

  • User_R0EYL
    User_R0EYL Member Posts: 7 Green Ribbon

    Hi Arturo,

    This afternoon I worked with Oracle support and they suggested to export schema level which resolved the issue.

    Thank you for your time to support me.

    Regards,

    Ram