| |
- Causa
- SQLDA INCLUDES integer1 SQLVAR ENTRIES, BUT integer2 ARE REQUIRED BECAUSE AT LEAST ONE OF THE COLUMNS BEING DESCRIBED
IS A DISTINCT TYPE
Given that at least one of the columns being described is a distinct type, space should be provided
for the extended SQLVAR entries in addition to the base SQLVAR entries.
The value of SQLN, integer1, indicates that there are not enough SQLVAR entries for the base and extended SQLVAR entries.
The total number of SQLVAR entries that are required depends on whether USING BOTH was specified
(n is the number of columns being described):
- With USING BOTH, space should be allocated for 3n SQLVAR entries.
- Otherwise, space should be allocated for 2n SQLVAR entries.
The number of SQLVAR entries that are needed to return all of the information about the columns is integer2.
Note: in the case of DESCRIBE INPUT, each reference to column would actually be parameter.
- Ação do sistema
- DB2 has set the SQLDAID 7th byte flag "on" because sufficient space was not provided for the extended SQLVAR entries.
The value of the 7th byte flag indicates how many SQLVAR entries are needed for each column.
Additionally, because there were enough SQLVAR entries for the base SQLVARs, DB2 has set the fields of the base SQLVAR entries.
However, DB2 has not set any extended SQLVAR entries.
- Resposta ao Desenvolvedor
- If there is no need for the additional information about the distinct type(s), then no action is required unless USING BOTH was specified (in
which case additional SQLVAR entries must be provided for the labels).
If the distinct type information is needed, the value of the SQLN field in the SQLDA should be increased to integer2 (after making
sure that the SQLDA is large enough to support that amount) and the statement should be resubmitted.
SQLSTATE: 01594
|
| |
