Dead Lock what made by another user!(patition table)

I have a question about Dead-Lock!
Our Situation is ..
User "A" made a Patition Table, ACNT_WONJANG
(without any Trigger,Function, Procedure)
When "B" - another user - tried to drop its Partition,
Dead-Lock invoked.
but A droped it's Partition well.
What can i Do?
this is the trace file.
/oracle/home/admin/ACNT/udump/ora_44478_acnt.trc
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
ORACLE_HOME = /oracle/home
System name: AIX
Node name: acnt
Release: 3
Version: 4
Machine: 000C962D4C00
Instance name: ACNT
Redo thread mounted by this instance: 1
Oracle process number: 15
Unix process pid: 44478, image: oracle@acnt (TNS V1-V3)
*** SESSION ID:(16.394) 2001-10-04 15:00:41.829
A self-deadlock among DDL and parse locks
is detected. In most cases, this self-deadlock
is handled internally.
This should be reported to Oracle Support
ONLY IF an error is signalled back to the
user on a command-line or screen.
The following information may aid in finding
user on a command-line or screen.
The following information may aid in finding
the problem.
ORA-04020: deadlock detected while trying to lock object
F03P.ACNT_WONJANG
session: 440786b4 request: X
LIBRARY OBJECT HANDLE: handle=43108348
name=F03P.ACNT_WONJANG
hash=76b93583 timestamp=NULL
namespace=TABL/PRCD/TYPE flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0001-0001 lock=S pin=S latch=0
lwt=43108360[43108360,43108360] ltm=43108368[43108368,43108368]
pwt=43108378[43108378,43108378] ptm=431083d0[431083d0,431083d0]
ref=43108350[43108350,43108350] lnd=431083dc[4310824c,425b7ec4]
LIBRARY OBJECT: object=431080d0
flags=NEX[0002] pflags= [00] status=VALD load=0
DATA BLOCKS:
data# heap pointer status pins change
0 431082d8 43108154 I/P/A 0 NONE
HEAP DUMP OF DATA BLOCK 0:
HEAP DUMP heap name="library cache" desc=0x431082d8
HEAP DUMP heap name="library cache" desc=0x431082d8
extent sz=0x224 alt=32767 het=8 rec=9 flg=2 opc=0
parent=30000030 owner=431080d0 nex=0 xsz=0x0
EXTENT 0
Chunk 431080c0 sz= 196 perm "perm "
alo=196
431080C0 500000C5 00000000 00000000 000000C4 [P...............]
431080D0 43108348 431080D4 431080D4 431080DC [C..HC...C...C...]
431080E0 431080DC 00000000 00000000 00020100 [C...............]
431080F0 00000000 00000000 00000000 00000000 [................]
43108100 43108144 00000000 00000000 00000000 [C..D............]
43108110 00000000 00000000 00000000 00000000 [................]
Repeat 2 times
43108140 00000000 431082D8 00000000 43108154 [....C.......C..T]
43108150 00000000 00000000 00000000 00000000 [................]
Repeat 1 times
43108170 00000000 00000000 00000019 00000000 [................]
43108180 00000000 [....]
Total heap size = 196
FREE LISTS:
Bucket 0 size=0
Total free space = 0
UNPINNED RECREATABLE CHUNKS (lru first):
Total free space = 0
UNPINNED RECREATABLE CHUNKS (lru first):
PERMANENT CHUNKS:
Chunk 431080c0 sz= 196 perm "perm "
alo=196
Permanent space = 196

carlyfromal wrote:
Here's the thing I myself have an Ipad 3 that I got from Ebay that is activation locked and I have the same issue. Can't get the info. Well,since Apple conveniently decided to discontinue selling the Ipad 3 the only way I could get one was to buy a used one,so it looks to me like they could have some mercy and help a person unlock the thing. We're not dishonest people that go around stealing things,yet because of Apple's brilliant(I use that term sarcastically) idea to put this stupid new crap in place people like us who have to buy second-hand products have to suffer and get screwed out of money we had to save up to buy this stuff! And all anyone can come up with is "well boohoo" or "tough luck" or whatever! But,what about the rights of the rest of us?! Some of you may find this a tad rude, but oh well,tough luck!
On the other hand, there are those of us that appreciate the theft protection provided by the latest IOS.
There are certain things to watch out for when purchasing used devices of any sort, the first of which is to ensure that you're not buying stolen property. Since you are unable to obtain cooperation from the seller, perhaps your device was stolen!

Similar Messages

Another user modified table rdr3

Hi
I got error "Another user modified table rdr3" when try to update additional expenses on sales order form.
Case: Update Add. expences through my code based on condition and document updated well with add. expenses
but after that if i update add. expenses through system functionality <b>means By pass my code</b> based on some condition, SBO throws this error.
Help needed!???

In what event are you performing your update? I was getting the same message when I did my update in the in "item clicked" (for the update button) and this is evidently before the form does the update. It saw the changes I made to the record and therefore aborted the update.
I moved my update to item-pressed and that solved the problem. But it's been a little more complicated than that for me.
As far as I can tell, SBO updates the object on the form AFTER the BeforeAction event is triggered from item pressed. But the way my debugging suggests it happens is that if there are no errors from that update, while item pressed does get it's AfterAction triggered, the form is no longer in update mode - it's in OK mode. So it seems that the update really needs to happen from OK mode but there's one more complication.
At least for the item master form, button 1 can be in OK mode after doing an Update (which will work), but will also be in OK mode after a find (where the user types, for instance, an item number and presses enter, rather than the find button). So what I am doing is setting a flag on item pressed/update mode/before action that let's me know that update is requested. then in item pressed/find mode/after mode I test for update requested, then update the object and turn off my flag:
Case Is = SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED
    If pVal.ItemUID = "1" Then
       Select Case pVal.FormMode
            Case Is = SAPbouiCOM.BoFormMode.fm_UPDATE_MODE
                     If pVal.BeforeAction Then
                        g_UpdateModeStarted = True
                     End If
           Case Is = SAPbouiCOM.BoFormMode.fm_OK_MODE
                      If g_UpdateModeStarted Then
                           If pVal.Action_Success Then
                              UpdateItem()
                              g_UpdateModeStarted = False
                           End If
                      End If
WARNING: I am very new to SBO programming and haven't even taken the class yet. This works for me but I imagine that others in this forum might say I'm going about it all wrong. But since no one else has offered a solution to this yet, I thought I'd let you know how I got around the problem.
Good Luck!

Error: Another user -modified table (ODBC -2039)

I receive an error when trying to post data through to the SapbobsCom6.7 business object reading "Another user -modified table (ODBC -2039)"
Could anyone please assist me regarding this!
Thank you!
Etienne

Hi Etienne et al,
I don't know if this helps you, as your last post in this topic was quite a while ago, but never the less I found one reason for the -2039 error which may be of help to other Business One developers in the future.
I was getting the -2039 error every time I tried to update a record in one of my user defined forms, yet the error wouldn't happen with most of the other records in the table.
Looking at the record I found that there was a column related to a Date field on the which had an incorrectly entered value from a previous data import.
What should have been '2004-06-23 00:00:00.000' in the table was actually '1899-12-30 23:06:04.000' and would appear as 30/12/99 in the form field. Once I corrected the format of the data the addon form was happy to update the record.
I hope this helps anyone else out there.
Nick Jacka

[OACT], Another user-modified table 'G/L Accounts' (ODBC-2039)

Dear All,
When AP dept user attempting to add outgoing payment, the error message ""[OACT], Another user-modified table 'G/L Accounts' (ODBC-2039)" appears, what could the causes of the problem be ? I have restarted server many times but still unsolved yet.
TIA
Rgds,

Steve,
One reason why this happens ("Another User Modifed table") is if the SQL database has been updated while the document is open. When trying to add the document, the information in the document will be inconsistent with the values in the database itself.
It can also be because someone tried to Run one of the Restore Balances Procedure.
Please contact SAP Support by logging a message at http://service.sap.com
Suda

Another user-modified table... Errors

Dear Experts,
Two of our clients are experiencing same error message but different Table name and scenario.
First: Customer1 change the password of Manager account and it became successful. But when they change the password again, they encounter the u201CAnother user-modified table 'Users'(OUSR)...u201D error message.
Second: Customer2 can't change the Item description in Item Master Data. When they try to update the description, the "Another user-modified table 'Items'(OITM)(ODBC-2039)[Message 131-183]" error message appears.
I've read some of the preferred solutions but the same issue occurs.
Are these considered as bugs?
Please help us.
Thank you so much.
Regards,
Doriza Cortez

Dear Doriza Cortez,
All those errors are caused by table locks. Users have at least to exit from B1 for all their sessions. If the problem still persist, restart server is the last cure. Before that, you can try to kill certain hidden session from SQL Studio.
Thanks,
Gordon

Another user-modified table 'Product Tree' (OITT) - Error message

Hi
Our B1 2005A SP01 PL48 sometimes shows the following error message when trying to change a BOM, even if this error is not possible.
Another user-modified table 'Product Tree' (OITT) (ODBC -2039) [Message 131-183]
What can I do, except for deleting and recreating the BOM?
Thanks
Franz

Hi Franz,
Please check these threads to find anything in common:
Another user-modified table 'Items' (ODBC -2039)
Another User modified Table (ODBC -2039) - Sales order
In Purchase Order
Re: Warehouse alerts not popping up.
Thanks,
Gordon

Another User-modified Table [Message 131-183]

Hi Expert,
My client tries to add the Sales Quotation and get a following error message.
"Another User-modified Table u201C(QUT1) (ODBC -2039) [Message 131-183]"
And also canu2019t add as a draft either.
Using: 2007A PL42
I checked notes and Forum but canu2019t solve this issue.
Please help me.
Thank you!
Naoko

"Another User-modified Tableu201C is a very common problem. It is either caused by a bug or the result of actually another user locked the record.
If you could not find any other clues, log to SAP support. In the mean time, try to reproduce it in the test environment.
Thanks,
Gordon

Another user modified table (NNM1) (ODBC-2039)

Hi All
While Creating a document series the system displayes an error message saying "Another User Modified table (NNM1) (ODBC-2039)"
What could be the error?
Thanks
SV Reddy

Hi SV Reddy,
Check the thread
Error while updating the Document Numbering Form
Problem in numbering series
*Close the thread if issue solved.
Regards
Jambulingam.P
Edited by: Jambulingam P on Aug 10, 2009 10:01 AM

Another User Modified Table RDR1(-2039)

Hi
I got error "Another User Modified Table RDR1(-2039)" sometimes when i update Sales Order. Since I m doing customization on Sales Order form, <b>i m unable to proceed with my code since it run on ActionSuccess</b>.
What could be the reason ..
Plz help

Hi Pankaj,
Firstly make sure that you don't hold references to objects that you don't use. If you have reference to an order and maybe update the order and later again use another object to access the same order this might happen. Create and release objects as you use or don't use them. You can release the objects with
System.Runtime.InteropServices.Marshal.ReleaseComObject(x)
Hope it helps,
Adele

Another user-modified table (VPM1)

Dear Experts,
I faced the above error when trying to add outgoing payment.
Firstly, I saved the outgoing payment as a draft. Then, I open the outgoing payment draft through payment draft report.
Before I add the outgoing payment draft into valid outgoing payment document, I have to confirm and update the check number in payment mean.
Finally I save the outgoing payment. However, system doesn't allow to save this draft into valid document and display error "Another user-modified table (VPM1) (ODBC-2039) [Message 131-183]". Please help!

Dear Teng,
It seems to be a database corruption issue.
We would like to suggest you to open a message for SAP Support.
Regards,
Rakesh Pati
SAP Business One Forum Team.

Error: Another User Modified Table in Service Call in SAP B1 8.8 PL9

Hi Experts,
We are facing an issue in SAP B1 8.8 Patch 9 in Service Call. When taking service calls continuosly, when we try to update every 3rd Service Call the following error is coming
"Another user or another operation modified data; to continue, open the window again 'Service Calls' (OSCL) (ODBC -2039) [Message 131-183]".
Only 1 user is using the service call.. Several times we logged out and logged in, still the same error is coming,
Kindly help to solve this.
Regards
Sundaram

Hi
You may check this thread. It might be a bug.
Re: another user modify table error on Service call
Thanks,
Gordon

Another user modify table error on Service call

Dear All,
i am getting error while updating the service call.
As this is SAP2007B PL 16 i have created a service call when i am updating this service call i am getting the error like-another user is modify table-service call .
Kindly help me out.
Regard,
Divya Singh

Dear Divya,
In most cases, the error messages " Another user modified table XXX (XXXX) (ODBC -2039)." comes because after opening the form at your side, another user opened the same form and applied some changes. You can close the form, open it again, apply your changes and then update it to avoid this error message.
But in some cases, even if you close all the clients and login again, the problem still exists. In that case, this error might be caused by Database Corruption which need DB fix. If this is the case, Kindly log a message to SAP Support.
Regards,
Varun
SAP Business One Forum Team

Another user-modified table '' (POR1) (ODBC -2039) [Message 131-183]

I have updated the purcahse order form.I have added a combo excisable.Also I have defined excisable and non-excisable warehouses.I have added a condition as,
If I select Yes from the combo then the warehouse of the item should be excisable.And,if I select No then the item should be from non-excisable warehouse.
When I change the warehouse as per the above condition it gives error as,
Another user-modified table '' (POR1) (ODBC -2039) [Message 131-183]
I am using SAP Business One 2007 B.
PL:11
The errors occurs when I click on update button.The error does not occur if I don't update purchase order.
Regards,
Dilip Kumbhar

Dilip Kumbhar,
You may check these threads first:
Updating a PO
In Purchase Order
Thanks,
Gordon

Another user-modified table 'Items' (ITEM) (ODBC - 2039) [Message 131-183]

Hi All,
Just had an issue reported by a customer. They tried to amend a UDF on an Item Master record and they can change data such as the Item description, remarks etc and update the item successfully... However, when they tried to amend the contents of the UDF's attached to the Item the system issue the message:
Another user-modified table 'Items' (ITEM) (ODBC - 2039) [Message 131-183]
Any thoughts?
Best regards
Earl

I figured it out
We had a UDF name U_Discount that was set to only allow Y or N.
In the database I had a space after the Y or N value for some of the records. I discovered it by running
SELECT distinct [U_Discount], COUNT(*) FROM [OITM] group by [U_Discount]
No idea how the space got there, but I ran
update OITM set U_Discount = 'N' where LEFT(U_Discount,1) = 'N'
update OITM set U_Discount = 'Y' where LEFT(U_Discount,1) = 'Y'
and it fixed it

Another User modified Table (ODBC -2039) - Sales order

Via a button on sales order form I delete some of the order lines with oMatrix.DeleteRow(rowNr).
It works fine but the DocTotal is not updated as it will be if I delete the row manually with the right-click Delete Row command.
When saving the order via Update button it refuses with the error "Another User modified Table (ODBC -2039)".
Do you have any ideas for workarounds for this?
I've tried to set the price to 0 before deleting the row (the DocTotal will be updated) but the error is the same when saving.
I don't manipulate the FormMode in the code.
Regards
Lars

HI,
SAP has answered with notes 720076.
They suggest to use
oMatrix.Columns.Item("1").Cells.Item(i).Click()
SBO_Application.ActivateMenuItem("1293")
instead of
oMatrix.DeleteRow(i)
It works for me.
Best regards,
Paolo.

Dead Lock what made by another user!(patition table)

Similar Messages

Maybe you are looking for