Slow Performance due to JDBC Version ?

Technical Support for an application that uses Oracle Spatial data told me that slow application performance could be due to an old version of JDBC drivers. Has anyone else encountered this issue?
I am using Oracle 8.1.7 Release 3 on Sun Solaris. My application uses the thin Oracle driver that came with the client installation in classes12.zip.
Is there a better JDBC version for Spatial data?
Andrew Greis
FCC/CompuTech

 
Satellite P55-A5200
seemed to really slow down to a crawl  ...   Am I looking at virus or bad memory module?
More likely your hard drive is failing. Multiple read/write attempts slow things down.
Time to immediately back up everything important. Also, create an image of the drive on an external disk.
Then run chkdsk /r at an elevated command prompt. It will insist upon rebooting Windows. Reply Yes and restart Windows. Expect this to take quite a while on a 750 GB disk.

Similar Messages

  • Extremely slow performance on projects under version control using RoboHelp 11, PushOk, Tortoise SVN repository

    We are also experiencing extremely slow performance for RoboHelp projects under version control. We are using RoboHelp 11, PushOk and a Tortoise SVN repository on a Linux server. We are using a Linux server on our IT guys advice because we found SVN version control under Windows was unstable.
    When placing a Robohelp project under version control, and yes the project is on my local machine, it can take up to two hours to complete. We are using the RoboHelp sample projects to test.
    We have tried to put the project under version control from Robohelp, and also tried first putting the project under version control from Tortoise SVN, and then trying to open the project from version control in Robohelp. In both cases, the project takes a ridiculous amount of time to open. The Robohelp status bar displays Querying Version Control Status for about an hour before it starts to download from the repository, which then takes more than an hour to complete. In many cases Robohelp becomes unresponsive and we have to start the whole process again.
    If adding the project to source control completes successfully, and the the project is opened from version control, performing any function also takes a very long time, such as creating a topic. When I generated a printed documentation layout it took an astonishing 218 minutes and 17 seconds to complete. Interestingly, when I generated the printed documentation layout again, it took 1 min and 34 seconds. However when I closed the project, opened from version control, and tried to generate a printed documentation layout, it again took several hours to complete. The IT guys are at a loss, and say it is not a network issue and I am starting to agree that this is a RoboHelp issue.
    I see there are a few other discussions here related to this kind of poor performance, none of which seem to been answered satisfactorily. For example:
    Why does it take so long when adding a new topic in RH10 with PushOK SVN
    Does anybody have any ideas on what we can do or what we can investigate? I know that there are options for version control, but am reluctant to pursue them until I am satisfied that our current issues cannot be resolved.
    Thanks Mark

    Do other applications work fine with the source control repository? The reason I'm asking is because you must first rule out that there are external factors causing this behaviour. It seems that your it guys have already looked at it, but it's better to be safe than sorry.
    I have used both VSS and TFS and I haven't encountered such a performance issue. I would suggest filing it as a bug if you rule out that the problem is not related to external influences: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform&loc=en
    Kind regards,
    Willam

  • Slow performance WLS with jdbc pools

    Hi all, we have follow configuration of our system: the server with applications and server with jdbc pools. Recently we get strange situation. The server with jdbc pools it seems hung. We get thread dumps for this server and we see that it not hung, but normally work but very slow. Many weblogic.kernel.Default threads were busy by rmi database calls (see below). Anothe strange that before slowing server work nothing enties in server log. Last entry in server log were one hour before slow work. May someone propose why this situation can occure?
    Thread dump:
    <b>"ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" id=11 idx=0x1c tid=6668 prio=5 alive, daemon
    at java/util/WeakHashMap.get(Ljava/lang/Object;)Ljava/lang/Object;(WeakHashMap.java:342)[optimized]
    at weblogic/rmi/internal/ClientRuntimeDescriptor.intern(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(ClientRuntimeDescriptor.java:130)[inlined]
    at weblogic/rmi/internal/BasicRuntimeDescriptor.getClientRuntimeDescriptor(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(BasicRuntimeDescriptor.java:459)[optimized]
    at weblogic/rmi/internal/BasicServerRef.getStub()Ljava/lang/Object;(BasicServerRef.java:656)[optimized]
    at weblogic/rmi/internal/OIDManager.getReplacement(Ljava/lang/Object;)Ljava/lang/Object;(OIDManager.java:189)[optimized]
    at weblogic/rmi/extensions/StubFactory.getStub(Ljava/rmi/Remote;)Ljava/lang/Object;(StubFactory.java:66)
    at weblogic/jdbc/rmi/internal/CallableStatementImpl.interopWriteReplace(Lweblogic/common/internal/PeerInfo;)Ljava/lang/Object;(CallableStatementImpl.java:50)
    at weblogic/rmi/utils/io/InteropObjectReplacer.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(InteropObjectReplacer.java:38)[optimized]
    at weblogic/common/internal/ChunkedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:54)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:249)[optimized]
    at java/io/ObjectOutputStream.writeObject0(Ljava/lang/Object;Z)V(Unknown Source)[inlined]
    at java/io/ObjectOutputStream.writeObject(Ljava/lang/Object;)V(Unknown Source)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream.writeObject(Ljava/lang/Object;)V(ChunkedObjectOutputStream.java:120)[inlined]
    at weblogic/rjvm/MsgAbbrevOutputStream.writeObject(Ljava/lang/Object;Ljava/lang/Class;)V(MsgAbbrevOutputStream.java:94)[optimized]
    at weblogic/jdbc/rmi/internal/ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)[optimized]
    at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:477)[optimized]
    at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:420)[inlined]
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)[inlined]
    at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)[inlined]
    at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:415)[inlined]
    at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:27)[optimized]
    at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:219)[optimized]
    at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace
    "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" id=12 idx=0x1e tid=6669 prio=5 alive, daemon
    at java/util/WeakHashMap.get(Ljava/lang/Object;)Ljava/lang/Object;(WeakHashMap.java:346)[optimized]
    at weblogic/rmi/internal/ClientRuntimeDescriptor.intern(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(ClientRuntimeDescriptor.java:130)[inlined]
    at weblogic/rmi/internal/BasicRuntimeDescriptor.getClientRuntimeDescriptor(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(BasicRuntimeDescriptor.java:459)[optimized]
    at weblogic/rmi/internal/BasicServerRef.getStub()Ljava/lang/Object;(BasicServerRef.java:656)[optimized]
    at weblogic/rmi/internal/OIDManager.getReplacement(Ljava/lang/Object;)Ljava/lang/Object;(OIDManager.java:189)[optimized]
    at weblogic/rmi/extensions/StubFactory.getStub(Ljava/rmi/Remote;)Ljava/lang/Object;(StubFactory.java:66)
    at weblogic/jdbc/rmi/internal/CallableStatementImpl.interopWriteReplace(Lweblogic/common/internal/PeerInfo;)Ljava/lang/Object;(CallableStatementImpl.java:50)
    at weblogic/rmi/utils/io/InteropObjectReplacer.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(InteropObjectReplacer.java:38)[optimized]
    at weblogic/common/internal/ChunkedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:54)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:249)[optimized]
    at java/io/ObjectOutputStream.writeObject0(Ljava/lang/Object;Z)V(Unknown Source)[inlined]
    at java/io/ObjectOutputStream.writeObject(Ljava/lang/Object;)V(Unknown Source)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream.writeObject(Ljava/lang/Object;)V(ChunkedObjectOutputStream.java:120)[inlined]
    at weblogic/rjvm/MsgAbbrevOutputStream.writeObject(Ljava/lang/Object;Ljava/lang/Class;)V(MsgAbbrevOutputStream.java:94)[optimized]
    at weblogic/jdbc/rmi/internal/ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)[optimized]
    at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:477)[optimized]
    at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:420)[inlined]
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)[inlined]
    at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)[inlined]
    at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:415)[inlined]
    at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:27)[optimized]
    at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:219)[optimized]
    at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace</b>

    Denis Reimer wrote:
    Hi all, we have follow configuration of our system: the server with applications and server with jdbc pools. Recently we get strange situation. The server with jdbc pools it seems hung. We get thread dumps for this server and we see that it not hung, but normally work but very slow. Many weblogic.kernel.Default threads were busy by rmi database calls (see below). Anothe strange that before slowing server work nothing enties in server log. Last entry in server log were one hour before slow work. May someon
    e propose why this situation can occure?
    Thread dump:
    <b>"ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" id=11 idx=0x1c tid=6668 prio=5 alive, daemon
    at java/util/WeakHashMap.get(Ljava/lang/Object;)Ljava/lang/Object;(WeakHashMap.java:342)[optimized]
    at weblogic/rmi/internal/ClientRuntimeDescriptor.intern(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(ClientRuntimeDescriptor.java:130)[inlined]
    at weblogic/rmi/internal/BasicRuntimeDescriptor.getClientRuntimeDescriptor(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(BasicRuntimeDescriptor.java:459)[optimized]
    at weblogic/rmi/internal/BasicServerRef.getStub()Ljava/lang/Object;(BasicServerRef.java:656)[optimized]
    at weblogic/rmi/internal/OIDManager.getReplacement(Ljava/lang/Object;)Ljava/lang/Object;(OIDManager.java:189)[optimized]
    at weblogic/rmi/extensions/StubFactory.getStub(Ljava/rmi/Remote;)Ljava/lang/Object;(StubFactory.java:66)
    at weblogic/jdbc/rmi/internal/CallableStatementImpl.interopWriteReplace(Lweblogic/common/internal/PeerInfo;)Ljava/lang/Object;(CallableStatementImpl.java:50)
    at weblogic/rmi/utils/io/InteropObjectReplacer.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(InteropObjectReplacer.java:38)[optimized]
    at weblogic/common/internal/ChunkedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:54)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:249)[optimized]
    at java/io/ObjectOutputStream.writeObject0(Ljava/lang/Object;Z)V(Unknown Source)[inlined]
    at java/io/ObjectOutputStream.writeObject(Ljava/lang/Object;)V(Unknown Source)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream.writeObject(Ljava/lang/Object;)V(ChunkedObjectOutputStream.java:120)[inlined]
    at weblogic/rjvm/MsgAbbrevOutputStream.writeObject(Ljava/lang/Object;Ljava/lang/Class;)V(MsgAbbrevOutputStream.java:94)[optimized]
    at weblogic/jdbc/rmi/internal/ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)[optimized]
    at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:477)[optimized]
    at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:420)[inlined]
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)[inlined]
    at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)[inlined]
    at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:415)[inlined]
    at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:27)[optimized]
    at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:219)[optimized]
    at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace
    "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" id=12 idx=0x1e tid=6669 prio=5 alive, daemon
    at java/util/WeakHashMap.get(Ljava/lang/Object;)Ljava/lang/Object;(WeakHashMap.java:346)[optimized]
    at weblogic/rmi/internal/ClientRuntimeDescriptor.intern(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(ClientRuntimeDescriptor.java:130)[inlined]
    at weblogic/rmi/internal/BasicRuntimeDescriptor.getClientRuntimeDescriptor(Ljava/lang/String;)Lweblogic/rmi/internal/ClientRuntimeDescriptor;(BasicRuntimeDescriptor.java:459)[optimized]
    at weblogic/rmi/internal/BasicServerRef.getStub()Ljava/lang/Object;(BasicServerRef.java:656)[optimized]
    at weblogic/rmi/internal/OIDManager.getReplacement(Ljava/lang/Object;)Ljava/lang/Object;(OIDManager.java:189)[optimized]
    at weblogic/rmi/extensions/StubFactory.getStub(Ljava/rmi/Remote;)Ljava/lang/Object;(StubFactory.java:66)
    at weblogic/jdbc/rmi/internal/CallableStatementImpl.interopWriteReplace(Lweblogic/common/internal/PeerInfo;)Ljava/lang/Object;(CallableStatementImpl.java:50)
    at weblogic/rmi/utils/io/InteropObjectReplacer.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(InteropObjectReplacer.java:38)[optimized]
    at weblogic/common/internal/ChunkedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:54)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream$NestedObjectOutputStream.replaceObject(Ljava/lang/Object;)Ljava/lang/Object;(ChunkedObjectOutputStream.java:249)[optimized]
    at java/io/ObjectOutputStream.writeObject0(Ljava/lang/Object;Z)V(Unknown Source)[inlined]
    at java/io/ObjectOutputStream.writeObject(Ljava/lang/Object;)V(Unknown Source)[inlined]
    at weblogic/common/internal/ChunkedObjectOutputStream.writeObject(Ljava/lang/Object;)V(ChunkedObjectOutputStream.java:120)[inlined]
    at weblogic/rjvm/MsgAbbrevOutputStream.writeObject(Ljava/lang/Object;Ljava/lang/Class;)V(MsgAbbrevOutputStream.java:94)[optimized]
    at weblogic/jdbc/rmi/internal/ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(ILweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;Ljava/lang/Object;)Lweblogic/rmi/spi/OutboundResponse;(Unknown Source)[optimized]
    at weblogic/rmi/internal/BasicServerRef.invoke(Lweblogic/rmi/extensions/server/RuntimeMethodDescriptor;Lweblogic/rmi/spi/InboundRequest;Lweblogic/rmi/spi/OutboundResponse;)V(BasicServerRef.java:477)[optimized]
    at weblogic/rmi/internal/BasicServerRef$1.run()Ljava/lang/Object;(BasicServerRef.java:420)[inlined]
    at weblogic/security/acl/internal/AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(AuthenticatedSubject.java:363)[inlined]
    at weblogic/security/service/SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedExceptionAction;)Ljava/lang/Object;(SecurityManager.java:147)[inlined]
    at weblogic/rmi/internal/BasicServerRef.handleRequest(Lweblogic/rmi/spi/InboundRequest;)V(BasicServerRef.java:415)[inlined]
    at weblogic/rmi/internal/BasicExecuteRequest.execute(Lweblogic/kernel/ExecuteThread;)V(BasicExecuteRequest.java:27)[optimized]
    at weblogic/kernel/ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V(ExecuteThread.java:219)[optimized]
    at weblogic/kernel/ExecuteThread.run()V(ExecuteThread.java:178)
    at jrockit/vm/RNI.c2java(IIII)V(Native Method)
    -- end of trace</b>Hi. It seems you're doing JDBC in an external client, using our RMI-based
    JDBC wrappers to the actual connection in the WLS server, and you are
    doing LOB retrieval. This means your query goes from your client to
    the WLS process, and then to the DBMS, and the LOB data (big) has to go
    from the DBMS to the WLS process and then back over RMI to your client.
    This is bound to be inefficient. If you can move your JDBC to a JSP or
    other serverside class, it will be much faster. Otherwise, if the
    management that WLS provides is not strictly necessary for the LOB
    manipulation, it may be faster to get that directly from the DBMS to
    the external client by using the vendor's JDBC driver directly.
    Joe

  • Lion slow performance due to hanging TCP sessions

    After upgrading to 10.7.2 I experienced that Safari and Mail hangs.
    After a reboot the problem was gone but occured again after a while.
    I found out that a lot of TCP sessions were in the CLOSE_WAIT state.
    The affekted deamon was ocspd.
    I killed the deamon and it restarted automatically. The problem related to hanging https sessions Safari an Mail was gone.
    The problem occurs again and again.
    Does someboda have an idea how to solve this issue.
    Bellow I listed some output:
    Hinkelstein:~ mav$ sudo lsof -i -P | grep CLOSE_WAIT
    applepush  372           root   13u  IPv4 0xffffff801434e320      0t0    TCP 192.168.10.52:53317->nk11p01st-courier018-bz.push.apple.com:443 (CLOSE_WAIT)
    WebProces 3720            mav   16u  IPv4 0xffffff802e9ce880      0t0    TCP 192.168.66.154:54481->tls_server.uslendernetwork.com:80 (CLOSE_WAIT)
    WebProces 3720            mav   17u  IPv4 0xffffff80330fac20      0t0    TCP 172.20.1.73:58913->172.20.5.7:443 (CLOSE_WAIT)
    PubSubAge 7794            mav   19u  IPv4 0xffffff80344426c0      0t0    TCP 172.20.1.73:59003->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root    3u  IPv4 0xffffff802f6b84e0      0t0    TCP 172.20.1.73:58847->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root    7u  IPv4 0xffffff803310d6c0      0t0    TCP 172.20.1.73:59014->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root    8u  IPv4 0xffffff802e03ba40      0t0    TCP 172.20.1.73:58849->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root    9u  IPv4 0xffffff802e952c00      0t0    TCP 172.20.1.73:58845->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   10u  IPv4 0xffffff8033150fa0      0t0    TCP 172.20.1.73:58850->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   11u  IPv4 0xffffff80330f6c00      0t0    TCP 172.20.1.73:58878->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   12u  IPv4 0xffffff8034443c20      0t0    TCP 172.20.1.73:58843->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   13u  IPv4 0xffffff802e8b0160      0t0    TCP 172.20.1.73:58844->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   14u  IPv4 0xffffff80331404e0      0t0    TCP 172.20.1.73:58856->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   15u  IPv4 0xffffff802e9b54e0      0t0    TCP 172.20.1.73:58892->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   18u  IPv4 0xffffff802e8afa40      0t0    TCP 172.20.1.73:58867->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   19u  IPv4 0xffffff802f6bafa0      0t0    TCP 172.20.1.73:58863->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   20u  IPv4 0xffffff803317dc20      0t0    TCP 172.20.1.73:58885->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   21u  IPv4 0xffffff8033164c20      0t0    TCP 172.20.1.73:58884->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   22u  IPv4 0xffffff8033141320      0t0    TCP 172.20.1.73:58871->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   23u  IPv4 0xffffff80331396c0      0t0    TCP 172.20.1.73:58874->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   24u  IPv4 0xffffff802e9b7160      0t0    TCP 172.20.1.73:58881->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   25u  IPv4 0xffffff8033171c00      0t0    TCP 172.20.1.73:58897->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   26u  IPv4 0xffffff801434f880      0t0    TCP 172.20.1.73:58918->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   27u  IPv4 0xffffff80330f7320      0t0    TCP 172.20.1.73:58877->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   28u  IPv4 0xffffff802f6c4880      0t0    TCP 172.20.1.73:58899->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   29u  IPv4 0xffffff802e8bac00      0t0    TCP 172.20.1.73:58917->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   30u  IPv4 0xffffff803316afa0      0t0    TCP 172.20.1.73:58964->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   31u  IPv4 0xffffff8034441160      0t0    TCP 172.20.1.73:58906->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   32u  IPv4 0xffffff802e956500      0t0    TCP 172.20.1.73:58985->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   33u  IPv4 0xffffff8033172a40      0t0    TCP 172.20.1.73:58905->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   34u  IPv4 0xffffff8033106c20      0t0    TCP 172.20.1.73:58935->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   35u  IPv4 0xffffff802e9b6a40      0t0    TCP 172.20.1.73:58904->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   36u  IPv4 0xffffff8033136c00      0t0    TCP 172.20.1.73:58965->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   37u  IPv4 0xffffff8033138880      0t0    TCP 172.20.1.73:58980->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   38u  IPv4 0xffffff8033147c00      0t0    TCP 172.20.1.73:58915->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   39u  IPv4 0xffffff802e954160      0t0    TCP 172.20.1.73:58966->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   40u  IPv4 0xffffff8033138fa0      0t0    TCP 172.20.1.73:58938->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   41u  IPv4 0xffffff8033149160      0t0    TCP 172.20.1.73:58933->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   42u  IPv4 0xffffff8033103a40      0t0    TCP 172.20.1.73:58939->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   43u  IPv4 0xffffff8033142880      0t0    TCP 172.20.1.73:58930->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   44u  IPv4 0xffffff80331056c0      0t0    TCP 172.20.1.73:58940->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   45u  IPv4 0xffffff8033173fa0      0t0    TCP 172.20.1.73:58937->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   46u  IPv4 0xffffff801434dc00      0t0    TCP 172.20.1.73:58941->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   47u  IPv4 0xffffff803314fa40      0t0    TCP 172.20.1.73:58992->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   48u  IPv4 0xffffff803312ffa0      0t0    TCP 172.20.1.73:58975->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   49u  IPv4 0xffffff803314b500      0t0    TCP 172.20.1.73:58981->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   50u  IPv4 0xffffff8033104880      0t0    TCP 172.20.1.73:58967->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   51u  IPv4 0xffffff80330fa500      0t0    TCP 172.20.1.73:58982->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   52u  IPv4 0xffffff802e9cf6c0      0t0    TCP 172.20.1.73:59033->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   53u  IPv4 0xffffff8033142160      0t0    TCP 172.20.1.73:58969->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   54u  IPv4 0xffffff802e9ccc00      0t0    TCP 172.20.1.73:58989->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   55u  IPv4 0xffffff8033149880      0t0    TCP 172.20.1.73:58970->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   56u  IPv4 0xffffff802e9b8de0      0t0    TCP 172.20.1.73:59004->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   57u  IPv4 0xffffff80331516c0      0t0    TCP 172.20.1.73:58971->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   58u  IPv4 0xffffff803317cde0      0t0    TCP 172.20.1.73:58972->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   59u  IPv4 0xffffff8034623500      0t0    TCP 172.20.1.73:59023->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   60u  IPv4 0xffffff802e03a4e0      0t0    TCP 172.20.1.73:59081->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   61u  IPv4 0xffffff803461fc00      0t0    TCP 172.20.1.73:59034->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   62u  IPv4 0xffffff803314a6c0      0t0    TCP 172.20.1.73:59042->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   63u  IPv4 0xffffff802e9944e0      0t0    TCP 172.20.1.73:59075->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   64u  IPv4 0xffffff802e9cda40      0t0    TCP 172.20.1.73:59016->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   65u  IPv4 0xffffff803312ea40      0t0    TCP 172.20.1.73:59026->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   66u  IPv4 0xffffff8033161a40      0t0    TCP 172.20.1.73:59036->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   67u  IPv4 0xffffff80331364e0      0t0    TCP 172.20.1.73:59018->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   68u  IPv4 0xffffff80331684e0      0t0    TCP 172.20.1.73:59056->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   69u  IPv4 0xffffff8034621fa0      0t0    TCP 172.20.1.73:59019->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   70u  IPv4 0xffffff8033173880      0t0    TCP 172.20.1.73:59020->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   71u  IPv4 0xffffff802e8b0880      0t0    TCP 172.20.1.73:59035->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   72u  IPv4 0xffffff803310cfa0      0t0    TCP 172.20.1.73:59021->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   73u  IPv4 0xffffff8033175500      0t0    TCP 172.20.1.73:59067->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   74u  IPv4 0xffffff80331794e0      0t0    TCP 172.20.1.73:59022->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   75u  IPv4 0xffffff803314e4e0      0t0    TCP 172.20.1.73:59148->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   76u  IPv4 0xffffff8033172320      0t0    TCP 172.20.1.73:59052->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   77u  IPv4 0xffffff802f6c5de0      0t0    TCP 172.20.1.73:59095->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   78u  IPv4 0xffffff803443f4e0      0t0    TCP 172.20.1.73:59064->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   79u  IPv4 0xffffff8034443500      0t0    TCP 172.20.1.73:59082->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   80u  IPv4 0xffffff8033169320      0t0    TCP 172.20.1.73:59068->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   81u  IPv4 0xffffff8034622de0      0t0    TCP 172.20.1.73:59130->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   82u  IPv4 0xffffff8034629de0      0t0    TCP 172.20.1.73:59119->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   83u  IPv4 0xffffff802e8bba40      0t0    TCP 172.20.1.73:59054->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   84u  IPv4 0xffffff8033131500      0t0    TCP 172.20.1.73:59061->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   85u  IPv4 0xffffff8033139de0      0t0    TCP 172.20.1.73:59071->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   86u  IPv4 0xffffff8033163de0      0t0    TCP 172.20.1.73:59058->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   87u  IPv4 0xffffff802e9cd320      0t0    TCP 172.20.1.73:59096->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   88u  IPv4 0xffffff8034628fa0      0t0    TCP 172.20.1.73:59084->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   89u  IPv4 0xffffff803310a4e0      0t0    TCP 172.20.1.73:59080->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   90u  IPv4 0xffffff802e8ba4e0      0t0    TCP 172.20.1.73:59115->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   91u  IPv4 0xffffff802e8bec20      0t0    TCP 172.20.1.73:59085->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   92u  IPv4 0xffffff802e8bd6c0      0t0    TCP 172.20.1.73:59094->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   93u  IPv4 0xffffff802f6bb6c0      0t0    TCP 172.20.1.73:59138->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   94u  IPv4 0xffffff802e8b16c0      0t0    TCP 172.20.1.73:59117->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   95u  IPv4 0xffffff8033130de0      0t0    TCP 172.20.1.73:59103->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   96u  IPv4 0xffffff8033104160      0t0    TCP 172.20.1.73:59134->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   97u  IPv4 0xffffff802e954fa0      0t0    TCP 172.20.1.73:59104->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   98u  IPv4 0xffffff8033149fa0      0t0    TCP 172.20.1.73:59135->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root   99u  IPv4 0xffffff803312f880      0t0    TCP 172.20.1.73:59114->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  100u  IPv4 0xffffff802e9cc4e0      0t0    TCP 172.20.1.73:59140->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  101u  IPv4 0xffffff8034620320      0t0    TCP 172.20.1.73:59150->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  102u  IPv4 0xffffff803310ec20      0t0    TCP 172.20.1.73:59120->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  103u  IPv4 0xffffff802e9b6320      0t0    TCP 172.20.1.73:59116->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  104u  IPv4 0xffffff802e9cfde0      0t0    TCP 172.20.1.73:59126->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  105u  IPv4 0xffffff8033131c20      0t0    TCP 172.20.1.73:59127->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  106u  IPv4 0xffffff803317aa40      0t0    TCP 172.20.1.73:59183->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  107u  IPv4 0xffffff802f6bcc20      0t0    TCP 172.20.1.73:59129->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  109u  IPv4 0xffffff8033162fa0      0t0    TCP 172.20.1.73:59144->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  110u  IPv4 0xffffff8033144500      0t0    TCP 172.20.1.73:59156->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  111u  IPv4 0xffffff802e998500      0t0    TCP 172.20.1.73:59158->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  112u  IPv4 0xffffff803312f160      0t0    TCP 172.20.1.73:59154->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  113u  IPv4 0xffffff80330f8160      0t0    TCP 172.20.1.73:59185->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  115u  IPv4 0xffffff8033174de0      0t0    TCP 172.20.1.73:59177->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  116u  IPv4 0xffffff802f6c2c00      0t0    TCP 172.20.1.73:59187->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  117u  IPv4 0xffffff803314ade0      0t0    TCP 172.20.1.73:59172->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  118u  IPv4 0xffffff8034441880      0t0    TCP 172.20.1.73:59164->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  119u  IPv4 0xffffff803317d500      0t0    TCP 172.20.1.73:59179->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  120u  IPv4 0xffffff803316a160      0t0    TCP 172.20.1.73:59173->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  121u  IPv4 0xffffff80346226c0      0t0    TCP 172.20.1.73:59196->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  122u  IPv4 0xffffff802f6c6c20      0t0    TCP 172.20.1.73:59170->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  123u  IPv4 0xffffff803310ac00      0t0    TCP 172.20.1.73:59206->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  124u  IPv4 0xffffff80331636c0      0t0    TCP 172.20.1.73:59239->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  125u  IPv4 0xffffff80331306c0      0t0    TCP 172.20.1.73:59242->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  126u  IPv4 0xffffff801434f160      0t0    TCP 172.20.1.73:59215->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  128u  IPv4 0xffffff8033144c20      0t0    TCP 172.20.1.73:59208->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  129u  IPv4 0xffffff8033102c00      0t0    TCP 172.20.1.73:59209->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  130u  IPv4 0xffffff80331604e0      0t0    TCP 172.20.1.73:59233->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  131u  IPv4 0xffffff803461f4e0      0t0    TCP 172.20.1.73:59210->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  132u  IPv4 0xffffff803313a500      0t0    TCP 172.20.1.73:59211->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  133u  IPv4 0xffffff8033150160      0t0    TCP 172.20.1.73:59218->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  135u  IPv4 0xffffff802e03e500      0t0    TCP 172.20.1.73:59213->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  136u  IPv4 0xffffff80330f8880      0t0    TCP 172.20.1.73:59214->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  137u  IPv4 0xffffff8033104fa0      0t0    TCP 172.20.1.73:59241->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  138u  IPv4 0xffffff802e8be500      0t0    TCP 172.20.1.73:59234->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  140u  IPv4 0xffffff802e9524e0      0t0    TCP 172.20.1.73:59235->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  143u  IPv4 0xffffff803314f320      0t0    TCP 172.20.1.73:59237->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  144u  IPv4 0xffffff803316bde0      0t0    TCP 172.20.1.73:59225->172.20.5.7:443 (CLOSE_WAIT)
    ocspd     7823           root  145u  IPv4 0xffffff802e03dde0      0t0    TCP 172.20.1.73:59232->172.20.5.7:443 (CLOSE_WAIT)

    Hi
    Is ther anybody having the same problem?
    I still didn't got rid of it.

  • Slow performance of JDBC - ODBC MS ACCESS

    I experience a very slow performance for jdbc-odbc using ms access as the database. This program works fine with other computer (in term of performance). However, the harddrive is cranking big time with this computer (this is the fastest one among the computers I tested, and also has many gigabytes left to be used). The database is very small. Other computer use exactly the same java version and msaccess driver version. If anyone found the same problem, or have any suggestion please help. Thank you.

    I am having the same problem with one machine as well. Running MS Access 2000 (unfortunately), and all machines run well with one exception. DB reads take about 10 seconds each. If a solution has been found, please report.
    --Dave                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • BC_MSG slow performance

    I experience slow performance in a SAP PI 7.1EHP1 SP05 installation. The BC_MSG table contains about 550.000 messages. I archive and delete message that are 10 days old. The environment is Redhat Linux 5.5 64bit with 16GB RAM and oracle 10.2.0.4.<br>
    <br>
    The problem is when I want to query all message containg error in the last 7 days or more. It needs about 5 minutes to respond and sometimes more that ends with request timeout from ICM. I shrink the tables, rebuild the indexes, restart the system many times, apply latest service pack (SP06) but the performance remains unchanged.<br>
    <br>
    The query that is executed is the following:<br>
    <br>
    <pre>
    SELECT "MSG_ID","DIRECTION","REF_TO_MSG_ID","CORRELATION_ID","SEQUENCE_ID",
      "SEQUENCE_NBR","CONN_NAME","MSG_TYPE","STATUS","TO_PARTY_NAME",
      "TO_PARTY_TYPE","FROM_PARTY_NAME","FROM_PARTY_TYPE","TO_SERVICE_NAME",
      "TO_SERVICE_TYPE","FROM_SERVICE_NAME","FROM_SERVICE_TYPE","ACTION_NAME",
      "ACTION_TYPE","DELIVERY_SEMANTICS","SENT_RECV_TIME","TRAN_DELV_TIME",
      "SCHEDULE_TIME","PERSIST_UNTIL","TIMES_FAILED","RETRIES","RETRY_INTERVAL",
      "MSG_PROTOCOL","TRANSPORT","ADDRESS","CREDENTIAL","TRAN_HEADER",
      "VALID_UNTIL","NODE","ERROR_CODE","ERROR_CATEGORY","PP_USER","PP_HASH",
      "VERS_NBR","VERS_WAS_EDITED","PRIORITY_TYPE","PRIORITY"
    FROM
    "BC_MSG" WHERE "BC_MSG"."MSG_ID" IS NOT NULL AND ("STATUS" = :1 OR "STATUS" =
       :2) AND "SENT_RECV_TIME" >= :3 AND "SENT_RECV_TIME" <= :4 ORDER BY 21 DESC
    </pre>
    <br>
    Parameters:<br>
    :1 = 'FAIL'<br>
    :2 = 'NDLV'<br>
    :3 = 2011-03-01 08:06:02.34 (example)<br>
    :4 = 2011-03-02 08:06:02.34 (example)<br>
    <br>
    <br>
    This statement is executed for each day for the time interval I specify (e.g. 7 days of the week if the interval is 'Last 7 Days'). I don't know why they don't use one SQL for the specified interval.<br>
    <br>
    When I enable trace in the Open SQL monitor the execution time I see is very disappointing, about 22 - 46 seconds for each query. I also enable SQL trace in Oracle database and the results I get are the following:<br>
    <br>
    <pre>
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        0      0.00       0.00          0          0          0           0
    Execute      2      0.00       0.00          0          0          0           0
    Fetch        2     10.74      79.70      50473      62752          0           6
    total        4     10.74      79.70      50473      62752          0           6
    Misses in library cache during parse: 0
    Optimizer mode: ALL_ROWS
    Parsing user id: 32
    Elapsed times include waiting on following events:
       Event waited on                             Times   Max. Wait  Total Waited
       Waited  -
      db file sequential read                     50473        0.15         72.90
      SQL*Net message to client                       2        0.00          0.00
      SQL*Net more data to client                     1        0.00          0.00
      SQL*Net message from client                     2        0.00          0.00
    </pre>
    <br>
    The 'db file sequential read' is what worries me but I don't know what to do.<br>
    <br>
    Also I tried the same query using Db Visualizer and the jdbc jar file. The response was much better and the execution plan was different as you can see in sql trace results:<br>
    <br>
    <pre>
    call     count       cpu    elapsed       disk      query    current        rows
    Parse        1      0.01       0.01          0          0          0           0
    Execute      1      0.00       0.00          0          0          0           0
    Fetch        1      0.00       0.00          0          7          0           0
    total        3      0.01       0.01          0          7          0           0
    Misses in library cache during parse: 1
    Optimizer mode: ALL_ROWS
    Parsing user id: 32
    Rows     Row Source Operation
          0  SORT ORDER BY (cr=7 pr=0 pw=0 time=636 us)
          0   INLIST ITERATOR  (cr=7 pr=0 pw=0 time=487 us)
          0    TABLE ACCESS BY INDEX ROWID BC_MSG (cr=7 pr=0 pw=0 time=459 us)
          0     INDEX RANGE SCAN I_BC_MSG_STATUS_SENT (cr=7 pr=0 pw=0 time=347 us)(object id 96079)
    Elapsed times include waiting on following events:
       Event waited on                             Times   Max. Wait  Total Waited
       Waited  -
      SQL*Net message to client                       2        0.00          0.00
      SQL*Net message from client                     2        0.18          0.19
    </pre>
    <br>
    The I_BC_MSG_STATUS_SENT index that scans is the index using the columns STATUS, SENT_RECV_TIME I created to see if performance is better.<br>
    <br>
    Generally the system works fine. I handles 50.000 messages per day with no delays. But the monitoring performance is annoying. I need your expertise on that.<br>

    You, also, have waaaay too many user startup/Login items.
    You need to pare these down to the apps you really need to have launched at startup and running in the background.
    Add or remove automatic items
    Choose Apple menu > System Preferences, then click Users & Groups.
    Select your user account, then click Login Items.
    Do one of the following:
    Click Add below the list on the right, select an app, document, folder, or disk, then click Add.If you don’t want an item’s windows to be visible after login, select Hide. (Hide does not apply to servers, which always appear in the Finder after login.)
    Select the name of the item you want to prevent from opening automatically, then click Delete below the list on the right.
    You need to make sure to update all of your third party software if there are OS X Mavericks updates that can be applied.
    You may need to go the third party developers' websites if there are no updates through the Mac App Store.
    Make sure all of your Web browser Internet plugins, extensions and add-ons are updated to recent versions, also.

  • Server 2012 R2 slow performance over all

    This is a DELL PowerEdge R820 / 256GB RAM / 4TB onboard storage configured as Remote Desktop Services Host /TS... running QuickBooks, MS Office 2010 STD, Symantec EndPoint Protection (basic antivirus installation ONLY)... 1 month old server... SUPER fast,
    super powerfull.... Part of an AD in SBS 2008 Premium... single NIC card 4 ports / 3 ports disabled. single IP... no VLANS... server is able to resolve ANY pc, DNS record with no problems... able to resolve DC by name, able to receive GP, able to update, able
    to do everything that I can think of.... EXCEPT... anything I open, word, excel, QuickBooks, IE.... takes forever to open... after the application is open is fast but to open anything takes 3-4 minutes.... open ticket with Symantec all looks good, created
    lots of exceptions for antivirus/real time scanning, open ticket with QuickBooks: files look good application was removed and reinstalled to be sure all was done correctly... check the binding order for the disabled NIC; the active one is TOP option, no errors
    at all in event viewers for system, application, setup, no errors at all in DELL management tool, no hard drive errors, no controllers errors.... this server is replacing an old dell poweredge 2008 STD with 24GB RAM... the old DELL opens the same applications
    way faster than the new one... same Quicken version; old server opens Quicken in seconds, new one 3-4 minutes..... Real time monitoring NEVER goes above 1% for CPU and 3% for memory utilization.... one more thing... removed antivirus 100% restart... same performance
    without antivirus.....
    Any ideas will be great as of how to troubleshoot the slow performance....
    Thank you!

    Hi,
    As Sam suggested, please check if there any issue occurred in hard drive.
    On current situation, please also refer to following steps and troubleshoot, then check if we can find more
    clues.
    Please check if you have installed all necessary updates for the Windows Server 2012 R2.
    Please
    perform a clean boot to check if there has software conflicts.
    Please use Resource Monitor to troubleshoot and check if we can find some more details.
    Using Resource Monitor to Troubleshoot Windows Performance Issues Part 1
               Using
    Resource Monitor to Troubleshoot Windows Performance Issues Part 2
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Slow performance on a iMac 27" (maybe originated by the HDD)

    Hello,
    Well, I've had my iMac for 10 months now, but have never really paid attention to its performance since it was my first Mac and I was upgrading from a quite old computer, so it obviously proved to be a far superior machine.
    However, I noticed the problem when I started to be more critical with my machine's performance (this triggered by the fact that I bought, some months after, a MacBook Air which flies beyond time and space). Curious about this, I requested a friend to do a benchmark test with Xbench resulting in his machine (another iMac 27” with comparable specs) clearly outperforming mine. Even the Air, with its slower processor and smaller RAM, has a relatively close performance.
    Additionally, I have started to notice how the computer takes a long time to start-up and, after the desktop is “layed out”, it takes a lot of time before the machine becomes “responsive” (I usually try to start Mail and Google Chrome as soon as the pointer pops in!) with the final result that I have to wait in company of the beach ball for quite some seconds (half a minute) and even after the application had started, I can still hear the HDD working it as if there would be no tomorrow! And then, it is slooooow. Funnily enough, “tougher” applications like Photoshop or Illustrator don’t seem to have as many problems, relatively speaking.
    A little bit on the background info: I have two partitions: one for Bootcamp (since I was migrating from Windows, I had some software that I wanted to use there: Matlab and Office, basically, and then some smaller Windows-only programs).
    Derived from the benchmark test, I think I might have isolated the problem to the HDD (not sure though!).
    SO THE QUESTIONS ARE:
    1. How can I verify that the slow performance is due to the HDD being defective/badly configured/etc.?
    2. Has the Windows Bootcamp Partition any effect on my machine’s performance under MacOS? (I would assume not, but you never know!). I have more than 1.3 TB free space left
    3. What kind of corrective measures should I take?
    4. Any other type of advice will be warmly welcome: I will try to do some PRAM and SMC resets but I am not counting on it. I had also ran the disk utilities and there were no permission errors (not so sure what this means, but I’ve read that it is supposed to be good news.)
    5. Any extra info you might need, lemme know!
    Greetz,
    Víctor.
    PS: Sorry for the loooong post. I tried to be thorough!

    1. How can I verify that the slow performance is due to the HDD being defective/badly configured/etc.?
    Run Apple Hardware Test: http://support.apple.com/kb/HT1509
    2. Has the Windows Bootcamp Partition any effect on my machine’s performance under MacOS? (I would assume not, but you never know!). I have more than 1.3 TB free space left
    Probably not but 1.3TB of free space left on the total HD is not enough for OS X, OS X needs a minimum of 10-15% free space! If you mean 1.3TB of Windows space I'd recommend posting that question in the Boot Camp forum.
    3. What kind of corrective measures should I take?
    If the drive is failing per the AHT then it's covered by warranty and will need to be replaced. Remember back up!!!!!!!!!!
    4. Any other type of advice will be warmly welcome: I will try to do some PRAM and SMC resets but I am not counting on it. I had also ran the disk utilities and there were no permission errors (not so sure what this means, but I’ve read that it is supposed to be good news.)
    Can't hurt, make sure you read the instructions carefully and execute the tests exactly as they are described for Intel based iMacs.
    5. Any extra info you might need, lemme know!
    If you no longer have a need for Windows on your iMac I'd recommend removing that partition using Boot Camp Assistant. That may correct your problems.
    I would also recommend checking if System Preferences - Startup Disk and see if your internal HD is highlighted as the Startup Disk.
    In addition I would recommend checking your Login Items (System Preferences - Accounts - Login Items) and delete any applications you don't need launching at Login.

  • Slow performance LR 1.3.1 (Library Module)

    LR 1.2 is running OK on my iMac. A while ago I tried LR 1.3. The upgrade really slowed down performance. Mostly a lag in the sliders and navigation tools in both Library and Develop modules that made it unworkable to me. I changed back to LR 1.2.
    Since I want to import Canon G9 RAW files into LR, I upgraded to LR 1.3.1 recently. Performance of sliders and the navigation tool in the Develop module seems the same as in LR 1.2 (or maybe even a little better). Which means it is OK (workable). It still shows the blur when navigating a 100% zoomed image though. But the navigation tool in the Library module still has the same slow performance as it had in LR 1.3. Unworkable!!! I tried everything: optimizing, new catalog, rendering previews, etc.
    I need the Library module to work smoothly (as in LR 1.2) in order to compare images at 100% zoom. I am afraid I have to go back to LR 1.2 again and find another solution for my Canon G9 RAW files. Most inconvenient. I am very disappointed. Especially, since Adobe showed they CAN get it right with the Develop module in version LR 1.3.1...
    Oh yeah, my system specs:
    iMac 2.16 GHz Intel Core 2 Duo
    3GB 667 Mhz DDR2 SDRAM (2GB + 1GB)
    232,89 GB Harddrive, 113 GB available
    ATI Radeon X1600 128MB
    Mac OS 10.4.11
    Please Adobe, make the Library module run as smoothly as the Develop module in version 1.3.2...

    The preview folder is 2,11 GB big. The .lrcat is 47 MB big.
    I opened a new test catalog. I imported 326 images. After the import I rendered 1:1 previews. It took a long time. Real memory used was between 700-1000MB. Virtual memory used was between 1000-1400MB. When it was done rendering it still keep on using 700MB real memory and 1000MB virtual memory. I had to close LR and restart. Real memory after restart was 75MB real memory and 375 virtual memory.
    But it didn't matter. The lag in the navigation tool of the Library module was still there.
    I noticed that when clicking in the navigation window there was less delay as when I slide the white square in the window (in Library module). In the develop module this seems the other way around. Sliding showed less delay than clicking.
    What's going on here?
    I also have a MacBook. Performance seems much faster than on my iMac overall. After creating a new catalog and rendering 1:1 previews, the lag in the navigation window seems less than before. But it was still there...

  • Slow Performance Forms 10g !!!!

    Hi,
    I have migrated several forms from 6i to 10g and i use a 11g Database.
    Most of the users accessing from different countries complain of slow performance but the basic idea of migration is to get a better performance. My users mostly work on laptops.
    I am unable to find where the problem is. Is this might be due to network traffic since they are accessing via internet or any server related issues. Please help me to find and fix the problem and is there any tips for gaining better performance in using forms 10g.
    Regards,
    Suresh

    So, were they running on 6i via laptop and accessing via the internet before you migrated ? (ie: was it 6i client server or 6i web forms)
    Did you migrate the database too ?
    Slow performance as in : it used to be seconds and now it's taking minutes ?
    Steve

  • Slow performance with 2 new full T1 installed .

    We've just added second Full T1 line to
    this router to dedicate full T1 bandwidth our two database servers.We are still experiencing the slow performance to our remote location such as file copying and acceessing applications.below are configs and sh run.Any help and inputs are greatly appreciated.Is the router configuration correct? or need to be modified.Thanks
    Danny.
    router2621xm#sh run
    Building configuration...
    Current configuration : 1924 bytes
    version 12.3
    service timestamps debug datetime msec
    service timestamps log datetime msec
    service password-encryption
    service udp-small-servers
    service tcp-small-servers
    hostname OPS
    boot-start-marker
    boot-end-marker
    enable secret xxxx
    enable password xxxx
    no network-clock-participate slot 1
    no network-clock-participate wic 0
    no aaa new-model
    ip subnet-zero
    ip cef
    no ftp-server write-enable
    class-map match-any VOIP
    match ip dscp ef
    policy-map VOIP-QOS
    class VOIP
    priority 1158
    class class-default
    fair-queue
    random-detect dscp-based
    interface FastEthernet0/0
    ip address 192.168.157.1 255.255.255.0 secondary
    ip address 192.168.7.1 255.255.255.0
    ip policy route-map policyroute speed auto
    full-duplex
    no mop enabled
    interface Serial0/0
    ip unnumbered FastEthernet0/0
    service-policy output VOIP-QOS
    no ip mroute-cache
    interface Serial0/1
    ip unnumbered FastEthernet0/0
    service-policy output VOIP-QOS
    no ip mroute-cache
    router eigrp 15
    network 192.168.1.0
    network 192.168.2.0
    network 192.168.3.0
    network 192.168.4.0
    network 192.168.5.0
    network 192.168.6.0
    network 192.168.7.0
    network 192.168.8.0
    network 192.168.151.0
    network 192.168.152.0
    network 192.168.153.0
    network 192.168.154.0
    network 192.168.155.0
    network 192.168.156.0
    network 192.168.157.0
    network 192.168.158.0
    network 192.168.201.0
    no auto-summary
    ip classless
    ip route 0.0.0.0 0.0.0.0 192.168.1.5
    no ip http server
    access-list 150 permit ip host 192.168.7.5 any
    access-list 150 permit ip host 192.168.7.6 any
    access-list 151 permit ip any any
    dialer-list 1 protocol ip permit
    route-map policyroute permit 10
    match ip address 150
    set interface Serial0/1
    route-map policyroute permit 20
    match ip address 151
    set interface Serial0/0
    line con 0
    line aux 0
    line vty 0 4
    password xxxx
    login
    end

    A couple of items worth noting are the QOS policies themselves.
    This is OK
    class-map match-any VOIP
    match ip dscp ef
    Add this
    class-map match-any VOIP-signalling
    match dscp af31
    match dscp cs3
    Change the policy-map to reflect the changes
    policy-map VOIP-QOS
    class VOIP-signalling
    bandwidth 16
    class VOIP
    priority 24
    class class-default
    fair-queue 256
    random-detect dscp-based
    The bandwidth is meant for 4 concurrent phone conversations so adjust up as needed. The priority is based on my own testing so take it as you may.
    The most important statement is "fair-queue 256", by default you only get 16 queues. Allowing for 256 queues only uses a modest amount of memory so its a simple low impact choice for the router and allows more conversations between devices without interruption.
    Upping the number of queues in your policy would be the best and most important item for your performance problem, next of couse to coercing EIGRP to load balance the T1s properly.
    Brian
    P.S. Create a loopback interface for the ip unnumbered use, cause if the Fa0/0 goes down everything goes down and you can't telnet in from anywhere to look at it. Eliminate the following items from the config by using "no" in fromt of them, a bit of research will tell you why, and start you toward eliminating a few other items.
    service udp-small-servers
    service tcp-small-servers

  • Slow Performance on QueueReciever.recieve() + MQ

    Hi,
    I have been wrecking my brains around this pickle for the last week or so and would appreciate any assistance I could get here.
    Problem Description: Incredibly slow performance when invoking a QueueReciever.recieve() connecting to MQ server version 6
    Benchmarks: 100-900ms per invocation
    Configuration:
    JVM: WS 6's own
    MQ: 6.0
    Application Server: WAS 6
    Managed resources: Queue Connection Factory (queues are dynamically created)
    Runtime artifacts: QueueConnectionFactory, QueueConnection, QueueConnection, QueueSession, QueueSender,
    QueueReciever, TextMessage, in Queue out Queue
    Scenario:
    QueueSender created
    QueueReciever created using a MessageSelector filtering on JMSCorrelationID
    Message is sent to the in queue using QueueSender, embedded with a JMSCorrelationIDImmediately after, a QueueReciever.receive() is invoked listening on the out queue
    Result: VERY slow return from the synchronous block on the receive().
    Given: reply message is put on the out-queue after about 40ms by 3rd party application.
    Again any assistance would be appreciated.
    Message was edited by:
    sg9aeee

    Hi Wietse
    Your RFC communication may be slow because limitations on the Gateway connection parameters.
    Please check the Gateway profile parameters, like max_conn, blocksize etc
    Thanks
    Yatin Bhatt

  • Slow Performance when program was once 100% proficient

    I am working on a 2011 Macbook Pro - OS X version 10.9.5
    For over a year I have been working in Adobe Premiere Elements 11 on this computer with no issues.  Recently the program began running EXTREMELY slow - for example., taking well over an hour to render video that previously would render in only a minute or two.  Went to Apple - thinking it was my MAC - diagnostics on the MAC show the computer itself is fine.
    Purchased Premiere Elements 13 (liked the new features and offerings) and was naively hoping it would fix my slow performance issue. 
    But program is still running horribly slow.
    Any suggestions or similar issues?

    laurabodey
    Premiere Elements 11 or 13 on Mac Computer.
    Which program do you want to troubleshoot first?
    Let us assume Premiere Elements 11....
    1. Edit Menu/Preferences/Scratch Disk
    Where are the Scratch Disk pointing and how much free space is at that location
    Please assure a clean up of any pile ups of any preview files (Adobe Premiere Elements Previews File Folder), conformed audio files (Media Cache Files Folder), and conformed audio (best cleaned out through Edit Menu/Preferences/Media and the Media Cache Database area Clean button.
    2. Download, install, and run the free ccleaner.
    https://www.piriform.com/ccleaner/download?mac
    3. How much installed RAM does you computer have? Are your source media stored on external hard drive (with the appropriate formatting for Mac)?
    4. Does the information in online articles such as the following make any impact on your situation?
    Seven ways to free up drive space | Macworld
    Let us start here and then decide what next.
    I am strictly and Elements Windows user who tries to find common ground between Premiere Elements Windows and Mac to address some of these issue. So, I am
    not all that great on Mac locations. Please help me translate from Windows to Mac if necessary.
    We will be watching for your results.
    ATR

  • Slow performance on characteristic dimension filter

    Hi folks, I'm hoping you can help me troubleshoot something.  We have a report in a cube that's been in production and stable for a while (a year or more).  We're getting some complaints about slow performance, and I'm noticing that it takes 15 to 20 minutes for the selection screen to refresh with possible values for one of the characteristics of the Material dimension.  The characteristic only has 3 possible values for my selection.  I would expect it to take more like 1 or 2 minutes.  What should I look at to find the cause?  We're running BEx with version 3.0B of Business Warehouse.

    Carolyn,
    In the properties for the characteristic - set it to read data from the dimension table - this can be done from the BeX tab for the infoobject or from WAD if you are using a web template or from the properties in the characteristic in BeX..
    Arun
    Message was edited by:
            Arun Varadarajan

  • Slow performance prevents correction

    I'm using OBI 11g. Is there any way to go directly to the criteria tab or view editor or turn off display of the Compound View?
    Slow performance in displays is keeping me from looking at my code to correct performance.
    Also, the view editor seems to be unstable, and I cannot even tell if the current problem is with the last code I saved or some previous or "corrupted" version.

    You, also, have waaaay too many user startup/Login items.
    You need to pare these down to the apps you really need to have launched at startup and running in the background.
    Add or remove automatic items
    Choose Apple menu > System Preferences, then click Users & Groups.
    Select your user account, then click Login Items.
    Do one of the following:
    Click Add below the list on the right, select an app, document, folder, or disk, then click Add.If you don’t want an item’s windows to be visible after login, select Hide. (Hide does not apply to servers, which always appear in the Finder after login.)
    Select the name of the item you want to prevent from opening automatically, then click Delete below the list on the right.
    You need to make sure to update all of your third party software if there are OS X Mavericks updates that can be applied.
    You may need to go the third party developers' websites if there are no updates through the Mac App Store.
    Make sure all of your Web browser Internet plugins, extensions and add-ons are updated to recent versions, also.

Maybe you are looking for