SAP Knowledge Base Article - Preview

2761091 - Error 632 or Signal 11 in exc_raise() caused by Full Database Encryption - SAP ASE 16.0

Symptom

  • Full Database Encryption fails with Error 632 followed by a stack trace:

The encryption of database 'ABC' has started.
Error: 632, Severity: 20, State: 2
Attempt to move memory with an incorrect length of -36335. Maximum allowed length is 16384.
DB Encryption Worker: The encryption of the pages failed. Please contact SAP Technical Support for assistance.

  • This is a sample command executed via isql:

use master
go
alter database ABC encrypt with DEK
go

  • The stack trace for the failing spid includes functions:

memmove_error
ea_bufencrypt
bufawrite
ea_encrypt_decrypt_pages

  • Alternatively the "Infected with signal 11" error in the module exc_raise*() followed by a stack trace can occur during Full Database Encryption or Decryption:

Current process (0x0) infected with signal 11 (SIGSEGV)
Address 0x0x0000000001d3aa4f (exc_raise+0x3f), siginfo (code, address) = (1, 0x0x000000000000bcb0)

  • The corresponding stack trace includes functions:

exc_raise
memmove_error
ea_bufdecrypt
brfinish

   Note: A complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise 16.0
  • SAP Adaptive Server Enterprise 16.0 for Business Suite

Product

SAP Adaptive Server Enterprise 16.0

Keywords

812183, CR812183, CR#812183, CR817680, CR#817680, 817680, SEGV, segmentation, storage, access, violation, fault, segfault, kisignal, stacktrace,  registers , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , 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.