Use of NFS or iSCSI datastores

A few queries..
1. Is it possible to make use of NFS or iSCSI storage as permanent datastores for a EVO:RAIL appliance?
2. What are the choices for VSAN data protection when creating VMs inside EVO:RAIL?

>>1. Is it possible to make use of NFS or iSCSI storage as permanent datastores for a EVO:RAIL appliance?
Yes, but they have to be manually configured on each one of the nodes (just like you would have to do on a regular vSphere deployment).
>>2. What are the choices for VSAN data protection when creating VMs inside EVO:RAIL
Any vSphere solution products (such as VDP) which are supported with vSphere 5.5 and VSAN 1.0 are supported with EVO:RAIL. Same idea applies to 3rd party solution as well as long as they are deemed supported with vSphere 5.5 and VSAN 1.0.

Similar Messages

  • NFS and ISCSI using ip hash load balance policy

    As i know all these days that the best practice for iscsi is to use single nic and one standby with " route based port id" ButI have seen in a client placethat NFS and iscsi are configured to use"route based ip hash" and multiple nic and it has been working all these days. i can not see that iscsi does multi path there.I was told by the sys admin that it is ok to use that since the both protocol are configured in same storage and it does not make sense to separate it ,his explanation that if we want separate policy then use separate storage that is one for nfs and other for iscsi, i do not buy that, i might be wrong.He pointed his link below saying that you can use ip hash.http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalI....Is it ok to use " route based ip hash for iscsi as on the link?
    This topic first appeared in the Spiceworks Community

    When you create your uplink port profile you simply use the auto channel command in your config:
    channel-group auto mode on
    This will create a static etherchannel when two or more ports are added to the uplink port profile from the same host.  Assuming your upstream switch config is still set to "mode on" for the etherchannel config, there's nothing to change.
    Regards,
    Robert

  • NFS vs ISCSI for Storage Repositories

    Anyone have any good guidance in using NFS vs ISCSI for larger production deployments of OVM 3?
    My testing has been pretty positive with NFS but other than the documented "its not as fast as block storage" and the fact that there is no instant clones (no OCFS2), has anyone else contemplated between the two for OVM? If so, what did you choose and why?
    Currently we are testing using NFS thats presented from a Solaris HA Cluster servicing a ZFS pool (basically mimicking ZFS 73xx and 74xx appliances) but I don't know how the same setup would perform if the ZFS pool grew to 10TB of running virtual disk images.
    Any feedback?
    Thanks
    Dave

    Dave wrote:
    Would you personally recommend against using one giant NFS mount to storage VM disk images?I don't recommend against it, it's just most often the slowest possible storage solution in comparison to other mechanisms. NFS cannot take advantage of any of the OCFS2 reflinking, so guests must be fully copied from the template, which is time consuming. Loop-mounting a disk image on NFS is less efficient than loop-mounting it via iSCSI or directly in the guest. FC-SAN is the usually the most efficient storage, but bonded-10Gbps interfaces for NFS or iSCSI may now be faster. If you have dual-8Gpbs FC HBAs vs dual 1Gbps NICs for NFS/iSCSI, the FC SAN will win.
    Essentially, you have to evaluate what your critical success factors are and then make storage decisions based on that. As you have a majority of Windows guests, you need to present the block devices via Oracle VM, so you need to use either virtual disk images (which are the slowest, but easiest to manage) or FC/iSCSI LUNs presented to the guest (which are much faster, but more difficult to manage).

  • Unable to use device as an iSCSI target

    My intended purpose is to have iSCSI targets for a virtualbox setup at home where block devices are for the systems and existing data on a large RAID partition is exported as well. I'm able to successfully export the block files by using dd and added them as a backing-store into the targets.conf file:
    include /etc/tgt/temp/*.conf
    default-driver iscsi
    <target iqn.2012-09.net.domain:vm.fsrv>
    backing-store /srv/vm/disks/iscsi-disk-fsrv
    </target>
    <target iqn.2012-09.net.domain:vm.wsrv>
    backing-store /srv/vm/disks/iscsi-disk-wsrv
    </target>
    <target iqn.2012-09.net.domain:lan.storage>
    backing-store /dev/md0
    </target>
    but the last one with /dev/md0 only creates the controller and not the disk.
    The RAID device is mounted, I don't whether or not that matters, unfortunately I can't try it being unmounted yet because it is in use. I've tried all permutations of backing-store and direct-store with md0 as well as another device (sda) with and without the partition number, all had the same result.
    If anyone has been successful exporting a device (specifically a multi disk) I'd be real interested in knowing how. Also, if anyone knows how, or if it's even possible, to use a directory as the backing/direct store I'd like to know that as well, my attempts there have been unsuccessful as well.
    I will preempt anyone asking why I'm not using some other technology, eg. NFS, CIFS, ZFS, etc., by saying that this is largely academic. I want to compare the performance that a virtualized file server has that receives it's content being served by both NFS and iSCSI, and the NFS part is easy.
    Thanks.

    Mass storage only looks at the memory expansion.
    Did you have a micro SD card in it?
    What OS on the PC are you running?
    Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
    Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
    Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
    BESAdmin's, please make a signature with your BES environment info.
    SIM Free BlackBerry Unlocking FAQ
    Follow me on Twitter @knottyrope
    Want to thank me? Buy my KnottyRope App here
    BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

  • Hello. I have a problem with OEL 6.5 and ocfs2. When I mount ocfs2 with mount -a command all ocfs2 partitions mount and work, but when I reboot no ocfs2 partitions auto mount. No error messages in log. I use DAS FC and iSCSI FC.

    Hello.
    I have a problem with OEL 6.5 and ocfs2.
    When I mount ocfs2 with mount -a command all ocfs2 partitions mount and work, but when I reboot no ocfs2 partitions auto mount. No error messages in log. I use DAS FC and iSCSI FC.
    fstab:
    UUID=32130a0b-2e15-4067-9e65-62b7b3e53c72 /some/4 ocfs2 _netdev,defaults 0 0
    #UUID=af522894-c51e-45d6-bce8-c0206322d7ab /some/9 ocfs2 _netdev,defaults 0 0
    UUID=1126b3d2-09aa-4be0-8826-0b2a590ab995 /some/3 ocfs2 _netdev,defaults 0 0
    #UUID=9ea9113d-edcf-47ca-9c64-c0d4e18149c1 /some/8 ocfs2 _netdev,defaults 0 0
    UUID=a368f830-0808-4832-b294-d2d1bf909813 /some/5 ocfs2 _netdev,defaults 0 0
    UUID=ee816860-5a95-493c-8559-9d528e557a6d /some/6 ocfs2 _netdev,defaults 0 0
    UUID=3f87634f-7dbf-46ba-a84c-e8606b40acfe /some/7 ocfs2 _netdev,defaults 0 0
    UUID=5def16d7-1f58-4691-9d46-f3fa72b74890 /some/1 ocfs2 _netdev,defaults 0 0
    UUID=0e682b5a-8d75-40d1-8983-fa39dd5a0e54 /some/2 ocfs2 _netdev,defaults 0 0

    What is the output of:
    # chkconfig --list o2cb
    # chkconfig --list ocfs2
    # cat /etc/ocfs2/cluster.conf

  • Could not create/access the TopLink Session. This session is used to connect to the datastore.

    We are getting the below error in our production server & also other servers(UAT, Staging). Only option is to restart the OSB server.
    Test connection is working fine and able to connect the database without any issue. We have enabled connection leak profiling and also, provided the inactive time outs , still does not work. Need your suggestion for the below error.
    ***endpoint***:https://extzwsdev.zurichna.com/services/RiskAnalysis-v1***
    Payload<soapenv:Envelope    xmlns:soapenv = "http://schemas.xmlsoap.org/soap/envelope/"    xmlns:ris = "http://webservices.zurich.com/zsoa/nac/underwritingmanagement/riskanalysis-v1_0"    xmlns:zsoa = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/zsoa"    xmlns:com = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/common"    xmlns:con = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/contractandspecification"    xmlns:fin = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/financialservicesagreement"    xmlns:par = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/party"    xmlns:act = "http://schemas.zurich.com/zsoa/nac/underwritingmanagement/2009/11/activityconditionplace">    <soapenv:Header/>    <soapenv:Body>        <ris:calculateTargetPolicyRateChangeByProductGroup>            <ris:insurancePolicySearchCriteria>                <con:externalReference>1151638</con:externalReference>            </ris:insurancePolicySearchCriteria>        </ris:calculateTargetPolicyRateChangeByProductGroup>    </soapenv:Body></soapenv:Envelope>
    ***RTOneService Output Response*** <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            ... 1 more
    Caused by: BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
            at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
            at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            ... 38 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
            at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.&lt;init>(NameEnquoter.java:59)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            ... 1 more
    .</faultstring><detail><con:fault xmlns:con="http://www.bea.com/wli/sb/context"><con:errorCode>BEA-380001</con:errorCode><con:reason>[invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:152)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
            ... 1 more
    Caused by: BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.db.exceptions.DBResourceException.createRetriableException(DBResourceException.java:676)
            at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:645)
            at oracle.tip.adapter.db.exceptions.DBResourceException.couldNotCreateTopLinkSessionException(DBResourceException.java:314)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:918)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            ... 38 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(Unknown Source)
            at net.sourceforge.jtds.jdbc.ConnectionJDBC2.getMetaData(Unknown Source)
            at weblogic.jdbc.wrapper.Connection.getMetaData(Connection.java:479)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:122)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.init(NameEnquoter.java:92)
            at oracle.tip.adapter.db.toplinkext.NameEnquoter.&lt;init>(NameEnquoter.java:59)
            at oracle.tip.adapter.db.DBManagedConnectionFactory.acquireSession(DBManagedConnectionFactory.java:705)
            at oracle.tip.adapter.db.transaction.DBTransaction.getSession(DBTransaction.java:375)
            at oracle.tip.adapter.db.DBConnection.getSession(DBConnection.java:256)
            at oracle.tip.adapter.db.DBInteraction.executeOutboundRead(DBInteraction.java:311)
            at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:233)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:535)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            ... 1 more
    .</con:reason><con:location><con:node>RouteNode1</con:node><con:path>response-pipeline</con:path></con:location></con:fault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>
    !!! Exception occurred <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>BEA-380001: [invokeExecutionFault] Error Dispatching the Event: unexpected error. - [BEA-380002] Invoke JCA outbound service failed with connection error, exception: com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
    com.bea.wli.sb.transports.jca.JCATransportException: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:153)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:586)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:154)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:446)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:584)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:67)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:74)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:92)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:67)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:45)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:34)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkManagerServiceImpl.java:153)
            at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
            at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused by: oracle.tip.adapter.sa.api.JCABindingException: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:261)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            ... 32 more
    Caused by: oracle.tip.adapter.sa.impl.fw.ext.org.collaxa.thirdparty.apache.wsif.WSIFException: servicebus:/WSDL/UWIS/RiskAnalysis-v1.0/DBAdapters/getCMRateTrackerData [ getCMRateTrackerData_ptt::getCMRateTrackerDataSelect(getCMRateTrackerDataSelect_inputParameters,TblCmRctrackerMatch2009Collection) ] - WSIF JCA Execute of operation 'getCMRateTrackerDataSelect' failed due to: Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    ; nested exception is:
            BINDING.JCA-11622
    Could not create/access the TopLink Session.
    This session is used to connect to the datastore.
    Caused by java.sql.SQLException: Invalid state, the Connection object is closed..
    You may need to configure the connection settings in the deployment descriptor (i.e. DbAdapter.rar#META-INF/weblogic-ra.xml) and restart the server.  This exception is considered retriable, likely due to a communication failure.  To classify it as non-retriable instead add property nonRetriableErrorCodes with value "0" to your deployment descriptor (i.e. weblogic-ra.xml).  To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff.  All properties are integers.
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.performOperation(WSIFOperation_JCA.java:650)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeOperation(WSIFOperation_JCA.java:369)
            at oracle.tip.adapter.sa.impl.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:328)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.invokeWsifProvider(JCABindingReferenceImpl.java:352)
            at oracle.tip.adapter.sa.impl.JCABindingReferenceImpl.request(JCABindingReferenceImpl.java:259)
            at com.bea.wli.sb.transports.jca.binding.JCATransportOutboundOperationBindingServiceImpl.invoke(JCATransportOutboundOperationBindingServiceImpl.java:150)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.sendRequestResponse(JCATransportEndpoint.java:209)
            at com.bea.wli.sb.transports.jca.JCATransportEndpoint.send(JCATransportEndpoint.java:170)
            at com.bea.wli.sb.transports.jca.JCATransportProvider.sendMessageAsync(JCATransportProvider.java:585)
            at sun.reflect.GeneratedMethodAccessor652.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.bea.wli.sb.transports.Util$1.invoke(Util.java:83)
            at com.sun.proxy.$Proxy139.sendMessageAsync(Unknown Source)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageAsync(LoadBalanceFailoverListener.java:148)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToServiceAsync(LoadBalanceFailoverListener.java:510)
            at com.bea.wli.sb.transports.LoadBalanceFailoverListener.sendMessageToService(LoadBalanceFailoverListener.java:445)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageToService(TransportManagerImpl.java:582)
            at com.bea.wli.sb.transports.TransportManagerImpl.sendMessageAsync(TransportManagerImpl.java:449)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransportDispatcherDelegate.send(TransportDispatcherDelegate.java:66)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.TransactionalDispatcherDelegate.send(TransactionalDispatcherDelegate.java:51)
            at com.bea.alsb.flow.messaging.dispatcher.servicebus.ResultCacheDispatcherDelegate.send(ResultCacheDispatcherDelegate.java:50)
            at com.bea.alsb.flow.messaging.dispatcher.ServiceBusDispatcherHandler.send(ServiceBusDispatcherHandler.java:93)
            at com.bea.bpel.services.messaging.OutboundDispatcherServiceImpl.send(OutboundDispatcherServiceImpl.java:73)
            at com.bea.bpel.internal.dispatcher.OutboundDispatcherImpl.dispatch(OutboundDispatcherImpl.java:91)
            at com.bea.bpel.interpreter.internal.instruction.messaging.InvokeRequest.enter(InvokeRequest.java:90)
            at com.bea.bpel.interpreter.internal.process.ProcessNodeImpl.enter(ProcessNodeImpl.java:181)
            at com.bea.bpel.interpreter.internal.Interpreter.interpret(Interpreter.java:155)
            at com.bea.bpel.interpreter.internal.Interpreter.invoke(Interpreter.java:87)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:66)
            at com.bea.bpel.internal.dispatcher.EngineManagerImpl.dispatch(EngineManagerImpl.java:44)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEventJobScheduled(SchedulerServiceContextImpl.java:87)
            at com.bea.bpel.internal.dispatcher.SchedulerServiceContextImpl.fireEvent(SchedulerServiceContextImpl.java:68)
            at com.bea.alsb.flow.scheduler.SchedulerServiceImpl$1.run(SchedulerServiceImpl.java:33)
            at weblogic.work.ContextWrap.run(ContextWrap.java:41)
            at com.bea.alsb.platform.weblogic.WlsWorkManagerServiceImpl$WorkAdapter.run(WlsWorkMa

    Its hard to say what is going on.  Though the message says the error is in obtaining a TopLink session, the exception stack has nothing to do with TopLink, and the error seems to be coming from oracle.tip.adapter.db.toplinkext.NameEnquoter.init() directly calling weblogic.jdbc.wrapper.Connection.getMetaData() on what must be a stale or closed connection.  This looks like a DB adapter application, so you might want to post this question there as they might be able to help configure your datasource appropriately for the application.
    Best Regards,
    Chris

  • Extremely bad read/write latency on iSCSI datastore

    Hello,
    I have a single host in my test lab which is having very bad read/write latency to an iSCSI datastore.  All of my hosts have 1G ethernet, other hosts in the lab are not having this issue.  What can I check to help isolate this issue?  Are there any steps I can take to optimize the performance?

    I'm struggling with exactly the same problem, but on ESXi 4.1.
    It seems that zfs inflate IO. When you check disk activity you can see that underline zfs trash the disks, while it results in a modest activity within ntfs.
    I just cannot figure out how to cope with it.

  • Fault Tolerance of NFS and iSCSI

    Hello,
    I'm currently designing a new datacenter core environment. In this case there are also nexus 5548 with FEXs involved. On this fex's there are some servers which speak NFS and iSCSI.
    While changing the core component there will be a disruption between the servers.
    What ks the maximim timeout a NFS or iSCSI protocoll can handle while changing the components. Maybe there will be disruption for a maximimum of 1 sekond.
    Regards
    Udo
    Sent from Cisco Technical Support iPad App

    JDW1:  In case you haven't received the ISO document yet, the relevent section of the cited ISO 11898-2:2003 you want to look at is section 7.6 "Bus failure management", and specifically Table 12 - "Bus failure detection" and Figure 19 - "Possible failures of bus lines".

  • Is there an alternative to use of NFS in SAP Installations

    Hello All,
    My customer is very concerned about the use of NFS in his landscape. I am planning a build of a new application server on a seperate UNIX box as the existing box has maxed out (capacity wise).
    The new dialog application server would need to share interface directories , sapmnt etc , however the IT Security policy at our customer end prohibits NFS mounts
    Now that application server could run with its own set of profiles and kernel directories , however sharing the interface directory should be mandatory.
    I am wondering if there is any alternative to this ?
    Regards,
    Siddhesh

    Hello Markus,
    >You could use NFSv4 which has lots of new security features compared to old NFSv3 (or even v2). What is his concern? I´m sure he also use Windows shares in his company for the frontends..
    I had suggested the same, however we are on AIX 5.2 and NFSv4 i think needs AIX 5.3, so to have NFSv4 we would need to go for AIX 5.3 which is essentially an upgrade of the OS.
    Windows front ends cannot be shared as per company policy..
    >You need a single transport directory shared across the landscape.
    Not neccessary, we can still have transports working, SAP would use RFCs to copy over data.
    Currently we do not have any transport directories shared.
    >Depending on what OS you use you can use SMB/CIFS to share/mount the directories, however, I would still use NFS.
    Yes i agree totally NFS is clean and simple!
    Anyways the project is stalled for the moment and I have forced them to have a waiver for the policy as an exception
    Regards,
    Siddhesh

  • NFS vs iSCSI IOPS differ - why?

    Hello -
    I recently setup an environment utilizing 8 IO Analyzers each accessing either an iSCSI LUN or NFS Share (but not both at the same time). The secondary virtual disk was set at 30GB.
    For the iSCSI tests, we ran a 50/50 0% random workload and our total IOPS reached 4086.11.
    When we created the second disk on an NFS datastore and ran the same test as above, our total IOPS only reached 583.57 for the same time period (2 hours).  Additionally, latency doubled.
    I checked IOMeter on the guests, and it appeared they were pushing fewer IOPS as well.
    Any ideas as to why we couldn't push as many IOPS using NFS? I would think the amount of IOPS would be the same across tests, regardless of the backend?
    Thanks in advance.

    For those wondering about ZFS and implications on performance, you may want to visit this thread that helped me understand: https://pthree.org/2013/04/19/zfs-administration-appendix-a-visualizing-the-zfs-intent-log/

  • Use NAS (NFS) share as storage? Can't make shares.

    Hi,
    Trying to make shares on a network storage, nas, connected via nfs but i noticed that its greyed out. Is it supposed to only use disks or iSCSI för shares?

    This is frustrating!.. I've managed to get that working but i have a different issue now ..here is what i have done in details:
    Server: MAC OSX 10.6.8.
    Server was standalone and then I bounded to the AD then promoted to Open Directory Master without kerberos realm - as it is the AD is the one that holds the accounts.. that's how it should be correct ?
    Disk utility: I mounted the NFS share and in WGM i enabled file sharing on the NFS share via AFP, and now it shows under WGM - Home tab as: afp://xserve.mydomain.com/homes
    - for the clients, I bounded them to OD first for MCX and then to AD.
    Directory Utility: settings for both "client & server"
    *Create mobile account at login - false
    *Force local home directory on startup disk - false
    *Une UNC path - True with AFP protocol.
    Server Admin:
    * AFP is enabled on the NFS share "homes" and its auto-mounted.
    * Open Directory Master:
    - LDAP Server is running
    - Password Server is running.
    - Kerberos is stopped.
    Workgroup Manager:
    * I selected the test user "adtest" and assigned the home folder which is:
    Home URL: afp://xserve.domain.com/homes/adtest
    Full Path: /Network/Servers/xserve.domain.com/homes/adtest
    and when i click on Create Home Now, it did create the user home directory under the NFS share which is auto-mounted
    Active Directory Server:
    under the adtest user - profile tab, i see: \\xserve.domain.com\homes\adtest
    Problem:
    - when i try to login with adtest user from the client, i get the error message:
    "You are unable to login in o the user account "adtest" at this time - logging in to the account failed because an error occurred."
    Troubleshooting:
    1- logged in with local admin account and typed id adtest in terminal.. it shows all user attributes and groups, which means the machine is bound correctly to both AD & OD
    2- when I change the home for the user to the the default "/Users".. i can login just fine with the adtest account.. does that look like its a permissions issue ?
    Thanks again for your help.

  • Mirroring Windows Server to a Solaris Server using filesync & NFS

    I am trying to mirror the data from a Windows 2000 server to a Solaris 10 server using filesync over NFS. I have been able to do this from one solaris/sparc machine to another without problems, but this heterogeneous sync is failing. The Windoze machine is running Hummingbird NFS Maestro Server. I've tried both an old version of Maestro (5.x) and the newest version. On the solaris machine, I craft the .packingrules file by hand and issue "filesync -o src" to copy from the nfs mounted source to a local directory. The initial copy seems to go well, albeit with numerous complaints about ownership and permissions. On either the second or third running of "filesync -o src", it wants to delete all of the files that it just wrote. Argh! Sometimes it works, sometimes it does not.
    Perhaps I need to mirror in some other way. If all else fails, next I'll compile rsync on the solaris machine, trying it over NFS.
    I'd appreciate any suggestions of how best to mirror.
    By the way, my goal here is to show to Windoze PC users that this Solaris server can do everything that the Windows server can do, and more. With hopes, I'll be able to migrate completely off of the Windoze server.
    Thanks

    smbmount doesnt exist for solaris 10.
    The functionality would require a smbfs kernel module which is not available in solaris 10.
    I think there might be a commercial product that provides this functionality, but its name escapes me at the moment..

  • Dbcopy gives error (8201) if used through NFS

    Doing a migration from NW (7.0.3) to Linux (7.0.3).
    Mounted the NW volume through NFS.
    dbcopy (running on the linux box) finishes with hundreds of errors, and because of this lot of files are not copied to the new location.
    Some part of the log file of dbcopy:
    Error: Unable to open source file /mnt/nwgw01-mail/Grpwise/Po/GWDMS/LIB0001/DMSD0001.DB (8201) errno (13)
    Error: Unable to open source file /mnt/nwgw01-mail/Grpwise/Po/NGWCHECK.DB (8201) errno (13)
    Error: Return Code (8201) processing /mnt/nwgw01-mail/Grpwise/Po/NGWCHECK.DB
    Error: Unable to open source file /mnt/nwgw01-mail/Grpwise/Po/NGWGUARD.DB (8201) errno (13)
    Error: Return Code (8201) processing /mnt/nwgw01-mail/Grpwise/Po/NGWGUARD.DB
    If I mount the NW volume through NCP, and do the same process, there are now errors at all.
    As NFS much much faster than NCP (20min vs 2hours for a 10GB PO), I would like to use it (probablyin the future as the PO already copied).
    Is there some extra switch or something that I have to add for the NFS connection? I also tried to copy when the PO is down, but it makes no difference for the NFS copy.

    Tried CIFS. It is a bit faster than NCP, but not as fast as NFS.
    Thanks anyway for the tip.
    Originally Posted by jmarton
    On Wed, 29 Jul 2009 11:36:02 +0000, tcsabina wrote:
    > If I mount the NW volume through NCP, and do the same process, there are
    > now errors at all.
    >
    > As NFS much much faster than NCP (20min vs 2hours for a 10GB PO), I
    > would like to use it (probablyin the future as the PO already copied).
    It's quite possible you are experiencing file locking issues. Have you
    tried CIFS?
    Joe Marton
    Novell Knowledge Partner
    SUSE Linux Enterprise 11 is ready for action.

  • Cloning Databases - Anyone using Direct NFS & clonedb?

    Looking to see what experiences other customer have had using/trying Direct NFS (dNFS) and clonedb - a newer feature available in 11.2.0.2 (and above) - described in MOS Note 1210656.
    In particular we are looking at this for cloning a Production database for testing changes.
    Thanks!
    Marty

    Tim Hall had a presentation in Sydney InSync about it some times ago. You should be able to find his experience in his website.
    Here it is: http://www.oracle-base.com/articles/11g/Clonedb_11gR2.php
    Edited by: AliD on 20/10/2011 21:26

  • How to mount NFS into a zone or how to use the same IP in every zone?

    Hi,
    we are using a NFS server in a different subnet (= different network interface; nxge1) than our 'normal' network (= nxge0).
    Now I want to mount serveral NFS directories into our zones.
    First I thought the follwoing is possible:
    In the global zone I just mount the filesystem into its place:
    mount 10.11.3.1:/vol/vol_nfs_zones/zoneNNN_mnt /zones/zoneNNN/root/mnt
    When the zone is halted this mount works, but when I start the zone, I receive the error:
    # zoneadm -z zoneNNN boot
    zoneadm: zone 'zoneNNN': These file-systems are mounted on subdirectories of /zones/zoneNNN/root:
    zoneadm: zone 'zoneNNN': /zones/zoneNNN/root/mnt
    zoneadm: zone 'zoneNNN': call to zoneadmd failed
    When zoneNNN is already running and I try to mount it, I receive
    nfs mount: mount: /zones/zoneNNN/root/mnt: Device busy
    So the question is: How do I mount something in the gloabl zone from a NFS server into a zone?
    The only alternative I see is to make the interface nxge1 available in every zone and give each an own IP in our storage network... But sadly this isn't an alternative because we don't have so many free IPs in that net! (Or is there a trick to use the same IP in the global and non-global zones for only this interface??)
    Does anyone have a solution for our problem? I cannot believe that SUN misses this!
    Any hints are more than welcome!

    Mounting it by NFS in the global zone and trying to add this by the "add fs" and "type=lofs"-option yields to an error, when installing the zone:
    cannot verify fs /data: NFS mounted file-system.
    A local file-system must be used.
    zoneadm: zone zoneNNN failed to verifyOur storage network is not accessable from other nets. (And I think it is a very bad idea to route storage network traffic...)
    So I think we def. have to increase our storage network. :-(

Maybe you are looking for

  • Color warning in CS5

    Hi, I just installed LR5 and use CS5.  I was going to edit my first image from LR into CS5 and when I was going to save it, I got this message: Are you sure you want to convert colors to a destination document with a color profile that does not match

  • Unable to view PDF (baggage file) in CHM

    Hi, I have recently started using a new desktop pc running Windows 7. I am now unable to view PDF files (added as baggage files in RoboHelp) in the CHMs generated by RoboHelp. Even existing CHMs (generated before switching desktops) have this problem

  • Trouble with Connectivity and with internet dropping

    I seem to be having the same problem as everyone else. I just got this computer a few days ago and this problem is driving me crazy. My laptop is a Toshiba Satellite C75D-B7260 with 8.1 windows. Any idea what might be the fix? I cannot even update th

  • Table USR01 and USR02

    Hi Can someone advise what is the difference between table USR01 and USR02 and is it possible for the 2 tables to have different number of records. Thank you.

  • Why is apple releasing the ipad4 witha new and inproved wifi attena without addressing the wifi issue in the ipad3

    Why is apple releasing the ipad4 witha new and inproved wifi attena without addressing the wifi issue in the ipad3