Message-ID: <253D42C2917FD511880E00508B66B6701F8C2B@schicktnix.bomico.com> From: Schoenwaelder Oliver <oschoenwaelder@de.infogrames.com> Date: Mon, 8 Oct 2001 18:41:27 +0200 Subject: ORA-03113 error after 8.1.6 to 8.1.7 upgrade on SuSE 7.0
Hi,
I have had a running and stable Oracle database with lots of triggers and
some packages - running on Oracle 8.1.6 and SuSE 7.0.
Due to some reasons I had to upgrade to at least Oracle 8.1.7. I did so by
upgrading to 8.1.7.0.1. I didn't upgrade my SuSE installation, it's still
7.0. And I didn't install the glibc patch because it's not needed for 7.0.
Am I right?
I migrated the database and recompiled all triggers/packages just to be sure
everything is fine.
Now I have a serious problem with (explicit?) cursors in certain conditions.
When the "main" procedure of one package is invoked by only one trigger
everything is fine. When the procedure is called more than once I got
ORA-03113 errors. The trace file reports SIGSEGV error (and a lot of things
I don't understand):
*** SESSION ID:(13.36611) 2001-10-08 17:42:30.450
Exception signal: 11 (SIGSEGV)
*** 2001-10-08 17:42:30.881
ksedmp: internal or fatal error
What's amazing is that whenever the error has occured the application fails
at the same point - even when running alone! I have to restart the database
to get at least on application running at a time.
I tried both "original" 2.2.16 and my own 2.2.19-SuSE kernel. Both have the
same result.
Does anyone have an idea? I've got no more, I've searched OTN and found
nothing related to my problem. It seems that I have to update to
Oracle817/SuSE72/glibc-patch and hope for a stable databse...
Regards,
Oliver
This archive was generated by hypermail 2.1.0 : Thu Oct 11 2001 - 14:55:32 PDT