|
|
|
The upgradedb command installs and upgrades one or all databases in the Ingres installation.
Upgradedb triggers upgradefe. For more information, see the upgradefe command description.
If upgradedb cannot upgrade the user interface catalogs for a database, it prints a warning and marks the database operative. You can then either run upgradefe directly on the database, or rerun upgradedb, specifying the database individually with the dbname parameter.
Note: Upgradedb takes a lock on iidbdb. Make sure rmcmd must is shut down (that is, set to zero in CBF) before running upgradedb.
The upgradedb command has the following format:
upgradedb dbname |vnode::dbname[/server_class]|-all [-f product {product}] [help]
Specifies the name of the database (one name only) to be upgraded, and if required, the vnode and server_class, as described in Standard Flags and Parameters.
Causes upgradedb to operate on all databases in the installation that have not already been upgraded to the new release level. With this flag, upgradedb skips any databases already at the current release level.
Note: You can specify either dbname or all, but not both.
Specifies the user interface products for which you want to upgrade the database. Allowable product names are ingres, ingres/dbd, vision, windows_4gl and nofeclients, as described in Standard Flags and Parameters. If you omit this parameter, all Ingres tools for the database are processed.
Note: We advise, in most cases, to use the same -f command to upgrade the database that was used to create it initially. If you are upgrading a pre-6.3 database, the -fingres command upgrades your existing user interface catalogs without creating the catalogs for the Ingres tool products that were new with 6.3 (Vision and Windows 4GL).
Displays command syntax online.