jpctool db dmconvert

Format

jpctool db dmconvert    -d backup-directory

To Page Top

Function

The jpctool db dmconvert command converts the data model for backup data. When a conversion is performed, the data model version for the backup data becomes the same version as that of the currently installed instance of PFM - Agent or PFM - RM.

To Page Top

Hosts that can execute the command

• PFM - Manager

• PFM - Agent

• PFM - RM

To Page Top

Execution permission

In Windows:

User with Administrators permissions

In UNIX:

User with root user permissions

To Page Top

Installation directory

In Windows:

installation-folder\tools\

In UNIX:

/opt/jp1pc/tools/

To Page Top

Arguments

To Page Top

Notes

• You cannot downgrade the data model version.

• You can execute the jpctool db dmconvert command only when the Store version of the backup data to be specified in the -d option is 2.0.

• An error occurs if the agent with the same product ID as the backup data is not installed.

• An error will occur when the data model version of the backup data is later than the data model version of the installed agent.

• The target backup data must be data that was backed up when the Store version was 2.0.

• When this command is executed, twice as much free disk space as the amount of data converted is temporarily required in the directory specified for jpctool db dmconvert -d.

  Use the total size of the database stored in the directory specified for the -d option.

  For example, if the total size of the database in the directory specified for the -d option is 100 MB, secure at least 200 MB of free disk space, and then execute this command.

• If the jpctool db dmconvert command fails with a KAVE05849-E message, use the procedure described below to correct the failure.

  Note that the jpctool db dmconvert command backs up data internally. You might need to delete the backup data or need to perform restoration from the backup data, according to the situation.

  The following table lists the files that the jpctool db dmconvert command backs up, and the locations in which the backup files are stored.

  In Windows, please replace a slash (/) with a backslash (\).

  Type	Backup source	Backup destination
  Store database	backup-directory	backup-directory/cvtwork
  Definition file	backup-directory/jpcsto.ini	backup-directory/jpcsto.ini.bak
  	backup-directory/STDICT.DAT	backup-directory/STDICT.DAT.bak
  	backup-directory/STRULES.DAT	backup-directory/STRULES.DAT.bak

  Before performing the procedure described below, check whether a KAVE05801-I message has been output.

  • If a KAVE05801-I message has been output:

    Database conversion has been completed.

    Unnecessary backup data might remain at the backup destination.

    Check the backup destination, and delete data, if any.

  • If a KAVE05801-I message has not been output:

    Database conversion was not completed.

    Use the following procedure to troubleshoot the problem:

  1. Check the message that was output immediately before the above message, and remove the cause of the error.

  2. Restore the data from the backup data as described below. If there is no backup data, you do not need to perform restoration.

     Before you start restoration, do not use any Performance Management commands or services to manipulate or view the Store database in the backup directory.

     How to restore the Store database differs depending on whether a KAVE05800-I message has been output. Check whether a KAVE05800-I message has been output.

     If a KAVE05800-I message has been output:

     Delete the backup-source STPI, STPD, and STPL directories, and then copy all backup files and directories back to their original locations.

     Any remaining source files must be overwritten with the corresponding backup files.

     If a KAVE05800-I message has not been output:

     Copy all backup files and directories back to their original locations, without deleting the backup-source STPI, STPD, and STPL directories.

     Any remaining source files and directories must be overwritten with the corresponding backup files and directories.

     For definition files, backup files are saved with different names. After copying files and directories, delete these definition files, and then restore these definition files by renaming their backup files.

  3. Re-execute the command.

To Page Top

Return values

To Page Top