Re: Mysterious failure!

When I had the problem all I had to do was install a new 10.2.0.2 instant client on the client box, move the old instant client to a CYA and then move the new one into place. The app on that box then had to be restarted. Nothing was necessary on the db side, and I doubt bouncing the database would have had any effect for this particular bug since the client box would still have been up for 248 days and have had the problem.

Mason, your Java clients would be subject to this bug since they use the instant clients jdbc thin client.

Finn

On 11/30/07, Allen, Brandon <Brandon.Allen_at_oneneck.com> wrote:
>
> Further confusing the issue - Note 4612267.8 states that all versions <
> 11g are believed to be affected, however notes 338461.1 and 358749.1 (
> 10.2.0.2 List of Bug Fixes), state that the fix was also backported in
> patchset 10.2.0.2. So, it looks like the options for the OP are to apply
> patch 4612267 or upgrade to 10.2.0.2.
>
> Regards,
> Brandon
>
> Privileged/Confidential Information may be contained in this message or
> attachments hereto. Please advise immediately if you or your employer do not
> consent to Internet email for messages of this kind. Opinions, conclusions
> and other information in this message that do not relate to the official
> business of this company shall be understood as neither given nor endorsed
> by it.
>

--
http://www.freelists.org/webpage/oracle-l