RE: Constant corruption in DB2-UDB on the i5.

Objects get damaged.  Any number of things can cause a damaged object, but
typically they are do to system faults of some type or other, usually
hardware related.  Software-related corruption is an unusual and highly
critical problem.

I did notice that you have two PMRs.  One looked to be a corrupt LDAP
implementation, while the other is a Management Central issue.  I don't see
either one telling you "that's what backups are for", although the fact that
the MGTC PMR is still open is certainly a cause for concern.  I'm currently
trying to find out who is responsible for this area.

I have to note that I don't see any PMR for the application files.  Are the
application files getting corrupted regularly as well?  If so, you should
definitely open a separate PMR on those.

Joe

> From: rob@xxxxxxxxx
> 
> I'm sure that IBM did not create message id CPF3285 just for little ol'
> me.
> 
> PMR 06414,500
> He had me unconfigure and reconfigure LDAP.  Since we really weren't using
> it.
> 
> I had another PMR opened in Feb 05 regarding DB corruption for management
> central pmr 79884,500.  That got closed and reopened as 38427,500.  Still
> open.
> 
> Happens so often for Management Central files that I do a save of those
> libraries into a save file in qtemp prior to a full system save to delete
> the offending files prior to it hanging up the full system save.  Written
> up instructions that whoever performs the full system save does the qtemp
> save prior.
> 
> Nasty thing is that we run a RCLSTG immediately prior to the full system
> save and it does nothing with these corrupted files.