Bug 20505778 Private memory corruption / ORA-7445 [kfuhRemove] / ORA-7445 [kghstack_underflow_internal] / ORA-600[17147] from DBA_TABLESPACE_USAGE_METRICS

select * from gv$instance查看startup_time，

发现4节点自动重启过，导致service漂移到其他节点。未及时发现，导致一节点负载异常。

alert及trace文件发现ora-600错误。

Bug 20505778  Private memory corruption / ORA-7445 [kfuhRemove] / ORA-7445 [kghstack_underflow_internal] / ORA-600[17147] from DBA_TABLESPACE_USAGE_METRICS

 This note gives a brief overview of bug 20505778.
 The content was last updated on: 17-APR-2018
 Click here for details of each of the sections below.

Affects:

Product (Component)	Oracle Server (Rdbms)
Range of versions believed to be affected	Versions BELOW 12.2
Versions confirmed as being affected	12.1.0.2 (Server Patch Set) 11.2.0.4
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 20505778 is first included in

12.2.0.1 (Base Release) 12.1.0.2.180417 (Apr 2018) Database Patch Set Update (DB PSU) 12.1.0.2.170418 (Apr 2017) Database Proactive Bundle Patch 12.1.0.2.170228 (Feb 2017) Bundle Patch for Windows Platforms

Interim patches may be available for earlier versions - click here to check.

Symptoms:	Related To:
Process May Dump (ORA-7445) / Abend / Abort Memory Corruption Internal Error May Occur (ORA-600) ORA-600 [17147]] Dump in or under kfuhremove / kghstack_underflow_internal Stack is likely to include ktte_get_maxsize1 Stack is likely to include kttets_cb Can affect KGHSTACK memory Can affect PGA memory	Performance Monitoring DBA_TABLESPACE_USAGE_METRICS

Description

Function ktte_get_maxsize1 can cause KGH stack memory corruption due to string overwrite
of a buffer that is too short.
 
Rediscovery Notes
  This can show as memory corruption errors like the above ORA-600 / ORA-7445 if a 
  session selects from DBA_TABLESPACE_USAGE_METRICS if a tablespace datafile
  is not auto extendable.
 
Workaround
  None.
 

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. For questions about this bug please consult Oracle Support.

References

Bug:20505778 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article