From: Lynn Lacaillade (LynnL@BENJERRY.COM)
Date: Thu Jan 23 2003 - 11:46:36 EST
We were having trouble with the same errors. Our Oracle DBA found the
following;
The fix was to add the following to the init.ora. What it does is ignore
small space leaks, causing the error to not be generated. It will also
reduce the ORA-600s reported in the alert log.
# ***** EVENTS SET DUE TO BUGS ENCOUNTERED *****
# 08/20/02 See note 31056.1 - setting this event to ignore small ora-600
[729]
# Will ignore space leaks smaller than 102400
bytes
event = "10262 trace name context forever, level 102400"
Lynn Lacaillade
Unix Systems Administrator
Ben & Jerry's Homemade, Inc.
802-846-1543 x7860
mailto:lynnl@benjerry.com <mailto:lynnl@benjerry.com>
-----Original Message-----
From: Tom Wood [mailto:twood@REZLINK.COM]
Sent: Thursday, January 23, 2003 11:20 AM
To: aix-l@Princeton.EDU
Subject: CORE_DUMP from errpt -a
Hello,
I have received a couple of these reports and would like to know if any
would give me some assistance in trying to track down the culprit. Is there
any way of relating the inode number to a particular file? This is a 7026
(6m1) running 4.3.3 and Oracle 8.1.7.
Thanks
tom
---------------------------------------------------------------------------
LABEL: CORE_DUMP
IDENTIFIER: C60BB505
Date/Time: Tue Jan 21 11:22:37
Sequence Number: 7681
Machine Id: 0004872F4C00
Node Id: aixdb
Class: S
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Probable Causes
SOFTWARE PROGRAM
User Causes
USER GENERATED SIGNAL
Recommended Actions
CORRECT THEN RETRY
Failure Causes
SOFTWARE PROGRAM
Recommended Actions
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE
Detail Data
SIGNAL NUMBER
6
USER'S PROCESS ID:
126930
FILE SYSTEM SERIAL NUMBER
9
INODE NUMBER
671750
PROGRAM NAME
oracle
ADDITIONAL INFORMATION
??
slcra 354
ssexhd 2B0
??
Unable to generate symptom string.
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:31 EDT