|
Problem IT01606
|
Status: Closed |
TEST FOR FREE SPACE>LOG SPACE WILL FAIL DUE TO ALREADY ALLOCATED LOG PRIMARY SPACE IS NOT TAKEN INTO ACCOUNT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
After increasing LOGPRIMARY parameter, DB2 may return a message
SQL1762N, Unable to connect to database
because there is not enough space to allocate active log files,
even though enough space is available.
In the db2diag.log we will see messages similar to this:
2014-04-15-14.41.08.326452-420 I46210555A834 LEVEL: Error
PID : 4718608 TID : 4114 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : TEST
APPHDL : 0-7 APPID: *LOCAL.inst1.140415214105
AUTHID : DB2INST1 HOSTNAME: db2.storage
EDUID : 4114 EDUNAME: db2agent (TESTDB1) 0
FUNCTION: DB2 UDB, data protection services, sqlpgReallocLogs,
probe:970
MESSAGE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG
"Not enough space to create primary logs"
DATA #1 : String, 59 bytes
Log path / Free space (bytes) / Log space required (bytes):
DATA #2 : String, 39 bytes
/LOGSTREAM0000/
DATA #3 : unsigned integer, 8 bytes
283772977152
DATA #4 : unsigned integer, 8 bytes
549757911040
Currently allocated log space is not being factored into the
equation for free space versus log space, though it will be
freed and reallocated to equal enough space. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fixpack 4 or higher. *
**************************************************************** |
| Local Fix: |
Reduce LOGPRIMARY to a minimum value so that only a small amount
of log space is required. Disconnect from the db and reconnect.
This will free the previous allocations. Now the LOGPRIMARY
parameter can be increased to the desired value. Reconnect to
the db and new parameters will be in effect. Numbers will need
to be adjusted to fit with current available space. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Version 10.5 Fixpack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.05.2014
26.01.2015
26.01.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
