ORA-1688: UNABLE TO EXTEND TABLE IN SYSAUX TABLESPACE

Hi,
We are running oracle10g R-2 (10.2.0.2.0) on solaris 10.
In our alert log file we get following message interminantely:-
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition
WRH$_
ACTIVE_455891297_399 by 128 in tablespace SYSAUX
MMON Flush encountered SYSAUX out of space error(1688).
MMON (emergency) purge of WR snapshots (243) and older
The above error reproduce after every 1 hour.
Thanks & Regards
Rishikesh

It seems your tablespace SYSAUX to be little: you need to make it bigger or add another datafile. Using "Oracle Enterprise Manager" is quite easy to do, in section "Storage Manager".

Similar Messages

ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY

Hi,
In the alert log file it is occuring below error on some interval.The database version is 10.2.0.4.0.
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_
ACTIVE_506486335_9939 by 128 in tablespace SYSAUX
Thanks,
Quadri
Edited by: Quadri on Feb 6, 2010 6:52 AM

Hello,
You wrote:
Can i delete some rows to release the space from the SYS.WRH$_ACTIVE_SESSION_HISTORY table?To purge the Table SYS.WRH$_ACTIVE_SESSION_HISTORY, you may first query the Snapshot History
with the query below:
select snap_id, begin_interval_time from sys.dba_hist_snapshot order by snap_id;Then, you choose the range of snapshot you want to delete, and you execute the following Procedure:
exec dbms_workload_repository.drop_snapshot_range ( low_snap_id => snap_id_1, high_snap_id=> snap_id_2 );But, if the delete will free space inside the Table, it won't release space to the SYSAUX Tablespace.
You wrote:
For system tablespace can i add or resize the datafile if it needs?Yes as any Tablespace. But your error message was on the Tablespace SYSAUX. So this is the reason why it
was not necessary to extend the Tablespace SYSTEM.
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Feb 6, 2010 6:33 PM

ORA-1688: unable to extend table SYS.WRH

Hi,
on 10g R2 I have following error in alertlog :
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3192442214_8801 by 128 in tablespace SYSAUX
here :
I found :
BEGIN
DBMS_WORKLOAD_REPOSITORY.DROP_SNAPSHOT_RANGE (low_snap_id => 22,
high_snap_id => 32, dbid => 3310949047);
END;
Should wxe do it regularly ? Oracle does'nt it regularly ? In DB control can we drop the snapshots ?
Any other suggestion for ORA-1688: unable to extend table SYS.WRH error ?
Thank you.

user522961 wrote:
Hi,
on 10g R2 I have following error in alertlog :
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3192442214_8801 by 128 in tablespace SYSAUX
here :
I found :
BEGIN
DBMS_WORKLOAD_REPOSITORY.DROP_SNAPSHOT_RANGE (low_snap_id => 22,
high_snap_id => 32, dbid => 3310949047);
END;
Should wxe do it regularly ? Oracle does'nt it regularly ? In DB control can we drop the snapshots ?
Any other suggestion for ORA-1688: unable to extend table SYS.WRH error ?
Thank you.Why are you starting a duplicate thread from one you started 7+ hours earlier?
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY

ORA-1653: unable to extend table ABC in tablespace APPS_TS_TX_DATA

Facing problem
ORA-1653: unable to extend table ABC in tablespace APPS_TS_TX_DATA
Searched many forums but no particular update

Pl do not post duplicates - Which table belong to which table

ORA-1653 (unable to extend table) and ORA-1654 (unable to extend index)

Hi,
We recently installed 12c.r1 and have it running now form some three weeks. About 100 assets currently in it.
When trying to add a new discovery profile a received an error message from the BUI, in the cacao log from the EC i found a lot java exceptions caused (probably by : Internal Exception: java.sql.SQLException: ORA-01653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS)
When looking at the alert log from the database i found its full with ORA-1653 and ORA-1654 messages; (and still those errors are being put in the alert logfile on a continues basis.)
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.VDO_SERVICE_INFO by 128 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.VDO_SERVICE_INFO by 128 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
And
ORA-1654: unable to extend index OC.VMB_RESOURC_ASSOCIA_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VMB_RESOURC_ASSOCIA_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VMB_RESOURC_ASSOCIA_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VMB_RESOURCE_CAPABIL1_UNQIDX by 128 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VMB_RESOURCE_CAPABIL1_UNQIDX by 128 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VMB_RESOURCE_CAPABIL1_UNQIDX by 128 in tablespace OC_DEFAULT_TS
Only thing i could think of would be a space issue in the filesystem. But there's still some 15G of free space available for the DB to extend.
Any clues as to where to find the cause of this?
Thanks in advance
Kind regards
Patrick

Hi,
Sorry for the late response (wasn't in the office last week)
I'v extended the zpool with additional LUN's , now there is 168GB of free space (total DB size now 42GB) so, efficient free space should be available. After a restart of the DB unfortunately again the alert file is flooded with ORA-1653 / 64 messages on a continues basis;
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_ALERT_MONITOR_ST1_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_ALERT_MONITOR_ST1_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
Mon Jul 16 13:56:46 2012
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
Mon Jul 16 13:56:55 2012
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
ORA-1654: unable to extend index OC.VDO_SENSOR_INFO_ID_UNQIDX by 8 in tablespace OC_DEFAULT_TS
Mon Jul 16 13:57:02 2012
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
ORA-1653: unable to extend table OC.PERSISTENTALERT by 8 in tablespace OC_DEFAULT_TS
etc,.....etc,......etc,.....
Unsure what to do.
Check the PCT_USED with a script and found;
NAME MBYTES USED FREE PCT_USED LARGEST MAX_SIZE PCT_MAX_USED EXTENT_MAN SEGMEN
USERS 5 1.31 3.69 26.25 3.69 32767.98 0 LOCAL AUTO
OC_INDEX_TS 100 1 99 1 99 32767 0 LOCAL AUTO
OC_DATA_TS 100 1 99 1 99 32767 0 LOCAL AUTO
TEMP 174 174 0 100 0 32767.98 .53 LOCAL MANUAL
SYSTEM 720 711.31 8.69 98.79 8 32767.98 2.17 LOCAL MANUAL
SYSAUX 1230 1148.44 81.56 93.37 64.44 32767.98 3.5 LOCAL AUTO
UNDOTBS1 7625 445.75 7179.25 5.85 3656 32767.98 1.36 LOCAL MANUAL
OC_DEFAULT_TS 32767 32767 0 100 0 32767 100 LOCAL AUTO
8 rows selected.
Seems the OC_DEFAULT_TS is 100% full.
Shouldn't this autoextend?!?
I'm no DBA, and the OPCenter installation is default 'out-of-the-box' on a new system. Only running for a month now with about 100 assets.
Any help appreciated
Thanks
Patrick
Edited by: Patrick on Jul 16, 2012 3:13 PM
Edited by: Patrick on Jul 16, 2012 3:15 PM

ORA-1653: unable to extend table DEV_ADS.ADS_ATTRIBUTES by 128 in tablespace DEV_ADS

Hi All,
Oracle 11.2.0.3
redhat 6.4
I got these errors for datafile even though the autoextend is on & ample space available on hard disk,
ORA-1653: unable to extend table DEV_ADS.ADS_ATTRIBUTES by 128 in tablespace DEV_ADS
ORA-1653: unable to extend table DEV_ADS.ADS_ATTRIBUTES by 1024 in tablespace DEV_ADS
The Maxbytes for this datafile is 1gb & current size is 100m but it gave error after reacing 100m, i added another datafile to this but i couldnt understand why the autoextend fails
Tablespace Name                Total size Used Size Free space     %free       %used
SYSAUX                                700        662         38          5         94
UNDOTBS1                             755         27        728         96          3
INTG_AIM_LOB                       500         67        433         86         13
USERS                                   5          2               3         60         40
DEV_ADS                             1100        302        798         72         27
The usage after adding another datafile is 302 mb then why it cannot autoextend for first datafile.

Thanks ,
ulimit -a is unlimited
The initial size of tablespace was 100m with autoextend max 1000m enabled.
Table ADS_ATTRIBUTES is created with following clauses
select INITIAL_EXTENT,NEXT_EXTENT from dba_segments where SEGMENT_NAME='ADS_ATTRIBUTES';
INITIAL_EXTENT NEXT_EXTENT
         65536     1048576
select EXTENTS,BLOCKS from dba_segments where SEGMENT_NAME='ADS_ATTRIBUTES';(This after adding one datafile)
   EXTENTS     BLOCKS
        38       2944
The initail extent is 64mb and values of next extent is 1024m.
So is that it gave me error for creating second extent of 1024m since maxsize datafile is 1g.Correct me if i am wrong

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.

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

ORA-01653: unable to extend table... problem

Hello.
I'm using Oracle 8i 8.1.5.0.2 SE on Adelinux 6.2(kinda localized version of RedHat 6.2).
When I run my Pro*C module, the following error message appeared even though there's enough free space on that tablespace.
ORA-01653: unable to extend table UALMAS.TBL_OPTIONS_T by 466608 in tablespace TALMAS
The free space of TALMAS tablespace is as follow:
--->> cut here <<---
SQL> SELECT TABLESPACE_NAME,BYTES FROM DBA_FREE_SPACE;
TABLESPACE_NAME BYTES
TALMAS 284839936
TALMAS 204271616
TALMAS 732184576
TALMAS 846002176
TALMAS 547749888
TALMAS 305330176
TALMAS 194267136
TALMAS 50661376
TALMAS 561453056
TALMAS 108539904
10 rows selected.
--->> cut here <<---
I use COMMIT at the end of some part of insertion, and the free space listed is not the result of rollback I think.
Does anyone have such an experience?
Can anyone tell me how to solve this problem?
Any comment would be appreciated.
@Wings... of Icarus
null

Hi,
Maxsize unlimited means the maxsize of 32GB. Check if your tablespace is reaching its maxsize, you may have to add a datafile to the tablespace. Sometime, maxfile is not reached but you do not enough disk in the file system to extend the tablespace. So check the file system utilization as well.
HTH

ORA-1653: unable to extend table

hi guys!
its the second time am posting this message! had this error in this alert.log
ORA-1653: unable to extend table APPLSYS.WF_LOCAL_ROLES_STAGE by 4849950 in tablespace APPLSYSD
the tablespace is APPLSYSD free_space 59390.4688M used_space 22495.7031M
initial extent 40960, next_extent 1048576, max_extent 2147483645 and pct_free is set to 0!
the tablespace contains three datafiles and their percentage used is 36%, 35% and 12%. I dont really understand how this error comes! how come in the error, it wants to extend by 4849950 while the value for next_extent is 1048576? could some one please help me overcome this problem??
Thanls

hi.
here are the output to some queries.
select initial_extent,next_extent, pct_increase from dba_tablespaces where tablespace_name='APPLSYSD'
INITIAL_EXTENT NEXT_EXTENT PCT_INCREASE
40960 40960 0
select initial_extent, next_extent, pct_free, pct_increase from dba_tables where owner='APPLSYS' and table_name=('WF_LOCAL_ROLES_STAGE')
INITIAL_EXTENT NEXT_EXTENT PCT_FREE PCT_INCREASE
40960 1048576 10 0
select table_name,NEXT_EXTENT,PCT_INCREASE from dba_tables where owner='APPLSYS' and table_name='WF_LOCAL_ROLES_STAGE';
TABLE_NAME NEXT_EXTENT PCT_INCREASE
WF_LOCAL_ROLES_STAGE 1048576 0
select OWNER,SEGMENT_NAME,NEXT_EXTENT,PCT_INCREASE,EXTENTS from dba_segments where owner='APPLSYS' and segment_name='WF_LOCAL_ROLES_STAGE';
OWNER SEGMENT_NAME NEXT_EXTENT PCT_INCREASE EXTENTS
APPLSYS WF_LOCAL_ROLES_STAGE 1048576 0 1

ORA-01653 unable to extend table.

Hi All,
I am Using oracle 9i on Windows XP box
I got the following error messages .
ORA-01653: unable to extend table SCOTT.EMP2 by 128 in tablespace ORADATA
I was inserting 557056 rows from emp table to emp2 table , by issuing
sql> insert into emp2 select * from emp ;
My emp2 table is in tablespace oradata which I created by issuing.
create tablespace oradata
datafile 'c:\oratemp\data01.dbf' size 20m
extent management local
autoallocate
segment space management auto
Please help me to explain why I got this error and how to solve this error.
Thanks.

Your ORADATA tablespace got filled, ang got no free space to accommodate new insertions.
So, resize the datafile of ORADATA tablespace using the following statement.
SQL> CONNECT /AS SYSDBA
SQL> ALTER DATABASE DATAFILE 'c:\oratemp\data01.dbf' RESIZE 100M;
Regards,
Sabdar Syed.

ORA-1653: unable to extend table (but tablespace is not full!)

Hi folks,
I was navigating through the Alert Log file and I'm strangely noticing the error:
ORA-1653: unable to extend table PROMO.DETAILS by 40973 in tablespace PROMO
I'm defining it as strange because:
(1) The tablespace is only 65% full (there are 750MB of freespace), and
(2) There is ample space on the harddisk
I then used TOAD to try to debug the problem and there is a tool which allows me to view a map of the tablespace. I could see that the tablespace "PROMO" had indeed freespace, but the table "DETAILS" looked like it had no space where to extend (there was a table both before, and after it in the map). Is there a way to solve this problem , or isn't a problem at all?

this problem occurs because
your table don't find one big free space for next extent in tablespace.
solutions:-
1st solution
* alter tablespace <tablespace_name> add datafile ' path';
OR
2nd solution
- coalesce your tablespace 'alter tablespace <tablespace name> coalesce'.
OR
3rd solution
check u r pctincrease parameter if it is 50 then
ALTER TABLE <tablename> STORAGE (NEXT 1M PCTINCREASE 0);
kuljeet pal singh

ORA-01653: unable to extend table DISPATCH.T_EVENT_DATA by 4096 in tablespa

Hello everybody,
I try to explain the problem I had, because I still didn't understand real causes.
Everything started when I got this error:
ORA-01653: unable to extend table DISPATCH.T_EVENT_DATA by 4096 in tablespace USERS
I'm using ASM.
This was the situation of the tablespace USER:
FILE NAME                                                 TB NAME   SIZE (gb)                   STATUS
DATA/evodb/datafile/users.261.662113927     USERS     63,999969482421875     AVAILABLE
and this was the situation of the DATAS diskgroup:
GR # NAME        FREE_MB    USABLE     STATE      SECTOR SIZE   BLOCKSIZE
2     DATA     60000     60000     MOUNTED     512     4096
That diskgroup is composed by 5 files:
PATH       DISK#       GR NAME           FREE MB    OS MB       TOTAL MB NAME                FAILGROUP
/dev/asm2     0     DATA          12000     48127     48127     DATA_0000     DATA_0000
/dev/asm3     1      DATA          12000     48127     48127     DATA_0001     DATA_0001
/dev/asm4     2     DATA          12000     48127     48127     DATA_0002     DATA_0002
/dev/asm5     3     DATA          12000     48127     48127     DATA_0003     DATA_0003
/dev/asm6     4     DATA          12000     48127     48127     DATA_0004     DATA_0004
This are the information about the table got from the dba_tables table:
OWNER     DISPATCH
TABLE_NAME     T_EVENT_DATA
TABLESPACE_NAME USERS
CLUSTER_NAME
IOT_NAME
STATUS     VALID
PCT_FREE     10
PCT_USED
INI_TRANS     1
MAX_TRANS     255
INITIAL_EXTENT     4294967296
NEXT_EXTENT
MIN_EXTENTS     1
MAX_EXTENTS     2147483645
PCT_INCREASE
FREELISTS
FREELIST_GROUPS
LOGGING     YES
BACKED_UP      N
NUM_ROWS     532239723
BLOCKS     1370957
EMPTY_BLOCKS     0
AVG_SPACE      0
CHAIN_CNT 0
AVG_ROW_LEN     32
AVG_SPACE_FREELIST_BLOCKS     0
NUM_FREELIST_BLOCKS     0
DEGREE     1
INSTANCES     1
CACHE     N
TABLE_LOCK     ENABLED
SAMPLE_SIZE     532239723
LAST_ANALYZED 21/09/2009 22.45
PARTITIONED     NO
IOT_TYPE
TEMPORARY     N
SECONDARY      N
NESTED     NO
BUFFER_POOL     DEFAULT
ROW_MOVEMENT DISABLED
GLOBAL_STATS     YES
USER_STATS     NO
DURATION
SKIP_CORRUPT     DISABLED
MONITORING     YES
CLUSTER_OWNER
DEPENDENCIES     DISABLED
COMPRESSION     DISABLED
COMPRESS_FOR
DROPPED      NO
READ_ONLY     NO
So, my question is:
Why did it happen?
Why the table was unable to allocate the space? From what I can see the space was there.
I alstro tried an ALTER TABLESPACE USER COALESCE, but with no luck.
To solve the problem, I had to create another tablespace and put there the T_EVENT_DATA table.
Looking forward to read some answer,
thanks in advance!

There can be two reasons:
1.) Datafile is unable to extend as the auto-extend is set to NO.
2.) Datafile reached to the MAXSIZE provided at the datafile creation.
Query dba_data_files view and confirm this.
Regards.

ORA-01653: unable to extend table MY_PROJECTS.TEST_TABLE by 8 in

Hi
I am getting the following error while submitting a form in Oracle Apex.
ORA-01653: unable to extend table MY_PROJECTS.TEST_TABLE by 8 in tablespace FLOW_2283
Error Unable to process row of table TEST_TABLE
Please help me.
Edited by: Umesh Chandra Moharana on Sep 22, 2008 10:28 AM
Edited by: Umesh Chandra Moharana on Sep 22, 2008 10:29 AM

Hi John,
Thanks for your quick reply. Our application is hosted on apex.oraclecorp.com. Since this is a internally used server, we are not sure whom we should be approaching for increasing the table space, or if there is any administrative tools available to increase the tablespace. I will really appreciate if you can guide in this regard.
Thanks,
Varkey (On Behalf of Umesh)

ORA-1653: unable to extend table APPLSYS.FND_LOG_MESSAGES by 128 in

ORA-1653: unable to extend table APPLSYS.FND_LOG_MESSAGES by 128 in tablespace FND_TAB
as this getting in alert log.........

Hi,
Please implement the solutions outlined in the following document.
Note: 743785.1 - How I resolved ORA-1653 on APPS_TS_TX_DATA tablespace
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=743785.1
Regards,
Hussein

ORA-1688: UNABLE TO EXTEND TABLE IN SYSAUX TABLESPACE

Similar Messages

Maybe you are looking for