It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×267
×54

question asked: Sep 21 '12, 3:25 a.m.
question was seen: 5,561 times
last updated: Sep 27 '12, 9:18 a.m.

Related questions

error running repotools.sh -addTables during upgrade from 3.0.1.3 to 4.0.0.1

1
Robin Parker (326●3●37●39) | asked Sep 21 '12, 3:25 a.m.
 HI all,

I am doing a test upgrade on a copy of our live databases.

I am running the its-upgrade.sh script on our RHEL 5 server and during the addTables phase a DB2 error pops out.

The log file shows the DB2 error as well as some more information:

2012-09-21 08:12:57,647 Running post addTables for "com.ibm.team.reports"...

2012-09-21 08:13:01,027 DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=RIODS.TIMELINE, DRIVER=3.57.82

com.ibm.db2.jcc.am.io: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=RIODS.TIMELINE, DRIVER=3.57.82

        at com.ibm.db2.jcc.am.bd.a(bd.java:676)

        at com.ibm.db2.jcc.am.bd.a(bd.java:60)

        at com.ibm.db2.jcc.am.bd.a(bd.java:127)

        at com.ibm.db2.jcc.am.km.c(km.java:2506)

        at com.ibm.db2.jcc.am.km.d(km.java:2483)

        at com.ibm.db2.jcc.am.km.a(km.java:1963)

        at com.ibm.db2.jcc.t4.db.g(db.java:139)

        at com.ibm.db2.jcc.t4.db.a(db.java:39)

        at com.ibm.db2.jcc.t4.t.a(t.java:32)

        at com.ibm.db2.jcc.t4.sb.h(sb.java:135)

        at com.ibm.db2.jcc.am.km.eb(km.java:1934)

        at com.ibm.db2.jcc.am.lm.ic(lm.java:2798)

        at com.ibm.db2.jcc.am.lm.b(lm.java:3517)

        at com.ibm.db2.jcc.am.lm.Vb(lm.java:654)

        at com.ibm.db2.jcc.am.lm.executeQuery(lm.java:628)

        at com.ibm.team.repository.service.internal.db.jdbcwrappers.stat.PreparedStatementStatWrapper.executeQuery(PreparedStatementStatWrapper.java:60)

        at com.ibm.team.repository.service.internal.db.jdbcwrappers.errlog.PreparedStatementErrLogWrapper.executeQuery(PreparedStatementErrLogWrapper.java:78)

        at com.ibm.team.repository.service.internal.db.jdbcwrappers.leak.PreparedStatementLeakWrapper.executeQuery(PreparedStatementLeakWrapper.java:57)

        at com.ibm.team.datawarehouse.service.etl.util.DataWarehouseFunctions.fixupURLs(DataWarehouseFunctions.java:308)

        at com.ibm.team.datawarehouse.service.internal.common.CommonRemoteSnapshotService.fixupSnapshot(CommonRemoteSnapshotService.java:274)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$2.run(AbstractRemoteSnapshotService.java:290)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254)

        at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)

        at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy198.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:29)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy793.write(Unknown Source)

        at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.fixupData(AbstractRemoteSnapshotService.java:285)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy283.fixupData(Unknown Source)

        at com.ibm.team.datawarehouse.service.internal.InternalDataWarehouseService.fixupURLs(InternalDataWarehouseService.java:959)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy280.fixupURLs(Unknown Source)

        at com.ibm.team.reports.service.internal.ReportsMigrationHandler.postAddTables(ReportsMigrationHandler.java:196)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy781.postAddTables(Unknown Source)

        at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.doPostAddTables(MigrationHandlerDispatcher.java:688)

        at com.ibm.team.repository.migration.internal.service.MigrationHandlerDispatcher.postAddTables(MigrationHandlerDispatcher.java:680)

        at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:1429)

        at com.ibm.team.repository.service.internal.rdb.DatabaseMaintenanceService.performPostAddTables(DatabaseMaintenanceService.java:340)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)

        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)

        at $Proxy190.performPostAddTables(Unknown Source)

        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:85)

        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand$1.run(AddTablesCommand.java:1)

        at com.ibm.team.repository.service.internal.TeamServiceContext.runAsAdmin(TeamServiceContext.java:141)

        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.addTables(AddTablesCommand.java:60)

        at com.ibm.team.repotools.commands.local.internal.AddTablesCommand.execute(AddTablesCommand.java:166)

        at com.ibm.team.repotools.command.AbstractCommand.execute(AbstractCommand.java:66)

        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.run(RepositoryToolsApplication.java:768)

        at com.ibm.team.repotools.rcp.internal.RepositoryToolsApplication.start(RepositoryToolsApplication.java:843)

        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)

        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:600)

        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)

        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)

        at org.eclipse.equinox.launcher.Main.run(Main.java:1408)

        at org.eclipse.equinox.launcher.Main.main(Main.java:1384)

2012-09-21 08:13:01,321 Post addTables for com.ibm.team.reports took 3674 ms.


I assume its not safe to ignore this error?  Any idea how to resolve it?

Many Thanks,

Robin
Comments

Accepted answer

2
permanent link
Rosa Naranjo (2.9k●1●17●23) | answered Sep 26 '12, 5:50 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Using the link provided by Bo, in the comment above, to defect 232642, it appears that this error can be ignored.  It appears that in all other cases, the -addtables completes.  the user can get around this by running upgradewarehouse first and then addtables.  we understand that this is a deviation from the how the script runs the repotools commands. the issue has been taken care of for the next release, 4.0.1.

Robin, does this make sense? if so, please confirm.
Robin Parker selected this answer as the correct answer

3 other answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
T M (887●8●188●143) | answered Sep 21 '12, 12:12 p.m.
I think some DB2 variable is not set in your application server setup.
0
permanent link
Robin Parker (326●3●37●39) | answered Sep 23 '12, 1:29 p.m.
 It appears that the problem is that when the its_upgrade.sh script runs the retools-jts.sh -addTables, it expects the RIODS.TIMELINE table to exist in the data warehouse.  This table isn't added to the data warehouse until the next step: retools-jts.sh -upgradeWarehouse.

If I let the jts-upgrade.sh script complete and then run a new repotools-jts.sh -addTables, then the error doesn't appear.

I'm going to assume that doing this means that the database is in the correct state afterwards.
Comments
Rosa Naranjo commented Sep 25 '12, 12:03 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

Robin, had you configured a data warehouse at all with the 301 installation?
The sequence when running jts_upgrade is that it is supposed to do a repotools-jts -addtables first, then followed by a repotools-jts -upgradeWarehouse. My understanding is that the repotools-jts -addtables is working solely with the JTS repository DB and not the DW database.
For this test, do you make copies of both the JTS and the DW databases?
0
permanent link
Robin Parker (326●3●37●39) | answered Sep 27 '12, 2:57 a.m.
  Hi Rosa,
It looks like the error can be ignored, which is good.

I did try running the upgradeWarehouse command first as well but this doesn't work either I'm afraid.  The upgradeWarehouse (run from the 4.0.0.1 installation) complains that the JTS database (which is still at 3.x version because I haven't run -addTables yet) is at the wrong version.  So its a chicken and egg situation.

That the error can be ignored is good enough for me.  ;o)

(Apologies for adding this as an answer - I tried to add it as a comment to one of the other answers but it wouldn't let me save - it kept saying '10 characters needed' and the Post Comment button stayed greyed out)
Comments
Bo Chulindra commented Sep 27 '12, 9:18 a.m.
JAZZ DEVELOPER

for the problem with the comment, see https://jazz.net/forum/questions/89178/is-it-possible-to-add-a-screenshot-when-posting-a-forum-comment

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.