Trying to lock periods
<p>I want to lock a whole year with consolidated data. Although thestatus is ok or ok sc and all units are published I often get thereply Can not lock process unit if calculation, .. or consolidationis needed. Can't understand why. 90% of the units are alreadylocked but the remainig 10% just wont lock.</p><p> </p><p>Some units are also marked CN but when I try to consolidate Ionly get a VBScript error message. Also locking every singel unittakes for ever, like ten minutes for locking two units.</p><p> </p><p>Starting to get really annoyed, any suggestions?</p><p> </p><p>Thankful for anything!!!</p>
<p>IF you have two parallel entitys (parents) and some childentitys exist in both. If you do a consolidation, only taking intoaccount one of the parents, and then try tolock a child exisiting in both, will itwork??</p><p> </p><p>I think that might be what has happened but I don't know if itwould cause a problem?</p>
Similar Messages
-
Hello Experts,
I am trying to lock a period and I am receiving an error when I try. Error states "Cannot lock data because the validation account is not zero." I haven't had any issues with any other period except August. I noticed that there is country that would not lock. All the entities within that one country locked; however, at the parent and consolidated level, it would not. Please help if you can.
Thanks!Hi,
Please refer the below article that might help you ,
"Cannot lock data because the validation account is not zero" when trying to lock a parent entity (Doc ID 1314837.1)
Cause
The cause was that there were calculated values in the <Parent Currency> Value member in the child entity. This is caused by rules, and previous periods may not have these calculated values. It is not possible to lock <Parent Currency> value member of the child entity if it is not zero in the validation account.
When the <Entity Currency> value member of a parent entity is locked, the system also needs to lock the <Parent Currency> of the child entity in the same action. If the value of the validation account at <Parent Currency> level in the child entity is not zero, the user will not be allowed to lock the <Entity Currency> of the parent. If calculation or translation rules are writing values to this <Parent Currency> value member, they will need to be checked to ensure that this value remains zero.
Solution:
1) The calculation or translation rules will need to be adjusted so that numerical non-zero values are not generated in the <Parent Currency> value member of the child entity.
2) Then the entity will be lockable at "translation" (Parent currency) value member level,
3) If it can be locked at this level, then the parent entity will be able to be locked at <Entity Currency> level.
4) After amending the rules, load the changed rules, and run some translations and consolidations and test the locking process again.
Regards,
Gunasekaran Rayar -
I opened my iPod Touch up to fix my home button. When i closed it back up it had a white screen. I tried pressing lock and home button for 10 seconds and it worked but while i'm using it it goes white with lines on the screen. Help please. This has been happening for a while and i've tried everything but it doesn't work.
Try:
fix for Home button
iPhone Home Button Not Working or Unresponsive? Try This Fix
- If you have iOS 5 and later you can turn on Assistive Touch it add the Home and other buttons to the iPods screen. Settings>General>Accessibility>Assistive Touch
- If not under warranty Apple will exchange your iPod for a refurbished one for:
Apple - Support - iPod - Repair pricing
You can do it an an Apple store by:
Apple Retail Store - Genius Bar
or sent it in to Apple. See:
Apple - Support - iPod - Service FAQ
- There are third-party places like the following that will repair the Home button. Google for more.
iPhone Repair, Service & Parts: iPod Touch, iPad, MacBook Pro Screens -
JDAPI Error: ORA-04020: deadlock detected while trying to lock object
I have written a JDAPI program to perform read-only impact analysis and report any problems.
The following error is occurring:
"A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in the design of an application or from issuing a set of concurrent statements which can cause a deadlock.
ORA-04020: deadlock detected while trying to lock object /NSPC6/CHECK_FOR_FORM_CHANGE"
The error refers to a procedure in a PL/SQL library.
In one case the error occurred after my final "end of processing" message, which is followed only by a call to "Jdapi.shutdown()".
Any ideas?
Thanks,
Neville Sweet.I have written a JDAPI program to perform read-only impact analysis and report any problems.
The following error is occurring:
"A deadlock among DDL and parse locks is detected.
This deadlock is usually due to user errors in the design of an application or from issuing a set of concurrent statements which can cause a deadlock.
ORA-04020: deadlock detected while trying to lock object /NSPC6/CHECK_FOR_FORM_CHANGE"
The error refers to a procedure in a PL/SQL library.
In one case the error occurred after my final "end of processing" message, which is followed only by a call to "Jdapi.shutdown()".
Any ideas?
Thanks,
Neville Sweet. -
I have a lock rotation next ti my battery on my iPad 2 and it won't change from landscape and I tried to reset it but nothing and I tried from lock rotation to mute but nothing and I don't no what to do now. Can u help me plz?
With Settings > General > Use Side Switch To set to 'Lock Rotation' have you then moved the switch on the right-hand side of the iPad above the volume control 'off' ?
Or with the switch set to control 'notification mute' you should be able to unlock rotation via the far left of the taskbar : double-click the home button; slide from the left; and it's the icon far left; press home again to exit the taskbar. The function that isn't being controlled by the side switch is set via the taskbar instead : http://support.apple.com/kb/HT4085 -
Error while trying to Lock the data in Essbase
Hi All,
I am currently facing a issue in Essbase when I am trying to lock the data it shows me the following error message.
Error Encountered is : "You do have sufficient access to perform a lock on this database". I have checked with the administrators / support team and according to them there is nothing wrong with my access. I have the write access to the database and I should be able to lock and send the data but they are unable to figure out why my access is not working or i am facing the above issue. They asked me to select update mode in the essbase options and try but even that didn't work. I am able to make the changes on the same data in Hyperion Planning. I want to lock and send the data directly to server. But I am unable to lock the data. Please expedite.
Thanks a lot for your help in advance.From your post, it sounds like the problem is not Update mode since you mentioned you tried turning it on (I do not recommend having it on). It does sound like a security issue. Depending on the version, planning and Essbase can use different IDs for the same perosn (If I remember planning used to create two IDs one for planning and one for Essbase) The Essbase id had less access than the planning id did. I would test this by having a test Essbase ID set up that has write access and see if that ID can write directly to Essbase. If it can, I would look at filters and groups the ID is on to see if there is some sort of conflict. I have sen that message when a user had read access to part of the DB and write access to another part, but they were pulling data from the read access section only
-
my screen is completely white, i've tried holding lock and home buttons as seen on you tube something called 'white screen of death' its goes black (think it switches off) then back to the white screen need help fast please!
If you have not done a factory reset on the device, I recommend doing a complete factory reset.
Factory Reset - Warning this will reset device back to original factory settings.
This method will not erase any MDN/MIN information
Turn off the phone
Press Power + Volume Up/Down at the same time and hold until display will show a triage android screen
Display will show:
Reboot system Now
Apply sdcard:update.zip
Wipe Data/Factory Reset
Wipe Cache Partition
Use VOL Down key to scroll down to "Wipe Data/Factory Reset", press home icon to select option and wipe device.
Display shows "All user data will be wiped out", press VOLUME Up to continue or VOLUME Down to exit.
Press Volume Up
Press Home to select "Reset System Now" - device will reboot
If the problem persist I recommend having a store technician take a look at the device.
Copy and paste the link below into your browser's address bar for the store locator.
http://www.verizonwireless.com/b2c/storelocator/index.jsp -
Error : Unknown error trying to lock file
Hello,
I am facing this issue since last 2 weeks.
I have one doc lib in it am saving excel documents. When am trying to open any excel document it wil open doc innitially in read only mode. When i click on "edit workbook" option to edit this excel file it will give me this error "Unknowen
error trying to lock the file".
Kindly share your views on this that how can i resolve this error.Try below:
http://wiki.uky.edu/sharepoint/Wiki%20Pages/Unknown%20Error%20Trying%20to%20Lock%20File.aspx
If it persists, there is a KB article about “Office 2003 and 2007 Office documents open read-only in Internet Explorer”, the scenario of your issue is very similar
to the issue fixed in this KB article, I suggest following the resolution and checking. For more information, please refer to:
http://support.microsoft.com/kb/870853
http://social.technet.microsoft.com/wiki/contents/articles/11155.sharepoint-2007-unknown-error-trying-to-lock-file.aspx
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
On the Edit menu, point to New, and then click Multi-String Value.
Type AuthForwardServerList, and then press ENTER.
On the Edit menu, click Modify.
In the Value data box, type the URL of the server that hosts the Web share, and then click OK.
Exit Registry Editor. -
LockException when trying to lock the instance before writing.
hi...
i am working with entity beans. when i am trying to update the data from multiple clients at the same time it is giving exception like...................
[code]
java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Exception in method updateTest2.
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:140)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0p4_Skel.dispatch(Test2UpdateSessionObjectImpl0p4_Skel.java:157)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception in method in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(java.lang.String).
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:780)
at in.mobileone.test2.Test2UpdateSessionBean.updateTest2(Test2UpdateSessionBean.java:64)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:122)
... 10 more
Caused by: <b>com.sap.engine.services.ejb.entity.pm.lock.LockException: LockException when trying to lock the instance before writing</b>.
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:87)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeLock(UpdatablePersistent.java:186)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeOperation(UpdatablePersistent.java:209)
at in.mobileone.test2.Test2EntityBean0PM.setStrFiled2(Test2EntityBean0PM.java:97)
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:755)
... 12 more
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007072510571546800000mobileone202.................5791450, %TMP_TEST2 wCGMIA, test2, E]; it is in use by another owner. The lock collision occurred with user admin.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:154)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:126)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:129)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
... 16 more
; nested exception is:
javax.ejb.TransactionRolledbackLocalException: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception in method in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(java.lang.String).
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:780)
at in.mobileone.test2.Test2UpdateSessionBean.updateTest2(Test2UpdateSessionBean.java:64)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:122)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0p4_Skel.dispatch(Test2UpdateSessionObjectImpl0p4_Skel.java:157)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.ejb.entity.pm.lock.LockException: LockException when trying to lock the instance before writing.
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:87)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeLock(UpdatablePersistent.java:186)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeOperation(UpdatablePersistent.java:209)
at in.mobileone.test2.Test2EntityBean0PM.setStrFiled2(Test2EntityBean0PM.java:97)
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:755)
... 12 more
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007072510571546800000mobileone202.................5791450, %TMP_TEST2 wCGMIA, test2, E]; it is in use by another owner. The lock collision occurred with user admin.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:154)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:126)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:129)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
... 16 more
com.sap.engine.services.ejb.entity.pm.lock.LockException: LockException when trying to lock the instance before writing.
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:87)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeLock(UpdatablePersistent.java:186)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeOperation(UpdatablePersistent.java:209)
at in.mobileone.test2.Test2EntityBean0PM.setStrFiled2(Test2EntityBean0PM.java:97)
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:755)
at in.mobileone.test2.Test2UpdateSessionBean.updateTest2(Test2UpdateSessionBean.java:64)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:122)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0p4_Skel.dispatch(Test2UpdateSessionObjectImpl0p4_Skel.java:157)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007072510571546800000mobileone202.................5791450, %TMP_TEST2 wCGMIA, test2, E]; it is in use by another owner. The lock collision occurred with user admin.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:154)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:126)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:129)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
... 16 more
at com.sap.engine.services.ejb.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:276)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:135)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:296)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: javax.ejb.TransactionRolledbackLocalException: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception in method in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(java.lang.String).
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:780)
at in.mobileone.test2.Test2UpdateSessionBean.updateTest2(Test2UpdateSessionBean.java:64)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:122)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0p4_Skel.dispatch(Test2UpdateSessionObjectImpl0p4_Skel.java:157)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.ejb.entity.pm.lock.LockException: LockException when trying to lock the instance before writing.
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:87)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeLock(UpdatablePersistent.java:186)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeOperation(UpdatablePersistent.java:209)
at in.mobileone.test2.Test2EntityBean0PM.setStrFiled2(Test2EntityBean0PM.java:97)
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:755)
... 12 more
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007072510571546800000mobileone202.................5791450, %TMP_TEST2 wCGMIA, test2, E]; it is in use by another owner. The lock collision occurred with user admin.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:154)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:126)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:129)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
... 16 more
com.sap.engine.services.ejb.entity.pm.lock.LockException: LockException when trying to lock the instance before writing.
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:87)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeLock(UpdatablePersistent.java:186)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.writeOperation(UpdatablePersistent.java:209)
at in.mobileone.test2.Test2EntityBean0PM.setStrFiled2(Test2EntityBean0PM.java:97)
at in.mobileone.test2.Test2EntityLocalLocalObjectImpl0.setStrFiled2(Test2EntityLocalLocalObjectImpl0.java:755)
at in.mobileone.test2.Test2UpdateSessionBean.updateTest2(Test2UpdateSessionBean.java:64)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0.updateTest2(Test2UpdateSessionObjectImpl0.java:122)
at in.mobileone.test2.Test2UpdateSessionObjectImpl0p4_Skel.dispatch(Test2UpdateSessionObjectImpl0p4_Skel.java:157)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2007072510571546800000mobileone202.................5791450, %TMP_TEST2 wCGMIA, test2, E]; it is in use by another owner. The lock collision occurred with user admin.
at com.sap.engine.core.locking.impl3.LockingManagerImpl.lockInternal(LockingManagerImpl.java:154)
at com.sap.engine.core.locking.AbstractLockingManagerImpl.lock(AbstractLockingManagerImpl.java:420)
at com.sap.engine.services.applocking.AbstractBaseLocking.lockInternal(AbstractBaseLocking.java:126)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:129)
at com.sap.engine.services.applocking.TableLockingImpl.lock(TableLockingImpl.java:138)
at com.sap.engine.services.ejb.entity.pm.lock.TableLockingSystem.write(TableLockingSystem.java:82)
... 16 more
at com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException.writeReplace(BaseTransactionRolledbackLocalException.java:273)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
... 11 more[/code]
regards
Guru
Message was edited by:
Guruvulu Bojja
Message was edited by:
Guruvulu BojjaHi Guru,
> we need to lock the table when client is accessing so that we can maintain the consistente data
And that's exactly why the LockException is thrown. If the second client was allowed to update the same data record, this would result in a dirty write which is not allowed by any means. So it's not quite clear what you expect... You lock the data - you get a LockException on concurrent write access - it's so simple and not surprising at all, isn't it?
What you can probably do is to catch the LockException and retry the operation according to your business logic.
HTH!
-- Vladimir -
Locking Periods using the Second Hierarchy in the Time Dimension
Hi,
They are not usiing work status for this...
I am at a client, and they used the second hierarchy in the time dimension to lock periods. If they left the second hierarchy blank, no data can be written to it. To open the open the period, they code the Second Heirarchy with CONS_OPEN. Just wondering if anyone has information on this?
It was working fine, then we needed to run a transport to move BPC to a new machine, and it stopped working. Not sure if anyone has done it this way before?
Thanks,
ChandraDear Kacper,
the way I understood, there are two separate questions in this post, namely:
I'm using a shared resource in multiple actors, and the code accessing the resource can take quite some time to execute. How can can I ensure this does not mess up the timing of one or all accessors?
I'm using a shared resource in multiple actors, and the code accessing the resource can generate errors if I try to access it from multiple places. How can I ensure synchronization between all accessors?
As for the first question, the optimal solution to separate the resource prone to timing issues in a different thread/actor. Put anything that is not strictly timed (file access, network comunication) in a separate loop. For each actor, you will get queue references to communicate with, so instead of logging the measurements in the actors where they are made, just queue them up for a different loop to process.
For the second part, the same logic still applies. Ideally, every singular resource should be handled by its own thread and nowhere else, so if anything else needs data from/to said resource, it can send a request to the dedicated thread or actor.
If, for some reason, this is not sufficient, you have to handle synchronization in some other way. There are a lot of techniques here, for example:
Create a named semaphore or lock as a part of the class. Have class functions use the semaphore before accessing the resource.
Use actor messages. Have a "resource in use" or "resource released" messages sent to all users whenever obtaining or releasing said resource.
Have a separate actor handle all resources, awarding them to threads needing them. This method also allows setting priorities between requests.
These are just a few examples, there are many other options.
Please let me know if this was helpful.
Kind regards:
Andrew Valko
National Instruments Hungary -
ORA-04020: deadlock detected while trying to lock object SYS
Upgrading database from 7.3.3 to 7.3.4. Running CAT7304.sql,
Catalog.sql, and Catproc.sql. In the log file created there are
mulptiple occurrences of;
ORA-04045: errors during recompilation/revalidation of
SYS.DBMS_SYS_SQL
ORA-04045: errors during recompilation/revalidation of
SYS.DBMS_SQL
ORA-04020: deadlock detected while trying to lock object
SYS.DBMS_SYS_SQL
This only occurs on a Netware server, it works fine on NT.
nullHi Steve,
I recommend that you contact Oracle RDBMS support directly.Our
main area of expertise is migrations from non-oracle
environments.
Regards
John
Steve Schindler (guest) wrote:
: Upgrading database from 7.3.3 to 7.3.4. Running CAT7304.sql,
: Catalog.sql, and Catproc.sql. In the log file created there are
: mulptiple occurrences of;
: ORA-04045: errors during recompilation/revalidation of
: SYS.DBMS_SYS_SQL
: ORA-04045: errors during recompilation/revalidation of
: SYS.DBMS_SQL
: ORA-04020: deadlock detected while trying to lock object
: SYS.DBMS_SYS_SQL
: This only occurs on a Netware server, it works fine on NT.
Oracle Technology Network
http://technet.oracle.com
null -
Trying to lock down DNS server settings to force use of OpenDNS
I'm trying to lock down my time capsule on my home network to only allow outgoing DNS traffic to go through OpenDNS. I have an 18 year old son, with his own computer, who bypasses my OpenDNS by entering the DNS settings for Google on his Windows 7 machine. I have no control over his machine, only my router.
A discussion on the OpenDNS forums mentions blocking port 53 and forcing all DNS traffic through the OpenDNS server settings I've entered into my router, but I can't see any way to do this on the time capsule. Am I missing something?There is nothing you can do.. TC do not have access to firewall.. at least for ipv4.
You need a much better router.. bridge the TC and grab a Netgear WNDR3800 and run Gargoyle firmware. The power will be put back in your hands.. then he will buy his own 3G connection.. maybe at 18 it is rather too late. -
Trying to lock out Solaris 11 non-root users but not working-
Hi,
We are trying to lock out non-root user after 5 unsuccessful login attempts by editing the policy.conf file but it's not working..It's working in the global zone but not in the non-global zones. Is there something else we need to do?
This is Solaris 11 with Solaris 11 NGZs.
kind regardsIt works exactly the same way in the global and non global zone cases. This code is 100% userland so it doesn't mater if it is running
in a global or non global zone.
Note that you do need to configure policy.conf in both the global and non global zone.
Are both configured similarly with respect to nameservices ?
Currently we only support lock_after_retries for the local files nameservice. -
Problems when trying to close periods
Hi all,
I'm trying to close period and when using the Oracle Diagnostic Tool it gave me this error: Items have been found in one or more organizations sharing set of books 'XX_DOVERIE' which will prevent closing of period '12-2010'. But there is no unaccounted payments, invoices, etc. The report Period Close Exceptions Report is empty. Any ideas?
Thanks,
AlexYou should typically avoid changing values using diagnostics > examine.
And for far reaching things such as period status, you should never do it via this method.
If you have to close the period, follow the standard procedure for closing a period. If you are encountering problems with it, you can either ask the question on these forums or raise an SR.
Sandeep Gandhi -
"Unknown error trying to lock file." SharePoint Online
Greetings,
I am setting up a document library that will be used by users in our terminal session environment. Hosts are Windows 2008 Server R2. We are setup in a Office 365 / SharePoint Online. We have Office 2013 installed on the hosts.The test user that I have
setup has Edit permissions to this document library. Whenever the user goes to open a document in the library it always opens in "Read Only" mode, and when trying to edit I receive the message "Unknown error trying to lock file." I have
read other threads and already changed the following.
-Put our SharePoint in the correct internet zone / and trusted sites (GP)
-Setting to require documents to be checked out before they can be edited (Library Settings)
-Allow documents for opening in Read/Write (GP)
-Added registry entry for AuthForwardServerList including our Sharepoint site (Registry)
Any help would be greatly appreciated.
Thanks,
-MagooHi Dermot,
Did this issue happen to all web applicaitons, and all users? What if you access SharePoint site drectely other than via TFS?
Have you checked if there is any related error message in SharePoint ULS log or event in Event Viewer for any clue?
Also check if SharePoint server application pool (scheduled) recycle could help.
http://www.techbubbles.com/iis/recycling-application-pools-in-iis-for-sharepoint-2010/
Thanks
Daniel Yang
TechNet Community Support
Maybe you are looking for
-
Please help me, i really need help. Thanks a lot guys... this is my error: C:\Temp>java Lab2 Welcome! This program computes the average, the exams The lowest acceptable score is 0 and th Please enter the minimum allowable scor Please enter the maximu
-
Mistakenly reversed goods receipt after invoice posted
Hi experts, I already post this question in EAM forum, but moved to here as I think I will get more useful replies. I have a PO that was goods receipted and invoiced receipted. Later on, the GR was reversed, and now that entry needs to be reverse...
-
Where can I find an explanation of Processes and Log files for LMS 3.2?
Being fairly new to Ciscoworks, I've been scouting for documentation that explains the processes as enumerated by the "pdshow" command. Also, when there are problems, I find myself hunting through the log files without a clear understanding of which
-
I have a laptop that goes back & forth from MI. to AZ. Mi has the 4500 series, and AZ has the 1410 series. Now my laptop shows the 4500 as offline & I can't print from my printshop, or Kodak files. How do I put the 4500 back online???
-
Hi, This piece of code is taking a long time and many times gives Abap runtime errors with SYSTEM_IMODE_TOO_LARGE. (Basically the performance of the query needs to improve. I have done ST05 and also ran the query and I would appreciate any input on i