Skip to content

Fixed extended validation errors (IDs, empty inlines) #514

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chabowski merged 1 commit into from
Oct 1, 2025
Merged

Fixed extended validation errors (IDs, empty inlines) #514

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 19 additions & 19 deletions adoc/SAP-NetWeaver-7.50-SLE-15-Setup-Guide-AliCloud.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1867,7 +1867,7 @@ Check <<Cluster-Integration-of-Fault-Manager>> before you start the installation
----

This is an example of the installation process:
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
replication manager agent user DR_admin and password set in Secure Store.
Keep existing values (yes/no)? (yes)
Expand Down Expand Up @@ -1967,7 +1967,7 @@ A few parameters that need to be updated in the _SYBHA.PFL_ to make the fail-ove

.For option 1 [[Option-1]] the _SYBHA.PFL_ file in case of ASCS integration.
======================================
[subs="specialchars,attributes,verbatim,quotes"]
[subs="specialchars,attributes"]
----
ha/syb/support_cluster = 1
ha/syb/fail-over_if_unresponsive = 1
Expand All @@ -1983,7 +1983,7 @@ ha/syb/dbfmhost = **virtual hostname of ASCS instance**

.For option 2 [[Option-2]] the _SYBHA.PFL_ file in case of independent integration.
======================================
[subs="specialchars,attributes,verbatim,quotes"]
[subs="specialchars,attributes"]
----
ha/syb/support_cluster = 1
ha/syb/fail-over_if_unresponsive = 1
Expand All @@ -2004,7 +2004,7 @@ _ha/syb/cluster_fmhost2_ provide the physical host names of both nodes where the

._As user {mysapadm}_, check if the `sybdbfm` process is shown.
======================================
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
{mysapadm}> sapcontrol -nr {myAscsIno} -function GetProcessList

Expand Down Expand Up @@ -2032,7 +2032,7 @@ _sybdbfm.sap.<SID>_ASCS<instance number> status_ :

_As user {mysapadm}_ for ASCS integration, do:

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# cd /usr/sap/<SID>/ASCS<instance number>/work
# ./sybdbfm.sap<SID>_ASCS<instance number> status
Expand All @@ -2051,7 +2051,7 @@ failover prerequisites fulfilled: YES.

_As user {mysapadm}_ for stand-alone integration, do:

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# cd /usr/sap/{mySid}/{aseInst}/work
# ./sybdbfm status
Expand All @@ -2072,7 +2072,7 @@ Checking the log file is also a suitable method to validate the status.

_As user {mysapadm}_, do:

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# cd /usr/sap/<SID>/ASCS<instance number>/work
# tail -f dev_sybdbfm
Expand Down Expand Up @@ -2149,12 +2149,12 @@ In the example, we use the following values:
- <instance number> => {myAscsIno}
- virtual host name => {myVipNAscs}

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# crm configure edit rsc_sap_{mySid}_ASCS{myAscsIno}
----

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
primitive rsc_sap_{mySid}_ASCS{myAscsIno} SAPInstance \
operations $id=rsc_sap_{mySid}_ASCS{myAscsIno}-operations \
Expand Down Expand Up @@ -2200,7 +2200,7 @@ service with the ASCS, you must separate them first.
.Option two:
=============================================
Host preparation on all nodes which are cluster members.
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes,quotes"]
----
# mkdir -p /usr/sap/{mySid}/{aseInst}
## adding the vIP and the host name of FM instance
Expand All @@ -2211,7 +2211,7 @@ You must execute the separation steps only on one cluster node. If the Fault Man
The Fault Manager configuration must be uncommented in the ASCS profile.
Edit the file _/usr/sap/{mySid}/SYS/profile/{mySid}____{myInstAscs}____{myVipNAscs}_ and uncomment the Fault Manager sections.

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
#-----------------------------------------------------------------------
# copy sybdbfm and dependent
Expand All @@ -2236,7 +2236,7 @@ Edit the file _/usr/sap/{mySid}/SYS/profile/{mySid}____{myInstAscs}____{myVipNAs
Now you need a *new* instance profile for the Fault Manager. You can take a *copy* of the ASCS profile and adapt it carefully.

*The result should look like this:*
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# cat /usr/sap/{mySid}/SYS/profile/{mySid}_{aseInst}_{myVipNFM}
SAPSYSTEMNAME = {mySid}
Expand Down Expand Up @@ -2279,15 +2279,15 @@ service/halib_cluster_connector = /usr/bin/sap_suse_cluster_connector
The SAP _sapstartsrv_ needs an entry in the _/usr/sap/sapservices_ for the Fault Manager. This must be done on *all* cluster nodes.
The ASCS entry can be used as template for the Fault Manager. The ERS entry is different and cannot be used as a template.

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# cat /usr/sap/sapservices
...
LD_LIBRARY_PATH=/usr/sap/{mySid}/{aseInst}/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/{mySid}/{aseInst}/exe/sapstartsrv pf=/usr/sap/{mySid}/SYS/profile/{mySid}_{aseInst}_{myVipNFM} -D -u {mySapAdm}
----

Before you can test if the Fault Manager is able to start as single instance, you need some files.
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# ip a a {myVipAFM} dev eth0
# mount {myDevPartFM} /usr/sap/{mySid}/{aseInst}
Expand All @@ -2300,7 +2300,7 @@ Before you can test if the Fault Manager is able to start as single instance, yo
----

The new configuration can be tested as shown. Use `CTRL+c` to stop it.
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# LD_LIBRARY_PATH=/usr/sap/{mySid}/{aseInst}/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH;
# /usr/sap/{mySid}/{aseInst}/exe/sapstartsrv pf=/usr/sap/{mySid}/SYS/profile/{mySid}_{aseInst}_{myVipNFM} -u {mySapAdm}
Expand All @@ -2312,15 +2312,15 @@ SAP Service SAP{mySid}_{aseIno} successfully started.
If the result *successfully started* is shown, use `Ctrl+c` and interrupt the process. Now do the live
test with the `sapstart` framework. In any other cases check your log files, for example _/usr/sap/{mySid}/{aseInst}/work_.

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# sapcontrol -nr {aseIno} -function StartService {mySid}
# sapcontrol -nr {aseIno} -function Start
----

_As user {mysapadm}_, check if the _sybdbfm_ process is shown:

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# sapcontrol -nr {aseIno} -function GetProcessList

Expand All @@ -2338,7 +2338,7 @@ sybdbfm, , GREEN, Running, 2020 04 22 18:28:31, 27:43:21, 17733
Prepare a file which contains the resource for the Fault Manager. We are using the same method of three primitives
(IP, file system, SAP Instance) as used for the ASCS or ERS. The values must be adapted to your infrastructure.

[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# vi crm-fm.txt
primitive rsc_fs_{mySid}_{aseInst} Filesystem \
Expand All @@ -2364,7 +2364,7 @@ group grp_{mySid}_{aseInst} rsc_ip_{mySid}_{aseInst} rsc_fs_{mySid}_{aseInst} rs
----

*Upload the configuration to the cluster and check the cluster*
[subs="specialchars,attributes,quotes,verbatim"]
[subs="specialchars,attributes"]
----
# crm configure load update crm-fm.txt
# crm status
Expand Down
4 changes: 2 additions & 2 deletions adoc/SAP-S4HA10-setupguide-sle15.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ For deploying new HA clusters, please use the simple-mount setup, described in
"SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster With Simple Mount - Setup Guide"
(https://documentation.suse.com/en-us/sbp/sap-15/html/SAP-S4HA10-setupguide-simplemount-sle15/).

[id="sec.resource"]
[id="sec-resource"]
=== Additional documentation and resources

Several chapters in this document contain links to additional documentation resources that
Expand Down Expand Up @@ -119,7 +119,7 @@ NOTE: This guide implements the cluster architecture for enqueue replication ver
versions 1809 or newer enqueue replication version 2 is the default.

This guide focuses on the high availability of the central services. For {saphana} system replication
consult the guides for the performance-optimized or cost-optimized scenario (see <<sec.resource>>).
consult the guides for the performance-optimized or cost-optimized scenario (see <<sec-resource>>).

NOTE: This setup with cluster-controlled file system resources has been obsoleted by the
so-called simple-mount setup. The setup with cluster-controlled file systems
Expand Down
4 changes: 2 additions & 2 deletions l10n/ko-kr/xml/SAP_S4HA10_SetupGuide-SLE15.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -627,7 +627,7 @@ User dbhadm 2003</screen>
# sapcontrol -nr 10 -function StopService</screen>
</section>
<section xml:id="id-maintaining-sapservices">
<title><emphasis/>sapservices 관리</title>
<title>sapservices 관리</title>
<para>두 클러스터 노드 모두에서 <emphasis>/usr/sap/sapservices</emphasis>에 두 항목(ASCS 및 ERS)이 모두 있는지 확인합니다. 이를 통해 <emphasis role="strong">sapstartsrv</emphasis> 클라이언트가 다음과 같이 서비스를 시작할 수 있습니다.</para>
<para><emphasis>en2adm</emphasis> 사용자로 다음 명령 입력:</para>
<screen># sapcontrol -nr 10 -function StartService EN2</screen>
Expand All @@ -645,7 +645,7 @@ LD_LIBRARY_PATH=/usr/sap/EN2/ERS10/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH;
-reg</screen>
</section>
<section xml:id="id-integrating-the-cluster-framework-using-sap-suse-cluster-connector">
<title><emphasis/>sap-suse-cluster-connector를 사용하여 클러스터 프레임워크 통합</title>
<title>sap-suse-cluster-connector를 사용하여 클러스터 프레임워크 통합</title>
<para>SUSE 리포지토리에서 <emphasis role="strong">sap-suse-cluster-connector</emphasis> 패키지 버전 3.1.0 설치:</para>
<screen># zypper in sap-suse-cluster-connector</screen>
<note>
Expand Down