Geoff,
I'm going to make a non-technical suggestion: You need to have
change control implemented so that packages in your database
are not changing during business hours.
If you are 24x7, then you need to schedule an outage, and notify
your customers of scheduled downtime.
This is more of a
2000 12:03 PM
> To: 'Perrin Harkins'; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: RE: Apache::DBI and altered packages
>
>
>
>
> > -Original Message-
> > From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, Decembe
> -Original Message-
> From: Perrin Harkins [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 11:55 AM
> To: Geoffrey Young; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Apache::DBI and altered packages
>
>
>
> If you change the
> -Original Message-
> From: jared still [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 22, 2000 11:52 AM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
> Subject: Re: Apache::DBI and altered packages
>
>
>
>
> Ge
> my Oracle gurus here tell me that whenever a package changes any open
> connections will get this error. Since the connection itself ok (just not
> the stuff I need to use) the only solution currently available seems to be
> $r->child_terminate() so that at least that child doesn't barf every t
hi all...
I was wondering if anyone has found a good way around persistent connections
and package recompiles. With Apache::DBI, on occasion when someone
recompiles a package and doesn't tell me, I see
ORA-04061: existing state of package body "FOO.BAR" has been invalidated
ORA-04065: not execu
