SAP Knowledge Base Article - Preview

2655466 - ASE crash after Object Coherency Manager error during ocm_lock:CONVERT and signal 11 in ocm_lock() - SAP ASE

Symptom

  • ASE log reports (many) Object Coherency Manager messages:

Internal Error!! Object Coherency Manager received error from Cluster Lock Manager during ocm_lock:CONVERT

  • Followed by a signal 11 in the module ocm_lock() whcich may be seen some time after above messages first started:

Current process (0x11d109bd) infected with signal 11 (SIGSEGV)
Address 0x0x0000000000f4ab83 (ocm_lock+0x733)

  • With a stack trace that includes modules:

ocm_lock
ptn_nextcopy
par_get_ptnids
par_get_info

  Note: A complete stack trace is available under Attachments.

  • The signal 11 crashes ASE as it is holding the partition (Pdes) spinlock:

Spinlocks held by  kpid 123456789
Spinlock Pdes Spinlocks at address 0x00002aaab0535800 owned by 123456789
End of spinlock display.


Read more...

Environment

SAP Adaptive Server Enterprise Cluster Edition (ASE CE) 15.7

Product

Sybase Adaptive Server Enterprise Cluster Edition 15.7

Keywords

CR815482,  CR#815482,  815482, CONVERT, shutdown, abort, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  registers , KBA , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.