Link to home
Start Free TrialLog in
Avatar of s2000_com
s2000_com

asked on

Export from Oracle 9.2.0.3 : EXP-00056: ORACLE error 4068 encountered

Hi,

Using Oracle 9.2.0.3, I receive the following error  : EXP-00056: ORACLE error 4068 encountered
when exporting from Enterprise Manager console...I?ve searched on the web for a solution withuout result.

Thanks in advance.

Below the end of the export log :

. exporting operators
. exporting referential integrity constraints
. exporting triggers
EXP-00056: ORACLE error 4068 encountered
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
EXP-00056: ORACLE error 4068 encountered
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully

Phil
Avatar of imran_fast
imran_fast

it seems that there is problem with the packages their statuses are INVALID.
Try recompling them and then export
alter package <package_name> compile;
Also check that the export user have  export_full privs?
Avatar of s2000_com

ASKER

Hi imran_fast,

I have 2 databases : 1 for the management server (Man) and the other for test (Test)

I export from the management server (db Man) so I checked the package from this db and it's compiled but the package from the other db (Test) cannot be compiled and give me this :

(some keywords are in french because Win2003 has french regional settings) :

Numéro de ligne = 63 Numéro de colonne = 17 Texte d'erreur = PLS-00306: wrong number or types of arguments in call to 'IS_HIERARCHY_ENABLED_INTERNAL'
Numéro de ligne = 63 Numéro de colonne = 7 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 76 Numéro de colonne = 29 Texte d'erreur = PLS-00302: component 'GENERATE_TRGNM' must be declared
Numéro de ligne = 76 Numéro de colonne = 7 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 110 Numéro de colonne = 37 Texte d'erreur = PLS-00302: component 'TRUNCATE_NAME' must be declared
Numéro de ligne = 110 Numéro de colonne = 9 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 125 Numéro de colonne = 7 Texte d'erreur = PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
Numéro de ligne = 125 Numéro de colonne = 7 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 137 Numéro de colonne = 37 Texte d'erreur = PLS-00302: component 'TRUNCATE_NAME' must be declared
Numéro de ligne = 137 Numéro de colonne = 9 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 155 Numéro de colonne = 33 Texte d'erreur = PLS-00302: component 'TRUNCATE_NAME' must be declared
Numéro de ligne = 155 Numéro de colonne = 9 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 170 Numéro de colonne = 7 Texte d'erreur = PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
Numéro de ligne = 170 Numéro de colonne = 7 Texte d'erreur = PL/SQL: Statement ignored
Numéro de ligne = 183 Numéro de colonne = 33 Texte d'erreur = PLS-00302: component 'TRUNCATE_NAME' must be declared
Numéro de ligne = 183 Numéro de colonne = 9 Texte d'erreur = PL/SQL: Statement ignored

So it cannot be compiled....
both the servers have same oracle release.
it's the same machine but 2 instances (Man + Test) with vers. 9.2.0.3
Avatar of schwertner
Please do  not use OEM for Export/Import.
Use Export/Import utilities instead:
C:>exp parfile=C:\expsch.par

Where the paramater file coul be:

USERID="sys/reks@rman as sysdba"
FILE=c:\m\dbeta.dmp
SHOW=n
IGNORE=y
GRANTS=y
ROWS=y
FULL=n
FROMUSER=LSUSER
LOG=c:\m\exp.log
Hi schwertner,

I scheduled some export jobs and OEM is the rigt tool to do it. If there is this feature in this tool why do I have to use something else ?

My question is how to fix this issue ?
chwertner,

As expected I have the same error if I use the export utility "exp".

Any other suggestions ?
This is a good news, because it is more generic.

Often this means that you have an incomplete upgrade of the Data BAse.
Have you run the script catupgr.sql in .../rdbms/admin after you upgrade the
software using the Oracle Universal Installer?
Have you run the utility in the same directory to recompile the packages?
 
Oracle recommends the following. Please read it.
I will also strongly recommend to upgrade to 9.2.0.8.
Please do this professionally - read carefully the
README.HTM file in the upgrade set.

1. If you are using the XML functionality, and you have recently applied
   a patch-set, check whether the data dictionary has been upgraded
   accordingly.

   SQL> SELECT SUBSTR(comp_id,1,15) comp_id, status, SUBSTR(version,1,10)
        version, SUBSTR(comp_name,1,30) comp_name
        FROM dba_registry ORDER BY 1;

   If the version of the components CATALOG, CATPROC, XDB (among others)
   is lower than the patch-set version that you have applied, re-run the
   script catpatch.sql after a startup migrate. See the readme file of
   the patch-set for all these mandatory post-installation instructions.

2. If you are using the XML functionality, and the data dictionary
   components have the correct version and are VALID or LOADED,
   then re-create the package XDB.DBMS_XDBUTIL_INT with (example with
   UNIX syntax):

   SQL> connect sys/<password> AS SYSDBA
   SQL> @?/rdbms/admin/prvtxdb.plb
   SQL> exit
I've upgraded from 9.2.0.1 to 9.2.0.3 but I don't have catupgr.sql

I don't have access anymore to Metalink and Oracle is not providing this patchset in the website.

If I run prvtxdb.plb, I receive this  in the end :

show errors
Errors for PACKAGE BODY XDB.DBMS_XDBUTIL_INT:

LINE/COL ERROR
-------- -----------------------------------------------------------------
63/7     PL/SQL: Statement ignored
63/17    PLS-00306: wrong number or types of arguments in call to
         'IS_HIERARCHY_ENABLED_INTERNAL'

76/7     PL/SQL: Statement ignored
76/29    PLS-00302: component 'GENERATE_TRGNM' must be declared
110/9    PL/SQL: Statement ignored
110/37   PLS-00302: component 'TRUNCATE_NAME' must be declared
125/7    PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
125/7    PL/SQL: Statement ignored
137/9    PL/SQL: Statement ignored
137/37   PLS-00302: component 'TRUNCATE_NAME' must be declared
155/9    PL/SQL: Statement ignored
155/33   PLS-00302: component 'TRUNCATE_NAME' must be declared
170/7    PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
170/7    PL/SQL: Statement ignored
183/9    PL/SQL: Statement ignored
183/33   PLS-00302: component 'TRUNCATE_NAME' must be declared
Here is the result of the SELECT :

COMP_ID         STATUS      VERSION    COMP_NAME
--------------- ----------- ---------- ------------------------------
AMD             INVALID     9.2.0.1.0  OLAP Catalog
APS             LOADED      9.2.0.1.0  OLAP Analytic Workspace
CATALOG         VALID       9.2.0.3.0  Oracle9i Catalog Views
CATJAVA         VALID       9.2.0.1.0  Oracle9i Java Packages
CATPROC         INVALID     9.2.0.1.0  Oracle9i Packages and Types
CONTEXT         VALID       9.2.0.1.0  Oracle Text
JAVAVM          VALID       9.2.0.1.0  JServer JAVA Virtual Machine
ODM             LOADED      9.2.0.1.0  Oracle Data Mining
ORDIM           LOADED      9.2.0.1.0  Oracle interMedia
OWM             VALID       9.2.0.1.0  Oracle Workspace Manager
SDO             LOADED      9.2.0.1.0  Spatial
WK              VALID       9.2.0.1.0  Oracle Ultra Search
XDB             INVALID     9.2.0.1.0  Oracle XML Database
XML             VALID       9.2.0.2.0  Oracle XDK for Java
XOQ             LOADED      9.2.0.1.0  Oracle OLAP API
How you understand that your Oracle server is version 9.2.0.3?

SQL>select * from v$version

What is the result?
If it is 9.2.0.3 then try to upgrade the catalog again:

1. Ensure:
- at least 10 MB free in SYSTEM tablespace
- shared_pool_size > 150MB
- java_pool_size   > 150MB

SQL>shutdown immediate
SQL>startup migrate pfile=init.ora
init.ora should provide the above sizes for the pools
SQL>spool c:\patch.log
SQL> @ ?\rdbms\admin\catpatch    (or catupgrade ....)
SQL>spool off
SQL>shutdown immediate
SQL>startup
SQL>@ ?\rdbms\admin\utlrp
The result is :
BANNER
----------------------------------------------------------------
Oracle9i Release 9.2.0.3.0 - Production
PL/SQL Release 9.2.0.3.0 - Production
CORE      9.2.0.3.0      Production
TNS for 32-bit Windows: Version 9.2.0.3.0 - Production
NLSRTL Version 9.2.0.3.0 - Production

5 rows selected.

I will try to upgrade the catalog again...
If I use SPFILE, do I have to use "startup migrate pfile=init.ora" or just "startup migrate" ?
I changed in the SPFILE both pools to 150MB
If this is the case it is enough
SQL>startup migrate
After some hours, below the end of the log (+19MB) for catpatch execution :

e8 :3 0 62 :3 0
a03 1196 1198 a05
1195 119a :3 0 3e
:2 0 135 :4 0 a08
119c 119e :3 0 3e
:2 0 e8 :3 0 62

It seems not finished and I cannot compile XDB.DBMS_XDBUTIL_INT. The errors are the same as above

Why the patch script cannot finish ? I changed the pools to 150MB and used the pfile for patching ?
ASKER CERTIFIED SOLUTION
Avatar of schwertner
schwertner
Flag of Antarctica image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

I will tak a look at these options. I will keep you up-to-date.