When upgrading from version 08-00 or earlier to 08-10 or later, the required database capacity is different between these versions because the database structure has been changed. This may result in a space shortage error during upgrading. If this is the case, re-estimate the required database capacity and then upgrade the database. You can change the database capacity during upgrading. For details about estimating capacity during upgrading from version 08-00 or earlier to 08-10 or later, see 5.4.1(9) Notes on differences between sizes for version 08-00 and earlier and version 08-10 and later in the Description and Planning Guide.

The backup files acquired prior to database upgrading cannot be restored because the database structure is different. After upgrading the database, acquire a backup again.

Notes

• Before you upgrade the database, stop Remote Install Server service by opening Control Panel, and then choosing Administrative Tools, and Services.
• If you are using Asset Information Manager Subset, stop the Asset Information Manager Subset services in the following order.
  

  World Wide Web Publishing Service or World Wide Web Publishing Commands and tasks of the Asset Information Synchronous Service and Asset Information Manager Subset JP1/Client Security Control - Manager (applicable if JP1/CSC is linked)

To use Asset Information Manager Subset after you have used the Database Manager, start the services in the reverse order from that listed above.

• If a connection pool has been set up in the ODBC database, the connected status will not change from the time that the Asset Information Manager Subset job was stopped until the timeout time set in the connection pool elapses. Therefore, wait for the connected status to change before upgrading the database.

To upgrade the database:

1. In the Welcome dialog box, select Upgrade database, and then click the Next button.
   The Authentication Information of Database dialog box appears.
   
2. In the Authentication Information of Database dialog box, specify the password, and then click the Next button.
   The Cluster System Environment Settings dialog box appears.
   

   Figure 7-11 Cluster System Environment Settings dialog box

   

   If the database to be upgraded is used in a cluster environment, specify the same settings as when the existing database was created.
   
3. In the Cluster System Environment Settings dialog box, specify the settings and then click the Next button.
   The Database Management Settings dialog box appears.
   

   Figure 7-12 Database Management Settings dialog box

   

   You can change the size of the work table space. The default is that the value set during the creation process is displayed. However, if an automatic size increase is specified, the current size is displayed.
   If the size of the work table space that is currently allocated is the same as the estimated size, use the automatic size increase setting.
   In a cluster system environment, the Automatically increase the size check box setting should be the same in both the executing system and the standby system.
   
4. Specify the settings in the Database Management Settings dialog box, and then click the Next button.
   The Detailed Settings of Database dialog box appears.
   

   Figure 7-13 Detailed Settings of Database dialog box

   

   You can change the sizes of database area files. The defaults are the values set when the database area files were created.
   This dialog box is not displayed if you selected Standby system in the Cluster System Environment Settings dialog box.
   
5. Specify the settings in the Detailed Settings of Database dialog box, and then click the Next button.
   This displays a dialog box for selecting whether to migrate patches acquired by the security update management facility. The dialog box is not displayed in the following cases:
   
   • When upgrading from a database earlier than version 08-10
   • When the database version is 08-10, and no table was created for security update management
     

     Figure 7-14 Dialog box for selecting whether to migrate patches acquired by the security update management facility

     

   Migrate downloaded patches

   During database upgrades, select this option to migrate any patches acquired by the security update management facility.

   If you select this item, the patches are temporarily saved, so database upgrades will require more time. When you select this item and click the Next button, a dialog box will be displayed that provides a rough estimate of the increased time for the upgrade.

   Also, since the patches are saved temporarily, you will need sufficient space in the JP1/Software Distribution Manager installation target directory. The required space is displayed in the dialog box for selecting whether to migrate patches acquired by the security update management facility.

   Do not migrate downloaded patches

   During database upgrades, select this option to not migrate patches acquired by the security update management facility.

   The package in which the patch is stored is not deleted when this item is selected. We recommend selecting this item when a patch is packaged or when a patch can be re-acquired.

   When you select this item and click the Next button, a dialog box will be displayed to confirm that it is OK to delete the patch.

6. Specify a setting in the dialog box for selecting whether to migrate patches acquired by the security update management facility, and then click the Next button.
   The Output Destination for Temporary Files Used for Upgrading dialog box appears.
   

   Figure 7-15 Output Destination for Temporary Files Used for Upgrading dialog box

   

   Specify the output destination of the temporary files that are output during database upgrading.
   This dialog box is not displayed if you selected Standby system in the Cluster System Environment Settings dialog box.
   

   Path where the temporary files used during an upgrade are stored

   Specify the folder to which the temporary files used for upgrading are to be output. The files listed below are output to the specified folder:

   netmUpgTemp

   netmdm_cabinet

   netmdm_collect

   netmdm_inspackage

   netmdm_jobgen_collect

   netmdm_jobgen_pack

   netmdm_package_inf

   UPGTemp.log

7. Specify the settings in the Output Destination for Temporary Files Used for Upgrading dialog box, and then click the Next button.
   The Upgrade Database dialog box appears.
   

   Figure 7-16 Upgrade Database dialog box

   

8. Click the Execute button.
   The database is upgraded.
   When upgrading is completed, the temporary files used during upgrading are automatically deleted.
   If a message indicating that migration of a patch to the database during upgrading has failed, the patch can be stored in the database by executing the DPTInpt.exe command. The upgrade will terminate normally when this happens. For details about the DPTInpt command, see (3) DPTInpt.exe (store patch in database).
   If an error message indicating that there is not enough space in the database area file is displayed during upgrading, re-estimate the required database capacity, and specify a sufficient size during upgrading.
   Even when the message The database has been upgraded successfully. Back up the database again because you cannot use a backup that was made before the upgrade is displayed, the events listed in the following table may be output to the application log. In such a case, no action is necessary because the upgrade processing has been completed successfully.
   

   No.	Source	Type	Event ID	Message ID
   1	HiRDBEmbeddedEdition_JN1	Warning	30001	KFPH22004-W
   2	HiRDBEmbeddedEdition_JN1	Warning	30001	KFPH22012-W
   3	HiRDBEmbeddedEdition_JN1	Warning	30001	KFPS04604-W
   4	HiRDBEmbeddedEdition_JN1	Warning	30001	KFPX24231-W
   5	HiRDBEmbeddedEdition_JN1	Error	30001	KFPH00142-E
   6	HiRDBEmbeddedEdition_JN1	Error	30001	KFPH00306-E
   7	HiRDBEmbeddedEdition_JN1	Error	30001	KFPH22003-E
   8	HiRDBEmbeddedEdition_JN1	Error	30001	KFPS00349-E
   9	HiRDBEmbeddedEdition_JN1	Error	30001	KFPX14236-E

When you upgrade the database, suppression history and operation history for software operation monitoring are not migrated. If you use the Operation Log List window to manage operation information, use the dcmmonrst command to migrate the operation information. For details about the dcmmonrst command, see 4.13 dcmmonrst.exe (storing operating information in a database) in the manual Administrator's Guide Volume 2.

This subsection describes the DPTInpt command, which migrates patches to the database when using Embedded RDB as the relational database. This command can only be executed on the PC on which the server core facility of JP1/Software Distribution Manager is installed. Embedded RDB must be running to execute this command.

Function

Stores patches in database. Execute this command when migrating a patch during an upgrade of Embedded RDB version 08-10 or later if the patch migration fails.

Format

DPTInpt.exe /U user-name/P password

Arguments

• /U
  Specifies the login ID for accessing Embedded RDB. This ID must be expressed as 1 to 8 alphanumeric characters beginning with an alphabetic character.
  
• /P
  Specifies the password for accessing Embedded RDB. Express the password as 1 to 30 alphanumeric characters beginning with an alphabetic character. Spaces cannot be used.
  

Return codes

The following table shows the codes returned when DPTInpt is executed.

Code	Description	Action
0	Terminated normally.	None.
1	Invalid value specified as argument.	Check the values of the command arguments.
2	An internal error occurred.	Check whether Embedded RDB is running.

Notes

• Do not execute more than one instance of the DPTInpt command.
• Do not start the security update management facility while the DPTInpt command is executing. Note that the security update management facility can be started using the task scheduler. Therefore, if you are using the task scheduler, be careful not to start the security update management facility while a DPTInpt command is executing.
• In the following cases, do not execute the DPTInpt command:
  When Database Manager is running
  When the security update management facility is running
  

Execution example

To execute the DPTInpt command with a login ID of netmdm and password of abcde12345, specify the command as follows.

DPTInpt.exe /U netmdm /P abcde12345