Ingres Version: All OS: All Q: How is table level checkpoointing implemented?
You can rollforward a table from a database level checkpoint – though you will get warnings about the tables you didn’t rollforward possibly being logically/physically inconsistent. However, as soon that table is modified (modify statement not data changes) a flag is set which will stop you doing either checkpoints or rollforwards at table level on that table. This flag is re-set by an offline database checkpoint but not an online checkpoint. This flag is also set/unset by doing modify mytable to table_recovery_allowed | table_recovery_disallowed So if you want to do a table level recovery from a database checkpoint and you get the error – “E_DM135F_RFP_NO_TBL_RECOV Table level recovery disallowed for table mytable” – you can modify the table to table_recovery_allowed and it will let you do the rollforward. See the SQL Reference Guide for the modify statement. It is intended to enable you to enforce logical consistency. If table XXX should never be out of step with YYY then if you modi
