Jeffrey Butera wrote on 01/20/2006 10:00:01 AM: > Thanks to all for ideas. I finally copied the DICT from another account, > overwriting that in production and the issue went away. So, can anyone shed > light on how to properly check a dictionary for file corruption? We checked > ours and no errors were reported.
Did you happen to save the old dict file before copying in the new one? I would think about running a program to check each item in the two copies - particularly the "D" types, since you hit your problem when using ALL. I wonder if there may have been some weird character embedded somewhere. You said you checked for file corruption in the dictionary file - does this mean you ran guide on it? If not, I would suggest doing so. It may also be interesting to run CD against the troublemaker. It may uncover something interesting. Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group 717-545-6403 [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
