Ann Burk wrote:
>
> I get constant error message ORA-02019 in the alert file. I added an (snip...snip...)
> trace to tell me which of my
> ~100 links is causing the problem...
I wonder which version you had migrated *from*? I raise that question
because we have been getting ORA-2019s in a 7.3.3.5 database -- they are
caused (intermittantly) by a stored function that uses a db link
whenever it was being executed by some user *other than* the owner of
the function. I was told to upgrade to 7.3.4.4 & that that *should* fix
the problem. I'm guessing based on this that some releases in the 7.3.3
family were OK & maybe your database was running one of these before the
upgrade to 7.3.4? BTW: for what it's worth the workaround is to create
a PUBLIC db link to replace the one that is generating the ORA-2019s.
--
Vincent Ventrone | The MITRE Corp.
DBA, Dept. R101 | M/S C020
vav_at_mitre.org | 202 Burlington Rd.
(781) 271-7048 | Bedford, MA 01730
Received on Thu May 27 1999 - 12:39:48 CDT
