SAPHanaSR-manageProvider(8)

πŸ“¦ version 1.3.4, in opensuse-leap 16.0

πŸ’– NAME πŸ’–

SAPHanaSR-manageProvider β€” the lil tool that adds, updates, removes or shows HADR provider sections for SAP HANA ✨


✨ SYNOPSIS ✨

SAPHanaSR-manageProvider [ --help | --version ]
SAPHanaSR-manageProvider [ --sid=SID ] [--reconfigure] --add <template-file>
SAPHanaSR-manageProvider [ --sid=SID ] [--reconfigure] --remove <template-file>
SAPHanaSR-manageProvider [ --sid=SID ] --show --provider=<provider>

🌸 DESCRIPTION 🌸

okay so bestie, SAPHanaSR-manageProvider is literally your little HADR provider section manager 😌 it lets you add (and update), remove and show SAP HANA HADR provider sections. and the serve? you can do it online or offline β€” on the primary and on the secondary, no cap πŸ’…

the provider section name is case sensitive β€” yes really, watch the caps πŸ‘€ usually all lowercase is used for the section name, and the provider hook script names are camelCase. so like, know the difference, iykyk πŸ¦‹

run this script as the <sid>adm user, fr fr. that's the vibe check it needs to pass πŸ™ˆ


πŸŽ€ OPTIONS πŸŽ€

  • --help β€” show help, babes 🫢
  • --version β€” show version 🌟
  • --add <template-file> β€” add the section given in the template file to configuration πŸ’–
  • --remove <template-file> β€” remove the section given in the template file from configuration πŸ—‘οΈ
  • --reconfigure β€” apply the change to running HANA, like 'hdbnsutil -reloadHADRProviders' πŸ”₯
  • --show --provider=<provider> β€” show the section for the given provider from configuration πŸ‘€
  • --sid=<SID> β€” use SAP system ID <SID>. it should be autodetected if there's only one SAP HANA instance installed on the local cluster node πŸ’«

πŸ”₯ RETURN CODES πŸ”₯

  • 0 β€” successful program execution, slay ✨
  • >0 β€” usage, syntax or execution errors 😭

πŸ’… EXAMPLES πŸ’…

πŸ’« show names of all HA/DR provider sections in global.ini

might be useful to see whether sections are named lower/upper/camel-case, bestie πŸ‘€ SID is HA1.

# su - ha1adm -c "cdcoc; grep ^\[ha_dr_provider_ global.ini"

πŸ¦‹ show the global.ini section ha_dr_provider_suschksrv, if available

example SID is HA1, the HADR provider script is susChkSrv.py. see also manual page susChkSrv.py(7).

# su - ha1adm -c "/usr/bin/SAPHanaSR-manageProvider --show --provider=suschksrv"

🌟 add the section and activate the provider hook script susHanaSR.py

example SID is HA1, the HADR provider hook script is susHanaSR.py. see also manual page susHanaSR.py(7).

note: 'hdbnsutil -reloadHADRProviders' loads everything from global.ini 😳
# cat /usr/share/SAPHanaSR/samples/global.ini
# su - ha1adm -c "/usr/bin/SAPHanaSR-manageProvider --add /usr/share/SAPHanaSR/samples/global.ini"
# su - ha1adm -c "hdbnsutil -reloadHADRProviders; echo rc:"
# su - ha1adm -c "cdtrace; grep SAPHanaSR.init nameserver_*.trc"

🧚 change timeout for HADR provider hook script susTkOver.py

example SID is HA1, timeout is changed from 35 to 30. the configuration is changed and applied to the running hook script. see also manual page susTkOver.py(7).

# su - ha1adm
~> /usr/bin/SAPHanaSR-manageProvider --show --provider=sustkover >sustkover.old
~> sed s/sustkover_timeout\ =\ 35/sustkover_timeout\ =\ 30/g <sustkover.old >sustkover.new
~> /usr/bin/SAPHanaSR-manageProvider --add --provider=sustkover sustkover.new
~> hdbnsutil -reloadHADRProviders
~> cdtrace; grep susTkOver.init nameserver_*.trc

πŸ¦‹ FILES πŸ¦‹

  • /usr/bin/SAPHanaSR-manageProvider β€” the program itself πŸ’–
  • /usr/sap/<SID>/SYS/global/hdb/custom/config/global.ini β€” the global.ini configuration on disk. do not edit directly 🚫
  • /usr/sap/<SID>/HDB<INO>/<VIRT_HOST>/trace/ β€” directory with HANA trace files 🌸
  • /usr/share/SAPHanaSR-angi/samples/ β€” directory with samples of HADR provider sections πŸŽ€
  • setParameter.py β€” the SAP python script to interact with global.ini ⭐

πŸ’€ BUGS πŸ’€

okay so heads up: the command hangs if it needs an input file and you do not specify the file 😭 the way that it'll just sit there... not iconic.

in case of any problem, please use your favourite SAP support process to open a request for the component BC-OP-LNX-SUSE. Please report any other feedback and suggestions to feedback@suse.com 🫢


⭐ REQUIREMENTS ⭐

  • Perl 5.18 runtime environment or compatible πŸ’œ

🌈 SEE ALSO 🌈

SAPHanaSR-ScaleOut(7) , SAPHanaSR(7) , susHanaSR.py(7) , susHanaSrMultiTarget.py(7) , susCostOpt.py(7) , susTkOver.py(7) , susChkSrv.py(7) , SAPHanaSR_maintenance_examples(7) , SAPHanaSR-manageAttr(8) , cs_show_hana_info(8) , https://documentation.suse.com/sbp/sap/ , https://documentation.suse.com/sles-sap/ , https://www.susecon.com/doc/2015/sessions/TUT19921.pdf , https://www.susecon.com/archive-2020.html , https://www.susecon.com/archive-2021.html


πŸ‘‘ AUTHORS πŸ‘‘

F.Herschel, L.Pinne. icons only, periodt πŸ’…


(c) 2022-2026 SUSE LLC

SAPHanaSR-manageProvider comes with ABSOLUTELY NO WARRANTY. for details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html πŸ™ˆ


and that's the whole page bestie 🫢 this was SAPHanaSR-manageProvider(8) from SAPHanaSR, dated 24 Jul 2025 β€” go forth and manage those providers, you got this πŸ’–βœ¨

πŸ“¦ where this page comes from