|
Problem IC80041
|
Status: Closed |
RESTORE DATABASE OVER TOP OF AN EXISTING DATABASE WITH THE SAME NAME WHEN STORAGE PATH IS REMOVED SUCCEEDS UNEXPECTEDLY |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
For DB2 users on Windows, performing a database restore over top
of an existing database with the same name, after a database
storage path has been removed, will succeed when an error should
be returned instead. This is due to a defect within the DB2
code.
Consider the following database backup and restore scenario:
- db2start
- db2 create db <dbname> on <path1>
- db2 update db cfg for <dbname> using logretain on
- db2 backup db <dbname>
- db2 connect to <dbname>
- db2 alter database <dbname> add storage on '<path2>'
- db2 connect reset
- db2 terminate
- remove <path2>
- db2 restore db <dbname> without rolling forward without
prompting
In the above scenario, because of the code defect, the restore
command will return with the following,
"SQL2540W Restore is successful, however a warning "2539" was
encountered
during Database Restore while processing in No Interrupt mode."
instead of the expected result, which is the following error,
"SQL1051N The path "<path2>" does not exist. SQLSTATE=57019" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Users on Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* See "Error Description." *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.5 Fix Pack 9. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem was first fixed in Version 9.5 Fix Pack 9. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2011
12.03.2012
12.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
