This subsection discusses the causes and actions to be taken for each type of DBMS eror.

(a) The DBMS environment is invalid or corrupted

• Four possible causes are as follows:
  
  • The DBMS client's DLL cannot be loaded.
  • There is no DBMS driver.
  • The DBMS does not reach the Asset Information Manager Subset server on the network.
  • The number of concurrent connections to DBMS has reached the maximum.
  Check the specified settings for any error. If the Asset Information Manager Subset server is different from the Asset Information Manager Subset database server, make sure that the DBMS's client environment has been installed.
  
• Network settings might be specified in such a manner that the DBMS server or the network containing the DBMS server cannot be reached.
  Check the communication channel to the DBMS server.
  

(b) Attempt to connect to the Asset Information Manager Subset database results in an error

• The DBMS server might be inactive, shut down, or engaged in termination processing.
  Make sure that the DBMS is running correctly.
  
• The network settings might be specified in such a manner that the DBMS server or the network containing the DBMS server cannot be reached.
  Check the communication channel to the DBMS server.
  
• The user ID or password specified during connection establishment might be invalid.
  Make sure that the correct user ID and password are specified.
  
• A timeout or resource shortage might have occurred due to an error in the DBMS server.
  Check the DBMS operating status.
  

(c) Script execution results in an error

• The disk might be full.
  Check the free space on the drive where the disk space has been allocated, whether there are extensions, and the maximum value.
  
• The transaction logs might be full.
  If a message indicating that transaction logs are full is output to the Asset Information Manager Subset log, check the DBMS's transaction log settings. We recommend that you stop collecting transaction logs, or periodically back up the transaction logs.
  
• A lock error due to lock control or a database connection timeout might have occurred.
  Check the DBMS's operating status.
  
• Five possible causes are as follows:
  
  • Permissions are invalid for the request.
  • An overflow has occurred in the script buffer.
  • There is a syntax error in the script.
  • A disk I/O error occurred.
  • A target table does not exist.
  Restore the environment that existed before customization.
  

For Embedded RDB, you must take into account the causes specific to Embedded RDB in addition to the causes discussed in (1) Errors common to DBMS.

This subsection discusses the causes and actions to be taken for each type of error.

(a) Creation of an Asset Information Manager Subset database stops due to an error

The disk space for database storage or the space for Embedded RDB specified during database creation might have become full.

Re-create the Asset Information Manager Subset database on a disk that has enough space for the capacity specified in Size for Management area and Operation area in the Detailed Database Settings dialog box that is displayed during database creation.

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

No Asset Information Manager Subset database has been created.

Make sure that you have already started the Server Setup dialog box and enter Login ID and Password in Database Information, then click the OK button.

Do not use a reserved word in the login ID or service name (you can check the list of reserved words in RESWORDS.TXT that is stored in JP1/Software-Distribution-Manager-installation-folder\jp1asset).

Now create an Asset Information Manager Subset database.

(c) Authentication for database connection fails

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

• KDAM5001-E[HY000] character-string-displayed-according-to-the-status KFPA11561-E

Login ID or Password in Database Information might have been changed after Asset Information Manager Subset operation was started.

Open the Server Setup dialog box and change Login ID and Password in Database Information to the values specified when the Asset Information Manager Subset database was created.

Login ID and Password in Database Information cannot be changed during operation.

(d) A database communication error has occurred or an error has occurred in the database

An error message beginning with one of the following character strings is output to the log:

• KDAM5001-E[HY000] character-string-displayed-according-to-the-status KFPA11723-E
• KDAM5001-E[HY000] character-string-displayed-according-to-the-status KFPA11728-E

The DBMS server might be running, be shut down, or have terminated. Check the following:

• Check if the HiRDB/EmbeddedEdition _AM1 service is running. If it is not running, start it. After this service has started completely, re-start World Wide Web Publishing Service.
  For details about the logs, see the manual HiRDB Version 8 Message.
  
• Make sure that the network cable is connected securely to the Asset Information Manager Subset server. If the network cable is disconnected from the server, communication is not available between Embedded RDB and Asset Information Manager Subset.

(e) There is a shortage of database capacity

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

• KDAM5001-E[HY000] character-string-displayed-according-to-the-status KFPA11756-E

There might be a shortage of pages in the database area.

Reorganize the Asset Information Manager Subset database. If the same error message is displayed again after the database has been reorganized, re-create the Asset Information Manager Subset database and change its size.

For details about how to reorganize the Asset Information Manager Subset database, see 10.3.7 Reorganizing databases in an Embedded RDB environment in the manual Setup Guide. For details about how to change the size of an Asset Information Manager Subset database, see 5.2.3(3) Changing the size of an Embedded RDB.

(f) Free space has decreased on the drive where the Asset Information Manager Subset database was created

This might have been caused by automatic extension of the Embedded RDB work file (used to store temporary information required for executing SQL statements).

The size of the work file is extended automatically when a large volume of search results is output. If a space shortage has occurred on the drive where the Asset Information Manager Subset database has been created, you can release the area extended automatically for the work file by executing jamemb_workcomp.exe.

This subsection describes the function, format, and return values of jamemb_workcomp.exe, the command for releasing the area expanded automatically for the work file in Embedded RDB. The subsection also includes notes about command execution.

jamemb_workcomp.exe is stored in the following folder:

JP1/Software-Distribution-Manager-installation-folder\jp1asset\exe

Function

This command releases area that has been extended automatically for the work file in Embedded RDB.

Format

jamemb_workcomp.exe

Return value

The command returns one of the following values:

Return value	Description
0	Normal termination
11	Option format is invalid
101 or greater	Terminated due to some other error

Notes about command execution

A user with Administrator permissions must execute jamemb_workcomp.exe.