Print this page.  If your browser doesn't allow JavaScript, right-click this page and choose Print from the popup-menu.        
Upgrade to Mimer SQL 9.1
Categories: Database administration, Migration
Introduction

Often, when a new version of Mimer SQL is released, you need to upgrade existing databases to the new version. Usually, this is because of updates made in the data dictionary structure. The upgrade procedure can be divided into two parts: upgrading the database and upgrading the application database access.

Note that if you are creating a new database, upgrading is not an issue.

Description

The upgrade program, “sdbgen –u” can be used for Mimer SQL version 7 or version 8 databases.

The upgrade program will rebuild the entire system databank, SYSDB. The new file name will be SYSDB9.

The rebuild process will do the following operations:

  • Create the following schemas: FIPS_DOCUMENTATION, INFORMATION_SCHEMA, INFO_SCHEM, MIMER.


  • Convert the old transaction handling databank (TRANSDB), transaction logging databank (LOGDB) and work databank (SQLDB). The old contents in these databanks are deleted, and the entire log is dropped.


  • Transfer all information from the old system databank (SYSDB) to the new. Data is moved and converted according to the new layouts for the system base tables.


  • Convert and re-build bitmaps and root pages for all user databanks (and shadows). Note! If a databank (or shadow) cannot be opened, e.g. the file cannot not be found at the location stored in dictionary, an error message is displayed. In this situation the databank can be dropped later on or the upgrade program can be executed once again when the problem is solved.


In addition, for version 8.1 databases or older versions, the following operations will be performed in the system databank (SYSDB):

  • Eliminate any duplicate access privileges encountered.


  • Transform the programs MIMER_BR, MIMER_SC, and MIMER_SW to the equivalent BACKUP, STATISTICS and SHADOW privileges.


  • Give generated names to all constraints, such as primary keys, foreign keys and check clauses.


  • Update COLUMN_PRIVELEGES so that primary key updates will be allowed.


  • Mark all indexes as inconsistent so they will be rebuilt.


  • Quote any newly reserved word used as names for objects created earlier.


  • Drop synonyms and views that are found to be defined on any of the old system base tables or views. The reason for this is that the old base tables no longer exist and the views are changed. Any use from application or scripts be changed.


  • Remove any privileges granted on old system base tables or views. SYSADM has SELECT privilege on the new base tables. PUBLIC has SELECT privilege (with grant option) on all system views, so no further granting is required.


  • Rebuild any 'index' table for each user databank with one or more
    VARCHAR columns.


Linking Mimer7 Level2 applications with Mimer SQL

If a Mimer7 application is to be used with a Mimer SQL version 9 database server, there are different approaches to establishing communication:

  • On Unix we recommend to connect to the database using the client/server interface locally, i.e. the Mimer7 client and Mimer SQL version 9 server are on the same node. See How To Use Mimer V7 Applications with Mimer SQL V8 on Unix. (The procedure for using a version 8 or version 9 Mimer SQL server is the same).


  • On VMS use the command procedure, MIMBUILD8.COM in order to build the V7 components "on top" of an existing V8 installation. See How To Use Mimer V7 applications with Mimer V8 on OpenVMS. The procedure for connecting to a Mimer SQL 9 server is following the same principle, but the tolls and details are not yet availabale.



Techniques

To upgrade from Mimer SQL 7 or 8 to version 9, the sdbgen program should be used. The database name should be given as a parameter to the sdbgen program (or be defined in MIMER_DATABASE) as shown below. The database name is presumed to be registered on the system, e.g. found in the sqlhosts file:

sdbgen -u database name

Recommendation

We recommend that you run the Update Statistics SQL command on the whole database after upgrading the database. If coming from version earlier than 8.2 the secondary indexes are marked as “inconsistent” after the upgrade procedure and the index lookup only feature cannot be used.


Benefits

Once you have upgraded your database to Mimer SQL version 9, you can use new version 9 features. See Mimer SQL 9 for details.

Last updated: 2003-12-15

 

Powered by Mimer SQL

Powered by Mimer SQL