DB2 - Problem description
Problem IT19687 | Status: Closed |
DB2 upgrade may hit error SQL1762N even though there is sufficient disk space for upgrade | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
DB2 upgrade may hit error SQL1762N even though there is sufficient disk space for upgrade. Here is the specific error message: $ db2 upgrade database MYDB SQL1762N Unable to connect to database because there is not enough space to allocate active log files. SQLSTATE=08004 The diaglog will show the following: 2017-03-01-16.13.45.142221-420 I70744A944 LEVEL: Error PID : 17367116 TID : 4628 PROC : db2sysc 0 INSTANCE: tsminst1 NODE : 000 DB : MYDB APPHDL : 0-7 APPID: MYAPPID AUTHID : MYAUTH HOSTNAME: MYHOSTNAME EDUID : 4628 EDUNAME: db2agent (TSMDB1) 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, 37 bytes Log path / Re-Usable space (bytes) / DATA #2 : String, 48 bytes Free space (bytes) / Log space required (bytes): DATA #3 : String, 49 bytes /tsm/server/aLog1/IVTalog/NODE0000/LOGSTREAM0000/ DATA #4 : unsigned integer, 8 bytes 537927680 DATA #5 : unsigned integer, 8 bytes 11259609088 DATA #6 : unsigned integer, 8 bytes . | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Fix Pack 1 * **************************************************************** | |
Local Fix: | |
Add more disk space | |
available fix packs: | |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 11.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.03.2017 09.05.2017 09.05.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |