Ok, starting this time from bottom up 'testing MaxDB' instead of 'assuming it
works'... I found the following:
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
--- file test1 begin --
SQLMODE INTERNAL
//
USE USER test test
//
CREATE TABLE "TEST"."ZEBRA1" ( "USERSYSID" Integer NOT NULL, "CONTACTEMAIL1" Varchar
(64), PRIMARY KEY ("USERSYSID") )
//
INSERT INTO "TEST"."ZEBRA1" (USERSYSID, ContactEMAIL1) VALUES (100, '[EMAIL
PROTECTED]')
//
--- file test1 end ---
==== 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.
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.
I need this problem resolved ASAP. I've spent more than 30 hours tracking it down to
this one specific issue! Any help reproducing it or
getting to the bottom of it is appreciated.
Thank you.
Stephen Gutknecht
---- Msg sent via @Mail - http://www.IPCoast.com/
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
