SAP Knowledge Base Article - Preview

3259488 - HADR failover did not happen from Primary to Standby after Primary node OS reboot - SAP SRS

Symptom

  • Automatic failover did not occur after Primary node rebooted from OS level.
  • Standby RMA (Replication Management Agent) log displays something like:

2022-10-14 03:33:54 [ERROR] [Failover:161566][RMA] - [HADRPromoteASE           ] - Task Promote the ASE - Failed with error message - Unable to execute the command to promote the ASE '<DB_server_name>' on host '<logical_hostname>' to the primary site.
2022-10-14 03:33:54 [ERROR] [Failover:161566][RMA] - [HADRPromoteASE           ] - Task Promote the ASE - Failed with Exception - Message: 'The current 'max memory' value '28039191', is not sufficient to change the parameter 'HADR mode' to '1'. 'max memory' should be greater than 'total logical memory' '28053335' required for the configuration.' Cause: ''.
2022-10-14 03:33:54 [TRACE] [Failover:161566][RMA] - [HADRPromoteASE           ] - Task Promote the ASE - Failed with Stack Trace - The current 'max memory' value '28039191', is not sufficient to change the parameter 'HADR mode' to '1'. 'max memory' should be greater than 'total logical memory' '28053335' required for the configuration.
com.sybase.jdbc4.jdbc.SybSQLException: The current 'max memory' value '28039191', is not sufficient to change the parameter 'HADR mode' to '1'. 'max memory' should be greater than 'total logical memory' '28053335' required for the configuration.


Read more...

Environment

SAP Adaptive Server Enterprise (ASE) 16.0 with Always On Option (HADR)

Product

SAP Replication Server 16.0

Keywords

HADR, max memory , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , 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.