The SAP MaxDB instance requires several options for a user to successfully access a database instance. These required pieces of information must be passed in to the SAP MaxDB tool being used to access the database instance. The SAP MaxDB software includes the xuser tool for simplifying the specification of many required options to SAP MaxDB tools. The xuser tool allows you to predefine and save user data. Once this data has been saved, it can be used when you call the DBMCLI or other tools requiring user options. This predefined user data is stored in a user key (User_Key). An individual user can manage and maintain several user keys for the same or multiple databases. Each key includes a combination of options including username/password, database name as well as database server name.
The SAP MaxDB Recovery Kit requires a valid User_Key for each database instance under protection. This User_Key must be created and accessible by the OS User that owns the database instance. The user information specified for each User_Key must be for a DBM operator with the following permissions:
- DBStart
- DBStop
- DBInfoRead
- ParamRead
The User_Key can be generated using the command:
xuser –b <file name>
where <file name> is the name of a file containing the valid XUSER entries as follows:
| USERKEY | Unique name for the User_Key |
| USERID | User name of the dbm operator |
| PASSWORD | Password of the user |
| SERVERDB | Name of the database instance that this key will refer to |
| SERVERNODE | The name of the server where the database is running (this should be the DNS or host file entry for the LifeKeeper protected IP) |
| SQLMODE | This determines what SQL dialects are compatible |
| CACHELIMIT | This determines the cache limits for a given session |
| TIMEOUT | Time in seconds before terminating an inactive session (-1 is the default) |
| ISOLATION | Determines the isolation level used for locks that affect the user (-1 is the default) |
| DB_LOCAL | Specifies the database locale |
Refer to the SAP MaxDB User Manual for more information on parameters. Once proper entries have been specified, use the xuser tool to generate the.XUSER.62 file in the OS User home directory. A sample XUSER file is included below containing two keys (an entry must exist for the DEFAULT User_Key).
DEFAULT
NULLDB
NULLDB
NULLDB
LKIP.example.com
INTERNAL
-1
-1
-1
my_locale
LK_USERKEY
LKDBMOPER
LKDBMPASSWD
DB1
LKIP.example.com
INTERNAL
-1
-1
-1
en_US
This example XUSER file specifies that two user keys be created, DEFAULT and LK_USERKEY. Once the xuser tool has been run to generate the User_Key(s), the file specified for use by the xuser tool should not be deleted.
Post your comment on this topic.