cancel
Showing results for 
Search instead for 
Did you mean: 

Missing xuser entries for MaxDB

08-18-2006 11:46 AM
2087 views 5 comments Go to solution
0 Likes
SAP Managed Tags
Subscribe

Hello *,

I installed the latest ABAP edition of the SAP NetWeaver Sneak Preview on a Windows 2000 machine. I just had a look into the xuser configuration file, using

xuser -U DEFAULT list

This command showed me just one entry (key = DEFAULT and user = SAPNSP), but according to SAP note #39439 there have to be at least five other one. Or do I have to call xuser as <sid>adm in order to see all entries? What to do if they're still not there? Is it recommended to add them by hand?

Regards, Lars

0 Likes

Accepted Solutions (1)

Accepted Solutions (1)

former_member229109
Active Contributor
0 Likes

Hello Lars,

-> Did you run 'xuser list' command?

< run this command as <systemSID>adm user >

If you will skip the option::

-U user_key user key

string (max. 18 characters), default 'DEFAULT'

It will give you all Xuser connection information:

  • list user connection information (default all user keys)

  • ignores all options, except -U

You could find more information about xuser tool:

  • Run command 'xuser -h'.

  • At link - MaxDB documentation:

http://help.sap.com/saphelp_nw04s/helpdata/en/07/595f51b1889b478869e338198171b5/frameset.htm

Glossary -> XUSER ( under Database Tools )

  • SAP note: 767598 Available documentation

Thank you & best regards, Natalia Khlopina

Former Member
0 Likes

Hello Natalia

I had to run the command as user SAPServiceNSP to see all entries. Running it as an administrator or <SID>adm just shows a DEFAULT profile. But in this case, xuser claims that the password and some other values are unspecified. But in the DEFAULT profile for the SAPServiceNSP user these values are set correctly.

Does xuser distinguish between operating system users? I mean, does every user have its own DEFAULT profile or is there just one for all users? If the latter is the case, why does xuser claim, that some values are unspecified when running the command as "wrong" user?

Kind regards,

Lars

former_member229109
Active Contributor
0 Likes

Hello Lars,

-> What is your database version?

-> Please update with output of 'sdbregview -l' command.

*Does xuser distinguish between operating system users?

Yes xuser data could be different b/w the system users.

For example, you have the two R/3 SAP systems running on the same

server - NSP & NSD, the users nspadm & nsdadm

*I mean, does every user have its own DEFAULT profile or is there

just one for all users?

More information could be found in the note SAP note 39439.

For 'USERKEY : DEFAULT' xuser data < run 'xuser list' >

should be the same for the users nspadm and SAPServicensp on Windows server.

*If the latter is the case, why does xuser claim, that some values are

unspecified when running the command as "wrong" user?

Could you be more specific, please. Which command you was executed?

And with what user did you logon

Thank you & best regards, Natalia Khlopina

Former Member
0 Likes

Hello Natalia,

I'm using MaxDB 7.6 (as it comes with the Sneak Preview):

DB Analyzer c:/sapdb/programs 7.6.00.18 32 bit valid

Server Utilities c:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7300 c:/sapdb/programs 7.3.00.54 valid

Base c:/sapdb/programs 7.6.00.18 32 bit valid

Redist Python c:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7301 c:/sapdb/programs 7.3.01.19 valid

JDBC c:/sapdb/programs 7.6.00.16 valid

Messages c:/sapdb/programs MSG 0.3017 valid

ODBC c:/sapdb/programs 7.6.00.18 32 bit valid

Database Kernel c:/sapdb/nsp/db 7.6.00.18 32 bit valid

Loader c:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7104 c:/sapdb/programs 7.1.04.45 valid

PCR 7600 c:/sapdb/programs 7.6.00.09 32 bit valid

SQLDBC c:/sapdb/programs 7.6.00.18 32 bit valid

SQLDBC 7600 c:/sapdb/programs 7.6.00.18 32 bit valid

PCR 7403 c:/sapdb/programs 7.4.03.40 32 bit valid

Regarding the DEFAULT profile for different Windows users: running "xuser -c Administrator list" produces the following output:

XUSER Entry 1

-


Key :DEFAULT

Username :SAPNSP

UsernameUCS2:S.A.P.N.S.P. . . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:<unspecified>

Dbname :<unspecified>

Nodename :<unspecified>

Sqlmode :<unspecified>

Cachelimit :-1

Timeout :-1

Isolation :-1

Charset :<unspecified>

Running "xuser -c SAPServiceNSP list" produces this:

XUSER Entry 1

-


Key :DEFAULT

Username :SAPNSP

UsernameUCS2:S.A.P.N.S.P. . . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :NSP

Nodename :xxxxx

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

-


XUSER Entry 2

-


Key :c

Username :CONTROL

UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :NSP

Nodename :xxxxx

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

-


XUSER Entry 3

-


Key :c_J2EE

Username :CONTROL

UsernameUCS2:C.O.N.T.R.O.L. . . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :NSP

Nodename :xxxxx

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

-


XUSER Entry 4

-


Key :w

Username :SUPERDBA

UsernameUCS2:S.U.P.E.R.D.B.A. . . . . . . . . . . . . . . . . . . . . . . . .

Password :?????????

PasswordUCS2:?????????

Dbname :NSP

Nodename :xxxxx

Sqlmode :SAPR3

Cachelimit :-1

Timeout

Isolation

Charset :<unspecified>

So there is obviously a difference in the xuser entries in regard to the Windows user, especially in the DEFAULT entry.

I guess the Web AS (ABAP) uses the DEFAULT entry from user SAPServiceNSP to connect to the database. So if one would like to change that connection information fpr the database, one has to do it for user SAPServiceNSP and not for any other user. Right? I mean, it's important to know, which entry from which Windows user has to be changed in such a case.

Regards, Lars

former_member229109
Active Contributor
0 Likes

Hello Lars,

-> XUSER entries are stored separately for each operating system user.

XUSER entries are stored in the registry in Microsoft Windows, and

in the file system in UNIX/Linux.

-> The xuser data should be the same & set correctly for the

users 'nspadm' and 'SAPServiceNSP' on Windows server

( Not only for the DEFAULT user ) .

The xuser data have the correct user/pwd/server/database name

information from the connected to the NSP system database.

More information could be found in the note SAP note 39439.

As you know, as of Version 7.5, you must only maintain correctly the Xuser

entries for the users <sid>adm (UNIX/Windows) and SAPService<sid> (Windows only).

-> If you are going to change the password of the users in the database of the NSP

system, SAP note 25591, the Xuser data must be updated on all instance servers

with the new values as described in Note 39439.

< for the users 'nspadm' and 'SAPServiceNSP' on Windows servers, and for the

'nspadm' on UNIX. >

You could find more information about xuser tool:

MaxDB Library -> Tools -> Utilities -> XUSER

Thank you & best regards, Natalia Khlopina

Answers (0)