<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>《ORA-27103 when Memory target parameter is set to more than 3 GB(11.1.0.7)》的评论</title>
	<atom:link href="https://www.xifenfei.com/2012/03/ora-27103-when-memory-target-parameter-is-set-to-more-than-3-gb11-1-0-7.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com/2012/03/ora-27103-when-memory-target-parameter-is-set-to-more-than-3-gb11-1-0-7.html</link>
	<description>提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971</description>
	<lastBuildDate>Thu, 11 Dec 2025 02:46:14 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>作者：惜分飞</title>
		<link>https://www.xifenfei.com/2012/03/ora-27103-when-memory-target-parameter-is-set-to-more-than-3-gb11-1-0-7.html/comment-page-1#comment-750</link>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
		<pubDate>Thu, 29 Mar 2012 09:04:31 +0000</pubDate>
		<guid isPermaLink="false">https://www.xifenfei.com/?p=2789#comment-750</guid>
		<description><![CDATA[ORA-27103 when  Memory target parameter is set to more than 3 GB
[shell]
Applies to:
Oracle Server - Enterprise Edition - Version: 11.1.0.7 to 11.1.0.7 - Release: 11.1 to 11.1
Linux x86-64

Symptoms
When setting the memory_target parameter on 11.1.0.7 &gt; 3GB, The instance can not start up and crashes with the following errors displayed in the alert log:
ALTER DATABASE MOUNT 
This instance was first to mount 
Errors in file /oracle/app/oracle/diag/rdbms/dwhp/DWHP1/trace/DWHP1_mman_22192.trc: 
ORA-27103: internal error 
Linux-x86_64 Error: 11: Resource temporarily unavailable 
Additional information: -1 
Additional information: 1 
MMAN (ospid: 22192): terminating the instance due to error 27103 
System state dump is made for local instance 
System State dumped to trace file /oracle/app/oracle/diag/rdbms/dwhp/DWHP1/trace/DWHP1_diag_22166.trc 
Trace dumping is performing id=[cdmp_20080929103326] 
Instance terminated by MMAN, pid = 22192

OR

ORA-27103: internal error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: -1
Additional information: 1
MMAN (ospid: 12249): terminating the instance due to error 27103
Instance terminated by MMAN, pid = 12249

OR

Errors in file /app/oemrep/diag/rdbms/emrep/emrep/trace/emrep_mman_30849.trc: 
ORA-27103: internal error 
Linux-x86_64 Error: 17: File exists 
Additional information: -1 
Additional information: 1 
MMAN (ospid: 30849): terminating the instance due to error 27103 
Instance terminated by MMAN, pid = 30849 

OR

DBCA fails with ORA-03114 error
This issue is not reproduced in 11.1.0.6

Changes

Applied the 11.1.0.7 patch set.

Cause
The problem is due to Bug:7272646, introduced in 11.1.0.7 patchset on 64bit Linux.

In some cases, after applying the 11.1.0.7 patch set on 64Bit Linux x86 the instance will not start when MEMORY_TARGET &gt; 3GB.


Solution
An interim Patch:7272646 is available on My Oracle Support for Linux x86-64 11.1.0.7. 
After applying the patch, test with memory_target set  &gt; 3GB to verify patch resolves issue.

To workaround the issue:

1. Reduce value for kernel parameter SHMMAX below 4Gb (4294967296). This will cause more shared memory segments to be created for the instance SGA. There is no impact to setting SHMMAX lower.
[/shell]]]></description>
		<content:encoded><![CDATA[<p>ORA-27103 when  Memory target parameter is set to more than 3 GB</p>
<pre class="brush: bash; title: ; notranslate">
Applies to:
Oracle Server - Enterprise Edition - Version: 11.1.0.7 to 11.1.0.7 - Release: 11.1 to 11.1
Linux x86-64

Symptoms
When setting the memory_target parameter on 11.1.0.7 &gt; 3GB, The instance can not start up and crashes with the following errors displayed in the alert log:
ALTER DATABASE MOUNT 
This instance was first to mount 
Errors in file /oracle/app/oracle/diag/rdbms/dwhp/DWHP1/trace/DWHP1_mman_22192.trc: 
ORA-27103: internal error 
Linux-x86_64 Error: 11: Resource temporarily unavailable 
Additional information: -1 
Additional information: 1 
MMAN (ospid: 22192): terminating the instance due to error 27103 
System state dump is made for local instance 
System State dumped to trace file /oracle/app/oracle/diag/rdbms/dwhp/DWHP1/trace/DWHP1_diag_22166.trc 
Trace dumping is performing id=[cdmp_20080929103326] 
Instance terminated by MMAN, pid = 22192

OR

ORA-27103: internal error
Linux-x86_64 Error: 25: Inappropriate ioctl for device
Additional information: -1
Additional information: 1
MMAN (ospid: 12249): terminating the instance due to error 27103
Instance terminated by MMAN, pid = 12249

OR

Errors in file /app/oemrep/diag/rdbms/emrep/emrep/trace/emrep_mman_30849.trc: 
ORA-27103: internal error 
Linux-x86_64 Error: 17: File exists 
Additional information: -1 
Additional information: 1 
MMAN (ospid: 30849): terminating the instance due to error 27103 
Instance terminated by MMAN, pid = 30849 

OR

DBCA fails with ORA-03114 error
This issue is not reproduced in 11.1.0.6

Changes

Applied the 11.1.0.7 patch set.

Cause
The problem is due to Bug:7272646, introduced in 11.1.0.7 patchset on 64bit Linux.

In some cases, after applying the 11.1.0.7 patch set on 64Bit Linux x86 the instance will not start when MEMORY_TARGET &gt; 3GB.


Solution
An interim Patch:7272646 is available on My Oracle Support for Linux x86-64 11.1.0.7. 
After applying the patch, test with memory_target set  &gt; 3GB to verify patch resolves issue.

To workaround the issue:

1. Reduce value for kernel parameter SHMMAX below 4Gb (4294967296). This will cause more shared memory segments to be created for the instance SGA. There is no impact to setting SHMMAX lower.
</pre>
]]></content:encoded>
	</item>
</channel>
</rss>
