Re: waited too long for row cache enqueue lock

There are a number of bugs (especially at 7.1.4) that could be causing
this to happen. It isn't necessarily any tuning parameter.

For example, if you try to create a unique index on a table in one session
and simultaneously analyze the table from another table you can get a deadlock of this type irrespective of the resources available.

However, you might try increasing the library cache (by increasing the
shared pool) since some of the problems are caused by over active systems with library cache and row cache flushing occurring too rapidly. Received on Thu Apr 23 1998 - 11:58:21 CDT