HP 3000 Manuals

Getting Started with HP IMAGE/SQL

Detaching a TurboIMAGE/XL Database 

This task describes how to detach a TurboIMAGE/XL database from a
DBEnvironment.

Getting Ready 

Before detaching a TurboIMAGE/XL database, do the following:

   *   Obtain exclusive access to the DBEnvironment.

   *   Make sure the appropriate SET SQLDBE and SET TURBODB commands have
       been issued.  To check the status of these commands, use the
       DISPLAY OPTIONS command:
___________________________________________
|                                         |
|     >>DISPLAY OPTIONS                   |
|     Current base    :                   |
|     Current SQLDBE  :                   |
|     Echo            : ON                |
|     Command Logging : ON                |
|     Log File        : ATCLOG.PUB.TURBONM|
|     >>                                  |
___________________________________________

            

   *   If necessary, issue the SET command.  For example:
________________________________________
|                                      |
|     >>SET SQLDBE MUSICDBE.PUB.TURBONM|
|     >>SET TURBODB MUSIC.PUB.TURBONM  |
|     >>                               |
________________________________________

            

Performing the Task 

Once you have issued the appropriate SET commands, you are ready to
detach the database from the DBEnvironment.  For example:
_____________________________________
|                                   |
|     >>DETACH                      |
|     >>                            |
_____________________________________

            

This command detaches the MUSIC database from the MusicDBE DBEnvironment.
If MUSIC is the only database attached to MusicDBE, the ATCINFO file will
be deleted.  If MusicDBE is the only DBEnvironment to which MUSIC is
attached, the MUSICTC file will also be deleted.

In addition, all mapped table definitions are removed from the
DBEnvironment system catalog.  All IMAGE/SQL views and user-created views
based on IMAGE/SQL tables and views are dropped.

Task Reference 

   *   There are several reasons to detach a TurboIMAGE/XL database from
       a DBEnvironment:
          *   If the database is to be restructured.  (This includes
              restructuring with DBChange and other third-party
              restructuring tools.)
          *   If ALLBASE/SQL is to be migrated back to a version that
              does not support IMAGE/SQL.
          *   If you wish to reset all mapping information to default
              values.

   *   All mapped tables, all IMAGE/SQL views based on these tables, and
       all user-created views based on IMAGE/SQL views and tables are
       dropped when the database is detached.

   *   The ATCINFO file is purged when it no longer contains mapping
       information about any databases.

   *   The DBaseNameTC file is deleted when the database is no longer
       attached to any DBEnvironments.

MPE/iX 5.0 Documentation