Has anyone heard of a table going into reorg pending state without a schema
change being made? Possibly related to automatic maintenance?

On 7 mei, 02:51, "Mark A" <no... (AT) nowhere (DOT) com> wrote:
Never encountered, but that sure would ... ahem... be a rather
unpleasant experience,
so I hope you find out the cause.

--
Frederik Engelen

"Frederik Engelen" <engelenfrederik (AT) gmail (DOT) com> wrote

This is not my system, so I don't know all the facts pertaining to this
incident. The person who asked me about it claimed that no schema changes
were done, and implied it has happened more than once.

On another DB2 forum, a reliable poster (who happens to live in Toronto)
"suggested" that this (table goes into reorg pending state without schema
changes having been done) could occur on a database with automatic
maintenance, and this database does have automatic maintenance set on as
default (everything is defaulted for the 9.7 databases they created). Also,
they are unfortunately still running 9.7.0 (but could not find any APAR's
dealing with this issue).

On May 7, 3:26*pm, "Mark A" <no... (AT) nowhere (DOT) com> wrote:
Possiblities?

Column-length ALTER or Column-DOMAIN ALTER (CHAR to VARCHAR..)?
Health-Monitor? (another excellent reason to disable this "feature"!)
LARGE-RID Enable?