Oracle Error 4063 Encountered
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Oracle, error while exporting schema up vote 2 down vote favorite I'm using a command: $ exp userid=apex_public_user/apex_public_user OWNER=apex_public_user DIRECT=Y CONSISTENT=Y FILE=/home/oracle/apex_public_user.dmp and getting following output: Export: Release 10.2.0.1.0 - Production on Fr May 18 11:55:20 2012 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production Export done in AL32UTF8 character set and AL16UTF16 NCHAR character set . exporting pre-schema procedural objects and actions EXP-00008: ORACLE error 4063 encountered ORA-04063: package body "SYS.DBMS_REPCAT_UTL" has errors ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_REPCAT_UTL" ORA-06512: at "SYS.DBMS_REPCAT_EXP", line 87 ORA-06512: at line 1 EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_EXP.schema_info_exp . exporting foreign function library names for user APEX_PUBLIC_USER . exporting PUBLIC type synonyms . exporting private type synonyms . exporting object type definitions for user APEX_PUBLIC_USER About to export APEX_PUBLIC_USER's objects ... . exporting database links . exporting sequence numbers . exporting cluster definitions . about to export APEX_PUBLIC_USER's tables via Direct Path ... . exporting synonyms . exporting views . exporting stored p
error 4063 encounteredORA-04063: package body "SYS.DBMS_LOGMNR_LOGREP_DICT" has errorsORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGMNR_LOGREP_DICT"ORA-06512: at line 1EXP-00083: The previous problem occurred when calling SYS.DBMS_LOGMNR_LOGREP_DICT.system_info_expEXP-00008: ORACLE error 4063 encounteredORA-04063: package body "SYS.DBMS_LOGMNR_LOGREP_DICT" has errorsORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGMNR_LOGREP_DICT"ORA-06512: at line 1EXP-00083: The previous problem occurred when calling http://dba.stackexchange.com/questions/18140/oracle-error-while-exporting-schema SYS.DBMS_LOGMNR_LOGREP_DICT.system_info_expUsing sql*plus found that the sys schema package body DBMS_LOGMNR_LOGREP_DICT is invalid.Trying to validate this package using the following statement not success:Alter package DBMS_LOGMNR_LOGREP_DICT compile;Searched the $ORACLE_HOME/rdbms/admin and found that this package is created with the Oracle supplied script prvtlmrd.plb. Trying to validate this package using http://databasefun.blogspot.com/2009/03/full-export-error-caused-by.html this script is still not working.@$ORACLE_HOME/rdbms/admin/prvtlmrd.plbFinally, try to rebuild the whole database stored procedures using catproc.sql did not validate this package body(but has a side effect, explained later). So I asked the Oracle support for help. The reply went back quickly with an action plan based on Doc ID 550197.1.For the packages of the LogMiner to be created successfully, you need to drop the SYSTEM.LOGMNR_SESSION$ table first, and then you can run the Oracle supplied scripts to recreate the LogMiner packages successfully. But the action plan missed the prvtlmrd.plb.So, it should be:SQL> connect / as sysdbaSQL> drop table SYSTEM.LOGMNR_SESSION$ purge;SQL> @?/rdbms/admin/dbmslm.sqlSQL> @?/rdbms/admin/prvtlm.plbSQL> @?/rdbms/admin/dbmslmd.sqlSQL> @?/rdbms/admin/prvtlmd.plbSQL> @?/rdbms/admin/prvtlmc.plbSQL> @?/rdbms/admin/prvtlmrd.plbThis makes the invalid sys schema package body DBMS_LOGMNR_LOGREP_DICT valided.But the export still got error. This time, the log is like this:EXP-00056: ORACLE error 932 encounteredORA-00932: inconsistent datatypes: expected BLOB, CLO
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
http://www.dba-oracle.com/t_compile_pl_sql_procedures.htm ORA-04063 table/view Has Errors Tips Oracle Database Tips by Burleson Consulting Updated March 17, 2015 Question: I am running a Java program that calls a stored procedure and I get this error: ORA-04063: view "AR.GPE" has errors How to I see the specific error from the ORA-04063 error? Answer: You use the oerr utility to see what to do oracle error with the ORA-04063 error: ORA-04063: table/view has errors Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types. oracle error 4063 Action: Fix the errors and/or create referenced objects as necessary. You need to execute the PL/SQL independently (within SQL*Plus) and then use the show errors command to see the exact error message. This will enhance the ORA-04063 and show you the exact line of PL/SQL and reason for the error. ***************************************************************************** In some cases, the ORA-04063 error is caused when a PL/SQL procedure of package becomes invalid after a change to a subordinate procedure or a schema (table) change. ORA-04063: package body "xxx" has errors To resolve this ORA-04063, I would start by trying to re-compile the package and see what the error is using: ALTER PROCEDURE | FUNCTION| PACKAGE [