Question & Answer
Why is error "SQL0818N: A timestamp conflict occurred" received when rolling forward a tablespace?
This can occur after an unexpected failure with DB2. For example, if an I/O error occurs during crash recovery, the table space will be left in rollforward pending state after the crash recovery. Once the underlying I/O error is corrected, the rollforward of the table space may fail with an SQL0818N error.
The explanation associated with the SQL0818N error message says "the timestamp generated by the precompiler at precompile time is not the same as the timestamp stored with the package at bind time". In this case, the package associated with the ROLLFORWARD command is problematic.
The solution associated with the SQL0818N error is to bind the application again, using the bind file for the program that matches the object module. In this case, the appropriate BIND commands are as follows:
db2 connect to <dbname>
db2 bind <path>/@db2ubind.lst blocking all grant public action add
16 June 2018