RTC 1.0.1.1 repotools -export seems to be hanging
I am trying to use repotools -export on my RTC 1.0.1.1 server. It starts up fine, but seems to hang. No export file is created. Here is the output of repotools_export.log... it has been sitting at that last message for 90+ minutes now:
2009-07-10 14:02:36,745 repotools -export toFile=./exportUAT20090710.tar
2009-07-10 14:02:36,752 Repo Tools, Version 1.0.1.1 - M20090225-1543
2009-07-10 14:02:36,754 Provisioning using "./provision_profiles".
2009-07-10 14:02:49,081 Rational Jazz Team Server - Standard
2009-07-10 14:02:49,105 Loading configuration from "file:teamserver.properties".
2009-07-10 14:02:50,484 Attempting Initial Database Connection Using
Db Name/Location: //localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;
2009-07-10 14:02:55,182 Initial database connection successful
Db Product Name: DB2/LINUX
Db Product Version: SQL09051
Db URL: jdbc:db2://localhost:50001/JAZZ
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.6.60
2009-07-10 14:02:57,506 CRJAZ8192E: Fulltext Index Location: workitemindex/fulltext_index/
2009-07-10 14:03:05,370 The user "ADMIN" has logged in to the database "//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;".
2009-07-10 14:03:05,390 Exporting the data from the database "//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;" to the file "./exportUAT20090710.tar".
2009-07-10 14:03:05,391 Using encoding "UTF-8"
Using 'top', I can see the process 'db2sysc' using about 20% CPU. The DBA says that the DB2 logs do not show any DB2 problems.
I have no idea how to debug something like this. Can you help? Are there any repotools debug switches I can use to see what is happening?
Thanks in advance,
Dave
2009-07-10 14:02:36,745 repotools -export toFile=./exportUAT20090710.tar
2009-07-10 14:02:36,752 Repo Tools, Version 1.0.1.1 - M20090225-1543
2009-07-10 14:02:36,754 Provisioning using "./provision_profiles".
2009-07-10 14:02:49,081 Rational Jazz Team Server - Standard
2009-07-10 14:02:49,105 Loading configuration from "file:teamserver.properties".
2009-07-10 14:02:50,484 Attempting Initial Database Connection Using
Db Name/Location: //localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;
2009-07-10 14:02:55,182 Initial database connection successful
Db Product Name: DB2/LINUX
Db Product Version: SQL09051
Db URL: jdbc:db2://localhost:50001/JAZZ
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.6.60
2009-07-10 14:02:57,506 CRJAZ8192E: Fulltext Index Location: workitemindex/fulltext_index/
2009-07-10 14:03:05,370 The user "ADMIN" has logged in to the database "//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;".
2009-07-10 14:03:05,390 Exporting the data from the database "//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;" to the file "./exportUAT20090710.tar".
2009-07-10 14:03:05,391 Using encoding "UTF-8"
Using 'top', I can see the process 'db2sysc' using about 20% CPU. The DBA says that the DB2 logs do not show any DB2 problems.
I have no idea how to debug something like this. Can you help? Are there any repotools debug switches I can use to see what is happening?
Thanks in advance,
Dave
2 answers
Try sending kill -3 to the java process for repotools. This will generate a
javacore file with the stacktraces of the running threads. You can attach
that to a work item filed against Jazz Foundation->Repository and we can
take a look.
I assume also the Jazz Server is completely stopped?
--
Ritchie Schacher
Jazz Server Development
"deweber" <deweber> wrote in message
news:h385am$10o$1@localhost.localdomain...
javacore file with the stacktraces of the running threads. You can attach
that to a work item filed against Jazz Foundation->Repository and we can
take a look.
I assume also the Jazz Server is completely stopped?
--
Ritchie Schacher
Jazz Server Development
"deweber" <deweber> wrote in message
news:h385am$10o$1@localhost.localdomain...
I am trying to use repotools -export on my RTC 1.0.1.1 server. It
starts up fine, but seems to hang. No export file is created. Here
is the output of repotools_export.log... it has been sitting at that
last message for 90+ minutes now:
2009-07-10 14:02:36,745 repotools -export
toFile=./exportUAT20090710.tar
2009-07-10 14:02:36,752 Repo Tools, Version 1.0.1.1 - M20090225-1543
2009-07-10 14:02:36,754 Provisioning using
"./provision_profiles".
2009-07-10 14:02:49,081 Rational Jazz Team Server - Standard
2009-07-10 14:02:49,105 Loading configuration from
"file:teamserver.properties".
2009-07-10 14:02:50,484 Attempting Initial Database Connection Using
Db Name/Location:
//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;
2009-07-10 14:02:55,182 Initial database connection successful
Db Product Name: DB2/LINUX
Db Product Version: SQL09051
Db URL: jdbc:db2://localhost:50001/JAZZ
Jdbc Driver Name: IBM DB2 JDBC Universal Driver Architecture
Jdbc Driver Version: 3.6.60
2009-07-10 14:02:57,506 CRJAZ8192E: Fulltext Index Location:
workitemindex/fulltext_index/
2009-07-10 14:03:05,370 The user "ADMIN" has logged in to
the database
"//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;".
2009-07-10 14:03:05,390 Exporting the data from the database
"//localhost:50001/JAZZ:fullyMaterializeLobData=false;user=xxxxxxxx;password=xxxxxxxx;"
to the file "./exportUAT20090710.tar".
2009-07-10 14:03:05,391 Using encoding "UTF-8"
Using 'top', I can see the process 'db2sysc' using about 20% CPU. The
DBA says that the DB2 logs do not show any DB2 problems.
I have no idea how to debug something like this. Can you help? Are
there any repotools debug switches I can use to see what is
happening?
Thanks in advance,
Dave