The distributed join installation feature and associated federated system functionality, as documented, are not currently supported with DB2 UDB Version 6.1.
The following statement should be added to the end of the first paragraph in the explanation:
The OVER clause can only be specified following a function that is supported as an OLAP function.
SQL0112N The operand of the column function "<name>" includes a column function, an OLAP function, a scalar fullselect, or a subquery.
Explanation: The operand of a column function cannot include a:
In a SELECT list, the operand of an arithmetic operator cannot be a column function that includes the DISTINCT keyword.
The statement cannot be processed.
User Response: Correct the use of the column function to eliminate the invalid expression and try again.
sqlcode: -112
sqlstate: 42607
SQL0120N A WHERE clause, GROUP BY clause, HAVING clause, SET clause, or SET transition-variable statement contains a column or OLAP function.
Explanation: A WHERE clause can contain a column function only if that clause appears within a subquery of a HAVING clause, and the argument of the column function is a correlated reference to a group. A GROUP BY clause can contain a column function only if the argument of the column function is a correlated reference to a column in a different subselect than the one containing the GROUP BY clause. A SET clause of an UPDATE statement or a SET transition-variable statement can only include a column function within a fullselect on the right hand side of an assignment. An OLAP function can only appear in the select list of a subselect.
The statement cannot be processed.
User Response: Change the statement so that the column or OLAP function is not used or used only where it is supported.
sqlcode: -120
sqlstate: 42903
SQL0206N "<name>" is not a column in an inserted table, updated table, or any table identified in a FROM clause, or is not a valid transition variable for the subject table of a trigger.
Explanation: This error can occur in the following cases:
The statement cannot be processed.
User Response: Verify that the column and table names are specified correctly in the SQL statement. For a SELECT statement, ensure that all the required tables are named in the FROM clause. For OLAP functions, ensure the column references in the window partition clause and the window order clause are to columns in the same subselect. For a subselect in an ORDER BY clause, ensure that there are no correlated column references. If a correlation name is used for a table, verify that subsequent references use the correlation name and not the table name.
For a CREATE TRIGGER statement, ensure that only new transition variables are specified on the left hand side of assignments in the SET transition-variable statement, and that any references to columns of the subject table have a correlation name specified.
sqlcode: -206
sqlstate: 42703
SQL1179W The "<object-type>" called "<object-name>" may require the invoker to have necessary privileges on data source objects.
Explanation: The object identified by "<object-name>" references an OLE DB table function or a nickname where the actual data exists at a data source. When the data source data is accessed, the user mapping and authorization checking is based on the user that initiated the operation.
If the "<object-type>" is SUMMARY TABLE, then the operation is refreshing the data for the summary table. The user that invoked the REFRESH TABLE or SET INTEGRITY statement that cause the refresh may be required to have the necessary privileges to access the underlying data source object at the data source.
If the "<object-type>" is VIEW, then any user of the view may be required to have the necessary privileges to access the underlying data source object at the data source.
In either case, an authorization error may occur when the attempt is made to access the data source object.
User Response: Granting of privileges to the view or summary table may not be sufficient to support operations that access the data from the data source. User access may need to be granted at the data source for the underlying data source objects of the view or summary table.
sqlcode: 1179
sqlstate: 01639
Replace the existing description of this message with the following:
SQL1592N The INCREMENTAL option is not valid with reason code "<reason-code>" since the table "<table-name>" cannot be incrementally processed.
Explanation: The cause is based on the "<reason-code>":
31 The table is not in check pending state if the INCREMENTAL
option is specified in a REFRESH TABLE statement.
32 The table is not a REFRESH IMMEDIATE summary table.
33 A Load Replace or Load Insert has occurred to the table if it
is a summary table.
34 A Load Replace has occurred to the table or the NOT LOGGED
INITIALLY WITH EMPTY TABLE option has been activated
after the last integrity check.
35 One of the following:
o New constraint has been added to the table itself or its
parents (or its underlying table if it is a summary table)
while in check pending.
o If it is a summary table, a Load Replace has occurred to any
underlying table of the table after the last refresh.
o If it is a summary table, some of its underlying table has
been taken out of check pending before it gets refreshed.
o If it is a summary table, some of its underlying tables were
loaded. The table was then refreshed, followed by some more
loads to the same underlying tables.
o Some of its parents (or underlying table if it is a summary
table) have been Load Replaced or checked for integrity
non-incrementally.
o The table was in check pending state before migration. Full
processing is required for the first time the table is
checked for integrity after migration.
o The table space containing the table or its parent has been
rolled forward to a point in time.
36 Incremental processing of a summary table is not currently
supported.
User Response: Do not specify the INCREMENTAL option. The system will check the entire table for constraint violations (or if it is a summary table, recompute the summary table definition query).
sqlcode: -1592
sqlstate: 55019
SQL1596N WITH EMPTY TABLE cannot be specified for "<table-name>" that is a REFRESH IMMEDIATE summary table or has a dependent REFRESH IMMEDIATE summary table.
Explanation: The table "<table-name>" is a REFRESH IMMEDIATE summary table or is referenced in the query for at least one REFRESH IMMEDIATE summary table. The WITH EMPTY TABLE clause cannot be specified when altering a table to ACTIVATE NOT LOGGED INITIALLY on a table with such a dependency.
The statement cannot be processed.
User Response: Remove the WITH EMPTY TABLE clause from the ALTER TABLE statement.
sqlcode: -1596
sqlstate: 42928
Reason code 14
Explanation: Table has an invalid primary key or unique constraint.
User Response: Table has an index that was erroneously used for a primary key
or unique constraint. Drop the primary key or unique constraint that uses the index.
This must be done in the release of the database manager in use prior
to the current release. Resubmit the database migration command
under the current release and then recreate the primary key or unique constraint.
Reason code 15
Explanation: Table does not have a unique index on the REF IS column.
User Response: Create a unique index on the REF IS column of the typed table
using the release of the database manager in use prior to the current release.
Resubmit the database migration command under the current release.
Reason code 16
Explanation: Table is not logged but has a DATALINK column with file link control.
User Response: Drop the table and then create the table without the not logged property.
This must be done in the release of the database manager in use prior
to the current release. Resubmit the database migration command
under the current release.
Reason Code 17
Explanation: Fail to allocate new page from the DMS system catalog table space.
User Response: Restore database backup onto its previous database manager system.
Add more containers to the table space. It is recommended to allocate 70%
free space for database migration. Move back to the current release and
migrate the database.
Possible new reason codes:
5. Exception table has DATALINK columns defined as file link control.
6. Table is in DataLink Reconcile Not Possible state.
7. Exception table cannot be specified when reconciling typed table.
8. Setting/Resetting table to/from DataLink Reconcile Pending/
DataLink Reconcile Not Possible state failed.
Possible solutions:
5. Ensure that the exception table has DATALINK columns all defined
as NO LINK CONTROL.
6. Look into the Administrative Guide to see how to take a table out of
DataLink Reconcile Not Possible state.
7. Do not specify an exception table when reconciling typed table.
8. Examine the db2diag.log for problem determination information
and contact an IBM Service Representative for assistance.
This message also applies to reconcile exception tables.
Two new reason codes have been added to message SQL4304N:
4 - Cannot load driver for "jdbc:default:connection". 5 - Cannot establish default context.
Additional diagnostic information is written to the db2diag.log file in each case.
New SQLSTATE text:
The view or summary table may require the invoker to have necessary privileges on data source objects.
Changed SQLSTATE text:
A WHERE, VALUES, GROUP BY, HAVING, or SET clause includes an invalid reference, such as a column or OLAP function.
New SQLSTATE text:
WITH EMPTY TABLE cannot be specified for a REFRESH IMMEDIATE summary table or a table that has a dependent REFRESH IMMEDIATE summary table.