7.1.5 Handling a shortage of database capacity
If a shortage of database capacity occurs while SLM - Manager is running, you must undo the SLM - Manager setup, extend the database area, and then set up SLM - Manager again.
You can determine whether there is a shortage of database capacity by checking the Windows event logs. From Windows Start menu, select Administrative Tools, then Event Viewer, and then check the Applications logs for the following messages:
No. |
Type |
Source |
Event |
Message |
|---|---|---|---|---|
1 |
Error |
JP1_ITSLM_Manager_DB_Service |
30001 |
KFPH22025-E |
2 |
Error |
JP1_ITSLM_Manager_DB_Service |
30001 |
KFPH22026-E |
If either of these messages has been output, take the appropriate corrective action by following the procedure described below.
- Organization of this subsection
(1) Before you start
Make a database backup. For details about how to back up the database, see 8.1.2 Backing up the database.
Estimate the size of the database area required for storing data. For details about how to estimate the size of the database area, see How to estimate the size of the database area in 9.12 jslmmgrsetup (sets up SLM - Manager) in 9. Commands. Provide as much free space as needed based on the estimation of the database area that is to be extended.
(2) Procedure
The procedure differs depending on whether you must use the jslmmgrimport command (imports service monitor information) to change all or some of the following items: IP address of the web server that provide the services to be monitored, and the IP address, service group name, and service name of SLM - UR.
If you need past data but do not need to change the IP address, service group name, or service name by using the jslmmgrimport command (imports service monitor information), perform the following procedure:
-
Back up all definition files.
For details about how to back up the definition files, see 8.1.1 Backing up the definition files.
-
Back up the database.
Perform steps 1 to 5 in (2) Procedure in 8.1.2 Backing up the database.
-
Terminate the SLM - Manager service SLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0).
-
Run the unsetup command for SLM - Manager.
For details about the unsetup command, see 9.13 jslmmgrunsetup (undoes SLM - Manager setup) in 9. Commands.
-
Create the options file (jp1itslm_setup.opt) needed for setting up SLM - Manager and specify values for the following definition items:
-
hdb_area_size
The database size you estimated in (1) Before you start
-
hdb_area_path (or if SLM is running in a cluster system, hdb_share_area_path)
The path of an area that contains the amount of free space specified in the definition item hdb_area_size (the absolute path that you specified for hdb_area_path when you backed up the definition files in step 2)
For details about the options file, see 9.12 jslmmgrsetup (sets up SLM - Manager).
-
-
Run the setup command for SLM - Manager.
For details about the setup command, see 9.12 jslmmgrsetup (sets up SLM - Manager) in 9. Commands.
-
If necessary, change the startup method of SLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0) to Manual (the default setting is Automatic).
-
Compare the definition files that were created in step 6 with the backup definition files that were created in step 1, and then, update the definition files if necessary.
-
Make sure that the SLM - Manager service SLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0) is started.
-
Restore the database.
Perform steps 5 to 7 in (2) Procedure in 8.1.5 Restoring the database.
If restoration of the database terminates normally, the database area has been expanded.
If any of the following conditions are met, perform the procedure described below.
- You need to use the jslmmgrimport command (imports service monitor information) to change all or some of the following items: the IP address, the service group name, and the service name.
-
You do not need past data.
-
Back up all definition files.
For details about how to back up the definition files, see 8.1.1 Backing up the definition files.
Run the jslmmgrexport command to create an export file.
For details about the jslmmgrexport command, see 9.9 jslmmgrexport (exports service monitor information) in 9. Commands.
-
Terminate the SLM - Manager service SLM - Manager Service (service name: JP1_ITSLM_MGR_Service).
-
Terminate the SLM - Manager service SLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0).
Run the unsetup command for SLM - Manager.
For details about the unsetup command, see 9.13 jslmmgrunsetup (undoes SLM - Manager setup) in 9. Commands.
Create the options file (jp1itslm_setup.opt) needed for setting up SLM - Manager and specify values for the following definition items:
-
hdb_area_size
The database size you estimated in (1) Before you start
-
hdb_area_path (or if SLM is running in a cluster system, hdb_share_area_path)
The path of an area that contains the amount of free space specified in the definition item hdb_area_size
For details about the options file, see 9.12 jslmmgrsetup (sets up SLM - Manager).
-
Run the setup command for SLM - Manager.
For details about the setup command, see 9.12 jslmmgrsetup (sets up SLM - Manager) in 9. Commands.
-
If necessary, change the startup method of SLM - Manager DB Service (service name: HiRDBEmbeddedEdition_JL0) to Manual (the default setting is Automatic).
-
Compare the definition files that were created in step 7 with the backup definition files that were created in step 1, and then, update the definition files if necessary.
Start the SLM - Manager service SLM - Manager Service (service name: JP1_ITSLM_MGR_Service).
-
Start the SLM - Manager service SLM - Manager Web Service (service name: JP1_ITSLM_MGR_Web_Service).
Run the jslmmgrimport command to import the export file created in step 2.
For details about the jslmmgrimport command, see 9.10 jslmmgrimport (imports service monitor information) in 9. Commands.
If the jslmmgrimport command terminates normally, the database area has been extended.