Job Management Partner 1/Automatic Job Management System 3 Troubleshooting

[Contents][Glossary][Index][Back][Next]


2.8.5 Action to be taken if a communication error or power failure occurs

This subsection describes the action to be taken if the Communication error or Power failure occur.

Organization of this subsection
(1) Action to be taken if a communication error occurs
(2) Action to be taken if a power failure occurs

(1) Action to be taken if a communication error occurs

An error message reporting that a communication error has occurred in the transaction will be displayed.

Investigate the cause of the error, and then terminate the embedded database and take action to resolve the problem. If the communication error prevents you from terminating the embedded database normally, then forcibly terminate the embedded database.

(2) Action to be taken if a power failure occurs

When the OS and the embedded database are restarted following recovery from a power failure, the power backup mechanism in the hardware restores the system to the point immediately before the power failure occurred.

Cautionary note (for Windows)
If the KFPO00107-E message ("aa....aa(bb....bb)" failed. errno = 999: dd....dd) is output when a command is executed or the embedded database starts, an embedded database work file might have become corrupted. If so, make sure that the embedded database has stopped, and then delete and restore all of the files listed below. Note that the files from number 4 and up might not exist in your system.
  1. embedded-database-practical-directory\uxpldir\spool\system\filmng.dat
  2. embedded-database-practical-directory\uxpldir\spool\system\flg.dat
  3. embedded-database-practical-directory\uxpldir\spool\system\shmmng.dat
  4. embedded-database-practical-directory\spool\~pdatmode
  5. embedded-database-practical-directory\spool\~pdipcid
  6. embedded-database-practical-directory\spool\oslmqid
  7. embedded-database-practical-directory\spool\oslsmid
  8. embedded-database-practical-directory\spool\pdprcsts
  9. embedded-database-practical-directory\spool\scdqid1
  10. embedded-database-practical-directory\spool\scdqid2
  11. embedded-database-practical-directory\tmp\pdommenv
  12. All files under embedded-database-practical-directory\uxpldir\spool\shm
  13. embedded-database-practical-directory\uxpldir\spool\system\semmng.dat
  14. embedded-database-practical-directory\uxpldir\spool\system\msgmng.dat
After you delete these files, make sure that embedded-database-practical-directory\tmp is not being accessed by any other applications, such as Windows Explorer, when you restart the embedded database.

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.