K
Keith Sudbury
Guest
We have similar issues. I also consider this a bug/design issue that needs to be fixed. There is really no logical reason why changing SQL permissions for a user should block other users from accessing the database... or invalidate the schema cache. A few things I have found to help out (but not solve) the issue... 1) Only one commit for the entire script (not one per grant) to reduce the number of schema locks required. 2) Use the -schlockwq DB startup param to reduce some of the impact of schema locks.
Continue reading...
Continue reading...