Differences

This shows you the differences between two versions of the page.

--- programs:dbinstal:intro [2009/07/17 02:29]
admin
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Dbinstal Index Specification and Index Building ======
-DBINSTAL is a server based console utility that is used to install and build the Omnidex indexes on Omnidex Environment Catalog files. For Omnidex XML Catalogs, the Dbinstal functions are called directly by the Omnidex Administrator (OdxAdmin).  Dbinstal can not be used directly to specify or populate indexes on an Omnidex XML Catalog.
-Indexing options are specified during the DBINSTAL installation process and then built with the DBINSTAL Build command.
-It is important to note that the two processes, installing the indexes and building the indexes, are two completely separate processes that do not necessarily have to be performed at the same time. This means that there are times when the indexes must be reinstalled but not necessarily rebuilt after upgrading to a more recent version of Omnidex.  Please refer to the Release Notes to determine if indexes need to be re-installed or re-indexed after an version upgrade.
-There are also times when the indexes must be rebuilt but not necessarily reinstalled, like when deferring indexing to a batch process in an update application. The existing index installation is still valid but the indexes are built and rebuilt during periodic batch processes.
-The actual process of the Build command is to serially read the specified table and unload the appropriate columns of data into a special Omnidex unload file. This file is then read and the physical Omnidex indexes are populated with the internal Omnidex index structure from the unload file. Omnidex has options to generate multiple indexes and uses very high-speed processing techniques to minimize the actual indexing time.
-For the initial index installation and build, DBINSTAL should be run interactively. Manually define the MDK and ASK indexes for each table and then run the Build command to populate the index files. After this is complete, run OAHELPER to generate an installation batch script. This script allows the indexes to be re-installed and re-built in the future by simply executing the script. This installation script can be easily modified using any text editor.
-If DBINSTAL prematurely stops on UNIX systems (for example, results in a core dump), particularly on HP-UX systems, then run DBINSTAL again for each indexing operation, or try reducing the memory allocation through DBINSTAL's BUF=n option. This problem is due to an anomaly in some versions of UNIX. A DISC work-around is in progress.
-===== Running Dbinstal =====
-DBINSTAL is an Omnidex executable that can be run by entering Dbinstal at a command window prompt.
-  os> dbinstal
-It can optionally take two different command line arguments:
-  - An Omnidex Environment Catalog filespec
-  - Dbinstal index installation or index build script
-Running Dbinstal with an Omnidex Environment Catalog
-  os> dbinstal c:\omnidex\demo\orders.env
-Running Dbinstal with an installation and/or build script
-  os> dbinstal < orders.in
-===== Commands =====
-Operational Commands
-The following is a list of commands that can be entered at the DBINSTAL Cmd: prompt during program operation.
-System Commands - Execute a system command from within DBINSTAL. See below for more details.
-^ Command ^ Description ^ Options ^ Option Explanation ^
-| B | Build Omnidex indexes | [;buf=n][;nomr][;status]  | ;buf=n sets the buffer size where n is the number of MegaBytes, 2 - 512. |
-| |  | ;nomr | |
-| |  | ;status | outputs indexing status information to a file. |
-| E |  Exit to the Environment prompt. | ||
-| H or ? | Display help information. | ||
-| I | Specify Indexes | | Specifies or replaces an existing Omnidex index. |
-| INDEX | Build Omnidex indexes - same as the B-Build command. |||
-L - (Letter L) Display a range of keys to the screen or a file.
-M - Enable or disable bitmap merges for an MDK table
-MI - Display a map of installed indexes.
-P=parentname - Link a child table to its parent by entering P=parentname at the Link column #: prompt.
-QUIT - Immediately exit DBINSTAL. Can be passed at any prompt.
-Set UTIL {ON|OFF} - Enable or disable diagnostic info display
-T - (Letter T) Load a translation table.
-V - (Letter V) Display version information and existing installation version information.
-X[!] - (Letter X and optionally an exclamation point) X loads an excluded words list.
-X! clears an excluded words list.
-Z[!] - (Letter Z and optionally an exclamation point) Zap the existing index files.
-Z erases the contents of the index files except for a portion of the root index file.
-Z! deletes the physical index files from the operating system.
-System Commands
-System commands can be executed from within DBINSTAL by preceding them with one of the following characters:
-! (exclamation point) executes the command as typed
-: (colon) upshifts the command before executing
-$ (dollar sign) upshifts the command before executing
-Syntax:
-{! | : | $} command_string
-For example, on the UNIX operating system:
-Entering !ls at the DBINSTAL Cmd: prompt would list the files in the current directory.
-Entering $ls would return a command not found error, because DBINSTAL would upshift the command before passing it to the shell.
-sun3> [/users/test]$ dbinstal orders.env
-OMNIDEX DBInstal, Release 3.7.0 Fri Nov 30 2001 13:04:52
-(c) Copyright 1981-1998 Dynamic Information Systems Corporation
-Cmd: !ls
-orders.env orders.in orders.src
-Cmd: :ls
-sh: LS: not found
-Cmd: $ls
-sh: LS: not found
-===== Buffer Size =====
-Use the DBINSTAL Build BUF=n option to allocate an appropriate amount of memory for DBINSTAL indexing operations.
-Determining the optimal BUF=n size is best done by trial and error on a subset of the database. Monitor the number of sort segments required (displayed by DBINSTAL). The maximum is 2048 segments. Vary the BUF=n size on the database subset, and use the BUF=n value that provides a sort segment size closest to 1024.
-Use 8 Mbytes of BUF=n space for each Distributed Index (;DI) processed. If a Build option of @9 is used, then the BUF=n size should be set to 72 (8 * 9).
-===== Indexing Child Tables =====
-A child table can be indexed as a stand-alone table in its own domain, in its parent's domain, as a parent and child, or any combination of these. With all of these options, Omnidex can always ensure the best query performance.
-Child tables are defined with foreign key constraints in the Omnidex environment catalog. This causes DBINSTAL to issue a Link Column prompt when defining indexes for a child table.
-To index a child table in its own domain, without indexing it in its parent's domain, simply enter a forward slash at the Link Column prompt:
-  Table name? ORDERS
-  Link Column 1: /
-To index a child only in its parent's domain, enter the column name that links it to its parent or enter P=parentname, at the Link Column prompt:
-  Table name ? ORDERS
-  Link Column 1: ACCT
-or
-  Link Column 1: P=CUSTOMERS
-  Table will be indexed in the domain of CUSTOMERS
-  Link Column 2: /
-To index a child in both its parent's domain and its own domain, link the child table to the parent table and then enter $DR at the next Link Column prompt:
-  Link Column 1: P=CUSTOMERS
-  Table will be indexed in the domain of CUSTOMERS
-  Link Column 2: $DR
-  Table will be indexed in its own domain
-To index a table as both a parent and a child table, enter $PK at the first Link Column prompt, then link the table to its parent at the next Link Column prompt:
-  Link Column 1: $PK
-  Table will be indexed in its own domain
-  Link Column 2: P=CUSTOMERS
-  Table will be indexed in the domain of CUSTOMERS
-====== Quick Links ======
-^    [[:start|Quick Links]]  ^^^^^
-^   General     ^   Programs              ^       Interfaces       ^   General Topics       ^   Miscellaneous Items^
-| [[overview:intro|Omnidex Introduction]] | [[programs:odxsql:intro|OdxSQL]] |[[development:interfaces:odbc:intro|ODBC]] | [[design:grids:intro|Grids]] | [[releasenotes:intro|Release Notes]] |
-| [[odxadmin:intro|Administrating Omnidex (OdxAdmin)]]     | [[programs:odxnet:intro|OdxNet]] |[[development:interfaces:jdbc:intro|JDBC]] | [[design:unionview:intro|Union Views]]| [[osinstall:intro|Server Installs]] |
-| [[design:intro|Data and Index Design]]         | [[programs:odxaim:intro|OdxAim]] |[[development:interfaces:storedproc:intro|Stored Procedures]] | [[design:rolluptable:intro|Rollup Tables]] | [[osinstall:licensing:intro|Licensing]] |
-| [[sql:intro|Omnidex Queries & SQL]]       | [[programs:dbinstal:intro|DBInstal]]   |[[development:interfaces:omniaccess:intro|OmniAccess]] | [[design:partitioning:intro|Partitioning]] | [[osinstall:settings:intro|Settings]] |
-| [[activecounts:intro|Active Counts]] | [[programs:oaenv:intro|OaComp/decomp/helper]]   |[[development:interfaces:clientoa:intro|Client OA]] | [[development:explainplan:intro|Explain Plans]]| [[glossary:intro|Glossary]] |
-| [[powersearch:intro|PowerSearch]] | [[programs:client:intro|DSEdit/OdxQuery]]  | [[rdbms:intro|RDBMS Indexing]] | [[development:debugging:intro|Debugging]]  | [[appendix:intro|Appendix]] |
-(c) Copyright Dynamic Information Systems - This document was last updated July 15, 2009.
-----

Back to top

programs/dbinstal/intro.1247797761.txt.gz · Last modified: 2012/10/26 14:25 (external edit)

Sitemap Recent Changes