ORA-01652: unable to extend temp segment by 8192...

ORA-01652: unable to extend temp segment by 8192...

2014-04-14 11:11  6261人阅读  评论(1)  收藏  举报

  分类：

-----Oracle故障处理（50） 

版权声明：本文为博主原创文章，欢迎扩散，扩散请务必注明出处。

      最近在rebuild index时提示unable to extend temp segment by 8192 in tablespace..的错误提示。这个是个比较常见的错误。索引在创建的时候需要使用到该用户缺省的临时表空间进行排序，以及在索引表空间生成临时段。如果当前的索引表空间限制了自动扩展或者已经达到了数据文件的最大值，此错误提示便会出现。下面是具体的分析及其解决过程。

 

1、错误提示信息

[python]  view plain  copy

 print ?

1. alter index err ORA-01652: unable to extend temp segment by 8192 in tablespace  
2. GX_ARCHIVE_IDX  
3. DECLARE  
4. *  
5. ERROR at line 1:  
6. ORA-01652: unable to extend temp segment by 8192 in tablespace GX_ARCHIVE_IDX  
7. ORA-06512: at line 90  
8.   
9. #下面的信息来自alert log  
10. Sun Mar 30 03:08:51 2014  
11. ORA-1652: unable to extend temp segment by 128 in tablespace                 GX_ARCHIVE_IDX  
12. ORA-1652: unable to extend temp segment by 8192 in tablespace                 GX_ARCHIVE_IDX  
13.   
14. #故障环境  
15. SQL> select * from v$version where rownum<2;  
16.   
17. BANNER  
18. ----------------------------------------------------------------  
19. Oracle Database 10g Release 10.2.0.3.0 - 64bit Production  
20.   
21. SQL> ho cat /etc/issue  
22.   
23. Welcome to SUSE Linux Enterprise Server 10 SP4  (x86_64) - Kernel \r (\l).  

2、关于ORA-1652错误
Error:  ORA-1652
Text:   unable to extend temp segment by %s in tablespace %s
------- -----------------------------------------------------------------------
Cause:  Failed to allocate an extent for temp segment in tablespace.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
        files to the tablespace indicated or create the object in another
        tablespace.

*** Important: The notes below are for experienced users - See Note:22080.1

Explanation:
        This error is fairly self explanatory - we cannot get enough space for a temporary segment.
        The size reported in the error message is the number of contiguous free Oracle blocks that cannot be found in the listed tablespace.

  NOTE: A "temp segment" is not necessarily a SORT segment in a temporary tablespace.
        It is also used for temporary situations while creating or dropping objects like tables and indexes in permanent tablespaces.
        eg: When you perform a CREATE INDEX a TEMP segment is created to hold what will be the final permanent index data.
              This TEMP segment is converted to a real INDEX segment in the dictionary at the end of the CREATE INDEX operation.
              It remains a temp segment for the duration of the CREATE INDEX operation and so failures to extend 
     it report ORA-1652 rather than an INDEX related space error.

临时段被使用的情形
A TEMPORARY segment may be from:
1) A SORT                  Used for a SELECT or for DML/DDL
2) CREATE INDEX          The index create performs a SORT in the users default TEMP tablespace and ALSO uses a TEMP segment to build the final index in the INDEX  tablespace. 
                            Once the index build is complete the segment type is changed.
3) CREATE PK CONSTRAINT   
4) ENABLE CONSTRAINT   
5) CREATE TABLE              New tables start out as TEMPORARY segments.
           Eg: If MINEXTENTS is > 1 or you issue CREATE table as SELECT.
6) Accessing a GLOBAL TEMPORARY TABLE   When you access a global temporary table a TEMP segment is instantiated to hold the temporary data. 

 

3、TROUBLESHOOTING ORA-01652(Reference Doc ID 1267351.1)

#下面是无法扩展临时段的2种情形
EXAMPLE 1:

Temporary tablespace TEMP is being used and is 50gb in size (a recommended minimum for 11g)

TIME 1 : Session 1 starts a long running query
TIME 2 : Session 2 starts a query and at this point in time Session 1 has consumed 48gb of TEMP's free space
TIME 3 : Session 1 and Session 2 receive an ORA-1652 because the tablespace has exhausted of of its free space
    Both sessions fail .. and all temp space used by the sessions are freed (the segments used are marked FREE for reuse)
TIME 4 : SMON cleans up the temporary segments used by Session 1 and Session 2 (deallocates the storage)
TIME 5 : Queries are run against the views V$SORTSEG_USAGE or V$TEMSEG_USAGE and V$SORT_SEGMENT ... and it is found that no space is being used (this is normal)

 

EXAMPLE 2:

Permanent tablespace INDEX_TBS is being used and has 20gb of space free #此时无法扩展临时表空间的问题当属第2种情形

TIME 1 : Session 1 begins a CREATE INDEX command with the index stored in INDEX_TBS 
TIME 2 : Session 1 exhausts all of the free space in INDEX_TBS as a result the CREATE INDEX abends
TIME 3 : SMON cleans up the temporary segments that were used to attempt to create the index
TIME 4 : Queries are run against the views V$SORTSEG_USAGE or V$TEMSEG_USAGE ... and it is found that the INDEX_TBS has no space used (this is normal)

#下面是Solution部分
First it is important to forget what is known about past behavior of the instance as the current tablespace size is insufficient to handle the demand by current sessions

There are three recommended methods of supplying sufficient storage space to meet the needs of current sessions by increasing the size of your temporary tablespace

 

1) Set one or more of the tempfiles|datafiles for the tablespace to AUTOEXTEND with MAXSIZE set ... so that you do not exhaust all available disk volume space 
               (discuss this with a System Administrator)

    After a month or so of having this setting ... AUTOEXTEND can be disabled .. as it is likely that the system has found its true high watermark for temporary segment usage

        (This is the most recommended method as it allows the database instance to find its own high watermark)

 

2) Monitor the temporary segment usage via queries like

           SELECT sum(blocks)*<block size of the temporary tablespace>
           FROM v$tempseg_usage
           WHERE tablespace = '<name of the temporary tablespace>';

     and resize one or more of the tempfiles|datafiles for the tablespace as the tablespace becomes close to exhausted

 

3) Add a tempfile|datafile to the temporary tablespace with the problem and monitor usage as described in #2

Another good idea is to monitor temporary tablespace usage over time to determine what queries are consuming the temporary space space

        For example: How Can Temporary Segment Usage Be Monitored Over Time? (Doc ID 364417.1)
        This note was written to monitor temporary tablespaces .. but may be able to be modified to also monitor permanent tablespaces

 

4、本案例故障解决方案  

[sql]  view plain  copy

 print ?

1. SQL> @temp_sort_segment.sql  
2.   
3. +==================================================================================+  
4. | Segment Name            : The segment name is a concatenation of the             |  
5. |                           SEGMENT_FILE (File number of the first extent)         |  
6. |                           and the                                                |  
7. |                           SEGMENT_BLOCK (Block number of the first extent)       |  
8. | Current Users           : Number of active users of the segment                  |  
9. | Total Temp Segment Size : Total size of the temporary segment in bytes           |  
10. | Currently Used Bytes    : Bytes allocated to active sorts                        |  
11. | Extent Hits             : Number of times an unused extent was found in the pool |  
12. | Max Size                : Maximum number of bytes ever used                      |  
13. | Max Used Size           : Maximum number of bytes used by all sorts              |  
14. | Max Sort Size           : Maximum number of bytes used by an individual sort     |  
15. | Free Requests           : Number of requests to deallocate                       |  
16. +==================================================================================+  
17.   
18.     Tablespace  Segment Current       Total Temp        Currently Pct.   Extent              Max         Max Used         Max Sort     Free  
19.           Name     Name   Users     Segment Size       Used Bytes Used     Hits             Size             Size             Size Requests  
20. -------------- -------- ------- ---------------- ---------------- ---- -------- ---------------- ---------------- ---------------- --------  
21. TEMP           SYS.0.0        0   29,570,891,776                0    0   17,230   29,570,891,776   29,570,891,776   29,569,843,200        0  
22. GOEX_TEMP      SYS.0.0       12   24,135,073,792       12,582,912    0  214,932   24,135,073,792    4,908,384,256    2,960,130,048        0  
23. **************          ------- ---------------- ----------------      -------- ---------------- ---------------- ---------------- --------  
24. sum                          12   53,705,965,568       12,582,912       232,162   53,705,965,568   34,479,276,032   32,529,973,248        0  
25. --从上面的查询中可知，当前实例的temp临时表空间曾耗用量达到29,570,891,776，等于Total Temp Segment Size  
26. --当前我们使用sys帐户来rebulid index，sys帐户使用的是默认的临时表空间temp。  
27.   
28. SQL> @temp_sort_users.sql  -->这个查询是查询当前哪些session正在使用临时段，其结果与上面的一致为12,582,912  
29.   
30. Tablespace Name Username           SID   Serial# Contents  Segment Type  Extents   Blocks        Bytes  
31. --------------- --------------- ------ --------- --------- ------------ -------- -------- ------------  
32. GOEX_TEMP       GOEX_WEBUSER      1079     39023 TEMPORARY LOB_DATA            1      128    1,048,576  
33.                 GOEX_WEBUSER      1078     22320 TEMPORARY LOB_DATA            1      128    1,048,576  
34.                 GOEX_WEBUSER      1075     15301 TEMPORARY LOB_DATA            1      128    1,048,576  
35.                 GOEX_WEBUSER      1056     22505 TEMPORARY LOB_DATA            1      128    1,048,576  
36.                 GOEX_WEBUSER      1046     17617 TEMPORARY LOB_DATA            1      128    1,048,576  
37.                 GOEX_WEBUSER      1042     30925 TEMPORARY LOB_DATA            1      128    1,048,576  
38.                 GOEX_WEBUSER      1041     10180 TEMPORARY LOB_DATA            1      128    1,048,576  
39.                 GOEX_WEBUSER      1038     20315 TEMPORARY LOB_DATA            1      128    1,048,576  
40.                 GOEX_WEBUSER      1034     19147 TEMPORARY LOB_DATA            1      128    1,048,576  
41.                 GOEX_WEBUSER      1028      6362 TEMPORARY LOB_DATA            1      128    1,048,576  
42.                 GOEX_WEBUSER      1027     12614 TEMPORARY LOB_DATA            1      128    1,048,576  
43.                 GOEX_WEBUSER      1022     23077 TEMPORARY LOB_DATA            1      128    1,048,576  
44. ***************                                                         -------- -------- ------------  
45. sum                                                                           12    1,536   12,582,912  
46.   
47. --那我们来看看GX_ARCHIVE_IDX表空间上索引的情形  
48. SQL> SELECT *  
49.   2  FROM (  SELECT segment_name, bytes / 1024 / 1024 / 1024 AS size_g, extents  
50.   3          FROM dba_segments  
51.   4          WHERE tablespace_name = 'GX_ARCHIVE_IDX'  
52.   5          ORDER BY 2 DESC) t  
53.   6  WHERE ROWNUM < 3;  
54.   
55. SEGMENT_NAME                                                         SIZE_G  Extents  
56. ----------------------------------------------------------------- ---------- --------  
57. PK_ACC_POS_STOCK_ARCH_TBL                                         25.9765625      540  
58. PK_ACC_POS_CASH_PL_ARCH_TBL                                       3.97167969      177  
59. --上面的这个查询尽然有一个接近26GB的大索引，问题应该是由于这个大索引引起的。至于这个这么大的索引是另外一个话题，不再次描述。  
60. --根据当前的临时表空间的情形来看应该是够的。  
61. --查看前面描述的 临时段被使用的情形2 CREATE INDEX部分在INDEX  tablespace上也会有temp segment  
62. --所以alert日志报告无法在GX_ARCHIVE_IDX 上extend temp segment  
63.   
64. SQL> @tbs_free_single.sql  
65. Enter value for input_tablespace_name: GX_ARCHIVE_IDX  
66. old  22: AND T.TABLESPACE_NAME=upper('&input_tablespace_name')  
67. new  22: AND T.TABLESPACE_NAME=upper('GX_ARCHIVE_IDX')  
68.   
69. TABLESPACE_NAME                USED_MB  FREE_MB  TOTAL_MB PER_FR  
70. ------------------------------ -------- -------- -------- ------  
71. GX_ARCHIVE_IDX                 45,912   19,037   64,949   29 %  
72.   
73. SQL> @tbs_free_by_file_id.sql  
74. Enter value for input_tbsname: GX_ARCHIVE_IDX  
75. old  26:        AND t.tablespace_name = UPPER ('&input_tbsname')  
76. new  26:        AND t.tablespace_name = UPPER ('GX_ARCHIVE_IDX')  
77.   
78. TABLESPACE_NAME                   FILE_ID USED_MB  FREE_MB  TOTAL_MB PER_FR  
79. ------------------------------ ---------- -------- -------- -------- ------  
80. GX_ARCHIVE_IDX                       25   29,328    2,916   32,244    9 %  
81. GX_ARCHIVE_IDX                       40   16,584   16,121   32,705   49 %  
82.   
83. SQL> select file_id,file_name,autoextensible from dba_data_files where file_id in(25,40);  
84.   
85.    FILE_ID FILE_NAME                                                    AUT  
86. ---------- ------------------------------------------------------------ ---  
87.         25 /u02/database/CABO3/oradata/CABO3_archive_idx.dbf            NO  
88.         40 /u02/database/CABO3/oradata/CABO3_archive_idx2.dbf           YES  
89.   
90. --根据1267351.1的solution，我们为GX_ARCHIVE_IDX表空间添加一个新的数据文件  
91. SQL> alter tablespace GX_ARCHIVE_IDX add datafile '/u02/database/CABO3/oradata/CABO3_archive_idx3.dbf'  
92.   2  size 2g autoextend on;  
93.   
94. Tablespace altered.  
95.   
96. --为该表空间增加数据文件后，无此异常