RE: Package becomes INVALID when a partiiton is dropped
- From: "Mercadante, Thomas F (LABOR)" <Thomas.Mercadante@xxxxxxxxxxxxxxxxx>
- To: <sharmakdeep_oracle@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 28 Jun 2005 07:35:27 -0400
Deepak,
Is this a problem for you? Oracle is working as expected - DDL is
executing against the table, so all dependent objects need to be
recompiled.
You could change your package to say "col1 varchar2(whatever);" and this
problem would go away. Or you could simple recompile all invalid
objects in your schema every time you drop a partition. Or you could
simply ignore the problem and let Oracle automatically recompile the
object when it gets referenced. I vote for the last option because this
really is not an issue. Oracle cleans things up nicely.
Tom
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Deepak Sharma
Sent: Monday, June 27, 2005 5:01 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Package becomes INVALID when a partiiton is dropped
I have a table, say T1, having 3 partitions P1, P2 and
P3.
There exists a PL/SQL procedure that declares
variables as :
col1 T1.col1%TYPE
When I drop a partition P1 of table T1, the PL/SQL
procedure becomes INVALID.
The PL/SQL doesn't reference the partition P1 at all.
____________________________________________________
Yahoo! Sports
Rekindle the Rivalries. Sign up for Fantasy Football
http://football.fantasysports.yahoo.com
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
