Database Memory & 4030/4031 (MOSC)

MOSC Banner

ORA-04036 when PGA_AGGREGATE_LIMIT=0

in Database Memory & 4030/4031 (MOSC) 6 commentsAnswered

Hey all,

one of our production database reported ora-04036 last week when some user process was running out of PGA.

Some of our db consultants decided to change PGA_AGGREGATE_LIMIT to zero to avoid this ORA- error. So he entered: ALTER SYSTEM SET PGA_AGGREGATE_LIMIT=0 scope=both;, but it didn't help.Ora-04036 is still being reported.

How is that possible? It should work as pre 12c - without hard limit on PGA consumed. Am I right?

So, next day we changed this parameter to 30G (db host has some unused memory so we wanted to use it). But again, ora-04036 is still reported. So i checked v$pgastat and what i found was confusing - it says that maximum PGA allocated is around 5.7G, that is almost exactly out PGA_AGGREGATE_TARGET (!!) parameter. Quite weird, isn't it?

Tagged:

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center