After the time is moved back, if you display the time that was recorded in a HiRDB file before the time was moved back, a future point of time might be displayed.

HiRDB maintains the index information file creation time in the table management information within RDAREAs, and in the index information files. During batch creation of indexes, to ensure integrity between the data in the index information file and the table data, HiRDB checks whether the maintained times match and terminates abnormally if they do not match.

If an index information file is created after the system time is moved back and you specify an index information file that was created before the time was moved back, a problem could result. That is, if the times in the table management information within RDAREAs match, executing batch creation of indexes does not cause an error, and as a result the table and the indexes lose correspondence. To restore correspondence, you must re-create the indexes (with the -k ixrc option).

After the time is moved back, if you execute the facility for predicting reorganization time of the database condition analysis utility (pddbst), the time for scheduled database maintenance might be moved forward (from where it had been before the time was moved back), or an instruction for unnecessary maintenance might be issued.

When the database recovery utility (pdrstr) is executed with the -T, -d, and -l options specified after the time is moved back, the database is damaged if the log input sequence is incorrect. Therefore, the unload log files before and after moving back the time must be managed separately.