Oracle error message code 1653 op 4, ORA-01653: unable to extend table

Hi
Our application use Oracle 9i as database. I modified one of tables and try to convert it from this application, then I got an Oralce 1653 error as followings:
Creating Table SAMPLE_T
Copying data from SAMPLE to SAMPLE_T
Unable to move data from table 'SAMPLE' to table 'SAMPLE_T'
Oracle error message code 1653 op 4, ORA-01653: unable to extend table SAND.SAMPLE_T by 1024 in tablespace SAMPLE_RESULT
I suspect the tablespace SAMPLE_RESULT is not big enough and also can not extended automatically, but not sure if it is right or there maybe other reasons behind this error.
Any idea?
Thanks
Li

Lets try .....
SQL> select tablespace_name,sum(bytes)/1024 from dba_free_space where tablespace_name='USERS' group by tablespace_name;
TABLESPACE_NAME                SUM(BYTES)/1024
USERS                                      384
SQL> alter database datafile 'C:\ORACLE\ORADATA\MYDB\USERS01.DBF' autoextend off;
SQL> alter table scott.emp allocate extent;
Table altered.
SQL> /
alter table scott.emp allocate extent
ERROR at line 1:
ORA-01653: unable to extend table SCOTT.EMP by 128 in tablespace USERSI believe you must add more space to tablespace SAMPLE_RESULT or set the autoextend on for associated datafiles.
Hope it help ..
Bhupinder

Similar Messages

  • Oracle error message code 1401 op 4, ORA-01401: inserted value too large fo

    Hi All
    I got this error when I try to run convert tables on our application server. Anyone know why? I am using Oracle 9i
    Here is the error message:
    Checking Table WORK_INSTRUCTION
    Table not in database
    Conversion Method - Create Table
    Creating Table WORK_INSTRUCTION
    Unable to create database table 'WORK_INSTRUCTION'
    Oracle error message code 1401 op 4, ORA-01401: inserted value too large for column
    WORK_INSTRUCTION definition as followings:
    table work_instruction;
    field identity
         used_for unique_key
         datatype identity;
    { APR 31/3/03 - Bug Nr WI4}
    field wi_admin
    {         links_to personnel . identity;}
    {         links_to location . identity;}
         links_to lab_section . identity;
    { ARP 31/3/03 - Bug Nr WI5 }
    field wi_title
    {         datatype text(20);   }
         datatype text(100);
    field version
              datatype text ( 4 );
    field wi_status
         datatype identity
         prompt_type choose
         choose_type WI_STATUS
         default 'I ' ;
    field wi_type
         datatype identity
         prompt_type choose
         choose_type WI_TYPE
         default '0 ';
    field sterlab_status
         datatype identity
         prompt_type choose
         choose_type STER_STAT
         default '0 ';
    field used_in_lims
         datatype boolean
         true_word 'Yes'
         false_word 'No'
         default 'No' ;
    { ARP WI16 28/5/03 - Extend from 10 to 45 }
    field method
         datatype text(45);
    field ref_method
         datatype text(100);
    field delegate
         links_to personnel . identity;
    field date_expire
         datatype date;
    field date_draft
         datatype date;
    field double_method
         datatype boolean
         true_word 'Yes'
         false_word 'No'
         default 'No' ;
    field technique
         datatype identity
         prompt_type choose
         choose_type TECHNIQUE
         default '0 ';
    field date_distribute
         datatype date;
    field report_date
         datatype date;
    field group_autho
         datatype text ( 16 );
    field astm_volume
         datatype text ( 6 );
    field date_non_active
         datatype date;
    field translated_in
         datatype text(10);
    { ARP WI16 28/5/03 - Extend from 60 to 2000 }
    field comments
         datatype text(2000);
    field doc_path
         datatype text ( 300 )
         prompt_type user_defined
         library 'TEST_SOP_FILE'
         routine 'file_browse';
    field modified_on
         datatype date
         used_for modified_on ;
    field modified_by
         links_to personnel.identity
         used_for modified_by;
    field modifiable
         datatype boolean
         used_for modifiable;
    field removeflag datatype boolean
         used_for remove_flag;
    { MOD TDR - 10/04/03 - Link to livelink document }
    field livelink_url
    datatype text ( 300 ) ;
    Thanks
    Li

    Verbatim from the manual:
    ORA-01401:     inserted value too large for column
    Cause:     The value entered is larger than the maximum width defined for the column.
    Action:     Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.You should find which value is bein attempted to be inserted into a column with a capacity shorter than the value length.
    ~ Madrid.

  • Generating 20 million rows induced error: ORA-01653: unable to extend table

    Exact error is: ORA-01653: unable to extend table HR.F by 1024 in tablespace SYSTEM.
    Why cannot it extend table HR.F?
    Is it because I have Oracle Express Edition 10g?
    "Typically you will receive one of the following messages during the upgrade if your SYSTEM tablespace size is insufficient". What should I consider when wanting to generate 20 million rows? By the way, generating 1 million rows is successful.

    1.By esuring the status of the tables FND_INSTALL_PROCESS and AD_DEFERRED_JOBS and if there are any rows in it, also checking the worker logs (If it exisits) and patch log, we can consider options which we can make sure that the current issue can be taken care. If the adpatch has come out and back to prompt, after adding the space we can restart with the various options to start from where it left off.If FND_INSTALL_PROCESS and AD_DEFERRED_JOBS have not been dropped by adpatch, you can start adaptch from the beginning (after fixing the failed worker via adctrl as stated by Rajiv), and continue with the previous failed adpatch session.
    2. By adding up the space we can also ensure that the future patch application will not fail again.Correct -- Provided you have sufficient space or turning autoextend on for this tablespace (with cautious).
    Thanks,
    Hussein

  • 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-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-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)

  • REG:ORA-01653: unable to extend table SYS.OBJ$ by 128 in tablespace SYSTEM

    Hi
    My database is
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    PL/SQL Release 10.2.0.4.0 - Production
    CORE     10.2.0.4.0     Production
    TNS for Solaris: Version 10.2.0.4.0 - Production
    NLSRTL Version 10.2.0.4.0 - Production
    I get the following error
    ORA-00604: error occurred at recursive SQL level 1 ORA-01653: unable to extend table SYS.OBJ$ by 128 in tablespace SYSTEM
    java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01653: unable to extend table SYS.OBJ$ by 128 in tablespace SYSTEM
    When query the dba_data_files system tablespace
    TABLESPACE_NAME AUTOEXTENSIBLE FILE_NAME MAXBYTES/1024/1024/1024 BYTES/1024/1024/1024 SYSTEM YES DATA/maq1/datafile/system.260.709848331        31.9999847412109375     0.65447998046875                                                                                                                                                                                                                                                                                                                                                                                                                            SYSTEM                         NO             DATA200/maq1/datafile/system.310.729819887 0 0.9765625
    2 rows selected
    Please advice

    Hello,
    ORA-00604: error occurred at recursive SQL level 1 ORA-01653: unable to extend table SYS.OBJ$ by 128 in tablespace SYSTEM
    TABLESPACE_NAME AUTOEXTENSIBLE FILE_NAME                                   MAXBYTES/1024/1024/1024  BYTES/1024/1024/1024
    SYSTEM          YES            +DATA/maq1/datafile/system.260.709848331    31.9999847412109375      0.65447998046875
    SYSTEM          NO             +DATA200/maq1/datafile/system.310.729819887 0                        0.9765625
    If you have enough space on the Disk for the first Datafile to extend, it's a rather strange behaviour.
    In this case, I suggest you to open a SR on My Oracle Support.
    On Solaris, a similar bug was reported (in 9.2.0.8 release):
    Bug 7196775: ERROR ORA-01653 OCCURS WHILE INSERTING RECORDS IN TABLE WITH DATAFILE AUTOEXTENDElse, you may try to extend manually the Datafiles so as to get enough free space inside the Tablespace SYSTEM.
    Hope this help.
    Best regards,
    Jean-Valentin

  • 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  by 16 in tablespace

    Hi All,
    When i run the script it throws the following error msg:
    ORA-01653: unable to extend table by 16 in tablespace
    Can anyone help me.
    Thanks in advance

    See this link and get an idea of it:
    http://www.dbmotive.com/oracle_error_codes.php?errcode=01653
    Generally when u try to create a table of size more than the tablespace you will encounter this problem.Even for more no of columns you will face this problem.

  • ORA-01653: unable to extend table SYS.ARGUMENT$ by 13 in tablespace SYSTEM

    I have created new database manually.
    when I am @?/rdbms/admin/catproc.sql putting this sql to run.
    for sometime it says created, granted. but after some part it give me the error.
    ORA-01653: unable to extend table SYS.ARGUMENT$ by 13 in tablespace SYSTEM
    Please help me on this.
    Thank you in advance.

    Your query does not provide SYSTEM tablespace size. It provides list of tablespaces. And it can't be a complete list since I do not see UNDO and TEMP tablespaces. In any case, based on the output you did not create any user tablespaces, so all tables you are creating went to SYSTEM tablespace and eventually you ran out of space. You need to create user tablespaces if you do not have any. You need to change non-system users and set default tablespace to non-system tablespaces. Even if you do have non-system tablespaces, tables will be created in user default tablespace unless you explicitly specify one. You need to move existing user tables/indexes to non-system tablespaces.
    SY.
    P.S. In order to get SYSTEM tablespace size you need to run:
    select sum(bytes)/1024/1024 tablespace_size_in_mb
    from dba_data_files
    where tablespace_name = 'SYSTEM';

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

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

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

  • ORA-01653: unable to extend table SBC.TBL_WEBPHONE by 3078 in tablespace

    HI all,
    I know the solution for the above error is to either resize the datafile or add a new datafile to that paticular tablespace.
    But i want to knowthe exact space required by the new extent in that paticular tablespace?
    i am using 10g on unix platform.
    regards

    But i want to knowthe exact space required by the new extent in that paticular tablespace?Are you asking what's 3078 ? Blocks.
    $ oerr ora 1653
    01653, 00000, "unable to extend table %s.%s by %s in tablespace %s"
    // Cause:  Failed to allocate an extent of the required number of blocks* for
    // a table segment in the tablespace indicated.
    // *Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more
    // files to the tablespace indicated.
    $

  • ORA-01653:enable to extend table APPLSYS.FND_LOGIN by 128

    Hi,
    I am facing the below error while running the concurrent program:
    ORA-01653:enable to extend table APPLSYS.FND_LOGIN by 128 in Tablespace FND_TAB.
    Could you please suggest me something on this.
    Thanks

    Logging into and working in EBS causes audit data to be inserted into various FND tables, one of them being FND_LOGIN. It is a best practice to run the "Purge Signon Audit Data" concurrent program regularly, based on your needs and requirements as to how long login audit data needs to be retained at your site. This program runs the script $FND_TOP/sql/FNDSCPRG.sql. This will delete data form FND_LOGIN (and other) tables and keeps them from growing too big.
    HTH
    Srini

  • 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".

  • 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

Maybe you are looking for

  • K9N Platinum onboard ethernet resource problem

    I am having a problem getting my onboard ethernet to work on the MSI K9N Platinum motherboard. The device manager is giving me Error Code 12 which stands for Not enough available resources. I have tried everything short of reinstalling Windows to get

  • How do I recover my lost Apple ID account??

    Hi, About a year ago, I had my original Apple ID account on my Iphone 4s, but later forgot my password and my security questions, so I ended up just creating a whole new account and email address. Now I updated my Iphone, but all my stuff was erased

  • Questions on PO attachments

    Hi Gurus, Is there any possibility to restrict the viewing or editing of attachments in PO, unless it belongs to the purchasing group. Is there any commands which will enable this in SAP? Thanks.

  • Corrupt attachments with damaged filenames

    hi, i'm experiencing problems when receiving certain attachments. the filenames look like this: 'Archive_17?= =?utf-8?Q?0607.zip?=' if i rename it to 'Archive17_0607.zip' i can open the zip, but the ppt-file inside is damaged. i had this problem quit

  • Why is the box "add security exemption" coming up when trying to download email from Comcast?

    am afraid to click on "accept as an exemption" in case this is not what it appears to be and downloads problems to my computer.