Large data transfer hangs timecapsule

While transfering many small files my time caspule hangs after a short while. I can still use the device from my Mac, but from windows the device is no longer existstant. Even webtraffic doesn't work.
I'm using the latest timecapsule firmware 7.6.1 and the timecapsule is a model bought in 2011. I had hoped that the 7.6.1 firmware would solve the problem as 7.6 also had this issue.

Click here and fill out the form.
If desired, you can use the ditto command in the Terminal instead of the Finder to copy files.
(122436)

Similar Messages

INPUT: KT4/V vs CRC error in large data transfer/CD burning HERE!

This issue can be solved with BIOS update. KT4V & KT4 Ultra users who are having this problem can request for the TEST BIOS to test on your system. You may either pm/email me or Bas, or get it at http://ftp://ftp.heppen.be/MSI/
Please report back whether the test BIOS would really fix the problem, or cause any new problem, or any performance hit.
** this sounds like a Christmas Gift to KT4V users AND New Year Gift to KT4 Ultra users!!! :D **
To all KT4 Ultra and KT4V users, either you have data corruption or CRC error in large data transfer and CD burning or not, your inputs are needed.
Please list down your system specs as details as possible. Below here is a guideline, you may take this, CTRL-C (copy) and write your specs in your post.
1. System specs:
CPU:
Motherboard:
RAM Slot-1: (exact brand and model)
RAM Slot-2:
RAM Slot-3:
display card: [no overclock]
IDE-1M: (exact HDD brand and model pls)
IDE-1S:
IDE-2M:
IDE-2S:
IDE-3:
SER-1:
SER-2:
PCI-1:
PCI-2:
PCI-3:
PCI-4:
PCI-5:
PCI-6:
PSU: (brand, model, total power, (estimated) combined power)
BIOS revision:
Operating System:
VIA 4-in-1 drivers : (if you installed it, tell us the version)
other drivers, services or applications might affect the data transfer such as : PCI Latency patch, WPCREDIT modifications, VCool, CoolerXP...
2. CRC ERROR?
PASS or FAIL
If PASS, let us know your BIOS settings.
If FAIL, proceed as below:
3. Please use these BIOS settings:
1. Load BIOS Setup Default
2. NO OVERCLOCK ON FSB! Set accordingly to your CPU
2. Set RAM to
a) SPD, if failed try
b) User defined to the slowest RAM timings, ie 266,2.5,3,6,3,disable interleave,4,disable 1T, normal
If PASS, go for more extreme BIOS settings as you usually use:
1. High Performance Default
2. set RAM to the extreme timings
3. DO NOT overclock yet until both 1. and 2. are PASS
4. Try these suggestions:
1. Microsoft IDE drivers (uninstall VIA 4-in-1's)
2. VIA 4-in-1 different version's IDE filter driver?
3. VIA IDE Miniport driver?
4. use IDE-3 RAID channel for one HDD data transfer
5. same HDD transfer, ie C:\dir1\*.* -> C:\dir2\*.*
6. burn CD at 1x speed
7. Set the HDD and/or CD to PIO mode, or slower UDMA mode.
8. If and only if you know how to update BIOS correctly and willing to take some risks, try the BETA BIOS KT4 (1.25), KT4V (1.64) too.
Please report back your tests and experimentations of these suggestions.
If you have any workaround to deal with this issue other than set back FSB to 100Mhz, please tell us too.
Thanks for your inputs!

My system, just gotten this 2 days ago
CPU: Athlon XP 2000+
Motherboard: MSI KT4V (MS-6712)
RAM Slot-1:
RAM Slot-2: 512 Mb Kingston DDR 333 CAS 2.5
RAM Slot-3:
display card: Abit Siluro GF3 Ti200
IDE-1M: Western Digital WD800JB (8 Mb Cache) - 80 GB
IDE-1S: Seagate U-Series ST360020A - 60 GB
IDE-2M: Sony DVD-ROM 16x (DDU1621)
IDE-2S: Creative CDRW121032
IDE-3:
SER-1:
SER-2:
PCI-1:
PCI-2:
PCI-3: Accton 1207F 10/100 Fast Ethernet Card
PCI-4: SBLIVE 5.1 Platinum with Live!Drive II
PCI-5:
PCI-6:
PSU: 400Watts (Generic)
BIOS revision: 1.6
Operating System: Windows 2000 with SP3
VIA 4-in-1 drivers : Hyperion 4.45, only AGP and INF installed. IDE drivers are standard Win2k/SP3 ones.
2. CRC ERROR?
FAIL.
When i had my system, i tried installing Windows ME as i wanted to do dual-booting together with Win2K. When i tried to install NVIDIA Detonator drivers (Ver 30.82), it proceeded as normally and asked for a reboot, which i did, then it just hang before the start of Windows ME. I did a reboot, and later selected "Normal" as Windows ME detected a failed startup, and later i was able to enter Windows ME, but it reported that the NVIDIA Detonator drivers were invalid and of wrong type to my display card.
Later i tried to move my files from my C:\ to D:\ and it reported saying that my destination file is invalid.
When i changed my OS to Win2k/SP3 (no more dual-boot), and installed the same NVIDIA detonator driver version, it worked. When i started to copy files again, it later BSOD, and said PAGE_FAULT_ERROR (something like this). When installing from CDs, it will report that my .CAB files are corrupt or have insufficient swap file space (i set mine manually at 1.2Gb size). Then there are times during my reboots and entering win2k, i found my keyboard and mouse (all PS/2) not working and windows loads as usual.
Later i changed my PCI latency setting from 32 to 96, i managed to install from CD without much further issues.
Upon reading these posts here, i didn't realize that the MSI KT4 series or the KT400 chipset had so much issues! i have read from countless sites like extremetech and anandtech and none reported about this particular errors i have encountered during my first 2 days with this setup. (this is my first Athlon setup, i'm previously and Intel person-type).
So far, i conclude in my settings is that:
-32-Bit settings in Bios settings for CD/DVD/CD-RW must be disabled, i concur with Shumway's recommendations.
-DMA settings in Windows 2000 for CD/DVD/CD-RW must be set to PIO mode otherwise when copying from CD to HDD will have read errors.
-Installing the PCI latency fix really does wonders for my set. (PCI Latency fix ver 1.9). Now i can copy files from all my drives without worrying so much about CRC errors. Thank you, George E. Breese.
-I really want to know why in WinME i can't install the NVIDIA detonator drivers, while in Win2K i can.
I post again, once i have done some more tests to my system, especially CD-R writes.
Angel17

XML Large Data transfer

I am trying to retrive about 3000 rows from a table and then converting it to XML using the oracle provided classes(oracle.xml.sql) and display it on IE 5.0/Netscape 4.5 but get a timeout ( I can do the same thing with 10 rows coming back ) with Oracle application Server 4.0.8 on Solaris 2.6 . And I am trying to figure out where its timing out .
Thanks for your help in advance.
Rajan
null

I assume that you've been successful in running this query from SQLPlus, and that it runs in a reasonable amount of time, if not you may need to tune your query or split it to make it run faster.
Also, take a look at your servlet log and verify that you are not overrunning the StringBuffer. If you are you may want to make sure that you have configured the XSQL servlet properly. There's a parameter you can set that will not buffer the output. I can't remember what it's called but it's in the docs.
Hope this helps,
Mark
null

Data Transfer Workbench Slow on Large Imports

I am using version 6.5.11 of the workbench, API version 6.50.53
I have a problem with the speed of imports where the file sizes become large. e.g. I am importing sales invoices using a header file and line items file. Both are tab-delimited text files. If I import 2000 invoices, it takes around 1.8 seconds per invoice. If I import 10000 invoices, it takes around 18 seconds per invoice (50 hours). I actually wanted to import around 30000 invoices, but that was taking a minute per invoice.
Another problem is that the first data line after the header line in every import file is ignored and not processed.
Does anyone know if these have been fixed or will be fixed soon?

To import a large amount of items or invoices with the Data Transfer Workbench, I always shrink the file into x files with 1000 records. That's the only to have a fast process.
Apparently this problem is correctedwith 2004 which is much faster. I haven't tested yet the DTW with 2004 as I just received it.
For the bug you have with the line, it occured to me one time too but not anymore and I can't work out why it did that. Maybe, it could be more efficient for you to create message on the marketplace.
Vincent

Java.lang.OutOfMemoryError during transfer of large data from SAP to PI

Hi experts,
We are trying to transfer large data from SAP to external system via PI but the transfer stucked in sm58 of SAP system with 'error java.lang.OutOfMemoryError'. We have tested before this and we can only get approximately 100K of records to go through successfully. We neeed approximately transfer 300k datas per time. Current setting of max heap size (in mb) of our PI system is 512 at message server and bootstap tab. At servers general tab the max heap size (in mb) is 2048 and its java parameters are having the values below:
-Xmx1024m
-Xms1024m
-Djco.jarm=1
-XX:PermSize=512m
-XX:MaxPermSize=512m
-XX:NewSize=320m
-XX:MaxNewSize=320m
What need to be increased to solve the error?
Thanks.
Regards,
Thava

Hi Thava,
We can set a limit on the request body message length that can be accepted by the HTTP Provider Service on the Java dispatcher. The system controls this limit by inspecting the Content-Length header of the request or monitoring the chunked request body (in case chunked encoding is applied to the message). If the value of the Content-Length header exceeds the maximum request body length, then the HTTP Provider Service will reject the request with a 413 u201CRequest Entity Too Largeu201D error response. You can limit the length of the request body using the tting MaxRequestContentLength property of the HTTP Provider Service running on the Java dispatcher. By default, the maximum permitted value is 131072 KB (or 128MB).You can configure the MaxRequestContentLength property using the Visual Administrator tool. Proceed as follows:
       1.      Go to the Properties tab of the HTTP Provider Service running on the dispatcher.
       2.      Choose MaxRequestContentLength property and enter a value in the Value field. The length is specified in KB.
       3.      Choose Update to add it to the list of properties.
       4.      To apply these changes, choose (Save Properties).
The value of the parameter MaxRequestContentLength has to be set to a high value.
In short parameters to reset values for ABAP side are
icm/HTTP/max_request_size_KB
icm/server_port_ TIMEOUT
rdisp/max_wprun_time
zttp/max_memreq_MB
Parameter to reset values for JAVA side is MaxRequestContentLength.
You can use following link to know more about ICM parameters
http://help.sap.com/saphelp_nw04/helpdata/EN/61/f5183a3bef2669e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/EN/25/b0a4f6f2b03a43a727a165a4d6a555/frameset.htm
regards
Anupam

HCM TDMS data transfer phase hanging and no tables transfered

Hello SAP Colleagues / Practitioners,
Background: We are running TDMS 4.0 HCM PA PD Copy
We are now at the data transfer phase of the data copy. Add it has been already an hour since we have triggered. But the tables are still not being populated. Is there a way to check if the transfer is really processing? The job CNV_MBTCNV_MBT_PEM_START is running in control system but in the receiver system, there are no tdms work process running. is this hanging or is there a way to check if tables are really processed? Thank you.
Regards,
Meinard

You can check the transfer progress in transaction dtlmon in central system. Enter the mass transfer I'd of your package and click on execute button, in the next screen click on tab 'relevant tables', there you can see how many tables have been processed, for more detailed information change the view to calculate throughput.

Large data usage transfer every 6 hours while on a WiFi network, who is doing this transfer? Is Verizon polling my phone causing this usage?

I have three iPhone 5s. All are using my WiFi while at home. One iPhone is sending data over Verizon's network, not WiFi, every 6 hours or so. The time of this data transfer changes every few days. I see data usage number on my Verizon account ranging from a few kilobytes to almost a gigabyte. Is this due to Verizon polling the iPhone for data usage and billing purposes on a regular basis? And what do these billing numbers mean? Where does Verizon get these numbers? Any running apps while on my WiFi should use the WiFi, not Verizon, correct?

I'm having the same issue and this month these data pulls equated to 1891.51 MB!!!
Model: iPhone 5S 64GB. Today I received a notification from Verizon that I had exceeded my data plan. I just went through my entire usage detail report on my phone and separated-out everything that appears to be part of a 6-hour pattern. When I'm at home and most of the time while I'm at work, I am connected to wifi. These data pulls often happen in the middle of the night, when I know for a fact that my phone is charging and connected to wifi at home. Below are the results of the pattern analysis. Keep in mind that I removed all lines that, as far as I could tell, were not part of a 6-hour pattern.
THE PROOF: You sent me three alerts immediately after pulling data from my phone.
The first alert said that I had used 75% of my data plan on 8/11/2014 at 9:45pm while I was at home on wifi. There was a data pull logged at 9:45pm which was part of the 6-hour pattern above.
The second alert stated that I had used 90% of my data at 10:46pm on 8/14/2014; the data log shows a pull just before the alert at 10:45pm.
The third alert telling me I had used all of my data came today while my phone was sitting next to me, connected to wifi at the office. The alert arrived at 12:48pm, the log shows a data pull at 12:48pm.
Screenshots:
How about an explanation Verizon?

Data transfer very slow on mac pro!! mac H/W unable to fit specifications.

Hi,
I am installinginternal disks on the quad mac pro and the transfer ratet in the mac are very slow!!!
the disks are: barracuda 7200.10 disks, 500 GB. Sta II 300, max ST3500630AS firmware 3.AAE . throughput:300mb.jumpred off to get the 300.
MAC tells that the QUAD MAC Pro equipment (2x2.66ghz dualcore intel xeon) comes with a 3.Gigabit specification/ 300MB/sec. (Intel ESB2 AHCI, speed: 3.0 Gigabit. AHCI version 1.10 supported)...
And the benchmarks of the disk ST3500630AS show maximum 80MB/sec and a minimin of 37.3MB/sec, average 63.1 MB/sec. (anandtech tests).
According to seagate.com the maximum sustained data transfer rate:78MB/s
but in the mac the reallity is different: I am getting a transfer rate of 22MB/sec!!!!! . with out any application running and only making copy of the files!!!!
that means that the mac is only providing only 1/3 of the expected transfer rate for the disks..
so, is there a way that the MAC Pro gets all the normal transfer rate for those disks???
Is the Quad MAC Pro hardware unable to get the maximum throughput of the disks???
It seems that the mac is unable to get also the average transfer rate of those disks.. how to correct it???
thanks a lot
Alberto
ps. just for fun: I am getting a faster transfer rate from an old power pc ,and old pc, and firewire 400 and old ide disks!!! (36MB/seg!!!)

Yup.
BThe latest Mac Pro are better, so if you have a new or 2 month old unit, Seagate should work, though I think there should be later firmware.
Some would say those drives take the cake or woRSe.
http://www.barefeats.com/hard91.html
SEAGATE PUZZLES
+Firmware version 3.AEE or later solves the slow sustained large block write speed issue for a single 7200.10 inside the Mac Pro.+
+The remaining performance issue is slow small random read speeds for one, two, three or four drives. No matter how many drives you configure in RAID 0 sets, the average random read speed for combined block sizes from 64K to 1024K is less than 30MB/s (based on QuickBench 3 testing).+
+Until Seagate fixes this, we can't recommend the 7200.10 series as the ideal boot drive for the Mac Pro (or Power Mac).+
http://www.barefeats.com/quad08.html

Linksys WRT54GS vs Dlink DI-524 data transfer rate different.

I was moving some files from one PC to another with the Linksys router and noticed it was slow so I ran DU Meter and Max speed of transfer was 156kb. I then hooked up my Dlink and did the same test and was getting7mg. Why the difference in data transfer speed?
Message Edited by Chadb on 08-23-2007 03:42 PM
Message Edited by Chadb on 08-23-2007 04:00 PM

I installed the new firmware last week. I'm here because of it. I now have intermittent drop/hang/mixed mode problem everybody's complaining about, which I never had before on my GS, till I went from 1.52.0 to the latest 1.52.2 on a v5 GS. Nobodys responded to me, so I'm rolling back.... I can't keep swapping to G only everytime the kids want to use thier PSP's

How can I check the data transfer rate of my FW800 port

I have an iMac 2.4 20 inch (MB323LL/A) with a Lacie external rugged hard drive (320 GB). I have attached it using my FW800 port with the cable supplied with the drive.
It seems slow to me so I was wondering if there is any way to see what the current data transfer is for a backup in progress. Of course it should be 800Mbps but is it really moving at that speed ? How can I tell what speed it is transferring at ? Can I use the same method for USB ports too ?

When you move a large file, you are more likely to see a sustained transfer rate than a small file. Small files have to be individually read/write back and forth, thus slows the actual transfer rate down. If you are moving any file up to 4 GB and probably over 1 MB you'll see more realistic transfer rates. Furthermore your hard drive access time, and RPM figures into the equation too, as well as how much RAM you have. 800Mbps works out to 100 Megabytes per second under ideal conditions.

Very slow network directory listing - but fast data transfer speed once listed?

Hello,
I have really tried to sort this myself before opening up to the community, however I have run out of ideas, and hope someone can offer the magic solution I have missed.
I am currently using the 3.4ghz i7 iMac on a 1GB LAN, running OSX10.7.2 - connecting to a Windows Server 2008 (Running Release 2) over ethernet.
If i go to a network directory that i haven't recently accessed it can take up to 60 seconds to show the contents of that directory. Once i have accessed that folder, if i come out of it and go back in it will be instant again - but the first time it lists the directory it looks like i have opened an empty folder - which after anything from 10seconds to 1 minute will suddenly show the files that are there.
Internet connectivity is fast through the network, and file transfers across the LAN are fast. (showing as approx 300mb per second) I can play and edit HD content across the network with no slowdown so I am confident that this issue is not related to the network speed itself, and is more to do with a setting on this mac.
Symptoms are very similar to this post: https://discussions.apple.com/message/12245148?messageID=12245148&amp%3b#1224514 8 - however i understand that in OSX Lion - SMB was removed - so i cannot find this file to edit.
I have tried bypassing additional hubs in the network by wiring direct cables to the switch that is connected to the file server, this made no difference.
I have also tried disconnecting the ethernet cable, and running over wifi. This fixes the listing problem, but when editing HD content over a network drive, this connection is not fast enough to carry the data without interruption (some projects are linked to up to 900gb of hd video content!)
Using ethernet, I have tried DHCP, DHCP with manual address, and manual mode. All reproduce this problem. i have tried using the windows workgroup, and tried without it.
I have also followed this suggestion: https://discussions.apple.com/thread/2134936?threadID=2134936&tstart=45 and used OpenDNS. this did not fix the issue.
For argument sake, I have also just tested a Macbook Pro running Snow Leopard to see if it was OS related. This reproduces the exact same problem, near instant directory listing on the wifi, a long and arduous wait on ethernet.
I cannot work out why directory listing is instant over wifi, but not over ethernet on 2 different macs, running 2 different versions of OSX. I also do not understand why if the network is having trouble listing the directories - the data transfer speed is 300mbps when i copy files across the wired network from the file server to the mac.
Does anyone have any other ideas as to what could be the problem here? We are about to start work on a very large project, where the content we are editing is spread out across around 200 different network folders (different shoots captured over the past 2 years). We really don't have the time to wait 60 seconds each time we need to access one of those directories to look for a file, and I am very close to pulling all my hair out!
I really look forward to hearing from anyone who can offer any insight.

If you are suspecting that the Windows update had something to do with your LAN going slow, then try the following:
1. Look for updates for your clients LAN NIC driver; or
2. Un-install the updates.

Possible network issues preventing successful application data transfer?

Hello all.
We are having a few issues with a specific set up here at work involving Oracle 11, and Oracle 9 databases and I was hoping someone with a fair idea of how Oracle configurations work when it comes to network connectivity and data transfer would mind sharing their opinion on the matter.
First off, a bit of background. I'm a network security engineer by trade and my experience when it comes to the application side of things, specifically databases is inherently weak; so I apologise if my terminology or logic is slightly off here.
Basically what I'm trying to determine is where a fault lies between our users using a terminal server and a remote Oracle SQL database that should service their requests.
The problem lies wherein the user will utilise the 'sqlplus' application invoked from a Windows command prompt window, and expect to be able login and query a database. I believe we have two versions available to use, version 9 which is not actually in production but able to be used for testing and version 11 which is active in production.
When accessing Oracle 11 servers will hang where we expect to see a successful connection followed by a healthy looking "SQL>" prompt data transfer appears to stall as follows:
C:\>sqlplus username/[email protected]
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Sep 22 18:12:17 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
*hangs here*If we try on the Oracle 9 setup things look fine initially:
C:\>sqlplus username/[email protected]
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Sep 22 18:19:20 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - ProductionHowever once connected to the Oracle 9 box; if we run a query similar to:
sqlplus username/[email protected]
select * from <database> where rownum < 10;This will again hang.
That said however, if we try and run a query similar to:
sqlplus username/[email protected]
select * from <database> where rownum < 5;This will return 4 rows of usable data, without issue.
Our systems engineer provided me with a SQLNET trace from the server side and believes he's identified where it occurs:
[21-SEP-2010 16:06:42:989] nsdo: entry
[21-SEP-2010 16:06:42:989] nsdo: cid=0, opcode=85, *bl=0, *what=0, uflgs=0x0, cflgs=0x3
[21-SEP-2010 16:06:42:989] nsdo: rank=64, nsctxrnk=0
[21-SEP-2010 16:06:42:990] nsdo: nsctx: state=8, flg=0x420c, mvd=0
[21-SEP-2010 16:06:42:990] nsdo: gtn=156, gtc=156, ptn=10, ptc=2011
[21-SEP-2010 16:06:42:990] nsdo: switching to application buffer
[21-SEP-2010 16:06:42:990] nsrdr: entry
[21-SEP-2010 16:06:42:990] nsrdr: recving a packet
[21-SEP-2010 16:06:42:990] nsprecv: entry
[21-SEP-2010 16:06:42:990] nsprecv: reading from transport...
[21-SEP-2010 16:06:42:990] nttrd: entry
#    HANG OCCURS HERE
[21-SEP-2010 16:10:13:347] ntt2err: entry
[21-SEP-2010 16:10:13:347] ntt2err: soc 25 error - operation=5, ntresnt[0]=517, ntresnt[1]=131, ntresnt[2]=0
[21-SEP-2010 16:10:13:347] ntt2err: exit
[21-SEP-2010 16:10:13:347] nttrd: exit
[21-SEP-2010 16:10:13:347] nsprecv: transport read error
[21-SEP-2010 16:10:13:347] nsprecv: error exit
[21-SEP-2010 16:10:13:347] nserror: entry
[21-SEP-2010 16:10:13:347] nserror: nsres: id=0, op=68, ns=12547, ns2=12560; nt[0]=517, nt[1]=131, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[21-SEP-2010 16:10:13:348] nsrdr: error exit
[21-SEP-2010 16:10:13:348] nsdo: nsctxrnk=0
[21-SEP-2010 16:10:13:348] nsdo: error exit
[21-SEP-2010 16:10:13:348] nioqrc: wanted 1 got 0, type 0
[21-SEP-2010 16:10:13:348] nioqper: error from nioqrc
[21-SEP-2010 16:10:13:348] nioqper:    nr err code: 0
[21-SEP-2010 16:10:13:348] nioqper:    ns main err code: 12547
[21-SEP-2010 16:10:13:348] nioqper:    ns (2) err code: 12560
[21-SEP-2010 16:10:13:348] nioqper:    nt main err code: 517
[21-SEP-2010 16:10:13:348] nioqper:    nt (2) err code: 131
[21-SEP-2010 16:10:13:349] nioqper:    nt OS   err code: 0
[21-SEP-2010 16:10:13:349] nioqer: entry
[21-SEP-2010 16:10:13:349] nioqer: incoming err = 12151
[21-SEP-2010 16:10:13:349] nioqce: entry
[21-SEP-2010 16:10:13:349] nioqce: exit
[21-SEP-2010 16:10:13:349] nioqer: returning err = 3113
[21-SEP-2010 16:10:13:349] nioqer: exit
[21-SEP-2010 16:10:13:349] nioqrc: exit
[21-SEP-2010 16:10:13:349] nioqds: entry
[21-SEP-2010 16:10:13:349] nioqds: disconnecting...
[21-SEP-2010 16:10:13:349] nsdo: entry
[21-SEP-2010 16:10:13:349] nsdo: cid=0, opcode=67, *bl=0, *what=1, uflgs=0x2, cflgs=0x3
[21-SEP-2010 16:10:13:350] nsdo: rank=64, nsctxrnk=0
[21-SEP-2010 16:10:13:350] nsdo: nsctx: state=1, flg=0x420c, mvd=0
[21-SEP-2010 16:10:13:350] nsdo: nsctxrnk=0
[21-SEP-2010 16:10:13:350] nsdo: error exitFrom the client log side, it looks like this:
[21-SEP-2010 16:06:42:886] nsdo: entry
[21-SEP-2010 16:06:42:886] nsdo: cid=0, opcode=84, *bl=0, *what=1, uflgs=0x20, cflgs=0x3
[21-SEP-2010 16:06:42:886] nsdo: rank=64, nsctxrnk=0
[21-SEP-2010 16:06:42:886] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[21-SEP-2010 16:06:42:886] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[21-SEP-2010 16:06:42:886] nsdofls: entry
[21-SEP-2010 16:06:42:886] nsdofls: DATA flags: 0x0
[21-SEP-2010 16:06:42:886] nsdofls: sending NSPTDA packet
[21-SEP-2010 16:06:42:886] nspsend: entry
[21-SEP-2010 16:06:42:886] nspsend: plen=17, type=6
[21-SEP-2010 16:06:42:886] nttwr: entry
[21-SEP-2010 16:06:42:886] nttwr: socket 1724 had bytes written=17
[21-SEP-2010 16:06:42:886] nttwr: exit
[21-SEP-2010 16:06:42:886] nspsend: packet dump
[21-SEP-2010 16:06:42:886] nspsend: 00 11 00 00 06 00 00 00 |........|
[21-SEP-2010 16:06:42:886] nspsend: 00 00 03 05 1C 01 01 01 |........|
[21-SEP-2010 16:06:42:886] nspsend: 0F                       |.       |
[21-SEP-2010 16:06:42:886] nspsend: 17 bytes to transport
[21-SEP-2010 16:06:42:886] nspsend: normal exit
[21-SEP-2010 16:06:42:886] nsdofls: exit (0)
[21-SEP-2010 16:06:42:886] nsdo: nsctxrnk=0
[21-SEP-2010 16:06:42:886] nsdo: normal exit
[21-SEP-2010 16:06:42:886] nsdo: entry
[21-SEP-2010 16:06:42:886] nsdo: cid=0, opcode=85, *bl=0, *what=0, uflgs=0x0, cflgs=0x3
[21-SEP-2010 16:06:42:886] nsdo: rank=64, nsctxrnk=0
[21-SEP-2010 16:06:42:886] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[21-SEP-2010 16:06:42:886] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[21-SEP-2010 16:06:42:886] nsdo: switching to application buffer
[21-SEP-2010 16:06:42:886] nsrdr: entry
[21-SEP-2010 16:06:42:886] nsrdr: recving a packet
[21-SEP-2010 16:06:42:886] nsprecv: entry
[21-SEP-2010 16:06:42:886] nsprecv: reading from transport...
[21-SEP-2010 16:06:42:886] nttrd: entry
#    HANG OCCURS HERE
#    Need to <CTRL C> twice to kill
#I've tried searching the net for similar occurrences of some of the interesting looking trace data but there appears to be limited information available, none of which is terribly helpful.
What I'm really after is either someone who has had this issue before, or someone who can better interpret the error output from the trace files and perhaps give me an idea of what's causing it to occur. Specifically whether that error text above relates to a failed connection on the underlying network connectivity side of things or whether it may be something on a higher level within the application layers. We have done packet dumps on firewalls to check the traffic as it traverses the firewall but there are no anomalies that I can see which may be contributing to the issue at hand.
I have organised for some testing to occur within the next 24 hours as there is a Cisco ASA Firewall that sits in the network path that is performing inspection on packets travelling through it. The inspection for SQLNET specifically is disabled, but we intend to enable this once more for testing to see whether it makes a difference. I'm not entirely confident it will however, and until we do get a chance to test any constructive input or alternate ideas will be greatly appreciated. I'm trying to cover as many bases as possible here.
Cheers,
Josh.

So some further testing doesn't show anything interesting. But that said here's a look at a TCP Dump for the Oracle 11 session that hangs:
SNORT01:~ # tcpdump -nni bond0 -vvv vlan and host 125.x.x.x and host 172.x.x.x -c 10000
tcpdump: WARNING: bond0: no IPv4 address assigned
tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 68 bytes
21:55:43.781596 IP (tos 0x0, ttl 126, id 24439, offset 0, flags [DF], proto: TCP (6), length: 48) 125.x.x.x.62008 > 172.x.x.x.1521: S, cksum 0x4d0a (correct), 2416392635:2416392635(0) win 64512 <mss 1380,nop,nop,sackOK>
21:55:43.782454 IP (tos 0x0, ttl 59, id 50281, offset 0, flags [DF], proto: TCP (6), length: 48) 172.x.x.x.1521 > 125.x.x.x.62008: S, cksum 0xc0ae (correct), 3123579836:3123579836(0) ack 2416392636 win 49680 <mss 1460,nop,nop,sackOK>
21:55:43.783311 IP (tos 0x0, ttl 126, id 24440, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.62008 > 172.x.x.x.1521: ., cksum 0xb382 (correct), 1:1(0) ack 1 win 64512
21:55:43.787142 IP (tos 0x0, ttl 126, id 24441, offset 0, flags [DF], proto: TCP (6), length: 284) 125.x.x.x.62008 > 172.x.x.x.1521: P 1:245(244) ack 1 win 64512
21:55:43.788504 IP (tos 0x0, ttl 59, id 50282, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.62008: ., cksum 0xed72 (correct), 1:1(0) ack 245 win 49436
21:55:43.859023 IP (tos 0x0, ttl 59, id 50283, offset 0, flags [DF], proto: TCP (6), length: 48) 172.x.x.x.1521 > 125.x.x.x.62008: P, cksum 0xe166 (correct), 1:9(8) ack 245 win 49680
21:55:43.860392 IP (tos 0x0, ttl 126, id 24445, offset 0, flags [DF], proto: TCP (6), length: 284) 125.x.x.x.62008 > 172.x.x.x.1521: P 245:489(244) ack 9 win 64504
21:55:43.861773 IP (tos 0x0, ttl 59, id 50284, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.62008: ., cksum 0xeb82 (correct), 9:9(0) ack 489 win 49680
21:55:43.861908 IP (tos 0x0, ttl 59, id 50285, offset 0, flags [DF], proto: TCP (6), length: 72) 172.x.x.x.1521 > 125.x.x.x.62008: P 9:41(32) ack 489 win 49680
21:55:43.865341 IP (tos 0x0, ttl 126, id 24446, offset 0, flags [DF], proto: TCP (6), length: 196) 125.x.x.x.62008 > 172.x.x.x.1521: P 489:645(156) ack 41 win 64472
21:55:43.867017 IP (tos 0x0, ttl 59, id 50286, offset 0, flags [DF], proto: TCP (6), length: 167) 172.x.x.x.1521 > 125.x.x.x.62008: P 41:168(127) ack 645 win 49680
21:55:43.874836 IP (tos 0x0, ttl 126, id 24447, offset 0, flags [DF], proto: TCP (6), length: 77) 125.x.x.x.62008 > 172.x.x.x.1521: P 645:682(37) ack 168 win 64345
21:55:43.876405 IP (tos 0x0, ttl 59, id 50287, offset 0, flags [DF], proto: TCP (6), length: 226) 172.x.x.x.1521 > 125.x.x.x.62008: P 168:354(186) ack 682 win 49680
21:55:43.995921 IP (tos 0x0, ttl 126, id 24451, offset 0, flags [DF], proto: TCP (6), length: 1420) 125.x.x.x.62008 > 172.x.x.x.1521: . 682:2062(1380) ack 354 win 64159
21:55:43.995978 IP (tos 0x0, ttl 126, id 24452, offset 0, flags [DF], proto: TCP (6), length: 671) 125.x.x.x.62008 > 172.x.x.x.1521: P 2062:2693(631) ack 354 win 64159
21:55:43.999910 IP (tos 0x0, ttl 59, id 50288, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.62008: ., cksum 0xe18d (correct), 354:354(0) ack 2693 win 49680
21:55:44.015402 IP (tos 0x0, ttl 126, id 24455, offset 0, flags [DF], proto: TCP (6), length: 326) 125.x.x.x.62008 > 172.x.x.x.1521: P 2693:2979(286) ack 354 win 64159
21:55:44.020491 IP (tos 0x0, ttl 59, id 50289, offset 0, flags [DF], proto: TCP (6), length: 1420) 172.x.x.x.1521 > 125.x.x.x.62008: . 354:1734(1380) ack 2979 win 49680
21:55:44.020789 IP (tos 0x0, ttl 59, id 50290, offset 0, flags [DF], proto: TCP (6), length: 671) 172.x.x.x.1521 > 125.x.x.x.62008: P 1734:2365(631) ack 2979 win 49680
21:55:44.021015 IP (tos 0x0, ttl 59, id 50291, offset 0, flags [DF], proto: TCP (6), length: 355) 172.x.x.x.1521 > 125.x.x.x.62008: P 2365:2680(315) ack 2979 win 49680
21:55:44.022489 IP (tos 0x0, ttl 126, id 24457, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.62008 > 172.x.x.x.1521: ., cksum 0x9ea4 (correct), 2979:2979(0) ack 2365 win 64512
21:55:44.148236 IP (tos 0x0, ttl 126, id 24461, offset 0, flags [DF], proto: TCP (6), length: 215) 125.x.x.x.62008 > 172.x.x.x.1521: P 2979:3154(175) ack 2680 win 64197
21:55:44.152125 IP (tos 0x0, ttl 59, id 50292, offset 0, flags [DF], proto: TCP (6), length: 187) 172.x.x.x.1521 > 125.x.x.x.62008: P 2680:2827(147) ack 3154 win 49680
21:55:44.174040 IP (tos 0x0, ttl 126, id 24462, offset 0, flags [DF], proto: TCP (6), length: 1054) 125.x.x.x.62008 > 172.x.x.x.1521: P 3154:4168(1014) ack 2827 win 64050
21:55:44.732635 IP (tos 0x0, ttl 126, id 24482, offset 0, flags [DF], proto: TCP (6), length: 1054) 125.x.x.x.62008 > 172.x.x.x.1521: P 3154:4168(1014) ack 2827 win 64050
21:55:44.735346 IP (tos 0x0, ttl 59, id 50294, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.62008: ., cksum 0xcefc (correct), 3632:3632(0) ack 4168 win 49680
21:56:17.076742 IP (tos 0x0, ttl 126, id 25631, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.62008 > 172.x.x.x.1521: R, cksum 0x942e (correct), 4168:4168(0) ack 2827 win 0
*SQL session hangs here*The 'RESET' occurs when I kill the client using CTRL+C after a long period of inactivity, not during the session itself.
And then.. Here's a successful login and query of 7 rows on the Oracle 9 database from a network perspective:
SNORT01:~ # tcpdump -nni bond0 -vvv vlan and host 125.x.x.x and host 172.x.x.x -c 10000
tcpdump: WARNING: bond0: no IPv4 address assigned
tcpdump: listening on bond0, link-type EN10MB (Ethernet), capture size 68 bytes
21:53:27.598450 IP (tos 0x0, ttl 126, id 19396, offset 0, flags [DF], proto: TCP (6), length: 48) 125.x.x.x.61937 > 172.x.x.x.1521: S, cksum 0xc9b4 (correct), 2519356327:2519356327(0) win 64512 <mss 1380,nop,nop,sackOK>
21:53:27.612189 IP (tos 0x0, ttl 53, id 46015, offset 0, flags [DF], proto: TCP (6), length: 48) 172.x.x.x.1521 > 125.x.x.x.61937: S, cksum 0x1cdb (correct), 1010936359:1010936359(0) ack 2519356328 win 49680 <mss 1460,nop,nop,sackOK>
21:53:27.612905 IP (tos 0x0, ttl 126, id 19398, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.61937 > 172.x.x.x.1521: ., cksum 0x0faf (correct), 1:1(0) ack 1 win 64512
21:53:27.616233 IP (tos 0x0, ttl 126, id 19399, offset 0, flags [DF], proto: TCP (6), length: 321) 125.x.x.x.61937 > 172.x.x.x.1521: P 1:282(281) ack 1 win 64512
21:53:27.629987 IP (tos 0x0, ttl 53, id 46016, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x4886 (correct), 1:1(0) ack 282 win 49680
21:53:27.692135 IP (tos 0x0, ttl 53, id 46017, offset 0, flags [DF], proto: TCP (6), length: 48) 172.x.x.x.1521 > 125.x.x.x.61937: P, cksum 0x3d6e (correct), 1:9(8) ack 282 win 49680
21:53:27.693603 IP (tos 0x0, ttl 126, id 19402, offset 0, flags [DF], proto: TCP (6), length: 321) 125.x.x.x.61937 > 172.x.x.x.1521: P 282:563(281) ack 9 win 64504
21:53:27.707460 IP (tos 0x0, ttl 53, id 46018, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x4765 (correct), 9:9(0) ack 563 win 49680
21:53:27.707883 IP (tos 0x0, ttl 53, id 46019, offset 0, flags [DF], proto: TCP (6), length: 72) 172.x.x.x.1521 > 125.x.x.x.61937: P 9:41(32) ack 563 win 49680
21:53:27.711950 IP (tos 0x0, ttl 126, id 19403, offset 0, flags [DF], proto: TCP (6), length: 196) 125.x.x.x.61937 > 172.x.x.x.1521: P 563:719(156) ack 41 win 64472
21:53:27.725971 IP (tos 0x0, ttl 53, id 46020, offset 0, flags [DF], proto: TCP (6), length: 167) 172.x.x.x.1521 > 125.x.x.x.61937: P 41:168(127) ack 719 win 49680
21:53:27.734468 IP (tos 0x0, ttl 126, id 19405, offset 0, flags [DF], proto: TCP (6), length: 77) 125.x.x.x.61937 > 172.x.x.x.1521: P 719:756(37) ack 168 win 64345
21:53:27.748270 IP (tos 0x0, ttl 53, id 46021, offset 0, flags [DF], proto: TCP (6), length: 199) 172.x.x.x.1521 > 125.x.x.x.61937: P 168:327(159) ack 756 win 49680
21:53:27.878720 IP (tos 0x0, ttl 126, id 19409, offset 0, flags [DF], proto: TCP (6), length: 1110) 125.x.x.x.61937 > 172.x.x.x.1521: P 756:1826(1070) ack 327 win 64186
21:53:28.994991 IP (tos 0x0, ttl 126, id 19443, offset 0, flags [DF], proto: TCP (6), length: 1110) 125.x.x.x.61937 > 172.x.x.x.1521: P 756:1826(1070) ack 327 win 64186
21:53:29.010680 IP (tos 0x0, ttl 53, id 46023, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x3d83 (correct), 1276:1276(0) ack 1826 win 49680
21:53:32.561849 IP (tos 0x0, ttl 53, id 46024, offset 0, flags [DF], proto: TCP (6), length: 989) 172.x.x.x.1521 > 125.x.x.x.61937: P 327:1276(949) ack 1826 win 49680
21:53:32.710661 IP (tos 0x0, ttl 126, id 19550, offset 0, flags [DF], proto: TCP (6), length: 223) 125.x.x.x.61937 > 172.x.x.x.1521: P 1826:2009(183) ack 1276 win 63237
21:53:32.724384 IP (tos 0x0, ttl 53, id 46025, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x3ccc (correct), 1276:1276(0) ack 2009 win 49680
21:53:32.732636 IP (tos 0x0, ttl 53, id 46026, offset 0, flags [DF], proto: TCP (6), length: 133) 172.x.x.x.1521 > 125.x.x.x.61937: P 1276:1369(93) ack 2009 win 49680
21:53:32.739922 IP (tos 0x0, ttl 126, id 19553, offset 0, flags [DF], proto: TCP (6), length: 947) 125.x.x.x.61937 > 172.x.x.x.1521: P 2009:2916(907) ack 1369 win 63144
21:53:32.763266 IP (tos 0x0, ttl 53, id 46027, offset 0, flags [DF], proto: TCP (6), length: 329) 172.x.x.x.1521 > 125.x.x.x.61937: P 1369:1658(289) ack 2916 win 49680
21:53:32.770925 IP (tos 0x0, ttl 126, id 19555, offset 0, flags [DF], proto: TCP (6), length: 78) 125.x.x.x.61937 > 172.x.x.x.1521: P 2916:2954(38) ack 1658 win 64512
21:53:32.784774 IP (tos 0x0, ttl 53, id 46028, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 1658:1836(178) ack 2954 win 49680
21:53:32.787455 IP (tos 0x0, ttl 126, id 19556, offset 0, flags [DF], proto: TCP (6), length: 149) 125.x.x.x.61937 > 172.x.x.x.1521: P 2954:3063(109) ack 1836 win 64334
21:53:33.478760 IP (tos 0x0, ttl 126, id 19578, offset 0, flags [DF], proto: TCP (6), length: 149) 125.x.x.x.61937 > 172.x.x.x.1521: P 2954:3063(109) ack 1836 win 64334
21:53:33.492256 IP (tos 0x0, ttl 53, id 46030, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x34ce (correct), 2268:2268(0) ack 3063 win 49680
21:53:36.820908 IP (tos 0x0, ttl 53, id 46031, offset 0, flags [DF], proto: TCP (6), length: 472) 172.x.x.x.1521 > 125.x.x.x.61937: P 1836:2268(432) ack 3063 win 49680
21:53:36.824225 IP (tos 0x0, ttl 126, id 19733, offset 0, flags [DF], proto: TCP (6), length: 57) 125.x.x.x.61937 > 172.x.x.x.1521: P 3063:3080(17) ack 2268 win 63902
21:53:36.837345 IP (tos 0x0, ttl 53, id 46032, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x34bd (correct), 2268:2268(0) ack 3080 win 49680
21:53:36.838015 IP (tos 0x0, ttl 53, id 46033, offset 0, flags [DF], proto: TCP (6), length: 110) 172.x.x.x.1521 > 125.x.x.x.61937: P 2268:2338(70) ack 3080 win 49680
21:53:36.839520 IP (tos 0x0, ttl 126, id 19734, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 3080:3119(39) ack 2338 win 63832
21:53:36.853507 IP (tos 0x0, ttl 53, id 46034, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 2338:2516(178) ack 3119 win 49680
21:53:36.855886 IP (tos 0x0, ttl 126, id 19735, offset 0, flags [DF], proto: TCP (6), length: 160) 125.x.x.x.61937 > 172.x.x.x.1521: P 3119:3239(120) ack 2516 win 63654
21:53:36.870292 IP (tos 0x0, ttl 53, id 46035, offset 0, flags [DF], proto: TCP (6), length: 99) 172.x.x.x.1521 > 125.x.x.x.61937: P 2516:2575(59) ack 3239 win 49680
21:53:36.879557 IP (tos 0x0, ttl 126, id 19738, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 3239:3278(39) ack 2575 win 63595
21:53:36.893506 IP (tos 0x0, ttl 53, id 46036, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 2575:2753(178) ack 3278 win 49680
21:53:36.895884 IP (tos 0x0, ttl 126, id 19739, offset 0, flags [DF], proto: TCP (6), length: 292) 125.x.x.x.61937 > 172.x.x.x.1521: P 3278:3530(252) ack 2753 win 63417
21:53:36.911464 IP (tos 0x0, ttl 53, id 46037, offset 0, flags [DF], proto: TCP (6), length: 305) 172.x.x.x.1521 > 125.x.x.x.61937: P 2753:3018(265) ack 3530 win 49680
21:53:36.913580 IP (tos 0x0, ttl 126, id 19740, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 3530:3569(39) ack 3018 win 63152
21:53:36.927515 IP (tos 0x0, ttl 53, id 46038, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 3018:3196(178) ack 3569 win 49680
21:53:36.938328 IP (tos 0x0, ttl 126, id 19742, offset 0, flags [DF], proto: TCP (6), length: 315) 125.x.x.x.61937 > 172.x.x.x.1521: P 3569:3844(275) ack 3196 win 64512
21:53:36.953008 IP (tos 0x0, ttl 53, id 46039, offset 0, flags [DF], proto: TCP (6), length: 183) 172.x.x.x.1521 > 125.x.x.x.61937: P 3196:3339(143) ack 3844 win 49680
21:53:36.961020 IP (tos 0x0, ttl 126, id 19743, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 3844:3883(39) ack 3339 win 64369
21:53:36.974890 IP (tos 0x0, ttl 53, id 46040, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 3339:3517(178) ack 3883 win 49680
21:53:36.977183 IP (tos 0x0, ttl 126, id 19744, offset 0, flags [DF], proto: TCP (6), length: 208) 125.x.x.x.61937 > 172.x.x.x.1521: P 3883:4051(168) ack 3517 win 64191
21:53:36.991461 IP (tos 0x0, ttl 53, id 46041, offset 0, flags [DF], proto: TCP (6), length: 110) 172.x.x.x.1521 > 125.x.x.x.61937: P 3517:3587(70) ack 4051 win 49680
21:53:36.993439 IP (tos 0x0, ttl 126, id 19747, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 4051:4090(39) ack 3587 win 64121
21:53:37.007199 IP (tos 0x0, ttl 53, id 46042, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 3587:3765(178) ack 4090 win 49680
21:53:37.011239 IP (tos 0x0, ttl 126, id 19748, offset 0, flags [DF], proto: TCP (6), length: 183) 125.x.x.x.61937 > 172.x.x.x.1521: P 4090:4233(143) ack 3765 win 63943
21:53:37.025767 IP (tos 0x0, ttl 53, id 46043, offset 0, flags [DF], proto: TCP (6), length: 210) 172.x.x.x.1521 > 125.x.x.x.61937: P 3765:3935(170) ack 4233 win 49680
21:53:37.027455 IP (tos 0x0, ttl 126, id 19750, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 4233:4272(39) ack 3935 win 63773
21:53:37.041382 IP (tos 0x0, ttl 53, id 46044, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 3935:4113(178) ack 4272 win 49680
21:53:37.044708 IP (tos 0x0, ttl 126, id 19751, offset 0, flags [DF], proto: TCP (6), length: 75) 125.x.x.x.61937 > 172.x.x.x.1521: P 4272:4307(35) ack 4113 win 63595
21:53:37.058388 IP (tos 0x0, ttl 53, id 46045, offset 0, flags [DF], proto: TCP (6), length: 56) 172.x.x.x.1521 > 125.x.x.x.61937: P 4113:4129(16) ack 4307 win 49680
21:53:37.060398 IP (tos 0x0, ttl 126, id 19752, offset 0, flags [DF], proto: TCP (6), length: 75) 125.x.x.x.61937 > 172.x.x.x.1521: P 4307:4342(35) ack 4129 win 63579
21:53:37.073926 IP (tos 0x0, ttl 53, id 46046, offset 0, flags [DF], proto: TCP (6), length: 56) 172.x.x.x.1521 > 125.x.x.x.61937: P 4129:4145(16) ack 4342 win 49680
21:53:37.088056 IP (tos 0x0, ttl 126, id 19753, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.61937 > 172.x.x.x.1521: ., cksum 0xf23e (correct), 4342:4342(0) ack 4145 win 63563
21:53:56.309909 IP (tos 0x0, ttl 126, id 20509, offset 0, flags [DF], proto: TCP (6), length: 176) 125.x.x.x.61937 > 172.x.x.x.1521: P 4342:4478(136) ack 4145 win 63563
21:53:56.325783 IP (tos 0x0, ttl 53, id 46047, offset 0, flags [DF], proto: TCP (6), length: 398) 172.x.x.x.1521 > 125.x.x.x.61937: P 4145:4503(358) ack 4478 win 49680
21:53:56.329152 IP (tos 0x0, ttl 126, id 20511, offset 0, flags [DF], proto: TCP (6), length: 57) 125.x.x.x.61937 > 172.x.x.x.1521: P 4478:4495(17) ack 4503 win 63205
21:53:56.557234 IP (tos 0x0, ttl 126, id 20519, offset 0, flags [DF], proto: TCP (6), length: 57) 125.x.x.x.61937 > 172.x.x.x.1521: P 4478:4495(17) ack 4503 win 63205
21:53:56.570496 IP (tos 0x0, ttl 53, id 46049, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x24ea (correct), 4904:4904(0) ack 4495 win 49680
21:53:58.561449 IP (tos 0x0, ttl 53, id 46051, offset 0, flags [DF], proto: TCP (6), length: 441) 172.x.x.x.1521 > 125.x.x.x.61937: P 4503:4904(401) ack 4495 win 49680
21:53:58.602228 IP (tos 0x0, ttl 126, id 20579, offset 0, flags [DF], proto: TCP (6), length: 79) 125.x.x.x.61937 > 172.x.x.x.1521: P 4495:4534(39) ack 4904 win 64512
21:53:58.615281 IP (tos 0x0, ttl 53, id 46052, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x24c3 (correct), 4904:4904(0) ack 4534 win 49680
21:53:58.616571 IP (tos 0x0, ttl 53, id 46053, offset 0, flags [DF], proto: TCP (6), length: 218) 172.x.x.x.1521 > 125.x.x.x.61937: P 4904:5082(178) ack 4534 win 49680
21:53:58.745531 IP (tos 0x0, ttl 126, id 20584, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.61937 > 172.x.x.x.1521: ., cksum 0xead2 (correct), 4534:4534(0) ack 5082 win 64334
21:54:01.476582 IP (tos 0x0, ttl 126, id 20707, offset 0, flags [DF], proto: TCP (6), length: 53) 125.x.x.x.61937 > 172.x.x.x.1521: P 4534:4547(13) ack 5082 win 64334
21:54:01.492998 IP (tos 0x0, ttl 53, id 46054, offset 0, flags [DF], proto: TCP (6), length: 53) 172.x.x.x.1521 > 125.x.x.x.61937: P 5082:5095(13) ack 4547 win 49680
21:54:01.499924 IP (tos 0x0, ttl 126, id 20709, offset 0, flags [DF], proto: TCP (6), length: 50) 125.x.x.x.61937 > 172.x.x.x.1521: P, cksum 0xe469 (correct), 4547:4557(10) ack 5095 win 64321
21:54:01.500558 IP (tos 0x0, ttl 126, id 20710, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.61937 > 172.x.x.x.1521: F, cksum 0xeaba (correct), 4557:4557(0) ack 5095 win 64321
21:54:01.513561 IP (tos 0x0, ttl 53, id 46055, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: F, cksum 0x23ec (correct), 5095:5095(0) ack 4557 win 49680
21:54:01.513628 IP (tos 0x0, ttl 53, id 46056, offset 0, flags [DF], proto: TCP (6), length: 40) 172.x.x.x.1521 > 125.x.x.x.61937: ., cksum 0x23eb (correct), 5096:5096(0) ack 4558 win 49680
21:54:01.514175 IP (tos 0x0, ttl 126, id 20713, offset 0, flags [DF], proto: TCP (6), length: 40) 125.x.x.x.61937 > 172.x.x.x.1521: ., cksum 0xeab9 (correct), 4558:4558(0) ack 5096 win 64321The above is obviously fine, but it's really quite strange. I can get the Oracle 9 queries to hang if I select over 7 rows (8 being the point at which it dies).
So I can run
Sqlplus user/[email protected]
Select * from <blah> where rownum < 7;Over and over again, as many times as I like without issue.
But!.. As soon as I run
Sqlplus user/[email protected]
Select * from <blah> where rownum < 8;The session will hang, and from a network perspective there are no packets being transferred in either direction. It looks exactly like the Oracle 11 session in that the session is still ESTABLISHED from a client perspective but no data is flowing in either direction..
Does anyone have any idea why '8' is the magic number that would be causing it to hang? I'm really stuggling to see from a network perspective how this may be occuring, as above the TCPDump looks clean.
Unfortunately I don't have access do a dump on the client/server itself however, just on the network path. I guess that may be where we need to be looking next.
Thanks for the ideas so far all, much appreciated.
Josh.

Re: (forte-users) Delays in data transfer..server-to-client

I would try using DOM (distributed object manager) traces. trc:do:20 will
give you information on each messages sent from and received by the
partition. Levels are 1, 2, 5, 7, and 8, and trc:do:*:8 is very
verbose. trc:do:20:1 may tell you what you want to know. trc:do:1:1 will
give you a basic 1-line-per DOM event trace that may also be all you need.
Communications manager traces will tell you about network and socket-level
activity, but not about the sizes of the messages themselves. In addition,
the operating system makes decisions about physical packet size and
send/receive timing, so CM activities only generally map to actual network
activity.
-tdc
iPlanet Integration Server Engineering
At 09:24 AM 5/1/01 -0700, you wrote:
All,
We are experiencing delays in object transfer between server and client. The
delays are longer with large objects (a single object with an array of objects
that reflect the rows returned in a database) than small (ie: 10 rows vs 400).
Does anyone have any (actual) experience using the various Forte' flags in
order
to show the actual size of the object/packets being passed between the server
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6 seconds or
so. The round trip fare however from the time the client makes the SO call to
the time that it completes is in the 25-30 second range, leaving roughly 20-25
seconds unaccounted for. I have brought in the network guys who are
requesting
the data size and packet information. I did not see what I am looking for
using
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10
flag, but
Forte' indicates that this flag is very verbose, the systems group hates
it when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.

Jeff,
If the object you are passing does not require changes made to it in the
server partition to be returned, pass the object as copy input (pass by
value not reference). If it is necessary to pass the object as input, try
to pass only the attributes that are required to the remote partition
instead of the whole object.
Input/Output is normaly used with scalar variables. When a scalar is passed
to a remote partition, if the value is changed in that partition, the value
is not returned to the calling partition unless Input/Output is used.
Input/Output should not be used for object type parameters, if you need to
pass a reference, use Input only. If you can pass by value, use Copy Input.
You will notice a huge difference in performance changing from Input to Copy
input when passing large objects.
Hope this helps,
Travis Foote
Fortedeveloper.com Inc.
----- Original Message -----
From: "Jeff Bennett" <[email protected]>
To: <[email protected]>
Sent: Tuesday, May 01, 2001 9:24 AM
Subject: (forte-users) Delays in data transfer.. server-to-client
>
All,
We are experiencing delays in object transfer between server and client.The
delays are longer with large objects (a single object with an array ofobjects
that reflect the rows returned in a database) than small (ie: 10 rows vs400).
>
Does anyone have any (actual) experience using the various Forte' flags inorder
to show the actual size of the object/packets being passed between theserver
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6seconds or
so. The round trip fare however from the time the client makes the SOcall to
the time that it completes is in the 25-30 second range, leaving roughly20-25
seconds unaccounted for. I have brought in the network guys who arerequesting
the data size and packet information. I did not see what I am looking forusing
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10flag, but
Forte' indicates that this flag is very verbose, the systems group hatesit when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.
-jeff
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

Reading Large data files from client machine ( urgent)

Hi,
I want to know the best way for reading large data at about 75MB file from client machine and insert to the database.
Can anybody provide sample code for it.
Loading the file should be done at client machine and inserting into the database should be done at server side.
How should i load the file?
How should i transfer this file or data to server ?
How should i insert into the database ?
Thanks in advance.
regards
Kalyan

Like I said before you should be using your application server to serve files >from the server off the filesystem. The database should not store files this big >and should instead just have a reference to this file. I think u have not understood the problem corectly.
I will make it clear.
The requirement is as follows.
This is a j2ee based application.
Application server is oracle application server.
Database is oracle9i
it is thick client (swing based application)
User enters datasource like c:\turkey.data
This turkey.data file contains data
1@1@20050131@1@4306286000113@D00@32000002005511069941@@P@10@0@1@0@0@0@DK@70059420@4330654016574@1@51881100@51881100@@99@D@40235@0@0@1@430441800000000@@11@D@42389@20050201@28483@15@@@[email protected]@@20050208@20050307@0@@@@@@@@@0@@0@0@0@430443400000800@0@0@@0@@@29@0@@@EUR
like wise we may have more than 3 lacs rows in it.
We need to read this file and transfer this to the application server. Which are EJBS.
There we read this file each row in file is one row in the database for a table.
Like wise we need to insert 3 lacs records in the database.
We can use Jdbc to insert the data which is not a problem.
Only problem is how to transfer this data to server.
I can do it in one way. This is only a example
I can read all the data in StringBuffer and pass to server.
There again i get the data from StringBuffer and insert into database using jdbc.
This way if u do it. It is performance issue and takes long time to insert into the database.It even may give MemoryOutofBond exception.
just iam looking for the better way of doing this which may get good performace issue.
Hope u have understood the problem.

Most efficient data transfer between RT and FPGA

This post is related to THIS post about DMA overhead.
I am currently investigating themost efficient way to transfer a set of variables to a FPGA target for out application. We have been using DMA FIFOs for communications in both directions (to and from FPGA) but I'm recently questioning whether this is the most efficient approach.
Our application must communicate several parameters (around 120 different variables in total) to the FPGA. Approximately 16 of these are critical meaning that they must be sent every iteration of our RT control loop. The others are also important but can be sent at a slightly slower rate without jeopardising the integrity of our system. Until now we have sent these 16 critical parameters plus ONE non-critical parameter over a DMA to the FPGA card. Each 32-bit value sent incorporates an ID which allows the FPGA to demultiplex to the appropriate global variables on the FPGA. Thus over time (we run a 20kHz control loop on the RT system - we have a complete set of paramaters sent @ approx. 200Hz). The DMA transfers are currently a relatively large factor in limiting the execution speed of our RT loop. Of the 50us available per time-slot running at 20kHz approximately 12-20us of these are the DMA transfers to and from the FPGA target. Our FPGA loop is running at 8MHz.
According to NI the most efficient way to transfer data to a FPGA target is via DMA. While this may in general be true, I have found that for SMALL amounts of data, DMA is not terribly efficient in terms of speed. Below is a screenshot of a benchmark program I have been using to test the efficiency of different types of transfer to the FPGA. In the test I create a 32MB data set (Except for the FXP values which are only present for comparison - they have no pertinence to this issue at the moment) which is sent to the FPGA over DMA in differing sized blocks (with the number of DMA writes times the array size being constant). We thus move from a single really large DMA transfer to a multitude of extremely small transfers and monitor the time taken for each mode and data type. The FPGA sends a response to the DMA transfers so that we can be sure that when reading the response DMA that ALL of the data has actually arrived on the FPGA target and is not simply buffered by the system.
We see that the minimum round-time for the DMA Write and subsequent DMA read for confirmation is approximately 30us. When sending less than 800 Bytes, this time is essentially constant per packet. Only when we start sending more than 800 Bytes at a time do we see an increase in the time taken per packet. A packet of 1 Byte and a packet of 800 Bytes take approxiamtely the SAME time to transfer. Our application is sending 64 Bytes of critical information to the FPGA target each time meaning that we are clearly in the "less efficient" region of DMA transfers.
If we compare the times taken when communication over FP controls we see that irrespective of how many controls we write at a time, the overall throughput is constant with a timing of 2.7us for 80 Bytes. For a small dedicated set of parameters, the usage of front panel controls seems to be significantly faster than sending per DMA. Once we need to send more than 800 Bytes, the DMA starts to become rapidly more efficient.
Say hello to my little friend.
RFC 2323 FHE-Compliant

So to continue:
For small data sets the usage of FP controls may be faster than DMAs. OK. But we're always told that each and every FP control takes up resources, so how much more expensive is the varsion with FP controls over the DMA.
According to the resource usage guide for the card I'm using (HERE) the following is true:
DMA (1023 Elements, I32, no Arbitration) : 604 Flip-Flops 733 LUT 1 Block RAM
1x I32 FP Control: 52 Flip-Flops 32 LUTs 0 Block RAM
So the comparison would seem to yield the following result (for 16 elements).
DMA : 604 FLip-Flops 733 LUT 1 Block RAM
FP : 832 FLip-Flops 512 LUT 0 Block RAM
We require more FLip-Flops, less LUTs and no Block RAM. It's a swings and roundabouts scenario. Depending on which resources are actually limited on the target, one version or the other may be preferred.
However, upon thinking further I realised something else. When we use the DMA, it is purely a communications channel. Upon arrival, we unpack the values and store them into global variables in order to make the values available within the FPGA program. We also multiplex other values in the DMA so we can't simply arrange the code to be fed directly from the DMA which would negate the need for the globals at all. The FP controls, however, ARE already persistent data storage values and assuming we pass the values along a wire into subVIs, we don't need additional globals in this scenario. So the burning question is "How expensive are globals?". The PDF linked to above does not explicitly mention the difference in cost between FP controls and globals so I'll have to assume they're similar. This of course massively changes the conclusion arrived to earlier.
The comparison now becomes:
DMA + Globals : 1436 Flip-Flops 1245 LUTs 1 Block RAM
FP : 832 FLip-Flops 512 LUT 0 Block RAM
This seems very surprising to me. I'm suspiscious of my own conclusion here. Can someone with more knowledge of the resource requirements differences between Globals and FP controls weigh in? If this is really the case, we need to re-think our approach to communications between RT and FPGA to most likely employ a hybrid approach.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Large data transfer hangs timecapsule

Similar Messages

Maybe you are looking for