Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
RE: loadercli problems, Windows XP to Solaris 8 - MaxDB 126.96.36.199
From: Schildberg, Steffen (steffen.schildbergsap.com)
Date: Thu Feb 19 2004 - 05:30:26 CST
iml-sapdbi405.com [mailto:iml-sapdbi405.com] wrote:
> Ok, PAGES format failed... so I'm trying "RECORDS UCS2" mode.
What has exactly been the problem. I couldn't reproduce any
error here when transporting a table from big endian to little
endian in format PAGES. The Loader is actually thought to do
> 1. When I try to run loadercli from Windows XP using the
> Solaris 64 as a destination node... I often get unxplained
> errors with authentication
> or other. Loadercli will sometimes say protocol error.
> However, there are times where it seems to work well...
> uploads for many hours (and
> database pages consumed on the Solaris side).. but then fials
> at the end in that none of the data can be found with SQL SELECT.
> 2. So I transfer my extracted table data using SCP (exact
> binary copy) from XP onto the disk of the Solaris system.
> Run the Solaris loadercli
> on local server and datafile. I get these errors:
> TABLELOAD TABLE mytable DATA INSTREAM FILE 'extract-r1-data'
> RECORDS UCS2
> // *
> // E -25371: Error converting data from UCS2 to ASCII;
> source contains invalid characters or character sequences
> // M Error at record 1 in infile.
> // E -25302: This value is not a valid number: -
> // M Last transaction committed at input record 0
> The table was created using the CREATE TABLE from my
> extract... it has the same structure (including a couple
> Unicode fields). The database
> was also created with Unicode enabled... The error just
> makes no sense. I'm suspecting a incompability here...
You can not transfer the generated file to another processor
architecture yet with UCS2 data as the Loader is not yet
aware of the byte swap in Unicode data. So the first approach
should be the one of choice. Would you mind to send error
messages found in the protocol file to let us help you further?
BTW if the loader says protocol error it simply means (in most
cases) it crashed :-(
SAP DB Team
SAP Labs Berlin
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb