Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2003
    Posts
    12

    Question Unanswered: orphan connections session afte select for update

    hello DBA's

    my problem is : we are using Java to read and right to the database , we using select for update in some cases, the problem is when the network disconnect between the application and the database . these rows that locked with select for update keeped locked even the session is not active any more because there is no network.

    my question is : how i can identify these sessions and kill theme by force , and why oracle did not do this operation automaticlly

    thanx

  2. #2
    Join Date
    Jul 2003
    Posts
    2,296
    unix command-line:
    Code:
    ps -ef | grep oracle
    then:
    Code:
    kill -9 pid#
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  3. #3
    Join Date
    Sep 2003
    Posts
    12

    Exclamation how can do that from oracle

    i need to do it form oracle meaning:
    when i rerun my application , i need the application to identify automaticlly these sessions(dead sessions) and kill them.

  4. #4
    Join Date
    Dec 2003
    Location
    Buenos Aires, Argentina
    Posts
    86
    You can set the following parameter in the "$ORACLE_HOME\network\admin\sqlnet.ora" file:

    sqlnet.expire_time=N
    Enables dead connection detection, that is, after the specifed time N (in seconds) the server checks if the client is still connected. If not, the server process exits. This parameter must be set on the server.

    If it doesn't work, check Metalink for your db version and available patch sets cause this feature, has several bugs.
    Regards,
    Manf

Posting Permissions

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