This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2143913 - Include symlink link to /opt/rh/SAP/lib64/libstdc++.so.6
Summary: Include symlink link to /opt/rh/SAP/lib64/libstdc++.so.6
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: compat-sap-c++-10
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Patrick Palka
QA Contact: Václav Kadlčík
URL:
Whiteboard:
Depends On: 2189453
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-18 11:02 UTC by Holger Hopp
Modified: 2023-09-22 15:15 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 15:15:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sap-linuxlab community.sap_install issues 263 0 None open sap_netweaver_preconfigure: Add link to libstdc++.so.6 in rpath directory other than /usr/lib64 2022-12-14 10:19:43 UTC
Red Hat Bugzilla 2189453 0 unspecified CLOSED Provide a compat-sap-c++ package without a version string as part of the package name 2023-09-22 15:18:33 UTC
Red Hat Issue Tracker   RHEL-7257 0 None Migrated None 2023-09-22 15:15:33 UTC
Red Hat Issue Tracker RHELPLAN-139903 0 None None None 2022-11-18 11:12:06 UTC

Description Holger Hopp 2022-11-18 11:02:53 UTC 
Description of problem:
Certain newer SAP kernels and tools on RHEL 8 are built with GCC 10. RHEL 8 is GCC 8 compatible, so a compat-sap-c++ library is required to provide compatibility. However, as the SAP kernel and tools are only looking for a file with name libstdc++.so.6 in the run path, these applications are currently not able find the compat-sap-c++ file.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Update the SAP kernel to one of the SAP kernel versions mentioned in SAP note https://launchpad.support.sap.com/#/notes/3119751, e.g. SAP kernel 754 or 788.
2. Start the SAP system and monitor the terminal output and SAP log files.

Actual results:
Messages like the following will be shown:
disp+work: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by disp+work)


Expected results:
The SAP system starts as expected, without such error messages. No further manual action (like for example creating a soft link) is required after installing the compat-sap-c++ package.

Additional info:
We will soon extend the SAP application's run path to also include /opt/rh/SAP/lib64, so the applications will search for file libstdc++.so.6 there as well.
We need this fix for all RHEL 8 versions which are in the standard, eus, or e4s support range (= RHEL 8.1, 8.2, 8.4, 8.6, 7.7) and all future RHEL 8 versions, on all SAP supported architectures (x86_64, ppc64le, and s390x).
We also need this fix in all compat-sap-c++ versions which are and will be available on RHEL 8, currently compat-sap-c++-10, -11, and -12.
Comment 1 Bernd Finger 2022-11-18 11:21:52 UTC 
There is a typo in the description: The correct RHEL versions in which the fix needs to be available are RHEL 8.1, 8.2, 8.4, 8.6, 8.7 (not 7.7).
Note: I had proposed the bug description to Holger, and the typo was introduced by me.
Comment 7 Gomathi Anandan 2023-01-09 13:44:24 UTC 
Reseting current deadline since issue will not be moved to modified today.
Comment 17 Holger Hopp 2023-06-20 14:00:19 UTC 
Some test results and comments for
compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm and
compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm :

From my point of view everything is okay (symlink libstdc++.so.6 is available, also all symlinks compat-sap-c++-*.so).

Some comments regarding upgrades:
Following seems to be possible:
(1) (New) Installation of compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm.
(2) (New) Installation of compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm AND all compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm
(3) Upgrade from installed older compat-sap-c++-12 to compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm AND all compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm

The result (installed files) is the same all 3 cases:
$ ll /opt/rh/SAP/lib64/
total 2296
lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-10.so -> compat-sap-c++-12.1.1.so
lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-11.so -> compat-sap-c++-12.1.1.so
-rwxr-xr-x. 1 root root 2343184 Apr 17 16:31 compat-sap-c++-12.1.1.so
lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-12.so -> compat-sap-c++-12.1.1.so
lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-9.so -> compat-sap-c++-12.1.1.so
lrwxrwxrwx. 1 root root      24 Apr 17 16:31 libstdc++.so.6 -> compat-sap-c++-12.1.1.so
-rw-r--r--. 1 root root    1022 Apr 17 16:31 README12

This is okay.

But upgrade is different.
Simple upgrade to compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm is impossible.
The upgrade requires compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm and all compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm (described in how-to-install-the-compat-sap-c++-test-packages.pdf).
All the versioned RPMs are installed, but do nothing. That seems to be awkwardly, but probably necessary, if (current) SAP HANA Installer requires the versioned package.

I've only tested rpm (-i and -U), no yum or dnf.
On SAP Kernel side this does not matter. The SAP kernel finds the /opt/rh/SAP/lib64/libstdc++.so.6 properly.

ToDo on SAP side:
Adapt SAP note 3119751 (https://launchpad.support.sap.com/#/notes/3119751) when RHEL 8 minor version of feature release is known.
Comment 18 Patrick Palka 2023-06-21 13:35:23 UTC 
(In reply to Holger Hopp from comment #17)
> Some test results and comments for
> compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm and
> compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm :
> 
> From my point of view everything is okay (symlink libstdc++.so.6 is
> available, also all symlinks compat-sap-c++-*.so).
> 
> Some comments regarding upgrades:
> Following seems to be possible:
> (1) (New) Installation of compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm.
> (2) (New) Installation of compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm AND all
> compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm
> (3) Upgrade from installed older compat-sap-c++-12 to
> compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm AND all
> compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm
> 
> The result (installed files) is the same all 3 cases:
> $ ll /opt/rh/SAP/lib64/
> total 2296
> lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-10.so ->
> compat-sap-c++-12.1.1.so
> lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-11.so ->
> compat-sap-c++-12.1.1.so
> -rwxr-xr-x. 1 root root 2343184 Apr 17 16:31 compat-sap-c++-12.1.1.so
> lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-12.so ->
> compat-sap-c++-12.1.1.so
> lrwxrwxrwx. 1 root root      24 Apr 17 16:31 compat-sap-c++-9.so ->
> compat-sap-c++-12.1.1.so
> lrwxrwxrwx. 1 root root      24 Apr 17 16:31 libstdc++.so.6 ->
> compat-sap-c++-12.1.1.so
> -rw-r--r--. 1 root root    1022 Apr 17 16:31 README12
> 
> This is okay.
> 
> But upgrade is different.
> Simple upgrade to compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm is impossible.
> The upgrade requires compat-sap-c++-12.1.1-1.1.el8_8.x86_64.rpm and all
> compat-sap-c++-{9,10,11,12}-12.1.1-1.1.el8_8.x86_64.rpm (described in
> how-to-install-the-compat-sap-c++-test-packages.pdf).
> All the versioned RPMs are installed, but do nothing. That seems to be
> awkwardly, but probably necessary, if (current) SAP HANA Installer requires
> the versioned package.

If I understand correctly, the unversioned compat-sap-c++ doesn't have any dependencies of its own. But if any older compat-sap-c++-{9,10,11,12} packages are installed on the system, then those will need to get upgraded when installing the unversioned compat-sap-c++, and this ought to happen automatically when using yum/dnf and the official package repository. Upgrading from an older compat-sap-c++-12 to the unversioned compat-sap-c++ won't require installing new versions of compat-sap-c++-{9,10,11}.

> 
> I've only tested rpm (-i and -U), no yum or dnf.
> On SAP Kernel side this does not matter. The SAP kernel finds the
> /opt/rh/SAP/lib64/libstdc++.so.6 properly.
> 
> ToDo on SAP side:
> Adapt SAP note 3119751 (https://launchpad.support.sap.com/#/notes/3119751)
> when RHEL 8 minor version of feature release is known.
Comment 27 RHEL Program Management 2023-09-22 15:14:37 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 28 RHEL Program Management 2023-09-22 15:15:38 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.