Encounter Library cache load Lock wait event

Encounter Library cache Load Lock wait event:

In troubleshooting Library Cache:lock, Pin and Load Lock (Doc ID 444560.1) This article explains the wait event in detail:

If an object was not in memory and then a library cache lock cannot was acquired on it. The object has been loaded into the memory to acquire the lock. The session tries to find the load lock for the database object so the it can load the object. In order to prevent multiple processes requesting the load of the same object simultaneously, the other requesting session S has to wait for the library cache load lock as the lock is busy with loading the object into the memory. The waits on the library cache load lock are due to the objects not being available in memory. The unavailability of the library cache object in the library cache was due to the undersized shared pool causing frequent Reloads or too many hard parse as a result of unshared Sqls.

There are several ways to avoid this wait event:

And then summed up a bit:

The library cache load Lock Wait event occurs on this db because the size of the shared_pool_size is reduced. It seems that seemingly simple operations can cause a lot of problems. And then I found time to increase the shared_pool_size.

The DBA's every move on the production bank can cause problems. Careful!

Encounter Library cache load Lock wait event