This appendix discusses the compatibilities of various releases of Ingres with the current release.
Note: All nodes accessed by Ingres Star must be running Release 6.4 or higher.
It also discusses using the upgradedb and upgradefe utilities with Ingres Star.
|
|
|
Use the upgradedb and upgradefe utilities to update a Release 6.4 Star database to the current release.
The following sections discuss Ingres Star-specific usage of these conversion utilities. For complete details on using upgradedb and upgradefe, see the Migration Guide.
|
|
|
Upgradedb converts distributed databases. You can specify the distributed database name with or without the /star flag.
You can run upgradedb regardless of whether the Star Server is running. However, if you use upgradedb without a Star Server, all tools catalog upgrades are skipped, and you must later run upgradefe through a Star Server to upgrade the tools catalogs.
Upgradedb cannot be used on coordinator databases.
|
|
|
The upgradedb command for distributed databases has the following format:
upgradedb distdbname [/star] | -all [-f product {product}]
Specifies the name of the distributed database to be converted.
(Optional) Designates the database as distributed. This parameter cannot be used if -all is used instead of a distdbname.
Specifies that all databases that have not been converted to the current release are to be upgraded.
(Optional) Indicates that one or more Ingres tools catalog product names are specified. A product name must be specified after -f.
Default: No -f flag, which means that all authorized Ingres tools catalogs that are legal for this installation are upgraded (if they exist) or created (if they do not exist). These are the products that the authorization string indicates the installation supports.
The -f flag options are as follows:
Specifies to upgrade (if they exist) or create (if they do not exist) the specified product tools catalogs. Product names are identical to those used with the createdb command.
Bypasses upgradefe processing (that is, no tools catalogs are upgraded). This special name cannot be used with any other product name.
Specifies one or more product names. Names may include:
|
|
|
This command upgrades distributed database mystardb and assures that all legal tools catalogs are upgraded (or created if they do not already exist). This is the most common use of upgradedb.
upgradedb mystardb
or
upgradedb mystardb/star
This command upgrades distributed database mystardb and bypasses upgrade operations on any tools catalogs that may exist in the database:
upgradedb mystardb -f nofeclients
or
upgradedb mystardb/star -f nofeclients
This command upgrades all databases in the installation, including any distributed databases that may reside in the installation. It upgrades only the core product tools catalogs (or creates them if they do not exist):
upgradedb -all -f Ingres
This command upgrades all databases in the installation, including any distributed databases that may reside in the installation. It upgrades or creates the tools catalogs for all products that this installation is authorized to use:
upgradedb -all
|
|
|
Upgradefe converts or creates tools catalogs for any of the distributed Ingres products. These include Ingres, Ingres/DBD, and Ingres Vision. You may invoke upgradefe directly, using the command syntax described below. Upgradefe is also invoked indirectly by upgradedb.
A Star Server must be running in order to run upgradefe on a distributed database.
Upgradefe cannot be used on coordinator databases.
|
|
|
The upgradefe command for distributed databases has the following format:
upgradefe distdbname/star {product}
Specifies the name of a distributed database.
Indicates that the database requires a Star Server because it is a distributed database.
Specifies one or more product names. Names may include:
|
|
|
upgradefe mystardb/star
Assure that the tools catalogs required for the OpenROAD product for distributed database mystardb are upgraded (or created if they do not already exist):
upgradefe mystardb/star windows_4gl