Unable to extend datafile which is autoextend on.

Hi All,
I am facing interesting problem in
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production
SunOS XYZ 5.10 Generic_138888-07 sun4u sparc SUNW,Sun-Fire-880
Datafile is autoextend on and enough free space is available in mount point on OS, but datafile is unable to extend.....
Below are the details:
select file_name,AUTOEXTENSIBLE from dba_data_files where tablespace_name='I_20090414_4';
FILE_NAME                                                                                                      AUTOEXTENSIBLE
/mnt/tfmdtwmna01/apps3/oradata/wmsgivn/i_20090414_4.dbf                                   YES
SQL> !df -h /mnt/tfmdtwmna01/apps3/
Filesystem             size   used avail capacity Mounted on
ABCDEF.cda.com:/vol/vol3/apps3
                       315G   201G   114G    64%    /mnt/tfmdtwmna01/apps3Did anyone have faced this type of issue????? I think this database is hitting some bugs....
Some inputs:
OS was recently upgraded to Solaris 5.10 and Database was also recently upgraded from 9.2.0.7 to 9.2.0.8
Please help!!!!!
-Yasser
Edited by: YasserRACDBA on Apr 15, 2009 6:18 PM

SQL> sho parameter block
NAME                                 TYPE        VALUE
db_block_buffers                     integer     0
db_block_checking                    string      FALSE
db_block_checksum                    boolean     TRUE
db_block_size                        integer     8192
db_file_multiblock_read_count        integer     16-Yasser

Similar Messages

Unable to extend table

Hi All,
I have Oracle 8i installed on Redhat 7.3
I am trying to import from a large dmp file (10 GB). Initially I was getting error related to "unable to extend datafile", which I got over by creating multiple datafiles with size 2GB each. Thanks to the help provided on this list.
But now I ran into another error that reads as following:
IMP-00058: ORACLE error 1653 encountered
ORA-01653: unable to extend table XXX.XXX_DAT by 311072 in tablespace YYY
IMP-00017: following statement failed with ORACLE error 1031:
"CREATE TRIGGER "USERME".XXX_BI before insert"
I have created enough datafile and I have 60 GB available space on the drive. Please guide me as to what am I doing wrong here, and how could I get over this problem.
Thanks.
Amit

Hi Joel,
Thanks for your time.
I have already done that part before I started import. The user has unlimited quota on the tablespace. But the problem still shows up.
By the way, I have multiple dmp files, I could import the first dmp file, but this error shows up while doing the import for the next dmp file, which should just append the data to the existing table. I am sorry, I should have mentioned this before.
Please advise.
-Amit

ORA-1653: unable to extend table - but enough space for datafile

We encountered this problem in one of our database Oracle Database 10g Release 10.2.0.4.0
We have all datafiles in all tablespaces specified with MAXSIZE and AUTOEXTEND ON. But last week database could not extend table size
Wed Dec 8 18:25:04 2013
ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
Wed Dec 8 18:25:04 2013
ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
Wed Dec 8 18:25:04 2013
ORA-1653: unable to extend table PCS.T0102 by 128 in                 tablespace PCS_DATA
ORA-1653: unable to extend table PCS.T0102 by 8192 in                tablespace PCS_DATA
Datafile was created as ... DATAFILE '/u01/oradata/PCSDB/PCS_DATA01.DBF' AUTOEXTEND ON NEXT 50M MAXSIZE 31744M
Datafile PCS_DATA01.DBF had only 1GB size. Maximum size is 31GB but database did not want to extend this datafile.
We used temporary solution and we added new datafile to same tablespace. After that database and our application started to work correctly.
There is enough free space for database datafiles.
Do you have some ideas where could be our problem and what should we check?
Thanks

ShivendraNarainNirala wrote:
Hi ,
Here i am sharing one example.
SQL> select owner,table_name,blocks,num_rows,avg_row_len,round(((blocks*8/1024)),2)||'MB' "TOTAL_SIZE",
2   round((num_rows*avg_row_len/1024/1024),2)||'Mb' "ACTUAL_SIZE",
3   round(((blocks*8/1024)-(num_rows*avg_row_len/1024/1024)),2) ||'MB' "FRAGMENTED_SPACE"
4   from dba_tables where owner in('DWH_SCHEMA1','RM_SCHEMA_DDB','RM_SCHEMA') and round(((blocks*8/1024)-(num_rows*avg_row_len/1024/1024)),2) > 10 ORDER BY FRAGMENTED_SPACE;
OWNER           TABLE_NAME                        BLOCKS   NUM_ROWS AVG_ROW_LEN TOTAL_SIZE           ACTUAL_SIZE          FRAGMENTED_SPACE
DWH_SCHEMA1     FP_DATA_WLS                        14950     168507          25 116.8MB              4.02Mb               112.78MB
SQL> select tablespace_name from dba_segments where segment_name='FP_DATA_WLS' and owner='DWH_SCHEMA1';
TABLESPACE_NAME
DWH_TX_DWH_DATA
SELECT /* + RULE */ df.tablespace_name "Tablespace",
       df.bytes / (1024 * 1024) "Size (MB)",
       SUM(fs.bytes) / (1024 * 1024) "Free (MB)",
       Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",
       Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used"
FROM dba_free_space fs,
       (SELECT tablespace_name,SUM(bytes) bytes
          FROM dba_data_files
         GROUP BY tablespace_name) df
WHERE fs.tablespace_name = df.tablespace_name
GROUP BY df.tablespace_name,df.bytes
UNION ALL
SELECT /* + RULE */ df.tablespace_name tspace,
       fs.bytes / (1024 * 1024),
       SUM(df.bytes_free) / (1024 * 1024),
       Nvl(Round((SUM(fs.bytes) - df.bytes_used) * 100 / fs.bytes), 1),
       Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes)
FROM dba_temp_files fs,
       (SELECT tablespace_name,bytes_free,bytes_used
          FROM v$temp_space_header
         GROUP BY tablespace_name,bytes_free,bytes_used) df
WHERE fs.tablespace_name = df.tablespace_name
GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_used
ORDER BY 4 DESC;
set lines 1000
col FILE_NAME format a60
SELECT SUBSTR (df.NAME, 1, 60) file_name, df.bytes / 1024 / 1024 allocated_mb,
((df.bytes / 1024 / 1024) - NVL (SUM (dfs.bytes) / 1024 / 1024, 0))
used_mb,
NVL (SUM (dfs.bytes) / 1024 / 1024, 0) free_space_mb
FROM v$datafile df, dba_free_space dfs
WHERE df.file# = dfs.file_id(+)
GROUP BY dfs.file_id, df.NAME, df.file#, df.bytes
ORDER BY file_name;
Tablespace                      Size (MB) Free (MB)     % Free     % Used
DWH_TX_DWH_DATA                     11456       8298         72         28
FILE_NAME                                                    ALLOCATED_MB    USED_MB FREE_SPACE_MB
/data1/FPDIAV1B/dwh_tx_dwh_data1.dbf                                 1216       1216             0
/data1/FPDIAV1B/dwh_tx_dwh_data2.dbf                                10240       1942          8298
SQL> alter database datafile '/data1/FPDIAV1B/dwh_tx_dwh_data2.dbf' resize 5G;
alter database datafile '/data1/FPDIAV1B/dwh_tx_dwh_data2.dbf' resize 5G
ERROR at line 1:
ORA-03297: file contains used data beyond requested RESIZE value
Although , we did moved the tables into another TB , but it doesn't resolve the problem unless we take export and drop the tablespace aand again import it .We also used space adviser but in vain .
As far as metrics and measurement is concerned , as per my experience its based on blocks which is sparse in nature related to HWM in the tablespace.
when it comes to partitions , just to remove fragmentation by moving their partitions doesn't help .
Apart from that much has been written about it by Oracle Guru like you .
warm regards
Shivendra Narain Nirala
how does free space differ from fragmented space?
is all free space considered by you to be fragmented?
"num_rows*avg_row_len" provides useful result only if statistics are current & accurate.

Query to find which past ses caused ORA-1652: unable to extend temp segment

Hi,
I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
I have generated the AWR report but not able to figure it out which sessions caused this error.
Thanks in advance

913410 wrote:
Hi,
I m trying to get information on the sessions/sql query that have cause ORA-1652: unable to extend temp segment from past 2 days. Basically need to know which all sessions in past 2 days have caused ORA-1652: unable to extend temp segment.
I have generated the AWR report but not able to figure it out which sessions caused this error.
Thanks in advance
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
// a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
// files to the tablespace indicated.

How to find which query ORA-1652: unable to extend temp segment by 128 in

How can i find which query caused the below error,the query is not running currently
ORACLE ERRORS IN ALERTS LOG dnb2stg3 - lnx300 on Thu Jun 17 12:10:01 EDT 2010
1 ORA-1652: unable to extend temp segment by 128 in tablespace TEMP_SCHED
SQL> select inst_id, tablespace_name, total_blocks, used_blocks, free_blocks from gv$sort_segment;
INST_ID TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS
1 TEMP 638336 0 638336
4 TEMP 565760 0 565760
4 TEMP_SCHED 16776704 0 16776704
3 TEMP 484864 0 484864
3 TEMP_SCHED 0 0 0
2 TEMP 455808 0 455808
6 rows selected.
SQL> SQL> SELECT S.sid || ',' || S.serial# sid_serial, S.username,
2 T.blocks * TBS.block_size / 1024 / 1024 mb_used, T.tablespace,
3 T.sqladdr address, Q.hash_value, Q.sql_text
FROM v$sort_usage T, gv$session S, gv$sqlarea Q, dba_tablespaces TBS
4 5 WHERE T.session_addr = S.saddr
6 AND T.sqladdr = Q.address (+)
7 AND T.tablespace = TBS.tablespace_name
8 ORDER BY S.sid;
no rows selected

Hello,
You may try to catch the SQL with a Servererror Trigger.
This link will give you an interesting example:
http://oratips-ddf.blogspot.com/2008/09/to-err-is-human.html
Hope this help.
Best regards,
Jean-Valentin

Unable to extend index name of the index by 8 in tablespace

Hello,
I am not a DBA and do not have much experience in Oracle. When I was trying to restore the backup of my application, I received the following error. I could not able to proceed further in my tasks.
ORA-01654: unable to extend index <name of the index> by 8 in tablespace <name of the Index tablespace>The following query was used to create the table space. Oracle version is 10g.
CREATE TABLESPACE TS_JIRA
DATAFILE 'D:\oracle\product\10.2.0\oradata\jiraadmi\TS_JIRA.dbf' SIZE 100M REUSE
AUTOEXTEND ON NEXT 10M MAXSIZE 200M
MINIMUM EXTENT 64K
DEFAULT STORAGE ( INITIAL 64K NEXT 64K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0);I do not know how to extend the size of the tablespace. Can anyone help to sort out this issue?
Thanks in advance
Ram

Hi Ram;
I suggest also review below doc for your future issue
TROUBLESHOOTING GUIDE (TSG) - UNABLE TO CREATE / EXTEND Errors [ID 1025288.6]
Overview Of ORA-01654: Unable To Extend Index %s.%s By %s In Tablespace %s [ID 146595.1]
OERR: ORA 1654 unable to extend index <name.name> by <num> for tablespace <nam [ID 19049.1]
I belive they will answer all your question ;)
PS:Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Unable to extend table space

Hi,
I am unable to extend the tablespace in oracle, and also all DBA jobs are failing like CHECKDB AND UPDATE STATISTICS.
When i run BRTOOLS with ora<SID> user on unix,
it gives the below error.
" BR1049W Not enough free space in /oracle/DEV/sapdata/sapdata2/sr3_35 for total maximum size of all database files of tablespace PSAPSR3 located on this disk volume, missing at least 151532.475 MB "
Pls see the file system size below
Filesystem             size   used avail capacity Mounted on
/dev/md/dsk/d6          20G    20M    19G     1%    /oracle/DEV/saparch
/dev/md/dsk/d7         281M   118M   135M    47%    /oracle/DEV/origlogA
/dev/md/dsk/d9         281M   101M   151M    41%    /oracle/DEV/mirrlogA
/dev/md/dsk/d8         281M   118M   135M    47%    /oracle/DEV/origlogB
/dev/md/dsk/d10        281M   101M   151M    41%    /oracle/DEV/mirrlogB
/dev/md/dsk/d11        319G   203G   112G    65%    /oracle/DEV/sapdata
pls advise.
Regards
Irfan

Hi Eric
Thank you for your reply
I executed the command mentioned by you,
then i selected the option 5 which is RESIZE DATA FILE
Then i selected the datafile .
below is the next screen, where MAXIMUM FILE IS 10 GB
1 * Current data file status (status) ....... [AUTOEXTEND]
2 * Current data file size in MB (currsize) . [2000]
3 * Alter data file action (action) ......... [resize]
4 # Maximum file size in MB (maxsize) ....... [10000]
5 # File increment size in MB (incrsize) .... [20]
6 ? New data file size in MB (size) ......... []
7 # New data file name (name) ............... []
8 # Force data file alter (force) ........... [no]
9 - SQL command (command) ................... [alter database datafile 'E:\ORAC
LE\DMP\SAPDATA1\SR3_1\SR3.DATA1' resize M]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
please let me know do i need to select the option 4 and reduce the maxsize from 10 GB to 5 GB.
Regards,
Irfan

ORA-01653: unable to extend table SYS.SOURCE$ by 64 in tablespace SYSTEM"

Hi,
While creating a package the , I got the following error.
"ORA-00604: error occurred at recursive SQL level 1
ORA-01653: unable to extend table SYS.SOURCE$ by 64 in tablespace SYSTEM"
Could anyone please explain, how to solve this problem.
Thank you,
Regards,
Gowtham Sen.

solution: increase the size of the system tablespace.
the text of all pl/sql objects is stored in the database by sys. packages, procedures, and functions are stored in sys.source$ (which is part of the USER_SOURCE view definition). so, you've created a lot of pl/sql, and the table wants to extend, but there isn't room.
this is a major problem, because it means that nothing in system can extend. add another datafile, or put the tablespace on autoextend.

ORA-01654: unable to extend index user.index_x by 16 in tablespace tablespa

Hi all,
I get the error message : ORA-01654: unable to extend index user.index_x by 16 in tablespace tablespace_t after an insert into table table_x(having the index index_x ).
Could you please help me ? Should I add new datafile? Is there any other solution
I have get this message before, I have added new datafile to this tablespace,
ALTER TABLESPACE tablespace_t ADD DATAFILE 'C:\APP\...\ORADATA\MABASE\S_TAB_user02.DBF' SIZE 500M
AUTOEXTEND ON NEXT 100M MAX SIZE 1000M;
TABLESPACE_NAME ALLOUE OCCUPE LIBRE
1 tablespace_t 5720 5421 297

i think that would work.. And also if the error still persists then you have to tune the queries which are cost effective..For that you have to wait until you get the same error after addition of the datafile..Cheers!

Unable to Extend the Tablespace in BW Production Server

Hello Gurus,
I am unable to extend the tablespace - PSAPODSD in our BW production server.
While extending it throws this error
BR1052E File odsd.data53 is already used by the database - this can cause problems in backups
I am attaching the log for your reference
Options for extension of tablespace PSAPODSD (1. file)
1 * Last added file name (lastfile) ....... [/oracle/PBW/sapdata3/odsd_52/odsd.data52]
2 * Last added file size in MB (lastsize) . [2000]
3 - New file to be added (file) ........... [/oracle/PBW/sapdata2/odsd_53/odsd.data53]
4 ~ Raw disk / link target (rawlink) ...... []
5 - Size of the new file in MB (size) ..... [2000]
6 - File autoextend mode (autoextend) ..... [no]
7 # Maximum file size in MB (maxsize) ..... []
8 # File increment size in MB (incrsize) .. []
9 - SQL command (command) ................. [alter tablespace PSAPODSD add datafile '/oracle/PBW/sapdata2/odsd_53/odsd.data53' size 2000M autoextend off]
Standard keys: c - cont, b - back, s - stop, r - refr, h - help
BR0662I Enter your choice:
BR0280I BRSPACE time stamp: 2009-05-04 07.32.04
BR0663I Your choice: 'c'
BR0259I Program execution will be continued...
BR1052E File odsd.data53 is already used by the database - this can cause problems in backups
BR0669I Cannot continue due to previous warnings or errors - you can go back to repeat the last action
BR0280I BRSPACE time stamp: 2009-05-04 07.32.04
BR0671I Enter 'b[ack]' to go back, 's[top]' to abort:
BR0280I BRSPACE time stamp: 2009-05-04 07.32.10
BR0257I Your reply: 'b'
BR0673I Going back to the previous menu...
Please guide us to resolve this issue .
Imp - backup is completed successfully, I checked through sqlplus V$backup there is no active files
Thanks & Regards
Shishir

Hi,
login as ora<SID> and run this
sqlplus "/as sysdba"
sql> select FILE_NAME from dba_data_files where TABLESPACE_NAME='PSAPODSD';
This will show the list of the files located at os level and check whether the "odsd.data53" is present in which sapdata*. If this exist then add a new datafile.
Thanks
Arun

ORA-01654: unable to extend index BNE.BNE_CONTENT_COLS_B_UK2 by 15 in table

Dear Gurus:
Following workers fail during upgrade from 11.5.10 to 12.1.1, i am u6678700.drv :
ATTENTION: All workers either have failed or are waiting:
FAILED: file pqpzzossempintg.ldt on worker 1.
FAILED: file pqpzzflxcnt.ldt on worker 2.
FAILED: file pqpzzflxmap.ldt on worker 3.
FAILED: file pqpzzossempmap.ldt on worker 4.
Adworker Log file Details:
Loading data using FNDLOAD function.
FNDLOAD APPS/***** 0 Y UPLOAD @BNE:patch/115/import/bnecont.lct @PQP:patch/115/import/US/pqpzzflxcnt.ldt -
Connecting to APPS......Connected successfully.
Calling FNDLOAD function.
Returned from FNDLOAD function.
Log file: /data/oracle/PRD/apps/apps_st/appl/admin/PRD/log/US_pqpzzflxcnt_ldt.log
Error calling FNDLOAD function.
Time when worker failed: Sat Oct 17 2009 16:53:51
Now i have alos checked the US_pqpzzflxcnt_ldt.log details are mention below:
Current system time is Sat Oct 17 14:39:52 2009
Uploading from the data file /data/oracle/PRD/apps/apps_st/appl/pqp/12.0.0/patch/115/import/US/pqpzzflxcnt.ldt
Altering database NLS_LANGUAGE environment to AMERICAN
Dumping from LCT/LDT files (/data/oracle/PRD/apps/apps_st/appl/bne/12.0.0/patch/115/import/bnecont.lct(120.0), /data/oracle/PRD/apps/apps_st/appl/pqp/12.0.0/patch/115/import/US/pqpzzflxcnt.ldt) to staging tables
Dumping LCT file /data/oracle/PRD/apps/apps_st/appl/bne/12.0.0/patch/115/import/bnecont.lct(120.0) into FND_SEED_STAGE_CONFIG
Dumping LDT file /data/oracle/PRD/apps/apps_st/appl/pqp/12.0.0/patch/115/import/US/pqpzzflxcnt.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (BNE_CONTENTS PQP PQP_FLEXI_WEBADI_CNT , BNE_CONTENT_COLS 286 ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables
Error loading seed data for BNE_CONTENT_COLS: CONTENT_ASN = PQP, CONTENT_CODE = PQP_FLEXI_WEBADI_CSV_CNT, SEQUENCE_NUM = 26, ORA-01654: unable to extend index BNE.BNE_CONTENT_COLS_B_UK2 by 15 in tablespace BNEX
ORA-06512: at "APPS.BNE_CONTENT_COLS_PKG", line 25
ORA-06512: at "APPS.BNE_CONTENT_COLS_PKG", line 441
ORA-01403: no data found
Concurrent request completed
Current system time is Sat Oct 17 14:39:53 2009
After looking at the error i did the following:
alter database datafile '/data/oracle/prddata/benx01.dbf' resize 2G;
alter database datafile '/data/oracle/prddata/benx01.dbf' autoextend on next 100m maxsize 3G;
ALTER TABLESPACE BENX ADD DATAFILE '/data/oracle/prddata/benx02.dbf' size 500m AUTOEXTEND ON;
But still the issue remains, please help in resolving the same
Thanks & Regards
Kiran Rana

Dear Guru,
Followed both the documents which i have already followed, but no much of use as following query alos does not return any rows:
select segment_name, owner, extents, max_extents
from dba_segments
where segment_type = 'INDEX' and
(extents +1) >= max_extents;
Any other thing which i need to check
Regards
Kiran Rana

ORA-01652 unable to extend temp segment in 11gR2 with ASM and 2 node RAC

Hi ,
I have a 11.2.0.1 system with 2 node RAC and ASM . We are hitting ORA-01652 very frequently
and I can see space is available in TEMP .
CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
SIZE 21474836480,
SIZE 137437904896
AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M ( Will the next size ignored as the extent size is 1MB ?)
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
And during the failure
SELECT tablespace_name,
total_blocks,
used_blocks,
free_blocks,
total_blocks*32768/1024/1024 as total_MB,
used_blocks*32768/1024/1024 as used_MB,
free_blocks*32768/1024/1024 as free_MB
FROM gv$sort_segment;
TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB
TEMP 4849568 2385728 2463840 151549 74554 76995
TEMP 0 0 0 0 0 0
Also when I checked from v$sort_usage I see only two session consuming space
SQL> SELECT b.tablespace tablespace,
2 -- b.segfile#,
3 -- b.segblk#,
4 b.blocks,
5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
6 a.sid,
7 a.username username,
8 a.osuser osuser,
9 a.inst_id,a.sid,a.serial#,a.module
10 FROM gv$session a, gv$sort_usage b
11 WHERE a.saddr = b.session_addr and
12 b.blocks != 16 and
13 a.inst_id = b.inst_id
14 ORDER BY b.tablespace, b.blocks, bytes desc;
BLOCKS BYTES SID USERNAME OSUSER INST_ID SID SERIAL# MODULE
1,192,864 37277 381 CN obiqb 2 381 860 nqsserver@icmqapp01cdp (TNS V1
1,192,864 37277 3952 CN obiqb 2 3952 1374 nqsserver@icmqapp01cdp (TNS V1
2,385,728 74554 (mb)
Wat is causing the 1652 ?

877394 wrote:
Thanks Srini,
But I did try all that notes with no luck .
I have a temporary tablespace with 150gb (130+20) datafiles .
TABLESPACE_NAME FILE_NAME (BYTES/1024/1024)
TEMP +DATA_01/tempfile/temp.314.743964            131071
TEMP +DATA_01/tempfile/temp.312.757303             20480
and the DDL is
CREATE TEMPORARY TABLESPACE "TEMP" TEMPFILE
SIZE 21474836480,
SIZE 137437904896
AUTOEXTEND ON NEXT 655360 MAXSIZE 131071M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576
And on querying v$sort_usage
SQL> SELECT b.tablespace tablespace,
2 -- b.segfile#,
3 -- b.segblk#,
4 b.blocks,
5 b.blocks * (SELECT value FROM v$parameter WHERE name = 'db_block_size')/1024/1024 bytes,
6 a.sid,
7 a.username username,
8 a.osuser osuser,
9 a.inst_id,a.sid,a.serial#,a.module
10 FROM gv$session a, gv$sort_usage b
11 WHERE a.saddr = b.session_addr and
12 b.blocks != 16 and
13 a.inst_id = b.inst_id
14 ORDER BY b.tablespace, b.blocks, bytes desc;
TABLESPACE BLOCKS BYTES SID OSUSER INST_ID SID SERIAL# MODULE
TEMP 63,328 1,979 3952 CN 2 3952 1374
TEMP 84,384 2,637 381 CN 2 381 860
TEMP 433,184 13,537 381 CN 2 381 860
TEMP 1,117,728 34,929 3952 CN 2 3952 1374
sum 1,698,624 53,082 (mb)
So the space utilization was less than 150gb and on querying v$sort_Segment
SQL> SELECT tablespace_name,
total_blocks,
used_blocks,
free_blocks,
total_blocks*32768/1024/1024 as total_MB,
used_blocks*32768/1024/1024 as used_MB,
free_blocks*32768/1024/1024 as free_MB
FROM gv$sort_segment;
TABLESPACE_NAME TOTAL_BLOCKS USED_BLOCKS FREE_BLOCKS TOTAL_MB USED_MB FREE_MB inst
TEMP 4849568 2311104 2538464 151549 72222 79327 2
TEMP 0 0 0 0 0 0 1
why for inst 1 it is showing 0 (which means no sort is happening in instance 1)
But still we got the error
ORA-1652: unable to extend temp segment by 32 in tablespace TEMP
01652, 00000, "unable to extend temp segment by %s in tablespace %s"
// *Cause: Failed to allocate an extent of the required number of blocks for
//          a temporary segment in the tablespace indicated.
// *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
//          files to the tablespace indicated.

Unable to extend table in tablespace

Hi,
I have a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
I'm receiving the unable to extend table T_DATA in tablespace USER
I'm using ASM.
This is the situation of datafiles of USER tablespace (dimension is in GB):
+DATA/evodb/datafile/users.277.737627613     USERS     9,97265625
+DATA/evodb/datafile/users.275.731805999     USERS     60,97265625
+DATA/evodb/datafile/users.261.662113927     USERS     63,999969482421875
+DATA/evodb/datafile/users.264.705345395     USERS     63,999969482421875
+DATA/evodb/datafile/users.265.698502565     USERS     63,999969482421875
+DATA/evodb/datafile/users.268.718788313     USERS     63,999969482421875
It seems I still have 2 datafile that can grow (maximium size is 63,999969482421875)
This is the situation of DATA group (the one to which USER tablespace belongs):
Group # | Name | Free_mb | Usable_file_mb | total_mb
2     DATA     300051     300051     1134809
And this is the situation of every device belonging to DATA diskgroup:
Path | disk_number | group_name | group_number | header_status| free_mb | os_mb | total_mb
/dev/asm212     13     DATA     2     MEMBER     56627     208500     208500
/dev/asm9     7     DATA     2     MEMBER     12607     48127     48127
/dev/asm6     4     DATA     2     MEMBER     12600     48127     48127
/dev/asm8     6     DATA     2     MEMBER     12595     48127     48127
/dev/asm11     9     DATA     2     MEMBER     13315     51199     51199
/dev/asm211     11     DATA     2     MEMBER     56555     208500     208500
/dev/asm5     3     DATA     2     MEMBER     12611     48127     48127
/dev/asm3     1     DATA     2     MEMBER     12614     48127     48127
/dev/asm12     10     DATA     2     MEMBER     0     5115     5115
/dev/asm7     5     DATA     2     MEMBER     12584     48127     48127
/dev/asm213     12     DATA     2     MEMBER     60138     228352     228352
/dev/asm4     2     DATA     2     MEMBER     12608     48127     48127
/dev/asm10     8     DATA     2     MEMBER     12598     48127     48127
/dev/asm2     0     DATA     2     MEMBER     12599     48127     48127
Why table cannot extend??
And more:
if I try to add a datafile to USER tablespace, I got:
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15041: diskgroup space exhausted
01119. 00000 - "error in creating database file '%s'"
Any suggestion??
thanks in advance,
Samuel

OK, but what does FREE_MB mean?
Is it the unallocated space?
Is it possible that this disk:
path | disk_number | group_name | group_number | header_status| free_mb | os_mb | total_mb
/dev/asm12 10 DATA 2 MEMBER 0 5115 5115
is causing the error?
Does it make sense to try to remove it from the diskgroup? I should have more than enough space on other disks of the DATA diskgroup.
Edited by: Samuel Rabini on Jan 12, 2011 6:14 PM

Unable to extend temp segment

Hi All,
I received the following error;
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP2
Then I added the datafile in temp2 tablespace.
But still it giving the same error;
Syntax of Create tablespace is
Create temporary tablespace temp2
Datafile \temp_01.dbf size 500m;
Table contains 100000 records;
Please help me.
Thanks and regards,
Prathamesh.

Please check the allocation and deallocation of space in a temporary tablespace sort segment using the V$SORT_SEGMENT view. The V$TEMPSEG_USAGE view identifies the current sort users in those segments.
Also, check settings of TEMP tablespace. May be it's trying to create a huge extent as NEXT (larger than available space), which is not required. In that case reduce NEXT EXTENT for this.

ORA-1653: unable to extend table PERFSTAT.STATS

Hi there,
I know it's Friday and by the end of the week we normally are not that alert anymore.
However now we have a very puzzling problem, one that leaves two DBA's very amazed.
This morning our alert-log of a 9.2.0.8 database on AIX 5.3 showed:
ORA-1653: unable to extend table PERFSTAT.STATS in tablespace TOOLSEasy, one would say. Extend the tablespace and you're done.
However the tablespace is on autoextend, not even mentioned that it has 2.5Gb of free space.
It is also "Locally Managed", with uniform extent size of 16Kb and manual "segment space management"
The index of this table is in the same tablespace.
The storage parameters are set to "unlimited" possibilities.
A manual
exec statspack.snapresults in the same error where as a
create table statstest as select * from stats$sqltext ; works fine. The mentioned source table here is the one which seems unable to extend due to the "tablespace restrictions"
Some storage parameters:
CREATE TABLE "PERFSTAT"."STATS$SQLTEXT" (
"HASH_VALUE" NUMBER NOT NULL ENABLE,
"TEXT_SUBSET" VARCHAR2 (31) NOT NULL ENABLE,
"PIECE" NUMBER NOT NULL ENABLE,
"SQL_TEXT" VARCHAR2 (64),
"ADDRESS" RAW (8),
"COMMAND_TYPE" NUMBER,
"LAST_SNAP_ID" NUMBER,
CONSTRAINT "STATS$SQLTEXT_PK" PRIMARY KEY
("HASH_VALUE", "TEXT_SUBSET", "PIECE
USING INDEX
PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE
INITIAL 1048576
NEXT 1048576
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT
) TABLESPACE "TOOLS"
ENABLE
PCTFREE 5
PCTUSED 40
INITRANS 1
MAXTRANS 255
NOCOMPRESS
LOGGING
STORAGE (INITIAL 5242880
NEXT 5242880
MINEXTENTS 1
MAXEXTENTS 2147483645
PCTINCREASE 0
FREELISTS 1
FREELIST GROUPS 1
BUFFER_POOL DEFAULT)
TABLESPACE "TOOLS"Can this be some kind of Data Dictionairy corruption ??

virendra.k wrote:
The next extent clause in creation script says that it is required to have at least 1G of contiguous memory. But the satement fails which means that a chunk of this size cannot be allocated. The situation may arise due to fragmentation of tablespace. See metalink doc id [1020182.6|https://metalink2.oracle.com/metalink/plsql/f?p=130:14:9000433346754441541::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,1020182.6,1,0,1,helvetica] if the largest free chunk >= 1G. Other wise increase the size of tablespace. It may help you.
I don't understand the result of 1G you calculated.
I only see: NEXT 1048576 of the primary key, which is 1M and NEXT 5242880 ( 5M) of the table itself.
However it the Note lead me to the solution.
The largest piece of contiguous free space in the tablespace is, according to this Note:
TABLESPACE NAME CONTIGUOUS BYTES
TOOLS 3,407,872 ==> 3Mb
TOOLS 3,407,872
TOOLS 3,407,872
TOOLS 3,301,376
TOOLS 3,194,880
TOOLS 3,194,880
TOOLS 3,194,880
TOOLS 3,194,880
TOOLS 3,088,384
So I executed the following:
SQL> alter table stats$sqltext storage (next 1m);And subsequently:
SQL> exec statspack.snap;Which now succeeds !!
Conclusion: Tablespace REORG needs to be planned.
One more strange thing however:
I altered the NEXT_EXTENT size back to 5M, and again the statspack.snap now works OK.
It must be the either a background COALESCE that solved the problem, or the (maybe existing) corruption in the dictionary is now fixed/gone
Thanks for the assistance

Unable to extend datafile which is autoextend on.

Similar Messages

Maybe you are looking for