The XUSER database tool is used to define XUSER entries for users and to store them under a key name. You can define XUSER entries for database users and DBM operators. XUSER entries make it easier for database tools (such as the Database Manager CLI) to connect to the database instance. XUSER can also be used in SAP systems.
We recommend that you only use XUSER in production systems if you have a sound knowledge of databases and operating systems.
XUSER is a command line tool and can be used on all operating systems supported by the database system.
XUSER is part of the MaxDB software, which you can download from the MaxDB web site (see Download and Installation Profiles).
For further information about the database system, see the documentation Concepts of the Database System and the Glossary.
XUSER entries consist of a user name and user password as well as other options. The user data and options are stored separately for each operating system user. Authorizations at file system level ensure that these entries can only be used and changed by the operating system user who created them.
The XUSER program enables user data to be stored for various tasks and used for logging on. An operating system user can define up to 32 user keys. If several database users work with the same computer but log on with different user names, the user data can be separated in this way.
Creating or Changing XUSER Entries
Logging On with an XUSER Entry
Displaying the Data in XUSER Entries
Some database tools (Loader and Database Manager GUI) and applications that use the ODBC interface (such as SQL Studio) cannot access XUSER data.
The purpose of XUSER is not to manage database users and DBM operators, but rather the XUSER entries for these users. You can only access a database instance using a database user stored in an XUSER entry if this user has actually been created for this database instance. Similarly, you can only manage a database instance using a DBM operator stored in an XUSER entry if you have defined this operator when the database instance was created.