[comp.databases] Help on moving ORACLE data from PC to VAX

df555@cs.city.ac.uk (WHITTAKER A.P.B.) (11/16/90)

I am having great problems exp(orting) a table from pc Oracle ver 5.1b to a  
VAX 8700 ver 5. When I try to imp(ort) the table,  I get messages about  
seals not matching when using  Pacerlink binary transfer and abnormal 
end of file when using Kermit. I have already tried multiple sources for help, 
including Oracle UK Support, with no luck -- everyone assures me it should work. 
Can _anyone_ help? 
 
No flames please, this is a novice speaking. 
 
Tony Whittaker  Medical Oncology, Royal London Hospital, London E1 1BB, UK 
a_whittaker@uk.ac.icrf

mar7363@saturn.lerc.nasa.gov (Michael A. Rife (Boeing Computer Support)) (11/19/90)

In article <1990Nov16.151549.4998@cs.city.ac.uk>, df555@cs.city.ac.uk (WHITTAKER A.P.B.) writes...
>I am having great problems exp(orting) a table from pc Oracle ver 5.1b to a  
>VAX 8700 ver 5. When I try to imp(ort) the table,  I get messages about  
>seals not matching when using  Pacerlink binary transfer and abnormal 
>end of file when using Kermit. I have already tried multiple sources for help, 
>including Oracle UK Support, with no luck -- everyone assures me it should work. 


We had a similar problem with Kermit.  We were using Kermit within a VT 
emulator.  What we had to do is increase the record size on the transfer.  
In the VT package we were using the max record size was set at 255.  We had 
to set it to the largest size possible because EXP files have large record 
sizes.  This will give you something to try.

anderson@well.sf.ca.us (David E. Anderson) (11/19/90)

>>I am having great problems exp(orting) a table from pc Oracle ver 5.1b to a  
>>VAX 8700 ver 5. When I try to imp(ort) the table,  I get messages about  
>>seals not matching when using  Pacerlink binary transfer and abnormal 
>>end of file when using Kermit. I have already tried multiple sources for help, 
test the data transfer with a round trip:
pc->vax->pc
then diff the files or try to import on the pc. 
This problem has always been a data transfer issue; failure in this test would
provide show where the problem lies.