(ORA-1653, ORA-1658)TABLESPACE 크기를 확장하는 방법
제품 : ORACLE SERVER
작성날짜 : 1995-11-21
(ora-1653, ora-1658)Tablespace를 확장하는 방법
=============================================
오라클 7.1 이하에서는 tablespace를 확장하려면 해당 tablespace에
데이타 화일을 추가하는 방법을 사용한다. 이 때 추가하는 데이타 화일의
이름은 기존의 화일과 동일한 이름이 아니기만 하면 되지만, 편의상 기존의
화일에 일련 번호를 붙여서 사용하는 것이 일반적이다.
예를 들어 tablespace TOOLS 를 확장한다고 가정하면
$sqlplus system/manager
SQL>select file_name, bytes
from dba_data_files
where tablespace_name = 'TOOLS';
이와 같이 하면 현재 TOOLS tablespace를 구성하고 있는 화일 이름과 크기
(bytes)가 출력된다. 여기서 출력된 file_name 이 /oracle/dbs/toolsORA.dbf
라고 한다면 다음과 같이 하여 tablespace를 확장한다.
SQL>alter tablespace tools
add datafile '/oracle/dbs/tools2ORA.dbf' size 50M;
여기서는 화일의 크기를 50M 로 주었는데 이것은 디스크의 FREE SPACE 와
기존의 데이타 화일의 크기 및 앞으로 들어갈 데이타의 크기 등을 고려하여
적절한 값으로 결정하도록 한다.
오라클 7.2 에서는 위의 방법 외에도 기존의 데이타화일의 크기를 변경시켜서
확장시킬 수 있다.
예를 들어 TOOLS tablespace가 현재 50M 크기의 /oracle/dbs/toolsORA.dbf
화일로 구성되어 있다면 다음과 같이 해서 이 화일의 크기를 100M 로 늘릴 수
있다.
SQL>alter database datafile
'/oracle/dbs/toolsORA.dbf' resize 100M;
RESIZE 옵션은 V7.2 에서 추가된 것으로 기존의 데이타 화일을 확장 또는
축소할 수 있다. 축소하는 경우는 데이타가 들어 있는 경우 하한선 이하로
내려가지는 않는다.
한편, 데이타가 계속 들어가서 tablespace를 꽉 채우게 되면 다음과 같은 명령을
이용하여 자동적으로 tablespace를 확장할 수도 있다.
SQL>alter database datafile
'/oracle/dbs/toolsORA.dbf'
autoextend on
next 10M
maxsize 200M;
이렇게 하면 데이타가 늘어나면서 자동적으로 10M 씩 데이타화일의 크기가
늘어나게 된다. 여기서는 최대 200M 까지 늘어날 수 있도록 설정하였다.
the error is because you can't create the table because your tablespace does not have a free extent large enough to hold the table referenced
So - you might have enough space if you just look at total free space, but the space is fragmented, and so it can't get enough space to create the table.
It references the tablespace in the error message. You can try to coalese the tablespace - I think the syntax is 'alter tablespace xxx coalesce'. If that doesn't work, you can add a datafile or extend an existing datafile, that will give you a big chunk of unfragmented space to work with.
One other thing - when you did the export, by default it changes the storage parameters so that the initial extent will hold the whole table, even if in the source table it spanned several extents
You can re-export with 'COMPRESS=N', then it will not change the space parameters, then try to re-import and it might work.
If none of those work, then it gets ugly - you can do a "import indexfile=xxx.sql" - that will give you a script that has the create table in it, but REMed out. You can change the storage parameters and create the table.
Then you re-import just that table with 'ignore=y', that will load the table even though it already exists.
I say it gets messy because then you have to make sure all the permissions got granted, all the constraints got created, etc, since you created the table manually.
A lot of this advice is 'old-school' - with the new locally managed and system managed tablespaces, this stuff is not needed any more. Is your tablespace dictionary-managed?
Similar Messages
-
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...
SaswatThis 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: 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 -
Hi Friends,
EBS 11i
Oracle DB 9.2.0.6
RHEL 4.6
I just encountered error in our database ora-1653 in the tablespace APPS_TS_QUEUES, and it has two datafiles namely:
SQL> select file_name, AUTOEXTENSIBLE from dba_data_files where tablespace_name='APPS_TS_QUEUES';
FILE_NAME AUT
/u02/oracle/oaproddata/a_queue02.dbf YES
/u02/oracle/oaproddata/a_queue01.dbf YESBased on the metalink notes, I did the command:
alter database datafile '/u02/oracle/oaproddata/a_queue01.dbf ' autoextend on;
alter database datafile '/u02/oracle/oaproddata/a_queue02.dbf ' autoextend on;
But it did not solve the issue :(
Do you think I need to bounce back the database of let the users exit from their login Forms data entry?
I tried doing this :
alter tablespace APPS_TS_QUEUES add datafile '/u02/oracle/oaproddata/a_queue03.dbf' size 500M ;
and the problem was solved.
I just can not understand why "autoextend" did not work :(
Please clear my doubts ...
Thanks a lot,
Ms KHussein,
Do you think that even if I made the all tablespace1 "autoextend on" I will still get Ora-1653?
I have another mistake too :( I cleared up all logs after I fixed the ora error becase the are lots and lots of logs in the database background dump files accumulated for the past years. I decided to clear to so that I can fresh see new logs.
I also reset the altertPROD.log huhuhuh. And now the support wants what exact time did the error occured. And I can not give it. This is the logs in the bdump database side.
Can I get logs for the error at the APPS tier side? where can I get the applications log when it hit Ora-1653 while the user was processing the Order Management module?
Thansk a lot
Edited by: user_unlimited on Oct 11, 2010 5:31 PM -
ORA-12012-ORA-12008-ORA-04063: error on r11i
Heloo all;
I have this error:
Errors in file 9.2.0/admin/erp/bdump/prod_j000_18936.trc:
ORA-12012: error on auto execute of job 189
ORA-12008: error in materialized view refresh path
ORA-04063: package body "APPS.FND_GLOBAL" has errors
undo_suppress_errors = FALSE
undo_suppress_errors = FALSE
ORA-12012: error on auto execute of job 189
ORA-12008: error in materialized view refresh path
ORA-04063: package body "APPS.FND_GLOBAL" has errors
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 820
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 877
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
ORA-00060: Deadlock detected. More info in file 9.2.0/admin/terp/udump/prod_ora_736.trc.
ORA-1653: unable to extend table APPLSYS.DR$FND_LOBS_CTX$I by 16 in tablespace APPS_TS_TX_DATA
ORA-1653: unable to extend table APPLSYS.DR$FND_LOBS_CTX$I by 16 in tablespace APPS_TS_TX_DATA
my APPS_TS_TX_DATA doesnt have size problem...iAPPS.FND_GLOBAL doesnt inviladi!....
after this error message today i have this error:
undo_suppress_errors = FALSE
ORA-00060: Deadlock detected. More info in file /oradb/PROD/proddb/9.2.0/admin/erp/udump/prod_ora_3463.trc.
for the both error undo_suppress_errors seems common...
is anyone has this error before?
Thanks
HeliosHelios,
Please review the following documents and try the suggested solutions.
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
Note: 154207.1- d1553256.drv Errors ORA-01631 Max Extents Reached Table APPLSYS.DR$FND_LOBS_CTX$I
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=154207.1
Note: 367861.1 - "Rebuild Help Search Index" fails with ORA-01631: max # extents (505) reached in table APPLSYS.DR$FND_LOBS_CTX$
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=367861.1
Note: 180588.1 - Solving ORA-01653: UNABLE TO EXTEND TABLE %S.%S BY %S IN TABLESPACE %S
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=180588.1
If you still get ORA-00060 after resolving the above error, refer to:
Note: 62365.1 - What to do with "ORA-60 Deadlock Detected" Errors
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=62365.1
Note: 164661.1 - ORA-60 / Deadlocks Most Common Causes
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=164661.1
Regards,
Hussein -
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 PMHi 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 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 -
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 -
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.sanjeeviHi,
Your system tablespace is full
http://ora-01655.ora-code.com/
Contact your DBA
Regards,
Jari -
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 updatePl do not post duplicates - Which table belong to which table
-
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?
ThanksShivendraNarainNirala 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??
Thanlshi.
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
PatrickHi,
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
Maybe you are looking for
-
How do I select multiple tracks in iTunes?
It's like a hold down control and something else, and then drag the curser to select the songs you want selected. I'm not sure what this shortcut is. Again, I want to select multiple tracks on iTunes so I can move files or delete them. Simply selecti
-
After installing Reader 11.0.07 update on my iMac OS X, v.10.8.5, when I open an Adobe pdf file I see Chinese script next to the blue loading bar at the bottom of the screen. This never appeared before when downloading pdf files and I am worried tha
-
Can't make static reference to method while it is static
Hello, can somebody please help me with my problem. I created a jsp page wich includes a .java file I wrote. In this JSP I called a method in the class I created. It worked but when I made the method static and adjusted the calling of the method it s
-
Mail not opening or closing correctly
In the process of trying to configure my mail to gmail, I have done something wrong. Now when I click on mail a completely different icon appears. I can not go to preferences (or anywhere else). It will not shut down by itself. I have to use force qu
-
Cannot get some photos to share/export. Help
Four of the 75 photos in an album I am sharing absolutelywill not export or copy or email in any way, no matter what I do. A "forbidden" icon (a diagonal slash though a circle) appears in the edge of the photo whenever I try to move/export it. Help.