There are several good reasons to upgrade from an Omnidex version 4.x installation to a 5.x installation.

• Faster Omnidex Index build times due to the merging of MDK and ASK indexes.
• Easier to maintain Omnidex Grid Environments with Grid aware Explain Plans
• Easier Omnidex Environment setup and maintenance using the Omnidex Data Defintion Language and OdxSQL.
• Improvements in the Sample and Random selection of records.
• Automatically de-dup records on selection.
• Cached Qualifications to improved the speed of drill down counts.
• PowerSearch for synonyms, miss-spellings, transpositions, plurality, etc.
• Autocomplete suggestions of words as they are being typed.

• NsAdmin is no longer supported and the replacement interface is not available in the Omnidex 5.1 version.

The best way to currently review all the upgrade notes is to start at the older releases and read through to the newer releases. Even if you are already on 5.0, you should review the upgrade notes on going from 4.x to 5.0 to see all the changes to the Omnidex product.

Upgrading Versions 4.x to 5.0

Upgrading Versions 5.0 to 5.1

Upgrading Versions 5.1 to 5.2

• Modify 4.x environment source to test environment locations (table physical, database index_prefix, etc.)

• Compile environment source using oacomp 5.1

• Run dbinstal install only (no build) script

• Run OdxSQL and do the following steps (assume current.env)

• Use Odxsql connect to .env environment

os> odxsql current.env

• Use OdxSQL to extract the new DDL from the current.env. This will include both the metadata from the Environment Catalog and the Omnidex indexing information.

odxsql> extract DDL to myddl.sql 

• Compile the extracted DDL to create a new Omnidex Environment with the XML format.

odxsql> use myddl.sql

• Connect to XML environment

odxsql> connect myddl.xml

• Build the new indexes

odxsql> update indexes