Line lock

Similar Questions

• [ORACLE 10.2.0.5] performance problem with high enq: TX - line lock contention waiting

  Hello

  I have a performance problem involving high line response to locking conflicts that I can't wait.

  The application updates the specific table about 1200 times for my AWR report representing 2 hours.

  This update represents 98% of the db_time and wait to enq: TX - line lock conflict is:

  -83 796 waiting

  -245 441 seconds

  The application updates a row both an unprecedented SELECT UPDATES. This is the query:

  Update my_table set creationtime =: 1, modificationdate =: version 2, =: creationuserid 3, =: fortesting 4, =: 5, modificationuserid =: participation_uuid 6, =: actimenucontact 7, =: allegroid 8, =: campaign_uuid 9, =: desjardinsemployeetype 10, =: effectiveparticipationtype 11, =: family_uuid 12, =: fetchpasseport 13, =: 14, healthratingfilldate =: hoursofsleeptimecommitment 15, =: igaid 16, =: initialsubscriptiontype 17, =: minutesofsleeptimecommitment 18, =: goal 19, =: partner_uuid 20, =: 21, promotionalemails =: 22, readrules =: sccsubscriptionprovenance 23, =: = subscriptionprovenance 24,: 25, supportemails =: where the 26 uuid = : 27 and = version: 28

  Clause where is filtering on uuid which is the primary key of my_table.

  The uuid is a specific user and two users would not update the same row, what could be the reason for this wait event?

  Thank you

  Why guess when you know.

  Watch ASH data for these events to the queue.

  He'll tell you sql id as well.

• How to find resulting sql ' enq: TX - line lock conflict.

  Hello
  
  In one of our database we still find "enq: TX - line lock conflict" for 2-3 days. But then he stopped. Time it happened he blocked other sessions for a long while and he got is resolved automatically. Now the ADDM report, we have sql queries that has waited for this but, we cannot find that question of what module caused the outcome. What I should look for that, beyond the information. Help, please.
  
  Database is 10 gr 2 on AIX.
  
  Kind regards
  Chaouki

  Hello
  Have you tried querying DBA_HIST_ACTIVE_SESS_HISTORY with event WHERE as "enq: TX %' ?" This should return the lines for the duration of that event (hold/lock) was underway. See column BLOCKING_SESSION which will tell you the session ID that blocked and caused this wait event/lock.

  Now again ask DBA_HIST_ACTIVE_SESS_HISTORY with session_id = .

  Here, you should see SQLs executed by this session "blocking". Take this list of SQLs and use v$ sql or AWR report using the awrsqrpt.sql script to see the details of each of these SQLs and this should help you find SQL blocking. DBA_HIST_ACTIVE_SESS_HISTORY also shows the module where this session/sql has been executed.

  Salman

• Width of line lock?

  I just got adobe ink & Slide and started to use it with the application Adobe Illustrator drawing. I wonder if it is possible to lock the width of the line: you chose, instead of having the stroke vary with your pen/stylus pressure? Please let me know if you have something!

  Thank you!

  Hi Francisco,.

  You use the most recent version (3.3) of the draw? In this version, there is a menu of settings of the brush. To access he tap any of the brushes in the Toolbox; It's at the bottom of the menu color.

  I would like to know if that's what you're looking for.

  Sue.

• Line lock error

  Hello

  We get the following error when the API call.

  Api Hr_Assignment_Api.Update_Emp_Asg

  -Step8.2 - Ora-20001: the current

  Line is locked Cause: you are

  Attempt to lock A row the

  Table of Per_All_Assignments_F which is

  Currently locked by another

  User.    Action: Re-interview and

  Try to block new line

  Although the API works successfully.we receive an error message.

  Please can you advice why we get the above error.

  Kind regards

  Jean Michel.

  Hi Patrice,

  The simple error message said, that someone else is also of/development help to update the same record that you are trying to update.

  Please ensure that no other person accesses the same person of front-end (or same dorsal).

  Thank you

  Vignesh

• Problem with the compatible version of line lock tables

  I tested the effect of locking in the tables in activated version to assess restrictions workspace manager to update the records in different workspaces and I met a locking issue where I can't seem to update different registers of the same table in different sessions if these same records have already been updated and committed in a different workspace.

  I run the tests on 11.2.0.3.  I have ROW_LEVEL_LOCKING worth IT.

  Here's a simple test case (I have many other test cases that are not as well, but understand why it is a problem of blocking will help me understand the results of others my test case):

  -Alter tablespace names in accordance with the requirements

  create table t1 (id varchar2 (36) not null, name varchar2 (50) not null) tablespace XXX;

  ALTER table t1 add the key primary t1_pk (id) of constraint using index tablespace XXX;

  exec ('LIVE') dbms_wm.gotoworkspace;

  insert into t1 values ('1 ', 'name1');

  insert into t1 values ('2 ', 'name2');

  insert into t1 values ('3 ', 'name3');

  commit;

  exec dbms_wm.enableversioning ('t1');

  exec ('LIVE') dbms_wm.gotoworkspace;

  exec dbms_wm.createworkspace ('TESTWSM1');

  exec dbms_wm.gotoworkspace ('TESTWSM1');

  -Update 2 files in a workspace not LIVING for the update later in different workspaces

  Update t1 set name = name | ' changed ' where id in ('1 ', ' 2');

  commit;

  quit smoking;

  -Now in a separate session (called session 1 for this example), run the following without commit the changes:

  exec ('LIVE') dbms_wm.gotoworkspace;

  Update t1 set name = 'modified' where id = '1';

  -Now in another session (session 2) update a different record in the same table.  The update below is blocked waiting on the transaction in the session 1 to perform (by commit / rollback):

  exec ('LIVE') dbms_wm.gotoworkspace;

  Update t1 set name = 'modified' where id = '2';

  I am surprised, recordings of the different IDS cannot be updated in different sessions which is why is session 1 blocking the update of the 2 folder that is not being updated anywhere else.  I tried this using different workspaces not LIVING with similar results.  I tried to change the properties of the table for example, initrans with and always get a lock.  Changes made to the properties of the table are correctly propagated to _LT tables but not all tables in handler related workspace created for table T1 that precedes.  I don't know if that's the problem.

  Note an example of the query Manager space background likely to create the lock is something like:

  UPDATE TESTWSM. T1_LT SET LTLOCK = WMSYS.LT_CTX_PKG. CHECKNGETLOCK (: B6, LTLOCK, NEXTVER,: B3, 0, 'UPDATE', VERSION, DELSTATUS,: B5), NEXTVER = WMSYS.LT_CTX_PKG. GETNEXTVER (NEXTVER,: B4, VERSION,: B3: B2, 683) WHERE ROWID =: B1

  Any help with this will be appreciated.  Thanks in advance.

  Hello

  The reason for the block is actually the same as above.  The splits is registered at the level of the version/savepoint, not necessarily just the workspace.  In your example, workspaces TESTWSM1 and TESTWSM2 have a single version and the LIVE workspace has 3 versions.  A new version is always implicitly created during a CreateWorkspace operation if the most RECENT/current version has modified data.  The lines for the id = "1" and id = "2" are changed in each workspace to the child and before creating a workspace.  However, since the id = "3" LIVE online has changed after the creation of TESTWSM1, it is in a different version of those other 2 rows.  So when the updates for the id = "1" and id = "2" are executed, the line is attempted to be divided between TESTWSM1, TESTWSM2 and the latest version of LIVE.  No other line has been updated with this combination so we try to introduce a set of lines in the metadata table.  As this happens multiple sessions at the same time, one of them is obliged to block until the other transaction issues a commit or rollback.

  It is not a way to avoid these LMD.  The lock is acquired in this case is a short-lived transaction lock and they are required for the correct rows be returned for a particular workspace.

  Kind regards

  Ben

• The implementation of the exclusive line locking in Oracle

  Hi all
  
  Since the beginning of learning Oracle, I've known that oracle has no row-level lock. Row level locking is achieved by ITL in the header of the block.
  In this context, I am curious how statement "lock table in exclusive mode of line" is implemented? Update for all ITLs lines all the blocks belonging to the table?
  
  Best regards
  Leon

  I'm not sure what you mean by Oracle has no blockage at the level of the lines. Line level Oracle most certainly is a lock. A single line in a table can be locked without blocking the other lines of the table, or even of other lines in the same block.

  You are right that this works through the ITL. When a DML is run, if a session doesn't has not already open transaction, Oracle will create one, by booking a slot/segment/wrap in the rollback segment header. Then, in the block where the line should be blocked, an ITL slot is reserved in the block header, that contains this transaction id, essentially pointing to this location of rollback segment. Now, to lock a specific line in the directory of the line, there is a byte of the lock. The locking byte is either 0, which means that the row is not locked, or she will 1.n value, where n is the number of ITL sites reserved in the block header. Thus, if the locking byte is not null, it points to slot ITL of the transaction that holds the lock. So, you can see that it is very easy for a transaction lock a single line in a block, or all lines in the block. Simply set the byte corresponding to the ITL (s) appropriate locking.

  This fact implies, it is that Oracle has no "centralized list of the locks on level line. Row-level locks are inherent in the structure of datablock, as stated above.

  Hope the helps to clarify your understanding.

  -Mark

• ENQ: TX - line lock conflict

  Hello
  
  We have enq: TX - conflict in line with update sql .a lock single session blocks the rest for a long period of time
  
  Here's the sql code
  
  ' Client UPDATE SET CUST_NUM = CUST_NUM +: B2 WHERE TABLE_NAME =: B1 '
  
  
  could you tell me, how do I solve this problem
  
  
  Thank you

  Try to use the DBA_BLOCKERS view to retrieve the blocking database session. As already said must COMMIT to this session blocking or ROLLBACK. In some cases, it may be necessary to kill the blocking of the database session, but you need to know the risk.

• line lock hiding

  Hi all
  
  DB version is 10.2.0.4
  
  In the AWR 5 Albums waiting events report, I could see wait event "locking of cache line. Searched in google and got the below
  

  SQL> select p1text,p1,p2text,p2,p3text,p3 from v$session where event = 'row cache lock';
  
  P1TEXT                       P1 P2TEXT                       P2 P3TEXT                                                                   P3
  -------------------- ---------- -------------------- ---------- ---------------------------------------------------------------- ----------
  cache id                     16 mode                          0 request                                                                   3
  
  1 row selected.
  
  SQL> select PARAMETER ,COUNT ,GETS ,GETMISSES ,MODIFICATIONS from v$rowcache where cache#=16;
  
  PARAMETER                             COUNT       GETS  GETMISSES MODIFICATIONS
  -------------------------------- ---------- ---------- ---------- -------------
  dc_histogram_defs                      1704   47481213   11479508          5408
  dc_histogram_data                       218    8211149    1277649             0
  dc_histogram_data                        83    2668657     301607             0
  
  3 rows selected.
  
  SQL> SELECT parameter, sum(gets), sum(getmisses), 100*sum(gets - getmisses) / sum(gets) pct_succ_gets, sum(modifications) updates FROM V$ROWCACHE WHERE gets > 0 GROUP BY parameter;
  
  PARAMETER                         SUM(GETS) SUM(GETMISSES) PCT_SUCC_GETS    UPDATES
  -------------------------------- ---------- -------------- ------------- ----------
  dc_constraints                         7468           4954    33.6636315       7468
  dc_free_extents                         578            445    23.0103806        178
  dc_tablespaces                     82731475          12753    99.9845851          0
  dc_tablespace_quotas                  41635           2672    93.5823226        110
  dc_awr_control                         1774            856    51.7474634         30
  dc_object_grants                   16804751         315710    98.1213051          0
  dc_histogram_data                  10893968        1582368    85.4748242          0
  dc_rollback_segments                4721434            934    99.9802179        606
  dc_sequences                         123169          46953    61.8792066     123169
  dc_usernames                       12046759          82141    99.3181486          0
  dc_segments                        43854408        3208602    92.6835131      32483
  dc_objects                         19096430        2728645    85.7112298       6698
  dc_database_links                    231247           1383    99.4019382          0
  dc_histogram_defs                  47588238       11511573    75.8100458       5408
  dc_table_scns                         77108          12028    84.4010998        128
  dc_used_extents                          71             45    36.6197183         71
  dc_users                          132473881          75854    99.9427404          0
  outstanding_alerts                     8387           7779    7.24931442         29
  dc_files                               2904           1072    63.0853994          0
  dc_object_ids                     277958942        3175244    98.8576572        831
  dc_global_oids                      1683020          46540    97.2347328          0
  kqlsubheap_object                     77217           3211    95.8415893          0
  dc_profiles                          150822           3056    97.9737704          0
  global database name                     22              7    68.1818182          0
  
  24 rows selected.

  Source: http://surachartopun.com/2009/11/investigate-row-cache-lock.html
  
  How can I solve this lock cache on dc_histogram_defs and dc_histogram_data line?
  
  Baskar.l
  

• Lines, locked in a table

  DB Version: 10 g 2, 11G
  
  Within a single session, for a table, is it possible to determine the number of rows locked in this table?

  -See lock it related information

  Select OS_USER_NAME os_user,
  PROCESS os_pid,
  ORACLE_USERNAME oracle_user,
  l.SID oracle_id,
  decode (TYPE,
  "SIR', 'Media Recovery."
  "RT", "redo the wire."
  A ', 'username ',.
  "TX", "Transaction."
  "TM", "DML"
  "UL", "PL/SQL User Lock."
  "DX", "Xaction distributed."
  "CF", "control file."
  'IS', 'State of the Instance.
  "FS", "file Set."
  "EI", "Instance recovery."
  "ST', 'disk space Operation."
  "TS", "Temp Segment."
  'IV', 'Library Cache Invalidation',
  "LS', 'Start or Switch Journal."
  "RW", "rank waiting."
  "SQ", "Sequence number",
  "TE", "expand the table."
  'TT', 'Table Temp', type) type of lock.
  decode (LMODE,
  0, 'none. '
  1, "null."
  2, "line-S (SS).
  3, 'Row - X (SX).
  4, "action."
  5, row/s-X (SSX)',
  Lock_held 6, 'exclusive', lmode);
  decode (REQUEST,
  0, 'none. '
  1, "null."
  2, "line-S (SS).
  3, 'Row - X (SX).
  4, "action."
  5, row/s-X (SSX)',
  Lock_requested 6, 'exclusive', ask).
  decode (BLOCK,
  0, "Do not block",
  1, 'blocking',
  State 2, 'global', block),
  OWNER,
  OBJECT_NAME
  v $ locked_object lo,.
  DBA_OBJECTS do,
  v$ lock l
  If lo. Object_id = do. OBJECT_ID
  AND l.SID = OL. SESSION_ID;

  Concerning
  Asif Kabir

• Failure to get the db line lock: ORA-01157

  Hello

  I have a client that uses that the customer is using Oracle Database 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production with the partitioning, Real Application Clusters, Automatic Storage Management. An application has been installed recently in which scripts created a .dbf file instead of save on the disk group. So if I run the query I see the following output below

  SQL> select name from v$datafile;
  NAME
  --------------------------------------------------------------------------------
  +RIAMSTG_DBF1/riamstg/datafile/oamstg_mds.259.821014833
  +RIAMSTG_DBF1/riamstg/datafile/oamstg_ias_opss.256.821014833
  +RIAMSTG_DBF1/riamstg/datafile/oamstg_oam.274.821014833
  +RIAMSTG_DBF1/riamstg/datafile/oamstg_ias_iau.276.821014835
  +RIAMSTG_DBF1/riamstg/datafile/bistg_mds.279.821875255
  +RIAMSTG_DBF1/riamstg/datafile/bistg_biplatform.278.821875255
  /db/oracle/112/db/dbhome_1/dbs/rbacx.dbf
  

  Now, when we reboot the DB we see the error below.

  ORA-01157: cannot identify/lock data file 18 - see DBWR trace file
  ORA-01110: data file 18: '/db/oracle/112/db/dbhome_1/dbs/rbacx.dbf'
  ORA-27037: unable to obtain file status
  Linux-x86_64 Error: 2: No such file or directory
  

  In my view, that the error may be related to the .dbf file. How can I move this ASM format?

  -Extreme

  It should be ALTER TABLESPACE OFFLINE RBACX without the single quotation mark character.   (I had the character to reach the unknown tbsname).

  Hemant K Collette

• ERROR LOCKING line seems to have been inserted in AD_ADOP_SESSIONS by another session

  Hi all

  Previously, I tried to apply a patch. During the process, there was a network error.

  I tried to reapply the patch by using this command: = phase prepare, apply, finalize, commissioning, clean jobs = restart 18620668 = yes

  Unfortunately, adopted out with status = 1 (failure)

  It's my data from the environment:

  EBS 12.2.4

  Database version 11.2.0.4

  OS: Oracle Linux 6

  adopscanlog-latest = Yes command output:

  Directory/u01/install/APPS/fs_ne/EBSapps/log/adoption/33/scan...

  /U01/install/apps/fs_ne/EBSapps/log/adop/33/adop_20150727_070102.log:

  ---------------------------------------------------------------------

  #(202-206) lines:

  ADPATCH logs directory: / u01/install/APPS/fs_ne/EBSapps/log/adoption/33/cutover_20150727_070102/DEV1_spaderp-dev1-app/log

  [PROCEDURE] Race: options adpatch /hotpatch, interactive nocompiledb = no = no console only = no workers = 1 restart no = no = abandonment Yes defaultsfile=/u01/install/APPS/fs2/EBSapps/appl/admin/DEV1_patch/adalldefaults.txt patchtop=/u01/install/APPS/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile = cutover.log driver = ucutover.drv acp = yes

  [UNEXPECTED] Error occurred during execution of CUTOVER.

  [UNEXPECTED] Implementation phase completed with errors/warnings. Check the log files

  #(204-208) lines:

  [UNEXPECTED] Error occurred during execution of CUTOVER.

  [UNEXPECTED] Implementation phase completed with errors/warnings. Check the log files

  [STATEMENT] Phase SHIFT END TIME: 27/07/2015-07:08:18

  [PROCEDURE] [EARLY 2015/07/27 07:08:18] Unlock sessions table

  /U01/install/apps/fs_ne/EBSapps/log/adop/33/finalize_20150727_070102/DEV1_spaderp-dev1-app/adzdshowlog.out:

  -----------------------------------------------------------------------------------------------------------

  #(517-521) lines:

  3451979 05:15:37 00:00:00 ad.bin.adop absorbent of PROCEDURE [START] lock on the sessions table

  3451979 05:15:37 table 00:00:00 ad.bin.adop STATEMENT locking ad_adop_sessions spaderp-dev1-app with interval of 60 seconds and the number of trials 2

  3451979 05:17:37 00:02:00 AD_ZD_ADOP. LOCK_SESSIONS_TABLE error: impossible to acquire the lock on the table to ad_adop_sessions.

  3451979 05:17:37 AD_ZD_ADOP 00:00:00. LOCK_SESSIONS_TABLE ERROR in line LOCK seems to have been inserted in AD_ADOP_SESSIONS by another session

  3451979 05:17:37 00:00:00 ad.bin.adop ERROR cannot execute the SQL statement:

  Hello.

  Bashar and Krishna,

  Thanks for your replies. I solved this problem by referring to the document and steps as breakfast by Oracle Support:

  Search for 0) locked sessions

  Select * from ad_adop_sessions where EDITION_NAME = "LOCK."

  (1) ad_adop_sessions backup:

  create the table ad_adop_sessions_bkp in select * from ad_adop_sessions;

  delete from ad_adop_sessions where adop_session_id = and EDITION_NAME = "LOCK."

  commit;

  (2) unlock the session:

  Start

  AD_ZD_ADOP. LOCK_SESSIONS_TABLE('spaderp-dev1-app',60,2);

  end;

  /

  (3) back up and delete the table APPLSYS. FND_INSTALL_PROCESSES;

  (4) restart adoption phase = failover and update the result

  5) next steps follow this document --> after applying the AD/T2K patches on 12.2.0, adoption phase = failover is a failure on startup of Apache OSH - time (Doc ID 1952008.1)

• Ignore the first n lines with locked back.

  TimesTen is used from Java using the client-server access. We need to replicate the lines of TimesTen to a different database.
  
  We have lines of parallel job processing. During the treatment, the rows are locked:
  
  N FIRST SELECT * FROM TABLE_X FOR UPDATE
  
  The problem is that the first task selects and locks the first n rows and other jobs must wait until the locks are released. Is it possible to skip lines locked, so the other jobs would choose another set of lines.
  
  With Oracle, this can be accomplished by using the SKIP LOCKED clause. Locked IS NULL clause with SQL Server by using WHERE.
  
  Is it possible to have this kind of behavior in TimesTen?
  
  Is there another solution for replication of the lines? XLA API seems to be for this, but it seems a little complicated and use the direct access, which is not appropriate for our facility.
  
  Thank you

  Unfortunately, TimesTen doesn't have an option to ignore locked rows. I'm guessing that the "another database" is not Oracle? In this case, you can use a cache AWT group. XLA (or JMS/XLA for Java) really is the best option to "reproduce" in terms of performance, etc.. It is true that use the component which performs the "replication" to run on the computer where TimesTen runs, but the rest of the application would not have to do. Live view you the spirit gives much better performance :-)

  If you really need to do it through SQL, then you will need to find a way to get different jobs watch different sets of rows without locking up. Exactly how you could of course a lot depends on the application and exactly what he's trying to do. One approach would be to have a column in the table to identify what "Replicator" currently dealing line. You can use NULL means that it is not being processed and an ID value (could just be a number) to indicate that Replicator 1 (or 2 or 3 or...) is the treatment. Replicator ' wouldn't 'reserve' a set of rows to update it column "n" and commit. He would then do its job and then update the column again to another value which means "made replication." This can work very well or may not depending on what the application should do with lines, etc.

  Chris

• Identify an impasse resources graphic with 1 line and 1 table lock

  Hi, I ran into occurrences repeated event deadlock graph at the bottom of this post and a few questions about this:
  
  1. it seems that proc 44, session 548 holds a line lock (X). Is the boy, proc. 30, session 542, is trying to acquire a lock line (X) also or an exclusive table (X) on the table lock that contains this line?
  2. under what circumstances would be something keep an exclusive table lock on line (SX) and to upgrade that to an exclusive table lock part (SSX) online?
  3. our cxml_foldercontent table contains a column "structuredDataId" with a cxml_structureddata.id FK and a trigger ON DELETE SET NULL. This would help to explain why a "update" for a table (i.e.g cxml_foldercontent) would also need to acquire a lock on a foreign table, cxml_structureddata?
  4. What is the difference between "current SQL statement:" and "for the session current SQL statement:"? This terminology is confusing. Session 542 running "update" or "delete"?
  5. in the ' waiting lines: "section is - this mean 542 Session expected on obj - rowid = 0000BE63 - AAAL5jAAGAAA6tZAAK or that it is has the lock on the same row, and other things are waiting on this subject?
  
  A couple of notes:
  -the cxml_foldercontent.structuredDataId FK column already has a clue on this subject
  

  Deadlock graph:
                         ---------Blocker(s)--------  ---------Waiter(s)---------
  Resource Name                    process session holds waits  process session holds waits
  TX-003a0011-000003d0        44       548     X               30        542             X
  TM-0000be63-00000000       30       542     SX              44        548     SX    SSX
  session 548: DID 0001-002C-000002D9     session 542: DID 0001-001E-00000050
  session 542: DID 0001-001E-00000050     session 548: DID 0001-002C-000002D9
  Rows waited on:
  Session 542: obj - rowid = 0000BE63 - AAAL5jAAGAAA6tZAAK
    (dictionary objn - 48739, file - 6, block - 240473, slot - 10)
  Session 548: no row
  Information on the OTHER waiting sessions:
  Session 542:
    pid=30 serial=63708 audsid=143708731 user: 41/CASCADE
    O/S info: user: cascade, term: unknown, ospid: 1234, machine: 
              program: JDBC Thin Client
    application name: JDBC Thin Client, hash value=2546894660
    Current SQL Statement:
  
  update cascade.cxml_foldercontent set name=:1 , lockId=:2 , isCurrentVersion=:3 , versionDate=:4 , metadataId=:5 , permissionsId=:6 , workflowId=:7 , isWorkingCopy=:8 , parentFolderId=:9 , relativeOrder=:10 , cachePath=:11 , isRecycled=:12 , recycleRecordId=:13 , workflowComment=:14 , draftUserId=:15 , siteId=:16 , prevVersionId=:17 , nextVersionId=:18 , originalCopyId=:19 , workingCopyId=:20 , displayName=:21 , title=:22 , summary=:23 , teaser=:24 , keywords=:25 , description=:26 , author=:27 , startDate=:28 , endDate=:29 , reviewDate=:30 , metadataSetId=:31 , expirationNoticeSent=:32 , firstExpirationWarningSent=:33 , secondExpirationWarningSent=:34 , expirationFolderId=:35 , maintainAbsoluteLinks=:36 , xmlId=:37 , structuredDataDefinitionId=:38 , pageConfigurationSetId=:39 , pageDefaultConfigurationId=:40 , structuredDataId=:41 , pageStructuredDataVersion=:42 , shouldBeIndexed=:43 , shouldBePublished=:44 , lastDatePublished=:45 , lastPublishedBy=:46 , draftOriginalId=:47 , contentTypeId=:48  where id=:49
  End of information on OTHER waiting sessions.
  Current SQL statement for this session:
  delete from cascade.cxml_structureddata where id=:1

  That basically there a sense today?

  Lol your description is more on linked in memory on relational tables and indexes lists!

  This means that there is a more verbose parameter for these traces of the impasse?

  Lol other SQLs would also be included in the deadlock trace.

  Hemant K Collette

• SELECT... FOR the vs LOCK TABLE of UPDATE... MODE OF LINE SHARING IN

  Hello
  In practice, what is the difference between the two versions of line locking methods...?
  In my case, I need to block only the lines that will be extracted by a cursor... but because the select stmt using the sum aggregate function... I can't use the format:

  cursor c1 
  
   is
  
    select x , y ,sum(a)
  
      from d
  
     group by x,y
  
      for update;

  So, the only alternative I have (I think) is the "LOCK TABLE d PART of the LINE in MODE.
  Is the above correct... to obtain row locks the same as the "select" for the update?
  
  Note: I use Db10g v.2
  Thank you
  SIM

  When you draw a select... Updated, it's immediately another session in standby mode until you release the lock.
  TABLE LOCK is a bit different, the other session will run in standby mode after an UPDATE statement. If the other session, run an UPDATE statement before your own session, you will wait for the release lock.
  So, it's different behaviors. Conclusion: they are not same.

  Nicolas.