SAP Knowledge Base Article - Preview

2904986 - RMA not returning correct status after restarting HADR - SRS

Symptom

  • companion RMA sap_status no longer reports the replication status after HADR restart:

1> sap_status path
2> go

PATH NAME VALUE INFO
---------- ------------ ---------------------------- -------------------------------
Start Time Sat Mar 8 08:45:26 CET 2020 Time command started executing.
Elapsed Time 00:00:00 Command execution time.
(2 rows affected)

1> sap_status route
2> go

PATH SEQUENCE NAME TYPE QID SPID SITE STATE BACKLOG
---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ----------
(0 rows affected)

 

  • companion RMA error log shows:

    "[ERROR] [Thread-39:74][RMA] - [ProxyGetLog ] - Task hadrGetLog - Failed with error message - Invalid logical name: SITE2."

    "[ERROR] [Thread-42:78][RMA] - [ProxyGetTicketHistory ] - Task hadrGetTicketHistory - Failed with error message - There is no host associated with the logical name SITE1."


  • RMA errorlog reported a stacktrace:

    2020-03-07 04:57:35 [ERROR] [TaskEngine_72486(ComponentStopTask):244359][LOGGER] - Diagnostic Data for Exception com.sybase.rs.repository.api.RepositoryException
    Detected by: com.sybase.rs.container.agent.ContainerAgent
    Thread: TaskEngine_72486(ComponentStopTask) - [244,359]
    Description: Error Storing State Object for ContainerAgent:SavedSpecifiedAgentMap

    StackTrace
    ( 0) - com.sybase.rs.repository.api.RepositoryServicesImpl.setState(RepositoryServicesImpl.java:386)
    (-1) - com.sybase.rs.repository.RepositoryServiceImpl.setState(RepositoryServiceImpl.java:384)
    (-2) - com.sybase.rs.container.agent.ContainerAgent.shutdown(ContainerAgent.java:375)
    (-3) - com.sybase.rs.container.runtime.ComponentManagerImpl.stopComponent(ComponentManagerImpl.java:242)
    (-4) - com.sybase.rs.container.runtime.ComponentStopTask.call(ComponentStopTask.java:80)
    (-5) - com.sybase.rs.container.taskservices.PoolRunnable.run(PoolRunnable.java:100)
    (-6) - java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
    (-7) - java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
    (-8) - com.sybase.rs.container.taskservices.PoolThread.run(PoolThread.java:73)

    Caused by: com.sybase.rs.repository.store.DataStoreException : SQL Exception Encountered Updating State ComponentName[ContainerAgent] ParmName[SavedSpecifiedAgentMap] ParmObject[{}] ParmClass[java.util.HashMap] Version[1.0] LastUpdate[0] Description[Saved Specified Agent Map]

    StackTrace
    ( 0) - com.sybase.rs.repository.store.jdb.JDBStore.writeState(JDBStore.java:986)
    (-1) - com.sybase.rs.repository.api.RepositoryServicesImpl.setState(RepositoryServicesImpl.java:383)
    (-2) - com.sybase.rs.repository.RepositoryServiceImpl.setState(RepositoryServiceImpl.java:384)
    (-3) - com.sybase.rs.container.agent.ContainerAgent.shutdown(ContainerAgent.java:375)
    (-4) - com.sybase.rs.container.runtime.ComponentManagerImpl.stopComponent(ComponentManagerImpl.java:242)
    (-5) - com.sybase.rs.container.runtime.ComponentStopTask.call(ComponentStopTask.java:80)
    (-6) - com.sybase.rs.container.taskservices.PoolRunnable.run(PoolRunnable.java:100)
    (-7) - java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
    (-8) - java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
    (-9) - com.sybase.rs.container.taskservices.PoolThread.run(PoolThread.java:73)

    Caused by: java.sql.SQLException : An SQL data change is not permitted for a read-only connection, user or database.
    SQLCode: 30,000
    SQLState: 25502

    StackTrace
    ( 0) - org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
    (-1) - org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
    (-2) - org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source)
    (-3) - org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source)
    (-4) - org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source)
    (-5) - org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source)
    (-6) - org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source)
    (-7) - org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown Source)
    (-8) - org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown Source)
    (-9) - com.sybase.rs.repository.store.jdb.DBStateElement.updateToPreparedStatement(DBStateElement.java:126)
    (-10) - com.sybase.rs.repository.store.jdb.JDBStore.writeState(JDBStore.java:982)
    (-11) - com.sybase.rs.repository.api.RepositoryServicesImpl.setState(RepositoryServicesImpl.java:383)
    (-12) - com.sybase.rs.repository.RepositoryServiceImpl.setState(RepositoryServiceImpl.java:384)
    (-13) - com.sybase.rs.container.agent.ContainerAgent.shutdown(ContainerAgent.java:375)
    (-14) - com.sybase.rs.container.runtime.ComponentManagerImpl.stopComponent(ComponentManagerImpl.java:242)
    (-15) - com.sybase.rs.container.runtime.ComponentStopTask.call(ComponentStopTask.java:80)
    (-16) - com.sybase.rs.container.taskservices.PoolRunnable.run(PoolRunnable.java:100)
    (-17) - java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
    (-18) - java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
    (-19) - com.sybase.rs.container.taskservices.PoolThread.run(PoolThread.java:73)

    Caused by: org.apache.derby.impl.jdbc.EmbedSQLException : An SQL data change is not permitted for a read-only connection, user or database.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

  • SAP Replication Server (SRS) 16.0
  • SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
  • SAP Adaptive Server Enterprise (ASE) 16.0 with High Availability Disaster Recovery (HADR) for Business Suite  

Product

SAP Adaptive Server Enterprise 16.0 ; SAP Replication Server 16.0

Keywords

RepServer, RS, RMA, sap_status, not working, HADR , KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , 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.