E
dit
A
ttach
P
rintable
r14 - 2015-05-27 - 17:00:22 - Main.sbagot
You are here:
TWiki
>
Deployment Web
>
DeploymentTroubleshooting
>
UpgradeTroubleshooting
>
CLMUpgradeTroubleshooting
>
AddDatabaseTables
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="" alt="" width="50" height="50" align="right"/> Add database tables (CCM, QM, JTS) %DKGRAY% Authors: [[UpgradeTroubleshootingTeam][UpgradeTroubleshootingTeam]] <br> Build basis: CLM 4.x and later %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> This page will discuss troubleshooting techniques and known issues that arise during the addTables step in the upgrade process. ---++ Troubleshooting During this step in the upgrade process, a log file appended with _addTables will be created in the ../server directory of the Collaborative Lifecycle Management (CLM) application installation directory. An example of this file is: <verbatim> repotools-ccm_addTables.log </verbatim> ---++ Known Issues Below are some known issues which arise during the addTables step in the upgrade process ---+++ Jazz Team Server errors This section will discuss errors common when adding database tables to the Jazz Team Server (JTS) database. ---++++Invalid object name 'RIODS.TIMELINE' *Version:* Upgrade to 4.0.0.1 <br> *Error During Upgrade:* Invalid object name 'RIODS.TIMELINE'. com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'RIODS.TIMELINE'. <br> *Cause:* This error is caused by [[https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=231471][defect 231471]] which is fixed in 4.0.1. You will notice this errors if you do not have a DW schema setup for your current JTS server before proceedng the upgrade. <br> *Resolution:* This error can be ignored as it does not block your JTS from upgrading successfully. ---+++CCM-specific errors This section will discuss errors common when adding Database tables to the Rational Team Concert (CCM) database. ---++++CRJAZ0350I Error fetching item values *Version:* Upgrade to 4.x <br> *Error During Upgrade:* <verbatim> CRJAZ0350I Error fetching item values. statement = Select S.VAL_ENCODING, S.ITEM_VALUE From REPOSITORY.ITEM_STATES S Join REPOSITORY.ITEM_TYPES T on T.ITEM_UUID = S.ITEM_UUID Where S.KEY_UUID = ? parameter[0] = xxxxxxx </verbatim> *Cause:* There are some corrupted item states in your current ccm repository database. They need to be fixed first before procceding ccm upgrade. <br> *Resolution:* Run [[https://jazz.net/wiki/bin/view/Main/L3DevTool][Online Verify Tool ]] to try identifying the problematic item state and fixing them. The best practice is to perform data integrity check against your current jts and ccm repository DBs to ensure data is in a consistent state *prior* to proceeding the upgrade. ---+++QM-specific errors | IN PROGRESS | This section will discuss errors common when adding Database tables to the Rational Quality Manager (QM) database. ---+++RM-specific errors | IN PROGRESS | This section will discuss errors common when adding Database tables to the Rational Requirements Composer (RM) database. ---+++Errors that can occur with any CLM application This section will discuss errors common when adding the Database tables to any application within the CLM (they are not application specific). ---++++CRJAZ1093I xxxx service class was not activated *Version:* Any upgrade version 4.x <br> *Error During Upgrade:* CRJAZ1093I xxxx service class was not activated <br> *Cause:* The server is unable to connect to the repository database to perform the addTables command. <br> *Resolution:* Ensure the jdbc driver is in the proper location according to upgrade instruction and it is compatible with the JDK version repotools runs on. For example, when connecting to SQL server DB, sqljdbc.jar works with the JDK 1.5, sqljdbc4.jar works with the JDK 1.6. For Oracle, JDK 1.5 use ojdbc5.jar, JDK 1.6 use ojdbc6.jar. The ojdbc14.jar driver will not connect to Oracle 11G etc. ---++++ORA-01031: Insufficient privileges *Version:* Any upgrade version 4.x <br> *Error During Upgrade:* java.sql.SQLException: ORA-01031: insufficient privileges <br> *Cause:* The JDBC Connection user does not have enough privileges to run the necessary commands to add the tables to the database. <br> *Resolution:* Ensure the JDBC Connection user has DBO permissions on all CLM applications, including databases for jts, qm, ccm, dw and rm. Note that the creation of the warehouse on Oracle requires more permissions as compared to other databases. When you specify the database user in the connection spec for data warehouse, ensure that the database user has DBA permissions. Then you can configure a smaller subset of permissions after the original creation, as identified on [[https://jazz.net/wiki/bin/view/Main/MoreControlOverTheOracleDataWarehouseSetup][More Control Over the Oracle DW Setup]] article. ---++++ Unable to create Index MARKERS_UNIQUE_MARKER *Version:* 4.0.4, SQL Server DB (may also occur on Oracle DB) <br> *Error During Upgrade:* The following SQL query did not execute properly on the server: CREATE UNIQUE INDEX MARKERS_UNIQUE_MARKER <BR> May be followed by oracle error: ORA-01450: maximum key length (6398) exceeded <br> *Cause:* This is caused by a 900 byte limit on MS SQL DBs, where the UUIDs are too long and hit the byte limit. <br> *Resolution:* This is a known defect tracked via [[https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=280057][jazz.net Defect 280057]], planned to be resolved in 4.0.5. This is referenced in the following techote: [[http://www-01.ibm.com/support/docview.wss?uid=swg21649768][Upgrading CLM products to version 4.0.4 fails when using Microsoft SQL Server]] <BR> <BR> As a *workaround*, only upgrade to 4.0.3, or [[http://www-01.ibm.com/software/rational/support/contact.html][contact IBM Support]] for a hotfix on 4.0.4. <BR> On *Oracle* DB, a similar error may occur due to the NLS_SEMANTICS_LENGTH configuration being _char_. Changing this to _byte_ will resolve the issue. ---+++++!! Related topics: * For more upgrade troubleshooting topics, refer to [[UpgradeTroubleshooting][Upgrade Troubleshooting]]. ---+++++!! External links: None ---+++++!! Additional contributors: MainTwiki.StephanieBagot, MainTwiki.SusanWu <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r14
<
r13
<
r12
<
r11
<
r10
|
M
ore topic actions
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
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
.