From: talkabout66 on
I saw the same error. This ended up being an issue with DB2. Our DBA
bounced DB2 and the problem went away. Hope that helps someone.

--
Message posted using http://www.talkaboutdatabases.com/group/comp.databases.ibm-db2/
More information at http://www.talkaboutdatabases.com/faq.html