search

SUSE / suse-best-practices

SUSE Best Practices documentation series
43 stars 74 forks source link

[doc] Example 12: Adding SAPHanaSR via global.ini #95

Closed roseswe closed 1 year ago

roseswe commented 4 years ago

Example 12: Adding SAPHanaSR via global.ini :

https://documentation.suse.com/sbp/all/single-html/SLES4SAP-hana-sr-guide-PerfOpt-12/#id-1.9.6.6

On one node only or on all nodes? We should document this more in detail

chabowski commented 4 years ago

@fmherschel @lpinne @pirat013 Ralph Roth has submitted several issues/questions (via the "report a bug" link in the doc which opens a GitHub issue). Can you please have a look? This is his second question/issue. Thanks very much!

fmherschel commented 4 years ago

The global.ini is Global to an entire SAP HANA database (once) per site. As typically the global.ini is installed on NFS for Scale-Out it needs (of course) only to be changed once per site. This should be clear for SAP architects and is more a SAP specific question. For scale-Up it needs to be done on both sides. We already explained that:

This step must be done on both sites.

roseswe commented 4 years ago

As said I mirror only customer experience here

fmherschel commented 4 years ago

And left is at the left side ;-)

lpinne commented 4 years ago

@roseswe: Thanks for the hint. Even if global.ini should be known to SAP admins, I agree the mentioned example is a little unclear. We might add somthing like:

On both nodes add HADR provider hook script SAPHanaSR to HANA's global.ini. Do not copy the global.ini file between nodes. Before editing global.ini, stop the HANA on both nodes. See manual page SAPHanaSR.py(7) for details.

lpinne commented 1 year ago

the guide now highlights a procedure which says three time "Implement the python hook script ... on both sites."

thanks for reporting!