ORA-07445 or ORA-600 Errors With a Big Stack or a Corrupted Stack (文档 ID 1318825.1)

In this Document Symptoms   Cause   Solution APPLIES TO: Oracle Database - Enterprise Edition - Version 9.0.1.0 and later Information in this document applies to any platform. ***Checked for relevance on 28-Nov-2013***  SYMPTOMS You are experiencing ORA-7445 errors like (example): ORA-07445: exception encountered: core dump [kghalo()+4] [SIGSEGV] [Stack Overflow] [0xFFFFFFFF7FFF1F98] [] [] or ORA-600 errors pointing to memory issues The tracefile shows a big or possibly corrupted stack. For example: ssdgetcall: WARNING! *** STACK TRACE TRUNCATED *** ssdgetcall: WARNING! *** UNREADABLE FRAME FOUND *** CAUSE A possible cause is the oracle user stacksize limit being too low.  Several cases reported are due to the stacklimit set to the default value 8MB. Setting this to 16Mb and restarting the database from a new shell will correct this. SOLUTION Increase the stacksize limit for the oracle user to at least 16MB and make sure the database(s) and listener(s) are restarted from the oracle account