Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

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

Samuel RabiniSep 25 2009 — edited Sep 25 2009
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!
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Oct 23 2009
Added on Sep 25 2009
3 comments
868 views