Skip to Content
avatar image
Former Member

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

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jul 08, 2009 at 12:50 PM

    Hi Rainer,

    to me it's totally unclear what your question really is.

    XUSER has been around for more the ten years.

    There is a note (39439 - XUSER Eintraege fuer SAP DB 6.x und 7.x) for which the first filed version dates back to April 1996 ...

    So what is your question?

    regards,

    Lars

    Add comment
    10|10000 characters needed characters exceeded

    • > 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

  • Jul 09, 2009 at 10:49 AM

    That's normal/standard.

    In Java only systems you will have a 'c_J2EE' control user key.

    In ABAP only systems you will have the usual 'c' control user key.

    In ABAP+Java you will have both the 'c_J2EE' control user and the 'c' control user keys.

    All the above use the same control 'username' but have slightly different settings for the key entries or allows for it at least.

    Nelis

    Add comment
    10|10000 characters needed characters exceeded