Home » Infrastructure » Unix » OS Solaris Parameter That May Affect the SGA (Oracle 10g, Solaris 10)
OS Solaris Parameter That May Affect the SGA [message #576427] Mon, 04 February 2013 19:41 Go to next message
rielph
Messages: 2
Registered: February 2013
Location: Philippines
Junior Member
Please help I can't reduced the SGA target to less than 850M, the server (UAT) is a replicate of the production the only difference is it's part of a zone now, in prod I can reduced the SGA to 200M, but now it's not possible an error message prompt please help what kernel or OS parameter, or Oracle parameter I need to set in the zone so I can reduced the SGA target. Below are the logs. Thank you

SQL> show parameter sga

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 1536M
sga_target big integer 1536M
SQL> create pfile='init_elams_20130204.ora' from spfile;




SQL> startup pfile=init_elams_20130204.ora
ORACLE instance started.

Total System Global Area 893386752 bytes
Fixed Size 2141952 bytes
Variable Size 199184640 bytes
Database Buffers 553648128 bytes
Redo Buffers 138412032 bytes
Database mounted.
Database opened.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[dev-dbs]:elams>/appl1/home/oracle/10.2/dbs>> sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Mon Feb 4 16:59:33 2013

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.


Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[dev-dbs]:elams>/appl1/home/oracle/10.2/dbs>> vi init_elams_20130204.ora
"init_elams_20130204.ora" 19 lines, 753 characters
*.audit_file_dest='/appl1/home/oracle/admin/elams/adump'
*.background_dump_dest='/appl1/home/oracle/admin/elams/bdump'
*.compatible='10.2.0.3.0'
*.control_files='/u101/oradata/elams/control/control_01.ctl','/u301/oradata/elams/control/control_02.ctl','/u501/oradata/elams/contro l/control_03.ctl'
*.core_dump_dest='/appl1/home/oracle/admin/elams/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='elams'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=elamsXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=1048576000
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=750M
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/appl1/home/oracle/admin/elams/udump'
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
"init_elams_20130204.ora" 19 lines, 753 characters
[dev-dbs]:elams>/appl1/home/oracle/10.2/dbs>> sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0 - Production on Mon Feb 4 17:00:09 2013

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL> startup pfile=init_elams_20130204.ora
ORA-12853: insufficient memory for PX buffers: current 0K, max needed 27738K
ORA-04031: unable to allocate 65560 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
SQL> exit
Disconnected
[dev-dbs]:elams>/appl1/home/oracle/10.2/dbs>> vi init_elams_20130204.ora
"init_elams_20130204.ora" 19 lines, 753 characters
*.audit_file_dest='/appl1/home/oracle/admin/elams/adump'
*.background_dump_dest='/appl1/home/oracle/admin/elams/bdump'
*.compatible='10.2.0.3.0'
*.control_files='/u101/oradata/elams/control/control_01.ctl','/u301/oradata/elams/control/control_02.ctl','/u501/oradata/elams/contro l/control_03.ctl'
*.core_dump_dest='/appl1/home/oracle/admin/elams/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='elams'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=elamsXDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=1048576000
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=850M
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/appl1/home/oracle/admin/elams/udump'
Re: OS Solaris Parameter That May Affect the SGA [message #576428 is a reply to message #576427] Mon, 04 February 2013 20:26 Go to previous messageGo to next message
BlackSwan
Messages: 22554
Registered: January 2009
Senior Member
>SQL> show parameter sga
we don't know upon which system above was done.

Only you can determine what is different between Prod & UAT.
Since you get different results between the two system; something must be different between the two systems.

Please read and follow the forum guidelines, to enable us to help you:

http://www.orafaq.com/forum/t/88153/0/
Re: OS Solaris Parameter That May Affect the SGA [message #576640 is a reply to message #576428] Wed, 06 February 2013 20:44 Go to previous message
rielph
Messages: 2
Registered: February 2013
Location: Philippines
Junior Member
Hi BlackSwan,

Thank you for reply, below are the snapshot of the kernel parameter of the production & the development servers. They differ on project.max-shm-memory but this is okay cause less memory is allotted for development but significantly they differs on project.max-device-locked-memory and project.max-crypto-memory, do you this reducing the project.max-device-locked-memory and project.max-crypto-memory is the key to reduce the SGA to 200MB?


Production:
>> ps -o taskid -p $$
TASKID
19029
>> prctl -i task 19029
task: 19029
project.max-device-locked-memory
privileged 1.95GB - deny
system 16.0EB max deny
project.max-crypto-memory
privileged 7.79GB - deny
system 16.0EB max deny
project.max-shm-memory
privileged 24.0GB - deny
system 16.0EB max deny



Development:
>> ps -o taskid -p $$
TASKID
1706
>> prctl -i task 1706
task: 1706
project.max-device-locked-memory
privileged 7.81GB - deny
system 16.0EB max deny
project.max-crypto-memory
privileged 31.3GB - deny
system 16.0EB max deny
project.max-shm-memory
privileged 10.0GB - deny
system 16.0EB max deny

Previous Topic: database/install/.oui: cannot execute
Next Topic: cron job
Goto Forum:
  


Current Time: Thu Jul 31 21:46:53 CDT 2014

Total time taken to generate the page: 0.06093 seconds