Hi Stephen,

[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wrote:
> 
> Ahh, progress!
> 
:-))

>   ===== Windows XP output START ========
> 
> C:\>loadercli -n 192.168.0.150
> Loader Server Protocol File:    'c:\program 
> files\sdb\data\wrk\loader.prt'
> 
> loadercli>USE USER test test SERVERDB TST
> ERR -25004
> A connection to the database could not be established: 1 = 
> database not running.
> ---
> loadercli>USE USER test test SERVERDB TST ON 192.168.0.150
> OK
> 
>   ===== Windows XP output END ========
> 
> 
> And a slight variation (second run) to emphasize further:
> 
> 
>   ===== Windows XP output START ========
> 
> C:\>loadercli -n 192.168.0.150 -d TST
> Loader Server Protocol File:    'c:\program 
> files\sdb\data\wrk\loader.prt'
> 
> Connection to database TST on 192.168.0.150 established.
> loadercli>USE USER test test SERVERDB TST
> ERR -25008
> Logon failure; previous user's () connection was restored.
> 
> ---
> loadercli>USE USER test test SERVERDB TST ON 192.168.0.150
> OK
> 
>   ===== Windows XP output END ========
> 
> Am I just being a fool here?   Is not the parameter '--n 
> 192.168.0.150" supposed to work the duration of the loadercli 
> session?  I'm sorry if this 
> is some misunderstanding of documentation on my part.
> 
May be I'm the fool here. I've to check this. The node info should
be saved up to the point where a new node is specified with a
new USE USER command.
I'll get back to you.

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]

Reply via email to