Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When a SAP central services (SCS) or ABAP SAP central services (ASCS) instance with enqueue replication performs a failover from one node to an adoptive node in a HPE Serviceguard Extension for SAP for Linux cluster, the SCS package will start on the node where the enqueue replication server (ERS) package is currently running. Both packages will run on the same node until the SCS has completed enqueue takeover from the replicated enqueue table maintained by the ERS. This is normal SAP operation. When this operation is completed, the ERS package will halt on the current node and attempt to start on some other cluster node. Simultaneously, the SCS package will complete startup and the sapenq.mon monitor will initialize before the ERS package has started on another node. During this initialization process, the sapenq.mon will check to determine if replication is established and print a warning similar to the following text in the package log if it is not established: ====== Aug 1 11:14:12 root@node1 sapenq.mon[25746]: (sapenq.mon,getJCIInitialReplicationStatus): WARNING: Replication process for SCS02 is not connected ====== This is not fatal to the SCS because the SCS is able to run without replication. However, when the ERS package start completes and replication is reconnected, the SCS package does not log a subsequent message later indicating that replication has been connected. The last message in the package log is the WARNING "Replication process for SCS<NR> is not connected;" although, the replication is functioning as expected. The message may cause confusion especially if it is displayed after an earlier package failure due to some other issue with sapenq.mon detecting a fatal problem. In this WARNING case, the problem is not fatal and is clearly labelled "WARNING;" however, no subsequent message is logged even though the enqueue replication is reconnected. It is safe to ignore the WARNING message. Any fatal condition regarding enqueue replication that is detected by the monitor will be appropriately logged and handled.
Any current HPE Serviceguard Extension for SAP implementation on Linux (12.50.03 or earlier) for packages that package SCS or ASCS SAP instances and use enqueue replication.
The WARNING message generated by the sapenq.mon getJCIInitialReplicationStatus function during package start and initialization after a failover can be safely ignored. Any fatal condition regarding enqueue replication that is detected by the monitor once it is running will be appropriately logged and handled. This message does not indicate any ongoing problem with enqueue replication and it is not fatal to the SCS instance. If additional information becomes available, this advisory will be updated. RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form. NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for HPE systems and Options, refer to the Navigation Tips document . SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document . To search for additional advisories related to Linux, use the following search string: +Advisory +ProLiant -"Software and Drivers" +Linux