The LOG option that you specify when you run
the LOAD and REORG utilities has different results depending on the
logging attribute of the table space that is being logged.
The following tables
show how the logging attribute of the
utility and the logging attribute of the table space interact:
Table 1. Attribute interaction for LOB table spaces| LOAD or REORG keyword |
Table
space logging attribute |
What is logged |
Table space status after completion |
|---|
| LOG YES |
LOGGED |
Control records
and LOB data redo information.
LOB data undo information is never logged for LOB table spaces. |
No pending status |
| LOG YES |
NOT LOGGED |
Control information. |
No
pending status |
| LOG NO |
LOGGED |
Nothing. |
COPY-pending |
| LOG NO |
NOT LOGGED |
Nothing. |
No pending
status |
Table 2. Attribute interaction for
non-LOB table spaces| LOAD or REORG keyword |
Table space logging attribute |
What is logged |
Table space
status after completion |
|---|
| LOG YES |
LOGGED |
Control records and data. |
No pending status |
| LOG
YES |
NOT LOGGED |
LOG
YES is changed to LOG NO. |
See Table 3 |
| LOG NO |
LOGGED |
Nothing. |
COPY-pending |
| LOG NO |
NOT
LOGGED |
Nothing. |
See Table 3 |
The following table shows the possible table space
statuses
for non-LOB tables spaces that are not logged:
Table 3. Status
of non-LOB table spaces that are not logged, after LOAD or REORG with
LOG NO keyword| Inline copy |
Records discarded |
Table
space status |
|---|
| Yes |
No |
No pending status |
| Yes |
Yes |
ICOPY-pending |
| No |
not applicable |
ICOPY-pending |