topic SIGBUS error on import in Operating System - HP-UX

SIGBUS error on import

Tim Medford — Fri, 16 Apr 2004 17:52:15 GMT

Running an L1000 server with HPUX 11i. Four gigs of memory and dual 440mhz CPUs.

We are in the process of converting from Oracle 8.1.7.4 to 9.2.0.4. We occasionally have a problem with the import crashing while it is importing a particularly large stored procedure.

ORA-07445: exception encountered: core dump [qcstda()+236] [SIGBUS] [unknown code] [0x000000000] [] []

I saw some similar messages about SIGBUS errors on this forum and increased maxdsize and maxdsize64 to 2gb each. It worked once, but then an import failed the next day.

Has anyone seen this? Any suggestions?

Thanks
Tim

Re: SIGBUS error on import

Stephen Andreassend — Sat, 17 Apr 2004 01:29:16 GMT

Have you tried upgrading from 8174 to 9201 first, then applying the patchset? Normally this is the standard upgrade path. Also perhaps try increasing the size of the shared pool if you have large plsql blocks.

Re: SIGBUS error on import

Stephen Andreassend — Sat, 17 Apr 2004 02:28:21 GMT

Take your trace file and use it with this tool from Oracle:

http://metalink.oracle.com/metalink/plsql/showdoc?db=Not&id=208922.1

Re: SIGBUS error on import

Victor Fridyev — Sat, 17 Apr 2004 06:41:19 GMT

Do you use parameter "commit=y" in the import command ?

Regards

Re: SIGBUS error on import

Brian Crabtree — Sat, 17 Apr 2004 17:29:01 GMT

Tim,

Does it always fail on a single stored procedure, or does it fail on random large ones?

What buffer parameter are you setting for the import as well?

Does the rest of the database complete successfully before hand (tables/indexes). What about dropping the procedure in 8i, and reloading it in 9i?

Thanks,

Brian

Re: SIGBUS error on import

Sanjiv Sharma_1 — Sat, 17 Apr 2004 17:50:53 GMT

Hi Tim,

Please check this link:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=242927

Re: SIGBUS error on import

Stephen Andreassend — Sun, 18 Apr 2004 02:07:58 GMT

Try repeating the import, but set the initialization parameter to disable PLSQL compilation when loading.

For example:

sqlplus "/ as sysdba"
alter system set "_plsql_load_without_compile"=true scope=spfile;
startup force;

imp ....

Then afterwards go through the procedures and compile them individually.

Also, you should be on 9205 patchset.

Re: SIGBUS error on import

Syed Shaffat Ali — Sun, 18 Apr 2004 07:57:12 GMT

Hello,

Why dont u go for a physical backup restore and upgrade the database.
Recently we did this for converting for a 9.0.1.4 RAC to 9.2.0.4 RAC.
It surely will be more time saving than an import.

Regards.
Shaffat.