Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
sga_max_size internally adjusted in pfile
- Thread starter bookouri
- Start date
SantaMufasa
Technical User
My guess is that when you use the:
"ALTER SYSTEM SET ... BOTH" command to adjust one or more parameter values, because you specified "BOTH", that Oracle modifies the parameter in your init<SID>.ora file to keep the parameter value consistent with the setting you specified in the "ALTER SYSTEM..." command.
You can test my theory by using another "ALTER SYSTEM SET... BOTH" command to change the "sga_max_size" value yet again, and see if there is any effect on your init<SID>.ora entry.
![[santa]](/data/assets/smilies/santa.gif "[santa] [santa]")
Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
"ALTER SYSTEM SET ... BOTH" command to adjust one or more parameter values, because you specified "BOTH", that Oracle modifies the parameter in your init<SID>.ora file to keep the parameter value consistent with the setting you specified in the "ALTER SYSTEM..." command.
You can test my theory by using another "ALTER SYSTEM SET... BOTH" command to change the "sga_max_size" value yet again, and see if there is any effect on your init<SID>.ora entry.
Mufasa(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]
- Thread starter
- #3
Actually, I only made the change through the enterprise manager utility. Then did a create pfile= from spfile as a backup and thats when i noticed the #internally adjusted notation. Ive since shutdown and restarted and recreated the pfile, but the notation is still there.
Hi,
The SGA has different components like db cache, redo log buffer, shared pool, large pool, java pool...
The total size of the SGA has to be large enough to hold them all. If you change this parameters and the sum of the sizes is larger than sga_max_size that parameter has to be increased.
You did your changes using em. I guess sga_max_size is checked and accordingly changed by em automatically.
As you did not explicitly change the value the remark was added to tell you about the change.
Stefan
The SGA has different components like db cache, redo log buffer, shared pool, large pool, java pool...
The total size of the SGA has to be large enough to hold them all. If you change this parameters and the sum of the sizes is larger than sga_max_size that parameter has to be increased.
You did your changes using em. I guess sga_max_size is checked and accordingly changed by em automatically.
As you did not explicitly change the value the remark was added to tell you about the change.
Stefan
- Status
