Oracle 10g Database Locking Session Issue












0















I have a problem with locking and not timing out in one of my Oracle databases. This session locks occur on certain transactions that come from Oracle Forms users. For instance, when some user requests to make a change on a locked object the transaction waits for the locked object to be released, but it waits indefinetely until killed by alter session.



I've tried the same in my testing database and it does kill the locked session after 60s, so I thought it has to be a configuration issue.
I've checked the v$parameters DISTRIBUTED_LOCK_TIMEOUT and it is set to 60s in both databases.



Does anyone know where is the "locking session/transaction timeout" set?



Any help is greatly appreciated.










share|improve this question















migrated from superuser.com Jan 22 at 15:39


This question came from our site for computer enthusiasts and power users.



















  • have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

    – kevinsky
    Jan 22 at 15:43











  • Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

    – ArnauVJ
    Jan 22 at 15:56


















0















I have a problem with locking and not timing out in one of my Oracle databases. This session locks occur on certain transactions that come from Oracle Forms users. For instance, when some user requests to make a change on a locked object the transaction waits for the locked object to be released, but it waits indefinetely until killed by alter session.



I've tried the same in my testing database and it does kill the locked session after 60s, so I thought it has to be a configuration issue.
I've checked the v$parameters DISTRIBUTED_LOCK_TIMEOUT and it is set to 60s in both databases.



Does anyone know where is the "locking session/transaction timeout" set?



Any help is greatly appreciated.










share|improve this question















migrated from superuser.com Jan 22 at 15:39


This question came from our site for computer enthusiasts and power users.



















  • have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

    – kevinsky
    Jan 22 at 15:43











  • Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

    – ArnauVJ
    Jan 22 at 15:56
















0












0








0








I have a problem with locking and not timing out in one of my Oracle databases. This session locks occur on certain transactions that come from Oracle Forms users. For instance, when some user requests to make a change on a locked object the transaction waits for the locked object to be released, but it waits indefinetely until killed by alter session.



I've tried the same in my testing database and it does kill the locked session after 60s, so I thought it has to be a configuration issue.
I've checked the v$parameters DISTRIBUTED_LOCK_TIMEOUT and it is set to 60s in both databases.



Does anyone know where is the "locking session/transaction timeout" set?



Any help is greatly appreciated.










share|improve this question
















I have a problem with locking and not timing out in one of my Oracle databases. This session locks occur on certain transactions that come from Oracle Forms users. For instance, when some user requests to make a change on a locked object the transaction waits for the locked object to be released, but it waits indefinetely until killed by alter session.



I've tried the same in my testing database and it does kill the locked session after 60s, so I thought it has to be a configuration issue.
I've checked the v$parameters DISTRIBUTED_LOCK_TIMEOUT and it is set to 60s in both databases.



Does anyone know where is the "locking session/transaction timeout" set?



Any help is greatly appreciated.







deadlock oracle-10g timeout






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 23 at 16:32







ArnauVJ

















asked Jan 22 at 15:17









ArnauVJArnauVJ

61




61




migrated from superuser.com Jan 22 at 15:39


This question came from our site for computer enthusiasts and power users.









migrated from superuser.com Jan 22 at 15:39


This question came from our site for computer enthusiasts and power users.















  • have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

    – kevinsky
    Jan 22 at 15:43











  • Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

    – ArnauVJ
    Jan 22 at 15:56





















  • have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

    – kevinsky
    Jan 22 at 15:43











  • Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

    – ArnauVJ
    Jan 22 at 15:56



















have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

– kevinsky
Jan 22 at 15:43





have you identified the code that is locking? Is it a table or row lock? Table locks might indicate that the coding can be improved

– kevinsky
Jan 22 at 15:43













Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

– ArnauVJ
Jan 22 at 15:56







Hi, it is a row lock. The Oracle Forms data blocks have a "locking mode" property which can be set to different locking options. One of them (the one I'm using) locks the row whenever it detects that someone is changing its value on the form (I need it to work this way).

– ArnauVJ
Jan 22 at 15:56












1 Answer
1






active

oldest

votes


















0














You can change distributed_lock_timeout at the instance level alter system set distributed_lock_timeout=<sec> scope=spfile;
But what you are describing is a session modifiable parameter in 11g called ddl_lock_timeout and I’m not aware of anything that replicates that in 10g. The fact that it runs as expected in one environment and not the other means you might want to pull a list of parameter settings between the two and see what’s different.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227773%2foracle-10g-database-locking-session-issue%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    You can change distributed_lock_timeout at the instance level alter system set distributed_lock_timeout=<sec> scope=spfile;
    But what you are describing is a session modifiable parameter in 11g called ddl_lock_timeout and I’m not aware of anything that replicates that in 10g. The fact that it runs as expected in one environment and not the other means you might want to pull a list of parameter settings between the two and see what’s different.






    share|improve this answer




























      0














      You can change distributed_lock_timeout at the instance level alter system set distributed_lock_timeout=<sec> scope=spfile;
      But what you are describing is a session modifiable parameter in 11g called ddl_lock_timeout and I’m not aware of anything that replicates that in 10g. The fact that it runs as expected in one environment and not the other means you might want to pull a list of parameter settings between the two and see what’s different.






      share|improve this answer


























        0












        0








        0







        You can change distributed_lock_timeout at the instance level alter system set distributed_lock_timeout=<sec> scope=spfile;
        But what you are describing is a session modifiable parameter in 11g called ddl_lock_timeout and I’m not aware of anything that replicates that in 10g. The fact that it runs as expected in one environment and not the other means you might want to pull a list of parameter settings between the two and see what’s different.






        share|improve this answer













        You can change distributed_lock_timeout at the instance level alter system set distributed_lock_timeout=<sec> scope=spfile;
        But what you are describing is a session modifiable parameter in 11g called ddl_lock_timeout and I’m not aware of anything that replicates that in 10g. The fact that it runs as expected in one environment and not the other means you might want to pull a list of parameter settings between the two and see what’s different.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 23 at 18:20









        gbourasgbouras

        11




        11






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227773%2foracle-10g-database-locking-session-issue%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Сан-Квентин

            Алькесар

            8-я гвардейская общевойсковая армия