Background documentationuser_logon Locate this document in the navigation structure

 

The specified DBM operator logs on to the Database Manager program.

Before you log on to the Database Manager, you have to open a session of the DBM server of the database instance you want to manage. You can open this session and log on at the same time (one step logon) or first just open the session and then log on to the Database Manager in a second step (two step logon).

A connection must always be made to the DBM server on the computer of the database instance to be administrated. If the database instance is located on a remote computer, you need to specify the name of the database computer too when logging on to the Database Manager.

Structure

Two Step Logon

You can first open the session with the DBM server and then log on to the Database Manager.

  1. Open a DBM Server session:

    >dbmcli –d <database_name> [-n <database_computer>]

    dbmcli on DEMODB>

  2. Log on to the Database Manager:

    dbmcli on DEMODB>user_logon <dbm_operator>,<dbm_operator_password>

    OK

    dbmcli on DEMODB>

One Step Logon

You can perform both logon steps at the same time by using the DBM option –u | -U. The Database Manager implicitly executes the DBM command user_logon.

Note Note

Note that the option has different meanings depending on whether it is in upper- or lowercase.

End of the note.
Using the DBM Option -u

>dbmcli -u [<dbm_operator>,<dbm_operator_password>] -d <database_name> [-n <database_computer>]

-u: logon with the DBM operator identified by the user name and password

Using the DBM option -U (logon with XUSER)

>dbmcli -U [<user_key>] -d <database_name> [-n <database_computer>]

-U: logon with a user stored in the XUSER file

You can use the XUSER program to store sets of user data as user keys and use them when logging on. User keys for DBM operators can be used successfully only if the operators stored in them have actually been created for the database instance in question (see: user_create).

If you do not specify a <user_key> when using –U, the Database Manager attempts to use the data under the DBMUSR user key.

You should therefore create an XUSER entry with the user key DBMUSR and the data of the DBM operator with the most comprehensive authorizations (see: -us: Creating or Changing XUSER Entries).

Result

dbmcli on [<database_computer>] : <database_name>

In the event of errors, see Reply Format.

Example

Two Step Logon
  1. Call the Database Manager in session mode and connect to the local database instance DEMODB:

    >dbmcli -d DEMODB

    dbmcli on DEMODB>

  2. Log on as operator OLEG with the password MONDAY:

    dbmcli on DEMODB>user_logon OLEG,MONDAY

    OK

    dbmcli on DEMODB>

or:

  1. Call the Database Manager in session mode and connect to the database instance MAXDB on remote computer GENUA:

    >dbmcli -d MAXDB - n GENUA

    dbmcli on GENUA : MAXDB>

  2. Log on as operator OLEG with the password MONDAY:

    dbmcli on GENUA : MAXDB>user_logon OLEG,MONDAY

    OK

    dbmcli on GENUA : MAXDB>

One Step Logon with User Key and Execution of a DBM Command

Call the Database Manager CLI, log on as an operator with the user key OLKEY, connect to the local database instance DEMODB, display the operational state of the database instance:

>dbmcli -U OLKEY -d DEMODB db_state

OK

State

OFFLINE

One Step Logon with Name and Password of a DBM Operator and Execution of a DBM Command

Call the Database Manager CLI, log on as operator OLEG with password MONDAY, connect to the database instance DEMODB, display the operational state of the database instance:

>dbmcli -u OLEG,MONDAY -d DEMODB db_state

OK

State

OFFLINE

More Information

Glossary, Server Permission

Database Administration, DBM Operators