Printable View
I get these errors and the database crashes ??
Oracle says that this is memory heap corruption ??
HAs anyone encountred the same
Any help will be of much use
Wed Dec 19 19:58:29 2001
Errors in file /opt/app/oracle/admin/SPRD/udump/sprd_ora_11806.trc:
ORA-00600: internal error code, arguments: [17114], [26054788], [], [], [], [],
[], []
This is a memory corruption error and could result due to the heap corruption. To further investigate this problem set the event in your ini.ora and bounce the instance. Such that when it were to occour next time it would generate a detail trace under udump. Then contact oracle.
My personal undestanding of this problem is that the corruption could have occoured at Call heap, PGA heap, session heap or SGA heap. The event trace can only pin point the exact location. On some occassions increasing the java_pool_size and shared_pool_size would help to solve the problem.Code:
event="10235 trace name context forever, level 1"
Sam
******************************************************
HEAP DUMP heap name="pga heap" desc=0x185e1d8
extent sz=0x213c alt=40 het=32767 rec=0 flg=3 opc=3
parent=0 owner=0 nex=0 xsz=0xfe28
EXTENT 0
Chunk 1aa72d4 sz= 65056 free " "
EXTENT 1
Chunk 1946d84 sz= 8500 free " "
EXTENT 2
Chunk 195107c sz= 8500 free " "
EXTENT 3
Chunk 195530c sz= 8500 free " "
EXTENT 4
Chunk 1a9749c sz= 65056 free " "
EXTENT 5
That's indeed pga heap .Do you know any work around to ensure that the database does not crashes ...
Try increasing the shared_pool_size. Also interested to know about the dbversion and os.
Sam
I have doubled the shared_pool_size (40MB)
The oracle version is 8.1.6.0.0 and OS is sun solaris 5.7
8.1.6.0 is quiet buggy. I would suggest that you put the patch set 3 to get it upgraded to 8.1.6.3. It was pretty stable.
Consider doing this upgrade rather than breaking your heads. This holidays is the great time to call your down time...
Sam