Table of Contents
Advertisement
POPULATE INDEX Utility
•
"Syntax Description of POPULATE INDEX"
•
"Considerations for POPULATE INDEX"
•
"Examples of POPULATE INDEX"
POPULATE INDEX is a utility that can be executed in the Neoview Command Interface (NCI).
The POPULATE INDEX utility loads Neoview SQL indexes.
POPULATE INDEX index ON table [index-option]
index-option is ONLINE | OFFLINE
Syntax Description of POPULATE INDEX
index
is an SQL identifier that specifies the simple name for the index. You cannot qualify index
with its schema name. Indexes have their own namespace within a schema, so an index name
might be the same as a table or constraint name. However, no two indexes in a schema can
have the same name.
table
is the name of the table for which to populate the index. See
(page
242).
ONLINE
specifies that the populate should be done online. That is, ONLINE allows read and write
DML on the base table while population occurs. Additionally, ONLINE reads the audit trail
to replay updates to the base table during the population phase. If a lot of audit is generated
and you perform many CREATE INDEX operations, Neoview SQL recommends that you
avoid ONLINE operations because they can add more contention to the audit trail. The
default is ONLINE.
OFFLINE
specifies that the populate should be done offline. OFFLINE only allows read access to the
base table. The base table is unavailable for write operations at this time. OFFLINE must be
specified explicitly. SELECT is allowed.
Considerations for POPULATE INDEX
When POPULATE INDEX is executed, the following steps occur:
•
The POPULATE INDEX operation runs in many transactions
•
The actual data load operation is run outside of a transaction
If a failure occurs, the rollback is faster because it doesn't have to process through a lot of audit.
Also, if a failure occurs, the index remains empty, unaudited, and not attached to the base table
(offline).
•
To populate an index, you must be the schema owner, object owner, have the ALTER
privilege, or have the SELECT, INSERT, and DELETE privileges.
•
When an offline POPULATE INDEX is being executed, the base table is accessible for read
DML operations. When an online POPULATE INDEX is being executed, the base table is
accessible for read and write DML operations during that time period, except during the
commit phase at the very end.
220
SQL Utilities
"Database Object Names"
Advertisement
Table of Contents
