Update SQL Server databases manually
Manually update Lotus Connections 3.0 databases to version 3.0.1 in an existing IBM WAS and Microsoft™ SQL Server database environment.
Before starting
Before applying updates, back up your databases. For more information, see the Backing up IBM Connections topic.Ensure that you have installed and configured all supporting software for version 3.0.1.
About this task
This topic describes how to manually update Lotus Connections version 3.0 databases to version 3.0.1. Use this procedure if you want an alternative to using the database wizard to update your databases.Notes:
- Use the Java™ Runtime Environment (JRE) under the Wizards directory in the installation media. Update your PATH variable to point to this JRE, using the instructions for your operating system. For example, the relative path to the JRE on the Microsoft Windows™ operating system might be C:\IBM\Lotus_Connections\Wizards\jvm\win\jre. For the AIX or Linux™ operating systems, the relative path might be /Wizards/jvm/aix/jre and /Wizards/jvm/linux/jre.
- IBM Connections does not support GNU Java.
- You do not need to use a database administrator ID to run the Java migration utilities described in this task. You can use a database user ID, such as lcuser.
- To improve readability, some commands and file paths in this topic are displayed on separate lines. Ignore these formatting conventions when entering the commands.
- After running each command, examine the output of the command for error messages. If you find errors, resolve them before continuing with the update process.
To update databases manually...
Procedure
- Log in to the WAS admin console.
- Go to Applications -> Application types -> WebSphere enterprise Applications.
- Stop all Lotus Connections applications.
- Log in as the database administrator and change to the directory containing the scripts. The relative path is shown in the step for each application.
- For each application, run the appropriate scripts by entering the commands shown in the following list. In these commands, <dbPassword> is the password for the SQL Server user named sa. If your database server has multiple SQL Server instances installed, add the following text as the first parameter to each command:
-S <sqlserver_server_name>\<sqlserver_server_instance_name>
where
- <sqlserver_server_name> is the name of your SQL Server database server
- <sqlserver_server_instance_name> is the name of your current instance
Note: To capture the output of each command to a log file, append the following parameter to each command: >> \<file_path>\db_<application>.log
where <file_path> is the full path to the log file and <application> is the name of the log file. For example: <sqlcmd> >> \home\<admin_user>\lc_logs\db_activities.log
where <sqlcmd> is a command with parameters and <admin_user> is the logged-in user. Ensure that you have write permissions for the directories and log files.
- Activities: Wizards\connections.sql\activities\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
where
- <dbUser> is the database user ID
- <dbPassword> is the administrator password
Note: This script generates a message that states Changing any part of an object name could break scripts and stored procedures. You can safely ignore the message.
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Blogs: Wizards\connections.sql\blogs\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- From a command prompt, change to the Wizards directory and enter the following text as a single command:
jvm\win\jre\bin\java -classpath
<jdbc_library_location>\sqljdbc.jar;
lib\lc.dbmigration.default.jar;
lib\blogs.migrate.jar;
lib\commons-lang-2.0.jar;
lib\commons-logging-1.0.4.jar
com.ibm.lconn.blogs.migration.MigrationFrom30To301
-dburl jdbc:sqlserver://<dbHost>:<dbPort>;databaseName=BLOGS
-dbuser <dbUser> -dbpassword <dbPassword>
where
- <jdbc_library_location> is the location of your JDBC driver
- <dbHost> is the name of the system hosting your database
- <dbPort> is the communications port for the database
- <dbUser> is the database user ID
- <dbPassword> is the administrator password
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Communities: Wizards\connections.sql\forum\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Dogear: Wizards\connections.sql\dogear\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Files: Wizards\connections.sql\files\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Forum: Wizards\connections.sql\forum\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Home page: Wizards\connections.sql\homepage\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Profiles: Wizards\connections.sql\profiles\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
Note: This script generates a message that states Changing any part of an object name could break scripts and stored procedures. You can safely ignore the message.
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
- Wikis: Wizards\connections.sql\wikis\sqlserver
- sqlcmd -U <dbUser> -P <dbPassword> -i upgrade-30-301.sql
- sqlcmd -U <dbUser> -P <dbPassword> -i appGrants.sql
What to do next
Check that all the databases are working correctly.(DB2 for Linux on System z only.) To improve database performance, enable the NO FILE SYSTEM CACHING option. For more information, see the Enable NO FILE SYSTEM CACHING for DB2 on System z topic.
Parent topic
Update 3.0 databases manually
});