-
What would invalidate a procedure?
Sorry to speak in such broad strokes but this is a question that was asked today. We had a download procedure go invalid today.
As far as I know dropping or altering the base tables, editing the proc will invalidate it, anything else?
A network glitch should not cause it to go invalid.
The proc basically downloads data through a db_link from another database.
I remember when this place was cool.
-
a procedure that it calls gets modified and it will go invalid. Check for all objects that had a last_ddl_Time of the day it went invalid for a starting point. You can also query sys.dependancy$ to check dependancies for that object.
Jeff Hunter
-
Surely a network glitch could invalidate an object. If that object in database x was in some connected via a db link to another object in database y, and the network between the two went down.
-
Originally posted by bazza
Surely a network glitch could invalidate an object. If that object in database x was in some connected via a db link to another object in database y, and the network between the two went down.
That sounds more like a guess. If that were the case whenever a remote database shutdown it would invalidate every object that depends on it. This is definitely not the case.
Last edited by marist89; 09-22-2004 at 12:25 PM.
Jeff Hunter
-
clear breaks
A network glitch would NOT invalidate dependent objects ... If so,
Look at Oracle Replication ... It would be a nightmare...
Here's a little script to find the dependences ...
break on r_name skip 1
column r_name format a80
column name format a80
column r_link format a80
set heading off
select decode(referenced_type, 'NON-EXISTENT', '.....', referenced_type)
|| ' ' || referenced_owner || '.' || referenced_name r_name,
' is referenced by: ' || type || ' ' || owner || '.' || name name,
' Referenced Link: ' || decode(referenced_link_name, null, 'none',
referenced_link_name) r_link
from sys.dba_dependencies
where referenced_name = '&&table_name'
order by 1,2;
HTH
Gregg
-
Re: What would invalidate a procedure?
Originally posted by Mr.Hanky
As far as I know dropping or altering the base tables, editing the proc will invalidate it, anything else?
Developers breathing near the machine?
-
Thanks for the replies guys, another suggestion from one of our developers was that someone created a TEMP table with the same name as an existing table and then dropped it. This is possible but no one is fessing up, big surprise. Even the developers want to shoot the developer responsible.
Thanks for the query Jeff, I checked on all object with DDL against them. We still think it was a temp table, we NEVER should have given them schemas that allow them to create tables in production.
C'mon, everyone sing along with me..........
"Shoot the developers!"
"Shoot the developers!"
"Shoot the developers!"
Roses are nice
Violets are mute
I never met a devloper
I didn't wanna SHOOT!
I remember when this place was cool.
-
Q: Mr.Hanky have u always ended up with "developers" who need to be shot ? Surely there are a few good one out there ?
-
just curious guys and gals,
thus triggers does not include the lists that affects the invalidity of a procs?
-
Originally posted by cruser3
Surely there are a few good one out there ?
Hanky would shoot them in the very first place if he finds such a dev.. Aint it Mr.H?
funky...
"I Dont Want To Follow A Path, I would Rather Go Where There Is No Path And Leave A Trail."
"Ego is the worst thing many have, try to overcome it & you will be the best, if not good, person on this earth"
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|