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 before detaching a TurboIMAGE/XL database.
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
Current Log File : ATCLOG.SERED.ATC
>>
|
If necessary, issue the SET commands. For example:
>>SET SQLDBE PARTSDBE.SERED.ATC
>>SET TURBODB SALES.SERED.ATC
>>
|
Performing the Task
Once you have issued the appropriate SET commands,
you are ready to detach the database from the DBEnvironment.
For example:
This command detaches the SALES database from the PartsDBE DBEnvironment.
If SALES is the only database attached to PartsDBE, the
ATCINFO file (DBEnvironmentNameCR)
will be deleted. If PartsDBE is the only DBEnvironment to which SALES
is attached, the SALESTC file will also be deleted.
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 you want 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 (default name DBEnvironmentNameCR)
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.
