SAP Knowledge Base Article - Preview

2057593 - Stack trace in cri__empty_idxptn and ptn_get_aphintpage() -SAP ASE

Symptom

issue with create index/reorg rebuild.
Signal 11 in ptn_get_aphintpage() while page allocation for index in creation.

 

When executing a CREATE INDEX or REORG REBUILD command, a stacktrace below may be reported in errorlog :

Current process (0x2ef01cf) infected with signal 11 (SIGSEGV)

ucstkgentrace+0x177()
ucbacktrace+0x12a()
terminate_process+0x11c2()
kisignal+0x38e()
ptn_get_aphintpage+0x23()
pg__allocate+0x1d7()
pg_allocate+0x61()
cri__empty_idxptn+0x1ef()
cri_bldemptyind+0x2e6()
01b816b0 ut_handle installe
cri_physbuild+0x645()
cri_bldindex+0xe43()
01b816b0 ut_handle installe
cri_main+0x9ee()
s_execute+0x73cf()

 


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 15.7

Product

SAP Adaptive Server Enterprise 15.7

Keywords

cri__empty_idxptn, ptn_get_aphintpage() , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

About this page

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

Search for additional results

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