{"id":2179,"date":"2011-03-01T22:00:00","date_gmt":"2011-03-01T21:00:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/"},"modified":"2011-03-01T22:00:00","modified_gmt":"2011-03-01T21:00:00","slug":"how-to-debug-a-data-pump-error","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/","title":{"rendered":"How to debug a Data Pump error"},"content":{"rendered":"

Recently, at a customer site, I had an Oracle Data Pump error which was not easy to localize. Here is the error I received during a DBIOWNER schema export with Data Pump:<\/p>\n

Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS\n ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]\n ORA-00942: table or view does not exist<\/pre>\n
Using Data Pump TRACE command<\/h4>\n
I began to analyze the problem with an higher expdp tracing level, by adding the below parameters into the expdp.par file:<\/p>\n
TRACE=480300
\nTRACE=1FF0300<\/code><\/p>\n
Before starting the Data Pump tracing, the privilege exp_full_database must be granted to the schema owner DBIOWNER, in order to allow the tracing.<\/p>\n
<\/code>SQL>grant exp_full_database to DBIOWNER;<\/pre>\n
Below, you will find the list of trace level values for Data Pump:<\/p>\n
<\/code>Trace \u00a0 \u00a0 DM\u00a0\u00a0 DW\u00a0 ORA\u00a0 Lines\n level \u00a0\u00a0 trc\u00a0 trc\u00a0 trc\u00a0\u00a0\u00a0\u00a0 in\n (hex) \u00a0 file file file\u00a0 trace\u00a0\u00a0 Purpose\n ------- ---- ---- ---- ------ -----------------------------------------------\n 10300\u00a0 \u00a0 \u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0 SHDW: To trace the Shadow process (API) (expdp\/impdp)\n 20300\u00a0 \u00a0 \u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0 KUPV: To trace Fixed table\n 40300\u00a0 \u00a0 \u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0 'div' To trace Process services\n 80300\u00a0 \u00a0 \u00a0 x\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 KUPM: To trace Master Control Process (MCP)\u00a0\u00a0\u00a0\u00a0\u00a0 (DM)\n 100300 \u00a0 \u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 KUPF: To trace File Manager\n 200300\u00a0 \u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0 KUPC: To trace Queue services\n 400300\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 \u00a0 x\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 KUPW: To trace Worker process(es)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 (DW)\n 800300\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0 x\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 KUPD: To trace Data Package\n 1000300\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 META: To trace Metadata Package\n 1FF0300\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0\u00a0\u00a0 x\u00a0 'all' To trace all components\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 (full tracing)<\/code><\/pre>\n
I did not find any real interesting information in the trace files created under background_dump_dest,
\napart from the identical error “ORA-00942: table or view does not exist”. However, there was no additional informations about which table is missing…<\/p>\n
Thus, I revoked the privilege expo_full_database from DBIOWNER and the TRACE parameter from expdb.par file, and used another method for tracing:<\/p>\n
<\/code>SQL> revoke exp_full_database from DBIOWNER;<\/pre>\n
Using Oracle event 22923<\/h4>\n
For the second method, I used the event 22923, which is documented on Oracle support to help for expdb\/impdp debugging:<\/p>\n
<\/code>SQL> alter system set events '22923 trace name errorstack level 3'\n System altered.<\/pre>\n
I started expdp for the schema DBIOWNER:<\/p>\n
<\/code>SQL> alter system set events '22923 trace name errorstack off'\n System altered.<\/pre>\n
I also analyzed the trace files here, but with the same results as for the above TRACE parameter setting.<\/p>\n
I was on the brink of opening a Service Request on Oracle Support to find out if my error is a new oracle Bug or an already existing Bug. But first, I wanted to trace the SQLs in order to look if some SQL statements report an error.<\/p>\n
Using event 10046 for SQL tracing<\/h4>\n
I started SQL tracing for the entire database:<\/p>\n
<\/code>SQL> alter system set events='10046 trace name context forever, level 12';\n System altered.\n\n<\/pre>\n
I started expdp from the scheme DBIOWNER and stopped the SQL tracing<\/p>\n
<\/code>SQL> alter system set events='10046 trace name context off';\n System altered.<\/pre>\n
Then, I started tkprof for the trace file:<\/p>\n
Host> tkprof pro73b_dw01_5525602.trc expdb_trace.tkprof<\/pre>\n
 <\/p>\n
After analyzing the created tkprof file I soon found the problem \ud83d\ude42\u00a0 “I like the event 10046”<\/p>\n
I extracted the output from the created tkprof file:<\/p>\n
****************************************************************************** SELECT \/*+rule*\/ SYS_XMLGEN(VALUE(KU$), XMLFORMAT.createFormat2('M_VIEW_T', '7')), KU$.MVIEW_TAB.OBJ_NUM ,KU$.VNAME ,KU$.VNAME ,'MATERIALIZED_VIEW' ,KU$.SOWNER FROM\n SYS.KU$_M_VIEW_FH_VIEW KU$ WHERE KU$.MVIEW.SOWNER=:SCHEMA1 AND\u00a0 NOT EXISTS (SELECT 1 FROM\u00a0 SYS.KU$NOEXP_TAB A WHERE A.OBJ_TYPE='MATERIALIZED_VIEW' AND A.NAME=KU$.V\n NAME AND A.SCHEMA=KU$.SOWNER) AND NOT EXISTS (SELECT 1 FROM\u00a0 SYS.KU$NOEXP_TAB A WHERE A.OBJ_TYPE='SCHEMA' AND A.NAME=KU$.SOWNER)\nError encountered: ORA-00942\n *******************************************************************************<\/pre>\n
Analyzing the above found SQL statement<\/h4>\n
I began to start a select count (*) of all involved tables of the statement and again (Bingo :-), one view was readable as user SYS but not as user DBIOWNER:<\/p>\n
<\/code>As user DBIOWNER\n ----------------- \n SQL> select count(*) from\u00a0 SYS.KU$_M_VIEW_FH_VIEW;\n select count(*) from\u00a0 SYS.KU$_M_VIEW_FH_VIEW\n *\n ERROR at line 1:\n ORA-00942: table or view does not exist\nAs user SYS\n ----------- \n SQL> select count(*) from\u00a0 SYS.KU$_M_VIEW_FH_VIEW;\nCOUNT(*)\n ----------\n 6<\/pre>\n
I then logged in on another database and started the below command as a normal schema owner in order to verify if the same problem appears.<\/p>\n
<\/samp>SQL> select count(*) from\u00a0 SYS.KU$_M_VIEW_FH_VIEW;\nCOUNT(*)\n ----------\n 13<\/pre>\n
After some checks on both databases, I found that the below public synonyms were missing on my database:<\/p>\n
<\/samp>TABLE_NAME\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GRANTEE\u00a0\u00a0\u00a0\u00a0\u00a0 OWNER\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 GRANTOR\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PRIVILEGE\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\n ---------------------------\u00a0\u00a0 ------------ ----------- ------------\u00a0 ----------\n KU$_10_1_PFHTABLE_VIEW\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PUBLIC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SELECT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\n KU$_M_VIEW_FH_VIEW\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PUBLIC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SELECT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\n KU$_M_VIEW_LOG_PFH_VIEW\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PUBLIC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SELECT\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0\n KU$_M_VIEW_PFH_VIEW\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PUBLIC\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SELECT<\/samp><\/pre>\n
Conclusion<\/h3>\n
It is unsure that you will find your Data Pump error with the Data Pump TRACE command or the corresponding Oracle event command. But the Oracle event 10046 can be a good alternative to localize missing objects or privileges.<\/p>\n
It was impossible for me to find out why these privileges were missing or not created during database setup (perhaps also deleted later).<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER schema export with Data Pump:<\/p>\n
 Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS
 ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
 ORA-00942: table or view does not exist<\/code><\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[198],"tags":[240,17],"type_dbi":[],"class_list":["post-2179","post","type-post","status-publish","format-standard","hentry","category-database-management","tag-data-pump","tag-oracle-11g"],"acf":[],"yoast_head":"\nHow to debug a Data Pump error - dbi Blog<\/title>\n<meta name=\"description\" content=\"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to debug a Data Pump error\" \/>\n<meta property=\"og:description\" content=\"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2011-03-01T21:00:00+00:00\" \/>\n<meta name=\"author\" content=\"Herv\u00e9 Schweitzer\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Herv\u00e9 Schweitzer\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\"},\"author\":{\"name\":\"Herv\u00e9 Schweitzer\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7\"},\"headline\":\"How to debug a Data Pump error\",\"datePublished\":\"2011-03-01T21:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\"},\"wordCount\":466,\"commentCount\":0,\"keywords\":[\"Data pump\",\"Oracle 11g\"],\"articleSection\":[\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\",\"name\":\"How to debug a Data Pump error - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2011-03-01T21:00:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7\"},\"description\":\"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to debug a Data Pump error\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7\",\"name\":\"Herv\u00e9 Schweitzer\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g\",\"caption\":\"Herv\u00e9 Schweitzer\"},\"description\":\"Herv\u00e9 Schweitzer has more than ten years of experience in database and infrastructure management, engineering, and optimization. He is specialized in Oracle technologies such as standardisation, Backup and Recovery, Tuning, and in High Availability solutions such as Oracle Data Guard, Oracle Grid Infrastructure, Oracle Real Application Clusters (RAC), Oracle GoldenGate, and Oracle Failsafe. Herv\u00e9 Schweitzer is \\\"Oracle Certified Master 11g (OCM 11g)\\\". Prior to joining dbi services, Herv\u00e9 Schweitzer was Senior Consultant at Trivadis in Basel. He also worked as an IT Administrator and Oracle DBA at Crossair in Basel. Herv\u00e9 Schweitzer holds a BTS degree in Information Systems from France. His branch-related experience covers Pharma, Transport and Logistics, Banking, Energy, Automotive etc.\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/herve-schweitzer\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"How to debug a Data Pump error - dbi Blog","description":"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/","og_locale":"en_US","og_type":"article","og_title":"How to debug a Data Pump error","og_description":"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist","og_url":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/","og_site_name":"dbi Blog","article_published_time":"2011-03-01T21:00:00+00:00","author":"Herv\u00e9 Schweitzer","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Herv\u00e9 Schweitzer","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/"},"author":{"name":"Herv\u00e9 Schweitzer","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7"},"headline":"How to debug a Data Pump error","datePublished":"2011-03-01T21:00:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/"},"wordCount":466,"commentCount":0,"keywords":["Data pump","Oracle 11g"],"articleSection":["Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/","url":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/","name":"How to debug a Data Pump error - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2011-03-01T21:00:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7"},"description":"Recently, I had an Oracle error with Data Pump at a Customer, which was not easy to localize. Here is the error I received during a DBIOWNER scheme export with Data Pump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] Error received during DBIOWNER schema export with datapump: Processing object type SCHEMA_EXPORT\/TABLE\/STATISTICS\/TABLE_STATISTICS ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ORA-00942: table or view does not exist","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/how-to-debug-a-data-pump-error\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to debug a Data Pump error"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/7fb08fbefcb9b2c146ef4533cfee00c7","name":"Herv\u00e9 Schweitzer","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0730552c0cfc0a9297c56f2efe56dadd8de399885ca6161a2bee83aebe291afc?s=96&d=mm&r=g","caption":"Herv\u00e9 Schweitzer"},"description":"Herv\u00e9 Schweitzer has more than ten years of experience in database and infrastructure management, engineering, and optimization. He is specialized in Oracle technologies such as standardisation, Backup and Recovery, Tuning, and in High Availability solutions such as Oracle Data Guard, Oracle Grid Infrastructure, Oracle Real Application Clusters (RAC), Oracle GoldenGate, and Oracle Failsafe. Herv\u00e9 Schweitzer is \"Oracle Certified Master 11g (OCM 11g)\". Prior to joining dbi services, Herv\u00e9 Schweitzer was Senior Consultant at Trivadis in Basel. He also worked as an IT Administrator and Oracle DBA at Crossair in Basel. Herv\u00e9 Schweitzer holds a BTS degree in Information Systems from France. His branch-related experience covers Pharma, Transport and Logistics, Banking, Energy, Automotive etc.","url":"https:\/\/www.dbi-services.com\/blog\/author\/herve-schweitzer\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=2179"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2179\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=2179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=2179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=2179"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=2179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}