Known issues

This page describes known issues that you might run into while using SAP on Google Cloud. The page includes only those issues that have come to the attention of the SAP specialists on the Cloud Customer Care team.

Other issues that can impact SAP systems might be listed in the documentation for other Google Cloud products and services. For example, issues that are related to Compute Engine VMs, persistent disks, or OS images, are listed on the Compute Engine known issues page.

StorageException for Cloud Storage can cause corrupted Backint agent backup

Under certain conditions, if a StorageException occurs when the Cloud Storage Backint agent for SAP HANA stores a backup in Cloud Storage, the Backint agent might append duplicate data to the backup file, which makes the backup file unusable for recovery.

If you try to recover the database from a backup file with duplicated data, you receive the following error:

  exception 3020043: Wrong checksum

Users affected

SAP HANA users that use the Cloud Storage Backint agent for SAP HANA to store backups in Cloud Storage.

Resolution

To resolve this issue, first install version 1.0.13 or later of the Backint agent and then check the Backint agent logs for any StorageException errors to see if you have been affected by this issue.

For instructions for upgrading the Backint agent, see Updating the Backint agent to a new version

To see if you have been affected by this issue, check the Backint agent logs:

  1. As sidadm user on the SAP HANA host, search the logs for the StorageException message:

    grep 'com.google.cloud.storage.StorageException' \
     /usr/sap/$SAPSYSTEMNAME/SYS/global/hdb/opt/backint/backint-gcs/logs/*.log.*
    
  2. If you find the error message, verify the status of the associated backup:

    $ hdbbackupcheck -e <var>EBID</var> --backintParamFile /usr/sap/$SAPSYSTEMNAME/SYS/global/hdb/opt/backint/backint-gcs/parameters.txt /usr/sap/$SAPSYSTEMNAME/SYS/global/hdb/backint/DB_$SAPSYSTEMNAME/<var>BACKUP_FILE_NAME</var>
    

    In the example, replace the following placeholder values:

    • EBID with the external backup ID of the backup.
    • BACKUP_FILE_NAME with the file name of the backup file.

    If you receive a checksum error, contact Cloud Customer Care.

In addition to the preceding check, to detect this and other issues before your backups are needed, make the following actions a regular part of your backup process:

  • As per SAP recommended best practices, execute the SAP hdbbackupcheck tool regularly against backups to verify logical consistency. For more information, see SAP Note 1869119.
  • Test your disaster recovery procedures regularly.

SAP HANA scale-out deployment fails due to a Python error

If you are installing SAP HANA 2.0 SPS 5 Revision 56 or later for an SAP HANA scale-out system with host auto-failover, the SAP HANA scale-out with host auto-failover deployment fails due to a Python error in the storage manager for SAP HANA. The SAP HANA trace log files show the following Python error for this failure: failed with python error: _sap_hana_forbid() got an unexpected keyword argument 'stdout'.

Resolution

Use version 2.2 or later of the storage manager for SAP HANA. Version 2.2 adds support for SAP HANA 2.0 SPS 5 Revision 56 and later. For more information about the storage manager for SAP HANA, see SAP HANA host auto-failover on Google Cloud.

High-availability cluster failover issue due to a Corosync communication delay

For your high-availability (HA) cluster for SAP HANA on Google Cloud, failover can be incorrectly triggered due to a temporary delay in the transmission of Corosync messages between the cluster nodes.

This issue occurs on both SUSE and Red Hat high-availability Linux distributions.

This issue is not specific to Google Cloud, but is described here because it has impacted SAP on Google Cloud users.

Resolution

The resolution of the issue is different depending on your operating system.

SUSE

SUSE provided a Corosync maintenance update that solves the problem. To apply the fix, update your Corosync software to one of the versions that are listed in the following table.

SUSE version Corosync version
SLES 12 all SPs corosync-2.3.6-9.19.1
SLES 15 corosync-2.4.5-5.13.1
SLES 15 SP1 corosync-2.4.5-9.16.1
SLES 15 SP2 corosync-2.4.5-10.14.6.1
SLES 15 SP3 corosync-2.4.5-12.3.1

Red Hat

Red Hat provided a Corosync maintenance update that solves the problem. To apply the fix, update your Corosync software to one of the versions that are listed in the following table.

Red Hat version Corosync version
RHEL 7 corosync-2.4.5-7.el7_9.2
RHEL 8 A patch has been submitted to resolve this issue and is under review for inclusion in the next minor release of RHEL 8.