Over last evening, one of my colleagues had begun recreating a materialized view. From looking at his code, it was only
doingsome selects, like one would expect, however, several API clients ended up being blocked by this, and I’m
attemptingto understand why. I should note that a couple of the tables used here, contained more than 100 million rows,
andI’m wondering if the system simply gave up trying to keep the view’s data consistency on par, and if a more than a
non-exclusiveread block was then imposed. The API’s involved basically kept getting respawned, and at one point there
weremore than 4000 attempted simultaneous connections. Not a lot of fun, but fortunately for me, the application team
onlycalled the other DBA to fix the issue. I’d still like to know what happened.
—
Jay
Sent from my iPad
