• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 197
  • Last Modified:

Consultation for changing the parameter MEMORY_TARGET

Hi experts,
In a RAC ASM 11g, Linux  (RedHat  2.6.18), with 2 instance, I need to modify:
memory_max_target parameters (static parameter) 
memory_target (dynamic).

Open in new window

Both in 8G ( currently have 6G)
I received a recommendation that tells me tweak in /etc/fstab:
 /dev/shm ----> defaults, size = 8G,

Open in new window

and then:
mount -o remount / dev / shm

Open in new window

In addition to the statements:
ALTER SYSTEM SET MEMORY_MAX_TARGET = 7680M SCOPE = SPFILE; 
ALTER SYSTEM SET MEMORY_TARGET = 7680M SCOPE = SPFILE; 

Open in new window

then, in both nodes:
shutdown immediate
startup

Open in new window

Currently the line in fstab says:
tmpfs /dev/shm tmpfs defaults, nosuid, nodev 0 0

Open in new window

Is it necessary to make this change in the fstab?
Would appreciate a look from you and the basic steps to perform the task.
Thank you very much
Regards
0
carlino70
Asked:
carlino70
  • 3
  • 3
1 Solution
 
sdstuberCommented:
yes, you need to make your tmpfs large enough to hold your MEMORY_MAX_TARGET.

You are trying to hold 7.6G of oracle memory inside 6G of allocation.

my guess is you are seeing ORA-00845 errors because of this.

So, make /dev/shm larger or your memory_max_target lower
0
 
carlino70Author Commented:
I'm not seeing errors like ORA-00845 in AlertLog
But if the base, shows slow queries and runs Oracle jobs.
Thanks
0
 
carlino70Author Commented:
sorry, I wrote bad:
But the database, shows slow queries and runs Oracle jobs.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
sdstuberCommented:
The instance shouldn't start if you have memory_target (or max_memory_target) of 7.6G with only 6G of shared memory.

Maybe I misunderstood what you posted above, are all of those code boxes suggestions or are some of them what you currently have?

I thought the 8G change was the suggestion and the rest was what you actually had, in which case I would expect an error.


If all of it is a suggestion, then yes, go with that.  It should work.
0
 
carlino70Author Commented:
Excellent!, Thanks
0
 
sdstuberCommented:
Glad I could help.

Making sure your shared memory at the OS level is big enough for the instance's memory is just an extension of the same thing you would have had to do when the database was created.

Configuring /dev/shm to be big enough is one of the preinstallation requirements

http://docs.oracle.com/cd/E11882_01/install.112/e47689/pre_install.htm#LADBI1096

Here you're already installed, but if you're making your instance bigger, then same idea as the preinstall.  You must also make the /dev/shm big enough to hold it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now