Repository migration is the process of converting the contents
of the database from one format to another. Repository migration is
necessary when you are upgrading the Jazz™ Team
Server from
version X to version Y, where version Y has schema changes.
About this task
Generally, data migration is a two step process:
- Exporting data that is there in the version X of Jazz repository
to a TAR file.
- Importing data from the TAR file to the version Y of Jazz repository.
You
can use the repotools application for export and import operation.
Note: Jazz Team
Server must
be stopped when you migrate the repository. Migration might take a
long time depending on your machine's configuration, operating
system, database, and so on. Therefore, schedule your outage appropriately.
Migrating the full text directory
The Jazz Team
Server manages a directory outside the database that stores all data
that is necessary to process full text queries. The location of the
directory is configured in the
teamserver.properties file
under the
com.ibm.team.fulltext.indexLocation property.
When migrating your database and want to use the previous directory
that was used for indexing, you must ensure that the location used
in the
-rebuildTextIndices repository tool matches
the location used by the server. When starting the server or running
the
-rebuildTextIndices command, the absolute path
to the location of the full text directory is printed in the log files.
You can check the server log file and the
repotools_rebuildTextIndicies log
file to compare both directories.
Tip: If the configured
directory in the teamserver.properties file is a
relative path, a warning will be printed in the log file. It is recommended
to configure this property to be an absolute directory path.
For
more information about creating full text indices, see
-rebuildTextIndices.
Jazz Team
Server migration
is a very intensive process that can take a fair amount of time depending
on the size of your data being migrated. Here is a checklist of things
to look out for to avoid common pitfalls.
DB2:
- DB2 by default tries to grow the buffer pool size as large as
necessary. Unless you have disabled this, DB2 should perform well
out of the box.
- To check the buffer pool, do the following:
- Connect to the Jazz database you want to import into by typing
the following in the command prompt:
db2 connect to <databaseName>
- Then, run the following command:
db2 "select bufferpoolid, bpname from syscat.bufferpools"
This
will output a bufferpool identifier in this format:BUFFERPOOLID BPNAME
------------ ----------------------------------
1 IBMDEFAULTBP
1 record(s) selected.
- In the above example, the buffer pool identifier is 1. Next, run
the following command:
db2mtrk -d
This will output
data similar to the following:Tracking Memory on: 2009/06/04 at 22:19:17
Memory for database: <databaseName>
utilh pckcacheh other catcacheh bph (1) bph (S32K)
64.0K 384.0K 128.0K 128.0K 95.4M 832.0K
bph (S16K) bph (S8K) bph (S4K) shsorth lockh dbh
576.0K 448.0K 384.0K 64.0K 2.5M 20.8M
apph (269) apph (268) apph (267) apph (266) apph (265) apph (262)
64.0K 64.0K 64.0K 64.0K 64.0K 64.0K
appshrh
128.0K
The bold output indicates the allocated
buffer pool size for your database.
To start the migration: