Customer upgraded Connections from 4.5 CR5 to 5.0 CR2 and also introduced Cognos with the new environment. After migrating the data I tried to run the “build-all.bat” script to recreate all cube data. However that script failed without any meaningful error message.
I then ran the “config-installation-verify.bat” script and I got a failed message for the Transformer component. This time I got the following error in the transformer verify log:
[codesyntax lang=”text”]
|
1 2 3 4 5 6 7 8 9 |
Tue 30 Jun 2015 4:54:41 PM 4 000042AB Timing, OPEN DATA SOURCE,00:00:00 Tue 30 Jun 2015 4:54:41 PM 2 00000161 (TR2317) The level 'COMMUNITY NAME' is designated as unique. Source value '10025' was used in an attempt to create a category in the path ( By COMMUNITY_ID,f,3~798,( Blank )~799,( Blank )~800,( Blank )~801,( Blank )~802,10025 ). '10025' already exists in level 'COMMUNITY NAME' in the path ( By COMMUNITY_ID,9,9~1,( Blank ),( Blank )~2,( Blank )~3,( Blank )~4,10025 ). [->OK] Tue 30 Jun 2015 4:54:41 PM 2 000042AB (TR2318) Transformer has detected 1 attempts to create a category in more than one path. Refer to the online help for a detailed explanation of level uniqueness. [->OK] Tue 30 Jun 2015 4:54:41 PM 4 000042AB End processing 4447 records from data source 'D_COMMUNITY~1'. Tue 30 Jun 2015 4:54:41 PM 4 000042AB Timing, READ DATA SOURCE,00:00:00 Tue 30 Jun 2015 4:54:42 PM 4 000042AB End cube update. Tue 30 Jun 2015 4:54:42 PM 4 000042AB Timing, TOTAL TIME (CREATE CUBE),00:00:02 Tue 30 Jun 2015 4:54:42 PM 2 000042AB (TR0136) A uniqueness violation was detected. The process has been aborted. [->OK] Transformer Tue Jun 30 16:54:42 2015 |
[/codesyntax]
This seemed to be a problem which was already introduced after upgrading 4.5 CR4 to CR5 but was not visible because the customer did not have installed Cognos in the old 4.5 environment.
To solve the issue we run a “cognos-configure-update.bat” (make sure the “cognos-setup.properties” contains the correct uernames and passwords for the database uses). After that the “build-all.bat” script was running sccessfully.
I got the same error after a migration of the METRICS database after running build-all.sh. Sorted after running the update shell script.