Common Model Upgrader Errors
Cognos ICM
January 2015
CONTENTS
Contents ........................................................................................................................................................................1
Error at Update 660 ...............................................................................................................................................2
Error at Update 758 ...............................................................................................................................................3
Error at Update 759 ...............................................................................................................................................5
Error at Update 762 ...............................................................................................................................................6
Error at Update 811 ...............................................................................................................................................7
Error at Update 823 ...............................................................................................................................................8
Error at Update 842 ...............................................................................................................................................9
Error at Update 866 .............................................................................................................................................10
Error at Update 873 .............................................................................................................................................11
Error at Update 878 .............................................................................................................................................12
Error at Update 915 .............................................................................................................................................13
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
1
ERROR AT UPDATE 660
What Does This Mean?
The listed table(s) has invalidated referential integrity.
To Resolve
Examine the picklist items to the values in the picklisted tables. Ensure that the values match.
Example Error Message
The following table(s) contain invalid data. Please correct the data and try again.
- Payee
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
2
ERROR AT UPDATE 758
Issue:
Starting v7.2, computed columns must begin with a letter, and contain only letters, numbers, and spaces. During
the upgrade to Varicent 7.2+, you may encounter the following error message:
"UPGRADING VARICENT MODEL ENCOUNTERED THE FOLLOWING ERROR.
CANNOT UPGRADE, THE NEW COLUMN NAME OF THE FOLLOWING COMPUTED COLUMNS MUST
BEGIN WITH A LETTER, AND CONTAIN ONLY LETTERS, NUMBERS, AND SPACES. NO SPECIAL
CHARACTERS ARE ALLOWED.
CC COMPUTED COLUMN (FROM PRESENTER REPORT: PAYEE COMMISSION REPORT; SOURCE: PAYEE
COMMISSION REPORT SOURCE)"
Steps to resolve:
[Preparation: Confirm that the New Column name is known + position (Column #) in Data Grid]
1. Edit the Computed Column so that it begins with a letter and only contains letters, numbers and spaces
2. Edit the Data Grid > Step 3 (Display Options) > there should be 2 new columns added (fixed column with the
change + column without the change), but missing the original problem column in its original position
3. Show the new correctly named column “CC Name 123” by right-clicking > Select Column > Show
4. Drag to desired column position
5. Set the appropriate column width by right-clicking > Set Column Widths
6. Right-click > Select Column > Rename Column > rename with special characters or spaces as desired
7. Click Next and then click Finish
8. Save changes
Repeat for all reports as needed.
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
3
Here is an example to illustrate the above.
Upgrading Varicent Model encountered the following error.
Cannot upgrade, the New Column name of the following Computed Columns must begin with a letter, and
contain only letters, numbers, and spaces. No special characters are allowed.
CC Computed Column (from Presenter Report: Payee Commission Report; Source: Payee Commission
Report Source)
Details of Problem Report
Presenter report: Payee Commission Report
Data Grid: Commission Report Datagrid, using source “CC ComputedColumn”
Computed Column: CC ComputedColumn
Computed Column’s New Column: “%CC_N@me_123”
Computed Column’s Source: Payee Commission Report Source
Steps to resolve:
[Preparation: confirm that the New Column name is known + position (Column #) in Data Grid]
1. Edit the Computed Column so that it begins with a letter and only contains letters, numbers and spaces
2. Edit the Data Grid > Step 3 (Display Options) > there should be 2 new columns added (“CC Name 123” and
“%CC_N@me_123”, but missing the “CC_N@me_123” in its original position
3. Show the correctly named column “CC Name 123” by right-clicking > Selecting Column > Show
4. Drag to desired column position
5. Set the appropriate column width by right-clicking > Set Column Widths
6. Right-click > Select Column > Rename Column > rename with special characters or spaces as desired
7. Click Next and then click Finish
8. Save changes
Repeat for all reports as needed.
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
4
ERROR AT UPDATE 759
Issue:
Update 759 is about sort orders of section breaks. The user friendly error message provides details on what needs
to be changed.
Typical actions to resolve:
You'll be re-ordering the sort order so that there isn't a sort on a column that follows either a Date type or Value
type field.
Example of error:
Unable to upgrade because the following violate rules for valid sections:
Presenter report: 'Problem Presenter Report'
Datagrid: 'dgDataGrid'
column 'ValueOrDate' in section 'Total'
Rules for sections:
1) All sort fields sequenced after a Date type field (excluding the Date column) are not valid to be sections
2) All sort fields sequenced after a Value type (including the Value column) are not valid to be sections
3) For all other cases, all sort fields are valid sections
To fix: re-order sort columns or delete the offending section.
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
5
ERROR AT UPDATE 762
What does this mean?
This model has the following errors with web form source validation rules:
A rule in the webform <Webform name> in component <Component Name> is missing source <Source Name>
Resolution
1.) Open up model and navigate to the Webform named in the error message.
2.) You will then need to look for the source named in the error message in each of the row sources. You can do
this by right clicking on the first row source, then navigating to step 4, validation rules.
If the source named appears in the Upgrader error message, you will need to remove it.
If the source is not present, proceed to the next row source and continue until you find the offending source.
3.) Exit the Admin client and re-run the Model Upgrader.
Example Error Message
This model has the following errors with web form source validation rules:
A rule in the web form WF -Landing Page in component Web Fiorms is missing source WebUser
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
...
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
6
ERROR AT UPDATE 811
What does this mean?
Aggregated Transformations in Presenter cannot be partitioned by Comment type columns
How to Fix?
Remove the offending partition
1. Locate the offending Aggregate Transformation within the referenced Presenter reports
2. Remove the offending partition from the Aggregate Transformation
3. In the Data Grid where the partition was used, remove the Comment partition reference in Step 2 of Data Grid
Wizard
4. In the Data Grid where the partition was used, update the Section Break in Step 4 of Data Grid Wizard by
editing the Section Break, deleting and re-adding the source related to the Comment partition
5. Reset Column Widths in the Data Grid where the partition was used
6. Save your changes
Example Error Message
Please resolve the following items and try upgrading again:
Presenter report 'Compensation Presenter':
Aggregate transformation 'Agg DataSource2' uses 'DataSource2'.'Comments' as a partition but 'Comments' is of
type Comment/URL
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
7
ERROR AT UPDATE 823
What does this mean?
This error means that all tables that are of type "Territory", such as terrTerritory, will need to be removed from the
model.
Possible Resolutions:
1. Remove terrTerritory and its dependent calcs, reports, web forms, and so forth. As you try to delete the
upstream object, Varicent throws a warning if there are downstream dependent objects
Or
2. If you'd prefer, replace this Territory type table with a Custom table, and fill in the data as you would. Then, you
would edit the downstream dependent objects to use the replacement Custom table. You would still need to
delete the terrTerritory table before you can proceed with the upgrade
Note:
This error message is misleading. As part of the v8 upgrade, web form territory tables would need to be removed
as well, and this would require the model to come in to our Development team
Error Message Example
The table(s) terrTerritoryTable has data. Please remove all territory tables and calculations before
proceeding. (Note: Web Form Territory tables can remain).
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](String table, ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
8
ERROR AT UPDATE 842
What does this mean:
There are circular references aka dependency cycles in the noted Presenter report
To fix:
Break up the circular references by removing offending items
Example Error Message:
Dependency cycles have been detected in web report 'Presenter 1':
Pa Period -> Picklist 'pl Period' -> src Active Period Picklist -> Pa Payee -> Picklist 'pl Payee' -> src Payee Picklist -> Pa
Period
Agg Period Picklist -> src Period Picklist -> Pa Payee -> Picklist 'pl Payee' -> src Payee Picklist -> Pa Period -> Picklist
'pl Period' -> src Active Period Picklist -> Pa Payee
Agg Payee Picklist -> src Payee Picklist -> Pa Period -> Picklist 'pl Period' -> src Active Period Picklist -> Pa Payee ->
Picklist 'pl Payee' -> src Payee Picklist
Agg YTD Payout -> cc Payout Summary Prior Paid -> src Payout Summary -> Pa Payee -> Picklist 'pl Payee' -> src
Payee Picklist -> Pa Period -> Picklist 'pl Period' -> src Active Period Picklist -> Pa Payee
Agg YTD Payout -> cc Payout Summary Prior Paid -> src Payout Summary -> Pa Period -> Picklist 'pl Period' -> src
Active Period Picklist -> Pa Payee -> Picklist 'pl Payee' -> src Payee Picklist -> Pa Period
Dependency cycles have been detected in web report 'Presenter 2':
Pa Period -> Picklist 'pl Period' -> Agg Period Picklist -> src Period Picklist -> Pa Payee -> Picklist 'pl Payee' -> src
Payee Picklist -> Pa Period
Agg Payee Picklist -> src Payee Picklist -> Pa Period -> Picklist 'pl Period' -> Agg Period Picklist -> src Period Picklist -
> Pa Payee -> Picklist 'pl Payee' -> src Payee Picklist
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
9
ERROR AT UPDATE 866
What does this mean?
There are tables of type Web Form Territory in the model. These need to be removed
Resolution:
A copy of the database model needs to be submitted to our Development for their assistance. The standard
turnaround time would be approximately 10 business days.
Example Error Message
Web form territory table(s) found. Please contact Varicent for assistance with upgrading your model.
Error Type:
==============
[Link].Update866+HasWFTException
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
10
ERROR AT UPDATE 873
What does this mean?
There are Stored Values referencing the Audit table. This is no longer permitted in ICM.
Resolution
1. Edit Stored Values so that these do not reference the Audit table
2. Edit dependent Data Grids and items that previously used the Stored Values
3. Save changes
Example Error Message
The web report 'Admin Status Report' has a Stored Value 'ExampleStoredValues' that uses the Audit Table.
The web report 'Plan Performance Tracking' has a Stored Value 'ExampleStoredValue' that uses the Audit Table.
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
11
ERROR AT UPDATE 878
What does this mean?
There are invalid formulas present, either in the Presenter Reports or within the validation rules for Input Forms.
Resolution
Correct the invalid formula as referenced by the error message
Example Error Message
The following formulas are now invalid, please check that they use AND and NOT for comparing true/false values.
Presenter Report (Plan Statement) ccYTDTotal : Round(([Link]*100),0)
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
12
ERROR AT UPDATE 915
What does this mean?
Model Upgrader has detected active workflows in Workflow Manager
Resolution
Stop all Workflows in Workflow Manager, and then resume the Model Upgrader operation
Example Error Message
Please stop all running workflows before upgrading model.
Error Type:
==============
[Link]
Stack Trace:
==============
at [Link](ISqlSink cmds)
…
© Copyright 2014 IBM Cognos ICM. All Rights Reserved.
13
