Messages Reference
SQL3802N
An invalid quiesce mode "<quiesce-mode>" was encountered.
Cause: An invalid quiesce mode was passed to the quiesce API.
Action: Resubmit the command with the correct parameters.
SQL3804N
The index is invalid.
Cause: An invalid index was encountered during the processing of a
utility command.
Action: Check in the
Administration Guide
to determine the appropriate
way to revalidate the index and resubmit the command after the
condition is corrected.
SQL3805N
The state of the application or of one or more table spaces for
the table specified prohibits the loadapi action or quiescemode
"<action>". Reason code = "<reason-code>".
Cause: The loadapi action (either quiescemode or callerac) passed to the
load API is in conflict with either the state of the application or
the state of one or more table spaces for the table.
The possible reason codes are as follows:
- 01
- the state of one of the table spaces for the table specified
prohibits the loadapi action or quiescemode.
- 02
- the application is not at the start of its logical unit of work.
This condition prohibits the load action specified.
- 03
- the state of the application prohibits the load action
specified.
- 04
- one or more of the table spaces for the table is already quiesced
by the maximum number of quiescers.
- 05
- system catalog table space cannot be quiesced.
- 06
- load copy not allowed when table space is in backup pending state.
- 07
- Attempt to restart a load at an incorrect phase
Action: Corresponding to each of the above reasons:
- 01
- Resubmit the command with the correct loadapi action or
quiescemode, or correct the state of the table spaces for the table.
- 02
- Resubmit the command with the correct load action or complete the
current logical unit of work by issuing either a COMMIT or ROLLBACK.
- 03
- Resubmit the command with the correct load action.
- 04
- Determine which table spaces for the table have reached the maximum
number of quiescers. QUIESCE RESET these table spaces.
- 05
- Resubmit the command with a table which is not in the system
catalog table space.
- 06
- Resubmit the command omitting the copy parameter
- 07
- Determine at which phase the load should be restarted and
resubmit the command with the correct phase.
SQL3806N
Not all table constraints are off for the table to be loaded.
Cause: One or more constraints for the table to be loaded are still on
when the load API is invoked.
Action: Resubmit the command after all table constraints are turned
off.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]