17.7.1 DBMS errors

(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.

To Page Top

(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.

To Page Top

(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 Console 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.

To Page Top

(4) An error occurs during the creation of the asset management database and execution stops

The disk at the database storage destination or the database that was specified when creating the database might have reached its capacity.

Re-create the asset management database on a disk that has enough space for Size, Management area, and Operation area, according to the settings specified in the Detailed Database Settings dialog box that was displayed during database creation.

To Page Top

(5) The login window opens, but a message "Page cannot be displayed" is displayed, and you cannot log in

It is possible that no asset management database has been created.

First, you must open the Server Setup dialog box. Enter values in Login ID and Password under Database Information and click the OK button.

Avoid reserved words for the login ID and service name. For the reserved words, see RESWORDS.TXT stored in the Asset Console installation folder.

After that, create the asset management database.

To Page Top

(6) Database connection authentication fails

An error message beginning with the following character string is output to the log:

• KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11561-E

Either Login ID or Password in Database Information might have been changed after Asset Console operations started.

Start the Server Setup dialog box and then reset Login ID and Password under Database Information to the status existing when the asset management database was created.

You cannot change Login ID and Password under Database Information while the database is running.

To Page Top

(7) A database communication error occurred or an error occurred inside the database

An error message beginning with the following character string is output to the log:

• KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11723-E

• KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11728-E

The DBMS server might be starting up, shut down, or stopped. Check the following:

• Make sure that the HiRDB/EmbeddedEdition _AM1 service is running. If it has stopped, start it by executing jamemb_dbstart.bat as a user with administrator permission. After this service has started completely, re-start World Wide Web Publishing Service.

  For details about logs, see the manual HiRDB Version 8 Messages.

• Ensure that the network cable is securely connected to the Asset Console server. If the network cable is disconnected from the server, the database and Asset Console cannot communicate with each other.

To Page Top

(8) A database capacity shortage occurred

An error message beginning with the following character string is output to the log:

• KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11756-E

A page shortage might have occurred in the database area.

Reorganize the asset management database. If the same error message is displayed again after reorganization, re-create the asset management database and change the size.

For details about how to reorganize the asset management database, see 18.2.1 Reorganizing the asset management database from the Database Manager dialog box or 18.2.2 Reorganizing the asset management database using commands. For details about how to change the size of the asset management database, see F.2 Changing the size of a database.

To Page Top

(9) Available space has been reduced on the drive where the asset management database was created

The capacity of the work file of the database (a file for storing the temporary information necessary for executing SQL statements) might have been expanded automatically, causing a shortage of disk space.

The work file capacity is automatically expanded when a large amount of search results are output. If there is not enough space on the drive where the asset management database was created, you can release the automatically expanded area for the work file by executing jamemb_workcomp.exe.

This subsection describes the function, format, and return values of jamemb_workcomp.exe, which releases the automatically expanded area for a database work file. This subsection also provides notes on the command's execution.

jamemb_workcomp.exe is stored in the following folder:

Asset-Console-installation-folder\exe

jamemb_workcomp.exe

To Page Top

(10) The KFPO00107-E message is output

If the KFPO00107-E message is output during a Database Manager operation, a work file has possibly been corrupted due to memory shortage, or the database service has possibly started before the related process finishes completely. In such a case, re-execute the operation in Database Manager. After that, if the problem has not been solved, delete all files listed in (a) and (b) below to recover the environment, and then re-execute the operation. As for the files listed in (b), you do not have to delete them if they do not exist. After the recovery processing, make sure to re-execute the operation only when no other applications (for example, Windows Explorer) are accessing Asset-Console-installation-folder\aimdb\tmp.

(a)

• Asset-Console-installation-folder\aimdb\uxpldir\spool\system\filmng.dat

• Asset-Console-installation-folder\aimdb\uxpldir\spool\system\flg.dat

• Asset-Console-installation-folder\aimdb\uxpldir\spool\system\shmmng.dat

(b)

• Asset-Console-installation-folder\aimdb\spool\~pdatmode

• Asset-Console-installation-folder\aimdb\spool\~pdipcid

• Asset-Console-installation-folder\aimdb\spool\oslmqid

• Asset-Console-installation-folder\aimdb\spool\oslsmid

• Asset-Console-installation-folder\aimdb\spool\pdprcsts

• Asset-Console-installation-folder\aimdb\spool\scdqid1

• Asset-Console-installation-folder\aimdb\spool\scdqid2

• Asset-Console-installation-folder\aimdb\spool\pdommenv

• Asset-Console-installation-folder\aimdb\tmp\pdommenv

• All files under Asset-Console-installation-folder\aimdb\uxpldir\spool\shm

• Asset-Console-installation-folder\aimdb\uxpldir\spool\system\semmng.dat

• Asset-Console-installation-folder\aimdb\uxpldir\spool\system\msgmng.dat

To Page Top