HP 3000 Manuals HP 3000 Manuals
Appendix C IMAGE/SQL and Database Utilities
DBUTIL
DBUTIL contains several enhancements to support IMAGE/SQL.
Displaying Information
If the TurboIMAGE/XL database which is also enabled for third-party
indexing (TPI), is attached to any DBEnvironments, the ALL parameter of
the SHOW command displays this information, as the following example
illustrates:
[REV BEG]
_______________________________________________________________________________
| |
| :DBUTIL |
| HP30391C.05.09 TurboIMAGE/XL:DBUTIL (C)COPYRIGHT HEWLETT-PACKARD COMPANY|
| |
| >>SHOW SALES ALL |
| For database SALES |
| |
| Maintenance word is not present. |
| |
| Access is enabled. |
| . . . |
| . . . |
| No other users are accessing the database. |
| |
| Attached to these HP SQL DBEnvironments: |
| PARTSDBE.SERED.ATC |
| Third Party Indexes are registered in these HP SQL DBEnvironments: |
| PARTSDBE.SERED.ATC |
| >> |
_______________________________________________________________________________
[REV END]
Purging an Attached Database
If you want to purge a TurboIMAGE/XL database that is attached to a
DBEnvironment, a new parameter, DETACH, of the PURGE command allows you
to detach and purge the database.[REV BEG]
Detaching an Attached Database
If you want to detach a database from all DBEnvironments to which it is
attached, the DETACH command allows you to do this as shown in this
example:[REV END]
[REV BEG]
_________________________________________________________________________________
| |
| :DBUTIL |
| HP30391C.07.00 TurboIMAGE/XL: DBUTIL (C) COPYRIGHT HEWLETT-PACKARD COMPANY|
| |
| >>DETACH db1 |
| |
| Database has been detached from these HP SQL DBEnvironments: |
| RTDBE.BTRTESTS.IMAGESQL |
| TPDBE.BTRTESTS.IMAGESQL |
_________________________________________________________________________________
[REV END]
DBUTIL Enhancements for TPI
[REV BEG]
DBUTIL is enhanced for TPIs. The ENABLE, DISABLE, and SHOW statements
have been modified for TPI registration as follows:[REV END]
* ENABLE database FOR INDEXING
If your database is already attached to at least one DBE and you
enable it for indexing (TPIs must be configured before you use the
ENABLE command), an attempt is made to enter definitions for the
TPIs in all DBEs to which the database is attached. If the
registration fails in one DBE, it proceeds to register in
subsequent existing DBEs. If such an attempt fails in one or more
DBEs, upon completion of the last attempt, a message is displayed
as follows:
Registration of Third-Party indices failed
from these HP SQL DBEnvironments
The names of DBEs in which the TPI definitions failed follows the
message.
* DISABLE database FOR INDEXING
If definitions for TPIs are entered in the ALLBASE/SQL SYSTEM
CATALOG, the DISABLE database for INDEXING command triggers
removal of the TPI information from all DBEs to which the database
is attached. The removal of TPI information from all DBEs is
necessary, otherwise, results can be unpredictable at run-time.
If removal of this information fails in one DBE, it proceeds with
subsequent existing DBEs. If such an attempt fails in one or more
DBEs, upon completion of the last attempt, a message is displayed
as follows:
Dropping of Third-Party Indices failed
from these HP SQL DBEnvironments
This is followed by names of DBEs in which the dropping of TPIs
failed.
In this case, the database still remains ATTACHed, however, the
ALLBASE/SQL Optimizer has no knowledge of the TPIs as that
information is removed.[REV BEG]
In brief, DETACH (of IMAGESQL) only deletes information about TPIs
from one DBE. DISABLE (of DBUTIL) attempts to remove information
on TPIs from all DBEs to which the database is attached as the
database is turned off for TPI.
* SHOW database FLAGS or SHOW database ALL
If definitions for the TPIs are registered in one or more DBEs,
the FLAGS option displays a message indicating that the
definitions of TPIs are entered. The ALL option displays all DBEs
to which the database is attached, as well as the DBEs in which
the TPI definitions are entered.
[REV END]