10 Replies Latest reply: Feb 2, 2011 12:37 PM by Srini Chavali-Oracle RSS

    UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.

    user12158503
      I am tring to take an export backup of my database which is 11.2.0.1 version. I am using expdp which is running from the same binaries as the 11.2.0.1 database. But , I get the below error -

      $ $ORACLE_HOME/bin/expdp db1/***** DIRECTORY=EXPORT_db1 FULL=Y job_name=full_db1_exp DUMPFILE=EXPORT_DIR:db1_%U_Jan31.dmp LOGFILE=EXPORT_LOG:db1_Jan31.log PARALLEL=3

      Export: Release 11.2.0.1.0 - Production on Mon Jan 31 14:34:16 2011

      Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
      UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.0

      The database that I am trying to export is also 11.2.0.1. Does anyone know why this still throws this error when both are the same version?



      sqlplus db1/****

      SQL*Plus: Release 11.2.0.1.0 Production on Mon Jan 31 15:39:03 2011

      Copyright (c) 1982, 2009, Oracle. All rights reserved.


      Connected to:
      Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
      With the Partitioning, OLAP, Data Mining and Real Application Testing options
        • 1. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
          19426
          What's the value of COMPATIBLE parameter of this 11gR2 database?

          Werner
          • 2. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
            user12158503
            the compatibility is 10.1.0.
            I have other databases on 11.2.0.1 with compatible version set to 10.1.0 and am able to do expdp on those. We just recently upgraded this database and will be updating this parameter soon., Meanwhile, on Metalink I found this [ID 1274439.1] -


            Cause

            Invalid packages DBMS_METADATA_INT or/and DBMS_METADATA_UTIL can produce such a behavior.
            Solution
            1. Verify, if packages DBMS_METADATA_UTIL/DBMS_METADATA_INT are invalid:


            These two views were invalid. I recompiled these two views and now expdp faled with error -

            Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
            ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [PROCACT_SCHEMA:"cedbce"]
            ORA-04063: view "SYS.KU$_CLUSTER_VIEW" has errors

            ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
            ORA-06512: at "SYS.KUPW$WORKER", line 8164

            ----- PL/SQL Call Stack -----
            object line object
            handle number name
            3aef35780 19028 package body SYS.KUPW$WORKER
            3aef35780 8191 package body SYS.KUPW$WORKER
            3aef35780 2814 package body SYS.KUPW$WORKER
            3aef35780 8846 package body SYS.KUPW$WORKER
            3aef35780 1651 package body SYS.KUPW$WORKER
            3a8d9d810 2 anonymous block

            Job "db1"."FULL_db1_EXP" stopped due to fatal error at 16:04:40


            While going through the invalid objects list , I found a bunch of other sys objects (views, packages ku$ objects) invalid. I ran the utlrp several times, but it still leaves them as invalid. We do not use any xml related stuff, so I didn't re-install xmldb during the upgrade. The invalid objects are below. I am not able to recompile
            SYS.KUPW$WORKER. Any ideas on how to proceed? I was using original exp and imp till now(since the db was in 9.2.0.8 earleir) and was rewriting the scripts to use data pump.


            select owner, object_name, object_type, status from dba_objects where status != 'VALID';

            OWNER     OBJECT_NAME     OBJECT_TYPE     STATUS

            SYS     DBA_XML_SCHEMAS     VIEW     INVALID
            SYS     ALL_XML_SCHEMAS     VIEW     INVALID
            SYS     DBMS_METADATA_HACK     PACKAGE BODY     INVALID
            SYS     IS_VPD_ENABLED     FUNCTION     INVALID
            SYS     SET_TABLESPACE     PROCEDURE     INVALID
            SYS     KU$_XMLSCHEMA_VIEW     VIEW     INVALID
            SYS     KU$_XMLSCHEMA_ELMT_VIEW     VIEW     INVALID
            SYS     KU$_OPQTYPE_VIEW     VIEW     INVALID
            SYS     KU$_COLUMN_VIEW     VIEW     INVALID
            SYS     KU$_PCOLUMN_VIEW     VIEW     INVALID
            SYS     KU$_NT_PARENT_VIEW     VIEW     INVALID
            SYS     KU$_FHTABLE_VIEW     VIEW     INVALID
            SYS     KU$_PFHTABLE_VIEW     VIEW     INVALID
            SYS     KU$_IOTABLE_VIEW     VIEW     INVALID
            SYS     KU$_PIOTABLE_VIEW     VIEW     INVALID
            SYS     KU$_VIEW_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_FH_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_PFH_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_IOT_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_PIOT_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_LOG_FH_VIEW     VIEW     INVALID
            SYS     KU$_M_VIEW_LOG_PFH_VIEW     VIEW     INVALID
            SYS     KU$_CLUSTER_VIEW     VIEW     INVALID
            SYS     ALL_XML_SCHEMAS2     VIEW     INVALID
            SYS     KU$_10_1_FHTABLE_VIEW     VIEW     INVALID
            SYS     KU$_10_1_PFHTABLE_VIEW     VIEW     INVALID
            SYS     KU$_ACPTABLE_VIEW     VIEW     INVALID
            SYS     KU$_10_1_IOTABLE_VIEW     VIEW     INVALID
            SYS     KU$_10_1_PIOTABLE_VIEW     VIEW     INVALID
            SYS     ADD_TO_DAV_SCHEMA     PROCEDURE     INVALID
            SYS     MOVEXDB_TABLE     PROCEDURE     INVALID
            SYS     XMLBINARYINPUTSTREAM     TYPE BODY     INVALID
            SYS     XMLBINARYOUTPUTSTREAM     TYPE BODY     INVALID
            SYS     XMLCHARACTERINPUTSTREAM     TYPE BODY     INVALID
            SYS     XMLCHARACTEROUTPUTSTREAM     TYPE BODY     INVALID
            SYS     CREATE_CSXINVALID_ENTRIES_TAB     PROCEDURE     INVALID
            SYS     DBMS_EPG     PACKAGE BODY     INVALID
            SYS     DBA_XML_TABLES     VIEW     INVALID
            PUBLIC     DBA_XML_TABLES     SYNONYM     INVALID
            SYS     ALL_XML_TABLES     VIEW     INVALID
            PUBLIC     ALL_XML_TABLES     SYNONYM     INVALID
            SYS     USER_XML_TABLES     VIEW     INVALID
            PUBLIC     USER_XML_TABLES     SYNONYM     INVALID
            SYS     DBA_XML_TAB_COLS     VIEW     INVALID
            PUBLIC     DBA_XML_TAB_COLS     SYNONYM     INVALID
            SYS     ALL_XML_TAB_COLS     VIEW     INVALID
            PUBLIC     ALL_XML_TAB_COLS     SYNONYM     INVALID
            SYS     USER_XML_TAB_COLS     VIEW     INVALID
            PUBLIC     USER_XML_TAB_COLS     SYNONYM     INVALID
            SYS     DBA_XML_VIEWS     VIEW     INVALID
            PUBLIC     DBA_XML_VIEWS     SYNONYM     INVALID
            SYS     ALL_XML_VIEWS     VIEW     INVALID
            PUBLIC     ALL_XML_VIEWS     SYNONYM     INVALID
            SYS     USER_XML_VIEWS     VIEW     INVALID
            PUBLIC     USER_XML_VIEWS     SYNONYM     INVALID
            SYS     DBA_XML_VIEW_COLS     VIEW     INVALID
            PUBLIC     DBA_XML_VIEW_COLS     SYNONYM     INVALID
            SYS     ALL_XML_VIEW_COLS     VIEW     INVALID
            PUBLIC     ALL_XML_VIEW_COLS     SYNONYM     INVALID
            SYS     USER_XML_VIEW_COLS     VIEW     INVALID
            PUBLIC     USER_XML_VIEW_COLS     SYNONYM     INVALID
            PUBLIC     DBA_XML_SCHEMAS     SYNONYM     INVALID
            PUBLIC     ALL_XML_SCHEMAS     SYNONYM     INVALID
            PUBLIC     ALL_XML_SCHEMAS2     SYNONYM     INVALID
            SYS     USER_XML_SCHEMAS     VIEW     INVALID
            PUBLIC     USER_XML_SCHEMAS     SYNONYM     INVALID
            SYS     DBA_XML_INDEXES     VIEW     INVALID
            PUBLIC     DBA_XML_INDEXES     SYNONYM     INVALID
            SYS     ALL_XML_INDEXES     VIEW     INVALID
            PUBLIC     ALL_XML_INDEXES     SYNONYM     INVALID
            SYS     USER_XML_INDEXES     VIEW     INVALID
            PUBLIC     USER_XML_INDEXES     SYNONYM     INVALID
            SYS     datetime_format83_T     TYPE     INVALID
            SYS     anydata82_T     TYPE     INVALID
            SYS     extra_attribute81_T     TYPE     INVALID
            SYS     column_value84_T     TYPE     INVALID
            SYS     extra_attribute_valu87_COLL     TYPE     INVALID
            SYS     extra_attribute_values86_T     TYPE     INVALID
            SYS     DDL_LCR85_T     TYPE     INVALID
            SYS     old_value90_COLL     TYPE     INVALID
            SYS     old_values89_T     TYPE     INVALID
            SYS     new_values91_T     TYPE     INVALID
            SYS     extra_attribute_values92_T     TYPE     INVALID
            SYS     ROW_LCR88_T     TYPE     INVALID
            SYS     XDS_ACL     VIEW     INVALID
            PUBLIC     XDS_ACL     SYNONYM     INVALID
            SYS     XDS_ACE     VIEW     INVALID
            PUBLIC     XDS_ACE     SYNONYM     INVALID
            • 3. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
              Srini Chavali-Oracle
              Using export/expdp for backups is a poor strategy.

              http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/intro010.htm#sthref110

              You should be using RMAN

              HTH
              Srini
              • 5. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
                user12158503
                I cam e across a a doc in metalink - ID 737618.1 hwich looks like the same error mesdsages I am getting. But m, it says it is on 32-bit p[latforms. But mine is a 64 bit platform. solaris Sparc 64-bit. It still applies to this case? Also, I have many other databases on 64 bit 11.2.0.1 and haven't hadf this issue on those.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   
                • 7. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
                  Lubiez Jean-Valentin
                  Hello,

                  We do not use any xml related stuff, so I didn't re-install xmldb during the upgrade. The invalid objects are below. I am not able to recompile
                  You may reinstall XDB. The following Note of My Oracle Support may guide you in this task:
                  XDB 11.2 Install and Deinstall Note. [ID 887279.1]
                  But, I don't think it could solve the problem about the DBMS_METADATA_% Packages so, it's better to check these points with the Support.

                  Else, instead of making a FULL Export, you may Export the Application's Schemas (the ones which store your datas).


                  Hope this help.
                  Best regards,
                  Jean-Valentin
                  • 8. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
                    user12158503
                    I only discovered that the catproc and the catalog vies were invalid while researching on this expdp issue. the solution according o Metalink note - [ID 742018.1] requires a downtime. Since this is a production DB and it is difficult to get a downtime/bounce the database and since this hasn't affected anything else so far, I would like to know what issues could arise from the catalog and catproc being invalid?
                    • 9. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
                      Srini Chavali-Oracle
                      If your production database is operating normally, I would think the issue is minor - but the description of the issue sounds major. Obviously these should not be invalid. Was this database upgraded from a previous release ? If so, sounds like the upgrade was not done correctly or completely. I would recommend you get downtime as soon as possible to rectify this situation.

                      HTH
                      Srini
                      • 10. Re: UDE-00018: Data Pump client is incompatible with database version 11.2.0.1.
                        user12158503
                        this was upgraded from 9.2.0.6. The upgrade was successful. It was done through DBUA. The post upgrade script, utluiobj.sql shows that nothing was invalidated after the upgrade. And prior to the upgrade everything was valid. Meaning this must have invalidated later on. But i am not sure when or what got it invalidated.