/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
- CPU temporarily spike after the termination of secondary site and the CPU consumption normalizes after log shipping timeout is identified.
- Massive transactional thread blockages can be observed.
- SYNC or SYNCMEM replication mode is used.
Read more...
Environment
- SAP HANA, platform edition 1.0
- SAP HANA, platform edition 2.0
- SAP HANA High Availability
Product
SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0
Keywords
cpu spike, uncommitted transactions, secondary shutdown, log shipping timeout, thread blockage, system replication , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)