Oracle expdp error: ORA-39125 ORA-4063 on view SYS. Ku $ _ cluster_view Solution

 

Use expdp to export the database. An error is reported and unexpected interruption occurs:

ORA-39125: worker unexpected fatal error in KUPW $ worker. unload_metadata while calling dbms_metadata.fetch_xml_clob [procact_schema: "GGS"]

ORA-04063: View "SYS. Ku $ _ cluster_view" has errors

ORA-06512: At "SYS. dbms_sys_error", line 105

ORA-06512: At "SYS. KUPW $ worker", line 6234

----- PL/SQL call stack -----

Object line Object

Handle number name

C00000014c508d0814916 package body SYS. KUPW $ worker

C00000014c508d086293 package body SYS. KUPW $ worker

C00000014c508d082339 package body SYS. KUPW $ worker

C00000014c508d086854 package body SYS. KUPW $ worker

C00000014c508d081259 package body SYS. kupnw $ worker

C000000211983d20 2 anonymous Block

Job "sys". "sys_export_full_05" stopped due to fatal error at09: 09: 55

 

 

In this case theproblem is generated because the view SYS. Ku $ _ cluster_view is invalid, inaddition to that the following components are invalids according with Theoutput of dba_registry.

-- This is because the SYS. Ku $ _ cluster_view view is invalid.

 

Some components may also be invalid. You can use the following SQL query:

Col comp_id for A12;
Col comp_name for A30;
Col version for A12;
Select comp_id, comp_name, version, status from dba_registry;

Owm Oracle workspacemanager 10.2.0.4.3 valid
Ordim oracleintermedia 10.2.0.4.0 invalid
Catalog Oracle Database catalog views 10.2.0.4.0invalid
Catproc Oracle database packages and types 10.2.0.4.0 invalid

 

Solution:

CD $ ORACLE_HOME/rdbms/admin
SQL> startup restrict
SQL> select count (*) from dba_objects where status = 'invalid ';
SQL> @ catalog
SQL> @ catproc
SQL> @ utlrp <= to compile the invalid objects
SQL> select count (*) from dba_objects where status = 'invalid ';
Col comp_id for A12
Col comp_name for A30
Col version for A12
Select comp_id, comp_name, version, status from dba_registry;
SQL> shutdown immediate
SQL> startup

 

Run the catalog. SQL script to refresh the view. The Catalog. SQL file contains the definitions and Common synonyms of these views. Run catalog. SQL to create these views and synonyms. To solve the view failure problem.

After the verification is completed, invalid objects and components can continue to expdp if they are normal.

 

 

Related links:

ORA-39125 ORA-4063 on viewsys. Ku $ _ cluster_view when doing a DataPump export [ID 742018.1]

 

Comparison between exp/IMP and expdp/impdp and some optimization items in use

Http://blog.csdn.net/tianlesoftware/article/details/6093973

 

Oracleexpdp/impdp example

Http://blog.csdn.net/tianlesoftware/article/details/6260138

 

Oracle 10 gdata pump expdp/impdp

Http://blog.csdn.net/tianlesoftware/article/details/4674224

 

Dynamic Oracle performance View

Http://blog.csdn.net/tianlesoftware/article/details/5863191

 

Invalid oraclecompile compilation object

Http://blog.csdn.net/tianlesoftware/article/details/4843600

Oracle8i/9i/10g/11g component (components) Description

Http://blog.csdn.net/tianlesoftware/article/details/5937382

 

 

 

 

Bytes -------------------------------------------------------------------------------------------------------

All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!

Skype: tianlesoftware

Email: tianlesoftware@gmail.com

Blog: http://www.tianlesoftware.com

WEAVER: http://weibo.com/tianlesoftware

Twitter: http://twitter.com/tianlesoftware

Facebook: http://www.facebook.com/tianlesoftware

LinkedIn: http://cn.linkedin.com/in/tianlesoftware

 

 

------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940