Release Notes

1Secure environments (Windows)

1You might experience file permission problems if you are using DB2 1Universal Database on Windows and are not an administrator on the Windows 1system. If you receive an SQL1035N, SQL1652N, or SQL5005C error 1message, possible causes and workarounds are shown in the following 1information:

1User does not have sufficient authority on the sqllib directory

1

1Problem

1User receives an SQL1035N or SQL1652N error when trying to open the DB2 1CLP or command window. The DB2 Universal Database code (core files) are 1installed into a directory structure where write privileges are limited, but 1some DB2 Universal Database tools need to write and create files in the 1DB2INSTPROF directory.

1Workaround

1Create a new directory where you can grant users, at minimum, the MODIFY 1permission and use either db2set -g db2tempdir to point to the new 1directory, or set the db2tempdir variable in the Windows system 1environment. 1

1User does not have sufficient authority to write to the 1sqllib\<instance_dir> directory even though user belongs to 1SYSADM_GROUP

1

1Problem

1User receives an SQL5005C system error when trying to update the database 1manager configuration file (update dbm cfg). The user does not have the 1required NTFS permissions to write to the sqllib\instance_dir 1directory even though you have added this user to the SYSADM_GROUP.

1First workaround

1Grant the users, at minimum, the MODIFY permission on the 1instance_dir directory at the file system level.

1Second workaround

1Create a new directory where you can grant the user, at minimum, the 1MODIFY permission. Use the db2set db2instprof command to 1point to the new directory. You will need either to recreate the 1instance so that the information is stored under the new instance directory 1specified by db2instprof, or you will need to move the old instance directory 1to the new directory. 1