Hitachi

JP1 Version 12 JP1/Service Support Configuration and Administration Guide


KNAB26103-E

Database recovery failed.

The database recovery command failed.

(S)

Cancels command processing.

(O)

Check the conditions described in the precautionary notes of the jssdbbackup.bat command, and the conditions listed below.

If any of the conditions exist when an error recovery is performed, correct the cause of the condition, and then re-execute the command.

If any of the conditions exist when an extension recovery is performed, perform an error recovery by using the error backup file that was created before the command was executed. Then, correct the cause of the condition and re-execute the command.

If any option is specified:

  • The backup file is specified on the network drive.

  • A UNC path is specified.

  • The drive specified as the backup file output destination does not exist. Alternatively, the medium is not inserted in the machine.

  • The drive specified as the backup file output destination cannot be used.

  • The JP1/Service Support service was started during execution of the command.

  • The JP1/Service Support - DB Server service was stopped during execution of the command.

  • Another JP1/Service Support command was executed during execution of the command.

  • An extension recovery was performed by using a file collected during an error backup. Alternatively, an error recovery was performed by using a file collected during an extension backup.#

  • An extension recovery was performed by specifying the size of the Item management database smaller than that specified for performing an extension backup. Alternatively, the recovery-target Item management database was too small to save the data due to database reconfiguration when backup was executed.#

  • The setup status and number of Item storage area expansions are different from those of the backup.#

#

If the -o option was specified to create backup data, information shown below was stored during backup in the dbpath.txt file that was output to the backup file output folder. Check the following information to identify the cause of the error:

- Options specified when the jssdbbackup.bat command was executed

- Database size

- Setup information for the Item management database and Item storage database, and information about the directories where the databases are expanded

If the -f option is specified:

  • The file name is not specified by using the absolute path.

  • A folder is specified for the backup file name.

  • The backup file name specified by using the absolute path contains more than 259 bytes.

  • The backup file name contains more than 255 bytes.

  • Multibyte characters or a character string that cannot be specified in the operating system is specified in the file name.

If the -i option is specified:

  • The folder name is not specified by using the absolute path.

  • A file name is specified for the backup file output folder.

  • Multibyte characters or a character string that cannot be specified in the operating system is specified in the folder name.

If the recovery was performed by using a backup file collected in a different version environment, perform the following procedure.

If the backup file collected in the latest version environment is recovered in an older version environment:
  1. Perform an overwrite installation of the latest version.

  2. Execute the setup command with the -vup option specified.

  3. Recover the backup file collected in the latest version environment.

If the backup file collected in an older version environment is recovered in the latest version environment:
  1. Uninstall the latest version.

  2. Perform a new installation of the version of JP1/Service Support used when the backup file was collected.

  3. Set up JP1/Service Support.

  4. Recover the backup file collected in the old version environment.

  5. Perform an overwrite installation of the latest version.

  6. Execute the setup command with the -vup option specified.

If none of the above cases applies, collect the data and then contact the system administrator.