jevdbinit
- Organization of this page
Function
The jevdbinit command initializes the event database. At command execution, the existing data is deleted and the event database is re-created.
The new start serial number is the number you specify or the number carried over from the event database before the data was deleted.
You can create a backup of the event database before initialization. Using the jevexport command, you can output the backup file to a CSV-format file. You cannot restore the backup file.
For details on the event database initialization, see 10.2 Initializing the event database.
Format
jevdbinit [-h event-server-name] [-s start-serial-number-in-event-database] [-f] {-b | -n}
Required execution permission
In Windows: Administrators (If User Account Control (UAC) for Windows is enabled, you must execute the command from the administrator console.)
In UNIX: Superuser or JP1/Base administrator permission
Command directory
- In Windows:
-
installation-folder\bin\
- In UNIX:
-
/opt/jp1base/bin/
Arguments
-h event-server-name
Specify the name of the event server at which to initialize the event database. If you omit this option, the logical host name set in the environment variable JP1_HOSTNAME is assumed as the event server name. If the environment variable JP1_HOSTNAME is not set, the event server name is assumed to be the same as the local host name. Specify the event server name as a character string of no more than 255 bytes.
-s start-serial-number-in-event-database
Specify the start serial number of the event database when it is re-created after initialization. The database will be created with the serial number specified in this option. The specifiable range is 0 to 2,147,483,647.
If you omit this option, the serial numbers carry on from the deleted event database.
-f
If you omit this option, a message asks if you are sure you want to execute the command. (The displayed message is Is This OK?[Y/N].) Specify this option if user confirmation is unnecessary.
-b
Specify this option to back up the event database before it is initialized. You must specify either -b or -n.
The backup files are saved to the same directory as the event database. The following files are backed up:
Event database file name |
Backup file name |
---|---|
IMEvent{0|1}.idx |
0IMEvent{0|1}.idx |
IMEvent{0|1}.dat |
0IMEvent{0|1}.dat |
IMEvent{0|1}.fwd |
0IMEvent{0|1}.fwd |
Note that the disk space occupied by the event database doubles when it is backed up. If you have kept a previous database backup file, it will be deleted when you specify the -b option.
-n
Specify this option if you do not want to back up the event database before it is initialized. You must specify either -b or -n. If you have kept a previous database backup file, it will remain when you specify the -n option.
Notes
-
You cannot execute this command while the event service is active.
-
You cannot start the event service while this command is executing.
-
If the event database is empty, executing this command returns a value of 7 (indicating that the event database is corrupted), but you can ignore this result.
-
If you modified the serial number of the event database by using the jevdbinit command with the -s option specified on the host with JP1/IM - Manager installed, you need to set up the integrated monitoring database again. You also need to re-create the command execution log in JP1/IM - Manager. See the chapter on JP1/IM system maintenance in the JP1/Integrated Management - Manager Administration Guide.
Return values
0 |
Normal end |
1 |
Invalid argument |
2 |
Insufficient execution permission |
3 |
I/O error |
4 |
Insufficient memory |
5 |
Undefined event server name |
6 |
No event database |
7 |
The event database is corrupt. |
8 |
The event database cannot be initialized because the event service is active. |
255 |
Other error |