DB2 10.5 for Linux, UNIX, and Windows

Recovering inoperative summary tables

Summary tables can become inoperative as a result of a revoked SELECT privilege on an underlying table.

About this task

The following steps can help you recover an inoperative summary table:

Determine the statement that was initially used to create the summary table. You can obtain this information from the TEXT column of the SYSCAT.VIEW catalog view.
Re-create the summary table by using the CREATE SUMMARY TABLE statement with the same summary table name and same definition.
Use the GRANT statement to re-grant all privileges that were previously granted on the summary table. (Note that all privileges granted on the inoperative summary table are revoked.)

If you do not want to recover an inoperative summary table, you can explicitly drop it with the DROP TABLE statement, or you can create a new summary table with the same name but a different definition.

An inoperative summary table only has entries in the SYSCAT.TABLES and SYSCAT.VIEWS catalog views; all entries in the SYSCAT.TABDEP, SYSCAT.TABAUTH, SYSCAT.COLUMNS and SYSCAT.COLAUTH catalog views are removed.