Using the Index Migration Scripts

The migration scripts are the following:

• drminst

• drmrun

• migrate.sql

The migrations scripts drminst and drmrun are obtained from your 8.1 installation. They are located in the $ORACLE_HOME/ctx/migrate directory.

You must copy these scripts into your production environment (pre-8.1). Run these scripts to generate migrate.sql.

The migrate.sql script attempts to recreate the pre-8.1 index as closely as possible. It does so by creating corresponding preferences and attributes and finally the index using interMedia Text 8.1 code.

You then copy migrate.sql to your test environment, edit it appropriately, and run the edited migrate.sql to transform your index.

See Also: For more information on planning your migration, see "Migration Plan" in Chapter 2.

User-Defined Preference Transformation

The migration script attempts to replace all preferences defined with pre-8.1 objects with preferences defined with the renamed 8.1 objects.

For example, if you have a pre-8.1 policy that uses a preference named mydatapref set to the OSFILE object, the migration script creates an 8.1 preference called mydatapref and sets it to use the FILE_DATASTORE object. The 8.1 index is created with the mydatapref storage preference.

Warning for Preferences Based on Obsolete Objects

When an pre-8.1 object or attribute has been made obsolete in 8.1, the migration script issues a warning in the form of a REM statement and creates no corresponding preference. In such cases, you must edit the migration script to reflect the correct replacement preference, if any, for your system.

See Also: For a list of renamed and obsolete objects, see "Preference Objects" in this chapter.

System-Defined Preference Transformations

The migration script replaces pre-8.1 system-defined preferences with 8.1 system-defined preferences.

Unchanged Preferences

When a system-defined preference name has not changed from pre-8.1 to 8.1, the migration script uses the same preference name and attribute. For example, if your pre-8.1 policy used the DEFAULT_LEXER system-defined preference, your 8.1 index will be created with the DEFAULT_LEXER system-defined lexer preference.

Renamed Preferences

When system-defined preference names or attributes have been renamed for 8.1, the migration script replaces the old name with the new name.

Warning for Obsolete Preferences

When an pre-8.1 system-defined preference or attribute has been made obsolete in 8.1, the migration script issues a warning in the form of a REM statement and creates no corresponding preference. In such cases, you must edit the migration script to reflect the correct replacement preference, if any, for your system.

Table of Transformations

The migration script replaces system-defined 2.X preferences with the new 8.1 preferences. The following table lists these replacements:

2.x System-Defined Preference	8.1 Replacement
DEFAULT_DIRECT_DATASTORE	DEFAULT_DATASTORE
MD_TEXT	Obsolete
MD_BINARY	Obsolete
OSFILE	FILE_DATASTORE
DEFAULT_URL	URL_DATASTORE
DEFAULT_NULL_COMPRESSOR	Obsolete
DEFAULT_NULL_FILTER	NULL_FILTER
AUTOB	INSO_FILTER
WW6B	INSO_FILTER
HTML_FILTER	Obsolete
BASIC_HTML_FILTER	Obsolete
DEFAULT_LEXER	DEFAULT_LEXER
VGRAM_JAPANESE	JAPANESE_LEXER
VGRAM_JAPANESE_1	JAPANESE_LEXER
VGRAM_JAPANESE_2	JAPANESE_LEXER
KOREAN	KOREAN_LEXER
VGRAM_CHINESE	CHINESE_LEXER
VGRAM_CHINESE_1	CHINESE_LEXER
VGRAM_CHINESE_2	CHINESE_LEXER
THEME_LEXER	Obsolete
BASIC_HTML_LEXER	Obsolete
BASIC_HTML_SECTION	Obsolete
SOUNDEX	DEFAULT_WORDLIST
NO_SOUNDEX	DEFAULT_WORDLIST
VGRAM_JAPANESE_WORDLIST	JAPANESE_WORDLIST
KOREAN_WORDLIST	KOREAN_WORDLIST
VGRAM_CHINESE_WORDLIST	CHINESE_WORDLIST
BASIC_HTML_WORDLIST	Obsolete
DEFAULT_STOPLIST	DEFAULT_STOPLIST
NO_STOPLIST	EMPTY_STOPLIST
DEFAULT_INDEX	DEFAULT_STORAGE
DEFAULT_LOADER	Obsolete
DEFAULT_TRANSLATOR	Obsolete
FRENCH_STOPLIST	FRENCH_STOPLIST
ITALIAN_STOPLIST	ITALIAN_STOPLIST
SPANISH_STOPLIST	SPANISH_STOPLIST
GERMAN_STOPLIST	GERMAN_STOPLIST

Index Creation Warnings

After attributes and preferences have been created, the migration script attempts to recreate the pre-8.1 indexes from the pre-8.1 policy information.

Policies do not exist in interMedia Text 8.1. In 8.1, you create a Text index as an extensible type of Oracle index. In addition, you can create only a single index per column.

Therefore, the migration script issues a warning as a REM statement if your pre-8.1 environment includes any of the following non-migratable structures:

• multiple policies on a single column

• non-indexed policies

• template policies

• indexes on views

  See Also: For more information on the Text index, see "About the Text Index" in Chapter 5.