A fix is available
APAR status
Closed as fixed if next.
Error description
When a Tivoli Storage FlashCopy Manager for Unix and Linux (FCM) for DB2, Oracle or SAP Oracle cloning operation fails during the creation of the FCM backup operation then this FCM clone is marked as FAILED in the FCM repository. If the FCM clone could not be mounted on the cloning target system, then FCM fails to delete this clone from the FCM repository using the FCM 'delete_clone' operation. During a FCM delete_clone operation the following is shown in the output: oraor1@utprod2:~/acs> ./fcmcli -f delete_clone -C CL1 -u oracl1 ... FMM6518I No snapshot backup is currently mounted. ... FMM0024I Return code is: 0. But the FCM clone was not deleted and is still in the FCM repository which can be verified with a inquire_delail_clone operation: > ./fcmcli -f inquire_detail_clone -C CL1 Type Backup-ID Bkp-Timestamp TSM Backup-ID State DevClass TargetSet BackgroundCopy BytesToBeFlashCopied #CLONE A0I37JDB4O 20141202182457 - FAILED CLONE 3(CL1) 10.000 GB of 10.000 GB 10.000 GB UsabilityStates: REMOTELY_MOUNTABLE,FULL_COPY,CLONE_DATABASE
Local fix
As a workaround the FCM clone needs to be updated by using the following FCM update_status command: > ./fcmcli -f update_status -S MOUNT=YES -B A0I37JDB4O -d ORCL__ -i OR1 ... FMM6272I Update snapshot backup with ID 'OR1,ORCL__,A0I37JDB4O'. ... FMM0024I Return code is: 0. Note: For Oracle and SAP Oracle the command line options -B <backupID>, -d <database> and -i <instance> must be set correctly: <backupID> as shown in the inquire_detail_clone output, <database> is always set to ORCL__ and <instance> must be set to the value of $ORACLE_SID on the production system. For DB2 the command line options -B <backupID>, -d <database> and -i <instance> must be set correctly: <backupID> as shown in the inquire_detail_clone output, <database> must be set to the database name of the production database and <instance> must be set to the DB2 instance name on the production system. After this update_status operation completes successfully the delete_clone operation can be re-executed and this time it will remove the FCM clone from the FCM repository.
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of Tivoli Storage FlashCopy Manager for Unix and Linux * * v2.2, v3.x and v4.1 performing database clone operation * **************************************************************** * PROBLEM DESCRIPTION: * * See ERROR DESCRIPTION * **************************************************************** * RECOMMENDATION: * * Apply fixing level when it is available or use a work-around * * described in the 'Circumvention' section * **************************************************************** If there will be a next release of the Tivoli Storage FlashCopy Manager for Unix and Linux it will correctly delete incompletely cloned databases from its repository
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
IT05993
Reported component name
FLSHCPY DB2 AGE
Reported component ID
5608AC6DB
Reported release
41A
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-12-09
Closed date
2015-02-12
Last modified date
2015-02-12
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
R41A PSY
UP
R41H PSY
UP
R41L PSY
UP
R41S PSY
UP
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS36V9","label":"Tivoli Storage FlashCopy Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"41A","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
08 January 2022