AWS sap documentation change
Summary
Updated documentation links to use proper markdown syntax and corrected URLs for SAP references
Security assessment
The changes only fix formatting of existing links and update URLs. No security vulnerabilities, mitigations, or security features are mentioned. The content remains focused on general troubleshooting procedures for SAP HANA replication.
Diff
diff --git a/sap/latest/sap-hana/hana-ops-ha-dr-troubleshoot.md b/sap/latest/sap-hana/hana-ops-ha-dr-troubleshoot.md index c8fb07ed1..6acc8b78b 100644 --- a//sap/latest/sap-hana/hana-ops-ha-dr-troubleshoot.md +++ b//sap/latest/sap-hana/hana-ops-ha-dr-troubleshoot.md @@ -9 +9 @@ This section provides guidance for troubleshooting SAP HANA high availability de -A healthy status of SAP HANA system replication is a foundational requirement for the cluster solution to maintain stability. If SAP HANA system replication doesn’t have any dependencies on cluster solution, it can be independently verified using {https---launchpad-support-sap-com---notes-2518979}[SAP Note 2518979 - HANA : how to check system replication status]. +A healthy status of SAP HANA system replication is a foundational requirement for the cluster solution to maintain stability. If SAP HANA system replication doesn’t have any dependencies on cluster solution, it can be independently verified using [SAP Note 2518979 - HANA : how to check system replication status](https://me.sap.com/notes/2518979). @@ -11 +11 @@ A healthy status of SAP HANA system replication is a foundational requirement fo -For manual deployment, there must not be any underlying issues within the cluster member systems for their continuous system replication and takeover procedures. This must be independently verified before integrating a cluster solution for automation. SAP HANA system replication depends on various factors for functioning smoothly. To troubleshoot any issues, see {https---help-sap-com-docs-SAP-HANA-PLATFORM-4e9b18c116aa42fc84c7dbfd02111aba-782a0583f3af4a0992c5075b2ee7bd98-html-version-2-0-04}[Troubleshoot System Replication.] +For manual deployment, there must not be any underlying issues within the cluster member systems for their continuous system replication and takeover procedures. This must be independently verified before integrating a cluster solution for automation. SAP HANA system replication depends on various factors for functioning smoothly. To troubleshoot any issues, see [Troubleshoot System Replication.](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/782a0583f3af4a0992c5075b2ee7bd98.html?locale=en-US) @@ -13 +13 @@ For manual deployment, there must not be any underlying issues within the cluste -Alternatively, you can use guided troubleshooting provided by SAP. For more information, see {https---ga-support-sap-com-dtp-viewer-index-html—tree-1623-actions-21021-21032}[SAP HANA Troubleshooting]. You can also chat with experts or open an incident with SAP. For a speedy resolution, collect the relevant SAP HANA logs as per {https---launchpad-support-sap-com---notes-2934640}[SAP Note 2934640 - HANA and Replication - Collecting Support Data for Replication / Network related Tickets]. The _fullsysteminfo-dumps_ log must be collected from all the cluster member systems for a complete analysis. +Alternatively, you can use guided troubleshooting provided by SAP. For more information, see [SAP HANA Troubleshooting](https://ga.support.sap.com/index.html#/tree/1623/actions/21021:21032). You can also chat with experts or open an incident with SAP. For a speedy resolution, collect the relevant SAP HANA logs as per [SAP Note 2934640 - HANA and Replication - Collecting Support Data for Replication / Network related Tickets](https://me.sap.com/notes/2934640). The _fullsysteminfo-dumps_ log must be collected from all the cluster member systems for a complete analysis.