SAP Note 39439 - XUSER entries for SAP DB and MaxDB

Note Language: English Version: 23 Validity:

Valid Since 16.12.2009

Summary
Symptom
This note describes creating XUSER entries for SAP DB Versions 7.3, 7.4.02, and 7.4.03, and as of MaxDB Version 7.5. XUSER entries the database. isp+work, tp, database. The o o o o o contain connection information that is required to log on to Missing or incorrect entries may result in SAP tools (such as R3trans, saplicense) not being able to log on to the following errors may occur:

-709 : CONNECT failed, check SERVERDB -715 : Missing user name or password for connect -807 : Connection down session released -4008: Unknown user password combination -821: the following error message appears when you execute xpu -v: SELECT SDBAADAUPD: SQL error -821 INSERT SDBAADAUPD: SQL ERROR -821

Other terms
XUSER, -709, -715, -807, -4008, -821

Reason and Prerequisites

1. 2. For which operating system user must XUSER entries be stored? Which XUSER entries are required?

Solution
1. For which operating system user must XUSER entries be stored? Store the XUSER entries for each operating system user that wants to use this function. You cannot copy the XUSER entries from one operating system user to the other or from one database server or application server to the other because the data that contains the user name and the server name is decrypted. a) Windows On Windows, the XUSER entries are stored in the registry. For the operating system users <sid>adm and SAPService<SID>, create the XUSER entries mentioned below. As of MaxDB Version 7.5, an operating system user that has administrator rights can store the XUSER entries for SAPService<SID>. To do this, use the XUSER option '-c'; for example: xuser -c <domain>\SAPService<SID> ... b) UNIX/Linux
04.11.2012 Page 1 of 3

SAP Note 39439 - XUSER entries for SAP DB and MaxDB

On UNIX/Linux, the XUSER entries are stored in the file .XUSER.62 in the home directory of the relevant operating system user. Create the XUSER entries mentioned below for the user <sid>adm and, for SAP DB Version 7.4.03 or lower, also create these for the user sqd<sid>. 2. Which XUSER entries are required? XUSER entries are required for the following database users: a) DBA user: SAPR3 (lower than SAP BASIS 6.10) xuser -U DEFAULT -u SAPR3,<password> -d <database_name> -n <database_server> -S SAPR3 -t 0 -I 0 set b) DBA user: SAP<SID> (SAP BASIS 6.10 or higher) xuser -U DEFAULT -u SAP<SID>,<password> -d <database_name> -n <database_server> -S SAPR3 -t 0 -I 0 set c) DBM user: for example, CONTROL. xuser -U c -u CONTROL,<password> -d <database_name> -n <database_server> -S INTERNAL set d) SYSDBA user: for example, SUPERDBA. xuser -U w -u SUPERDBA,<password> -d <database_name> -n <database_server> -S INTERNAL set e) Additional XUSER entry for J2EE: DBM user (for example, CONTROL): xuser -U c_J2EE -u CONTROL,<password> -d <database_name> -n <database_server> -S INTERNAL set You can use the following command to list XUSER entries that are already stored: xuser list You can also use the Database Manager CLI (dbmcli) to change the XUSER entries. For more information, see the SDN at: https://wiki.sdn.sap.com/wiki/x/UC8

Header Data
Release Status: Released on: Master Language: Priority: Category: Primary Component: Released for Customer 16.12.2009 13:55:51 German Recommendations/additional info Installation information BC-DB-SDB MaxDB

04.11.2012

Page 2 of

SAP Note 39439 - XUSER entries for SAP DB and MaxDB

The Note is release-independent

Related Notes
Number 1779540 1630050 1527538 1462332 1375863 1354248 1008828 877349 855619 790879 715701 689611 396492 319835 170297 146003 140431 129352 115284 111774 98559 92935 25591 Short Text Errors in SQLDB_DELUPGSHD phase SAP NetWeaver Landscape Virtualization Management 1.0 - Std SAP NetWeaver Landscape Virtualization Management 1.0 ACC 7.3 - Adaptive Computing Controller Collect. Note ACC 7.2 - Adaptive Computing Controller Collect. Note SAP NetWeaver 7.0 EHP2/Business Suite 7i: Windows/ SAP MaxDB ACC 7.1 PI / Adaptive Computing Controller Collective Note rename user => -4004, Unknown table name LC10, tp error: rtld: 0712-002 fatal error: exiti SAP Web AS 6.40 SR1 Installation on UNIX: MaxDB Migration to SAP DB/MaxDB Networker reports differences with backup sizes Changing the CONTROL user Availability SAP DB on Microsoft Cluster server SAP DB release upgrade to 6.2 Application servers cannot be started Additions upgrade to 4.5B ADABASforR/3 Homogeneous system copy with MaxDB (SAP DB) Additional info.: Upgrade to 4.5A ADABASforR/3 Lock problems due to Row Share locks Remote SQL Server cannot be started Backup actions in DB13 do not function Password change for DBM and DBA users

Attributes
Attribute Database system Value ADABAS D

04.11.2012

Page 3 of