"Anil Asher" <anilasher_at_hotmail.com> wrote in message
news:d24b10ea.0112090658.5015c4da_at_posting.google.com...
> I would either have to re-code my application to always make the
> second call on an error OR I can incoporate a check to see if any
> procedures have been re-compiled since the connection to the db was
> established, if yes then disconnect and re-connect.
If you really want to achieve this then the better way of doing this is to
trap the error and recall (or take appropriate action if you get a different
error). However as Jim and others have said you should not have INVALID code
lying around in a production system.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
Received on Mon Dec 10 2001 - 04:33:36 CST
