The following was originally posted to one of the UPK communities on LinkedIn. Since this post generated some feedback that this information was not well-known, I thought it would be good to repost, which I've done with permission from Earl Sullivan.
This is an FYI for those who have UPK 3.6.1 and applied the Enablement Pack 1. There is a manual database update that is needed to be run. Here is the information:
To correct an issue with permissioning in the Library, this Service Pack, issued in March 2010, also contains scripts to update the database on the Oracle Database or MicrosoftSQL server. Once you have run the Setup.exe file for the Service Pack, the necessary script files can be found at the root of the folder where the Developer is installed. These scripts must be run manually according to the instructions below.
To update a database located on an Oracle Database server manually:
Run the Setup.exe to install the files for the Service Pack.
Start SQL*Plus and login with the system account.
At the command prompt, enter the path to the AlterSchemaObjects.sql script located at the root of the folder where the Developer is installed. and append the following parameters:
schema_owner - There is a limit of 20 characters on the schema owner name. You can find this information in the web.config file located in the Repository.WS in the folder where the server is installed.
password - The existing schema owner password.
Statement with generic parameters:
@C:\AlterSchemaObjects.sql schema_owner password
4. Run the AlterSchemaObjects.sql script.
To update a database located on a Microsoft SQL server manually:
Run the Setup.exe to install the files for the Service Pack.
Log in to the database using the database administrator account.
Open and edit the AlterDBObjects.sql file located at the root of the folder where the Developer is installed.
Replace the ODServer text with the username used when the database was installed. You can find this information in the web.config file located in the Repository.WS folder in the folder where the server is installed.
Change the database from master to the name of the existing Developer database and run the AlterDBObjects.sql script.
Note: The database name is the initial catalog in the connection string in the
web.config file.
Editor's note: The database update fixes a problem with permissions where the permissions for a user will be incorrectly updated when a group that the user was removed from has their permissions changed.
