|
Problem IC74394
|
Status: Closed |
CHANGE REASON CODE/ERROR TEXT FOR SQL2581N IF LOGS ARE DETECTED IN DEFAULT LOG PATH |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If you run a snapshot restore without the "INCLUDE LOGS" clause
this might fail with error "SQL2581 rc=3", if DB2 detects old
log files residing in the default log directory. The current
error text for SQL2581 rc=3 is:
Error Text:
3 A log file name in the backup image matches a log file
which already exists in the log target path.
User response:
3 Check that there are no existing log files in the log
target path with the same name as log files in the backup
image being restored. Resubmit the command.
The error text for SQL2581 reason code 3 is currently confusing
and does not describe the real cause for this error message.
With this APAR we will change the reason code and provide a
better description of the situation as why this error occured. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 5. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 9.7 Fix Pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.02.2011
16.12.2011
16.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
