P1ERP4 Blocking Locks found

SID=1478 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA) is
blocking SID=1549 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA)
SID=1463 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA) is
blocking SID=1513 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA)
SID=1463 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA) is
blocking SID=1430 (ssibeConsolidatedCheckoutProcessor.jsp-3941;IBE_JAVA)
SID=1463 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA) is
blocking SID=1454 (ssibeConsolidatedCheckoutProcessor.jsp-3941;IBE_JAVA)
SID=1463 (ssibeConsolidatedCheckoutProcessor.jsp-31677;IBE_JAVA) is
blocking SID=1447 (ssibeConsolidatedCheckoutProcessor.jsp-3941;IBE_JAVA)
Associated Trace File :
INSERT INTO OE_PRICE_ADJUSTMENTS ( PRICE_ADJUSTMENT_ID , CREATION_DATE , CREATED_BY , LAST_UPDATE_DATE , LAST_UPDATED_BY , LAST_UPDATE_LOGIN , PROGRAM_APPLICATION_ID , PROGRAM_ID , PROGRAM_UPDATE_DATE , REQUEST_ID , HEADER_ID , DISCOUNT_ID , DISCOUNT_LINE_ID , AUTOMATIC_FLAG , PERCENT , LINE_ID , CONTEXT , ATTRIBUTE1 , ATTRIBUTE2 , ATTRIBUTE3 , ATTRIBUTE4 , ATTRIBUTE5 , ATTRIBUTE6 , ATTRIBUTE7 , ATTRIBUTE8 , ATTRIBUTE9 , ATTRIBUTE10 , ATTRIBUTE11 , ATTRIBUTE12 , ATTRIBUTE13 , ATTRIBUTE14 , ATTRIBUTE15 , ORIG_SYS_DISCOUNT_REF , LIST_HEADER_ID , LIST_LINE_ID , LIST_LINE_TYPE_CODE , MODIFIER_MECHANISM_TYPE_CODE , MODIFIED_FROM , MODIFIED_TO , UPDATED_FLAG , UPDATE_ALLOWED , APPLIED_FLAG , CHANGE_REASON_CODE , CHANGE_REASON_TEXT , OPERAND , ARITHMETIC_OPERATOR , COST_ID , TAX_CODE , TAX_EXEMPT_FLAG , TAX_EXEMPT_NUMBER , TAX_EXEMPT_REASON_CODE , PARENT_ADJUSTMENT_ID , INVOICED_FLAG , ESTIMATED_FLAG , INC_IN_SALES_PERFORMANCE , SPLIT_ACTION_CODE , ADJUSTED_AMOUNT , PRICING_PHASE_ID , CHARGE_TYPE_CODE , CHARGE_SUBTYPE_CODE , LIST_LINE_NO , SOURCE_SYSTEM_CODE , BENEFIT_QTY , BENEFIT_UOM_CODE , PRINT_ON_INVOICE_FLAG , EXPIRATION_DATE , REBATE_TRANSACTION_TYPE_CODE , REBATE_TRANSACTION_REFERENCE , REBATE_PAYMENT_SYSTEM_CODE , REDEEMED_DATE , REDEEMED_FLAG , ACCRUAL_FLAG , RANGE_BREAK_QUANTITY , ACCRUAL_CONVERSION_RATE , PRICING_GROUP_SEQUENCE , MODIFIER_LEVEL_CODE , PRICE_BREAK_TYPE_CODE , SUBSTITUTION_ATTRIBUTE , PRORATION_TYPE_CODE , CREDIT_OR_CHARGE_FLAG , INCLUDE_ON_RETURNS_FLAG , AC_CONTEXT , AC_ATTRIBUTE1 , AC_ATTRIBUTE2 , AC_ATTRIBUTE3 , AC_ATTRIBUTE4 , AC_ATTRIBUTE5 , AC_ATTRIBUTE6 , AC_ATTRIBUTE7 , AC_ATTRIBUTE8 , AC_ATTRIBUTE9 , AC_ATTRIBUTE10 , AC_ATTRIBUTE11 , AC_ATTRIBUTE12 , AC_ATTRIBUTE13 , AC_ATTRIBUTE14 , AC_ATTRIBUTE15 , OPERAND_PER_PQTY , ADJUSTED_AMOUNT_PER_PQTY , INVOICED_AMOUNT , LOCK_CONTROL ) VALUES ( :B101 , :B100 , :B99 , :B98 , :B97 , :B96 , :B95 , :B94 , :B93 , :B92 , :B91 , :B90 , :B89 , :B88 , :B87 , :B86 , :B85 , :B84 , :B83 , :B82 , :B81 , :B80 , :B79 , :B78 , :B77 , :B76 , :B75 , :B74 , :B73 , :B72 , :B71 , :B70 , :B69 , :B68 , :B67 , :B66 , :B65 , :B64 , :B63 , :B62 , :B61 , :B60 , :B59 , :B58 , :B57 , :B56 , :B55 , :B54 , :B53 , :B52 , :B51 , :B50 , :B49 , :B48 , :B47 , :B46 , :B45 , :B44 , :B43 , :B42 , :B41 , :B40 , :B39 , :B38 , :B37 , :B36 , :B35 , :B34 , :B33 , :B32 , :B31 , :B30 , :B29 , :B28 , :B27 , :B26 , :B25 , :B24 , :B23 , :B22 , :B21 , :B20 , :B19 , :B18 , :B17 , :B16 , :B15 , :B14 , :B13 , :B12 , :B11 , :B10 , :B9 , :B8 , :B7 , :B6 , :B5 , :B4 , :B3 , :B2 , :B1 )
ENQUEUE DUMP REQUEST: from 3.14182 on [0x660022][0x3c5d5],[TX] for reason 3 mtype 0
DUMP LOCAL BLOCKER/HOLDER: block level 5 res [0x660022][0x3c5d5],[TX]
----------resource 0x0x18aeb1920----------------------
resname : [0x660022][0x3c5d5],[TX]
Local node : 0
dir_node : 3
master_node : 3
hv idx : 75
hv last r.inc : 6
current inc : 8
hv status : 0
hv master : 0
open options : dd
Held mode : KJUSERNL
Cvt mode : KJUSERPR
Next Cvt mode : KJUSERNL
msg_seq : 0x1
res_seq : 59
grant_bits : KJUSERNL
grant mode : KJUSERNL KJUSERCR KJUSERCW KJUSERPR KJUSERPW KJUSEREX
count : 2 0 0 0 0 0
val_state : KJUSERVS_NOVALUE
valblk : 0x00000000000000000000000000000000 .
access_node : 3
vbreq_state : 0
state : x8
resp : 0x18aeb1920
On Scan_q? : N
Total accesses: 531
Imm. accesses: 372
Granted_locks : 0
Cvting_locks : 2
value_block: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
CONVERT_Q:
lp 0x19a0d87e0 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db46990 possible pid 14841 xid 8B000-0001-0000085F bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
lp 0x19baf40b8 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db01070 possible pid 6112 xid 7C000-0001-0000057A bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
----------enqueue 0x0x19a0d87e0------------------------
lock version : 736153
Owner node : 0
grant_level : KJUSERNL
req_level : KJUSERPR
bast_level : KJUSERNL
notify_func : (nil)
resp : 0x18aeb1920
procp : 0x19c9bc990
pid : 14841
proc version : 186
oprocp : (nil)
opid : 0
group lock owner : 0x19db46990
possible pid : 14841
xid : 8B000-0001-0000085F
dd_time : 60.0 secs
dd_count : 3
timeout : 0.0 secs
On_timer_q? : N
On_dd_q? : Y
lock_state : OPENING CONVERTING
Open Options : KJUSERDEADLOCK
Convert options : KJUSERGETVALUE
History : 0x1495149a
Msg_Seq : 0x0
res_seq : 59
valblk : 0x00000000000000000000000000000000 .
DUMP LOCAL BLOCKER: initiate state dump for DEADLOCK
possible owner[139.14841] on resource TX-00660022-0003C5D5
Submitting asynchronized dump request [28]
user session for deadlock lock 0x19a0d87e0
pid=139 serial=45298 audsid=162419588 user: 55/APPS
O/S info: user: p1applerp, term: unknown, ospid: 3941, machine: s3-perp.sitestuff.com
program: JDBC Thin Client
client info: 2 0
application name: ssibeConsolidatedCheckoutProcessor.jsp, hash value=4021281913
action name: 3941;IBE_JAVA, hash value=3111884307
Current SQL Statement:
INSERT INTO OE_PRICE_ADJUSTMENTS ( PRICE_ADJUSTMENT_ID , CREATION_DATE , CREATED_BY , LAST_UPDATE_DATE , LAST_UPDATED_BY , LAST_UPDATE_LOGIN , PROGRAM_APPLICATION_ID , PROGRAM_ID , PROGRAM_UPDATE_DATE , REQUEST_ID , HEADER_ID , DISCOUNT_ID , DISCOUNT_LINE_ID , AUTOMATIC_FLAG , PERCENT , LINE_ID , CONTEXT , ATTRIBUTE1 , ATTRIBUTE2 , ATTRIBUTE3 , ATTRIBUTE4 , ATTRIBUTE5 , ATTRIBUTE6 , ATTRIBUTE7 , ATTRIBUTE8 , ATTRIBUTE9 , ATTRIBUTE10 , ATTRIBUTE11 , ATTRIBUTE12 , ATTRIBUTE13 , ATTRIBUTE14 , ATTRIBUTE15 , ORIG_SYS_DISCOUNT_REF , LIST_HEADER_ID , LIST_LINE_ID , LIST_LINE_TYPE_CODE , MODIFIER_MECHANISM_TYPE_CODE , MODIFIED_FROM , MODIFIED_TO , UPDATED_FLAG , UPDATE_ALLOWED , APPLIED_FLAG , CHANGE_REASON_CODE , CHANGE_REASON_TEXT , OPERAND , ARITHMETIC_OPERATOR , COST_ID , TAX_CODE , TAX_EXEMPT_FLAG , TAX_EXEMPT_NUMBER , TAX_EXEMPT_REASON_CODE , PARENT_ADJUSTMENT_ID , INVOICED_FLAG , ESTIMATED_FLAG , INC_IN_SALES_PERFORMANCE , SPLIT_ACTION_CODE , ADJUSTED_AMOUNT , PRICING_PHASE_ID , CHARGE_TYPE_CODE , CHARGE_SUBTYPE_CODE , LIST_LINE_NO , SOURCE_SYSTEM_CODE , BENEFIT_QTY , BENEFIT_UOM_CODE , PRINT_ON_INVOICE_FLAG , EXPIRATION_DATE , REBATE_TRANSACTION_TYPE_CODE , REBATE_TRANSACTION_REFERENCE , REBATE_PAYMENT_SYSTEM_CODE , REDEEMED_DATE , REDEEMED_FLAG , ACCRUAL_FLAG , RANGE_BREAK_QUANTITY , ACCRUAL_CONVERSION_RATE , PRICING_GROUP_SEQUENCE , MODIFIER_LEVEL_CODE , PRICE_BREAK_TYPE_CODE , SUBSTITUTION_ATTRIBUTE , PRORATION_TYPE_CODE , CREDIT_OR_CHARGE_FLAG , INCLUDE_ON_RETURNS_FLAG , AC_CONTEXT , AC_ATTRIBUTE1 , AC_ATTRIBUTE2 , AC_ATTRIBUTE3 , AC_ATTRIBUTE4 , AC_ATTRIBUTE5 , AC_ATTRIBUTE6 , AC_ATTRIBUTE7 , AC_ATTRIBUTE8 , AC_ATTRIBUTE9 , AC_ATTRIBUTE10 , AC_ATTRIBUTE11 , AC_ATTRIBUTE12 , AC_ATTRIBUTE13 , AC_ATTRIBUTE14 , AC_ATTRIBUTE15 , OPERAND_PER_PQTY , ADJUSTED_AMOUNT_PER_PQTY , INVOICED_AMOUNT , LOCK_CONTROL ) VALUES ( :B101 , :B100 , :B99 , :B98 , :B97 , :B96 , :B95 , :B94 , :B93 , :B92 , :B91 , :B90 , :B89 , :B88 , :B87 , :B86 , :B85 , :B84 , :B83 , :B82 , :B81 , :B80 , :B79 , :B78 , :B77 , :B76 , :B75 , :B74 , :B73 , :B72 , :B71 , :B70 , :B69 , :B68 , :B67 , :B66 , :B65 , :B64 , :B63 , :B62 , :B61 , :B60 , :B59 , :B58 , :B57 , :B56 , :B55 , :B54 , :B53 , :B52 , :B51 , :B50 , :B49 , :B48 , :B47 , :B46 , :B45 , :B44 , :B43 , :B42 , :B41 , :B40 , :B39 , :B38 , :B37 , :B36 , :B35 , :B34 , :B33 , :B32 , :B31 , :B30 , :B29 , :B28 , :B27 , :B26 , :B25 , :B24 , :B23 , :B22 , :B21 , :B20 , :B19 , :B18 , :B17 , :B16 , :B15 , :B14 , :B13 , :B12 , :B11 , :B10 , :B9 , :B8 , :B7 , :B6 , :B5 , :B4 , :B3 , :B2 , :B1 )
Global blockers dump start:---------------------------------
DUMP LOCAL BLOCKER/HOLDER: block level 3 res [0x660022][0x3c5d5],[TX]
----------resource 0x0x18aeb1920----------------------
resname : [0x660022][0x3c5d5],[TX]
Local node : 0
dir_node : 3
master_node : 3
hv idx : 75
hv last r.inc : 6
current inc : 8
hv status : 0
hv master : 0
open options : dd
Held mode : KJUSERNL
Cvt mode : KJUSERPR
Next Cvt mode : KJUSERNL
msg_seq : 0x1
res_seq : 59
grant_bits : KJUSERNL
grant mode : KJUSERNL KJUSERCR KJUSERCW KJUSERPR KJUSERPW KJUSEREX
count : 2 0 0 0 0 0
val_state : KJUSERVS_NOVALUE
valblk : 0x00000000000000000000000000000000 .
access_node : 3
vbreq_state : 0
state : x8
resp : 0x18aeb1920
On Scan_q? : N
Total accesses: 533
Imm. accesses: 373
Granted_locks : 0
Cvting_locks : 2
value_block: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
CONVERT_Q:
lp 0x19a0d87e0 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db46990 possible pid 14841 xid 8B000-0001-0000085F bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
lp 0x19baf40b8 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db01070 possible pid 6112 xid 7C000-0001-0000057A bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
resource object no longer exists. Aborting lock dump
DUMP LOCAL BLOCKER/HOLDER: block level 5 res [0x660022][0x3c5d5],[TX]
----------resource 0x0x18aeb1920----------------------
resname : [0x660022][0x3c5d5],[TX]
Local node : 0
dir_node : 3
master_node : 3
hv idx : 75
hv last r.inc : 6
current inc : 8
hv status : 0
hv master : 0
open options : dd
Held mode : KJUSERNL
Cvt mode : KJUSERPR
Next Cvt mode : KJUSERNL
msg_seq : 0x1
res_seq : 59
grant_bits : KJUSERNL
grant mode : KJUSERNL KJUSERCR KJUSERCW KJUSERPR KJUSERPW KJUSEREX
count : 2 0 0 0 0 0
val_state : KJUSERVS_NOVALUE
valblk : 0x00000000000000000000000000000000 .
access_node : 3
vbreq_state : 0
state : x8
resp : 0x18aeb1920
On Scan_q? : N
Total accesses: 534
Imm. accesses: 373
Granted_locks : 0
Cvting_locks : 2
value_block: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
GRANTED_Q :
CONVERT_Q:
lp 0x19a0d87e0 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db46990 possible pid 14841 xid 8B000-0001-0000085F bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
lp 0x19baf40b8 gl KJUSERNL rl KJUSERPR rp 0x18aeb1920 [0x660022][0x3c5d5],[TX]
master 3 gl owner 0x19db01070 possible pid 6112 xid 7C000-0001-0000057A bast 0 rseq 59 mseq 0 history 0x1495149a
convert opt KJUSERGETVALUE
BLOCKED 0x19a0d87e0 3 wq 2 cvtops x1 [0x660022][0x3c5d5],[TX] [8B000-0001-0000085F] 0
BLOCKER 0x19b7e7080 3 wq 1 cvtops x8 [0x660022][0x3c5d5],[TX] [7F000-0004-00000919] 3
BLOCKED 0x19a0db798 5 wq 2 cvtops x1 [0x6a002d][0x41612],[TX] [7F000-0004-00000919] 3
BLOCKER 0x19a0db648 5 wq 1 cvtops x8 [0x6a002d][0x41612],[TX] [72000-0004-000018AB] 3
BLOCKED 0x19baf44c0 5 wq 2 cvtops x1 [0x660022][0x3c5d5],[TX] [72000-0004-000018AB] 3
BLOCKER 0x19a0d87e0 5 wq 2 cvtops x1 [0x660022][0x3c5d5],[TX] [8B000-0001-0000085F] 0

1. Try to Avoid using LOCK TABLE
2. Use only SELECT ... FOR UPDATE when really needed
3. Try to avoid massive INSERT/UPDATE/DELETE running at the same time on the same rows
In an Oracle database, SELECT without FOR UPDATE clause does not lock rows.
Readers (SELECT) are not blocked by writers (INSERT/UPDATE/DELETE) and vice-versa: only writers are blocked by writers.

Similar Messages

Blocking Locks - What Was Likely Going On?

I had a blocking lock yesterday that showed up in OEM under Cluster Database --> Cluster Database Locks. The blocking lock was a row exclusive (RX) table lock that was blocking 175 other sessions that were listed under the blocking lock as having requested row share (RS) locks. It was an hour before I found out about this problem.
Two questions:
1.] The "Oracle Database Concepts 10gR2" book, Table 13-13, states that a row exclusive (RX) table lock can be obtained as a result of INSERT, UPDATE or DELETE DML and that in RX mode share lock modes are not permitted (which is why I had 175 blocked sessions). Does this mean that a user must have been doing a long running (1 hour plus) INSERT, UPDATE or DELETE or is there another more likely cause that I'm not aware of?
2.] The only ways I know of to request a row share lock (of which 175 were blocked due to the RX lock) is by using:
LOCK_TABLE <table name> IN SHARE MODE;
LOCK_TABLE <table name> IN SHARE EXCLUSIVE MODE;
LOCK_TABLE <table name> IN EXCLUSIVE MODE;
I can't imagine a user doing any of these commands so is there another more likely reason that 175 row share (RX) locks were being requested (and blocked)?
Thanks for any insight you can offer. I ended up killing the session that held the RX lock and that resolved the problem but I'd like to better understand what was happening.

1.] The "Oracle Database Concepts 10gR2" book, Table
13-13, states that a row exclusive (RX) table lock
can be obtained as a result of INSERT, UPDATE or
DELETE DML and that in RX mode share lock modes are
not permittedThat table shows that RS (mode 2) is permitted while RX lock is held.
Did you mean to say that sessions were waiting on a S mode (4) lock?
This could indicate that update/delete was attempted on a parent table and that dependend table was lacking an index on fk column. (may answer your q.2)

How to find out the reason for blocking locks?

PB Application try to create data in ASE 12.5. With this operation, there are sql, sp, trigger involved. Most of the it is okay. With lock of sleeping or sync sleeping lock. User wait for a short time to get the result.
but some time, there are blocking lock.
If spid for the app is 1. then looks like this app also generate another spid, say it is 2. and 2 is blocking by 1. spid 1 holding lock!
then all user is frozen because of spid 1 holding lock!!! How to figure it out the reason for blocking locks?

Thanks, Mark. Yes, sp_lock, sp_who, ... are common tool I used.
I found out one case like:
I have a SP which call a View for data.
When I run this SP, suppose the sipd is 1. then it will create another spid 2 because of access view and it gone very quick. This cause spid 1 block spid 2 within a short time.
If the are many user run the app, the app will be frozen and everyone is waiting. Finally it release, no dead lock, but the performance is not acceptable.
That why I have this question.

Esm Block not found

We get the following error while calculating our essbase cubes on Unix Solaris 8. We have been unable to determine the cause of this error."Need to copy to Esm block during the dynamic calculation. Esm Block not found. Essbase internal error, Please report to Hyperion." Hyperion support have been unable to assist us in the resolution of this problem. It is not related to LOCK BLOCKS, as this has been tested in our development environment.

Do you have a number of stored members that depend on dynamic members? If so, Essbase must dunamically calculate the block(s) or member(s) in order to calcuate the dependents. No doubt there is a bug, but you should be able to at least calculate your database.As a general rule, try to avoid having stored members depend on dynamic ones. As a starting point, remove the Dynamic calc tags and see if the database will calc without generating that error.Regards,Jade------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Script to find blocking locks more than 30 minutes.

Hi Everyone,
Can anyone help me in writing a script where there is a blocking lock for more than 30 minutes ?

Suvi wrote:
Hi Everyone,
Can anyone help me in writing a script where there is a blocking lock for more than 30 minutes ?You can check BLOCKING_SESSION column in V$SESSIONS view and found which session is blocking. Moreover, check SECONDS_IN_WAIT columns as well

Just how bad is these blocked lock chains for performance?

I had the pleasure of participating in load test of an application running on WLS923/J27.6 I stumbled across these blocked lock chains in my JRA thread dumps. And started wondering, is this the bad or very bad? This is from test with somewaht excessive logging.
Blocked lock chains
===================
Chain 2:
"[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'" id=39 idx=0x98 tid=5040 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 3:
"[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'" id=42 idx=0xa4 tid=3600 waiting for java/lang/Class@0x2BC1BCE8 held by:
"[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" id=96 idx=0x17c tid=5252 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 4:
"[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" id=73 idx=0x120 tid=5496 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 5:
"[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'" id=93 idx=0x170 tid=1160 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 6:
"[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" id=94 idx=0x174 tid=4032 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 7:
"[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'" id=97 idx=0x180 tid=2084 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 8:
"[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'" id=98 idx=0x184 tid=5844 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 9:
"[ACTIVE] ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'" id=99 idx=0x188 tid=924 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 10:
"[ACTIVE] ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'" id=100 idx=0x18c tid=5316 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 11:
"[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'" id=102 idx=0x194 tid=4868 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 12:
"[ACTIVE] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" id=103 idx=0x198 tid=5160 waiting for java/lang/Class@0x2BC1BCE8 held by:
"[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" id=96 idx=0x17c tid=5252 in chain 3
Chain 13:
"[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'" id=104 idx=0x19c tid=5192 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 14:
"[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)'" id=105 idx=0x1a0 tid=5224 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 15:
"[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'" id=106 idx=0x1a4 tid=5360 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 16:
"[ACTIVE] ExecuteThread: '21' for queue: 'weblogic.kernel.Default (self-tuning)'" id=108 idx=0x1ac tid=5536 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 17:
"[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'" id=109 idx=0x1b0 tid=5156 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Chain 18:
"[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'" id=112 idx=0x1bc tid=5428 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 in chain 1
Open lock chains
================
Chain 1:
"[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" id=22 idx=0x60 tid=4600 waiting for com/fatcity/logging/RotatingFileLogger@0x2B703780 held by:
"[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" id=107 idx=0x1a8 tid=1720 (active)
Edited by: Allan Andersen on 2010-09-03 06:59

02-Oct-200705:53 PM
joevpt wrote:
You'd think... Eh!
What I found was that at various stages during the upgrade the NSU disconnects from the phone (which allows PC-Suite reconnect). When the NSU needs to reconnect, PC-Suite was holding onto the connection (because, I think, NSU only disconnects it once at the beginning... )
Regards,
Joe
Patheticlly true.

SQL Timeouts and Blocking Locks

SQL Timeouts and Blocking Locks
Just wanted to check in and see if anyone here has feedback on application settings, ColdFusion settings, JBOSS settings or other settings that could help to limit or remove SQL Timeouts and blocking locks on SID's.
We're using MS SQL 2000 with JBOSS and IIS5.
We've been seeing the following error in our logs that starts blocking locks in SQL:
java.sql.SQLException: [newScale] [SQLServer JDBC Drive] [SQLServer] Lock request time out period exceeded.
Once this happens, we're hosed until we remove the blocking SID in SQL. These are the connections to the application.
Any feedback would be great. Thanks!

Hi
This is your exact solution:
Select a.username, a.sid, a.serial#, b.id1, c.sql_text
From v$session a, v$lock b, v$sqltext c
Where b.id1 in( Select distinct e.id1
from v$session d , v$lock e
where d.lockwait = e.kaddr ) and
a.sid = b.sid and
c.hash_value = a.sql_hash_value and
b.request =0;
Thanks
Sarju
Oracle DBA
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by I'm clueless:
Can someone give me the SQL statement to
show if there are any blocking database locks and if so - which user is locking the Database?
Thanks in Advance<HR></BLOCKQUOTE>
null

Monitoring blocking Locks

Hi
This question relates to monitoring blocking locks on a 9.2.0.5 2 node RAC
Origionally I have been monitoring bocking locks with every 5 mins using the following query:
"select * from dba_blockers"
I have recently implemented monitoring via grid control this is running an out of the box metric every 5 mins, the sql behind it is as follows:
"SELECT blocking_sid, num_blocked
FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
FROM ( SELECT l.id1, l.id2,
MAX(DECODE(l.block, 1, i.instance_name||'-'||l.sid,
2, i.instance_name||'-'||l.sid, 0 )) blocking_sid,
SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
FROM gv$lock l, gv$instance i
WHERE ( l.block!= 0 OR l.request > 0 ) AND
l.inst_id = i.inst_id
GROUP BY l.id1, l.id2)
GROUP BY blocking_sid
ORDER BY num_blocked DESC)
WHERE num_blocked != 0 "
Now.. At one point today the alert using "select * from dba_blockers" fired where as the out of the box metric from gird control did not fire.... alert duration was around 5 - 10 mins
At first i simply assumed that this could have been a brief lock and due to both 5 min intervals being out of sync, the lock had shown and cleared before the grid control interval run.
now im a little more curious.
Is there any significan difference in what these 2 different SQL's will alert on, I was under the impression that DBA_BLOCKERS was simply querying a number of joined views, and Oracle had decided to use V$lock for their out of the box metric as it was more efficient.
Any comments welcome
Thanks

Just to prove that the SQL is correct I have constrcuted a demo for you...
SQL> create table t (a char(1));
Table created.
SQL> insert into t values ('z');
1 row created.
SQL> commit;
in session 1 ---->
select * from t where a='z' for update;
==================================================================
in session 2 ---->
update t set a='x' where a='z';
(session simply hangs)
==================================================================
in session 3 ------>
SQL> select * from dba_blockers;
HOLDING_SESSION
48
SQL>
SQL> SELECT blocking_sid, num_blocked
FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
FROM ( SELECT l.id1, l.id2, MAX(DECODE(l.block, 1, i.instance_name||'-'||l.sid,
2, i.instance_name||'-'||l.sid, 0 )) blocking_sid,
SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
FROM gv$lock l, gv$instance i
WHERE ( l.block!= 0 OR l.request > 0 ) AND
l.inst_id = i.inst_id
GROUP BY l.id1, l.id2)
GROUP BY blocking_sid
ORDER BY num_blocked DESC)
WHERE num_blocked != 0;
2 3 4 5 6 7 8 9 10 11 12
BLOCKING_SID NUM_BLOCKED
RAC1-48 1
So back to the origional question,
I am using both these queries from different monitors on my prod syystem, both running on 5 minute intervals, " select * from dba_blockers" fired where as the above query - querying gv$lock did not fire.
Origionaly i assumed that the blocking lock may have simply lasted 3t0 seconds, and due the 5 minute monitor intervals of each metric not being in sync, ... "select * from dba_blockers" may have picked up the lock, then the query selecting from gv$lock ran 2 mins later by which time the lock had disapeared.
-Can anyone suggest any other reasons other than this why one monitor (select * from dba_blockers) picked up the lock and the other (gv$lock) didnt?
Thanks

Monitoring Blocking locks (dba_blockers vs v$lock)

Hi
This question relates to monitoring blocking locks on a 9.2.0.5 database
Origionally I have been monitoring bocking locks with every 5 mins using the following query:
"select * from dba_blockers"
I have recently implemented monitoring via grid control this is running an out of the box metric every 5 mins, the sql behind it is as follows:
"SELECT blocking_sid, num_blocked
FROM ( SELECT blocking_sid, SUM(num_blocked) num_blocked
FROM ( SELECT l.id1, l.id2,
MAX(DECODE(l.block, 1,l.sid,
2,l.sid, 0 )) blocking_sid,
SUM(DECODE(l.request, 0, 0, 1 )) num_blocked
FROM v$lock l
WHERE ( l.block!= 0 OR l.request > 0 ) AND
GROUP BY l.id1, l.id2)
GROUP BY blocking_sid
ORDER BY num_blocked DESC)
WHERE num_blocked != 0 "
Now.. At one point today the alert using "select * from dba_blockers" fired where as the out of the box metric from gird control did not fire.... alert duration was around 5 - 10 mins
At first i simply assumed that this could have been a brief lock and due to both 5 min intervals being out of sync, the lock had shown and cleared before the grid control interval run.
now im a little more curious.
Is there any significan difference in what these 2 different SQL's will alert on (different types of blocking locks / sessions?) , I was under the impression that DBA_BLOCKERS was simply querying a number of joined views, and Oracle had decided to use V$lock for their out of the box metric as it was more efficient.
Any comments welcome
Thanks

Re: Monitoring blocking Locks

Using OleDbDataAdapter Update with InsertCommands and getting blocking locks on Oracle table

The following code snippet shows the use of OleDbDataAdapter with InsertCommands. This code is producing many inserts on the Oracle table and is now suffering from contention... all on the same table. How does the OleDbDataAdapter produce
inserts from a dataset... what characteristics do these inserts inherent in terms of batch behavior... or do they naturally contend for the same resource.
oc.Open();
for (int i = 0; i < xImageId.Count; i++)
// Create the oracle adapter using a SQL which will not return any actual rows just the structure
OleDbDataAdapter da =
   new OleDbDataAdapter("SELECT BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, " +
   "DIRECT_INVOICING, EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE FROM sysadm.PS_RI_INV_PDF_MERG WHERE 1 = 2", oc);
// Create a data set
DataSet ds = new DataSet("documents");
da.Fill(ds, "documents");
// Loop through invoices and write to oracle
string[] sInvoices = invoiceNumber.Split(',');
foreach (string sInvoice in sInvoices)
    // Create a data set row
    DataRow dr = ds.Tables["documents"].NewRow();
    ... map the data
    // Populate the dataset
    ds.Tables["documents"].Rows.Add(dr);
// Create the insert command
string insertCommandText =
    "INSERT /*+ append */ INTO PS_table " +
    "(SEQ_NBR, BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, DIRECT_INVOICING, " +
    "EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE) " +
    "VALUES (INV.nextval, :BUSINESS_UNIT, :INVOICE, :ASSIGNMENT_ID, :END_DT, :RI_TIMECARD_ID, :IMAGE_ID, :FILENAME, " +
    ":BARCODE_LABEL_ID, :DIRECT_INVOICING, :EXCLUDE_FLG, :DTTM_CREATED, :DTTM_MODIFIED, :IMAGE_DATA, :PROCESS_INSTANCE)";
// Add the insert command to the data adapter
da.InsertCommand = new OleDbCommand(insertCommandText);
da.InsertCommand.Connection = oc;
// Add the params to the insert
da.InsertCommand.Parameters.Add(":BUSINESS_UNIT", OleDbType.VarChar, 5, "BUSINESS_UNIT");
da.InsertCommand.Parameters.Add(":INVOICE", OleDbType.VarChar, 22, "INVOICE");
da.InsertCommand.Parameters.Add(":ASSIGNMENT_ID", OleDbType.VarChar, 15, "ASSIGNMENT_ID");
da.InsertCommand.Parameters.Add(":END_DT", OleDbType.Date, 0, "END_DT");
da.InsertCommand.Parameters.Add(":RI_TIMECARD_ID", OleDbType.VarChar, 10, "RI_TIMECARD_ID");
da.InsertCommand.Parameters.Add(":IMAGE_ID", OleDbType.VarChar, 8, "IMAGE_ID");
da.InsertCommand.Parameters.Add(":FILENAME", OleDbType.VarChar, 80, "FILENAME");
da.InsertCommand.Parameters.Add(":BARCODE_LABEL_ID", OleDbType.VarChar, 18, "BARCODE_LABEL_ID");
da.InsertCommand.Parameters.Add(":DIRECT_INVOICING", OleDbType.VarChar, 1, "DIRECT_INVOICING");
da.InsertCommand.Parameters.Add(":EXCLUDE_FLG", OleDbType.VarChar, 1, "EXCLUDE_FLG");
da.InsertCommand.Parameters.Add(":DTTM_CREATED", OleDbType.Date, 0, "DTTM_CREATED");
da.InsertCommand.Parameters.Add(":DTTM_MODIFIED", OleDbType.Date, 0, "DTTM_MODIFIED");
da.InsertCommand.Parameters.Add(":IMAGE_DATA", OleDbType.Binary, System.Convert.ToInt32(filedata.Length), "IMAGE_DATA");
da.InsertCommand.Parameters.Add(":PROCESS_INSTANCE", OleDbType.VarChar, 10, "PROCESS_INSTANCE");
// Update the table
da.Update(ds, "documents");

Here is what Oracle is showing as blocking locks and the SQL that has been identified with each of the SIDS. Not sure why there is contention. There are no triggers or joined tables in this piece of code.
Here is the SQL all of the SIDs below are running:
INSERT INTO sysadm.PS_RI_INV_PDF_MERG (SEQ_NBR, BUSINESS_UNIT, INVOICE, ASSIGNMENT_ID, END_DT, RI_TIMECARD_ID, IMAGE_ID, FILENAME, BARCODE_LABEL_ID, DIRECT_INVOICING, EXCLUDE_FLG, DTTM_CREATED, DTTM_MODIFIED, IMAGE_DATA, PROCESS_INSTANCE) VALUES (SYSADM.INV_PDF_MERG.nextval,
:BUSINESS_UNIT, :INVOICE, :ASSIGNMENT_ID, :END_DT, :RI_TIMECARD_ID, :IMAGE_ID, :FILENAME, :BARCODE_LABEL_ID, :DIRECT_INVOICING, :EXCLUDE_FLG, :DTTM_CREATED, :DTTM_MODIFIED, :IMAGE_DATA, :PROCESS_INSTANCE)
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1150 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1156 (BTSUSER,biztprdi,BTSNTSvc64.exe) in instance FSLX3
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 6 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX2
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 1726 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX2
SID 1452 (BTSUSER,BIZTPRDI,BTSNTSvc64.exe) in instance FSLX1 is blocking SID 2016 (BTSUSER,biztprdi,BTSNTSvc64.exe) in instance FSLX2

Blocking locks encountered while splitting partitions in 11g

Background: I've taken over administration of a database that has several date-range partitioned tables that, suffering from a lack of proper administration, have not had their MAXVALUE partition split into the requisite monthly partitions, in almost a year. As a result, in some cases the MAXVALUE partition has 10 million rows (the monthly partitions should average 750K rows).
My understanding is that the syntax I am using to perform the split, should allow for on-line access to the tables while the split is being performed. Here is my syntax without the actual table names:
ALTER TABLE owner.table_name
SPLIT PARTITION MAXVALUE AT
(TO_DATE(' 2012-02-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
INTO (PARTITION PART201201
TABLESPACE tablespace
PCTFREE 10
INITRANS 1
MAXTRANS 255,
PARTITION MAXVALUE) update indexes;
Problem: In attempting to split the MAXVALUE partition into monthly partitions while the database is on-line and accessible, I see application sessions being blocked by my split session.
So, is my understanding above incorrect? Is there some additional syntax that I am missing? Or, are the blocking locks I'm seeing merely transient in nature, and can be ignored? The server I'm running on is not very "beefy", and the split is taking quite a while to run.
Any assistance would be appreciated.

>
Background: I've taken over administration of a database that has several date-range partitioned tables that, suffering from a lack of proper administration, have not had their MAXVALUE partition split into the requisite monthly partitions, in almost a year. As a result, in some cases the MAXVALUE partition has 10 million rows (the monthly partitions should average 750K rows).
My understanding is that the syntax I am using to perform the split, should allow for on-line access to the tables while the split is being performed.
Problem: In attempting to split the MAXVALUE partition into monthly partitions while the database is on-line and accessible, I see application sessions being blocked by my split session.
So, is my understanding above incorrect? Is there some additional syntax that I am missing? Or, are the blocking locks I'm seeing merely transient in nature, and can be ignored? The server I'm running on is not very "beefy", and the split is taking quite a while to run.
>
DML that modifies the table cannot be performed on the table while the split is ongoing.
Your bigger problem is that you are using the WRONG method for your use case. If you repeatedly split the MAXVALUE partition you will be repeatedly copying and moving the same ultimate MAXVALUE data over and over again.
DBMS_REDEFINITION is one of your options. But since I just answered this same question 3 days ago see my reply in this thread for a more thorough discussion of your options.
Re: Which is the Best method to Split Partition

Blocking locks by user report hangs

Please,
"Blocking locks by user" report under "Database Administration Section" of "Data Dictionary Reports" is hanging
every time we try to run it against any database.
Please, confirm this issue in Oracle Sql Developer 4.0 EA since it was working perfectly in
Oracle SQL Developer 3.2.2 (3.2.20.09.87).
Also, allow us an estimate deadline for correction.
Thanks in advance,
Andraly Ng

please make a copy of the posting in the report-forum

Blocking Locks

Oracle 9.2.0.8
Our database is used as backend for IIS Servers. Several times per week we experience Blocking locks situation when we could have around 300 – 400 session waiting. Most time when somebody fire up some Update or Delete process. Every time when I check dba_waiters table during this it gives me 10 – 20 holding session. After killing them all things go back to normal.
My question how do I know which one out of this 10 – 20 session is first or real offender. The reason I asked that sometimes after checking SQL’s from several holding sessions they different. And I am not sure which one is the real issue. If I could find this I would be able to go back to developers and see if they missed commit or something in code.

You can use DBA_BLOCKERS and DBA_WAITERS to generate a hierarchy-- the session at the top of the hierarchy is the real offender (assuming, of course, that the locking is not intentional).
In DBA_WAITERS, you'll see a WAITING_SESSION and a HOLDING_SESSION. If you see entries indicating that A is waiting for B, B is waiting for C, and C is waiting for D, you see that there is a hierarchy of locks. Session D in this case is the ultimate culprit (it is blocking a session and it is not blocked by any other session). Of course, in reality, there may be multiple culprit sessions. And you'd want to run the query a couple of times to make sure that what you're seeing is consistent-- if the blockers and waiters change regularly, that's a very different situation than if things are stuck because one session has gone out to lunch.
Justin

Blocking Locks monitoring in 12c cloud control

Ours is a 11.2 4 node RAC environment, and to check for blocking locks i run a sql script. I want to monitor the blocking locks in the system and if there are any locks for more than say 10 minutes then send out a mail to a group to look into it.
We have 12c cloud control setup, my question is if there is a way to setup alerting/monitoring via 12c for checking blocking locks on all nodes and send out email notifications if there are any. I am not much familiar with 12c, please let me know and if its possible let me know the steps to set it up.

Resolved by removing and re-adding the target...

A lot of blocking locks on NRIV daily

Hi experts,
Our system has a lot of blocking locks on NRIV. I use DMV to check and find many processes update RF_BELEG frequently. I find note 840901 can solve using parallel buffering, but our FI users do not agree sale document number without continuous chronological ascending order. Any solution from SAP or SQL server? Could SQL server parallel update NRIV table?

hi dennis,
this issue would be complicated since if you're not allowing your Apps server buffering NRIV than your SAP performance will decrease. this is because every transaction which require number need to be generated first every time your user save data to your SAP system.
This buffering technique is used to handle this issue so if your Apps server do not need to ask new number every time your user save their transaction data.
i have same issue when our external (public) auditor ask me than i ask for SAP support and then they explain about this. when i explain this issue to my external auditor, they understand this issue and they said no problem as long as this issue could be accepted.
ardhian
http://sapbasis.wordpress.com
http://ardhian.kioslinux.com

P1ERP4 Blocking Locks found

Similar Messages

Maybe you are looking for