KMC_DBRM_CONTENT DB level locks observed in this table

Hi ,
Please let me know the purpose of the KMC_DBRM_CONTENT standart table in SAP Netweaver Portal Version 7.0 SP13.
We are observing Locks in the table DB level eventually causing portal to go down.
We are using very minimal KM functionality
Regards
Sudhir

Hi Sudhir,
Despite the DB is in the database of the Application Server. This specific table belongs and is controlled by the application KM. So I believe you will find a more suitable answer opening a thread, or moving this one to the Knowledge Management & Collaboration forum. There, many specialists of KM will be able to answer this question.
I hope I could help you, because the KM experts don't monitor this AS forum. So, there you will find your answer more quickly.
Thanks,
Anderson

Similar Messages

  • Record level lock on SAP ABAP table editing

    Hello All,
    I have a requirement wherein I need to give users ability to be able to update contents of a table. Currently, there are using maintenance view on the table for adding/editing contents of this table. However, this prevents other users from being able to enter the table and edit contents of other records within the table.
    Can anybody please guide me how do I go about giving record level edit lock on the table instead of entire table edit lock.
    Appreciate all responses.
    Thanks and Regards,
    Samta.

    Ok
    I  have had a request like yours, i.e the users could manage the same table in the same time.
    The standard behavior avoids it, because a lock of entire table is set.
    This was my solution:
    A) I've created a maintenance view for my table, and I set the attibute S (for subset) for all fields will be the key I want to lock.
    B) I've generated the maintenance table program for the view above.
    In this way if it try to manage the view by SM30, it'll be possible only to indicate the  values of the fields for the subset, so not all data of the table will be loaded, but only the records satisfying  the key.
    C) I've created a program to run SM30 for my view, using the fm VIEW_MAINTENANCE_CALL:
    .CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
           EXPORTING
                action      = 'S'  "Display mode
                view_name   = <table name>
           TABLES
                dba_sellist = tb_sellist
           EXCEPTIONS
                OTHERS      = 14.
    As you can see above, the SM30 is always called for DISPLAY only, in this way no standard lock is set
    D) I've use the event 19 in order to change the mode and set my lock:
    DATA: BEGIN OF MY_LOCK,
              MANDT       TYPE ZPPTA019-MANDT,
              WERKS       TYPE ZPPTA019-WERKS,
              /TRILOG/SE  TYPE ZPPTA019-/TRILOG/SE,
              COD_MOD_TAG TYPE ZPPTA019-COD_MOD_TAG,
            END OF MY_LOCK.
      DATA: W_SEL_LIST TYPE VIMSELLIST.
      DATA: VARKEY TYPE RSTABLE-VARKEY.
      FIELD-SYMBOLS: <MY_KEY> TYPE ANY.
      LOOP AT DBA_SELLIST INTO W_SEL_LIST
        WHERE VIEWFIELD = 'WERKS'
          OR  VIEWFIELD = '/TRILOG/SE'
          OR  VIEWFIELD = 'COD_MOD_TAG'.
        ASSIGN COMPONENT W_SEL_LIST-VIEWFIELD
           OF STRUCTURE MY_LOCK TO <MY_KEY>.
        IF SY-SUBRC = 0.
          MOVE W_SEL_LIST-VALUE TO <MY_KEY>.
        ENDIF.
      ENDLOOP.
      IF SY-SUBRC = 0.
        IF NOT MY_LOCK IS INITIAL.
          MY_LOCK-MANDT = SY-MANDT.
          VARKEY = MY_LOCK.
          CALL FUNCTION 'ENQUEUE_E_TABLEE'
            EXPORTING
              MODE_RSTABLE   = 'E'
              TABNAME        = 'ZPPTA019'
              VARKEY         = VARKEY
            EXCEPTIONS
              FOREIGN_LOCK   = 1
              SYSTEM_FAILURE = 2
              OTHERS         = 3.
          IF SY-SUBRC <> 0.
            MESSAGE ID SY-MSGID TYPE 'S' NUMBER SY-MSGNO
                    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ELSE.
            MAINT_MODE = VIEW_ACTION = 'U'.
          ENDIF.
        ENDIF.
      ENDIF.
      CLEAR OLD_019.
    I hope it can help you
    Max

  • Change lock type on large table

    I have a table which is about 2G size. the lock type on this table is set as AllPage.  I think this cause performance issue when issue select query, many SH lock applied. I try to change the lock type to datarow, which should have no lock when issue select as document indicated.
    but when I try it with DBArtisan, it took longtime and never end. Then I stop the app and connect it again. I found the lock type do change it to datarow. but there is a new table name like mytab_3309ac22 created.
    then I try to change lock type again on other table and got following info:
    You can not run Alter Table Lock in this database because the 'select into/bulkcopy' option is off.
    Looks like dboption changed. So want to know if this is safe for data when change lock type? how to ensure it is done properly?

    Hi Kent,
    The problem is that allpages has different physical structure than datarows.
    Changing from one format to another requires to rewrite the whole table.
    There are a few ways to achieve this goal.
    a) running the alter table directly:
    alter table x lock datarows
    This command causes to make the change internally. This is the fastest way to do that, but it requries to set the 'select into' option on the database. And that might be problematic because it breaks the  the transaction log sequence.
    If you don't have the option set on the database you are not able to run the command.
    b) doing it manually:
    1. create a second table with datarows scheme
    2. copy the rows to the table
    3. dropping the old and renaming the new table
    If you have a very busy system with little time for downtime then that would be the only solution. You can create triggers to manually log all the changes on the old table if that process would take too long.
    At the end you would have to add all the foreign keys to the new table. And of course recreate the indexes.
    I don't exactly know what DBArtisan is doing, but since you don't have the 'select into' option then probably it is running the second option. This new table with name mytab_3309ac22 might be the effect of the operation broken in the middle. How many rows has this table have? And what is the scheme?
    If you have plenty of time then I would recommend to run the alter table command together with the 'select into' option. Anyway you won't have any progress bar during this operation so it is very hard to predict the time of the operation.
    HTH,
    Adam

  • To get Lock object for Standard Table

    Hi all,
    i want to update table FKK_GPSHAD,so i need corresponding lock object for this table.can any one sughgest me the solution for this.
    Thanks in advance,...

    Hi,
    Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
    SAP Provide three type of Lock objects.
    Read Lock(Shared Locked)
    protects read access to an object. The read lock allows other transactions read access but not write access to
    the locked area of the table
    Write Lock(exclusive lock)
    protects write access to an object. The write lock allows other transactions neither read nor write access to
    the locked area of the table.
    Enhanced write lock (exclusive lock without cumulating)
    works like a write lock except that the enhanced write lock also protects from further accesses from the
    same transaction.
    You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
    Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
    Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
    Technicaly:
    When you create a lock object System automatically creat two function module.
    1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
    2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
    You have to use these function module in your program.
    check this link for example.
    http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
    tables:vbak.
    call function 'ENQUEUE_EZLOCK3'
    exporting
    mode_vbak = 'E'
    mandt = sy-mandt
    vbeln = vbak-vbeln
    X_VBELN = ' '
    _SCOPE = '2'
    _WAIT = ' '
    _COLLECT = ' '
    EXCEPTIONS
    FOREIGN_LOCK = 1
    SYSTEM_FAILURE = 2
    OTHERS = 3
    if sy-subrc 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    Normally ABAPers will create the Lock objects, because we know when to lock and how to lock and where to lock the Object then after completing our updations we unlock the Objects in the Tables
    http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
    purpose: If multiple user try to access a database object, inconsistency may occer. To avoid that inconsistency and to let multiple user give the accessibility of the database objects the locking mechanism is used.
    Steps: first we create a loc object in se11 . Suppose for a table mara. It will create two functional module.:
    1. enque_lockobject
    1. deque_lockobject
    before updating any table first we lock the table by calling enque_lockobject fm and then after updating we release the lock by deque_lockobject.
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
    GO TO SE11
    Select the radio button "Lock object"..
    Give the name starts with EZ or EY..
    Example: EYTEST
    Press Create button..
    Give the short description..
    Example: Lock object for table ZTABLE..
    In the tables tab..Give the table name..
    Example: ZTABLE
    Save and generate..
    Your lock object is now created..You can see the LOCK MODULES..
    In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
    Lock objects:
    http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
    Match Code Objects:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
    See this link:
    http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
    Check these links -
    lock objects
    Lock Objects
    Lock Objects
    Please reward points if useful.
    Regards
    Rose

  • Pl sql row level locking with wait ?

    Hi,
    I am using oracle 10g.
    I am new to Oracle locks. I have two tables Table1(id_no, employee, salary) and Table2(id_no, employee, salary).
    I need to pull any requested row from Table1 into Table2 only once on demand. I have a procedure to pull data and there could be more than one requests try to call same procedure to pull a row from Table1 into Table2 at any given time.
    I coded below to achieve row level lock. if one transaction gets row level lock on Table1 at 2, so other Transactions should wait till the lock is released at line 2 or 5 to avoid duplicates.
    But below code is not working, I am getting duplicates when I call this using two concurrent java threads.
    How do I control this concurrency issue so that I can avoid duplicate entries in Table2. Could any one please help?
    1.begin
    2.select 0 into emp_cnt
    3.from Table1 where id=id_no
    4.for update;
    5.update Table1 set employee='xyz'
    6.where id=id_no;
    7.select count(*) into table2_cnt from Table2 where id=id_no;
    8.if(table2_cnt =0) then
    9.code to insert above row from Table1 to Table2;
    10.end if;
    11.commit;
    12.End;
    Edited by: 980916 on Jan 9, 2013 5:48 PM

    Welcome to the forums and welcome to Oracle.
    Lets establish one thing right from the beginning ... the Oracle Database is not a Microsoft product.
    There is no general reason to use row level locks, you should not want to use row level locks, you don't need row level locks, and you will almost never have any valid reason to consider row level locks.
    That said there are two situations were it may be necessary to lock a row prior to an update or delete (possibly in a merge) and in those cases you want to use the built-in SELECT FOR UPDATE syntax. (Demo here: http://www.morganslibrary.org/reference/deadlocks.html#dlfu). But we should be clear here ... one rarely needs to use this locking mechanism as the chances of a collision in a well designed application are essentially zero.
    Also as you are new to Oracle please explore the dynamic performance view V$RESERVED_WORDS and do not name objects, columns, etc. with reserved word names not that there is an excuse in any product to name a column "ID." Something Joe Celko has railed about for decades and a tradition I think we should all follow.
    In the case of your posted code example (btw please read the FAQ and learn how to use tags) the solution is SELECT FOR UPDATE if locking can be justified which is unlikely.
    Edited by: damorgan on Jan 9, 2013 6:11 PM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Is this table considered to be large? Plz help

    Hello,
    I have a table that contains about 140 million rows. data size is about 38 GB. This is severly affecting performance of our application. Since this is one of the tables that stores "detail log of transactions", it keeps growing with every min and sec.
    are there any suggestions/comments to keep the size low? (e.g. by segregating columns that contain more than 1000 char of data)
    looking forward for your valuable advise.
    TIA

    Thanks for your inputs.
    Well, the procedure to insert data into this table
    takes a loong time and consume lot of resources. we
    have used insert .....select from with append hint,
    as there is very little data processing.Now we are getting somewhere ... 'The PROCEDURE is slow and uses a lot of resources' is somewhat more definitive than 'the large table is affecting our performance'. (Of course, we still do not know whether 'procedure' means a PL/SQ stored procedure or simply the sequence that you happen to be using.)
    You need to give us symptoms. Operating system & database version and patches, disk storage information (SAN, RAID level) is useful.
    What specific steps have you taken to identify the cause of slowness? Any trace, profile, explain plan?
    What level of complexity is involved in inserting into the table? Are you doing any joins in the select portion? How many indexes are there? What is the base table structure? (IOT, many wide columns, blob/clob?) How many records are being selected with each insert? Are you using bitmaps? Have you checked for any locks?
    Is only the procedure affected, or is everything affected while the procedure is running.
    So far it is as if you have gone to the doctor and said you are not feeling well.
    To get a prescription from the doctor, It is useful to know whether the bad feeling is in the back, the head, the neck, the stomach .... the more you tell us, the sooner we can make recommendations. Until we get enough details, all we can do is guess and keep asking for more detail.

  • Locked objects, Locked rows in a table, kind of locks

    Well, final question for the day.
    I created multiple session using sql plus, and in one session sql plus got lunch, it hour glasses and does nothing. I called up a DBA friend and he opined that it might be becasue one of my sessions has got a lock on a row in a table. I was also told that locks can be table level locks and row level locks.
    Please help me understand the below( I did try to read about locks, but atleast after first reading it is more confusing.. in order to update a row in a table why would oracle obtain a table level lock?)
    1. What are the different database objects which can get locked ?
    2. What are the different kinds of locks and what do they mean?
    3. When a row is locked by a session, can we identify that particular session and how ?
    4. What is the difference between pessimistic locking and optmistic locking ?
    5. Any scripts which I can use to get lock related info from database ?
    Gony

    1. What are the different database objects which can get locked ?There are locks which oracle acquire on any useful resource. We , as the users are most focussed on tables and their locks. But locks do happen in memory as well.
    2. What are the different kinds of locks and what do they mean?http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/dynviews_2.htm#REFRN30121
    3. When a row is locked by a session, can we identify that particular session and how ?Sure, there is a default script that comes up, utllockt.sql which can show you. Other than that, you can EM to do so as well. Read this,
    4. What is the difference between pessimistic locking and optmistic locking ?http://download.oracle.com/docs/cd/B28359_01/server.111/b28274/instance_tune.htm#sthref748
    5. Any scripts which I can use to get lock related info from database ?See #4 above.
    HTH
    Aman....

  • Record level locking

    Hi Experts,
              I want to lock a table as per ecord level locking . How to go for it?
              Actually the table is being updated with key records simultaneously through different processes.
    Regards,
    Jyoti Shankar

    HI,
    SAP provides you with the ability to restrict access to data while the table is being updated. This is fairly
    simple to implement via the use of a lock object . Create the Lock Object in SE11 for that table, if that already exist then use that one..
    Add the following code in-order to create the table lock. This function module must be called before any
    update takes place. If a lock has already been taken out it will display the appropriate message.
      CALL FUNCTION 'ENQUEUE_EZ_ZTABLENAME'
          EXPORTING
               mode_ZTABLENAME = 'E'
               mandt              = sy-mandt
               KEYFIELD1           = "Value
               KEYFIELD2           = "Value
               KEYFIELD3           = "Value
    *         X_KEYFIELD1            = ' '
    *         X_KEYFIELD2            = ' '
    *         X_KEYFIELD3            = ' '
    *         _SCOPE             = '2'
    *         _WAIT              = ' '
    *         _COLLECT           = ' '
    *   If exceptions are not used, message is displayed within FM
        EXCEPTIONS
             FOREIGN_LOCK       = 1
             SYSTEM_FAILURE     = 2
             OTHERS             = 3.
      IF sy-subrc <> 0.
    *   Retrieve message displayed within Function Module
        message id     sy-msgid
                  type   'I'
                  number sy-msgno
                  with   sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
    The following code will remove the lock for the specific table entries.
    CALL FUNCTION 'DEQUEUE_EZ_ZTABLENAME'
        EXPORTING
             MODE_ZTABLENAME = 'E'
             MANDT              = SY-MANDT
               mandt              = sy-mandt
               KEYFIELD1           = "Value
               KEYFIELD2           = "Value
               KEYFIELD3           = "Value
            X_KEYFIELD1            = ' '
            X_KEYFIELD2            = ' '
            X_KEYFIELD3            = ' '
            _SCOPE             = '3'
            _SYNCHRON          = ' '
            _COLLECT           = ' '
    releasing the lock is mandatory,
    See the link for more info.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4c8a79e11d1950f0000e82de14a/content.htm
    Regards
    Sudheer.

  • Detail screen for row level locking

    Hi All ,
    I have developed row level locking for a table , Next requirment is to display the details of each row i another screen when the user click on each row .And if the row which is clicked for display is geyout in first screen then it should be grey in details screen also .If the row is editable in the first screen then it should be in change mode in details screen .
    I appreciate the help and support .
    please provide the answer as soon as possbile .....
    Thanks,
    NJ

    Yes, if a process holds many row level locks on a table, those locks by default can be escalated to partition locks, and, if necessary, table locks.  Unless you are getting and holding many locks on a given table, this will not happen.
    You say you are exporting data.  If all you are doing is selecting from the table (not updating, deleting or inserting data) and you are using the read committed transaction isolation level, you would only hold a lock on a row for the small fraction
    of a second when you are actually reading it.  So you will never have large numbers of locks at one time.  If you are doing large numbers of updates, inserts, or deletes in a singletransaction or if you are doing large numbers of selects in a single
    transaction with the isolation level set to repeatable read or serializable, then it is possible to get enough locks to cause SQL server to escalate to partition or table locks.  This is normally a good thing (that's the reason Microsoft made it the default). 
    To many locks eats up memory.
    However, if you determine this is causing you a problem and you do not want the locks on a particular table ever escalated, you can use the ALTER TABLE SET (LOCK_ESCALATION = DISABLE) command to prevent most cases of lock escalation on a table by table basis. 
    See BOL for a description of the ALTER TABLE command.  However, I would recommend you not use this unless you have determined that lock escalation is causing you problems.  It is very easy to make things worse, not better by doing this.
    Tom

  • Row level locks

    Hi All,
    Version - Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
    I have a card's data in a table. Whenver a two different sessions/threads selects the data sometimes they get the same card.
    Now I need to lock the record. If Thred-1 selects then it will lock the first records and thread-2 must select the second record as the first record is locked by thread-1.
    I have written a piece of code , at first session it locks one record and when second session select it selects no records.
    I have takem MIN group function because I want the cards to be selected in order.
    Can you please tell where is my code went wrong or need some changes. Data and code is given below.
    SQL> SELECT * FROM crm_pps_cards_sz ORDER BY 1;
    CARD_NO          PIN  SERIAL_NUMBER DATE_CREATED DATE_MERGED DATE_ALLOCATED DATE_REGISTERED
    6338079966430591 9985 9950013661    12/06/2011                             
    6338079973369543 6858 9950013660    12/06/2011                             
    6338079978994154 7144 9950013655    12/06/2011                             
    6338079981471778 7631 9950013654    12/06/2011                             
    6338079986365041 7849 9950013657    12/06/2011                             
    SQL>
    Thread - 1
    Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
    Connected as crm
    SQL> set serveroutput on
    SQL>
    SQL> DECLARE
      2    l_rec crm_pps_cards_sz%ROWTYPE;
      3    CURSOR c IS
      4      SELECT * FROM crm_pps_cards_sz t WHERE t.card_no =
      5      (SELECT MIN(card_no) card FROM crm_pps_cards_sz)
      6      FOR UPDATE NOWAIT SKIP LOCKED;
      7 
      8  BEGIN
      9    OPEN c;
    10    FETCH c
    11      INTO l_rec;
    12    CLOSE c;
    13    dbms_output.put_line('Card Allocated ' || l_rec.card_no);
    14 
    15  END;
    16  /
    Card Allocated 6338079966430591
    PL/SQL procedure successfully completed
    SQL>
    Thread - 2
    Connected to Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
    Connected as crm
    SQL> set serveroutput on
    SQL>
    SQL> DECLARE
      2    l_rec crm_pps_cards_sz%ROWTYPE;
      3    CURSOR c IS
      4      SELECT * FROM crm_pps_cards_sz t WHERE t.card_no =
      5      (SELECT MIN(card_no) card FROM crm_pps_cards_sz)
      6      FOR UPDATE NOWAIT SKIP LOCKED;
      7 
      8  BEGIN
      9    OPEN c;
    10    FETCH c
    11      INTO l_rec;
    12    CLOSE c;
    13    dbms_output.put_line('Card Allocated ' || l_rec.card_no);
    14 
    15  END;
    16  /
    Card Allocated
    PL/SQL procedure successfully completed
    SQL> My concern is that it must allocate in the order
    6338079966430591
    6338079973369543
    ....

    It is because MIN(ard_no) is able to find value from table which is locked by you thread 1 and thread 1 mentioned NOWAIT thus it thread 2 went out without getting anything.
    Please check my reply to your duplicate thread "row level locking" .

  • OIM DB Row LOCK Exception on Quartz tables

    I am facing db row lock error in Prod OIM due to which the Scheduler fails to kick off and an OIM Restart is required to release the lock and start the Scheduler again.
    This Error is occuring at any time when none of the scheduler( Custom as well as House Keeping) are scheduled.The OIM Version is 9.0.3.1.
    I have enabled Database logs in Debug mode but there are no logs corresponding to the table where lock occured.
    This Error was encountered long back with OIM 9.0.1 and was reported as Bug 6491465, but was suspended because of no response from Customer.
    The Error trace is as follows
    ERROR,11 Sep 2009 16:57:05,497,[org.quartz.core.ErrorLogger],An error occured while scanning for the next trigger to fire.
    org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Io exception: Connection reset [See nested exception: java.sql.SQLException: Io ex
    ception: Connection reset]
    at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.obtainLock(StdRowLockSemaphore.java:154)
    at org.quartz.impl.jdbcjobstore.JobStoreCMT.acquireNextTrigger(JobStoreCMT.java:1376)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:231)
    * Nested Exception (Underlying Cause) ---------------
    java.sql.SQLException: Io exception: Connection reset
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:175)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:287)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:515)
    at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:1029)
    at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:535)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1126)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3001)
    at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3043)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:92)
    at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.obtainLock(StdRowLockSemaphore.java:137)
    at org.quartz.impl.jdbcjobstore.JobStoreCMT.acquireNextTrigger(JobStoreCMT.java:1376)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:231)
    Did anyone had ever encountered this error.Any Hints?

    I would check the network pieces as suggested in our internal emails. If the connection is dropping somewhere on your network, the lock would never be released.
    -Kevin

  • Lock and Unlock a table:AFVU

    Hi Folks.
    I want to modify a standard table (AFVU )  with new user dates from User.For this,First I need to lock and unlock the table.
    When I am trying for the standard table lock object (EAFVU) ,it was not there in the system.
    Is there any way to find out the lock object for a particular table?
    How to proceed for this?
    Any Pointers are much helpful.

    Hi,
    Go to SE11 and display your table - do a where used list and select lock objects.
    I really hope when you say you are modifying a standard table you are only updating custom appends on that table, and not directly updating standard SAP fields...
    Gareth.

  • How to lock a database Z table before updating it through a report program

    Hi,
    How to lock a database Z table before updating it through a report program and also how to unlock it after my updation.
    The whole process is done through report program.

    Hi,
    Go to SE11, in the option 'Lock object' enter the name of your lock,
    begin with 'E', suppose 'EXXXX' And create. In tab 'Tables' fill the
    table name where the record you want to lock exist and select the
    lock mode. Lock mode can be shared and exclusive. If 'shared',
    when you lock the record, other can also read data, but can not
    modify. If 'exclusive', when you lock the record, other can neither
    read nor modify the record. After save and activate, you will get two
    function module.'ENQUEUE_EXXXX' to lock record,
    'DEQUEUE_EXXXX' to release lock on one record.
    When use this function module it only lock one record at a time. It
    does not lock the table.
    Regards,
    Omkaram.

  • How to get the Minum Grade level from the view cluster table V_T710CL_B

    Hi Guys,
    I want to fetch the Minum Grade level from the view cluster table V_T710CL_B
    kindly help me
    Regards
    Rusidar.

    HI Siggi,
    Thank you for your reply..
    I am also planning to do FM to get the data. But it is saying that the Cluster table ZES does not exist (ZES is the the standard table, in SE11 also).
    How can I use the Fields from the that table.?
    What can I do now, can you please explain me about this point.
    Waiting for your reply.
    Thanks and Regards
    Rajesh
    Message was edited by:
            rajesh

  • Method-level Locking

    (Here's another one):
    I'm unable to find a way to enable method-level locking in WebLogic.
    This kind of lock has the same semantics as a simple "synchronized" on the
    method level (which you cannot write as a bean developer). The advantage is
    that you've got thread-safe access to a method without expensively
    interfering with the transaction manager.
    So is this possible in WLS v6.1/v7.0?
    Regards,
    Pieter Van Gorp.

    I assume you are talking about entity beans. You can use the "Exclusive"
    concurrency strategy. Here is the link:
    http://e-docs.bea.com/wls/docs61/ejb/reference.html#1139340
    "Pieter Van Gorp" <[email protected]> wrote in message
    news:[email protected]..
    (Here's another one):
    I'm unable to find a way to enable method-level locking in WebLogic.
    This kind of lock has the same semantics as a simple "synchronized" on the
    method level (which you cannot write as a bean developer). The advantageis
    that you've got thread-safe access to a method without expensively
    interfering with the transaction manager.
    So is this possible in WLS v6.1/v7.0?
    Regards,
    Pieter Van Gorp.

Maybe you are looking for