Upgrade Commands

Administrator User Guide

Database Upgrade : Upgrade Framework : Upgrade Commands

Upgrade Commands

There is a single upgrade command which will work on a DB or the whole project. If successful, the upgrade number for the DB will be updated.

The suggested syntax is:

DBUP PROJECT TO LATEST

DBUP SYSTEM TO LATEST

DBUP GLOBAL TO LATEST

DBUP DB team/dbname TO LATEST

DBUP DB team/dbname TO LATEST OPTIONAL

The user can replace LATEST with a known upgrade number which can be found using the Q UPGRADE LIST command.

DBUP PROJECT TO 12010101

Internally the code will invoke all upgrades to get to the required upgrade number. If the upgrade number is omitted, then it will be upgraded to the latest.

Any extracts will be refreshed as part of an upgrade when their Master database is upgraded.

Q UPGRADE STATUS

This command lists the current upgrade version of all databases in the project and the upgrade version that the software works on. If databases are on a lower upgrade version than the software, then the "upgrade required" text accompanies the database.

This command lists all the part upgrades ("item:" in the response) organized per upgrade version. I.e. a part upgrade belongs to a particular upgrade version. An upgrade version is the increment we do database upgrades in. The upgrade version is a 8-digit number. So to upgrade a database to a specific upgrade version, the user can give the command

DBUP DB MYTEAM/MYDB TO 12010103

This command will upgrade the database MYTEAM/MYDB to upgrade version 12010103 including the versions 12010100, 12010101, 12010102. I.e. upgrades versions are applied sequentially, and it is not possible to skip any intermediate versions.

If any of the upgrade versions listed, are of the type optional (see below), that is noted by a short remark in the list.

Global Projects

In Global projects, databases must be upgraded at their primary location. The upgrade must be run separately at each project location, since any secondary databases will be ignored.

All descendant extracts must be primary at the same location as their master database, otherwise the database hierarchy will not be upgraded. Such databases can be identified using the ISEXCP attribute. If a database is primary (ISPRIM TRUE), but not all its extracts are primary (ISEXCP FALSE), then it will be omitted from a project upgrade.

Additional syntax is available in Global projects to allow for centrally administered system databases. These cannot be upgraded at the administered location, but must be upgraded at their primary location:

DBUP SYSTEM FOR locnam TO LATEST

DBUP ALLSYSTEM TO LATEST

Where locnam defines the LOCID, name or reference (gid) of a Location element in a Global project. This syntax will be available in ADMIN.

The ALLSYSTEM option in a Global project allows all primary system databases to be upgraded.

Individual satellite system databases may be upgraded using the 'SYSTEM FOR locnam' syntax provided they are primary. If the Global daemon is running, the upgrade will issue Global commands to send such administered system databases back to the administered locations.

It is the responsibility of the System administrator to make sure that updates are run to send all modified databases to satellites; and to relocate extract databases as required back to their original primary locations.

In a Global project, the UPGRADE STATUS query (see below) will also show the status of secondary databases and extract hierarchies. This will help administrators to identify which extracts will need relocating.

Note:

Extract hierarchies which contain secondary extracts cannot be upgraded.

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.