But in 12c, Oracle prefers using OSM over either ISM or DISM. That appears to
be the cause the of the problems I'm having.
Anybody else install 12c on solaris and have issues with OSM not working as
expected?
Matt
From: Dimensional DBA [mailto:dimensional.dba@xxxxxxxxxxx]
Sent: Friday, February 12, 2016 11:40 AM
To: Matt Adams; oracle-l@xxxxxxxxxxxxx
Subject: RE: oracle handing memory allocation different between 11g and 12c?
A good reference note with a lot of explanations and some extra pointers to
other key docs
ISM or DISM Misconfiguration can Slow Down Oracle Database Performance (Doc ID
1472108.1)
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
Dimensional.dba@xxxxxxxxxxx<mailto:Dimensional.dba@xxxxxxxxxxx>
View Matthew Parker's profile on
LinkedIn<http://www.linkedin.com/pub/matthew-parker/6/51b/944/>
www.dimensionaldba.com<http://www.dimensionaldba.com>
From: Dimensional DBA [mailto:dimensional.dba@xxxxxxxxxxx]
Sent: Friday, February 12, 2016 8:35 AM
To: 'MAdams@xxxxxxxxxxxxxxxxxxx'; 'oracle-l@xxxxxxxxxxxxx'
Subject: RE: oracle handing memory allocation different between 11g and 12c?
There is a difference for Solaris
https://docs.oracle.com/database/121/UNXAR/appe_sol.htm#UNXAR013
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
Dimensional.dba@xxxxxxxxxxx<mailto:Dimensional.dba@xxxxxxxxxxx>
View Matthew Parker's profile on
LinkedIn<http://www.linkedin.com/pub/matthew-parker/6/51b/944/>
www.dimensionaldba.com<http://www.dimensionaldba.com>
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Matt Adams
Sent: Friday, February 12, 2016 7:36 AM
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: oracle handing memory allocation different between 11g and 12c?
OS: Solaris 10 running on a zone of a T-4
I'm attempting to upgrade a database from 11.2.0.4 to 12.1.0.4
After running all prerequisite checks and resolving issues, I'm ready to run
the upgrade
Starting the database using the 12c software, I'm getting the following
SQL> startup upgrade
ORA-27125: unable to create shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 2634
Additional information: 4194304
Additional information: 4194304
Sga_max_size is 1 G (same size used when database was 11g)
Sga_targeet is 1 G
(lowering both of these to 500 Meg makes no difference)
Ipcs -a shows roughly 2.5 gig being used by other 11 g datbases on this server.
/etc/project has
user.oracle:100::oracle::project.max-sem-ids=(priv,100,deny);project.max-shm-memory=(priv,5368709120,deny);rcap.max-rss=19327352832
(which I understand to mean that the total of all shared memory segments is
limited to 5 Gig.)
Is there something different between the 11g and 12c versions that might
explain this?
The alert log is showing:
Fri Feb 12 10:29:30 2016
Starting ORACLE instance (normal) (OS id: 14926)
Fri Feb 12 10:29:30 2016
CLI notifier numLatches:3 maxDescs:1344
Fri Feb 12 10:29:30 2016
All SGA segments were allocated at startup
Fri Feb 12 10:29:30 2016
WARNING: The system does not seem to be configured
optimally. Creating a segment of size 0x0000000000400000
failed. Please change the shm parameters so that
a segment can be created for this size. While this is
not a fatal issue, creating one segment may improve
performance
Fri Feb 12 10:29:30 2016
**********************************************************************
Fri Feb 12 10:29:30 2016
Dump of system resources acquired for SHARED GLOBAL AREA (SGA)
Fri Feb 12 10:29:30 2016
Available system pagesizes:
8K, 64K, 4096K, 256M, 2048M
Fri Feb 12 10:29:30 2016
Supported system pagesize(s):
Fri Feb 12 10:29:30 2016
PAGESIZE AVAILABLE_PAGES EXPECTED_PAGES ALLOCATED_PAGES ERROR(s)
Fri Feb 12 10:29:30 2016
4096K Configured 63 0 ORA-27125
Fri Feb 12 10:29:30 2016
256M Configured 1 0 NONE
Fri Feb 12 10:29:30 2016
2048M Configured 0 0 NONE
Fri Feb 12 10:29:30 2016
Reason for not supporting certain system pagesizes:
Fri Feb 12 10:29:30 2016
8K - Pagesize not supported by shared memory type
Fri Feb 12 10:29:30 2016
64K - Pagesize not supported by shared memory type
Fri Feb 12 10:29:30 2016
**********************************************************************
**** This communication may contain privileged and/or confidential information.
If you are not the intended recipient, you are hereby notified that disclosing,
copying, or distributing of the contents is strictly prohibited. If you have
received this message in error, please contact the sender immediately and
destroy any copies of this document. ****
**** This communication may contain privileged and/or confidential information.
If you are not the intended recipient, you are hereby notified that disclosing,
copying, or distributing of the contents is strictly prohibited. If you have
received this message in error, please contact the sender immediately and
destroy any copies of this document. ****
