Starting a table space or index space that has restrictions

Db2 can make an object unavailable for a variety of reasons. Typically, in those cases, the data is unreliable, and the object needs some attention before it can be started.

About this task

An example of such a restriction is when the table space is placed in COPY-pending status. That status makes a table space or partition unavailable until an image copy of the object is taken.

Important: These restrictions are a necessary part of protecting the integrity of the data. If you start an object that has restrictions, the data in the object might not be reliable.

However, in certain circumstances, it might be reasonable to force availability. For example, a table might contain test data whose consistency is not critical.

Procedure

Begin general-use programming interface information.To start an object that has restrictions:

Issue the START DATABASE command with the ACCESS(FORCE) option.

This command releases most restrictions for the named objects. These objects must be explicitly named in a list following the SPACENAM option.

Example

For example:

-START DATABASE (DSN8D13A) SPACENAM (DSN8S13E) ACCESS(FORCE)

Db2 cannot process the START DATABASE ACCESS(FORCE) request if postponed-abort or indoubt units of recovery exist. The RESTP (restart-pending) status and the AREST (advisory restart-pending) status remain in effect until either automatic backout processing completes or you perform one of the following actions:

  • Issue the RECOVER POSTPONED command to complete backout activity.
  • Issue the RECOVER POSTPONED CANCEL command to cancel all of the postponed-abort units of recovery.
  • Conditionally restart or cold start Db2.
Db2 cannot apply the START DATABASE ACCESS(FORCE) command to that object if a utility from a previous release of Db2 places an object in one of the following restrictive states:
  • UTRO (utility restrictive state, read-only access allowed)
  • UTRW (utility restrictive state, read and write access allowed)
  • UTUT (utility restrictive state, utility exclusive control)

To reset these restrictive states, you must start the release of Db2 that originally ran the utility and terminate the utility from that release.

End general-use programming interface information.