<wbr></wbr>
<wbr></wbr>
|
|
<wbr></wbr>
|
RAC databases and ORA-1652: Unable To Extend
Temp Segment By %s In Tablespace TEMP [ID 258941.1]
|
转到底部
|
<wbr></wbr>
|
修改时间:2012-2-7类型:PROBLEM状态:MODERATED优先级:3
|
注释 (0)
<wbr></wbr>
|
<wbr></wbr>
|
|
|
|
|
<wbr></wbr>
In this Document
Symptoms
Changes
Cause
Solution
References
This document is being delivered to you via
Oracle Support's Rapid Visibility (RaV) process and therefore has
not been subject to an independent technical review.
|
Applies to:
Oracle Server - Enterprise Edition - Version:
9.2.0.1 to 10.2.0.1 - Release: 9.2 to 10.2
Information in this document applies to any platform.
***Checked for relevance on 06-Feb-2012***
Symptoms
Scripts may fail due to ORA-1652 "unable to extend
temp segment by %s in
tablespace TEMP"
although free space exists in TEMP tablespace in a RAC database
configuration.
Also scripts may not fail you may find error messages
(ORA-1652)
inside the alert.log of some of the instances.
Changes
Migrate to RAC configuration.
Use Default Temporary Tablespace feature.
Cause
We have 2 separate bugs here:
bug 2934117 : ORA-1652:CAN'T ACQUIRE FREE EXTENTS OWNED BY
OTHER NODE
for when scripts fail and also
bug 2858082 : EVEN IF THE FREE EXTENTS ARE AVAILABLE, ORA-1652
OCCURS IN ALERT.
LOG ON RAC
when scripts do not fail but errors appear inside alert.log of RAC
instances.
Solution
1st Case
bug 2934117
====================
Due to
bug 2934117 we should NOT use a DEFAULT TEMPORARY
TABLESPACE
for RAC database configuration, otherwise scripts could fail with
ORA-1652 as a RAC node
cannot acquire free extents that are owned by another RAC instance
although they are free.
bug 2934117 is fixed in 9205 and all versions of Oracle 10.
Therefore, the best solution is to apply the latest patch set or to
upgrade to a supported version of Oracle.
Another solution is to apply the following workaround:
Workaround
------------------
step 1: Create new normal temp tablespace with minimum size (for
example TEMPRAC )
step 2: Set as default temp tablespace TEMPRAC
alter database default temporary tablespace TEMPRAC;
This commands changes all database users temporary tablespace to
TEMPRAC
Now previous default temporary tablespace TEMP is a normal
temporary tablespace.
step 3: For all database users change back temporary tablespace to
TEMP:
alter user default tempory teblespace TEMP;
step 4: shutdown immediate all instances
step 5: startup all instance
Unfortunatelly this TEMPRAC Default Temporary Tablespace cannot be
dropped
completely.
We should keep it with small size.
In case new Database users are created, and temporary tablespace is
not defined
at creation time, these would
have as temporary tablespace TEMPRAC, so every new user after
creation we have
to specify:
alter user temporary tablespace TEMP;
-> in order to change their temporary tablespace to TEMP which
is a normal
temporary tablespace.
2nd case
bug 2858082
==================
The 2nd issue is caused due to the
bug 2858082 "EVEN IF THE FREE EXTENTS ARE
AVAILABLE, ORA-1652 OCCURS IN ALERT.LOG ON RAC "
In this bug although scripts that need Temp tablespace space due to
Sort
Operations (order by, group by, join, etc)
are successfull we may see this error message inside alert.log of
RAC instances.
When a RAC instance fills its own sort pool of extents, instead of
allocation
new extents it may ask for free temp extents
from the other RAC instances. During this operation the ORA-1652
may appear
inside the alert.log although the operation has succeeded.
This bug would only be solved in subsequent releases as it has
been
characterised as a low priority issue from development as only
dis-affect is that alert.log
may contain such messages but process do not fail.
You can ignore these error messages.
bug 2858082 is now fixed in 9207 10104 and 10201.
Therefore, the best option is to apply the latest patch set.
References
BUG:2934117 - ORA-1652:CAN'T ACQUIRE FREE EXTENTS OWNED BY
OTHER NODE
<wbr></wbr>
<wbr></wbr>
ORA-1652
<wbr></wbr>
返回页首
<wbr></wbr>
<wbr></wbr>
分享到:
相关推荐
ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-01033:oracle initialization or shutdown in progress 解决方法 ora-...
在运行查询SELECT * FROM V$SESSION 会出现ORA-29275:部分多字节字符的错误,这是什么原因开始我不得其解,网上也没有介绍什么好办法。本文给出答案。
ORA-12154: TNS: 无法解析指定的连接标识符的解决方法
ORA-00031:标记要终止的会话解决方案; ORA-00031:标记要终止的会话解决方案;
ORA-32001:write to spfile requested but no spfile is in use请求写入spfile,但没有使用spfile的解决方法 在输入以下语句中报了这样的错误: SQL>alter system set control_files=’/u01/app/oracle/oradata/prod/...
调整参数后引起,ORA-00838: Specified value of MEMORY_TARGET is too small, needs to be at least 3 2768M 的解决方案
oracle12c程序连接时异常: ORA-01017: 用户名/口令无效; 登录被拒绝 的解决方案。
ORA-01036:非法的变量名/编号 oracle特有的错误
oracle 12 c ORA-01017: 用户名/口令无效; 登录被拒绝
NULL 博文链接:https://3w1h.iteye.com/blog/1211779
-- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... -- 解决ORA-00904: "WMSYS"."WM_CONCAT": 标识符无效 的文件包....... ...
解决ORACLE TNS: 无法解析指定的连接标识符; 里面有步骤
错误描述:oracle远程连接服务器出现 ORA-12170 TNS:连接超时 错误检查:有很多是oracle自身安装的问题,但是我这里服务器配置正常,监听正常,服务正常,远程可以ping通服务器。 这里主要是防火墙问题,解决办法: ...
最近在工作中遇到了一个问题,错误是Oracle dbca时报错:ORA-12547: TNS:lost contact,通过查找相关的资料终于找到了解决的方法,下面分享给大家,话不多说了,来一起看看详细的介绍吧。 环境: OS:RHEL6.5 x86-...
ora-12514:TNS:监听程序当前无法识别连接描述符中请求的服务bug,解决文档.
CLOB字段类型报错 ORA-01704:文字字符串过长的解决
oracle19c缺少的函数
ORA-12541 TNSno listener 的解决方案 ORA-12541 TNSno listener 的解决方案
ORA-12518 TNS:监听程序无法分发客户机连接,在您安装好数据库后配置连接数据库的过程中遇到这类问题应该很头疼吧,不过,当您还是四处查资料来解决您遇到的另你头疼的问题时,如果不经意间看到了这则贴子,那请您升...