Maxdb xuser Key "c" for "control" not exist

Question

Hello everyone,
a colleagues had a problem on a MaxDB 7.7 with NW 7.01 Java only Systems.
He said, that there is no xuser key "c" for the user "control".
<xuser list>
Ok, I can create the key with
xuser -U c -u control,<pass> -d <DBSID> -n <host> set
I this real ?
It's a bug ?
It' a new feature ?
Thanks,
Rainer

Answer 1

> we make backups with the xuser-key  "c"
>                   " dbmcli -d $sid -U c -uUTL -c ... "
Why do you put the SID again into the dbmcli call?
It's already included in the XUSER data.
> In the old Version the XUser Key stand for user  control.
It's still like this.
> In the new Version NW7.01on MaxDB 7.7 there in no default  xuser Key  "c" .
>
> XUSER Entry  1
> -
> Key              :DEFAULT
> Username    :SAPDBJ2EE
> -
> XUSER Entry  2
> -
> Key              :c_J2EE
> Username    :CONTROL
> -
> XUSER Entry  3
> -
> Key         :w
> Username    :SUPERDBA
Hmm... actually I never came across that.
Anyhow, since you can trigger backups with the 'w' key (SUPERDBA) as well there's no problem here.
> It's typical for all new Version from Database  Maxdb   > 7.7 ?
> It's typical for all new Version from NW   >  7.01 ?
> It's typycal for Java only Systems ?
As I said - I never realized that the key should be generally missing.
Maybe somebody deleted the key on your system?
Or maybe it was not created in the first place for the user you're working with.
regards,
Lars