3548411 - Application can't connect to database after tear down HADR for SAP ASE for BS

• HADR got removed by sap_teardown/removehadr successfully, however still application can't connect to database
• Verified in primary and companion ASE for HADR status all returned correctly as No HADR:
  1> select hadr_mode(), hadr_state()
  2> go
   
  ------------------------------ ------------------------------
  No HADR                        Unknown
  
  
• No error in primary ASE database server
• From application host test connection with command 'R3trans -d' as user '<SID>adm', in trans.log reported messages:
  
  4 ETW000  [     dev trc,00000]  dbs/syb/cache_size: 200
  4 ETW000  [     dev trc,00000]  Can't run against non primary server (hadr_mode is -1)
  4 ETW000  [     dev trc,00000]  CheckHadrPrimary failed. Connect terminated.
  4 ETW000  [    dblink  ,00000]  ***LOG BY2=>sql error 99980  performing CON
  4 ETW000  [    dblink  ,00000]  ***LOG BY0=>[ASE Error SQL99980]Can't run against non primary server.
  2EETW169 no connect possible: "DBMS = SYBASE --- "

• SAP Adaptive Server Enterprise (ASE) 16.0
• High Availability Disaster Recovery (HADR)

sybase, BS, SAP Business Suite, removehadr, teardown, failed, error, R3trans -X, down , KBA , BC-DB-SYB , Business Suite on Adaptive Server Enterprise , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Problem