Job Management Partner 1/Software Distribution Setup Guide

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

10.3.7 Reorganizing the database in an Embedded RDB environment

Reorganizing the database is a maintenance task performed as part of regular operations. For more information about when to reorganized the database, see 5.2.3(2) Reorganizing the database in the manual Administrator's Guide Volume 2.

Notes
  • Before you reorganize the Asset Information Manager Subset database, stop the services in the following order.
    1. World Wide Web Publishing Service or World Wide Web Publishing
    2. Commands and tasks of the Asset Information Synchronous Service and Asset Information Manager Subset
    3. JP1/Client Security Control - Manager (applicable if JP1/CSC is linked)
    To use Asset Information Manager Subset after you have used the Database Manager, start the services in the reverse order from that listed above.
  • If a connection pool has been set up in the ODBC database, the connected status will not change from the time that the Asset Information Manager Subset job was stopped until the timeout time set in the connection pool elapses. Therefore, wait for the connected status to change before reorganizing the database.
  • If database capacity is still insufficient after reorganizing the Asset Information Manager Subset database, expand the database capacity.

There are two ways to reorganize the Asset Information Manager Subset database in an Embedded RDB environment. One is by using Database Manager of Asset Information Manager Subset, and the other is by using jamemb_reorganization.bat.

The following subsections explain these methods.

Organization of this subsection
(1) How to reorganize the database in an Embedded RDB environment
(2) Using the command to reorganize the database in an Embedded RDB environment
(3) Releasing area whose size was increased automatically in an Embedded RDB work file
(4) Setting an execution timeout for reorganizing Embedded RDB

(1) How to reorganize the database in an Embedded RDB environment

To reorganize the Asset Information Manager Subset database in an Embedded RDB environment:

  1. In the Database Manager dialog box, choose Reorganize Embedded RDB and then click the Next button.
    The Reorganize Embedded RDB dialog box appears.

    Figure 10-21 Reorganize Embedded RDB dialog box

    [Figure]

  2. Click the Execute button.
    The Asset Information Manager Subset database is reorganized.

(2) Using the command to reorganize the database in an Embedded RDB environment

This subsection describes the function, format, options, return values, and command execution notes of jamemb_reorganization.bat, which reorganizes the Asset Information Manager Subset database in an Embedded RDB environment.

jamemb_reorganization.bat is stored in the following folder:

Asset-Information-Manager-Subset-installation-folder\exe

If reorganization fails, the Asset Information Manager Subset database can no longer be used. In such a case, you must restore the backup data and recover the Asset Information Manager Subset database.

(a) Function

jamemb_reorganization.bat reorganizes the Asset Information Manager Subset database.

(b) Format
jamemb_reorganization.bat port-number user-ID password -o result-file-path [-y]
(c) Options

port-number
Specifies the database connection port number that was specified when Asset Information Manager Subset was installed. To determine the port number that was set, check PDNAMEPORT in the HiRDB.ini file, which is stored in Asset-Information-Manager-Subset-installation-folder\aimdb\conf\emb. Specification of this option is mandatory.

user-ID, password
Specifies the values that were set in Login ID in Database Information in the Server Setup dialog box. Specification of this option is mandatory.

-o result-file-path
Specifies the full path of the files to which the execution results are to be output. Specification of this option is mandatory.

-y
Specifies that reorganization processing is to start without waiting for a response from the keyboard.
When this option is omitted, command execution waits for entry of a response from the keyboard. You can cancel execution by pressing the Ctrl + C keys.
(d) Return value

Returns one of the following return values:

Return value Description
0 Normal termination. You can check the results files for the reorganization details.
11 Invalid option specification.
101 or greater Terminated with another error.
(e) Notes about command execution
(f) Execution example
jamemb_reorganization.bat 30010 admin admin -o C:\temp\backup\kekka.log -y

(3) Releasing area whose size was increased automatically in an Embedded RDB work file

When a new Asset Information Manager Subset database is created in an Embedded RDB environment and the automatically grow option is enabled, free space may decrease dramatically on the drive where the database is created.

This may be caused by automatic size increase of Embedded RDB work files (files for temporary storage of information needed when SQL statements execute).

The size for work files is increased automatically when a large amount of search results is output. If there is not enough space on the drive where the Asset Information Manager Subset database has been created, you can release the automatically increased area for work files by executing jamemb_workcomp.exe.

This subsection describes the function, format, return values, and command execution notes of jamemb_workcomp.exe, which releases the automatically increased area for Embedded RDB work files.

jamemb_workcomp.exe is stored in the following folder:

Asset-Information-Manager-installation-folder\exe

(a) Function

jamemb_workcomp.exe releases the automatically increased area for Embedded RDB work files.

(b) Format
jamemb_workcomp.exe
(c) Return value

Returns one of the following return values:

Return value Description
0 Normal termination.
11 Invalid option specification.
101 or greater Terminated with another error.
(d) Notes about command execution

Execute jamemb_workcomp.exe as a user with administrator permissions.

(4) Setting an execution timeout for reorganizing Embedded RDB

While you are reorganizing Embedded RDB, if an error (such as a communication error or disk error) occurs, the reorganization process might not respond.

If you cannot forcibly terminate the reorganization process that does not respond because, for example, Embedded RDB was reorganized automatically by the Windows task feature or by JP1/AJS, perform the following steps to set an execution timeout for the reorganization process.

Notes
  • Before you set an execution timeout for reorganizing Embedded RDB, stop all the services, commands, and tasks of Asset Information Manager on the asset management server.
  • Stop the services of Asset Information Manager in the following order.
    1. World Wide Web Publishing Service or World Wide Web Publishing
    2. Asset Information Synchronous Service, and Asset Information Manager Subset commands and tasks
    3. JP1/Client Security Control - Manager (applicable if JP1/CSC is linked)
    To use Asset Information Manager Subset after you have changed an execution timeout for reorganizing Embedded RDB, start the services in the reverse order from that listed above.
  1. To terminate Embedded RDB, execute the jamemb_dbstop.bat command that is stored in JP1/Software-Distribution -installation-directory\jp1asset\exe.
    Check the message to make sure that Embedded RDB has terminated.
  2. Use a text editor to open the pdsys file that is stored in JP1/Software-Distribution-installation-directory\jp1asset\jp1asset\aimdb\conf.
  3. Add a line for set pd_utl_exec_time = execution timeout for reorganizing Embedded RDB in the pdsys file. #1
  4. Execute the jamemb_dbstart.bat command that is stored in JP1/Software-Distribution -installation-directory\jp1asset\exe to start the Embedded RDB.

#1
pd_utl_exec_time = execution timeout for reorganizing Embedded RDB To set an execution timeout for a command to manipulate the Embedded RDB, specify an execution timeout in the range from 0 to 35791394 (minutes) for the command. If you do not specify a value, or specify 0, the execution timeout will not be set.
If the command does not complete after the time specified for the execution timeout has elapsed, the command being executed will be abnormally terminated.
For this operand, specify a value that allows for some extra time compared to the actual time that the command requires for execution.
For example, if reorganizing the database requires a maximum of approximately 90 minutes, specify pd_utl_exec_time=120 for the timeout, just in case. This is because if a process that normally finishes in 90 minutes has not responded after 120 minutes, we can assume that an error causing the command not to respond has occurred.
Sample
#
#------------------------------------------------------------------
# set form 
#
:
 
:
set pd_utl_exec_time = 120
#
#------------------------------------------------------------------
# putenv form 
#