db_reg

Use this command to update the registration information of a database.

You can update the existing registration information, either completely or partially.

You can also use this command to make registration information known to the system again after it was deleted using db_unreg, provided that 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 <global_data_path>/config, are updated.

Note Note

You can use this command only when the new version of the database software does not require the database to be migrated .

End of the note.

Prerequisites

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

Structure

db_reg <change_definition> | <re-registration_definition>

<change_definition> :: = [ROOT <installation_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 <installation_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, use this option to provide 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 Database Manager CLI (or with Database Studio if appropriate) before you execute the command. If you execute the command in session mode, explicitly end Database Manager CLI afterwards. In this way, the next time you access the current database, you will use the new versions of the database software and the Database Manager CLI program. 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: Use this option to assign your database files to an operating system user group other than the standard group and 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 that is supposed to be registered again. Specify the database name, as well as 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 Database Manager CLI, log on as the user DBM with the password DBM, connect to the databaseDEMODB, change the current software version to version 7.7, which is stored in C:\Program Files\sdb\77:

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

OK

Changing the Software Version in Session Mode

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

>dbmcli -u DBM,DBM -d DEMODB

dbmcli on DEMODB>

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

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

Exit Database Manager CLI:

dbmcli on DEMODB>exit

OK