Database locks problem

Hi,
We encounter blocking locks within our applications on a frequent basis. We have various ways of detecting these but when we have locks we cannot see them via EM Grid Control.
We navigate to <Database> - Performance - Database Locks - Blocking Locks - there are none displayed even though we know there are blocking locks.
This is happening on a number of databases, all of which are 8.1.7.4.
There are no error messages displayed in the Grid Control console - it draws the locks screen fine - but just displays no results.
In the emoms.trc file we can see errors relating to locks and javanullpointer exceptions (see output below).
Has anyone else had this problem?
Any help appreciated.
Thanks,
Steve.
Output from emoms.trc:
[EMUI_13_45_56_/console/database/instance/lock] ERROR em.MetricEngine getMetricResult.1026 - MetricCollect
orTarget[MetricCollector:LOCK_THREAD302:30] unable to get cached data for metric
BLOCKING_LOCKS against target YBSL: java.lang.NullPointerException
java.lang.NullPointerException
at oracle.sysman.emo.perf.metric.rt.DbLockManagerQuery.getData(DbLockManagerQuery.java:316)
at oracle.sysman.emo.perf.metric.rt.DbBlockingLocksQuery.getData(DbBlockingLocksQuery.java:72)
at oracle.sysman.emSDK.emd.rt.MetricCollectorThread.getMetricResult(MetricCollectorThread.java:971)
at oracle.sysman.emSDK.emd.rt.MetricCollectorTarget.getMetricResult(MetricCollectorTarget.
java:534)

Hi;
Recently i have many (apps) user locks in my database . Any problem happen my database ?Which user? Seeded or customs? If one user locked which mean that user cant login database any more. Did you check those user end date?
Can i kill that Inactive (apps) users manually ? If one session is İnactive it doesnt meant it can be not active anymore. Please see:
session is still Alive-How to find the DB session is still Alive
How to find the DB session is still Alive
Regard
Helios

Similar Messages

Database lock problem?

Could someone please help? I have been trying to solve the problem for a week full-time, it seems so easy, what do I miss?
Many thanks in advance.
2 clients and 1 DBMS server
Clients are using OCI 8.1.7
This is what happens:
1. Client 1 (CL01) connects to database.
2. Client 2 (CL02) connects to database.
3. UPDATE of table CL02.testtable started from CL02. UPDATE is made in a PL/SQL loop. See below.
4. UPDATE of table CL01.testtable started from SERVER. UPDATE is made in a PL/SQL loop (same but different table).
5. CL01 and CL02 receives notifications using Oracle AQ (printing some message on screen every second). The subscription is set up using a trigger, a stored procedure and a non-persistent single consumer queue. The objects are created separately in CL01 and CL02's SCHEMAS. See below.
6. I disconnect CL01 (unplugging the network cable). CL01 (of course) doesn't receive any further notifications.
7. MY PROBLEM: AFTER APPROX. 23 SECONDS THE NOTIFICATIONS STOP TO ARRIVE ON CL02 (NO NETWORK TRAFFIC).
8. After exactly 50 seconds 50 notifications (update every second) arrive at the same time on CL02.
9. Notifications arrive as normal again on CL02.
A normal shutdown of CL01 in step 6 above, will not cause a delay.
PL/SQL loop:
DECLARE
Cnt NUMBER(5);
BEGIN
Cnt := 120;
WHILE (Cnt >= 1) LOOP
DBMS_LOCK.SLEEP(1);
UPDATE CL02.testtable
SET value=Cnt;
commit;
Cnt := Cnt - 1;
END LOOP;
END;
AQ Objects:
CREATE OR REPLACE TRIGGER CL02.aqtrigger
AFTER UPDATE ON CL02.testtable
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
CL02.ENQPROC('CL02.thequeue');
COMMIT;
END;
CREATE OR REPLACE PROCEDURE CL02.ENQPROC(queue varchar2)
AS
enq_opt dbms_aq.enqueue_options_t;
enq_msgid raw(16);
msg_prop dbms_aq.message_properties_t;
payload raw(10);
BEGIN
enq_opt.visibility:=dbms_aq.IMMEDIATE;
DBMS_AQ.ENQUEUE(queue, enq_opt, msg_prop, payload, enq_msgid);
END;
DECLARE
Subscriber sys.aq$_agent;
BEGIN
Subscriber:=sys.aq$_agent('CL02', NULL, NULL);
DBMS_AQADM.CREATE_NP_QUEUE(QUEUE_NAME => 'CL02.thequeue',
MULTIPLE_CONSUMERS => FALSE);
DBMS_AQADM.START_QUEUE('CL02.thequeue');
END;

Please advise for how to prevent such dead lock?Difficult to say. That suggests that there is a problem in application design.
Review the code, and/or try to load balance by using another server (in a cluster).
Actually. forget the last point. It won't solve the deadlock problem.
Message was edited by:
karma-9

Database locking problem

Have anyone ever had problem with iPlanet holding up the DB connection, and
hence subsequent request to the DB is blocked? My program close JDBC
connection everytime when the method call is completed, within a try-catch
block generated from Visual Cafe. I only have 1-2 tester using the
application but always find that the connection is blocked.
I have found some documents that talks about changing default iAS database
setting. Thus, my iAS setting have been changed to the following:
In iAS registry under SOFTWARE\iPlanet\Application
Server\6.0\CCS0\POOLS\oraclePool
DebugLevel=0
MaxPoolSize=50
MaxWait=30
MonitorInterval=30
SteadyPoolSize=15
UnusedMaxLife=30
What I've done is to force the cleanup thread to destroy idle connection
pool as quickly as possible.
Any help is appreciated.
Keith Cheng
Senior Consultant
------------------------------------------------------->
DeliriumCyberTouch Hong Kong >
TL:+852-2298-3888 FX:+852-2144-6332 DL:+852-2298-3560
MB: +852-9580-8778 http://www.deliriumctouch.com

What version of iAS are you on? If you are on iAS 6 SP2 (maybe even SP3), then you may be affected by the bug that causes transactions on pooled connections to be not committed properly. You may observe, however, that (based on your pool configuration) if you wait for about a minute, the transaction commits, releasing the DB resources. If this sounds like your problem, then there is a patch for the problem.
JC
Keith Cheng wrote:
>
Have anyone ever had problem with iPlanet holding up the DB connection, and
hence subsequent request to the DB is blocked? My program close JDBC
connection everytime when the method call is completed, within a try-catch
block generated from Visual Cafe. I only have 1-2 tester using the
application but always find that the connection is blocked.
I have found some documents that talks about changing default iAS database
setting. Thus, my iAS setting have been changed to the following:
In iAS registry under SOFTWARE\iPlanet\Application
Server\6.0\CCS0\POOLS\oraclePool
DebugLevel=0
MaxPoolSize=50
MaxWait=30
MonitorInterval=30
SteadyPoolSize=15
UnusedMaxLife=30
What I've done is to force the cleanup thread to destroy idle connection
pool as quickly as possible.
Any help is appreciated.
Keith Cheng
Senior Consultant
------------------------------------------------------->
DeliriumCyberTouch Hong Kong >
TL:+852-2298-3888 FX:+852-2144-6332 DL:+852-2298-3560
MB: +852-9580-8778 http://www.deliriumctouch.com

Database termination Problem

Hi every body ..plz help me on this..
We are facing database termination problem in ECC6 production syste.
Database: Oracle 10.2, O/S: Windows 2003. Spam :27, SP level 13.
Error is:
Errors in file f:\oracle\p02\saptrace\background\p02_ckpt_6520.trc:
ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: 'D:\ORACLE\P02\ORIGLOGB\CNTRL\CNTRLP02.DBF'
ORA-27072: File I/O error
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 33) The process cannot access the file because another process has locked a portion of the file.
When we are performing backup then data base termination occuring freequently.
Give right solution as early as possible.
Thanks,
Nani.

Hi,
Have a look at below snote which actually speaks about the oracle error codes
Snote : 546006
within the Snote it says :-
" If you cannot access a database file (for instance a data file, control file or RedoLog) for whatever reason, an ORA-270xx appears. The actual cause comes from additional error messages (usually in the operating system) that occur on ORA-270xx. "
And as per your last update
" ORA-00206: error in writing (block 3, # blocks 1) of control file
ORA-00202: control file: 'D:\ORACLE\P02\ORIGLOGB\CNTRL\CNTRLP02.DBF' "
i think there is problem accessing the database control file. Hence you are facing the above problem.
I think if you recreate your control file i think, it should resolve the problem.
Hope it will be helpful to resolve your problem.
Rgds
Radhakrishna D S

Forms 6i : Ole Container : Locking problem

We have a form in which user can attach all sorts of documents that are then saved in the database.
Once in a while we have a locking problem; when 2 users try to open the same document, the second one first gets a 'Could not reserve record (2 tries). Keep trying?'. When clicking 'No', the next error message is 'Frm-40501 : unable to reserve record for update or delete', and the form cannot be used anymore. He keeps complaining about the reserved record.
I've been looking into this problem but cannot seem to find a lot of help.
Does anyone have an idea how to solve this locking problem?
I have tried the following things:
* setting the block to locking mode 'Delayed' => we ended up having duplicate records.
* Changing properties of the ole-container (In Place Activation, Inside Out support, ...).
Forms version is 6.0.8.13.0, database 8.0.6.0.0.
Any help is appreciated.

that seems to be a normal locking problem. Do you have tried to work with an ON-LOCK trigger ? (e.g. first to see, when locking will occur, second for implementing an own locking-behaviour, maybe with a SELECT for UPDATE)
Or do you think, that there is something special with your OLE-programming ?
Gerd

Database Locks not working

Hello!
I am having some problems with the Berkley DB XML Locking System. My database is configured as follows:
     _envConfig = new EnvironmentConfig();
     _envConfig.setRunFatalRecovery(doFatalRecovery);
     _envConfig.setRunRecovery(!doFatalRecovery);
     _envConfig.setVerboseRecovery(true);
     _envConfig.setAllowCreate(true);
     _envConfig.setCacheCount(1);
     envConfig.setCacheSize(DBCACHE_SIZE * 1024 * 1024);
     _envConfig.setInitializeCache(true);
     _envConfig.setTransactional(true);
     envConfig.setMaxLocks(MAXLOCKS);
     envConfig.setMaxLockers(MAXLOCKERS);
     envConfig.setMaxLockObjects(MAXLOCKOBJECTS);
     // enable locking
     _envConfig.setInitializeLocking(true);
     _envConfig.setLockTimeout(50000000);
     logInfo("Database locking enabled.");
     // Configure db to perform deadlock detection internally, and to
// choose the transaction that has performed the least amount
// of writing to break the deadlock in the event that one
// is detected.
_envConfig.setLockDetectMode(LockDetectMode.MINWRITE);
Then I try to modify one object in my first thread:
xmlTransaction = xmlManager.createTransaction();
               xmlContainer = xmlManager.openContainer( xmlTransaction, _collection);
               context = xmlManager.createQueryContext(XmlQueryContext.LiveValues, XmlQueryContext.Eager);
               // Declare the read/modify/write cycle
          XmlDocumentConfig docConfig = new XmlDocumentConfig();
          docConfig.setLockMode(com.sleepycat.db.LockMode.RMW);
               XmlQueryExpression xmlQueryExprDocs = _xmlManager.prepare( xmlTransaction, sQuery, xmlQueryContext);
     results = xmlQueryExprDocs.execute( xmlTransaction, _context, docConfig);
     xmlQueryExprDocs.delete();
     // document(s) found - create modify, update objects
     * Iterate over _result documents
     while (_results.hasNext()) {
                    modify = xmlManager.createModify();
                    updateContext = xmlManager.createUpdateContext();
          docValue = _results.next();
          xmlDoc = docValue.asDocument();
          numMod = modify.execute(xmlTransaction, docValue, context, updateContext);
In my second thread I try to read the same object:
xmlTransaction = _xmlManager.createTransaction(null, cfg);
XmlContainer xmlContainer = getXmlManager().openContainer(xmlTransaction, sContainer, contConfig);
context = _xmlManager.createQueryContext(XmlQueryContext.DeadValues, XmlQueryContext.Eager);
xmlQueryExpr = _xmlManager.prepare( xmlTransaction, sQuery, xmlQueryContext);
     results = xmlQueryExpr.execute( context);
And then instead of waiting on the first object to unlock the database just logs:
Transaction that opened the DB handle is still active
I just want the db to wait until the modify is ready and then do the query in the second thread.
What am I doing wrong?
Thanks for your help!
Edited by: user11285545 on 19.06.2009 04:18

Hello,
I think you want to post this to the [Db XML forum|http://forums.oracle.com/forums/forum.jspa?forumID=274] instead of the BDB JE forum.
Charles Lamb

ADF Database lock and Refresh

I have two issues regarding ADF.
Database lock :
The problem :
In most test-cases the database lock functionality is working correctly in my app. We have two users working on the same dataset trying to store at the same time, one user get to store, and the other get a message saying that the rowkey have been changed, and can after s short while store his data.
However, in one .jsp saving at the same time gives a lock lasting for 15-20 minutes. The ViewObject related to this .jsp have many EntityObjects (6 EntityObject in one Viewobject), so it is more complex than the others.
What we have tried :
Changing the jbo.locking.mode to optimistic on the Appmodule.
What more can we do in ADF for configuring the locking? Is there a way to trace to see what is creating the lock for 15 - 20 minutes?
Refresh :
The problem :
In most cases ADF handles refresh of data correctly. But some places it seems to not update correctly. We are using JSF (ADF Faces)
What we have tried :
Changing the refresh condition on the iterator in the pageDef.xml to always.
<iterator id="berpriListIterator" RangeSize="-1"
binds="berpriList" Datacontrol="RegServiceDataControl1"
CachResult="false"
Refresh="always" />
Adding InvokeAction :
<invokeAction Binds="Execute" id="invokeExecute" RefreshCondition="${adfFacesContext.postback ==false }" />
Editing the Action:
<action IterBinding ="berpriListIterator" id="Execute" Instance=" " Datacontrol="" RequiresUpdateModel="true" Action="2" />
This seems to work. Is this a bug in ADF or should we always add invokeAction on all pageDefs? Some places it seems to update correctly even without invokeAction.
Is this issue also in 11g?

Using jbo.locking.mode=optimistic I would never expect an ADF web application to hold only any database locks for longer than the span of the commit processing in the normal case. The locks would be attempted only during the commit processing and if any DML error (including a failed lock attempt) occurs, then the transaction should be rolled back to a SAVEPOINT that ADF acquires before beginning the commit processing.
One way an ADF application could acquire and retain locks would be if your application is using the Transaction.postChanges() method to explicitly post, but not commit, pending database changes. Are you doing that by chance?
There are occasions in the Oracle database when doing one operation like a delete or update can lock a table if you have unindexed foreign keys (see http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:292016138754 ). Not sure if that is your situation, but still the locks should only be around for the very short span of time during the commit processing.
Regarding the refresh, you should be able to verify by launching two separate instances of the ADF Business Components Browser testing tool that, when you do the following:
(Assuming app module has jbo.locking.mode=optimistic)
* User A queries Employee with Empno = 7839
* User B queries Employee with Empno = 7839
* User A modifies Sal attribute from 5000 to 4999, Comm attribute from NULL to 1 and commits
* User B modifies Comm attribute from NULL to 55 and commits
* User B receives the "RowInconsistentException"
And, you should see:
* Modified value of Comm in User B's Emp row stays at its modified value (as would any attributes that are modified in its current transaction)
* Any unmodified values (like User B's Emp row's Sal value) will be refreshed to the current state of the database, so it should now be 4999
If you are using JSF and partial submits, you might need to configure PPR to see these data changes reflected accurately in the JSF page.

Re: what is difference between sap locking and database locking

hi,
    what is difference between sap locking and database locking. Iam locked the table mara by using lock objects.
But iam unable to unlock the mara table. I give u the coding. Please check it.
REPORT zlock .
CALL FUNCTION 'ENQUEUE_EZTEST3'
EXPORTING
   MODE_MARA            = 'S'
   MANDT                = SY-MANDT
   MATNR                = 'SOU-1'.
call transaction 'MM02'.
CALL FUNCTION 'DEQUEUE_EZTEST3'
     EXPORTING
          mode_mara = 'E'
          mandt     = sy-mandt
          matnr     = 'SOU-1'.
IF sy-subrc = 0.
WRITE: 'IT IS unlocked'.
ENDIF.

Hi Paluri
Here is the difference between SAP locks and Database locks, i will try to find the solution to your code.
Regards
Ashish
Database Locks: The database system automatically sets database locks when it receives change statements (INSERT, UPDATE, MODIFY, DELETE) from a program. Database locks are physical locks on the database entries affected by these statements. You can only set a lock for an existing database entry, since the lock mechanism uses a lock flag in the entry. These flags are automatically deleted in each database commit. This means that database locks can never be set for longer than a single database LUW; in other words, a single dialog step in an R/3 application program.
Physical locks in the database system are therefore insufficient for the requirements of an R/3 transaction. Locks in the R/3 System must remain set for the duration of a whole SAP LUW, that is, over several dialog steps. They must also be capable of being handled by different work processes and even different application servers. Consequently, each lock must apply on all servers in that R/3 System.
SAP Locks:
To complement the SAP LUW concept, in which bundled database changes are made in a single database LUW, the R/3 System also contains a lock mechanism, fully independent of database locks, that allows you to set a lock that spans several dialog steps. These locks are known as SAP locks.
The SAP lock concept is based on lock objects. Lock objects allow you to set an SAP lock for an entire application object. An application object consists of one or more entries in a database table, or entries from more than one database table that are linked using foreign key relationships.
Before you can set an SAP lock in an ABAP program, you must first create a lock object in the ABAP Dictionary.

Locking problem in VL02N at the time Post Goods issue

Hi,
We have implemented 2 BADIs to change qty in delivery and in subsequent documents. Once we receive an IDoc with batches, then we need to change subitems qty according to no of batches.
Once IDoc has updated, then PGI will do automatically.
1. LE_SHP_DELIVERY_PROC - Change qty in delivery (Method SAVE_DOCUMENT_PREPARE)
2. LE_SHP_GOODSMOVEMENT - Change qty in material document.
Now, we have a locking problem at the time of posting.
Please let us know, due to these BADI implementation this problem or any other cause? And provide required to solve this problem.

hi ,
do i need to do step 2....?
i dont think u need step2 ( change qty of MBLNR),bcos ,
say ur Del.qty is 100, now u want to do del. of 50, then just u will change its qty & do PGI ? so whats the need of changing MBLNR.
while doing PGI , program will take changed qty of del. only ?
let me know if i'm wrong.
regards
Prabhu

Database locks in OBPM 10gR3

Environment:
Oracle BPM 10gR3 Version: 10.3.1.0.0 Build: #99954
WebLogic Server 10.0 MP1 Clustered domain
JDBC Driver - WebLogic Type 4 XA ( weblogic.jdbcx.oracle.OracleDataSource )
We have a BPM project deployed on the WLS 10.0 MP1 Cluster,which was running fine for the last 18 months. But all of a sudden we are experiencing the database locks errors for the last few days, when we try to restart the BPM Engine.
WebLogic JTA Timeout = 30 seconds
Database Distributed_Lock_Timeout = 60 seconds
WebLogic Datasources for Directory and Engine XA Connection Timeout = 30 seconds
Error
Process '/Test#Default-1.0' could not be started. Details:\nProcess execution engine execution error.
Caused by: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:79)
     at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
     at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
     at fuego.ejbengine.service.EJBActiveProcessService.startProcess(EJBActiveProcessService.java:92)
     at fuego.server.service.ActiveProcessService.runProcessesLoader(ActiveProcessService.java:118)
     at fuego.server.service.ActiveProcessService.activateProcesses(ActiveProcessService.java:88)
     at fuego.ejbengine.service.EJBActiveProcessService.doActivateProcesses(EJBActiveProcessService.java:63)
     at fuego.ejbengine.cluster.DistributedEJBActiveProcessService.initialize(DistributedEJBActiveProcessService.java:37)
     at fuego.ejbengine.cluster.ClusterObjectFactory.initializeActiveProcessService(ClusterObjectFactory.java:33)
     at fuego.ejbengine.Engine.startServices(Engine.java:448)
     at fuego.ejbengine.Engine.start(Engine.java:129)
     at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
     at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
     at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
     at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
     at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
     at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1330)
     at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
     at $Proxy57.updateDeployedProcess(Unknown Source)
     at fuego.directory.DirDeployedProcess.update(DirDeployedProcess.java:1022)
     at fuego.server.ActiveProcessManager.handleProcess(ActiveProcessManager.java:496)
     at fuego.server.service.ActiveProcessService.startProcess(ActiveProcessService.java:136)
     at fuego.ejbengine.service.EJBActiveProcessService.startProcessImpl(EJBActiveProcessService.java:107)
     at fuego.ejbengine.service.EJBActiveProcessService.access$100(EJBActiveProcessService.java:32)
     at fuego.ejbengine.service.EJBActiveProcessService$2.execute(EJBActiveProcessService.java:95)
     at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
     at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
     at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
     at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
     at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
     ... 52 more
Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
     at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
     at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
     at weblogic.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
     at weblogic.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
     at weblogic.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
     at weblogic.jdbcx.base.BasePreparedStatementWrapper.executeUpdate(Unknown Source)
     at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:125)
     at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
     at fuego.directory.provider.jdbc.JDBCPersistenceManager.update(JDBCPersistenceManager.java:946)
     at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1327)
     ... 68 more

Hello -
Following is the Oracle recommendation for BPM timeouts. Now you can try this.
Increase the timeout:
-in the Oracle Weblogic console go to Services -> JTA -> Timeout Seconds . Set the value to 300.
also the DISTRIBUTED_LOCK_TIMEOUT value for BPM should follow the following formula:
DISTRIBUTED_LOCK_TIMEOUT >= XA Transaction Timeout >= WebLogic Server JTA timeout
This means that the configured "DISTRIBUTED_LOCK_TIMEOUT" value should be equal to or
larger than the "XA Transaction Timeout" value which in turn should be equal to or larger than the "WebLogic Server JTA timeout".
Note : Check your previous BPM Engine logs, you can see the timeout warning.
BR,
Justin.

Lock Problem while Broadcasting multiple reports using process chains

Hi All,
I am trying to broadcast 10 reports using the process chains using the program for RSRD_START and variants created in the Broadcaster..the Program jobs start fine.But I am facing the error that the RSRA_CA_LOG table is getting locked while trying to broadcast the Reports..Can any help me on how to run the jobs without the locking problem..Suggestions please.
Thanks,
Mike.

Hi,
Thanks for the Inputs and the SAP Notes.
I am trying to broadcast the Reports from the the Bex Analyer and getting this ock error and not the workbooks.
I am also trying to Broadcast the Workbooks also, but could not find the options to Broadcast them. we are in SAP -BW3.5 SP 12, Is it possible to broadcast the workbooks in this Patch level..or do we need to upgrade to achieve this.If so...can any one provide me the proceedure to Broadcast the Workbooks.
Thanks,
Mike.

Immediate HELP in Tomcat 5 to Postgresql 7.4 database connectivity problem

Hi,
I failed to connect Tomcat 5.0.24 with Postgresql
7.4.2. The files created by me and the changes i had
made in the existing files are rates.jsp,
conversionDAO.java, web.xml and server.xml. The error
message on the top of the rest of it was "The value of
useBean class attribute converter.conversionDAO is
invalid". So far I found out that the coding for
database connectivity purpose in conversionDAO.java
cause the error. Another thing is Postgresql jdbc
driver is required to set in the CLASSPATH for the
java file to access the Postgresql database. I don't
know where should I put it in Tomcat for web
application. Anyway, I put it in
$CATALINA_HOME/shared/lib according the book i
refered. I do the database connectivity coding refer
to the Tomcat Kick Start book from Sams Publishing.
Below are the coding involved, please show me the
mistake i had made. Thank you.
----server.xml----
<Context path="/database"
docBase="${catalina.home}/webapps/database" debug="0"
reload="true">
<ResourceParams name="jdbc/conversion">
<parameter>
<name>username</name>
<value>myusername</value>
</parameter>
<parameter>
<name>password</name>
<value>mypassword</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>org.postgresql.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:postgresql://localhost/conversion</value>
</parameter>
</ResourceParams>
</Context>
----web.xml----
<servlet>
<servlet-name>conversionDAO</servlet-name>
<servlet-class>converters.conversionDAO</servlet-class>
</servlet>
<resource-ref>
<res-ref-name>jdbc/conversion</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
----conversionDAO.java----
public conversionDAO() throws SQLException,
NamingException
Context init = new InitialContext();
Context ctx = (Context)
init.lookup("java:comp/env");
DataSource ds = (DataSource)
ctx.lookup("jdbc/conversion");
con = ds.getConnection();
select = con.prepareStatement(
"SELECT rate FROM Exchange WHERE src= ? AND dst =

Immediate HELP in Tomcat 5 to Postgresql 7.4 database connectivity problem (cont.)
Errors log
2004-06-06 01:07:53 StandardContext[servlets-examples]SessionListener: contextDestroyed()
2004-06-06 01:07:53 StandardContext[servlets-examples]ContextListener: contextDestroyed()
2004-06-06 01:07:53 StandardContext[jsp-examples]SessionListener: contextDestroyed()
2004-06-06 01:07:53 StandardContext[jsp-examples]ContextListener: contextDestroyed()
2004-06-06 01:07:59 StandardContext[balancer]org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
2004-06-06 01:08:00 StandardContext[jsp-examples]ContextListener: contextInitialized()
2004-06-06 01:08:00 StandardContext[jsp-examples]SessionListener: contextInitialized()
2004-06-06 01:08:00 StandardContext[servlets-examples]ContextListener: contextInitialized()
2004-06-06 01:08:00 StandardContext[servlets-examples]SessionListener: contextInitialized()
2004-06-06 01:08:01 StandardWrapperValve[jsp]: Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /rates/rates.jsp(5,0) The value for the useBean class attribute converters.conversionDAO is invalid.
     at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:39)
     at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:357)
     at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:141)
     at org.apache.jasper.compiler.Generator$GenerateVisitor.visit(Generator.java:1217)
     at org.apache.jasper.compiler.Node$UseBean.accept(Node.java:1116)
     at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
     at org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213)
     at org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219)
     at org.apache.jasper.compiler.Node$Root.accept(Node.java:456)
     at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163)
     at org.apache.jasper.compiler.Generator.generate(Generator.java:3261)
     at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:244)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
     at org.apache.jasper.compiler.Compiler.compile(Compiler.java:422)
     at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:507)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:274)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
----more----

Database configuring problem in setup of managed systems in SMD

Hello,
i'm doing the setup of a CRM 5.0 in SMD Abap+Java and the setup results returns following:
"Database configuration problem" with the exception:
java.lang.NullPointerException
     at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:114)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.configureCustomProperties(ConfigurationTask.java:242)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.configureProperties(ConfigurationTask.java:370)
     at com.sap.smd.agent.plugins.database.ConfigurationTask.execute(ConfigurationTask.java:124)
     at com.sap.sup.admin.setup.AppCfgTasks.configureDbApp(AppCfgTasks.java:115)
     at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:202)
     at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:217)
     at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:461)
     at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:26)
     at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:669)
     at java.lang.Thread.run(Thread.java:534)
Anybody knows which can be the problem?
Thanks a lot
Carlos

Hi Shriraj,
ensure that the installation path is correct. I only put /urs/sap/<SID> and you must put /usr/sap/<SID>/DV***/.
In my case with that the setup returns all in green.
I hope it helps you
Regards
Carlos

SIMPLE Database Design Problem !

Mapping is a big problem for many complex applications.
So what happens if we put all the tables into one table called ENTITY?
I have more than 300 attributeTypes.And there will be lots of null values in the records of that single table as every entityType uses the same table.
Other than wasting space if I put a clustered index on my entityType coloumn in that table.What kind of performance penalties to I get?
Definition of the table
ENTITY
EntityID > uniqueidentifier
EntityType > Tells the entityTypeName
Name >
LastName >
CompanyName > 300 attributeTypes
OppurtunityPeriod >
PS:There is also another table called RELATION that points the relations between entities.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
check the coloumn with WHERE _entityType='PERSON'
as there is is clustered index on entityType...there
is NO performance decrease.
there is also a clustered index on RELATION table on
relationType
when we say WHERE _entityType ='PERSON' or
WHERE relationType='CONTACTMECHANISM'.
it scans the clustered index first.it acts like a
table as it is physically ordered.I was thinking in terms of using several conditions in the same select, such as
WHERE _entityType ='PERSON'
AND LastName LIKE 'A%' In your case you have to use at least two indices, and since your clustered index comes first ...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Have you ever thought of using constraints in your
modell? How would you realize those?
...in fact we did.We have arranged the generic object
model in an object database.The knowledge information
is held in the object database.So your relational database is used only as a "simple" storage, everything has go through your object database.
But the data schema is held in the RDBMS with code
generation that creates a schema to hold data.If you think that this approach makes sense, why not.
But in able to have a efficent mapping and a good
performance we have thought about building only one
table.The problem is we know we are losing some space
but the thing is harddisk is much cheaper than RAM
and CPU.So our trade off concerated on the storage
cost.But I still wonder if there is a point that I
have missed in terms performance?Just test your approach by using sufficiently data - only you know how many records you have to store in your modell.
PS: it is not wise effective using generic object
models also in object databases as CPU cost is a lot
when u are holding the data.I don't know if I'd have taken your approach - using two database systems to hold data and business logic.
PS2: RDBMS is a value based system where object
databases are identity based.we are trying to be in
the gray area of both worlds.Like I wrote: if your approach works and scales to the required size, why not? I would assume that you did a load test with your approach.
What I would question though is that your discussing a "SIMPLE Database Design" problem. I don't see anything simple in your approach when it comes to implementation.
C.

Unwanted Database Lock when using CAF BO method 'update'

Hi all
We are using the Composite Application Framework (CAF), and Business Objects (BOs) to save data on the database. A service call is using a BO ‘Update’ method as follows:
_location.debugT("Test debug line 4");
getBOSalesDataService().update(salesData);
_location.debugT("Test debug line 5");
The same method is then called by another service, while the first service is still active. It does not error, but it waits until the first service has timed out. You can see this from the following screenshot:
I think this is because the first service sets a lock on the SQL database. This is not an explicitly coded lock, but a database lock. I’ve tried using the following statement:
getBOSalesDataService().unlock(salesData.getKey(), IBusinessObjectNodeServiceBase.MODE_WRITE);
It doesn’t work. I think this because the lock was not created by a ‘lock’ statement. Are there any other statements I can use to commit
all database updates? If it was ABAP, I would use a ‘COMMIT WORK’, is there a Java / CAF equivalent?
I have spoken to our Basis consultants, they have shown me Solution Manager where we can actually see the locks happening. Session ID 53
is the first update, 54 is the second.
Thanks
Iwan

For updates you actually need a lock to avoid inconsistencies.
the lock should automatically be released when the JTA transaction is completed - in the case of CMP EJBs when the first service is finished...

Database locks problem

Similar Messages

Maybe you are looking for