Hi Stephen,
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
>
>
> loadercli running on Windows XP talking to a Solaris 8 does
> NOT behave the same as loadercli running native on Solaris!
>
> 1. Install MaxDB 7.5.0.8 on Windows XP, Install MaxDB 7.5.0.8
> on Solaris 8.
> 2. create the demo (TST) database natively on Solaris 8.
> 3. Feed the following into loadercli using...
>
> loadercli -d TST -n 192.168.0.150 -u dba,dba -b test1 -E 1
>
[snipped loadercli script content]
>
> ==== The problem ====
>
> This works correctly on Solaris native loadercli. Problem is
> that a remote Windows XP loadercli (talking to Solaris MaxDB)
> always fails on
> the "USE USER" command. No matter what I try, putting
> username in password with and without quotes, uppercase /
> lowercase, it fails.
>
Hmm, do you think there is anything I could do to force you sending
the content of the protocol file loader.prt for the failing command
(do I have missed it somehow)?
I/We can't offer any help on messages like 'it fails'. How does
it fail (some err no)? Is there any entry in the protocol file?
Ok, to speed it up I'd suggest the following:
1. Start loadercli on your XP system without any option. You'll
be prompted for input.
2. Issue the command
USE USER dba dba SERVERDB TST ON 192.168.0.150
3. Send the output.
> I can use ODBC to "CREATE TABLE", but this does not fix the
> problem. System then has the opposite problem, not being
> able able to get
> loadercli to find tables when DBLOAD runs. loadercli seems
> to be using some incompatible means of creating /
> authenticating "USE USER" cross
> platform.
>
Nope, it doesn't actually.
Regards,
Steffen
--
Steffen Schildberg
SAP DB Team
SAP Labs Berlin
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
