12.1.5 Concurrent execution of pdpgbfon and other functions

This subsection explains execution of pdpgbfon concurrently with other functions.

Organization of this subsection
(1) Whether pdpgbfon can be executed concurrently with SQL statements
(2) Whether pdpgbfon can be executed concurrently with a UAP with a local buffer specified

(1) Whether pdpgbfon can be executed concurrently with SQL statements

The following table shows whether pdpgbfon can be executed concurrently with SQL statements.

Table 12-1 Whether pdpgbfon can be executed concurrently with SQL statements

SQL statementTarget of operation in the same RDAREA
Different table (or index)Same table (or index)
RetrievalNOWAIT specifiedYY
WITH SHARE specifiedYY
WITH EXCLUSIVE specifiedYY
FOR UPDATE clause specifiedYY
OtherYY
UpdatingNEXT VALUE clause specifiedYY
OtherYY
AdditionNEXT VALUE clause specifiedYY
OtherYY
DeletionYY
LOCK statementSHARE specifiedYY
EXCLUSIVE specified (non-shared table)YY
EXCLUSIVE specified (shared table)NN
Table deletionYN#
IndexesDefinitionYY
DeletionYN#
Deletion of all rowsYN
Table definition modificationYN#
Sequence generator definitionY (there is no need to identify the same table because the sequence generator definition is not an SQL statement that is executed on tables)
Sequence generator deletionY (there is no need to identify the same table because the sequence generator definition is not an SQL statement that is executed on tables)
Legend:
Y: Can be executed concurrently.
N: Cannot be executed concurrently (if attempted, lock-release wait status is applied).
#
While this utility is running, table deletion, index deletion, and modifying table definitions cannot be performed on a table or an index that is being processed by this utility. However, in some cases these operations might be possible depending on the timing, as described below.
A table that has been added by modifying table definitions cannot be processed by pdpgbfon. However, if table definitions are modified, resulting in deletion of a table, index, or RDAREA subject to processing by pdpgbfon, KFPA11815-E is output.

(2) Whether pdpgbfon can be executed concurrently with a UAP with a local buffer specified

The following table shows whether pdpgbfon can be executed concurrently with a UAP with a local buffer specified.

Table 12-2 Whether pdpgbfon can be executed concurrently with a UAP with a local buffer specified

Local buffer specification methodTarget of operation in the same RDAREA
pd_uap_wait operandpdlbuffer operandDifferent tableDifferent indexSame tableSame index
Y specified-r specifiedN#1N#1N#1N#1
-i specifiedYYYN#1
N specified-r specifiedN#2N#2N#2N#2
-i specifiedYYYN#2
Legend:
Y: Can be executed concurrently.
N: Cannot be executed concurrently.
#1
If attempted, lock-release wait status is applied.
#2
The UAP terminates with an error.