Space announcement


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Recovery of XML objects

NGT Recover supports the recovery of XML objects. NGT Recover also supports REBUILD requests for NodeID indexes.

When an XML column is created, DB2 implicitly creates the following XML objects to support the XML column:

  • DocID column in the base table—created on the base table and uniquely represents each row.

  • DocID index

  • XML table

  • XML table space containing the XML table

  • NodeID index on the XML table

For a point-in-time recovery, you must recover the following XML-related objects to the same point:

  • Base table—contains the base table, where the logical XML column is stored

  • XML table space—contains the XML auxiliary table, where the data is physically stored

  • NodeID index on the XML table

  • DocID index


In the CREATE statement and in the DB2 catalog, XML indexes are defined on the XML base table. However, the XML indexes are actually on the XML table (table type 'P').

Because of this, the IBM RECOVER utility does not process XML indexes in INDEX(ALL) TABLESPACE baseTableSpace requests. In order to process XML indexes with an INDEX(ALL) request, you must specify TABLESPACE XMLTableSpace.

For XML indexes, NGT Recover behavior is the same as that of IBM.

The following restriction applies to the recovery of an XML object:

  • A point-in-time recovery can always convert an XML object from extended to basic RBA format. However, the point-in-time recovery for an XML table space cannot convert from basic to extended format.

Related topic

Was this page helpful? Yes No Submitting... Thank you