Package owner - invalid packages

Hello guys,
I have this problem: I have two DB schemes A and B. I modified the code in both schemes. After compilation, many packages were invalidated. So I compiled all invalid packages, no compilation errors, everything ok.
Now if I run this query in scheme A:
SELECT *
FROM ALL_OBJECTS
WHERE OBJECT_TYPE IN ('PACKAGE', 'PACKAGE BODY')
AND STATUS = 'INVALID';I get two records.
The first one shows an invalid package where owner is scheme C - this is ok, because in scheme C is really such invalid package which has granted execute to scheme A.
The second one shows an invalid package body, where owner is scheme A. But in scheme A, there is no such package. The "invalid" package is in fact in scheme B, it is in fact not invalid and it has no grants at all. So scheme A has no access to that package at all.
Recompilation of this package in scheme B has no impact on the result. Why is the package marked as invalid and why is scheme A assigned as an owner???
Now I run exactly same query in scheme B and get one record.
One package is marked as invalid where owner is scheme B. However this package is in scheme A and scheme A is the owner of this package. Again the package is not invalid and recompilation of that package has no impact... In this case the package has granted execute to scheme B, so scheme B has the access to this package.
Can anyone help me with this?
Thanks, Dan

I found the problem...
After I did those changes to that packages, I first compiled the bodies to wrong schemes. So the bodies were created without specifications. I didn't see those packages because SQL Developer doesn't display them in such case...
So I droped them now.

Similar Messages

Package status shown invalid

Hi,
I am facing the below error,
ORA-04061: existing state of package body "TBM.PAYBACK" has been invalidated
ORA-06508: PL/SQL could not find program unit being called "TBM.PAYBACK"
Status of the package,
select status,object_name, owner from dba_objects where object_name='PAYBACK' and owner = 'TBM';
status object_name owner
invalid PAYBACK public
valid PAYBACK tbm
valid PAYBACK tbm
For TBM user it shows status "valid" and PUBLIC user "invalid"
So is the package valid or invalid.
Connecting as sys tried to compile the package and the package body.. it gets compiled successfully.
But the above sql query still show the same output.
Please guide.

You're welcome,
Since you got an answer and was satisfied with that, you really should close the thread.
Doing that would even improve your somewhat poor statistics
Handle:      A-K
Status Level:      Newbie
Registered:      Aug 5, 2007
Total Posts:      212
Total Questions:      104 *(97 unresolved)*

Exception in getStyleUserNames

HI All,
Whilst using mapbuilder to create styles they seem to disappear. The mapbuilder lists all the lines, color and marker styles but the xml description visible in mapbuild are the defaults descriptions not those which I had earlier defined. I've checked the database records and the style rules exist with what looks like valid xml. When I create a theme based on the styles mapbuilder throws error saying the style does not exist. Below is the output from command prompt of the mapbuilder session.
Any help or hints would be greatly appreciated.
Loading styles...
Style: A.POWER_STATION Type: AREA
Style: C.ACCESS_COVERAGE_YELLOW Type: COLOR
Style: C.CROSSING_DETAIL Type: COLOR
Style: C.ENVIRONMENTAL_FACTOR Type: COLOR
Style: C.HAZARD_FACTOR Type: COLOR
Style: C.LINE_YELLOW Type: COLOR
Style: C.POWER_STATION Type: COLOR
Style: C.PROPERTY_EASEMENT_COVERAGE Type: COLOR
Style: C.SUBSTATION Type: COLOR
Style: L.BLACK_TLINE Type: LINE
Style: L.ELEC_LINE_132KV_THIN Type: LINE
Style: L.ELEC_LINE_220KV_THIN Type: LINE
Style: L.ELEC_LINE_275KV_THIN Type: LINE
Style: L.ELEC_LINE_330KV_THIN Type: LINE
Style: L.ELEC_LINE_33KV_THIN Type: LINE
Style: L.ELEC_LINE_500KV_THIN Type: LINE
Style: L.ELEC_LINE_66KV_THIN Type: LINE
Style: L.ELEC_LINE_NOTINTUSE_THIN Type: LINE
Style: L.ELEC_OHEW Type: LINE
Style: L.ELEC_OPGW_THIN Type: LINE
Style: L.ENVIRONMENTAL_FACTOR Type: LINE
Style: L.PROPERTY_ACCESS_TRACK_THIN Type: LINE
Style: M.PROPERTY_GATE_LOCKED Type: MARKER
Style: M.PROPERTY_GATE_UNLOCKED Type: MARKER
Style: M.SIMPLE_STRUCTURE Type: MARKER
Style: M.STRUCTURE_COMPLEX Type: MARKER
Style: T.CROSSING_DETAIL Type: TEXT
Style: T.ENVIRONMENT_FACTOR Type: TEXT
Style: T.HAZARD_FACTOR Type: TEXT
Style: T.POWER_STATION Type: TEXT
Style: T.SPAN_ANNOTATION Type: TEXT
Style: T.SUBSTATION_TEXT Type: TEXT
Exception in getStyleUserNames: ORA-00904: "OWNER": invalid identifier
LoadUserStyles running thread: Thread-11
Query to load Sytles: select * from all_sdo_styles where owner = :1 order by ty
e desc, name asc (user- TRANS_DEV), (type- null)
Loading styles for user: trans_dev
Exception in loadStyles: ORA-00904: "OWNER": invalid identifier

Hi Joao,
Firstly I'm running Oracle 11g 11.1.0.6.0. on windows 32bit.
As far as patches go I don't think any have been applied yet. This is development environment but this issue exist it's sister environment using the same installation package.
As this is a Dev environment the security has not been implemented and all developers have sys access to the instance so I can't exclude the possibility that this issue is a result of user action.
I thought this might be of interest. The below has me puzzled.
As user trans_dev:
desc all_sdo_styles
Name Null Type
SDO_OWNER VARCHAR2(32)
NAME NOT NULL VARCHAR2(32)
TYPE NOT NULL VARCHAR2(32)
DESCRIPTION VARCHAR2(4000)
DEFINITION NOT NULL CLOB()
IMAGE BLOB()
GEOMETRY SDO_GEOMETRY()
As user mdsys:
desc all_sdo_styles
Name Null Type
OWNER NOT NULL VARCHAR2(32)
NAME NOT NULL VARCHAR2(32)
TYPE NOT NULL VARCHAR2(32)
DESCRIPTION VARCHAR2(4000)
DEFINITION NOT NULL CLOB()
IMAGE BLOB()
GEOMETRY SDO_GEOMETRY()
Is there a simpler fix than running the sdomapd.sql. I would like to avoid exporting and importing the existing styles.
If there is any more information that may assist you please let me know.
Thanks again...

How to find tables from database having no partition

Hello Sir,
How to find tables from oracle database having no partitions?
Thank you.
-Mal

@SB,
SQL> SELECT OWNER, TABLE_NAME FROM DBA_TABLES
2 MINUS
3 SELECT OWNER, TABLE_NAME FROM DBA_TAB_PARTITIONS;
SELECT OWNER, TABLE_NAME FROM DBA_TAB_PARTITIONS
ERROR at line 3:
ORA-00904: "OWNER": invalid identifier@OP,
select table_name,partitioned from dba_tables where partitioned='YES';
select table_name,partitioned from dba_tables where partitioned='NO';
Regards
Girish Sharma
Edited by: Girish Sharma on Jul 1, 2011 9:27 AM

Can Discoverer solve Index?

Hi!!
I have a problem with Oracle9i Discoverer. I have to resolve the index:
Number of blue pencils / Total Number of pencils
and I cannot apply the condition only to the numerator, because it applies to both of them. How can I solve it?. It is the same query, but in the numerator with a condition and in the denominator wihout the condition.
Thakns in advance,
Ana

I tried following code:
SQL>select owner,table_name,index_name from dba_indexes where index_name='T_IDX';
no rows selected
SQL>drop index "t_idx";
ERROR at line 1:
ORA-01418: specified index does not exist
SQL>select index_owner, index_name, table_owner, table_name, column_name
from dba_ind_columns
where table_name = 'T'
and column_name = 'X';
INDEX_OWNER                    INDEX_NAME
TABLE_OWNER                    TABLE_NAME
COLUMN_NAME
TEST                           SYS_C005408
TEST                           T
X
Where is Alert.log? Which directory it locates?
SQL>select owner, index_name, table_owner, table_name
from user_indexes
where upper(table_name) = 'T';
ERROR at line 1:
ORA-00904: "OWNER": invalid identifier
SQL>select index_name, table_owner, table_name
from user_indexes
where upper(table_name) = 'T';
no rows selectedI don't have oracle Metalink account,where can I get 10.2.0.4 or 10.2.0.5?
Thanks

R12 - Compile Invalid objects (Fast Formula, Package Body and View) Urgent

Invalid objects about 43, in this Fast Formula 2 AP Package object, and 1 view
OWNER     OBJECT_TYPE     COUNT(*)
APPS     PACKAGE BODY     37.00
APPS     PROCEDURE     1.00
SCOTT     PACKAGE BODY     1.00
APPS     VIEW     1.00
APPS     FUNCTION     3.00
any one can give idea to make it valid.
Awaiting for your reply.
FYI
the object list is below.
OWNER     OBJECT_NAME
APPS     FFP52474_01010001
APPS     FFP61059_01010001
APPS     FFP56168_01010001
APPS     FFP56167_01010001
APPS     FFP58579_01052004
APPS     FFP56169_01010001
APPS     FFP56170_01010001
APPS     FFP56171_01010001
APPS     FFP56172_01010001
APPS     FFP56173_01010001
APPS     FFP60309_01010001
APPS     FFP60306_01010001
APPS     FFP60308_01010001
APPS     FFP60310_01010001
APPS     FFP60307_01010001
APPS     AP_IMPORT_VALIDATION_PKG
APPS     FFP58576_01011951
APPS     FFP60357_01011951
APPS     FFP57511_01010001
APPS     FFP57510_01010001
APPS     FFP52473_01010001
APPS     FFP60305_01010001
APPS     FFP60545_01042004
APPS     FFP60342_01010001
APPS     FFP58887_01042004
APPS     FFP58888_01042004
APPS     FFP58870_01042004
APPS     FFP58885_01042004
APPS     FFP58907_01010001
APPS     FFP58906_01010001
APPS     FFP58861_01042004
APPS     FFP61122_01010001
APPS     FFP58871_01042004
APPS     FFP58857_01042005
APPS     FFP60917_01032006
SCOTT     MK_PLS_XML_REP_TEST
APPS     MK_PLS_XML_REP_TEST
APPS     AP_FSX_PAYMENT_ADVICE
APPS     RA_SITE_USES
APPS     ZDBAR_CONTACT
APPS     ZDBAR_FAX
APPS     ZDBCLOAD
APPS     ZDBAP_DV_PAYMENT_TYPE
Advanced thanks for reading and giving solution for this.
Thamaraiselvan

any one can give idea to make it valid.Run "Compile APPS Schema" from adadmin.
For Fast Formulas, refer to:
Note: 155737.1 - How To Compile Oracle Fast Formulas
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=155737.1

Invalid Package Body

I have a working instance of a commercial product based on an Oracle database. I exported the main schema of the database. I then created a new database with identical tablespaces and users as the original. After importing the .dmp file I found that everything works fine with the exception of a single package body that will not compile due to errors. Unfortunately the code is wrapped so I am unable to view the errors. Considering I have identical tablespace and user characteristics between the two databases, and that I imported the entire main schema owner, would it be correct to assume that the errors in that package must therefore be due to missing objects of other schemas (that were not imported)?

Could be anything really.
- Rights and roles (are all users truely identical)
- Missing/invalid Objects
- Code inside the package (Maybe they check the patchlevel of your database? Or the server name) => Unlikly but possible.
Best thing would be to get support help from the vendor of the commercial product.

Package in invalid status - compiles ok

I created a package having 2 procedures. The package compiles fine, no errors found. My "SELECT * FROM all_objects" shows the package with STATUS=INVALID.
If I try to call a procedure in the package Says "ORA-06575 Package or function is in an invalid state."
I've tried recompiling the package: "ALTER PACKAGE PKAXINT COMPILE BODY", but to no avail. And the key point being there is absolutely no compilation errors...

Jussi T wrote:
I created a package having 2 procedures. The package compiles fine, no errors found. My "SELECT * FROM all_objects" shows the package with STATUS=INVALID.
If I try to call a procedure in the package Says "ORA-06575 Package or function is in an invalid state."
I've tried recompiling the package: "ALTER PACKAGE PKAXINT COMPILE BODY", but to no avail. And the key point being there is absolutely no compilation errors...SELECT OWNER, OBJECT_TYPE, STATUS FROM ALL_OBJECTS WHERE OBJECT_NAME = 'PKAXINT';
post results from SQL above

Invalid packages, functions and procedures

Hi,
Ok, I think I screwed up. Maybe someone can help me.
Our dev db which I just created a few days ago is 10.2.01. I was reading to see what needed to be done to this base for it to accept a 9.2 version. Data. I came upon oracle documentation that said to run the catalog.sql script. This had something to do with the Import full database and export full database procedures, they had to be added. So I did. I then noticed all these packages, procedures and functions listed on my oem tool as invalid. To correct this problem I ran the following scipts several times
On individual schemas: EXEC DBMS_UTILITY.COMPILE_SCHEMA (SCHEMA => ‘OLAPSYS’);
And this one: EXEC UTL_RECOMP.recomp_serial(); for all of them.
But yet I still get invalid objects ( 6 different schemas) when I run this script the SYS owner being the outstanding one.
COLUMN object_name FORMAT A10
Column owner format a10
Column object_name format a40
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = 'INVALID'
--And owner = 'PUBLIC'
ORDER BY owner, object_type, object_name;
Any suggestions on repairing this damage short of recreating the database?
Any suggestions would help.
Regards,
al

I just did a flashback database to time. Before I did any of these procedures above. That db came up ok and you would think that everything is fine. I went in to check with the same query
COLUMN object_name FORMAT A10
Column owner format a10
Column object_name format a40
SELECT owner,
object_type,
object_name,
status
FROM dba_objects
WHERE status = 'INVALID'
--And owner = 'PUBLIC'
ORDER BY owner, object_type, object_name;
and found the same amount of objects still invalid. I know that I didn't do any work at that time because I was in a meeting. I even logged out and back in on the oem tool and sql plus and got the same invalid in the column.
Anyone knows what is going on here?
regards,
al

ORA-06575: Package or function EDN_DEQUEUE_OAOO_DELIVERY is in an invalid s

After migrating Data from one 11g server to a new one, restart SOA EM, error persists background:
background server is still reporting: "<Warning> <oracle.integration.platform.blocks.event.saq> <SOA-31013> <Error handling message (rolling back).
java.sql.SQLException: ORA-06575: Package or function EDN_DEQUEUE_OAOO_DELIVERY is in an invalid state
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:74)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:135)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:210)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:473)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:423)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1095)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:201)
at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1036)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1379)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3568)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3739)
at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:8150)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1535)
at weblogic.jdbc.wrapper.PreparedStatement.execute(PreparedStatement.java:99)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.readOAOODelivery(SAQBusinessEventBus.java:1302)
at
oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.handleSingleOAOODelivery(SAQBusinessEventBus.java:750)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.handleQueueEvents(SAQBusinessEventBus.java:669)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus.access$000(SAQBusinessEventBus.java:71)
at oracle.integration.platform.blocks.event.saq.SAQBusinessEventBus$1.run(SAQBusinessEventBus.java:319)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)"
===================================================
We found the EDN_DEQUEUE_OAOO_DELIVERY is a storage process， it failed after re-complied, details as below：
SQL> alter procedure DEV_SOAINFRA.EDN_DEQUEUE_OAOO_DELIVERY compile;
Warning: Procedure altered with compilation errors.
SQL> show error;
Errors for PROCEDURE DEV_SOAINFRA.EDN_DEQUEUE_OAOO_DELIVERY:
LINE/COL ERROR
2/9 PL/SQL: Item ignored
2/9 PLS-00201: identifier 'DBMS_AQ' must be declared
3/10 PL/SQL: Item ignored
3/10 PLS-00201: identifier 'DBMS_AQ' must be declared
8/3 PL/SQL: Statement ignored
8/3 PLS-00320: the declaration of the type of this expression is
incomplete or malformed
9/3 PL/SQL: Statement ignored
9/3 PLS-00320: the declaration of the type of this expression is
incomplete or malformed
LINE/COL ERROR
10/3 PL/SQL: Statement ignored
10/3 PLS-00320: the declaration of the type of this expression is
incomplete or malformed
12/3 PL/SQL: Statement ignored
12/59 PLS-00320: the declaration of the type of this expression is
Anybody have any suggestion will be highly appreciated.
Thanks,
Katherine

I did what could be the reason?Did it compile successfully? Do you still get the same error?
What is the status of the package now?
SQL> select owner, object_type, status
from dba_objects
where object_name = '<PACKAGE NAME>';The package may have been invalidated for different reasons (like editing the code without compiling it, one of more the objects referenced in the package became invalid, new columns added to tables/views which are used by the package, ..etc).
Thanks,
Hussein

Why do packages go invalid ?

Hi,
Whenever I do a DDL to a table or re-create existing functions, dependent packages/ functions go invalid.
Is there a reason for this?
Thanks!
Anand

Yes all dependent objects will go to invalid state and oracle will autocomplie when they will get accessed. OR you need to compile all or manually compile selected objects.
You can find dependencies from below query for the modified objects.
select * from DBA_DEPENDENCIES
where owner = 'PROVIDE SCHEMA_NAME'
and name = 'PROVIDE OBJECT_NAME'

Unable to recompile invalid package bodies

Hello,
Recently, I cloned the EBS installation, and there were a lot of invalid objects. I used the script to recompile them, and they went fine except for some package bodies, that can't be recompiled neither manually via sqlplus, nor sqldeveloper. Tried also via adadmin, there is no way to be recompiled.
There are 39 packages owned by apps schema as follows:
SQL> select object_name, object_type, owner, status
2 from dba_objects where status='INVALID';
OBJECT_NAME                                                                           OBJECT_TYPE     OWNER               STATUS
FII_AP_INV_ON_HOLD_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_AP_HOLD_DATA_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_AP_INV_PAYMTS_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_AP_INV_LINES_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_AP_SCH_PAYMTS_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_AR_TRX_DIST_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_PA_COST_F_C                                                                       PACKAGE BODY     APPS               INVALID
FII_PA_REVENUE_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_PA_UOM_CONV_F_C                                                                      PACKAGE BODY     APPS               INVALID
FII_PA_BUDGET_F_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_ASG_CHNG_M_C                                                                      PACKAGE BODY     APPS               INVALID
OBJECT_NAME                                                                           OBJECT_TYPE     OWNER               STATUS
EDW_HR_AGE_BAND_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_ASSGNMNT_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_GRADE_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_JOBS_M_C                                                                       PACKAGE BODY     APPS               INVALID
EDW_HR_SERVICE_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_MVMNT_TYP_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_PERSON_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_POSITION_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_REC_ACT_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_ORGANIZATION_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_PRSN_TYP_M_C                                                                      PACKAGE BODY     APPS               INVALID
OBJECT_NAME                                                                           OBJECT_TYPE     OWNER               STATUS
EDW_HR_RQN_VCNCY_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_HR_REASON_M_C                                                                      PACKAGE BODY     APPS               INVALID
HR_EDW_WRK_CMPSTN_F_C                                                                      PACKAGE BODY     APPS               INVALID
ISC_EDW_BOOK_SUM1_F_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_MTL_INVENTORY_LOC_M_C                                                                 PACKAGE BODY     APPS               INVALID
OPI_EDW_COGS_F_C                                                                      PACKAGE BODY     APPS               INVALID
OPI_EDW_OPM_JOB_RSRC_F_C                                                                 PACKAGE BODY     APPS               INVALID
OPI_EDW_OPM_JOB_DETAIL_F_C                                                                 PACKAGE BODY     APPS               INVALID
OPI_EDW_OPMCOGS_F_C                                                                      PACKAGE BODY     APPS               INVALID
OPI_EDW_OPMINV_DAILY_STAT_F_C                                                                 PACKAGE BODY     APPS               INVALID
EDW_OPI_OPRN_M_C                                                                      PACKAGE BODY     APPS               INVALID
OBJECT_NAME                                                                           OBJECT_TYPE     OWNER               STATUS
EDW_OPI_ACTV_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_OPI_LOT_M_C                                                                       PACKAGE BODY     APPS               INVALID
EDW_OPI_PRDL_M_C                                                                      PACKAGE BODY     APPS               INVALID
OPI_EDW_UOM_CONV_F_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_POA_SPLRITEM_M_C                                                                      PACKAGE BODY     APPS               INVALID
EDW_POA_LN_TYPE_M_C                                                                      PACKAGE BODY     APPS               INVALID
39 rows selected.
The compilation errors are all the same.
SQL> select name, text from user_errors;
and it gives me this:
EDW_HR_ASG_CHNG_M_C
PL/SQL: SQL Statement ignored
EDW_HR_AGE_BAND_M_C
PL/SQL: ORA-02083: database name has illegal character '-'
EDW_HR_AGE_BAND_M_C
PL/SQL: SQL Statement ignored
The same errors I get when I try to recompile them in sqldeveloper.
Please, any Idea how can I solve this?
I would be grateful If you help me with this one.
Thanks

Hi,
I was also facing similar problem when I applied packages from the code line to local DB.
You can try to first compile first the package specification and then compile the package body again.
If still you get the error : PL/SQL: SQL Statement ignored, this means that the package specification and the package body are not in sync (either one of them is an older version). In that case you need to check from the version control of these.
Regards,
Rahul

Installation failing due to invalid packages

During installation of Oracle 10G designer the repository installation fails due to invalid packages. When I examine the packages they are failing to compile based on dependencies on dbms_lock. I am running against a fresh installation of 11g on the database. I verified that the package exists and a public synonym has been created but I cannot see the package from any other user aside from sys. (system cannot see the package).
Is there anyway I can open up sys.dbms_lock to allow it to be used in compiling these objects?

How did you create the repository?
Did you follow the steps of the installation guide?
In this guide you find the folloiwing statements:
grant execute on dbms_rls to repos_owner;
grant execute on dbms_lock to repos_owner;
grant execute on dbms_pipe to repos_owner;
grant create table to repos_owner;
grant create view to repos_owner;
grant create procedure to repos_owner;
grant create synonym to repos_owner;
grant create sequence to repos_owner;
grant select on sys.v_$nls_parameters to repos_owner with grant option;
grant select on sys.v_$parameter to repos_owner;
grant select on dba_rollback_segs to repos_owner;
grant select on dba_segments to repos_owner;
grant create any synonym to repos_owner;
grant drop any synonym to repos_owner;
In the statement you will see that the dbms_lock package is granted to the repos_owner. (repos_owner is the username of the repository owner, if you installed under a different user use that username)

Invalid Packages question

Hi All,
First of all, here the background information about the database:
Oracle EBS R12.0.4
RDBMS 10.2.0.2
AIX 5L 5.3 64 bits
I have a question about invalid packages. When looking at ssome invalid package in TOAD, when I click on "ERROR" tab (or query dba_errors), I can see this message:
PLS-00923: native compilation failed: C compilation or linking failed:spdzj.c:Could not invoke program /usr/local/bin/gcc: No such file or directory
For now, I got the sysadmin to create a soft link from /usr/local/bin to point to /usr/bin/gcc and I could compile the packages.
When I log on the server as the RDBMS owner, and do the following:
env | grep gcc -> return nothing
which gcc -> /usr/bin
Considering the gcc should be going to /usr/bin and that when I type "which gcc" it return the one in /usr/bin, where in Oracle is it set to be in /usr/local/bin?
I looked into some configuration files and didn't find anything that would 'hardcode' the path to GCC.
Anyone ever got this issue?
Thank you,
Felix

Pl see if MOS Doc 269012.1 (PL/SQL Native Compilation in Oracle 10g) can help you
HTH
Srini

MIGRATION package invalid

Hello all!
Every time I try I use the migration tool I get an error saying the migration package is invalid. I have dropped and recreated the repository a few times and have just completed a recreation of the repository schema owner. Additionally I have attempted to compile the package again with no luck and granted just about every permission I can think of at this point. :)
Thank you for your time.
Daryl
db - 10.2.0.1 Enterprise Ed.
os - Red Hat Enterprise Linux AS release 4 (Nahant Update 4)

Daryl, There is a problem with the wrapping of the PLSQL code for 10.2.0.1. This is fine on XE, but doesnt compile on 10.2. Log a support ticket and we'll get you a unwrapped version of the packages.

Package owner - invalid packages

Similar Messages

Maybe you are looking for