Nonstop Database, HiRDB Version 9 Installation and Design Guide
This section describes the procedure for deleting plug-ins that have been registered into HiRDB. Deleting a plug-in means the following:
The plug-in-provided file that contains the plug-in file set is not deleted.
Before deleting a plug-in, the HiRDB administrator must delete the database resources listed below. The table below lists the SQL statements issued to delete the following resources:
Table 5-2 SQL statements for deleting database resources
| Database resources to be deleted | SQL statement to be used |
|---|---|
| Table | DROP TABLE |
| Index | DROP INDEX |
| View table | DROP VIEW |
| Function | DROP FUNCTION |
| Procedure | DROP PROCEDURE |
| Abstract data type | DROP DATA TYPE# |
The following command is executed for each plug-in that is to be deleted:
pdplgrgst -d plug-in-definition-filename PIC-filename
For details about how to delete registry information, see the applicable plug-in documentation.
The pdstop command must be entered to terminate HiRDB normally.
When HiRDB is terminated normally, the pdplugin operand must be deleted from the applicable system common definitions.
The pdplgset -d command is used to cancel setup of the plug-in. Before this command is executed, save all necessary files. No files are deleted from the conf directory. Plug-in setup cancellation must be performed at all units where HiRDB is set up.
The plug-in must be uninstalled from the server machine. For details about the uninstallation, see the procedure for the applicable plug-in.
All Rights Reserved. Copyright (C) 2012, 2015, Hitachi, Ltd.