With the fix for both bugs in place the x100 server is not called in any of the following cases:\n\n    The database was created without x100 support at all (createdb -no_x100,  you can see X100 supported: No  in the infodb output)\n    The database was created with x100 support, but x100 support was disabled later and there was no x100 table created. (The Status line in the infodb output (infodb -get_status) contains X100_DISABLED but does not contain X100_EXIST.\n    The x100 support was re-enabled for the database after the last checkpoint, i.e. that checkpoint was taken while x100 was disabled. (In the infodb output the mode column in the Checkpoint History for Journal section for the last checkpoint contains NOX100 (infodb -get_ckp_mode). Please note that this status is added to the last and already existing checkpoint when the x100 support is re-enabled with alterdb)\n\nPlease note that 2) implies that the x100 server wakes up even if the x100 support was disabled, but the X100_EXIST flag is set. This flag is set when the very first x100 table is created, but isn't unset when the last x100 table is dropped. To get the X100_EXIST flag removed run sysmod after the last x100 table was dropped.