Solved.
Time for the update and thanks to all for the replies and help.
To answer a question, we were using older versions of clients (more
specifically we are using Microsoft ODBC Driver with a 7.3.4 client and on
separate PCs Forms 4.5) but it turns out the problem is not related to this.
Instead, we were running into bug 1353943 with description "ORA-7445
[FEAD06D0]WHEN PARAMETER SERIAL_REUSE =ALL DURING PL/SQL EXECUTION "
Note that bug 1353943 also seems to effect you when you are using
serial_reuse=SELECT.
Now on NT you do not see the ora-7445 in the alert log.
Instead you get a core dump produced (and under 81714 / NT4 the
core_dump_dest does work for us) and you can get a stack trace from that
showing which Oracle functions were called.
Thanks,
Bruce Reardon
-----Original Message-----
Sent: Tuesday, 10 July 2001 8:38
Bruce,
Core dumps are even more of a pain on NT since they
don't generate a helpful trace file as on other
platforms. You should have a core.log file in one of
the dump directories (core_dump_dest didn't work on
NT, although I've heard it does on 8.1.7+, but haven't
tested it).
There should be a stack trace in it somewhere, but
that's about it. If you're lucky, it will be unique
enough to help support identify an existing bug.
Yes, I have had cases where enabling tracing prevented
the error from occurring, thereby making it incredibly
difficult to resolve.
HTH,
-- Anita
> Hi,
> I have just had the experience of upgrading to
> 81714, discovering a problem
> in our application that did not show up in any
> testing and having to go back
> to 815.
>
> The 815 instance is on a different server to the 817
> instance and we still
> have the 817 instance available for further
> troubleshooting.
>
> This is on NT4.
>
> With 817, we were getting ora-3113 in the forms
> application and in ODBC
> connections and also seeing ora-03121 as well.
>
> We got core dump files produced (under 817 they are
> produced on NT) but
> Oracle support does not seem to know how to
> interpret them on NT - has
> anyone had any experience with this?
>
> No mention of the core dump file was contained
> within the alert log and no
> files were produced in the user dump directory.
>
> When I turned sql trace on for the session running
> forms, the ora-3113 did
> not occur - has anyone seen behaviour like this
> where SQL Trace will cause
> an ora-3113 to stop occurring?
>
> All suggestions on what to look for or how to
> interpret NT core dumps are
> welcome.
>
> Thanks,
> Bruce Reardon
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Reardon, Bruce (CALBBAY)
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
