SAP Knowledge Base Article - Preview

2262631 - Load database fails with signal 11 during the cross-platform conversion - SAP ASE

Symptom

  • A load database failes due to a signal 11
  • On the target server of during a cross-platform ASE migration
  • The signal 11 can be seen in the modules starting with 'lddb', for example lddb__translate or lddb__unscr_log
  • The ASE errorlog entries include:

    Current process (0x741f01d7) infected with signal 11 (SIGSEGV) 
    Address 0x0000000000d67399 (lddb__translate+0x4d), siginfo ...
    or
    Address 0x0x0000000000c14214 (lddb__unscr_log+0xa1),...

  • The stack trace includes some or all of the following modules:

    lddb__translate
    lddb__unscr_log
    lddb__unscr_phys_page
    lddb__unscr_phys_pages
    lddb__unscr_phys_usro
    lddb__unscr_usro
    lddb_unscramble


Read more...

Environment

  • Source:
    • SAP Adaptive Server Enterprise 
    • Big Endian OS
      • Solaris Sparc
      • AIX
         
  • Target:
    • SAP Adaptive Server Enterprise
    • Small Endian OS
      • Linux
      • Windows

Product

SAP Adaptive Server Enterprise all versions

Keywords

"segmentation violation",  lddb__translate, lddb__unscr_phys_page, lddb__unscr_phys_usro, lddb__unscr_usro, lddb_unscramble, dump, stacktrace , 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.