|
Problem IT03947
|
Status: Closed |
CONNECTION ATTEMPT FAILS WITH SQL5099N WHEN THE MIRRORLOGPATH IS INVALID |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Connection attempt fails with SQL5099N when the mirrorlogpath is
invalid even though the active logpath is valid. In the
following scenario the first connection attempt works but the
second one fails with SQL5099N.
mkdir /tmp/mirror
db2 update db cfg for sample using MIRRORLOGPATH /tmp/mirror
db2 activate db sample
db2 deactivate db sample
chmod 0 /tmp/mirror/NODE0000/LOGSTREAM0000
db2 connect to sample
db2 terminate
db2 connect to sample |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to the latest fix pack. *
**************************************************************** |
| Local Fix: |
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.5 fix pack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.08.2014
16.12.2014
16.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
