IT47539: SAP HANA BACKUP TIMEOUT ISSUE TO CREATE SNAPSHOT - CTGGS0219, ERROR: RUNTIMEERROR(AGENT_HANA)

APAR status

• Closed as change to accomodate OEM Vendor's code.

Error description

• When running a backup job for SAP HANA instances a timeout
  
  error can cause issue to commit the HANA snapshot on client
  
  side.
  
  The IBM Storage Protect Plus job log shows the below
  error sequence:
  WARN, CTGGS0218, SAP HANA hdbsql client command failed
  WARN, Process timeout exceeded (PID: xxxx)
  ERROR, CTGGS0219, An error was encountered while creating
  
                                          a SAP HANA snapshot
  backup.
  
                                          Error:
  RuntimeError(agent_hana
  .
  While the agent command log shows the following messages:
  INFO pid:xxxx MainThread run: Running command 'sudo -n -u pkradm
  
                                -i /tmp/<filename>...'
  DEBUG pid:xxxx MainThread run: Trying to read stdout/stderr
  
                                 buffers and wait 0.1 seconds
  ...
  DEBUG pid:xxxx MainThread run: Trying to read stdout/stderr
  
                                 buffers and wait 30.0 seconds
  ERROR pid:xxxx MainThread log_chained_exception:
  
                            Process timeout exceeded (PID: yyyy)
  ...
  ERROR pid:xxxx MainThread log_chained_exception: agent_hana|
               create_snapshot_exception|
               RuntimeError(agent_hana|commit_snapshot_exception|
               RuntimeWarning(agent_hana|hdbclient_hdbsql_failed))
  
  
  
  IBM Storage Protect Plus Versions Affected:
  IBM Storage Protect Plus 10.1.x
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Storage Protect Plus users 10.1.x                        *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to SPP version 10.1.17[later versions].              *
  ****************************************************************
  

Problem conclusion

• This issue seen in customer environment in only one setup where
  it is observed that the saphana data is very big which is around
  500GB,
  while taking the snapshot it took more time than expected and
  causes the SAPHANA database auto trigger the snapshot
  termination which
  causes the backup failure, where SAPHANA source code is modified
  to be considered to take snapshot in all scenarios.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels