Loading...

Troubleshooting - SAP HANA Data Agent

Table of Contents

SAPHANA0001: BACKINT Hangs in a Cross-Machine Restore

SAPHANA0002: SAP HANA Restore from a Selective Copy Fails

SAPHANA0003: Hung Streams Cause Job Progress to Run Forever

SAPHANA0004: A Delay in Acquiring Commvault Resources Can Cause the Backup Job to Fail

SAPHANA0005: A SAP HANA Tenant Database Cross-machine Restore Has a JPR of Pending

SAPHANA0006: A SYSTEMDB Database Restore Fails When You Specify a Tenant Database Backup Prefix

SAPHANA0007: A SAP HANA Multinode to Multinode Database Copy Fails

SAPHANA0008: A Multitenant Backup That Uses a Third-Party Tool Fails

SAPHANA0009: A Backup Fails if The Instance is Not Instance0001

SAPHANA0010: A SAP HANA SYSTEMDB Restore Immediately Followed by a Tenant Database Restore Displays as Job Pending

Verifying the automatic update of the global.ini file and SAP HANA parameter file?

SAPHANA0001: BACKINT Hangs in a Cross-Machine Restore

Issue

The job progress runs forever because a few streams are hung.

Solution

Update the SAP HANA database to one of the following versions:

  • If you have a SPS11 SAP HANA configuration, then update the version to SPS11 2.6 or higher
  • If you have a SPS12 SAP HANA configuration, then update the version to SPS112 2.02 or higher

Upgrade the SAP HANA database to SPS112.6 or SPS122.02.

SAPHANA0002: SAP HANA Restore from a Selective Copy Fails

Issue

If you restore from a selective copy, the restore may fail because the software cannot find the catalog. You may get an error similar to the following:

Error Code: [18:146] Description: SAP HANA Error [One or more files could not be located on the media]. Source: hana02, Process: backint_hana

Solution:

Set the CV_restCopyPrec configuration file parameter to 0 and then perform the restore.

SAPHANA0003: Hung Streams Cause Job Progress to Run Forever

Issue

SAP HANA log backups take extra time to complete

The reason for the delay is that the SAP HANA connection may timeout when there is no data sent in a specified time.

Solution:

The Commvault software may not have enough resources. Increase the number of available streams on the log subclient storage policy. For more information, see Specifying the Device Streams.

SAPHANA0004: A Delay in Acquiring Commvault Resources Can Cause the Backup Job to Fail

Issue

The backup job fails when it takes longer than 10 minutes to acquire Commvault resources.

Resolution

The backint_response_timeout parameter specifies how long SAP HANA can wait for a log backup when hdbbackint is invoked.

The default is 10 minutes (600 seconds). When there is no log backup in that time period, SAP HANA kills the hdbbackint process and the job fails.

In environments where it takes longer than 10 minutes to acquire the Commvault resources, we recommend that you increase this value.

For scale environments, we recommend that you increase this value to 1800 seconds so that backint waits for a longer time to acquire the resources and that SAP HANA does not kill the process.

SAPHANA0005: A SAP HANA Tenant Database Cross-machine Restore Has a JPR of Pending

Issue

A tenant database restore shows a status of pending, and has an error that is similar to the following error:

Error Code: [18:146] Description: SAP HANA Error [2017-02-28T07:59:55-05:00 P003115 15a84cd9aa8 ERROR RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume 1, reached log position 0, [110058] The existing log area is not compatible to the log and data backups ]. Source: hana07, Process: ClHanaAgent

Resolution

Start a new restore job and make sure that you select the Initialize Logs check box (Restore Options dialog box, General tab).

SAPHANA0006: A SYSTEMDB Database Restore Fails When You Specify a Tenant Database Backup Prefix

Issue

If you specify a tenant database backup prefix when you perform a SYSTEMDB database restore that uses the recover only option, the restore job fails.

If you specify a SYSTEMDB database backup prefix when you perform a tenant database restore that uses the recover only option, the restore job fails.

Resolution

To restore a SYSTEMDB database, retry the restore operation and use the SYSTEMDB database backup prefix.

To restore a tenant database, retry the restore operation and use the tenant database backup prefix.

SAPHANA0007: A SAP HANA Multinode to Multinode Database Copy Fails

Issue

The srcCrossClient and srcCrossDbName parameters are not set on all nodes and the restore fails.

Resolution

Make sure to set the parameters on all nodes. For information on the Database Copy prerequisites, see the Before You Begin section of Performing a SAP HANA Database Copy.

SAPHANA0008: A Multitenant Backup That Uses a Third-Party Tool Fails

Issue

A multitenant backup that uses a third-party tool fails with the following error:

Error received as: "* 447: backup could not be completed: [110505] Backint fork failed, $sysmsg$ ($sysrc$). Invalid PID SQLSTATE: HY000"

Resolution

For more information, see SAP Note 2386226.

Shut down the entire SAP HANA instance, including the hdbdaemon, and then restart the instance.

Perform the following commands as the <SIDadm> user.

  • HDB stop
  • HDB Start

SAPHANA0009: A Backup Fails if The Instance is Not Instance0001

Issue

SAP HANA backups that use an instance other than Instance0001 go to a pending state. The following JPR is displayed:

JPR:
Error Code: [18:146]
Description: SAP HANA Error [hdbsql execution Failed. * 447: backup could not be completed: [110503] Backint cannot execute /usr/sap/NFS/SYS/global/hdb/opt/hdbbackint, No such file or directory (2) SQLSTATE: HY000].
Source: hana04_3, Process: ClHanaAgent error is displayed:

Resolution

You must manually link to hdbbackint.

SAPHANA0010: A SAP HANA SYSTEMDB Restore Immediately Followed by a Tenant Database Restore Displays as Job Pending

Issue

This issue applies to SAP HANA 1.0 or a SAP HANA 2.0 Multitenant Database Container configurations.

If you restore a SYSTEMDB database, and then immediately restore a tenant database, then the job controller displays the results for the tenant database restore as job pending even though the database recovered and is in the UP state.

Resolution

Use the job controller to resume the job.

Verifying the automatic update of the global.ini file and SAP HANA parameter file?

The Commvault software automatically updates the global.ini file and the SAP HANA parameter file (for example: /opt/commvault/iDataAgent/param) when you perform your first SAP HANA backup.

The Commvault software sets the following parameters in the global.ini file for the SYSTEMDB and tenant databases:

  • The SAP HANA data backup parameter file location (data_backup_parameter_file)
  • The SAP HANA log backup parameter file location (log_backup_parameter_file)
  • The parameter that allows SAP HANA to use Commvault for log backups (log_backup_using_backint=true)

The software also performs the following configuration:

  • Creates a link that points to a parameter file created by Commvault called param under the SAP directory, for example, /usr/sap/FH2/SYS/global/hdb/opt/hdbconfig/param.
  • Creates a link that points to the Commvault backint binary with SAP HANA hdbbackint, for example /usr/sap/FH2/SYS/global/hdb/opt/hdbbackint.

Examples

Last modified: 12/4/2017 1:55:11 PM