DISC

Contents | What's New | Quick Links

 

OAHELPER

Introduction

Software Installation

Concepts and Design

Designing Applications

Omnidex Environments

SQL Reference

Omnidex API's

Utilities

Interfaces

Performance Guide

Troubleshooting Guide

Appendix

 

 

Generate an Environment File

 

OAHELPER reads native data files and generates an environment catalog source file. In many cases, you can simply compile this source file into a usable environment catalog.

Run OAHELPER, entering at the system prompt the command appropriate to your operating system:

UNIX:

oahelper

OpenVMS:

oahelper

MPE/iX:

RUN OAHELPER.OA. DISCACCT

where DISCACCT is the account in which OAHELPER is located.

Oracle Numeric Datatypes

Generate an Environment File

Generate an Installation Script

OAHELPER

OACOMP

OADECOMP

DBINSTAL

Utility Reference

OAHELPER displays the following menu:

1. Generate Environment Source file from a database.
2. Generate DBINSTAL Indexing/Build script from existing installation.
3. Calculate tidmap using Quick Estimate method.
4. Calculate optimal tidmap using sequential scan method.
5. Generate Environment Source file existing installation.
6. Generate Migration scripts from existing installation.

E to Exit oahelper.

Enter menu number, ? for help, or 'E' to Exit:

Select option 1. Generate Environment Source file from a database. OAHELPER displays a menu of databases from which it can generate an environment source file.

Generate an environment file from:

1. Oracle
2. Sybase
3. Image
4. Informix
5. ODBC
6. DB2

Enter choice or ? for help:

Select a database. OAHELPER prompts for the following information about the data files:

Database Name

Enter the name of the database to use to generate the DATABASE statement of the environment source file.

Table list (table, owner.table, or *)

Enter the names of tables defined in the database separated by commas as shown in parentheses beside the prompt. To include all tables created for the database, enter an asterisk ( * ).

All the tables you include here must be accessible to the user you declare at the Default User name: prompt. If any one user cannot access all the tables you want accessible to OmniAccess, consider creating several environment catalog files, each with a different set of tables from the same database. Do not use a table in more than one environment catalog.

Environment logical name [ORDERS_ENV]

Enter a logical name to assign to the environment through the ENVIRONMENT statement. The name MUST BEGIN WITH A LETTER, A-Z (case insensitive) and may contain up to 32 characters including letters, numbers and allowed special characters.

Database logical name [ORDERS]

Enter the name you want to use to refer to the database through OmniAccess applications. The name MUST BEGIN WITH A LETTER, A-Z (case insensitive) and may contain up to 32 characters including letters, numbers and allowed special characters.

Database physical name [orders]

Enter the physical path to the database. This information declares a PHYSICAL location for the database in the environment catalog.

Index prefix [orders]

Enter the physical path and root name for any indexes created when OMNIDEX is installed on the compiled environment catalog. For TurboIMAGE, do not enter any information here. The OMNIDEX indexes will be created in the group and account of the TurboIMAGE database.

Default User name

Enter the name of a database user that can access all the tables you declared at the Table list (table, owner.table, or *): prompt. This, and the Default password: below, form the basis of the USERCLASS statement.

Default password

Enter the password of the user declared at the Default User name: prompt.

Environment source to generate [orders.src] (or / for screen output)

Enter the name you want to assign to the environment source file that OAHELPER will create.

OAHELPER creates the environment source file.

 

top

Dynamic Information Systems Corporation - Omnidex Version 3.8 Build 6 J15.03-Copyright © 2003

DISC | Documentation Home