SAP Knowledge Base Article - Preview

2876868 - setuphadr failed with Signal 4 in sybnet__flt_init() - SAP ASE 16.0

Symptom

  • The setuphadr utility failed in the "materialize <SID> database" phase:

** HADR operation: sap_materialize auto, <site1>, <site2>, <SID>
** Message: failed

  • An "infected with signal 4" error with a stack trace is reported in the standby ASE server.

Current process (0x1270094) infected with signal 4 (SIGILL)
Address 0x0000000000000000 (), siginfo (code, address) = (30, 0x0000000000000000)

  • The stack trace includes the following functions:

sybnet__flt_init
sybnet__nf_fixup_driver
sybnet_instfilter
sybnet_connect
np__conn_doconnect
ct_tds_connect
ct_async_exec_stack
ct__api_connect_async
ct_connect
usctconnect
omni_ct_connect
hadr_getremote_status
hadr_check_remote_nodes
hadr__propagate
hadr__addserver

   Note: A complete stack trace is available under Attachments.


Read more...

Environment

  • SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite
  • SAP Adaptive Server Enterprise (ASE) 16.0
  • High Availability Disaster Recovery (HADR)
  • AIX

Product

SAP Adaptive Server Enterprise 16.0

Keywords

CR#818642, CR818642, 818642, kisignal, stacktrace, registers, setup , 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 for Me (Login required).

Search for additional results

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