If bi-directional parallel data transfer possible in DAQ 6009???
want to interface AVR to DAQ6009 via parallel 8-bit bus but I need it to be bi-directional thus stuck at this point since m nt sure whether bi-directional data transfer possible or not
Solved!
Go to Solution.
First of all, serial port is available on win7. Silly to say that it's not. Since it is a single bit, mention of it is irrelevant, as is USB.
Second, the lines of the 6009 can be either input or output. A line cannot be both so you would need to stop your task, change the line direction, and start a new task.
Third, you say there is no protocol for the AVR yet you ask for an example. If you don't know the protocol, you need to read the data sheet and understand it. I'm going to assume that you mean this AVR.
For digital I/O examples, see Help>Find Examples. As mentioned, the 6009 is strictly software timed so you will be limited to 'bit-banging' per the device's specs and if it has a minimum clock rate, find other hardware.
Similar Messages
-
DIRECT MODE에서의 PARALLEL DATA LOADING
제품 : ORACLE SERVER
작성날짜 : 1999-08-10
Direct mode에서의 parallel Data Loading
=======================================
SQL*Loader는 동일 table에 대한 direct mode에서의 parallel data load를
지원하고 있다. 이는 여러 session에서 동시에 데이타를 direct mode로 올림으로써
대용량의 데이타의 로드 속도를 향상시킬 수 있다. 특히, data file을 물리적으로
다른 disk에 위치시킴으로써 더욱 큰 효과를 낼 수 있다.
1. 제약사항
- index가 없는 table에만 로드 가능
- APPEND mode에서만 가능. (replace, truncate, insert mode는 지원 안됨)
- parallel query option이 설치되어 있어야 함.
2. 사용방법
각각의 data file을 load할 control file들을 생성한 후, 차례차례 수행하면 됨.
$sqlldr scott/tiger control=load1.ctl direct=true parallel=true&
$sqlldr scott/tiger control=load2.ctl direct=true parallel=true&
$sqlldr scott/tiger control=load3.ctl direct=true parallel=true
3. constraint
- enable parameter를 사용하면 데이타 로드 작업이 모두 끝난 후, 자동으로
constraint을 enable시켜 준다. 그러나 종종 enable되지 못하는 경우가
있으므로 반드시 status를 확인해야 한다.
- primary key 나 unique key constraint이 걸려 있는 경우, 데이타 로드 후
자동으로 enable할 때, index를 생성하느라 시간이 많이 소모될 수 있다.
따라서 data만 parallel direct 모드로 로드 한 후, index를 따로 parallel로
생성하는 것이 성능 측면에서 바람직하다.
4. storage 할당 방법 및 주의사항
direct로 데이타를 로드하는 경우 다음 절차를 따라 작업한다.
- 대상 table의 storage 절에 기초해 temporary segment를 생성한다.
- 마지막 데이타 로드 작업이 끝난 후, 마지막에 할당되었던 extent의 비어 있는
즉, 사용하지 않은 부분을 trim 한다.
- temporary segment에 해당되어 있는 extent들의 header 정보를
변경하고, HWM 정보를 수정하여, 대상 table에 extent가 소속되도록 한다.
이러한 extent 할당 방법은 다음과 같은 문제를 야기시킨다.
- parallel data load에서는 table 생성 시 할당된 최초 INITIAL extent를
사용하지 않는다.
- 정상적인 extent 할당 rule을 따르지 않고, 각 process는 next extent에
정의된 크기를 할당하여 data load를 시작하고, 새로운 extent가 요구될
때에는 pctincrease 값을 기준으로 할당되게 되는데, 이는 process 간에
독립적으로 계산되어진다.
- fragmentation이 심하게 발생할 수 있다.
fragmentation을 줄이고, storage 할당을 효율적으로 하기 위해서는
- INITIAL을 2-5 block 정도로 작게 하여 table을 생성한다.
- 7.2 이상 버젼에서는 options 절에서 storage parameter를 지정하여
사용한다. 이 때 initial과 next를 동일한 크기로 주는 것이 바람직하다.
OPTIONS (STORAGE=(MINEXTENTS n
MAXEXTENTS n
INITIAL n K
NEXT n K
PCTINCREASE n))
- options 절을 control file에 기술하는 경우 반드시 insert into tables
절 다음에 기술해야 한다.First, thanks for the hints. In the meanwhile I found some other documentation regarding my issue.
As far as I understand, if I want to load parallel, I have to create multiple InfoPackes and split up the records in the selection criteria, e.g.:
- InfoPackage 1, Students 1 - 10.000
- InfoPackage 2, Students 10.001 - 20.000
...and so on.
Following that I need to create a Process Chain that starts loading all packages at the same point in time.
Now...when the extractor is called, there are two parts that it runs through:
- Initialization of the extractor
- Fetching of records
( via flag i_initflag in the extractor ).
In the initialization I want to run the pre-fetch module. I worked everything regarding that already. Only when the pre-fetch is finished, will the actual data loading start.
What I am not sure about is: Is this flag (the i_initflag mentioned above) passed for each InfoPackage that is started?
Jeroen -
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. -
6301 & PC Suite - "Data transfer not possible. Che...
Well, as the title says really.
Upgraded from 6280 -> 6301.
I use Outlook 2003 and sync contacts & calendar.
Sync'd the 6280 before finalising upgrade, plugged in the 6301 with a mini-usb cable (All driver reports it installed new hardware fine) once it had fully come into service and it wouldn't sync.
The phone displays "Data transfer not possible. Check connection" and Nokia PC Sync shows the warning "The mobile phone as not responded". It's solution is "Please ensure your phone is in the standby mode, then restart the Synchronisation. "
Have updated to latest version of PC Suite 6.85.
A bit annoying, as I no longer have any contacts info on the new phone...
Running XP, AMD 3ghz, 4gb ram.Having spent many hours on this I have now got it working...
This is how :
1. On the phone go to : Settings: Sync and Backup: Server Sync: PC Syncronisation and enter a username and password.
2. Select Synchronise in Nokia PC Suite, in the Connected to 6301 window click the spanner (settings) icon. Now click the Adjustable wrench (Advanced) Icon and go to the sync profile tab and enter the same username and password that you used on the phone. Click OK twice and sync away...
Message Edited by kage64 on 05-May-2008 11:04 PM -
Initialize delta without data transfer not possible
Hullo,
I want to switch the upload procedure for an ODS from full to delta. For I have researched SAP Note 689964 and executed the program RSSM_SET_REPAIR_FULL_FLAG for the ODS-object and datasource. It successfully modified the request and set the 'REPAIR_FULL' flag.
Now I want to change the InfoPackage from Full update to Delta. According to the note I have to perform an init simulation, my problem is that the option initialize delta without data transfer is in display mode only (i.e. it's gray and I cannot select it).
The InfoSource in question is "0HR_PY_1". I've checked several others and with some it is possible to select the initialization simulations and with others it's not.
My questions are a) Why is it this option grayed out? and b) What can I do to enable the selection of this option?
Any help is appreciated.Hullo AK,
thanks for pointing out that note, sadly it's for "0HR_PY_PP_1" and not "0HR_PY_1".
However it lead us to note '611199'...
<b>Symptom</b>
Some attributes of the following DataSources are not defined.
0HR_PY_1 DataSource:
- Commit after initialization phase
- DeltaInit Simulation
0HR_PY_PP_1 DataSource:
- Commit after initialization phase
0HR_PY_PP_2 DataSource:
- Commit after initialization phase
<b>Other terms</b>
PXDW, extractor, posting transfer, settlement, PCPO, PCP0
<b>Reason and Prerequisites</b>
The SAP settings for the DataSources are incomplete.
The following attributes should be set:
0HR_PY_1 DataSource:
- Commit after initialization phase: no commit
<u>- DeltaInit Simulation: Mode is not supported</u>
0HR_PY_PP_1 DataSource:
- Commit after initialization phase: no commit
0HR_PY_PP_2 DataSource:
- Commit after initialization phase: no commit
<b>Solution</b>
Import the corresponding Support Package into the Plug-In Releases 2003.1 and 2002.2 and copy/activate the DataSources in the plug-in system again.
If the correction is imported, you can <i>no longer select the "DeltaInit simulation"</i> option for the delta initialization of the <b>0HR_PY_1</b> DataSource/InfoSource.
As long as you have not imported the correction or you are using an even older plug-in release, you should never select the "DeltaInit simulation" option during the delta initialization for the 0HR_PY_1 DataSource/InfoSource. <b>The 0HR_PY_1 DataSource does not support this mode.</b>
The 0HR_PY_1 DataSource only supports the delta initialization (without the DeltaInit simulation) and subsequent delta calls.
Sadly enough, not what I wanted to read, but well at least I now know that I shouldn't look into this solution anymore.
Again, thanks for your help. -
Data transfer not possible? Nokia 2700 classic syn...
I have Ovi setting on my 2700 classic, everytime i try to sync contacts - the prompt comes like "data transfer not possible". Help me with it also plz tell me any way of getting contacts back on phone/sim from ovi without PC. Addl. Info:- i had syncd the phone successfully on gprs without pc and i am so hoping that their must be some way out. Thanks
I am also having the same problem. I am using Nokia 7210. Please help me
-
PC Suite 7 – Data transfer not possible. Check dat...
When I try to use (open, update, modify etc.) the “contacts list” in PC suite version 7.0.7, I always have the following error: “Data transfer not possible. Check data connection”. Instead the SMS list works fine. My phone is Nokia 6267.
Anyone has a solution?
Best Regards
Bix123Hi everyone,
I had the same problem for months with many PC Suite versions & both XP service packs until I tried a phone setting just for testing and everything worked out fine In my phone (3110c) under Settings / Connectivity / Data Transfer / PC Sync, I filled in a random User name & Password and voila!!! All contacts copied just fine!!! I hope this works with other models with the same menu as well. It looks that it's not a PC Suite problem after all (at least for me that is).
Hope I helped you guys
Spiros
Greece -
Will data transfer in parallel in GPIB interface?
Hi all,
I have two devices (supporting GPIB) connected in serial and connect to the GPIB interface card. Those two devices have two different addresses and I use VISA module to send data in parallel. But the GPIB cables are connected in serial, so does it mean it will be locked when transferring data to one device? I think GPIB transfer rate is not that low (about 1Mbyte/sec) but it takes so long to transfer 500kB to the device (about 45sec).
Solved!
Go to Solution.Dennis_Knutson wrote:
The GPIB bus does not support parallel data transfers so you are certainly sending it that way.
You have not provided the instrument or your code so it.is impossible to say anything about your transfer rate but the 1MB is a theoretical maximum that you seldom achieve in the real world.
Here is the link for the device I have
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9294659CE034080020E748...
The code is not written by me, but I extract the core part and show as below
You will see that there is only one GPIB interface (0), both device 1 and device 2 are connecting to the same card. The data sending to device 1 and device 2 is about 400kB (shown as xxxx.xxxxx. and yyyy.yyyyy). -
5310 "Data transfer not possible" calendar sync is...
I'm trying to get my Nokia 5310 to synchronise its calendar with my work's Outlook 2003, using PC Suite 7.1.26.1. At work they use Windows XP and Outlook 2003 SP2. I don't want to bring my USB cable into work, so I'm using bluetooth to connect. The connection itself works fine - I can browse the 5310's media content, calendar and contacts using my computer.
The problem is with synchronising calendar with Outlook. It just won't do it. Every time, I get a "Data transfer not possible. Check data connection" message on the phone and a "PC Sync was unable to locate your Outlook message store" error in the PC Suite sync log.
Things I have tried:
Repair PC Suite.
Install new settings (spanner star button) and go through the wizard again.
As 2, but with manually selecting the Outlook folders on my profile (which were, in any case, already preselected correctly).
Copying a new profile and trying to sync with that.
Putting in (the same) username/password in PC Suite and the phone's "sync and backup" option.
None of these works. My work computer will happily sync with Google calendars, but won't sync with my phone.
I've had a good look through the forums but can't seem to find any solutions that work for me. Does anyone have any ideas of how I can get this to work?Try one more thing. This worked for me.
1. Remove ALL email profiles. -
2. Recreate profile - don't forget to write down your Email exchanger server address. This will force Microsoft outlook to startup as if your a new user but will load your existing email from the server.
3. Setup PC Sync -- again
- this has been a pain in the neck!! - something gets corrupted in the profile that PC Sync does not like. -
Is there any support for data transfer compression in oracle XE?
Hi
Thank you for reading my post.
I am wondering whether it is possible to ask database and JDBC driver to use some sort of compression for data transfer?
I want to reduce the network workload as much as possible.
ThanksAFAIK, Not directly from Oracle.
-
Control parameters for data transfer
Hi!
There are no data in SBIW source system - General Settings - Maintain Control Parameters for Data Transfer.
How does it have an influence on loading data?Hi,
Maximum size of a data packet in kilo bytes
The individual records are sent in packages of varying sizes in the data transfer to the Business Information Warehouse. Using these parameters you determine the maximum size of such a package and therefore how much of the main memory may be used for the creation of the data package. SAP recommends a data package size between 10 and 50 MB.
Frequency with which status Idocs are sent
With this frequency you establish how many data IDocs should be sent in an Info IDoc.
Standard settings
Frequency 1 means, for example, that there is an Info IDoc for every data IDoc. In general, you should choose a frequency between 5 and 10 but not greater than 20.
Recommendation
The larger the packet size for a data IDoc, the smaller you should set the frequency. By doing this, you make it possible to get information on the respective data load status in relatively short time periods when uploading data.
Maximum number of parallel processes for data transfer
Select a number greater than 0.
Parallel processes can be set from the SAP core release 3.1I onwards.
These parameters are, therefore, ignored in releases before 3.1I.
However, there is a possibility of importing the SAP release 3.1I into earlier releases.
The more parallel processes that can run the better the performance of your system will be. However, you must bear in mind the number of available dialog processes here.
It will be fine and more effective if you use sap recomended values in those respective fields -
Is there a way to access OSX directly from Parallel Desktop - without a password?
Hi guys.
My dear late brother had left his Mac Mini when he chose to exit this world.
All the while - his Mac Mini was still on and running.
After a while when having to pack his belongings, I noticed this and tried to login - but all the passwords I've tried were wrong.
Meanwhile I had to shut his Mac off - and when later on turned it on again - it went straight to Parellel Desktop (running Windows)..
I noticed there were some files on it - through My Computer :// ...
But all those files which are found on the above folder etc. - is that all files available on the Mac including files on OSX??
So my question goes: The files found on My Computer :// (running Windows) - are they the exact files which can be seen on OSX or is it possible that there's more files available when running OSX??
One more question : Is it possible to access OSX directly from Parallel Desktop - without having to type any password on OSX?Thanks for the info.
So that must mean - there may be more files available on the OSX partition then..?
But seeing that it requires a password (login) in order for me to access the OSX system - is there any chance of getting access to all the data, without losing them? -
Hi all,
Can anyone please explain me what are synchronous and asychronous data transfer methods?
Where are the settings to be done in R/3 to get data to BI ?
Thanks in advanceData Transfer
Definition
Synchronous Data Transfer
Data is transferred directly (simultaneously, synchronously) from program to program via CPI-C communication.
Both communications partners must be available at the same time. Because the central SAP system in a typical SAP installation does not run round the clock, but the linked systems are frequently in operation 24 hours a day, asynchronous data transfer is necessary.
Synchronous data transfer has the following disadvantages:
Transfer is not possible is the partner system or the line is not available.
A data backlog in the reciever system causes a data backlog in the sender system. Processing in the application is delayed.
If a connection is broken, it may be necessary to perform a recovery in both systems.
Asynchronous Data Transfer
With asynchronous, or buffered, data transfer, data is temporarily stored in a sequential queue.
Asynchronous transfer has the following advantages:
Wait times in the sender system are avoided.
A recovery is automatically performed in the sender system.
Transfer need not be performed during online time. This avoids placing unnecessary load on the system and thus helps to reduce costs.
The Queue Application Programming Interface (Q-API) is an SAP interface for asynchronous data transfer.
Data is buffered sequentially and processed immediately or later by an asynchronously running process.
One possible processing method is to send data to an external partner system via CPI-C. Data units that belong together can be stored in accordance with transaction and sent to a communications partner.
Data is buffered in queues before it is transferred to the target system.
In an R/3 System, the queues are stored in a relational database. All R/3 database systems are supported. -
Hi Data transfer methods for ABAP Dataflow
HI
Good Day !!!!
Can any one Explain about What are Data tansfer mothods in ABAP Dataflow Explain Each one which is the best one can you explain with example .
Regards
ChanduData Transfer
Definition
Synchronous Data Transfer
Data is transferred directly (simultaneously, synchronously) from program to program via CPI-C communication.
Both communications partners must be available at the same time. Because the central SAP system in a typical SAP installation does not run round the clock, but the linked systems are frequently in operation 24 hours a day, asynchronous data transfer is necessary.
Synchronous data transfer has the following disadvantages:
Transfer is not possible is the partner system or the line is not available.
A data backlog in the reciever system causes a data backlog in the sender system. Processing in the application is delayed.
If a connection is broken, it may be necessary to perform a recovery in both systems.
Asynchronous Data Transfer
With asynchronous, or buffered, data transfer, data is temporarily stored in a sequential queue.
Asynchronous transfer has the following advantages:
Wait times in the sender system are avoided.
A recovery is automatically performed in the sender system.
Transfer need not be performed during online time. This avoids placing unnecessary load on the system and thus helps to reduce costs.
The Queue Application Programming Interface (Q-API) is an SAP interface for asynchronous data transfer.
Data is buffered sequentially and processed immediately or later by an asynchronously running process.
One possible processing method is to send data to an external partner system via CPI-C. Data units that belong together can be stored in accordance with transaction and sent to a communications partner.
Data is buffered in queues before it is transferred to the target system.
In an R/3 System, the queues are stored in a relational database. All R/3 database systems are supported. -
Hello All,
Can anybody explain data transfer using DXWB clearly(if possible screen shots).
In general Which tool was used either LSMW or DXWB.
thanks and Regards
madhavihi madhvi,
Before using the LSM Workbench or DX Workbench, you need a concept for data migration.
<b> Recommendation</b>
For batch input / direct input: use the test functionality in DX-Workbench and run the whole import process from LSMW
For BAPI / IDoc: use DX-workbench and do mapping and conversion via an LSMW object LSMW can be called from DX-workbench as a task (from 4.6C on)
<b>Core functions of the LSM Workbench:</b>
1.Import data from a legacy system
2.Converting data from its original (legacy system) format to the target (SAP) format
3.Importing the data using the standard interfaces of SAP (IDoc inbound processing, batch input, direct input)
<b>Core functions of the DX Workbench:</b>
1.Data import
2.Monitoring for data import
3.Create and edit test data
4.Restart functionality
thnx.
Ashraf.
Maybe you are looking for
-
Changing the _alpha value of a movie does nothing for me
Hi This is probably a real basic problem but it has had me tearing my hair out. I have two movies which I have moved into position programatically and now I wish to alter the _alpha value of them. Putting a trace on the fadeMovie function shows that
-
IPhone 5c stopped turning on after IOS 8.1 update.
2 days ago i decided to update my iPhone 5c to IOS 8.1. There was no noticeable issues with the update, but after attempting to use the phone, i did notice that the phone was not powering on. I've contacted apple support, and have done all the troubl
-
Regarding Creation of Custom IDOC
Hi, This is Abdullah Shaik. I want to create an IDOC from the existing IDOC. Some times I need to add some segments to the existing IDOC. Can anybody plz let me know the process how to create the Customized IDOC from the Standard IDOC? Thanks & Regar
-
I just tried to install iTunes 8 on Windows XP. It failed because it could not remover the old Apple Updater. The last update of the Updater failed and now I cannot remove it with Windows' remove installed programs. It wants an MSI that I cannot find
-
Horizontal stacked bar chart supported?
Hi, we have the requirement for a horizontal stacked bar chart. Is this supported in 12.x? Just to make shure bevore extending our own Chart Applets. Thanks, Matthias