Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Maxdb Imp Documentation

Maxdb Imp Documentation

Ratings: (0)|Views: 213|Likes:
Published by venky151

More info:

Published by: venky151 on Dec 13, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





User in a SAP MaxDB database
SAP MaxDB knows three different kinds of users:
database system administrator (SYSDBA user)
database manager operator (DBM operator)
database user 
Database system administrator (SYSDBA user)
This user is the first database user. It is created when the database is installed. In eachSAP MaxDB database exactly one user of type database system administrator does exist.The database system administrator has the permissions of a database administrator (user mode DBA) and additionally of a Database Manager operator (DBM operator).Therefore it is the user with most permissions.User name and password can be specified during the installation.
Database Manager operator (DBM operator)
Users of type DBM are used for maintenance issues performed with the DatabaseManager (DBMGUI or DBMCLI).DBM operators differ from database users as they don't have permissions to execute SQLstatements. Therefore you cannot logon to SQL Studio with a DBM operator.You can create several users of type DBM. During the database installation the so calledfirst DBM operator is created. User name and password of the first DBM operator arespecified during the installation.
Database user
Database users access the data in the database using SQL statements. They do not perform administrative tasks. Therefore they cannot logon to the Database Manager.The work processes of an SAP system always connect as database user SAPR3 resp. as of SAP Basis 6.10 as user SAP<SID> to the database. back to top
User in the configuration files
For each database the DBM operators and the database system administrator are stored infile <SID>.upc (upc means
User Profile Container 
). This file is located in directory<independent_data_path>/config. A copy of this file is located in the run directory and iscalled dbm.upc. Both files are binary files.Users which are stored in file <SID>.upc can logon to the DBM Server and executeadministrative tasks. The DBM Server connects to the database.
To determine which users are stored in the upc-file, you can use the following command:
dbmcli -d <database_name> -u <DBM_operator>,<password> user_getall 
For each user the property USERTYPE is stored in file <SID>.upc.You can show this property using the following command:
dbmcli -d <database_name> -u <DBM_operator>,<password> user_get <user_name>
Some administrative tasks can be executed using the Database Manager whithoutspecifying the actually needed user (e.g. load_systab). This works only if the needed user is stored in file <SID>.upc.If such a command is executed, the DBM Server checks if a user with the neededUSERTYPE is stored in the upc-file. If this is the case, this user information is used toexecute the statement. If no such user is stored, the DBM Server returns an error messageand you have to specify the needed user.When load_systab is executed with options
-u<database_system_administrator>,<password> -ud <domain_password>
thisinformation is stored in the upc-file.Example:
dbmcli -d <database_name> -u <DBM_operator>,<password> load_systab -u<database_system_administrator>,<password> -ud <domain_password>
For a SAP liveCache you have to store the SAP user in the upc-file (if it is not user SAPR3 with default password). This entry is needed to perform special actions likeexec_lcinit (e.g. to initialize or start the SAP liveCache). The entry is created using thefollowing command:
dbmcli -d <database_name> -u <DBM_operator>,<password> user_sap<user>,<password>
OS User as which the SAP System is running
Unix / Linux
On Unix/Linux the SAP System is running as user <sid>adm. This user should bemember of database administrator group sdba.
On Windows the SAP System is running as user SAPService<SID>. As of SAP MaxDBversion 7.7 this user has to be member of the local group "SDB Operators" which is thespecial operating system user group for SAP MaxDB.You can check this using the following command:
net localgroup "SDB Operators" 
It is possible to store user information (e.g. name, password, database name, ...) in aspecial file (.XUSER.62 in the HOME directory of the OS user - Unix/Linux) resp. in theregistry (Windows). The data can only be accessed by the OS user who owns the data.When you want to connect to the database, you only have to specify the defined user key.You don't have to enter user and password anymore.The SAP system uses this concept for the authorization of the work processes. Thereforethe XUSER data must be entered for the user <sid>adm (Unix/Linux/Windows) and for the user SAPService<SID> (Windows) as which the SAP system is running.
Handy Hint
As of WebAS 6.40, the SAPService<SID> user has the restrictive right "Deny logonlocally". Before you can log onto the system locally as SAPService<SID>, you mustremove this right for this user and then add it again after you have maintained theXUSER data. To do this please choose 'Start' - 'All Programs' - 'Administrative Tools' -'Local Security Policy'. On the left hand side please choose 'Local Policies' - 'User Rights Assignment'. In the policy list choose entry "Deny logon locally" and open thedialog 'Properties' from the context menu (right mouse button). Now you can see allusers who are assigned to this policy and can remove or add users.Alternatively you can maintain the XUSER data of user SAPService<SID> while youare logged on as the administrator by using XUSER option
-c <account name>
Example:xuser ...
-c <domain>\SAPService<SID>
For SAP liveCache the XUSER data is not needed, when the central authorisation is used.In this case the user information is stored in tables DBCON and DBCONUSR of theSCM database.In case of connect problems of an SAP system (e.g. R3trans, the work processes, ...) youshould always check the XUSER data.To maintain the XUSER data you can use Database Manager CLI (DBMCLI) or XUSER.How the XUSER entries should look like for an SAP system is described in note 39439.  back to top 
These are the main functions of command line tool XUSER:Get a list of all XUSER entries:
 xuser list 

Activity (5)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
vikasm4u liked this
vipinsagar liked this
asharma2359 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->