ORA-600 [kclfadd_1] instance crash


点击(此处)折叠或打开

  1. Sat Dec 16 03:37:19 2017
  2. Errors in file /u01/admin/anbob/udump/anbob2_ora_577604.trc:
  3. ORA-00600: internal error code, arguments: [kclfadd_1], [], [], [], [], [], [], []
  4. ORA-00600: internal error code, arguments: [kclfadd_1], [], [], [], [], [], [], []
  5. Sat Dec 16 03:37:21 2017
  6. Errors in file /u01/admin/anbob/bdump/anbob2_pmon_2076852.trc:
  7. ORA-00600: internal error code, arguments: [kclfadd_1], [], [], [], [], [], [], []
  8. Sat Dec 16 03:37:22 2017
  9. Errors in file /u01/admin/anbob/bdump/anbob2_pmon_2076852.trc:
  10. ORA-00600: internal error code, arguments: [kclfadd_1], [], [], [], [], [], [], []
  11. Sat Dec 16 03:37:22 2017
  12. PMON: terminating instance due to error 472
  13. Sat Dec 16 03:37:22 2017
  14. Errors in file /u01/admin/anbob/bdump/anbob2_lmon_1974576.trc:
  15. ORA-00472: PMON process terminated with error
  16. Sat Dec 16 03:37:22 2017
  17. Errors in file /u01/admin/anbob/bdump/anbob2_lmd0_2183646.trc:
  18. ORA-00472: PMON process terminated with error
  19. Instance terminated by PMON, pid = 2076852
  20. Sat Dec 16 03:37:54 2017
  21. Starting ORACLE instance (normal)
  22. LICENSE_MAX_SESSION = 0
  23. LICENSE_SESSIONS_WARNING = 0
  24. Interface type 1 en1 192.192.192.0 configured from OCR for use as a cluster interconnect
  25. Interface type 1 en0 10.24.1.0 configured from OCR for use as a public interface
  26. Picked latch-free SCN scheme 3
  27. Autotune of undo retention is turned on.
  28. LICENSE_MAX_USERS = 0
  29. SYS auditing is disabled
  30. ksdpec: called for event 13740 prior to event group initialization
  31. Starting up ORACLE RDBMS Version: 10.2.0.2.0.

Cause

Bug:5071492 LMS CRASH WITH ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KCLASTF_1], [2]

This problem only affects 64bit releases of Oracle.
In a RAC environment a global cache element structure can
become corrupted leading to various ORA-600 and instance crashes.


Solution

It is recommended to:

1) Apply a Patch Set where this issue is fixed (10.2.0.3 onwards)

or


2) Apply  one off patch for your platform if it's available, please check PATCH 5071492.



请使用浏览器的分享功能分享到微信等