IBM VisualAge TeamConnection 3.0.7 FixPak ------------------------------------------ File: readme.txt (10-Apr-2001)Documents ---------
backup_db.txt, fix302.ddl, fixdb.ddl, readme.txt, relnotes.txt, restore_db.txt, systeminfo.txt, trace.txt, upgrading_to_v303HF1.txtMain Index ----------
The installation instructions for FixPak 3.0.7 are divided into the following topics: - Where to get the most recent version of this file - Objective - Stylistic Conventions and Testing - What is VisualAge TeamConnection FixPak 3.0.7 - Important: End of Service for VisualAge TeamConnection. - See the Release Notes for more details - Known Incompatibilities - Netscape and AIX - Upgrading from previous versions of TeamConnection - Making Backups - Prerequisite Software and Hardware - Upgrading Clients and views - Getting Help: What to do if you have problems - Installing the FixPak on Intel - INTEL Part 1: Install or Update DB2 on Intel - INTEL Part 2: Installing TeamConnection FixPak v3.0.7 on Intel - Installing the FixPak on UNIX - UNIX Part 1: Install or Update DB2 on UNIX - UNIX Part 2: Installing TeamConnection FixPak v3.0.7 on UNIX - Appendix 1: Identifying the Level of DB2 - Appendix 2: UNIX Fastpath for TeamC, Asset Locator, and the Java GUI - Appendix 3: Uninstallation of DB2 Back to Main IndexWhere to get the most recent version of this file -------------------------------------------------
The most recent version of this file can be found at: ftp://ftp.software.ibm.com/ps/products/teamconnection/fixes/ Back to Main IndexObjective: ---------
This file contains information you will need to install FixPak 3.0.7 on both UNIX and Intel Platforms. For your ease, we suggest you view the HTML version of this document in a web browser. Back to Main IndexStylistic Conventions
To make the code examples viewable in HTML, this text and all documents mentioned in it use the convention [variableName] to represent a variable the MUST be typed. For example to start the TeamConnection family server the syntax is teamcd [familyName] in which case you should type teamcd testfam The HTML version of this file has been tested with Netscape Communicator 4.5.1. Back to Main IndexWhat is VisualAge TeamConnection FixPak 3.0.7 ---------------------------------------------
FixPak 3.0.7 for VisualAge TeamConnection is not a fullpak install. It is designed to be installed over an existing version of TeamConnection. Fixpak 3.0.7 is a cumulative delta fixpak that includes the fixes provided in FixPaks 3.0.5 and 3.0.6. Back to Main IndexImportant: End of Service for VisualAge TeamConnection
Effective October 17, 2000, IBM will withdraw from marketing VisualAge® TeamConnection™ Enterprise Server V3.0 licensed under the IBM International Program License Agreement. IBM is extending program service for VisualAge TeamConnection Enterprise Server V3.0 until January 31, 2002. VisualAge TeamConnection V3.0 will remain functionally stabilized. No enhancements or upgrades to supported platforms, IBM software, or third party software will be provided. FixPaks for customer-reported defects to existing function will be provided until the service end date. For more information on the announcement letter 900-206, see the following URL: http://www1.ibmlink.ibm.com/cgi-bin/master?xh=nsHTcGq6ZjWQnH1USenGnN9332&request=announcements&parms=H%5f900%2d206&xhi=usa%2emain%7cannouncements%5e&xfr=N Back to Main IndexSee the Release Notes for more details
Information on the following items can be found in the TeamConnection FixPak 3.0.7 Release Notes (relnotes.txt on the CD-ROM): - What's Fixed in FixPak 3.0.7 - What's Fixed in FixPak 3.0.6 - What's Fixed in FixPak 3.0.5 - Important behavior introduced by the fix for build deadlocks - Important Notes on VA TC Usage - Collecting traces of problems on the family server - Lotus Notes Issues - MVS Issues - Microsoft Source Code Control Information - Additional Information - Sample Parser Files - Getting Help - Services - Technical Support - Self Help - Trademarks - Your Satisfaction Back to Main IndexKnown Incompatibilities -----------------------
Because Websphere Application Server does not currently run on Solaris 2.5.1, Asset Locator does not work with Solaris 2.5.1. It is not necessary to use Asset Locator in order to use TeamConnection. Back to Main IndexNetscape and AIX ----------------
If you did not install Netscape from the Single-box CD, but instead use an existing installation of Netscape, the web-based JAVA GUI might not work correctly. You can fix this by copying the file swingall.jar to a directory in your CLASSPATH statement. Back to Main IndexUpgrading from Previous Versions of TeamConnection --------------------------------------------------
Based on the current level of TeamConnection on your system, the overall upgrade path is as follows: - Version 2 Clients: The version 2 and version 3 servers are not compatible. If you have version 2.X.X installed, you must migrate the database to V3.0.3HF1 using a special tool. Please contact TeamConnection Support. - Version 3.0.0 or 3.0.1: You need to upgrade to v3.0.3 Hotfix 1 first. The sequence of events you should follow is: run fix302.ddl as described in upgrading_to_v303HF1.txt, upgrade to FixPak v3.0.3HF1, run fixdb.ddl as described in upgrading_to_v303HF1.txt, and finally upgrade to FixPak v3.0.7. Please contact our technical support center for instructions, at any stage if you need help as this can be a complicated process. - Version 3.0.2 or 3.0.3: you need to upgrade to either v3.0.3 Hotfix 1 or version 3.0.4 (preferred). The sequence of events you should follow for v3.0.2 databases is: run fix302.ddl as described in upgrading_to_v303HF1.txt, upgrade to FixPak v3.0.3HF1 or v3.0.4, run fixdb.ddl as described in upgrading_to_v303HF1.txt, and finally upgrade to FixPak v3.0.7. The sequence of events you should follow for v3.0.3 databases is: run fixdb.ddl as described in upgrading_to_v303HF1.txt, upgrade to FixPak v3.0.3HF1 or v3.0.4, run fixdb.ddl again, and finally upgrade to FixPak v3.0.7. Please contact our technical support center for instructions, at any stage as this can be a complicated process. - Version 3.0.3 Hotfix 1 or higher: proceed with the instructions shown in this document. Back to Main IndexMaking Backups --------------
The installation scripts for the version 3.0.7 fixpak code will overwrite existing files on your system without making backups. Consequently, there is no automated way to back out the code installed by this fixpak. If you are concerned about backing out from a fixpak, then you should make a backup copy of the %TC_HOME% (Intel) or $TC_HOME (Unix) directory structure and the underlying files before starting this installation procedure. Back to Main IndexPrerequisite Software and Hardware -----------------------------------
Before installing TeamConnection, make sure you are aware of the correct prerequisite software and hardware. You can find this information by going to the following web sites: Software requirements: http://www.ibm.com/software/ad/teamcon/about/tcaboutswv3.htm Hardware requirements: http://www.ibm.com/software/ad/teamcon/about/tcabouthwv3.htm Back to Main IndexUpgrading Clients and Views
Before proceeding to the installation steps, please read the following notes: * CLIENT: We highly recommend that you use the same version of TeamConnection for the client and server, although a client that is one level backwards from the server, eg. a v3.0.7 server and a v3.0.6 client, should work properly. Unexpected behavior may result when using older clients. * UPGRADING: Anytime you run the fhcirt upgrade utility, you need to update the views TeamConnection uses. fhcirt is run as part of upgrade_db.ksh on UNIX and is run as an independent executable on INTEL. To update the views on UNIX nothing has to be done if you have run upgrade_db.ksh, as updateviews is called automatically. If you run fhcirt on UNIX or fhcirt.exe on INTEL as an independent executable, you will need to update TeamConnection's views with updateviews (on UNIX) or updviews (on INTEL). These scripts should be run from the cfgField directory of your family directory, eg. INTEL: %TC_DBPATH%\cfgField UNIX: $TC_DBPATH/cfgField (See Steps 4A, 4B, and 5 in "Part 2: Installing TeamConnection FixPak v3.0.7 on Intel" or "Part 2: Installing TeamConnection FixPak v3.0.7 on UNIX" for more information) Back to Main IndexGetting Help: What to do if you have problems -------------------------------
If you encounter problems installing this FixPak, read the section in the Release Notes entitled "Self Help". If you need to contact customer support, read the section in the Release Notes entitled "Technical Support" and then fill out the form systeminfo.txt before contacting support. Customer support will require this information in order to diagnose any problems you are having. If you have a reproducible problem, write down a detailed set of steps on how to reproduce the problem and provide this to customer support as well. If you are asked to collect a trace of the problem, follow the instructions in the document trace.txt. You may also collect the trace beforehand and provide it to customer support the first time you call in order to save time.======================================================================= Beginning of INTEL specific Information ======================================================================= Installing the FixPak on Intel ------------------------------
Before you begin, make certain you have read the section on "Upgrading from Previous Versions of TeamConnection" and have checked the Prerequisite Software and Hardware. Back to Main IndexPart 1: Install or Update DB2 on Intel ---------------------------------------
These are the steps you should follow to install DB2 and DB2 FixPak 11 on INTEL: Step 1 - Backup your database (Intel) Step 2 - Determine the level of DB2 on your system (Intel) Step 3 A - If your level of DB2 is 5.0 (Intel) Step 3 B - If your level of DB2 is 5.2 (Intel) Step 4 - Install DB2 FixPak 11 (Intel) Step 5 A - Updating DB2 5.0 Databases for use with DB2 5.2 (Intel) Step 5 B - Updating databases for use with a new DB2 FixPak (Intel) DB2 Troubleshooting Guide The specifics for each of these steps are discussed below. Note that steps are to be run from the family login unless otherwise specified. ASSUMPTION: You are installing or updating DB2 on a server which contains both TeamConnection and the TeamConnection family databases. Step 1 - Backup your database (Intel) ------------------------------------ Back up your TeamConnection family databases. The syntax of the DB2 backup command is: db2 backup database [tc_family] to [backup_directory] (Example: db2 backup database testfam to f:\teamc\testfam\backup) See the file, backup_db.txt, for more details. Back Step 2 - Determine the level of DB2 on your system (Intel) --------------------------------------------------------- It is important to determine the level of DB2 UDB you have installed on your system and the DB2 FixPak level because TeamConnection 3.0.3+ cannot be used with DB2 5.0. To determine the level of DB2, login as the TeamConnection family administrator and issue this command: db2level You should see an informational token that begins with 5.2, eg. DB2 v5.2.0.33 This would indicate that you are at DB2 version 5.2. If the db2level command cannot be found, please see Appendix 1, "Identifying the Level of DB2" for further instructions. DB2 FixPaks are identified by the last number in the informational token: 5.0.0.26 = fixpack 4 5.2.0.15 = fixpack 8 5.2.0.33 = fixpack 11 If you already have DB2 5.2 FixPak 11 installed, you may jump to Part 2 to install TeamConnection FixPak v3.0.7. If not, continue on with the next step. Back Step 3 A - If your level of DB2 is 5.0 (Intel) --------------------------------------------- If the level of DB2 you determined in Step 2 is 5.0, then proceed with the directions in this step. Otherwise, go to step 3 B. 1. Uninstall the DB2 UDB ------------------------ Since the version of DB2 on your system is older than version 5.2, you need to uninstall DB2 UDB 5.0. For more details on this task, see Appendix C --- "Uninstallation of DB2" --- in the technical report "Configuration and Administration of DB2 Universal Database V5 by users of VisualAge TeamConnection Enterprise Server Version 3.0" available from: http://www.ibm.com/software/ad/teamcon/library/. The information has been repeated in this document as Appendix 3. 2. Reinstall the DB2 UDB base code ---------------------------------- Once you have uninstalled DB2, you need to reinstall the DB2 base code. To install the DB2 UDB 5.2 base code, log in as the system administrator, then insert the CD-ROM that has DB2, and if autoplay is enabled, the installation of DB2 UDB 5.2 base code will start. Follow the prompts, then reboot your workstation. If autoplay is disabled, login as the system administrator and change to the top directory of the CD-ROM and execute "setup.exe" Go on to Step 4 to install DB2 FixPak 11. Back Step 3 B - If your level of DB2 is 5.2 (Intel) --------------------------------------------- If the level of DB2 you determined in Step 2 is 5.2, then proceed with the directions in Step 4 to apply DB2 FixPak 11. (WARNING: if you already have a FixPak later than DB2 FixPak 11 installed, eg. DB2 FixPak 12, you should not install DB2 FixPak 11. Proceed with installation of TeamConnection FixPak v3.0.7 in Part 2) Back Step 4 - Install DB2 FixPak 11 (Intel) ------------------------------------- a) Log in as the system Administrator b) If your level of DB2 is now 5.2, you only need to install DB2 FixPak 11. Insert the CD-ROM that has DB2. WARNING: If autoplay is enabled, the installation of DB2 UDB 5.2 base code will start. Exit as soon as you can! You do not wish to proceed with with this automatic installation because it will install the DB2 UDB 5.2 base code without fixpaks! Once you have stopped the automatic install of the base code, you need to start the fixpak install. To do this, right-click "Start", select "Explore" and use the Explorer to change to the "fixes" directory on the CD-ROM and run "setup.exe". Follow the prompts to install the FixPak. If autoplay is disabled on your CD-ROM, simply change to the "fixes" directory and run "setup.exe". NOTE: you may download a copy of both the DB2 FixPak and its readme from ftp://ftp.software.ibm.com/ps/products/db2/fixes/english-us/db2ntv5/ Back Step 5 A - Updating DB2 5.0 Databases for use with DB2 5.2 (Intel) ----------------------------------------------------------------- If you determined the level of DB2 on your system to be 5.0 in Step 2, then continue with this step. Otherwise, go on to Step 5 B. If you upgraded DB2 from 5.0 to 5.2, you must perform two actions. First, upgrade your databases for use by DB2 5.2 (this step) and second upgrade the databases for use with the new FixPak you installed (Step 5 B). To upgrade a 5.0 database for use with DB2 5.2 1. Restore the database from a backup if necessary. See restore_db.txt for details. 2. On NT, start a DB2 command window (you don't have to do this for OS/2) by doing one of the following: - From Start, select Programs > DB2 for Windows NT > Command Window or - From a normal command window, run the following command: db2cmd 3. View which databases are in your instance by running this command db2 list db directory Each database in the directory needs to be updated. 4. To update a database for use with DB2 5.2, log in as the VA TC family user id and run db2upd52 -d dbName where dbName is the name of your database. This command needs to be run for each database in your DB2 instance. Next, perform the actions in Step 5 B. Back Step 5 B - Updating databases for use with a new DB2 FixPak (Intel) ------------------------------------------------------------------ If you have installed a new FixPak or you have updated DB2 from 5.0 to 5.2, you must update the databases for use with a new FixPak. 1. Restore the database from a backup if necessary. See restore_db.txt for details. 2. Login as a DB2 administrator (such as: db2admin). 3. Issue "db2cmd" to open a db2 command window, then do db2 terminate db2 CONNECT TO [dbName] db2 BIND C:\SQLLIB\BND\@db2ubind.lst GRANT PUBLIC db2 BIND C:\SQLLIB\BND\@db2cli.lst GRANT PUBLIC db2 terminate Where [dbName] is the name of the database you are updating. You need to repeat this for each family database, including testfam. For more details on this process read the readme.txt for the DB2 FixPak which can be downloaded for your platform at: ftp://ftp.software.ibm.com/ps/products/db2/fixes/english-us/db2ntv5/ 4. Perform the following to refresh the statistics and to rebind: rexx %TC_HOME%\samples\tcrstats [family_name] rexx %TC_HOME%\samples\tcrebind [family_name] 5. You are finished with the installation of DB2. Proceed with "Part 2: Installing TeamConnection FixPak v3.0.7 on Intel". BackDB2 Troubleshooting Guide
If you have DB2 problems, you may find the Troubleshooting Guide useful. Go to http://www.ibm.com/support/ and search for "troubleshooting guide universal database" in the "Search by Keyword" field. Back to Main IndexPart 2: Installing TeamConnection FixPak v3.0.7 on Intel ---------------------------------------------------------
WARNING: Make sure you have DB2 FixPak 8 or preferably FixPak 11 installed before installing TeamConnection FixPak 3.0.7. DB2 FixPak 11 is included on the CD-ROM. These are the steps you should follow to install the FixPak in Intel: Step 1 - Stop all family processes (Intel) Step 2 - Backup the family database (Intel) Step 3 - Install the FixPak code (Intel) Step 4A - Run the database update utility (for 3.0.3 Hotfix 1) (Intel) Step 4B - Run the database update utility (for 3.0.4 or higher) (Intel) Step 5 - Update the database views (Intel) Step 6 - Run the database statistics and rebind scripts (Intel) Step 7 - Restart the family processes (Intel) The specifics for each of these steps are discussed below. Note that steps are to be run from the family login unless otherwise specified. Back to Main Index Step 1 - Stop all family processes (Intel) ------------------------------------------ Make sure all TeamConnection Processes have been shut down. You can stop the family servers by logging in as the family administrator and running the following command: tcstop [family_name] where family_name is the short form of the family name, eg. testfam. Make sure you run the tcstop command on ALL your families. Back Step 2- Backup the family database (Intel) ------------------------------------------ 1. Invoke a DB2 command window by running the following command: db2cmd 2. Back up your TeamConnection database using the "DB2 Backup" command. The syntax of the DB2 backup command is: db2 backup database [tc_family] to [backup_directory] Substitute your family name for [tc_family] and a full directory path for [backup_directory]. The DB2 backup utility will place a compressed version of the database in the backup directory path. Be sure to set file permissions for the backup directory such that the compressed backup file is accessible. For details on backing up DB2 databases, see backup_db.txt and the DB2 Universal Database Administration Guide. Also refer to the TeamConnection Administrator's Guide for information on using the DB2 backup command. Back Step 3 - Install the FixPak code (Intel) ---------------------------------------- To install the FixPak from the CD-ROM do the following: 1. Insert the CD-ROM. 2. Start a command window, and change to the top directory of the CD-ROM. For example, assuming that the CD-ROM drive is D:, do: D: cd \ 3. Ensure that %TC_HOME% is properly defined in your system. The TC_HOME environment variable should be set to the complete path of the directory containing Visual Age TeamConnection. For example: echo %TC_HOME% c:\teamc If it is not defined, then STOP: do not proceed until the TC_HOME environment variable is properly set, because the installation scripts use this variable and if it is not properly defined, then the scripts may copy the fixpak code into the wrong directories. 4. Run the appropriate installation scripts, according to your needs: a) To install the Family Server code for the fixpak, execute: instserv %TC_HOME% Alternatively, you can invoke the following command, which is the main command invoked by the script; if prompted, you may need to specify the All (letter A) option to overwrite the files: xcopy .\server %TC_HOME% /s b) To install the Build Server code for the fixpak, execute: instbld %TC_HOME% Alternatively, you can invoke the following command, which is the main command invoked by the script; if prompted, you may need to specify the All (letter A) option to overwrite the files: xcopy .\build %TC_HOME% /s a) To install the Client code for the fixpak, execute: instclt %TC_HOME% Alternatively, you can invoke the following command, which is the main command invoked by the script; if prompted, you may need to specify the All (letter A) option to overwrite the files: xcopy .\client %TC_HOME% /s Back Step 4A - Run the database update utility - for 3.0.3 Hotfix 1 (Intel) ---------------------------------------------------------------------- If you are upgrading from 3.0.3 Hotfix 1, complete the tasks in this section. If you are upgrading from 3.0.4 or higher, skip this step and go to step 4B. The FixPak code installs a utility that you need to run that updates the Version 3 database with schema changes. The utility, called FHCIRT.EXE, adds new tables, adds new columns to existing tables, and populates the tables where necessary. This step needs to be executed for each family, and you need to login to the system with the appropriate family administrator user id and have the appropriate TC_DBPATH and TC_FAMILY environment variables set. (We highly recommend that you only have one VATC family on an NT server.) To run FHCIRT, change to the drive where the family is installed and then run the following commands: (Ensure that you are logged in as the family administrator) cd %TC_DBPATH% fhcirt -vv %TC_HOME%\nls\cfg\*.dd* %TC_HOME%\nls\cfg\*.bnd 2>&1 >fhcirt.out Note that the 3.0.3 Hotfix 1 or 3.0.4 upgrade to 3.0.7 takes a little less than an hour. Proceed to Step 5. Back Step 4B - Run the database update utility - for 3.0.4 or higher (Intel) ----------------------------------------------------------------------- If you are upgrading from 3.0.4, complete the tasks in this section. If you are upgrading from 3.0.3 Hotfix 1 and you have performed step 4A, then skip this step and go to Step 5. FixPak 3.0.7 does not introduce any database schema changes (similar to fixpaks 3.0.5 and 3.0.6 in that respect), and therefore when upgrading from 3.0.4 or higher, there is no need to perform a schema upgrade and only a rebind is necessary. The FixPak code installs a utility that you need to run that updates the V3.0 database. The utility, called FHCIRT.EXE, rebinds the application files to the database. This step needs to be executed for each family, and you need to login to the system with the appropriate family administrator user id and have the appropriate TC_DBPATH and TC_FAMILY environment variables set. To run FHCIRT, change to the drive where the family is installed and then run the following commands: (Ensure that you are logged in as the family administrator) cd %TC_DBPATH% fhcirt -vv %TC_HOME%\nls\cfg\*.bnd 2>&1 >fhcirt.out Note that the rebind process takes a little less than an hour. Proceed to Step 5. Back Step 5 - Update the database views (Intel) ------------------------------------------ To update database views, change to the desired family directory and then change to the cfgField subdirectory. cd f:\teamc\testfam (replace drive and family directory with those for your installation) Make certain all the TeamConnection environment variables TC_FAMILY and TC_DBPATH are referencing the correct family. cd cfgField Next, run the following command: updviews This command should be run anytime you have previously used the fhcirt command. You can run the updviews command multiple times on the same view without damaging the family. Also note that if you want to run this command on another family, you must change all your TeamConnection environment variables to reflect the new family. Back Step 6 - Run the database tcrstats and tcrebind scripts (Intel) --------------------------------------------------------------- TeamConnection ships with database scripts that you should use after making significant changes to a family. A significant change might be loading the family, adding lots of new parts, or making numerous part changes. You should definitely run these scripts after running the fhcirt command. This process should produce optimal statistics and performance. On NT you have to submit DB2 commands from a DB2 command window. A. On NT, start a DB2 command window (you don't have to do this for OS/2) by doing one of the following: - From Start, select Programs > DB2 for Windows NT > Command Window or - From a normal command window, run the following command: db2cmd B. Change the directory to the family directory. For example: cd f:\teamc\testfam (replace drive and family directory with those for your installation) C. On NT, run the following commands from a DB2 window: rexx %TC_HOME%\samples\tcrstats [family_name] rexx %TC_HOME%\samples\tcrebind [family_name] On OS/2, run the following commands: %TC_HOME%\samples\tcrstats%TC_HOME%\samples\tcrebind D. Backup the database. From the command window, backup the database. The syntax for doing this is: db2 backup database [family_name] to [backup_directory] (Example: db2 backup database testfam to f:\teamc\testfam\backup) Back Step 7 - Restart the family processes (Intel) --------------------------------------------- Restart the family processes. ======================================================================= Beginning of UNIX specific Information ======================================================================= Installing the FixPak on UNIX ------------------------------
Before you begin, make certain you have read the section on "Upgrading from Previous Versions of TeamConnection" and have checked the Prerequisite Software and Hardware. Back to Main IndexPart 1: Install or Update DB2 on UNIX --------------------------------------
These are the steps you should follow to install DB2 and FixPak 11 on UNIX: Step 1 - Backup your database (UNIX) Step 2 - Determine the level of DB2 on your system (UNIX) Step 3 A - If your level of DB2 is 5.0 (UNIX) Step 3 B - If your level of DB2 is 5.2 (UNIX) Step 4 - Run the db2inst.ksh script (UNIX) Step 5 - Updating databases from DB2 5.0 or another FixPak (UNIX) DB2 Troubleshooting Guide The specifics for each of these steps are discussed below. Note that steps are to be run from the family login unless otherwise specified. ASSUMPTION: You are installing or Updating DB2 on a server which contains both TeamConnection and the TeamConnection family databases. Step 1 - Backup your database (UNIX) ----------------------------------- Back up your TeamConnection family databases. The syntax of the DB2 backup command is: db2 backup database [tc_family] to [backup_directory] See the file, backup_db.txt, for more details. Back Step 2 - Determine the level of DB2 on your system (UNIX) -------------------------------------------------------- It is important to determine the level of DB2 UDB you have installed on your system and the DB2 FixPak level because TeamConnection 3.0.3+ cannot be used with DB2 5.0. To determine the level of DB2, login as the TeamConnection family administrator and issue this command: db2level You should see an informational token that begins with 5.2, eg. DB2 v5.2.0.33 This would indicate that you are at DB2 version 5.2. If the db2level command cannot be found, please see Appendix 1, "Identifying the Level of DB2" for further instructions. DB2 FixPaks are identified by the last number in the informational token: 5.0.0.26 = fixpack 4 5.2.0.15 = fixpack 8 5.2.0.33 = fixpack 11 If you already have DB2 5.2 FixPak 11 installed, you may jump to Part 2 to install TeamConnection FixPak v3.0.7. If not, continue on with the next step. Back Step 3 A - If your level of DB2 is 5.0 (UNIX) -------------------------------------------- If the level of DB2 you determined in Step 2 is 5.0, then proceed with the directions in this step. Otherwise, go to step 3 B. Since the version of DB2 on your system is older than version 5.2, you need to uninstall DB2 UDB 5.0. For more details on this task, see Appendix C --- "Uninstallation of DB2" --- in the technical report "Configuration and Administration of DB2 Universal Database V5 by users of VisualAge TeamConnection Enterprise Server Version 3.0" available from: http://www.ibm.com/software/ad/teamcon/library/. The information has been repeated in this document as Appendix 3. Once you have uninstalled DB2, follow the directions in Step 4 to run db2inst.ksh and install the DB2 UDB 5.2 base code and FixPak 11. You will need to choose options 1) UDB 5.2 base product install 2) UDB 5.2 fixpak 11 install 4) UDB 5.2 fixpak 11 standard database upgrade Back Step 3 B - If your level of DB2 is 5.2 (UNIX) -------------------------------------------- If the level of DB2 you determined in Step 2 is 5.2 then proceed with the directions in this step. Since your level of DB2 is already 5.2 you only need to follow the directions in Step 4 to run db2inst.ksh and install DB2 FixPak 11. You will need to choose options 2) UDB 5.2 fixpak 11 install 4) UDB 5.2 fixpak 11 standard database upgrade (WARNING: if you already have a FixPak later than DB2 FixPak 11 installed, eg. DB2 FixPak 12, you should not install DB2 FixPak 11. Proceed with installation of TeamConnection FixPak v3.0.7 in Part 2) Back Step 4 - Run the db2inst.ksh script (UNIX) ----------------------------------------- a) Ensure that you are logged in as "root" (otherwise you will not be able to install the DB2 code.) b) Mount the CD-ROM per your operating system. c) From the CD-ROM root directory, invoke the following installation shell script: ./db2inst.ksh d) Follow the instructions from the installation shell script and select the appropriate options (you may skip Option 3, about the DB2 Extender, which is only used for the Asset Locator -- see the Prerequisite Software and Hardware.) 1) UDB 5.2 base product install 2) UDB 5.2 fixpak 11 install 3) UDB 5.2 text extender install 4) UDB 5.2 fixpak 11 standard database upgrade (Even if you have installed a FixPak other than 11 you should still choose Option 4 to upgrade). NOTE: you may download a copy of both the DB2 FixPak and its readme from ftp://ftp.software.ibm.com/ps/products/db2/fixes/english-us/db2ntv5/ Back Step 5 - Updating databases from DB2 5.0 or another FixPak (UNIX) ------------------------------------------------------------------ If you chose option (4) "UDB 5.2 fixpak 11 standard database upgrade", your existing databases have already been updated for use with db2 5.2 and the FixPak you installed. If you later have other DB2 5.0 databases or databases from other FixPak levels that you want to restore under the DB2 UDB 5.2 you have just set up, then restore the databases now and follow the directions in Step 4 to run db2inst.ksh again. See restore_db.txt for details on restoring. When running db2inst.ksh, you will need to choose option 4 only. 4) UDB 5.2 fixpak 11 standard database upgrade You may choose option (4) even if you have a different FixPak level. You have finished installing DB2. Proceed with "Part 2: Installing TeamConnection FixPak v3.0.7 on UNIX". BackDB2 Troubleshooting Guide
If you have DB2 problems, you may find the Troubleshooting Guide useful. Go to http://www.ibm.com/support/ and search for "troubleshooting guide universal database" in the "Search by Keyword" field. Back to Main IndexPart 2: Installing TeamConnection FixPak v3.0.7 on UNIX --------------------------------------------------------
WARNING: Make sure you have DB2 FixPak 8 or preferably FixPak 11 installed before installing TeamConnection FixPak 3.0.7. DB2 FixPak 11 is included on the CD-ROM. These are the steps you should follow to install the FixPak in UNIX: Step 1 - Stop all family processes (UNIX) Step 2 - Backup the family database (UNIX) Step 3 - Install the FixPak code (from CD-ROM) (UNIX) Step 4A - Run the database update script (for 3.0.3 Hotfix 1) (UNIX) Step 4B - Run the database update script (for 3.0.4 or higher) (UNIX) Step 5 - Update the database views (UNIX) Step 6 - Run the database statistics and rebind scripts (UNIX) Step 7 - Restart the family processes (UNIX) The specifics for each of these steps are discussed below. Note that steps are to be run from the family login unless otherwise specified. Step 1 - Stop all family processes (UNIX) ----------------------------------------- Make sure all TeamConnection Processes have been shut down. You can stop the family process by logging in as the family administrator and running the following command: tcstop [$LOGNAME] where $LOGNAME is the short form of the family name, eg. testfam. Make sure you run the tcstop command on ALL your families. Back Step 2 - Backup the family database (UNIX) ------------------------------------------ 1. Back up your TeamConnection database using the "DB2 Backup" command. The syntax of the DB2 backup command is: db2 backup database [tc_family] to [backup_directory] 2. Substitute your family name for [tc_family] and a full directory path for [backup_directory]. The DB2 backup utility will place a compressed version of the database in the backup directory path. Be sure to set file permissions for the backup directory such that the compressed backup file is accessible. For details on backing up DB2 databases, see backup_db.txt and the DB2 Universal Database Administration Guide. Also refer to the TeamConnection Administrator's Guide for information on using the DB2 backup command. Back Step 3 - Install the FixPak code (From CD-ROM) (UNIX) ----------------------------------------------------- This section covers installing the FixPak from a CD-ROM. To install the FixPak code in UNIX, complete the following steps: a) Ensure that you are logged in as "root" (otherwise you will not be able to install the TeamConnection code.) b) Mount the CD-ROM per your operating system. c) From the CD-ROM root directory, invoke the following installation shell script: ./tcinst.ksh d) Follow the instructions from the installation shell script. e) At the end of the execution of tcinst.ksh, you may see some warning messages about help files that could not be found. You can ignore these warning messages. Back Step 4A - Run the database update script - for 3.0.3 Hotfix 1 (UNIX) --------------------------------------------------------------------- If you are upgrading from 3.0.3 Hotfix 1, complete the tasks in this section. If you are upgrading from 3.0.4 or higher, skip this step and go to step 4B. The FixPak code installs a script (upgrade_db) that you need to run that updates the V3.0 database with schema changes. The script calls the fhcirt utility that adds new tables, adds new columns to existing tables, and populates the tables where necessary. You need to run the script for EACH family, and you need to log in to the system with the appropriate family administrator user id and have the appropriate TC_DBPATH and TC_FAMILY environment variables set. To update the TeamConnection database, invoke the script (for each family) as follows: (Ensure that you are logged in as the family administrator) cd $HOME $TC_HOME/samples/ksh/upgrade_db Note that the 3.0.3 Hotfix 1 or 3.0.4 upgrade to 3.0.7 takes a little less than an hour. The upgrade_db step also updates the views, the database statistics and rebinds the DB2 plans; thus, there is no need to perform steps 5 and 6. Therefore, you can proceed to step 7. However, you may need to periodically update the views (step 5) or update the database statistics (step 6). See those sections for further information. You are finished with the upgrade. Go to Step 7. Back Step 4B - Run the database update script - for 3.0.4 or higher (UNIX) --------------------------------------------------------------------- If you are upgrading from 3.0.4, complete the tasks in this section. If you are upgrading from 3.0.3 Hotfix 1 and you have performed step 4A, then skip this step and go to step 5. This fixpak 3.0.7 does not introduce any database schema changes (similar to fixpaks 3.0.5 and 3.0.6 in that respect) and therefore, when upgrading from 3.0.4 or higher, there is no need to perform a schema upgrade and only a rebind is necessary. The FixPak code installs a utility that you need to run that updates the V3.0 database. The utility, called fhcirt, rebinds the application files to the database. This step needs to be executed for each family, and you need to login to the system with the appropriate family administrator user id and have the appropriate TC_DBPATH and TC_FAMILY environment variables set. To run fhcirt, login as the family administrator and run the following commands: Ensure that you are logged in as the family administrator cd $TC_DBPATH fhcirt $TC_HOME/nls/cfg/*.bnd Note that the rebind process may take a little less than an hour. Proceed to Step 5. Back Step 5 - Update the database views (Unix) ------------------------------------------ This step is done automatically by upgrade_db so you will not need to update the views if you have run upgrade_db. However, you must run updateviews if you have previously run fhcirt by itself. To update database views, do the following: a: Login as the VA TC family administrator user id. b: Change the directory to the desired family: cd $HOME c: Change to the cfgField subdirectory: cd cfgField d: Run the following command: $TC_HOME/samples/ksh/updateviews You can run the updateviews command multiple times on the same view without hurting the family. Proceed to Step 6. Back Step 6 - Run the database statistics and rebind scripts (Unix) -------------------------------------------------------------- TeamConnection ships with database scripts that you should use after making significant changes to a family. A significant change might be loading the family, adding lots of new parts, or making numerous part changes. You should definitely run these scripts after running the fhcirt command. This process should produce optimal statistics and performance. A. Change the directory to the family directory. For example: cd /teamc/testfam (replace family directory path with that for your installation) B. Run the following commands: $TC_HOME/samples/ksh/tcRStats $TC_HOME/samples/ksh/tcRebind C. Backup the database. The syntax for doing this is: db2 backup database [family_name] to [backup_directory] (Example: db2 backup database testfam to /teamc/testfam/backup) Back Step 7 - Restart the family processes (UNIX) -------------------------------------------- Restart the family processes. Back Back to Main IndexAPPENDIX 1 Identifying the Level of DB2 -----------------------------
This section provides guidelines on how to check what level of DB2 you have installed. To identify whether DB2 UDB 5.0, or DB2 UDB 5.2 with FixPak 6 or FixPak 8 is installed, do the following: - Login as a VA TC family administrator id or as a DB2 instance owner to use the new DB2 command "db2level" (introduced in 5.2). This command will provide information about the level of DB2 in your system. If db2level is not found, then you do not have DB2 UDB 5.2. For example, in an AIX machine with DB2 UDB 5.2 FixPak 8, you would get the following output: $ db2level DB21085I Instance "db2inst1" uses DB2 code release "SQL05020" with level identifier "02050103" and informational tokens "DB2 v5.2.0.15", "c990318" and "U462899". The important pieces of information are the following informational tokens, which identify the level as being FixPak 8: "DB2 v5.2.0.15" DB2 FixPaks are identified by the last number in the informational token: 5.0.0.26 = fixpack 4 5.2.0.15 = fixpack 8 5.2.0.33 = fixpack 11 An additional way to identify the level of DB2 in your system as user root is shown below for each different platforms: WINNT: regedt32 click window titled "HKEY_LOCAL_MACHINE on Local Machine" double-click "Software" double-click "IBM" double-click "DB2" double-click "DB2 Universal Database Enterprise Edition" double-click "Current Version" In the window on the right you should see: Release:REG_DWORD:0x2 Version:REG_DWORD:0x5 (This indicates version 5.2.) AIX: lslpp -al "db2_05_00*" The output of the command should include the following for FixPak 8: db2_05_00.client 5.2.0.15 Solaris: pkginfo -l db2rte50 The output of the command should include the following for FixPak 8: VERSION: 5.2.0.15 HP-UX: swlist -l product "DB2*" The output of the command should include the following: DB2V5CAE 5.2.0.2 DB2 Client Application Enabler for HP-UX Back to Main IndexAPPENDIX 2 ------------------------------------------------------------------------- UNIX Fastpath for TeamC, Asset Locator, and the Java GUI. -------------------------------------------------------------------------
We strongly recommend that you read and understand the detailed instructions in "Verifying Installation of TeamConnection" at http://www.software.ibm.com/ad/teamcon/library. The following FASTPATH instructions are recommended only for experienced TeamConnection administrators. Assumptions: TeamConnection fixpak 3.0.7, DB2 5.2 (base and fixpak 11) and required singlebox line items have been installed successfully. TC_HOME defines the TeamConnection code home directory eg: AIX /usr/teamc HP-UX /opt/teamc Solaris /opt/teamc DB2_HOME defines the DB2 code home directory eg: AIX /usr/lpp/db2_05_00 HP-UX /opt/IBMdb2/V5.0 Solaris /opt/IBMdb2/V5.0 NEW FAMILY SETUP ---------------- It is recommended that the family account and the database account be one and the same. Requirements: TeamConnection fixpak 3.0.7 family server DB2 UDB 5.2 base product DB2 UDB 5.2 fixpak 11 Assumptions: TC_FAMILY tcfama TC_FAMILY database login tcfama TC_FAMILY primary group system TC_FAMILY secondary group grpfama minimum space required 200 MB Process: 1) as root o create the database instance cd /usr/lpp/db2_05_00/install /db2setup Follow the prompts to create a DB2 instance. Accept the defaults as much as possible. o update /etc/services with a unique port identifier for the family account tcfama o update /etc/hosts with a server alias identifier for the family account tcfama 2) as tcfama o copy the sample family profile to the family home directory cp ${TC_HOME}/install/en_US*/profile.family .profile chmod 755 .profile o update as required o re-source the profile . ${HOME}/.profile o start DB2 database instance db2start o create the TeamConnection family using: tcadmin -OR- ${TC_HOME}/samples/ksh/dbcreate o start the TeamConnection family using: tcadmin -OR- teamcd tcfama n >teamcd.out 2>&1 - where n is the number of daemons to start o start the TeamConnection notify daemon using: tcadmin -OR- notifyd tcfama mailexit >notifyd.out 2>&1 o If you need to shut down the family, stop all TeamConnection daemons using: tcadmin -OR- tcstop tcfama NEW JGUI SETUP -------------- Requirements: TeamConnection fixpak 3.0.7 family up and running singlebox Netscape Communicator singlebox Apache WebServer -OR- WebSphere Application Server SE (*1) singlebox Java JDK *1) Note for AIX and Solaris servers if you plan to use the Asset Locator function you should replace the installation of the Apache WebServer with WebSphere Application Server SE Assumptions: TC_FAMILY tcfama Process: 1) as tcfama o run the utility to automatically update the configuration ${TC_HOME}/samples/ksh/update_jgui 2) as root o start Apache WebServer or WebSphere Application Server SE WebServer per singlebox startup instructions ASSETLOCATOR SETUP (AIX/Solaris ONLY) ----------------------------------- Requirements: TeamConnection fixpak 3.0.7 family up and running DB2 UDB 5.2 text extender singlebox Java JDK singlebox WebSphere Application Server SE Assumptions: TC_FAMILY tcfama CRAWLER account crfama CRAWLER primary group system CRAWLER secondary group grpfama minimum space required 200 MB Process: 1) as root o run the utility to automatically update the configuration ${TC_HOME}/samples/ksh/update_websphere 2) as tcfama o create a TeamConnection login/host record for crfama with enough authority to extract releases 3) as crfama o copy the sample family profile to the family home directory cp ${TC_HOME}/install/en_US*/profile.assetloc .profile chmod 755 .profile o update as required o re-source the profile . ${HOME}/.profile o run the utility to automatically update the configuration ${TC_HOME}/samples/ksh/update_assetloc o crawl tcfama release using asset administration GUI assetadm 4) as root o temporarily source the crfama profile to pick up the DB2 environment . ~crfama/.profile o start WebSphere Application Server SE WebServer per singlebox startup instructions Back to Main IndexAPPENDIX 3 ---------------------- Uninstallation of DB2 ----------------------
The information in this appendix was taken from Appendix C --- "Uninstallation of DB2" --- in the technical report "Configuration and Administration of DB2 Universal Database V5 by users of VisualAge TeamConnection Enterprise Server Version 3.0" available from: http://www.ibm.com/software/ad/teamcon/library/. This chapter shows you how to uninstall (remove) DB2 products. C.1 UNINSTALLING DB2 FROM UNIX You need to perform the following steps: 1. Stop and backup the VisualAge TeamConnection families. 2. Stop the Administration Server. 3. Stop all DB2 Instances. 4. Remove the Administration Server. 5. Remove DB2 Instances - this step is optional. 6. Remove the DB2 products. C.1.1 Stop and backup the VisualAge TeamConnection families ____________________________________________________________ Use tcadmin or tcstop to stop all the VisualAge TeamConnection families. If you want to keep the databases for the families, then back them up. C.1.2 Stop the Administration Server _____________________________________ You must stop the Administration Server before you remove DB2 products. To stop the Administration Server, you need to perform the following steps: 1. Log in as one of the DB2 instances. 2. Obtain the name of the Administration Server using the fol- lowing command: $DB2_HOME/bin/db2set -g DB2ADMINSERVER 3. Stop the Administration Server. See 9.7, "Stopping the Administration Server" on page 114 for details. Appendix C. Uninstallation of DB2 119 4. Exit the session. C.1.3 Stop all DB2 Instances _____________________________ You must stop all DB2 Instances before you remove DB2 products. To stop DB2 Instances, you need to perform the following steps: 1. Login as the owner of a DB2 instance. 2. Obtain a list of the names of all DB2 instances on your system using the following command: db2ilist 3. Stop the instance. See 8.5.2, "Stopping a DB2 Server Instance" on page 107 for details. 4. Exit the session. 5. Repeat these steps for each instance. C.1.4 Remove the Administration Server _______________________________________ You must remove the Administration Server before you remove DB2 products. To remove the Administration Server, you need to perform the following steps: 1. Log in as root. 2. Remove the Administration Server. See 9.8, "Removing the DB2 Administration Server" on page 114 for details. C.1.5 Remove the DB2 Instances _______________________________ You can optionally remove some or all of the DB2 Version 5 Instances on your system. Once an instance is removed, all the DB2 databases owned by the instance, if any, will not be usable. Remove DB2 Instances only if you are not planning to use DB2 Version 5 products , or if you do not want to migrate existing instances to a later version of DB2. To remove DB2 Instances, you need to perform the following steps: 1. Log in as root. 120 DB2 UDB V5 with VA TC V3 2. Obtain a list of the names of all DB2 instances on your system using the following command: $DB2_HOME/bin/db2ilist 3. Remove the instance. See 8.8, "Removing Instances" on page 109 for details. C.1.6 Clean up the DB2 registry ________________________________ In order to have a clean system before reinstalling DB2, it is recommended to cleanup the DB2 registry: 1. Login as root. 2. Execute the following command: rm -fr /var/db2/v5 For more information about the DB2 registry, see 7.5, "Where are the files used with the profile registry?" on page 99. C.1.7 Remove the DB2 Products ______________________________ The following steps describe how you can remove DB2 products on UNIX operating systems. C.1.7.1 Remove the DB2 Products on AIX Systems You can remove the DB2 products on Version 4.1 or later of the AIX operating system using SMIT interface as follows: 1. Log in as root. 2. Type smit install_remove to proceed directly to the Remove Software Products screen. 3. Press F4 to display a list of the software to remove. Press F7 at the entries that have a prefix of db2_05_00. 4. Press Enter to start removing the DB2 products. 5. After the product is removed, exit smit. 6. Change the directory to /usr/lpp/db2_05_00 and see if still there are directories and files Appendix C. Uninstallation of DB2 121 There might be some directories or files that were not removed in /usr/lpp/db2_05_00. If you want to remove them, do the following: cd /usr/lpp rm -fr ./db2_05_00 You can also remove all DB2 Version 5 products on Version 4.1 or later of the AIX operating system, using the installp command with the de-install option: installp -u db2_05_00 C.1.7.2 Remove the DB2 Products on HP-UX Systems You can remove the DB2 products on the HP-UX operating system using the swremove program as follows: 1. Log in as root. 2. Use swremove to remove some or all of the DB2 Version 5 products. Select all the file sets that begin with DB2V5. In case that you have applied patches, you can select the ones that begin with PDB2 or that their description identify them as such. C.1.7.3 Remove the DB2 Products on Solaris Systems You can remove the DB2 products on the Solaris operating system using the pkgrm program as follows: 1. Log in as root. 2. Determine the packages for all DB2 for Solaris related pro- ducts you have installed on your system by typing: pkginfo | grep -i db2 | grep 50 3. Remove all packages listed in step 2 with the pkgrm command. 4. Select Yes at the prompt for each package to be removed. 5. Before removing a package, all its dependent packages must be removed first. You must remove packages in a particular order, which is mentioned in the Chapter 28 "Removing DB2 Products" from the Quick Beginnings for UNIX manual. 122 DB2 UDB V5 with VA TC V3 C.2 UNINSTALLING DB2 FROM WINDOWS NT 1. Login as Administrator or as another member of the Adminis- trators group. 2. Stop and backup the VisualAge TeamConnection families. 3. Stop all the DB2 processes: a. Start -> Settings -> Control Panel -> Services b. Select one by one, all those DB2 services that are active and click on the Stop button: DB2 - DB2 #This is the DB2 instance DB2 - DB2DAS00 #This is the DB2 Administrator Service DB2 Security Server TME 10 NetFinity Support Program Stop also the above TME service to avoid the following problem when trying to remove the code: DB2 is currently running and therefore cannot be updated. Stop the DB2 processes and try again. 4. Start -> Settings -> Control Panel -> Add/Remove Programs. 5. Select "DB2" or "IBM DATABASE 2 Products" and click on Add/Remove button. Handle appropriately all the dialogs during the uninstalla- tion process. 6. After the uninstallation, notice that the Start -> Programs does not show the entry for DB2 anymore. Also notice that the Services (in the Control Panel) does not show the services related to DB2 anymore. 7. Reboot your workstation. 8. (Optional) You may want to delete the directory for the DB2 instances, such as C:\DB2 and C:\SQLLIB. C.3 UNINSTALLING DB2 FROM OS/2 1. Stop and backup the VisualAge TeamConnection families. 2. Stop all the DB2 processes: a. Select the DB2 Control Center. Appendix C. Uninstallation of DB2 123 b. Select Control Center -> Shutdown DB2 Tools. 3. Double click on the folder "DB2 V5" and then double click on the folder "DB2 for OS/2". 4. Double click on the "Installation Utility". 5. Select "IBM DB2 Universal Database" and from the Actions menu select Delete. Handle appropriately all the dialogs during the uninstallation process. 6. After the uninstallation, notice that the DB2 for OS/2 folder should not exist. 7. Reboot your workstation. 8. (Optional) You may want to delete the directory for the DB2 instances, such as C:\DB2 and C:\SQLLIB. 124 DB2 UDB V5 with VA TC V3 Back to Main Index <*** End of File ***>