DB2 Issue while Upgrading to DBB 2.0.1

[Todd0513]

I'm getting a -803 on the metadataStore.copyCollection when trying to clone my master branch to my dev branch. Has anyone encountered this and if so, what solution did you find that worked?
com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,SQLERRMC=PCPERMX1;00000043BF, Driver=4.22.37
Caught: groovy.lang.MissingMethodException: No signature of method: build.finalizeBuildProcess() is applicable for argument types: (LinkedHashMap, Integer)

[dennis-behm]

Hi @Todd0513 ,

this almost sounds like that you have not applied the database schema changes, that are mandatory for 2.0.1.
Can you please verify, if you have applied those? In the upgrade script from 2.0.0 to 2.0.1 there some constraints are dropped.
You find them at at the DBB toolkit installation in the: /usr/lpp/dbb/v2r0/ddl/upgrade_DB2_2.0.1.sql

Link to the documentation: https://www.ibm.com/docs/en/dbb/2.0?topic=dbb-upgrading-db2-db2-zos-database

Thanks

[Todd0513]

Thanks Dennis! I will get that submitted. Any thoughts on what is causing it?

[dennis-behm]

@Todd0513 I ran into a similar issue recently:

I made the mistake and forgot that zAppBuild clones DBB collections for feature branches. The cloning then copies the ownership of collections.

In my case the owner of the collection of the mainBuildBranch let's say MortgageApplication-main was my personal user (I ran some tests from the cli), while my build was executed under the pipeline orchestrator user (Jenkins) which is then not allowed to update the copied collection metadata for the feature branch because of the mismatch of the ownership.

Please double check the owners of your collections and the user that is running the pipeline build.

[Todd0513]

Good to know! To check these, this is the data stored in the DB2 tables for the collections and the permissions tables?

[dennis-behm]

Yes, It's in the DBBCOLLECTION table. Alternatively, you can also use the DBB CLI to inspect the owner. I recommend to stay with the legacy cmds .

dbb collection view MortgageApplication-main-outputs --type db2 --db2-config /var/dbb/config/db2Connection_Jenkins.conf --password-file /var/dbb/config/db2-pwd-file.xml --user DBEHM

[Todd0513]

Thanks Dennis! This is VERY helpful!

[Todd0513]

@dennis-behm Hello Dennis! I have another question on the DBB 2.0 upgrade...in my test project, I removed a source code but left the related copybooks because I still have other source using those copybooks. But when I change one of those copybooks to test the impact, it still attempts to pull in the source I removed.
To remove it, I simply deleted it from the project. Is there another process I should have done to have "properly" updated the impact data? And now that I have removed it, is there a way to clean-up the impact data?
Thanks!

[dennis-behm]

@Todd0513 - would you mind to open another discussion thread for this, please? I'll respond to this one then in detail.

In short: computing the relative path of a deleted file (dependency information are stored in the DBB Metadatastore per repository file) is tricky, because we cannot test if the file exists. zAppBuild already supports multiple repository layouts, and I assume the default settings which is assumed for the deletion case, does not match yours.

[Todd0513]

Yes, I'll open a new thread. Thanks Dennis!