Job Management Partner 1/Asset Information Manager Planning and Setup Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
11.7.1 Errors common to the DBMS
(1) The DBMS environment is invalid or has been damaged
The following are the possible causes:
- A DLL of the DBMS client could not be loaded.
If the asset management server and the asset management database server are distributed, make sure that the client environment of the DBMS is installed correctly.
- No DBMS driver exists.
Make sure that the client environment of the DBMS is installed correctly.
- The number of concurrent connections to the DBMS has exceeded the limit.
Check the setting details to make sure that the number of concurrent connections to the DBMS has not exceeded the limit.
- The network is set so that the DBMS server or the network containing it cannot be reached.
Check the communication route settings for the network in which the DBMS server exists and determine whether the DBMS server can be recognized.
(2) Connection to the asset management database results in an error
The following are the possible causes:
- The DBMS server is inactive, shut down, or in the process of stopping.
Ensure that the DBMS is operating normally.
- The network is set so that the DBMS server or the network containing it cannot be reached.
Check the communication route to the DBMS server.
- The user ID or password specified for connection is invalid.
Make sure that the user ID and password are correct.
- A DBMS server error caused a timeout or resource shortage.
Check the operating status of the DBMS.
(3) Script execution results in an error
The following are the possible causes:
- Disk access failed.
Make sure that the disk is not full, there is no access problem, and no I/O error has occurred.
- The transaction log is full.
If a message indicating a full transaction log has been output to the Asset Information Manager log, check the setting for the DBMS transaction log. In this case, it is recommended that you either stop collecting transaction logs or collect backups on a regular basis.
- Locking control caused a lock error or database connection timeout.
Check the operating status of the DBMS.
- Script buffer overflow
- Invalid script syntax
- Nonexistent target table
If the environment was customized, make sure that the customization details are valid.
All Rights Reserved. Copyright (C) 2009, 2011, Hitachi, Ltd.