CPF4204 is the DB2 for i5/OS Query Engine equivalent to the i5/OS
message CPF9999. The only way to know what transpired, is to have
investigated the error(s) that led to the generic failure message being
issued. Having performed actions like recompile\recreate of objects may
enable bypassing the error condition, but does not [assist to] identify
the defect origin. That doing so [appears to] resolves the situation
does not necessarily imply that the issue is related to conversions,
even if that is probable. However it is surely not due to /background/
conversions, because SQL program [associated space] and database [file,
member, alignment, et al] object conversions would [almost exclusively]
transpire on /first touch/ of the objects.
Reporting the problem as a defect might assist to both identify the
origin and resolve the error by effecting a correction being provided in
the form of a PTF [even if only for future instances of similar upgrades
and objects], so others need not perform similar actions in an attempt
to bypass\circumvent the defect. Or, the problem might be found to
already have a preventive PTF available; for conversion issues, such
that future first-touch conversions will not exhibit the same failure.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.