How can this error be worked around ?
64 bit aix, db2 9.5
Trying to upgrade a 3.0.1.3 CLM to 4.0.0.1. The repotools-jts.sh -addTables spins for a bit and then fails with this message: Caused by: com.ibm.team.repository.common.InternalRepositoryException: CRJAZ0329I SQL statement execution failedSyntax error or access rule violationSQL: Insert Into {REPOSITORY.CONTEXT_SUBCONTEXTS} ({CONTEXT_UUID}, {SUBCONTEXT_UUID}, {OWNING_CONTEXT_UUID}, {REVISION_NUMBER}) select ?, ?, ?, ? from sysibm.sysdummy1 where not exists (select * from {REPOSITORY.CONTEXT_SUBCONTEXTS} where {CONTEXT_UUID}=? and {SUBCONTEXT_UUID}=? and {OWNING_CONTEXT_UUID}=?)SQL Exception #1SQL Message: DB2 SQL Error: SQLCODE=-418, SQLSTATE=42610, SQLERRMC=null, DRIVER=3.57.82SQL State: 42610Error Code: -418SQL Exception #2SQL Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-418;42610;, DRIVER=3.57.82SQL State: 56098Error Code: -727Exception Details: Vendor specific exceptionSQL Exception #3SQL Message: DB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-418;42610;, DRIVER=3.57.82SQL State: 56098Error Code: -727Exception Details: Vendor specific exception Asking DB2 about -418: SQL0418N A statement contains a use of a parameter marker that is not valid. Explanation: Untyped parameter markers cannot be used: * in a SELECT list * as the sole argument of a datetime arithmetic operation * in some cases as the sole argument of a scalar function * as a sort key in an ORDER BY clause * as an argument of an XMLQUERY, XMLEXISTS or XMLTABLE expression. * as an argument of UNNEST, CARDINALITY, MAX_CARDINALITY or TRIM_ARRAY, or used in array element specification. * on the left hand side of an assignment statement when the data type of the right hand side cannot be determined Parameter markers can never be used: * in a statement that is not a prepared statement * in the fullselect of a CREATE VIEW statement * in the triggered action of a CREATE TRIGGER statement I tried this from 3.0.1 level of CLM and got the same failure, then I upgraded to 3.0.1.3 and retried. |
Accepted answer
I think you may need to upgrade your version of DB2.
This article https://jazz.net/library/article/811#Databases lists 9.7 as the required version. Kevin Ramer selected this answer as the correct answer
Comments
Kevin Ramer
commented Nov 14 '12, 2:11 p.m.
I had that suspicion. This is just a 'test drive' for upgrading from v3 to v4 and our production CLM is on db2 v9.7 already.
|
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.