Job Management Partner 1/Base User's Guide
The procedure for initializing an event database while the event service is stopped depends on whether JP1 events are being forwarded from the event server to be initialized. The following describes the procedure for initializing an event database for each case.
- Organization of this subsection
- (1) When JP1 events are forwarded from the event server to be initialized
- (2) When JP1 events are not forwarded from the event server to be initialized
(1) When JP1 events are forwarded from the event server to be initialized
Work out the start serial number from the JP1 events forwarded to another event server and initialize the event database:
- On the destination event server, locate the serial number of the last JP1 event forwarded from the event server to be initialized.
Locate the serial number in either of the following ways. If JP1 events are forwarded to more than one event server, search on all the destination event servers.
- Event search in JP1/IM - View:
- Perform an event search from JP1/IM - View to find the JP1 events registered on the destination event server.
- For details on searching for JP1 events, see the manual Job Management Partner 1/Integrated Management - Manager Administration Guide.
- Outputting the event database contents to a CSV file:
- Using the jevexport command, output the contents of the event database on the destination event server to a CSV file for verification.
- For details on this command, see jevexport in 13. Commands.
- Execute the jevdbinit command. In the -s option, specify the start serial number in the event database.
Execute the following:
The event database is re-created using the start serial number specified in the -s option.
jevdbinit -s event-database-serial-number-found-at-step1+1 {-b | -n}
(2) When JP1 events are not forwarded from the event server to be initialized
Execute the following command to initialize the event database:
jevdbinit {-b | -n}This command deletes and re-creates the event database. The data serial numbers are inherited from the original database.
If the database is corrupted and you want to back it up, specify the -b option. If you do not want to back up the database, specify the -n option. You can output the contents to a CSV file by using the jevexport command.
For details on the jevdbinit command and backed up databases, see jevdbinit in 13. Commands.
Initialization fails at execution of the jevdbinit command if the serial numbers in the event database cannot be carried over. If the KAJP1789-E message is output, re-create the event database by specifying 0 as the start serial number in the -s option.
jevdbinit -s 0 {-b | -n}
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.