DB2 - Problem description
Problem IT33312 | Status: Closed |
DB2ICRT AND DB2PREQCHECK FREE SPACE AND HOST FAILURE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
This APAR resolves two problems when running db2icrt which calls db2prereqcheck uner the covers, or calling db2preqcheck directly: A) Insufficient disk space when there is actually plenty of disk space Validating "free space" ... DBT3571E The db2prereqcheck utility found that the directory "/tmp" does not have enough free space on host "test.ibm.com". Required space: "2000000 KB". Actual space present: "3731957960 KB". ERROR : Requirement not matched. Validating "free space" ... DBT3571E The db2prereqcheck utility found that the directory "/var" does not have enough free space on host "test.ibm.com". Required space: "2000000 KB". Actual space present: "3731957960 KB". ERROR : Requirement not matched. Validating "free space" ... DBT3571E The db2prereqcheck utility found that the directory "/usr" does not have enough free space on host "test.ibm.com". Required space: "512000 KB". Actual space present: "3731957960 KB". ERROR : Requirement not matched. B) Problem validating host name 2020-01-01-12:00:07 3828668160 -DATA- 30 db2iInterHostComVerifySSH_Tmp::getRemoteFolderFreeSpace - , STRING = 3731906992 2020-01-01-12:00:07 3828668160 -DATA- 40 db2iInterHostComVerifySSH_Tmp::getRemoteFolderFreeSpace - , INT = -563060304 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.5.0 or higher * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
See LOCAL FIX | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.06.2020 20.11.2020 20.11.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |