It's all about the answers!

Ask a question

Facing problem with Data Migration from Derby to Db2


vinay kumar nukala (4236572) | asked Apr 15 '14, 2:15 a.m.
Hi,
   We are trying to migrate data from derby to Db2 and facing the
following problem:

The teamserver.properties file is not updating after  running the
repotools-jts createTables.

The tasks we have done for migrating data from Derby to Db2

1.Taken Backup using repotools-jts  export toFile=JTSData.tar and for
CCM
also.
2.Modified teamserver.properties backup file.
which I modified.
3.Repotools-jts createTables (As it was my new DB2 installation)
4.The teamserver.properties file is not updating
5.And imported using repotools-jts  import fromFile=JTSData.tar and did
same for CCM also
6.Server Started.

But still the server is connected to Derby Database.

The following is teamserver.properties file:

###############################################################################
# Licensed Materials - Property of IBM
# (c) Copyright IBM Corporation 2005, 2011. All Rights Reserved.
#
# Note to U.S. Government Users Restricted Rights:
# Use, duplication or disclosure restricted by GSA ADP Schedule
# Contract with IBM Corp.
###############################################################################
# Properties file for configuring IBM Team Server

# Database settings

#Data Warehouse Automatic Setup - Set this to false if you have already created the data warehouse manually
com.ibm.team.datawarehouse.db.automatic.setup = true

# JDBC Data Warehouse DB location, specifying this property disables system-based selection of default location
#com.ibm.team.datawarehouse.db.vendor=DERBY
#com.ibm.team.datawarehouse.db.jdbc.location=conf/jts/derby/warehouseDB
#com.ibm.team.datawarehouse.db.net.port=1527

#
# DERBY Configuration
#

# JDBC Repository DB location, specifying this property disables system-based selection of default location
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE
#com.ibm.team.repository.db.vendor = DERBY
#com.ibm.team.repository.db.jdbc.location=conf/jts/derby/repositoryDB

#
# DB2 configuration
#

# Comment out the above lines, uncomment the following five database properties
# and customize the example database location to use DB2.
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE.
com.ibm.team.repository.db.vendor = DB2
com.ibm.team.repository.db.jdbc.location=//nukala-pc:50000/JTS:user=db2admin;password={password};
com.ibm.team.repository.db.jdbc.password=db2admin

# DB2 requires a path where the content tablespace should be created, examples for Win and Linux follow
#com.ibm.team.repository.db.db2.content.tablespace.location=content_tablespace

# Configure the size of the tablespace to be created, in 16K pages.
# This is a hard limit and will need to be raised for a production database.
# Your DB2 DBA will need to monitor the utilization of the CONTENTS tablespace and grow it as needed.
# Defaulting to 250,000 pages, or 4GB.
#com.ibm.team.repository.db.db2.content.tablespace.numpages=250000


# Comment out the Derby datawarehouse properties, uncomment the following
# five lines and customize the location to use DB2 for managing datawarehouse.
com.ibm.team.datawarehouse.db.vendor = DB2
com.ibm.team.datawarehouse.db.jdbc.location=//nukala-pc:50000/JTSDW:user=db2admin;password={password};
com.ibm.team.datawarehouse.db.jdbc.password=db2admin
# The path where the warehouse tablespace should be created
com.ibm.team.datawarehouse.db.base.folder = C:\\jazzdw\\tempspace32k
# The database user for whom proper permissions will be granted
com.ibm.team.datawarehouse.report.user = dwadmin

#
# Oracle configuration
#

# Comment out above lines, uncomment the following lines and customize example location to use Oracle
# Note:  Oracle location URLs can take several forms.  The examples here will work under most circumstances.
# Please consult the Oracle JDBC documentation for more details.
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE ORACLE USER or DATABASE 
#com.ibm.team.repository.db.vendor = ORACLE
# localhost connection strings should not include preceding //
#com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/ORCL
# non-localhost connection strings MUST include preceding //
#com.ibm.team.repository.db.jdbc.location=thin:jazzDBuser/{password}@//oracleserver.example.com:1521/ORCL
#com.ibm.team.repository.db.jdbc.password=jazzDBpswd

#com.ibm.team.datawarehouse.db.vendor = ORACLE
# localhost connection strings should not include preceding //
#com.ibm.team.datawarehouse.db.jdbc.location=thin:jazzDBuser/{password}@localhost:1521/ORCL
# non-localhost connection strings MUST include preceding //
#com.ibm.team.datawarehouse.db.jdbc.location=thin:jazzDBuser/{password}@//oracleserver.example.com:1521/ORCL
#com.ibm.team.datawarehouse.db.jdbc.password=jazzDBpswd
# The path where the warehouse tablespace should be created
#com.ibm.team.datawarehouse.db.base.folder = /jazzdw
# The database user for whom proper permissions will be granted
#com.ibm.team.datawarehouse.report.user = RPTUSER

# Sql Server configuration
#

# Comment out above lines, uncomment the following six lines and customize example location to use Sql Server
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE
#com.ibm.team.repository.db.vendor = SQLSERVER
#com.ibm.team.repository.db.jdbc.location=//localhost:1433;databaseName=jazz;user=jazzDBuser;password={password};
#com.ibm.team.repository.db.jdbc.password=jazzDBpswd

#com.ibm.team.datawarehouse.db.vendor = SQLSERVER
#com.ibm.team.datawarehouse.db.jdbc.location=//localhost:1433;databaseName=jazz;user=jazzDBuser;password={password};
#com.ibm.team.datawarehouse.db.jdbc.password=jazzDBpswd
# The path where the warehouse tablespace should be created
#com.ibm.team.datawarehouse.db.base.folder = /jazzdw
# The database user for whom proper permissions will be granted
#com.ibm.team.datawarehouse.report.user = RPTUSER

#
# DB2i configuration
#

# Comment out above lines, uncomment the following six lines and customize example location to use DB2i
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE
#com.ibm.team.repository.db.vendor = DB2i
#com.ibm.team.repository.db.jdbc.location=//hostname;hold statements=true;metadata source=1;user=jazzDBuser;password={password};
#com.ibm.team.repository.db.jdbc.password=jazzDBpswd

#com.ibm.team.datawarehouse.db.vendor = DB2i
#com.ibm.team.datawarehouse.db.jdbc.location=//hostname;hold statements=true;metadata source=1;user=jazzDBuser;password={password};
#com.ibm.team.datawarehouse.db.jdbc.password=jazzDBpswd
# The database user for whom proper permissions will be granted
#com.ibm.team.datawarehouse.report.user = RPTUSER

#
# DB2z configuration
#
# NOTE THAT EVERY APPLICATION INSTANCE AND JAZZ TEAM SERVER REQUIRES ITS OWN UNIQUE DATABASE

#com.ibm.team.repository.db.vendor = db2z
# Location name of the DB2z sub-system.
# ipAddress, ipPort and location be obtained by running the DB2 command -DISPLAY DDF
#com.ibm.team.repository.db.jdbc.location=//ipAddress:ipPort/location:user=jazzDBuser;password={password};
#com.ibm.team.repository.db.jdbc.password=jazzDBpswd
# DB2z repository Database name - must be unique for each database in the same DB2z subsystem
#com.ibm.team.repository.db.db2.dsn.dbname=JAZZDB
#DB2z schema prefix - must be unique for each database in the same DB2z subsystem
#com.ibm.team.repository.db.schemaPrefix=xx

#com.ibm.team.datawarehouse.db.vendor = db2z
#com.ibm.team.datawarehouse.db.jdbc.location=//ipAddress:ipPort/location:user=jazzDBuser;password={password};
#com.ibm.team.datawarehouse.db.jdbc.password=jazzDBpswd
# The database user for whom proper permissions will be granted
#com.ibm.team.datawarehouse.report.user = RPTUSER
#com.ibm.team.datawarehouse.db.db2.dsn.dbname=RIDW

#
# J2EE database connection example
#
#com.ibm.team.repository.db.type = J2EE
#com.ibm.team.repository.db.vendor=<VENDOR>
#com.ibm.team.repository.db.j2ee.dataSource = /jdbc/jazz

# Setting this value to 'true' opens a wide security hole. Only set it to 'true'
# in development time, when security isn't important and the developer
# doesn't wish to spend time configuring true J2EE authentication.
com.ibm.team.repository.ws.allow.identity.assertion = false

com.ibm.team.repository.web.suppressedPages = {"com.ibm.team.repository.web.admin": \
 ["com.ibm.team.repository.provision"]}

com.ibm.team.repository.web.helpuri = /clmhelp/index.jsp

#
# Freshness specification, in seconds, for ChangeEvent scrubbing.  Items older than this are
# deleted from the database.  For the itemTypes WorkItem and BuildResult (as specified in
# "changeEvent.expirationByType") freshness spec is 60 days and 2 days, respectively.  The
# default age, (as specified in "changeEvent.expirationDefault") is 14 days.
#
# All times must be represented in seconds.
#
# Values for the "changeEvent.expirationByType" and "changeEvent.expirationByCategory"
# properties are space-delimited.  Each value is a tuple of
# itemType shortName or longName, separated by ':', followed by a maxage
# value in seconds.  Whitespace is not allowed between the itemType, ':', and
# maxage value.  For "expirationByCategory", "itemType" is replaced by a category
# string, as would be found in the category field of ChangeEvent.
#
com.ibm.team.repository.changeEvent.expirationDefault = 1209600
#com.ibm.team.repository.changeEvent.expirationByType = com.ibm.team.workitem.WorkItem:5184000 com.ibm.team.build.BuildResult:172800
com.ibm.team.repository.changeEvent.expirationByCategory = SystemLog:259200

# Fulltext index location
com.ibm.team.fulltext.indexLocation=C:/IBM/JazzTeamServer/server/conf/jts/indices/workitemindex

# Location of JFS index root directory
com.ibm.team.jfs.index.root.directory=C:/IBM/JazzTeamServer/server/conf/jts/indices


2 answers



permanent link
Charlie Seo (22127) | answered Apr 15 '14, 2:53 a.m.
Can't clearly grab what's happening to you but I can presume, there might be caching issue as well as JDBC driver you  might need to check.

You sounded like using tomcat then remove the ../server/tomcat/work/*.* after adding jdbc driver and restart to see what happens.

permanent link
Krzysztof Ka┼║mierczyk (7.4k34997) | answered Apr 15 '14, 3:17 a.m.
Charlie answer is good. Another think you can try is just to rerun setup application (https://your-server/jts/setup) and just navigate to the steps with database configuration.

Please also notice that you need to change your database for all applications, not for jts only. This requires repeating all the steps (repotools commands, modification in teamserver.properties) for all jts, ccm and qm (if you use it).

Your answer


Register or to post your answer.