Specification of the ONLY keyword with a table now requires that the user have SELECT privilege on all subtables of the specified typed table. Similarly, specification of the ONLY keyword with a view now requires that the user have SELECT privilege on all subviews of a specified typed table. Previous versions only required SELECT privilege on the specified table or view.

Symptom:

There are two possible symptoms:

An authorization error (SQLCODE -551, SQLSTATE 42501) occurs when rebinding a package containing an SQL statement that specified the ONLY keyword in a FROM clause, if the authorization ID under which the package was bound lacks SELECT privilege on the subtables of the named typed table (or view).
If the definition of a view or trigger contains the keyword ONLY used in a FROM clause, the view or trigger will continue to work normally. However, the definition of the view or trigger can no longer be used to create a new view or trigger unless the creator holds SELECT privilege on all the subtables of the named table (or view).

Resolution:

The authorization ID that needs to rebind a package or to crate a new view or trigger should be granted SELECT privilege on all subtables (and subviews) of the table (or view) specified following the ONLY keyword.

Obsolete Profile Registry and Environment Variables in DB2 Universal Database Version 6

UNIX

OS/2

WIN

DB2 PE

Change:

The following profile registry values or environment variables are obsolete:

DB2_VECTOR

Resolution:

There is no longer a need for these profile registry or environment variables.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]