db_reg

You update the registration information of a database instance.

You use this command to update existing registration information, either completely or partially. You can also use this command to make registration information known to the system after it was deleted using db_unreg, that is if the existing database files still exist.

In Microsoft Windows the relevant entry in the Registry, and in Unix the file databases.ini in the directory <independent_data_path>/config, are updated.

Note Note

With this command, you can only switch between versions of the database software that do not require migration of the database instance.

End of the note.

Prerequisites

You have the server authorization InstallMgm.
The database instance is in the OFFLINE operational state.

Structure

db_reg <change_definition> | <re-registration_definition>

<change_definition> :: = [ROOT <dependent_path>] [AUTO | AUTO OFF] [GROUP <user_group>] [USER OFF | USER <user_definition>

<user_definition> :: = <os_user>,<os_user_password>]

<re-registration_definition> :: = DB <database_name> <first_dbm_operator>,<first_dbm_password>]

Options
Option	Description
`ROOT <dependent_path>`	Location of the database version-dependent server software Note If you have performed an upgrade and thus changed the version of the database software, you can use this to tell the system the path of the new software version. Since this also changes the Database Manager CLI version, it is necessary to close all open sessions with the Database Manager (or with the Database Manager GUI if appropriate) before you execute the command. If you execute the command in session mode, you have to explicitly end the Database Manager CLI afterwards. In this way, the next time you access the current database instance, it will be with the new versions of the database software and the Database Manager CLI. End of the note.
`AUTO [OFF]`	For Microsoft Windows only: You can define the service entry `Start-up-type` in the `Control-Panel`. Possible options are `AUTO \| AUTO OFF`. `AUTO`: The `Start-up-type` is set to `automatic`. `AUTO OFF`: The `Start-up-type` is set to `manual`. Under the Unix operating system this parameter is ignored.
`GROUP <user_group>`	For Unix only: You assign your database files to an operating system user group other than the standard group and can thus protect the files from unauthorized access.
`USER <os_user>,<os_user_password>`	For Microsoft Windows only: Operating system user specification The service for starting the database kernel should run under the specified operating system user. `<os_user>`: Name of the operating system user `<os_user_password>`: Password of the operating system user
`DB <database_name> <dbm_operator_name>,<dbm_operator_password>`	Data of the database instance that is supposed to be registered again. Specify the database name, the name and the password of the first DBM operator.

Result

OK

In the event of errors, see Reply Format.

Example

Changing the Software Version in Command Mode

Call the Database Manager CLI, log on as user DBM with password DBM, connect to the database instance DEMODB, change the current software version to version 7.6, which is stored in C:\Program Files\sdb\76:

>dbmcli -u DBM,DBM -d DEMODB db_reg ROOT "C:\Program Files\sdb\76"

OK

Changing the Software Version in Session Mode

Call the Database Manager CLI, log on as operator DBM with the password DBM, connect to the database instance DEMODB:

>dbmcli -u DBM,DBM -d DEMODB

Change the software version to version 7.6, which is stored in C:\Program Files\sdb\76:

dbmcli on DEMODB>db_reg ROOT "C:\Program Files\sdb\76"

Exit the Database Manager CLI:

dbmcli on DEMODB>exit

OK