10.2.1 Initializing an event database while the event service is active

If a JP1 event is being forwarded to another event server, refer to 10.2.2 Initializing an event database while the event service is stopped and initialize the event database.

To initialize an event database while the event service is active:

Back up the event database by using an OS command or by some other means.

Back up the event database if you want to verify its contents. You can output the contents to a CSV file by using the jevexport command.

For details on this command, see jevexport in 15. Commands.
Execute the jevdbswitch command twice.

Execute the jevdbswitch command two times to swap the event database out and in again.

The first time you execute this command, the active database (database currently in use) is replaced by the standby database. Also, the existing data in the standby database is erased. The second time you execute the jevdbswitch command, the existing data is cleared from both the active and standby databases.

For details on the jevdbswitch command, see jevdbswitch in 15. Commands.

Note: The procedure above cannot be used to clear out the memory in which the events are stored. A maximum of 2,000 events can be stored in memory during the transfer retry processing. If you want to delete the events by clearing the memory, initialize the event database by referring to the procedure described in 10.2.2 Initializing an event database while the event service is stopped.