It's been too long, I remember when we first hit it after DB/2 upgrade to V5 or something. Think the answer was it's 'an integrity issue'. For long time until we could get more 'power' in place we just QUIESCED the most active DB's without restarting DB/2. In a message dated 5/16/2013 6:34:32 A.M. Central Daylight Time, rel...@us.ibm.com writes:
I do not know DB2's position or plan in this area. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
