Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Memory & 4030/4031 (MOSC)

Oracle 11g ORA-04031: unable to allocate 32 bytes of shared memory ("shared pool","select order#,col

Jan 13, 2017 11:29AM edited Jan 22, 2017 12:48AM in Database Memory & 4030/4031 (MOSC) 5 commentsAnswered

What could be causing this error?

How do we identify if there is a memory leak? How often is it expected to bounce the DB ?

Can running the Gather Stats on Schema during heavy transaction cause this issue?

Thanks,

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month