Re: dsmserv restore db problem with 3494 libr
2002-02-19 07:54:51
a further APAR to the problem:
APAR Identifier ...... IC31865 Last Changed ........ 01/11/09
UNABLE TO USE 3494 LIBRARY FOR RESTORE DB. HAVE TO DEFINE DRIVE
WITHIN 3494 AS TYPE MANUAL TO COMPLETE DB RESTORE.
Symptom ...... IN INCORROUT Status ........... CLOSED PER
Severity ................... 3 Date Closed ......... 01/11/09
Component .......... 5698TSMAX Duplicate of ........
Reported Release ......... 410 Fixed Release ............ 999
Component Name TSM AIX SERVER Special Notice
Current Target Date .. Flags
SCP ................... AIXRSC
Platform ............ AIX
Status Detail: Not Available
PE PTF List:
PTF List:
Release 410 : PTF not available yet
Release 420 : PTF not available yet
Parent APAR:
Child APAR list: IC32146 IC32147 IC32148 IC32149
ERROR DESCRIPTION:
A 3494 library cannot be used when performing a TSM server
restore db. To complete a db restore using a drive in a 3494
you have to define the library as type manual and a drive within
the 3494 as belonging to this manual library. The db restore
tape(s) then has to be loaded into the drive manually (or via
mtlib). This restriction needs to be removed. TSM servers should
be able to use the full library function of a 3494 for db
restores.
Initial Impact: Medium
LOCAL FIX:
Define the library as type manual.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: Users whose database backup volumes are *
* in a 3494 library *
****************************************************************
* PROBLEM DESCRIPTION: The 3494 cannot be used with the *
* RESTORE DB command, but the volumes *
* can be loaded by changing the devconfig *
* file to use a "manual" library, with *
* the backup vols in that library. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem is a bug in the code that references the very
database that is being restored by RESTORE DB.
PROBLEM CONCLUSION:
The bug is removed.
|
|
|