IT39144: CANCELING OF DB2 BACKUP MIGHT CAUSE ORPHANED SNAPSHOTS LEFT ON THE APPLICATION SERVER

APAR status

• Closed as program error.

Error description

• If a user cancels a backup of Db2 database it might sometimes
  
  cause orphaned snapshots left on the Db2 application server.
  
  The issue depends on the time when the cancel request
  
  was generated in combination with a large database files size.
  
  Large file size means that the time required to copy it is more
  
  
  than 30 minutes. The orphaned snapshot can become inactive
  
  with time. As a result, any LVM command on the application
  
  host can show the error "Input/output error".
  
  
  For example:
  [root@sample-db etc]# lvs
  /dev/vg00/snap-tblspcs-db2pjr-202108302-1: read failed after 0
  of 4096 at 0: Input/output error
  /dev/vg00/snap-tblspcs-db2pjr-202108302-1: read failed after 0
  of 4096 at xx: Input/output error
  
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.2, 10.1.3, 10.1.4, 10.1.5,
  10.1.6, 10.1.7, 10.1.8
  
  Additional Keywords: SPPLUS, TS006504955 , DB2, Orphaned
  
  Snapshots, Input/output error
  
  Additional Keywords: SPPLUS, TS005531637, Oracle database. Timed
  

Local fix

• Identify orphaned snapshots and remove them manually.
  To identify all snapshots that are left after canceling
  
  a backup use the next commands:
  #Linux
  'lvs' or 'lvdisplay'
  Search for logical volumes with names starting from 'snap-'
  #AIX
  snapshot -q <snappedFS>
  
  In the normal case, when there are no orphaned snapshots
  
  on the system, the command should print out something like
  [root@sample-db etc]# snapshot -q /db2/SPP/db2spp/NODE0000
  /db2/SPP/db2spp/NODE0000 has no snapshots.
  
  When there is a snapshot for the specified source file system
  
  then the same command prints out something like:
  Current  Location          512-blocks        Free Time
   
   *        /dev/fslv00           786432      785664 Mon Nov 15
  13:55:08 2021
    
  To manually remove an orphaned snapshot use the next command:
  #Linux
  lvremove -f <snapshot_name> 
  #AIX
  snapshot -d <snapshotLV>
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.2, 10.1.3, 10.1.4,     *
  * 10.1.5, 10.1.6, 10.1.7, 10.1.8 and 10.1.9 protecting Db2 or  *
  * MongoDB                                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in the 10.1.9.3 and 10.1.10. Note that *
  * this information is subject to change at the discretion of   *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The IBM Spectrum Protect Plus Db2 and MongoDB agents have been
  fixed to correctly process cancel request and do not leave
  orphaned snapshots.
  

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:

Modules/Macros

• Apps     Db2      MongoDB
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels