AWS sap documentation change
Summary
Updated URL formatting for SAP documentation links using hyphenated syntax instead of slashes
Security assessment
Changes involve link formatting adjustments without introducing or modifying security-related content. No evidence of addressing vulnerabilities or security features.
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 53aad3ea4..c8fb07ed1 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 [SAP Note 2518979 - HANA : how to check system replication status](https://launchpad.support.sap.com/#/notes/2518979). +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]. @@ -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 [Troubleshoot System Replication.](https://help.sap.com/docs/SAP_HANA_PLATFORM/4e9b18c116aa42fc84c7dbfd02111aba/782a0583f3af4a0992c5075b2ee7bd98.html?version=2.0.04) +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.] @@ -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 [SAP HANA Troubleshooting](https://ga.support.sap.com/dtp/viewer/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://launchpad.support.sap.com/#/notes/2934640). 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 {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.