insert locks aplication Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: insert locks aplication

  1. #1
    Join Date
    Feb 2007

    insert locks aplication


    We have a problem in a insert, he locks the instance and nobody can do anything.
    Some one now how a insert can go out after a period of time like 60 second?

    The aplication is in java remotly.


  2. #2
    Join Date
    Nov 2000
    Pittsburgh, PA
    Does the app use locking? What insert triggers do you have? Have you looked at the dba_waiters view? Have you tried setting tracing?
    this space intentionally left blank

  3. #3
    Join Date
    Feb 2005
    "he locks the instance"
    An insert does not 'lock' an instance (unless you consider an uncommitted transaction a lock that prevents normal instance shutdown).
    It gets a share lock on the table being inserted into.
    The inserted row is 'locked' but if uncommitted then no other session would be able to see it from an UPDATE, DELETE, INSERT...SELECT or SELECT FOR UPDATE.
    SELECTs don't take locks anyway, so they would have no problems.

    INSERTs can cause concurrency issues for other INSERTs/UPDATEs/DELETEs if there is a bitmap index. (Effectively a single row in a bitmap index covers multiple table rows, so changing one table row can 'lock' other table rows).

    Suggest you read
    to understand locks
    Then explicilty state exactly what statements the insert is actually preventing/stopping/locking

  4. #4
    Join Date
    Nov 2004
    Mumbai, India
    We have a problem in a insert, he locks the instance
    Hmmm.. it may be a situation where you have to run hanganalyze.
    There are three kinds of lies: Lies, damned lies, and benchmarks...

    Unix is user friendly. It's just very particular about who it's friends are.

    Oracle DBA

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