DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: ORA-1652: unable to extend temp segment by 32 in tablespace TEST_LARGE_IX

  1. #1
    Join Date
    Oct 2003
    Location
    manila, philipppines
    Posts
    6

    ORA-1652: unable to extend temp segment by 32 in tablespace TEST_LARGE_IX

    Dump file /opt/app/oracle/admin/TEST//udump/test_ora_11285.trc
    Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.4.0 - 64bit Production
    ORACLE_HOME = /opt/app/oracle/product/8.1.7
    System name: SunOS
    Node name: qadb01
    Release: 5.8
    Version: Generic_108528-18
    Machine: sun4u
    Instance name: TEST
    Redo thread mounted by this instance: 1
    Oracle process number: 67
    Unix process pid: 11285, image: oracle@qadb01 (TNS V1-V3)

    *** 2003-10-17 09:57:54.663
    *** SESSION ID:(32.756) 2003-10-17 09:57:54.640
    DEADLOCK DETECTED
    Current SQL statement for this session:
    UPDATE FolderTab SET fo_Version = 143 WHERE rootId = '23haf.6s' AND fo_Version = 142
    The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock:
    Deadlock graph:
    ---------Blocker(s)-------- ---------Waiter(s)---------
    Resource Name process session holds waits process session holds waits
    TX-000b0017-000001b7 67 32 X 28 99 X
    TX-000c000e-000001b3 28 99 X 67 32 X
    session 32: DID 0001-0043-00000002 session 99: DID 0001-001C-00000002
    session 99: DID 0001-001C-00000002 session 32: DID 0001-0043-00000002
    Rows waited on:
    Session 99: obj - rowid = 0000945A - AAAJRaAAMAAAAMXABM
    Session 32: obj - rowid = 0000945A - AAAJRaAAMAAAAMdAA6
    ===================================================
    PROCESS STATE
    -------------
    Process global information:
    process: 3803e70a0, call: 3815662a8, xact: 38120a0b0, curses: 3804f4920, usrses: 3804f4920
    ----------------------------------------
    SO: 3803e70a0, type: 1, owner: 0, pt: 0, flag: INIT/-/-/0x00

    Can any one help me please?
    Cheers!
    SivaRam

  2. #2
    Join Date
    Sep 2002
    Location
    England
    Posts
    7,334
    "The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock"

    You have a bad application, track it down and remove the thing that causes the deadlock

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width