Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see UNLOAD PLUS for DB2 13.1.

Object status with DIRECT YES

This topic describes initial database and table space status requirements, and describes how UNLOAD PLUS changes the status of the objects during and after processing.

Initial status for DIRECT YES

To unload your table space when using DIRECT YES, the table space that you are unloading and the database associated with that table space cannot be in any of the following statuses:

  • Auxiliary CHECK pending (ACHKP)
  • CHECK pending (CHKP)
  • Group RECOVER pending (GRECP)
  • Logical page list (LPL)
  • Page set REBUILD pending (PSRBD)
  • REBUILD pending (RBDP)
  • Logical part REBUILD pending (RBDP*)
  • RECOVER pending (RECP)
  • Refresh pending (REFP)
  • REORG pending (REORP)
  • Restart pending (RESTP)
  • Utility restrictive state, utility exclusive control (UTUT)
  • Write error page range (WEPR)

In addition, the database that is associated with the table space that you are unloading cannot be in utility only (UT) status. This restriction does not apply when you specify SHRLEVEL CHANGE CONSISTENT NO QUIESCE NO.

If you are unloading from copies or VSAM linear data sets, the status of the table space is irrelevant.

Status changes during DIRECT YES processing

The following sections describe how object status changes during unload processing for different types of unload jobs.

For more information about the SHRLEVEL option, see SHRLEVEL.

SHRLEVEL REFERENCE

SHRLEVEL REFERENCE restricts object status to read-only during UNLOAD PLUS processing. UNLOAD PLUS then externalizes the pages of the table space. When operating on partitioned objects, access is restricted only to those partitions that are being unloaded. When UNLOAD PLUS processing completes, the utility restores the object to its original status.

SHRLEVEL CHANGE

SHRLEVEL CHANGE allows read and write access to the table space during unload processing. UNLOAD PLUS does not have concurrency issues when you specify SHRLEVEL CHANGE CONSISTENT NO. However, if you specify SHRLEVEL CHANGE CONSISTENT YES, access to the table space is briefly restricted. For more details, see the following sections.

CONSISTENT NO

When you specify SHRLEVEL CHANGE CONSISTENT NO, access to the object is not restricted.

The following table describes status changes based on the value of the QUIESCE option when you specify CONSISTENT NO:

QUIESCE option

Status change

QUIESCE or QUIESCE YES

When you specify SHRLEVEL CHANGE CONSISTENT NO QUIESCE YES, UNLOAD PLUS briefly restricts access to the object while externalizing pages from the Db2 buffer pool.

QUIESCE NO

When you specify SHRLEVEL CHANGE CONSISTENT NO QUIESCE NO, UNLOAD PLUS does not restrict access to the objects nor does it externalize pages from the Db2 buffer pool.

Warning

Due to this process, UNLOAD PLUS might not process any updated pages in the buffer pool. In addition, if encountering any pages that have uncommitted data, UNLOAD PLUS unloads the uncommitted data.

CONSISTENT YES

When you specify SHRLEVEL CHANGE CONSISTENT YES, UNLOAD PLUS briefly restricts access to the table space while externalizing the pages.

Related topics

DIRECT-YES-processing-phases

UNLOAD-PLUS-serialization-and-concurrency

Operational-considerations

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*