Re: upgrade segmentation fault
- From: Stefan Knecht <knecht.stefan@xxxxxxxxx>
- To: kat.axe@xxxxxxxxx
- Date: Mon, 26 Jul 2010 22:53:22 +0200
Could be an issue with memory management. Some things to try while you wait
for Oracle Support:
- Try increasing the shared pool
- Try disabling AMM (set memory_target to 0)
- Try disabling ASMM (set sga_target to 0)
I'd try in that order, one step at a time and see if it helps, if you can
afford the downtime to run it a couple times.
And just in general, make sure you have enough memory allocated to the
instance (11gr2 requires a lot more memory than 9i did).
Also, did you use the ORA-600 error lookup tool on metalink ?
Stefan
=========================
Stefan P Knecht
CEO & Founder
s@xxxxxxxx
10046 Consulting GmbH
Schwarzackerstrasse 29
CH-8304 Wallisellen
Switzerland
Phone +41-(0)8400-10046
Cell +41 (0) 79 571 36 27
info@xxxxxxxx
http://www.10046.ch
=========================
On Mon, Jul 26, 2010 at 10:46 PM, kathryn axelrod <kat.axe@xxxxxxxxx> wrote:
> Hi,
>
> I'm in the process of trying to upgrade 9.2.0.8 to 11.2.1.0 via manual
> upgrade on RHEL4 (64bit).
>
> Primarily using 837570.1 &
> Oracle® Database Upgrade Guide
> 11g Release 2 (11.2)
> Part Number E10819-02
>
> ----
> Note 837570.1 - step 29 -
> @catupgrd.sql
> it runs for a bit, and then tries to run
> SQL> GRANT SELECT ON xdb.xdb$config TO PUBLIC;
> at which point, it errors.
>
> To the screen, it reports
> ERROR:
> ORA-03114: not connected to ORACLE
> Segmentation fault.
>
> The trace file shows::
> ORA-07445: exception encountered: core dump [__intel_new_memcpy()+293]
> [SIGSEGV] [ADDR:0x10000] [PC:0x3432475] [Address not mapped to object] []
>
> I opened a tar on the issue but haven't heard anything back yet. In the
> meantime, I was hoping perhaps someone else had encountered this/had a fix
> for it?
>
> Thanks,
> -kathryn
>
>
Other related posts:
