ORA-1653

Dear all,
When inserting data into a particular table,am getting the below error :
ORA-1653: unable to extend table
When I checked,the tablespace has got maxsize unlimited and autoextend on and there is enough space avilable on the disk..
why is that still am getting this ORA-1653 error ?
DB : 10.2.0.4 Solaris 10
Kai
Edited by: KaiS on Sep 10, 2009 4:35 AM

KaiS,
It does mean
a few established facts
1 you never ever read any documentation. How do I know this? Because the analysis you posted doesn't belong to the problem.
You still didn't read the Concepts Manual!
2 You never ever look up error messages
3 You never ever do any research of your own
4 you just dump issues, and you don't post any information
5 When you need to answer a few viable questions, you refuse to do so, and you start biting the hand that nurtures you.
You are the excellent epitome of an incompetent, lazy and also rude wannabe DBA
Does that mean I don't know the answer?
How can I know the answer when you only post 'It doesn't work'?
How can I know the answer when you refuse (as that would require you to do work, something you really loathe to do) to answer the few questions I asked?
I am as smart as the poster asking a question.
When the poster is stupid, acts rude, and responds with a flame, I can not answer.
Heck, I should report you for consistent abuse of this forum!
And please, I will notice, when you start posting a new series of 'Hey, I can not be bothered to read the docs, kindly do the needful, URGENT' questions.
It is YOU who are the pest here. Not me. I help people out, you are only lazy, unhelpful and rude.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

More than 100 Mb space in tablespace but keeps having ORA-1653 unable to ex

Platform AIX 6.1
Oracle version 10.2.0.5.3
JOB_DET is a single table in one tablespace D_LGA1. It's space taken is 12096 Mb, the tablespace is capped at 12288 Mb, so technically it has 191 Mb free space.
13:06:55 SQL> select segment_name,tablespace_name,bytes/1024/1024 as mbytes
13:07:13   2 from dba_segments where segment_name='JOB_DET';
SEGMENT_NAME    TABLESPACE_NAME     MBYTES
JOB_DET         D_LGA1               12096
13:08:00 SQL> select tablespace_name, sum(bytes/1024/1024) as sum_mb,
sum(maxbytes/1024/1024) as sum_maxbytes_mb, AUTOEXTENSIBLE
from dba_data_files
where tablespace_name in ('D_LGA1') group by tablespace_name, autoextensible order by 1;
TABLESPACE_NAME     SUM_MB SUM_MAXBYTES_MB AUTOEXTEN
D_LGA1               12288           12288 YES
13:08:16 SQL> select tablespace_name, sum(bytes/1024/1024) as sum_free_mb
13:08:25   2 from dba_free_space where tablespace_name in ('D_LGA1')
13:08:32   3 group by tablespace_name order by 1;
TABLESPACE_NAME SUM_FREE_MB
D_LGA1             191.8125however I keep getting ORA-1653 in the alert log.
Thu Mar 08 13:09:54 TAIST 2012
ORA-1653: unable to extend table ADMIN.JOB_DET     by 128 in   tablespace D_LGA1
ORA-1653: unable to extend table ADMIN.JOB_DET     by 8192 in   tablespace D_LGA1
...OK, this is weird, but nevertheless, I added another datafile, which allows it to extend the size.
After which, the size of the segment JOB_DET is 12160 Mb, which was lesser than the original max size!! There doesnt seem to be any fragmentation going on there. I'm puzzled. Someone able to explain?
14:42:26 SQL> select segment_name,tablespace_name,bytes/1024/1024 as mbytes
14:42:28   2 from dba_segments where segment_name='JOB_DET';
SEGMENT_NAME    TABLESPACE_NAME     MBYTES
JOB_DET         D_LGA1               12160Edited by: len on Mar 8, 2012 3:05 PM

Hi sybrand,
would this help?
SQL> select * from dba_tables where table_name='JOB_DET';
OWNER      TABLE_NAME   TABLESPACE_NAME CLUSTER_NAME    IOT_NAME        STATUS     PCT_FREE   PCT_USED INI_TRANS
MAX_TRANS INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE FREELISTS FREELIST_GROUP
    BLOCKS EMPTY_BLOCKS AVG_SPACE CHAIN_CNT AVG_ROW_LEN AVG_SPACE_FREELIST_BLOCKS NUM_FREELIST_BLO
DEGREE                         INSTANCES                      CACHE           TABLE_LO SAMPLE_SIZE LAST_ANAL PAR
IOT_TYPE     T S NES BUFFER_ ROW_MOVE GLO USE DURATION        SKIP_COR MON CLUSTER_OWNER                  DEPENDEN
COMPRESS DRO
ADMIN       JOB_DET      D_LG06                                          VALID             5                     2
       255          65536     1048576           1 2147483645                                         YES N   51475345
   1531830            0          0          0         158                         0                   0
         1                              1                         N           ENABLED     51475345 10-FEB-12 NO
             N N NO DEFAULT DISABLED YES NO                  DISABLED YES                                DISABLED
DISABLED NO
SQL> select * from dba_free_space where tablespace_name='D_LGA1';
TABLESPACE_NAME    FILE_ID   BLOCK_ID      BYTES     BLOCKS RELATIVE_FNO
D_LGA1                  28     516100   67043328       8184           28
D_LGA1                  36     516105   67043328       8184           36
D_LGA1                  75       8201   37814272       4616           75
D_LGA1                 119     516105   67043328       8184          119
SQL> select * from dba_tablespaces where tablespace_name='D_LGA1';
TABLESPACE_NAME BLOCK_SIZE INITIAL_EXTENT NEXT_EXTENT MIN_EXTENTS MAX_EXTENTS PCT_INCREASE MIN_EXTLE
CONTENTS LOGGING   FOR EXTENT_MAN ALLOCATIO PLU SEGMEN DEF_TAB_ RETENTION   BIG
D_LGA1                8192          65536                       1 2147483645                   65536 ONLINE
PERMANENT LOGGING   NO LOCAL      SYSTEM    NO AUTO   DISABLED NOT APPLY   NOEach data file has roughly 64 Mb free space in them, the only way I can think it would result in ORA-1653 is if what the application was trying to insert/update far exceeds 64 Mb at one go?
This is my assumption, or am I out of the box already?

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.

SQL*LOADER 시 발생하는 ORA-1653 ERROR

제품 : SQL*PLUS
작성날짜 : 2002-04-25
SQL*LOADER 실행 시 발생하는 ORA-1653
====================================
PURPOSE
다음은 SQL*LOADER 실행시 ORA-1653 ERROR가 발생시에 조치하는
방법을 설명한다.
Explanation
ORA-1653 error 는 특정 tablespace 에 space 가 부족해서 table의
extent가 일어나지 못해서 발생하는 error 이다 .
먼저 error message 에서 tablespace name 이 무엇인지 먼저
check 한다.
그리고 다음 command 를 이용해 해당 tablespace 를 늘려주면 된다.
ALTER TABLESPACE tablespace_name ADD DATAFILE '.....' size 100m;
그러나 이때의 tablespace 가 SYSTEM 일 경우는 user 의 default
tablespace 가 잡혀있지 않기 때문이어서 근본적인 해결이 필요하다.
이 경우는 무작정 tablespsace 를 늘리지 말고 user 의 default
tablespace 를 create 후 user 에게 할당해주도록 한다.
CREATE TABLESPACE tablespace_name datafile '...' size 100m;
ALTER USER user_name IDENTIFIED BY passwd
DEFAULT TABLESPACE tablespace_name
TEMPORARY TABLESPACE temp ;
위와 같이 user의 default tablespace 를 변환한 후, 이 default
tablespace 안에 create table을 다시 한 후 sql*loader 를 실행한다.
Reference Documents
--------------------

Hi,
You must have more than one tnsnames file or multiple installations of oracle. What i suggest you do (as I'm sure will be mentioned in ed's link that you were already pointed at) is the following (* i assume you are on windows?)
open a command prompt
set TNS_ADMIN=PATH_TO_DIRECTOT_THAT_CONTAINS_CORRECT_TNSNAMES_FILE (i.e. something like set TNS_ADMIN=c:\oracle\network\admin)
This will tell oracle use the config files you find here and no others
then try sqlldr user/pass@db (in the same dos window)
see if that connects and let us know.
Cheers,
Harry
http://dbaharrison.blogspot.com

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-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-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 (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-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-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 SYS.TEST_MAIL by 128 ..

Hi guys,
Im trying to configure OEM on Windows to automatically sent out alert emails for event metrics,
but for some reason its not sending any after my setup.
Thu Aug 13 13:59:07 2009
ORA-1653: unable to extend table SYS.TEST_MAIL by 128 in tablespace TEST
Thanks in advance

TEST tablespace has run out of space.
You could either add more datafiles for TEST tablespace or turn on the autoextention for the files already part of TEST tablespace.
BTW, why are you creating objects as SYS?

SUB:ORA-1653: unable to extend table SYS.IDL_CHAR$ by 128 in TableSpace SYS

Hi Everybody,
I have installed my ORACLE software in a separate partition /oracle whith 3.3GB space
successfully.
Now i have free space 1GB in that Partition.
when i try to create NEW DB using DBCA it says it required around 500MB for DataFiles.
But while it was creating when it reaches 41% it was giving this error ORA-1653.
Even though when i have space in my oracle partition...why its running out of space???
when the DB creating was going on i open the Memory Monitor Utilities. There
physical Memory use almost 99%, Total Memory usage is 45%, Swap Space is just 14%.
MY RAM is 512MB.
Thanks In Advance
g.sanjeevi

Hi,
Your system tablespace is full
http://ora-01655.ora-code.com/
Contact your DBA
Regards,
Jari

ORA-00604,ORA-00600,ORA-1652,ORA-1653,ORA-00257 errors

Hi All,
I am getting the below alerts in my Oracle 9i database.
ORA-00604: error occurred at recursive SQL level 3
ORA-00600: internal error code, arguments: [kghpih:ds], [
ORA-1652: unable to extend temp segment by 128 in tablespace           TS_PHDB_5
ORA-1653: unable to extend table T49XPWM.TMP_PD_VALUES by 128 in           tablespace TS_PHDB_5
ORA-1652: unable to extend temp segment by 128 in tablespace           TS_PHDB_16
ORA-00257: archiver error. Connect internal only, until freed.
ORA-604 signalled during: ALTER DATABASE CLOSE NORMAL...
Saswat

This error does not necessarily indicate whether or not you have enough space
in the tablespace, it merely indicates that Oracle could not find a large enough area of free
contiguous space in which to fit the next extent.
add datafile to your table space.
Edited by: Asad99 on Apr 1, 2013 3:59 AM

ORA-1653 during upgrade db

Hello!
I see in alert.log during upgrade 10.2.0.5 -11.2.0.3
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEMShould I restart catupgrd.sql ?
Thanks and regards,
Pavel

Pavel wrote:
Hello!
I see in alert.log during upgrade 10.2.0.5 -11.2.0.3
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEM
ORA-1653: unable to extend table SYS.SETTINGS$ by 8 in tablespace SYSTEMShould I restart catupgrd.sql ?
Thanks and regards,
Pavelyou should make SYSTEM tablespace larger

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: nable to extend table

Hi guys. Had this error in the alert.log file.
Mon Jun 26 09:10:37 2006
ORA-1653: unable to extend table APPLSYS.WF_LOCAL_ROLES_STAGE by 4849950 in tablespace APPLSYSD
The tablespace have three datafiles of which its both datafiles are only 40% full.
pctree on the table is set to 10 and pctuse to 40
querying the dba_segments for the table gives header block 73674 , bytes 40960, blocks 5, initial_extent 40960, next_extent 3.9731E+10, min_extent 1, maxextent 2147483645, pct_increase 50 and freelist 1.
Can any one please help??
Thanks.
DID

Dont understand what you mean over here. Would u mind
explaining me what to do?? (separate segment????)sorry bout that. see my previous post.
segment is the physical "table" in oracle; the storage, made up of one or more extents.
>
the tablespace contain 3 datafiles file1 27GB,
35.98% used, file2 25GB, 35.07% used and file3 28GB,
12% used.thats why there is no way to allocate a single "piece" of 37GB, hence the error
Can you add a new, say, 40GB datafile? (if you really need the partition to extend that much??)
Was thinking of coalescing the tablespace space! Is
it gonna be neccessary?This will just "bundle" neighbouring free extents, which may not help much.
Message was edited by:
orafad

ORA-1653

Similar Messages

Maybe you are looking for