System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8

[Former Member]

Hi,

We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.

Following is our system environment

SAP Release.............. "640"

Application server....... "abci"

Operating system......... "SunOS"

Release.................. "5.10"

Hardware type............ "sun4v"

Database server.......... "abdb"

Database type............ "ORACLE"

Database name............ "ABP"

Database owner........... "SAPABP"

SAP kernel............... "640"

Database version......... "OCI_920 "

Patch level.............. "175"

Following below is the Core Dump that is generated for any process chains that we schedule on our BW server

Runtime Errors SYSTEM_CORE_DUMPED

Date and Time 14.04.2008 09:26:17

ShrtText

Process terminated by signal 11.

What happened?

The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

The current ABAP program "SAPMSSY2" had to be terminated because the ABAP

processor discovered an invalid system state.

What can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

An SAP System process was terminated by an operating system signal.

-

Possible reasons for this are:

1. Internal SAP System error.

2. Process was terminated externally (by the system administrator).

-

-

---

Last error logged in SAP kernel

-

---

Component............ "Taskhandler"

Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"

Version.............. 1

Error code........... 11

Error text........... "ThSigHandler: signal"

Description.......... " "

System call.......... " "

Module............... "thxxhead.c"

Line................. 9780

How to correct the error

The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often

contains a file called 'core'.

Save this file under another name.

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, select the Editor function "Further Utilities->

Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Kindly help.

Regards

Sachin

Edited by: Sachin N on Apr 14, 2008 12:26 PM

[Former Member]

Can these errors occur if env variables are not properly set??

Anu

[markus_doehr2]

No. If the environment would be wrong the system wouldn´t start up.

Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.

If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.

Markus

[Former Member]

d

Edited by: anu apte on Jun 30, 2008 1:18 PM

[Former Member]

hi,

Our problem was due to the mismatch in Oracle client and database version, there were some old oracle client files in the client directory, we rename the oracle client directory to old and extracted the new Oracle Client 9208.

That resolved the problem for us.

Sachin

[stefan_koehler]

Hello Sachin,

unfortunately you didn't tell us anything about your system (32-bit / 64-bit, etc..)

Take a look at the following sapnotes:

- Sapnote #647378:

>#define SIGSEGV 11 /* segmentation violation */

- Sapnote #429635

- Sapnote #350167

Regards

Stefan

[markus_doehr2]

> unfortunately you didn't tell us anything about your system (32-bit / 64-bit, etc..)

Solaris + 6.40 is ONLY 64bit

Did you install the latest interim patches as of note 938986 - Oracle Database 9.2: Patches for 9.2.0?

What might help to dig would be the C-stack trace in the dump in ST22 or in the corresponding workprocess trace.

Markus

[fidel_vales]

I would suggest also to check the oracle client.

Please, upgrade also it to 9.2.0.8 on the AS.

On the DB server it should not be necessary as you should have a soft link from the oracle client directories to the equivalent directories on the $ORACLE_HOME

[Former Member]

hi Fidel,

yes we have upgraded the Oracle client on the application and central instance server.

Regards

Sachin

[Former Member]

Hi Markus,

Yes we are having 64bit Solaris 10.

I did refer the SAP note 938986 but I haven't installed any latest interim patches.

What do i need to look into workprocesses trace file.

Regards

Sachin

[markus_doehr2]

If you scroll to the very bottom you will find a section

"Active Calls in SAP Kernel

Lines of C Stack in Kernel (Structure Differs on Each Platform)"

Post that stack.

Markus