Job Management Partner 1/Software Distribution Administrator's Guide Volume 2
This subsection describes the database maintenance procedures required in a cluster system environment. For details about backing up a database and restoring a database from a backup, see 5.3 Backing up and restoring the system.
You use Database Manager to maintain a database. For details about how to start Database Manager when an Embedded RDB relational database is used, see 7.4 How to use Database Manager (for Embedded RDB) in the manual Setup Guide. For details about how to start Database Manager when a Microsoft SQL Server or Oracle relational database is used, see 7.5 How to use Database Manager (for Microsoft SQL Server or Oracle) in the manual Setup Guide.
- Organization of this subsection
- (1) Reorganizing the database (cluster system environment)
- (2) Upgrading the database (cluster system environment)
(1) Reorganizing the database (cluster system environment)
To reorganize an Embedded RDB database in a cluster system environment:
- Place the following generic-service resources offline:
- Asset Information Synchronous Service#
- Microsoft Internet Information Services#
- Remote Install Server
- Using Database Manager, reorganize the database from Reorganize the database.
For details about Database Manager, see 7.4.6 Reorganizing the database in the manual Setup Guide.
- Place the following generic-service resources online:
- Remote Install Server
- Microsoft Internet Information Services#
- Asset Information Synchronous Service#
#: This item is required when Asset Information Manager Subset is used.
If you use a Microsoft SQL Server or Oracle relational database, see the RDBMS documentation for details about reorganizing the database.
(2) Upgrading the database (cluster system environment)
This subsection describes how to upgrade a database in a cluster system environment. You must upgrade the databases on both the active server and the standby server.
To upgrade a database:
- Place the following generic-service resources offline:#
- Asset Information Synchronous Service
- Microsoft Internet Information Services
- Delete the Registry Copy setting for the generic-service resource for Remote Install Server.
- Place the generic-service resources for Remote Install Server offline.
- Using Database Manager, upgrade the database from Upgrade database.
In the Cluster System Environment Settings dialog box, specify the same settings as for new creation.
If this is a Microsoft SQL Server or Oracle database, go to step 14. Steps 5 through 13 are required for an Embedded RDB database.
- Execute the netmdb_stop.bat command that is stored in JP1/Software-Distribution-Manager-installation-directory \BIN.
Check the message to make sure that Embedded RDB has terminated.
- Place the generic-service resource for HiRDB/ClusterService_JN1 offline.
- Execute the jamemb_dbstop.bat command that is stored in JP1/Software-Distribution-installation-directory\jp1asset\exe.#
Check the message to make sure that Embedded RDB has terminated.
- Place the generic-service resources for HiRDB/ClusterService_AM1 offline.#
- Use the cluster system administrator to move the group and set the owner as the standby server.
- Place the generic-service resource for HiRDB/ClusterService_JN1 online.
- On the standby server, perform steps 4 through 8.
- Use the cluster system administrator to move the group and set the owner as the active server.
- Place the following generic-service resources online:
- HiRDB/ClusterService_AM1#
- HiRDB/ClusterService_JN1
- Place the generic-service resources for Remote Install Server online.
- Enter the Registry Copy setting for the generic-service resource for Remote Install Server.
- Place the following generic-service resources online:#
- Microsoft Internet Information Services
- Asset Information Synchronous Service
#: This step is required when Asset Information Manager Subset is used.
All Rights Reserved. Copyright (C) 2009, 2013, Hitachi, Ltd.
Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.