| UNIX | OS/2 |
In DB2 Version 1, there was no way to indicate whether a privilege being granted was applicable to a user or to a group. In Version 2, a new field, called GRANTEETYPE, has been added to SYSCAT.DBAUTH, SYSCAT.INDEXAUTH, SYSCAT.PLANAUTH and SYSCAT.TABAUTH. GRANTEETYPE is either a 'U' to represent the GRANTEE is a user or 'G' to represent that the GRANTEE is a group.
During database migration, an attempt is made to determine whether existing privileges defined in the SYSIBM tables are for a user or a group. If the current privileges are for both a user and a group, only the user portion will be represented in the Version 2 database.
Loss of authorization if you are a member of a group which is also defined in the operating system as a user.
If this access is meant for groups (that is, where the environment variable DB2GROUPS=ON was used in Version 1), then execute the appropriate GRANT command for the appropriate access to the group.
| UNIX | OS/2 | WIN |
In Version 1, you could provide an authentication type on the CREATE DATABASE command. Beginning in Version 2, this option is ignored. All databases now have the same authentication type as the instance.
If the DB2 Version 5 instance authentication type is different than the Version 1 database authentication type, then authentication will behave differently after migration.
Make sure that the instance authentication type is the type you want for the databases within that instance.
| UNIX | OS/2 |
The SYSADM group must be explicitly set in the database manager configuration file.
This is automatically taken care of during migration, but a problem could arise if you use a script or command file to change SYSADM groups.
Update the script or command file to include the required changes in the database manager configuration file.
| UNIX | OS/2 |
Several security enhancements have been made to the product to make Version 2 and following versions more secure than Version 1. A few of the changes are listed here, however, this is not a complete list.
You may not be able to execute a DB2 command or API that you used to be able to execute. You will receive a "not authorized" type of SQLCODE.
Acquire the proper authorization for the task to be performed.
| UNIX | OS/2 | WIN | DB2 PE |
The following profile registry values or environment variables are obsolete:
There is no longer a need for this profile registry value. There is no need to disable DB2 support for multi-threaded applications.