My Oracle Support Banner

MD_META is Marked Invalid After Creating the SQL*Developer Repository (Doc ID 461545.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Oracle Migration Workbench - Version 10.2.0.3 and later
Oracle SQL Developer - Version 3.0 to 3.0 [Release 3]
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2011***


Symptoms

When creating the repository for SQL*Developer the package MD_META can be marked invalid and will not compile. SQL*Developer will display this object marked as invalid. This package is wrapped and
so there is no way to see what line is causing the error. Recompiling the package will result in
these errors:


PACKAGE BODY MD_META

Error(27,2): PL/SQL: SQL Statement ignored

Error(30,23): PL/SQL: ORA-00904: : invalid identifier




Problems from this vary and are unpredictable.

Here are a couple of examples

(1) Using SQL*Server
When trying to collect metadata information from SQL*Server the following errors occur -


oracle.dbtools.metadata.persistence.PersistenceException:

ORA-04063: package body "xxx.MD_META" has errors

ORA-06508: PL/SQL: could not find program unit being called: "xxx.MD_META"

ORA-06512: at "xxx.MD_PROJECTS_TRG", line 3

ORA-04088: error during execution of trigger 'xxx.MD_PROJECTS_TRG'



(2) Using Access


Unable to capture the XML file after using the exporter tool.




Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.