Reserved Memory Insight

[Jack Trachtman]

(VMS V7.3-2)

We use Reserved Memory to set aside memory
for Oracle. Occassionally, we have been
testing Oracle which included restarting it.
Usually, after only a few restarts, we get
to a point where Oracle will not start,
complaining that it can't get its
Reserved Memory. When we reboot, Oracle
is fine.

Can anyone explain what's happening here?
Can Reserved Memory get "fragmented"?

Thanks all

[Jan van den Ende]

Jack,

without further info, my first action would be to check whether Oracle releases the reserved memory upon shutdown.

I bet more than even chances that it does NOT, and reserves another chunk of memory upon restart each time. And so on, until reservable memory gets exhausted.
Of course reboot clears that :-(

Please, check this out first.

Proost.

Have one on me.

jpe

[Marc Van den Broeck · Accepted solution]

Jack,

i also use reserved memory for Oracle instances. I have 3 instances and each of it gets his own 'named' reserved memory chunk. After shutting down Oracle you have to wait some time before you restart the instance. Use show mem to see when your reserved memory has been released by Vms. If you start to soon you get the error you specify. You can also see in your alert.log file that the amount of memory you allocate is not too large (to avoid wasting memory). What version of Oracle do you have? My experience is based on Oracle7 and Oracle8 instances. I dont know (yet) how Oracle9 behaves. (Seen your Vms version i guess you are using Oracle9)

Rgds
Marc

[Marc Van den Broeck]

Jack,

some more info.
I dont think it can get fragmented, because it is one 'named' chunk of memory. It is not allocated in pieces, it is everything or nothing. The larger this reserved memory block is, the more time Vms needs to free it. I wait 2 minutes between shutdown and startup for a block of memory of 30000 pages. (sga of about 240M i think). Of course the time will also depend on the power of your Alpha. (I have a cluster of two COMPAQ AlphaServer DS20E 666 MHz).
There are no routines (lib$, sys$ or ...) you can use to ask Vms whether reserved memory has been freed. (unless they have been made available in Vms 7.3)

Rgds
Marc

[Jack Trachtman]

Marc's input is interesting. When we've
had this problem, we've issued a SHOW
MEM/RES and that has always shown that
the reserved memory is totally free. But
since our res mem size is (presently) 6GB,
maybe we do have to wait 5 minutes for the
memory to become available. Is this
reasonable, or should VMS be able to
deallocate memory in only a few seconds?

[Ian Miller.]

It appears that the reserved memory can become internally fragmented and that the order that you startup the oracle instances is important (big ones first is best).

Is there a significant swapper activity after oracle is shutdown or other system activity?

[Marc Van den Broeck]

Jack,

I wait 2 mins because 1 min was not long enough. So i dont know how long you should wait for 6Gb.
How many Oracle instances do you have and how large is each sga (or better block of memory you reserve).

Ian,
reserved memory is allocated at startup.
If I allocate two named chunks of reserved memory then how can it get fragmented when I shut/start Oracle? Isn't it allocated all the time but only used or free?

[Ian Miller.]

I think I saw a situation with one named reserved area and multiple oracle instances - vague memory so may be wrong

[Marc Van den Broeck]

Ian,
to refresh your memory ;-)
You can only load one Oracle instance in a named reserved memory block because Oracle uses the name the 'grab' the block.
e.g.
database name (sid in fact) MYDB
If you then create a reserved memory block with the name ORA_MYDB_SGA Oracle will use it, nothing else to do. (You must make it large enough to make the sga fit and not too large to waste memory)

Rgds
Marc

[Marc Van den Broeck]

Hi Jack,

I wonder if you found a good solution yet. It might be of interest for people involved with large databases.
Thx

Rgds
Marc