SAP Knowledge Base Article - Preview

2417271 - Signal 11 occurs when database is incorrectly encrypted - SAP ASE


  • Database is encrypted
  • run dbcc checkstorage that results in suspect conditions
  • run dbcc checkverify and signal 11 occurs
  • 1> dbcc checkstorage (database_name)
    2> go
    Checking <database_name>: Logical pagesize is 4096 bytes
    DBCC CHECKSTORAGE for database 'database_name' sequence 20 completed at Apr 10 2014
    9:26AM. 0 faults and 3 suspect conditions were located. 684 checks were aborted.
    You should investigate the recorded faults, and plan a course of action that
    will correct them.
    Suspect conditions are to be treated as faults if the same suspect condition
    persists in subsequent CHECKSTORAGE operations, or if they are also detected by
    other DBCC functions.
  • 1> dbcc checkverify (database_name)
    2> go
    Verifying faults for 'database_name'.
    Verifying faults for table '<table_name>'. The total number of tables to verify is 1.
    This is table number 1.
    [hangs here]



SAP Adaptive Server Enterprise (ASE) 16.0


SAP Adaptive Server Enterprise 16.0


Signal 11, SIGSEGV, dbcc checkverify, dbcc checkstorage, CR#761855, CR761855, 761855 , 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.