Symptom
- Error log reports: "Current process infected with signal 11 (SIGSEGV)" in module 'pchk_hash_search' during concurrent DBCC CHECKSTORAGE.
- sp_monitorconfig "number of worker processes" shows incorrect Num_active value.
- Issue observed after upgrade to ASE 16.1.
- A typical log sequence includes:
Current process infected with signal 11 (SIGSEGV) at 0x0x0000000001556116 (pchk_hash_search+0x96)
with stack functions
pchk_hash_searc
pchk_page_row
pchk_ndx_page
pchk_page
pchk_all_pages
pchk_scan_work
pchk_scan_mainError: 9970, Severity: 20, State: 1
DBCC cannot update the finish time in dbcc_operation_log table for this operation(opid = '13') of database 'data_govcorp'. This can be patched by executing sp_dbcc_patch_finishtime.Address 0x0x000000000107ac08 (prPCHK_INDEX_CHECK_IND+0x93)
Current process (0x77d03bf) infected with signal 11 (SIGSEGV)
SQL Text: insert dbcc_operation_log(dbid, opid, optype, suid, start, seq, id) values(16, 13, 2, 1, getdate(), null, null)
curcmd = 317 (DBCC_CMD) program = isqlwith stack functions
prPCHK_INDEX_CHECK_IND
pchk_get_all_rids
checkstorage
Read more...
Environment
- SAP Adaptive Server Enterprise(ASE) 16.1
Product
Keywords
ase 16.1, dbcc checkstorage, pchk_hash_search, sigsegv, infected with 11, concurrent execution, parallelism, monitorconfig , 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.
SAP Knowledge Base Article - Preview