Regards
JJ
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
The DB2 products on the workstation platforms have historically
folded userids to uppercase for use as authorization ids and
schema names. Problems could occur therefore if DB2 allowed
mixed case userids such as 'HELLO', 'hello', or 'HeLlO', etc.
DB2 would fold all such combinations to one upper case id of 'HELLO'. Therefore, the three individual users, 'HELLO', 'hello',
and 'HeLlO', would all share all of the privileges granted to
'HELLO'. There would be no way to prevent users 'hello' and 'HeLlO' from enjoying the same privileges granted to user 'HELLO' and no way to grant different privileges to users 'hello' and 'HeLlO'.
Some people think that uppercase authorization ids and schema names are the standard within the SQL standards but I am not sure if this is true or not - no one I have spoken too has ever confirmed this. Regardless, DB2 on the workstation platforms uses
only upper case.
Since lower case userids seem to be used more on the UNIX platforms, DB2 therefore only permits the use of lower case userids on these platforms. DB2 of course folds all userids to
upper case before use. I presume you are using DB2 on a UNIX platform such as AIX.
I understand that DB2 Version 2.1 did permit the use of upper case and lower case userids on UNIX platforms; however this security exposure was removed in DB2 UDB Version 5 so now, only
lower case userids are allowed.
On the Intel platforms (OS/2, Windows NT), upper case userids
(and not lower case) are allowed because userids are generally
upper case on these platforms.
--
Posted via CNET Help.com
http://www.help.com/