DB2 High Performance Unload (HPU) offers two different methods of processing the LOCK YES and QUIESCE YES combination.

Technote (FAQ)


Question

How does DB2 High Performance Unload (HPU) process LOCK YES and QUIESCE YES?

Answer

Depending on the status of the DB2 objects, HPU offers two different methods of processing a combination of LOCK YES and QUIESCE YES:

Standard method
Use this method when the Tablespace is not COPY PENDING, and when the indexes are accessible, not CHECK/REBUILD pending, and not DEFINE NO. 

1. LOCK TABLE in SHARE mode
2. QUIESCE          
                               
Alternative method
Use this method in any other case (for example, if the Tablespace is COPY PENDING, or if the index is unavailable or CHECK/REBUILD pending).

1. LOCK TABLE in EXCLUSIVE mode
2. STOP TABLESPACE
3. START TABLESPACE in RO
4. LOCK TABLE in SHARE MODE
5. If the database is defined ROSHARE R, STOP TABLESPACE
6. START TABLESPACE in the initial state


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 Tools for z/OS
DB2 High Performance Unload

Software version:

All Versions

Operating system(s):

OS/390, z/OS

Reference #:

1064001

Modified date:

2002-09-20

Translate my page

Machine Translation

Content navigation