Database Administration (MOSC)

MOSC Banner

Subject: memory interactions when removing AMM

edited Sep 27, 2019 5:06AM in Database Administration (MOSC) 7 commentsAnswered

It’s been a long, long (long!) time since I’ve dealt with memory allocation issues, so please bear with me.  Hopefully this miserable editor will let me present my data as I would like.

Oracle 12.1.0.2 SE-2

Standalone ASM 12.1.0.2, no RAC, no clustering

Oracle Linux 6

I am preparing to implement hugepages, and so am having to turn off AMM.  My first attempt was to simply ‘alter system reset memory_target scope=spfile;’, and the same for memory_max_target.  When I attempted to restart the db, I got

ORA-00371: not enough shared pool memory, should be at least 255852544 bytes

So I restored the spfile from a backup I had just made for this very issue and restarted the database. I then ran a query to get all of the existing memory related parms and specifically set them along with my ‘reset’ of memory_target.  This allowed me to get the instance started without AMM, but a review of the results showed several other memory parms changed - ones I hadn't touched.

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