The issue is resolved now and the cause for this is the internal schemas were anayzed during the upgrade process and unfortunately there was a scheduled job to analyse the whole DB which cause corruption in some internal schema statistics. Now the problem is fixed by scheduling the job to gather only user schemas. Reg, Ann On 4/19/08, ~Jeff~ <jifjif@xxxxxxxxx> wrote: > > either of the top 2 posts here might have something to do with it: > http://blogs.sun.com/glennf/ > > - Jeff Wong > EDS NZ. >