To those of you who were involved in the discussion on the random
truncate failure last December: seems like we fixed the problem (we
haven't had a truncate failure for the last 2 weeks, and it is being
used all the time). So for your information, I will copy here a
portion of the DBA's email abut the fix:
"> Oracle has identified a bug in our version - 8.1.6.3 - that could
be the
> cause. The bug erroneously reports an ORA-942, masking the real cause
> which is related to aging out of the parsed cursor in the shared pool
> under heavy load situations. There is a workaround - to make explicit
> grants rather through a role on the truncate_table procedure, and there is
> a patch available."
So he made the grants, and it seems to work.
Thanks again for all your ideas.
Erika
Received on Tue Feb 04 2003 - 08:49:31 CST
