ORA-07445: exception encountered: core dump [10]

[Thirumalai Ulaganathan]

Hi,

We are getting this message " ORA-07445: exception encountered: core dump [10] " in our production server running HP-UX 10.20, Oracle 8.0.5 DataBase. Can you please help me to understand the nature of cause of this problem.
your help will be greatly appreciated.

Thanks
Thirumalai

[Sridhar Bhaskarla]

This should create a core file in where you are executing this command. Run the file command on the core file and see if you see any kind of SEGV messages. If so, you need to consider changing your memory related parameters.

-Sri

[Magdi KAMAL]

Hi,

Findout the core file generated by the core dump, and run the following command to see which process or action is generating the core :

# strings core ? more

It's a start point to see which executable is core dumping.

Magdi

[Manel Ventura]

Upps, I've looked at the RevealNet server messages:

ORA-07445 exception encountered: core dump [string] [string] [string] [string] [string] [string]

Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.

Action: Contact Oracle Customer Support.

[T G Manikandan]

Hello,
Core dump can be of several issues.
One of the issues could be your shared pool size.
It could also be of some other reason.
Please attach your oracle trace files for to examine.
Thanks
G Manikandan

[AlHassani Mohamed]

An ora-7445 can have different causes. The error message only means that a core dump has occured during the excecution of the action. This usually means that the shadow process on the Oracle side has terminated with a core dump. To identify the cause of the error, you must first conduct a closer examination. The error can ssentially have the following causes:
o Incorrectly set NLS environment variables
o Corrupt blocks on the Oracle level
o A bug in the Oracle software
o Problems with the operating sysem/hardware
The following is critical to analyze the problem more closely:
o the core dump arguments: The first two arguments provides additional information regarding the cause of the error.
T examine the problem more closely, proceed as follows:
1. Has the NLS environment been set orrectly? If client Process ttempts to log onto the database, its NLS environment must either
agree with the one that the database was started with or it must be compatible with this one.
ORA_NLS
ORANLS32
ORANLS33
NLS_LANG
NLS*: essentially no NLS environment variables other than the four described above should be set.Differences can exist in the path for ORA_NLS33. Essentially the NLS environment
variables are compatible for all Oracle 8.X releases. If for example, ORA_NLS33 ..ocommon/nls/admin/data for oraSID and in ..ocommon/NLS_805/admin/data for. Make sure that thedirectories exist and the files are located in the directories to which the environment variables point.
2. Was the error caused by corrupt blocks on Oracle level? Because a statement is usually executed a lot of times if such an error occurs,check in several trace files as to what extent the same table is always referenced in the statements.
Then execute the following statements for each table for which the error is delivered:
svrmgrl
svrmgr> connect system/
svrgr> analyze table validate structure cascade;
If only a 'statement processed' message is returned for this statement, the table has no
corruption. Otherwise the returned error
should be reported to ORACLE
Mo.