Troubleshooting
Problem
db2 Warehouse on CP4D cannot been started up.
Symptom
Db2 Warehouse on CP4D cannot been started up and oc logs saw following error "no space left on device"
{"level":"error","component":"server","subComponent":"GetDb2Health","caller":"[11]:db2.go:262:GetDb2Health()","timestamp":"2024-01-31T08:58:42Z","message":"2 MLNs found in MLN dist file, but only 0 db2sysc processes match"}
zerolog: could not write event: write /mnt/blumeta0/support/c-db2wh-1704348179110570-db2u-0-db2u-api.log: **no space left on device**
{"level":"error","component":"server","subComponent":"GetDb2Health","caller":"[11]:db2.go:262:GetDb2Health()","timestamp":"2024-01-31T08:59:12Z","message":"2 MLNs found in MLN dist file, but only 0 db2sysc processes match"}
zerolog: could not write event: write /mnt/blumeta0/support/c-db2wh-1704348179110570-db2u-0-db2u-api.log: no space left on device
{"level":"error","component":"server","subComponent":"GetDb2Health","caller":"[11]:db2.go:262:GetDb2Health()","timestamp":"2024-01-31T08:59:42Z","message":"2 MLNs found in MLN dist file, but only 0 db2sysc processes match"}
zerolog: could not write event: write /mnt/blumeta0/support/c-db2wh-1704348179110570-db2u-0-
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"ARM Category":[{"code":"a8m3p000000hB51AAE","label":"Warehouse"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
01 May 2025
UID
ibm17120570