6.3 Deleting plug-ins

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.

Organization of this section
(1) Deleting the database resources that use the facility provided by the plug-in
(2) Deleting the registered plug-in
(3) Deleting the registry
(4) Terminating HiRDB
(5) Making appropriate changes to the system common definition
(6) Canceling setup of the plug-in
(7) Uninstalling the plug-in

(1) Deleting the database resources that use the facility provided by the plug-in

Before deleting a plug-in, the HiRDB administrator must delete the database resources listed below. Table 6-2 lists the SQL statements that can be used to delete these resources.

* The data type provided by a plug-in must not be deleted.

(2) Deleting the registered plug-in

The following command is executed for each plug-in that is to be deleted:

pdplgrgst -d plug-in-definition-filename PIC-filename

Notes
  1. When a data-type plug-in is to be deleted and an index-type plug-in providing the index facility for that data type is also registered, the index-type plug-in must be deleted first.
  2. If you are deleting a plug-in with an owner who is not MASTER, note the following:
    • Only a plug-in's owner can delete his/her plug-in. Specify the authorization identifier and password of the plug-in owner in the PDUSER operand in the client environment definitions. Then, specify the -u option when executing the pdplgrgst command.
    • The owner of a plugin registered with HiRDB Version 5.0 (with HiRDB Object Option) is not MASTER. Therefore, you need to take the actions described previously.
    • If you delete a plug-in owner's schema, the plug-in itself is also deleted. For details about the actions to be taken after the plug-in has been deleted, see the sections beginning at (3) as follows.

(3) Deleting the registry

For details about how to delete registry information, see the applicable plug-in documentation.

(4) Terminating HiRDB

The pdstop command must be entered to terminate HiRDB normally.

(5) Making appropriate changes to the system common definition

When HiRDB is terminated normally, the pdplugin operand must be deleted from the applicable system common definitions.

(6) Canceling setup of the plug-in

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.

(7) Uninstalling the plug-in

The plug-in must be uninstalled from the server machine. For details about the uninstallation, see the procedure for the applicable plug-in.