--- title: Impact Analysis in Cognos Analytics – Part II description: Some less traditional areas of impact analysis in Cognos Analytics, Object dependency, Data lineage, and Object failure history all relate to the overall health of a Cognos environment. image: https://www.envisn.com/hubfs/impact.jpg --- [![envisn](https://www.envisn.com/hs-fs/file-15282154-gif/images/logo.gif?width=120&name=logo.gif "envisn")](https://www.envisn.com) [![Request a Demo](https://hubspot-no-cache-na2-prod.s3.amazonaws.com/cta/default/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be.png)](https://hubspot-cta-redirect-na2-prod.s3.amazonaws.com/cta/redirect/70307/973f9256-ef61-4ab8-ab2d-a004a90a18be) [![cognos security as youve never seen it - learn more about netvisn](https://www.envisn.com/hs/cta/cta/default/70307/3166c389-8135-4d84-9988-99dc8d523426.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/3166c389-8135-4d84-9988-99dc8d523426) # Envisn's IBM Cognos Blog ## [Impact Analysis in Cognos Analytics – Part II](https://www.envisn.com/envisn-cognos-blog/impact-analysis-in-cognos-analytics-part-ii) Posted by [The Envisn Team](https://www.envisn.com/envisn-cognos-blog/author/the-envisn-team) - [Tweet](https://twitter.com/share) *![impact analysis cognos](https://www.envisn.com/hs-fs/hubfs/impact.jpg?width=222&name=impact.jpg)By Elwood Philbrick, [Envisn, Inc.](https://www.envisn.com/)* In this second part of this blog subject we are going to focus on some less traditional areas of [impact analysis](https://www.envisn.com/envisn-cognos-blog/impact-analysis-in-cognos-analytics) in Cognos Analytics but no less important. These are: - **Object dependency ** - **Data lineage ** - **Object failure history ** These three categories all have one thing in common and that is they all relate to the overall health of a Cognos environment. It is typical that a mature Cognos environment will at any given time have between 15 – 20 percent of its objects non-functional. We know this from data we’ve captured working with customers that have recently installed our NetVisn product in their environments. Reasons for this typically relate to broken data lineage or missing objects. Analyzing object failure run history also yields valuable information on causes of failure that can be easily corrected. ## **Object Dependency ** This relates to objects that rely on other objects in order to execute properly. An example could be a distribution list that’s needed in order to get a report to those scheduled to receive it. Another example is a base report that’s required for a view report to execute properly. In *Figure 1* we have selected an object dependency analysis that we will perform on reporting objects using the package BI Reporting. This analysis lets us select the types of dependent objects we want to look for on the reporting objects using that package. In this example we’ve selected all of them. In the right pane of *Figure 1* we can select the level of detail we want with this analysis as well as any additional data to be included in the analysis. ![object dependency cognos](https://www.envisn.com/hs-fs/hubfs/impact-fig1.jpg?width=700&name=impact-fig1.jpg) *Figure 2* shows the results of the object dependency analysis. There are a total of 19 issues identified and as we can see under the Errors column, some objects having more than one issue affecting its status. Obviously, none of these objects will become functional again until these issues are successfully resolved. ![object dependency analysis cognos](https://www.envisn.com/hs-fs/hubfs/impact-fig2.jpg?width=700&name=impact-fig2.jpg) It’s possible to do this type of analysis against the entire Content Store at once. Doing this broad analysis first should often be the first step if only to do some sizing on how big an issue object dependency is in total. Then you can work your way through resolving these issues folder by folder. ## **Data Lineage ** Breaks in the data lineage can occur for a number of reasons. Model items may have changed without understanding what the impact would be of making one or more model item changes in a planful way. There are also other reasons for broken lineage but the end result remains the same. If a single data item on a report has a lineage break the report will not execute successfully. In *Figure 3* we will be doing an analysis to identify objects with broken data lineage. In this example we will be looking to see how many objects have broken lineage across the entire Content Store. ![cognos analysis with broken data lineage](https://www.envisn.com/hs-fs/hubfs/impact-fig3.jpg?width=700&name=impact-fig3.jpg) The results of our analysis show a total 173 objects have lineage breaks in the Content Store. ![cognos content store breaks in lineage](https://www.envisn.com/hs-fs/hubfs/impact-fig4.jpg?width=600&name=impact-fig4.jpg) Filtering on the package labeled *BI Reporting* we see that there only one object with broken lineage using this package shown in *Figure 5* . Note that the detail shows the specific item in the lineage that is no longer valid: *PhoneNo*. ![cognos object with broken lineage](https://www.envisn.com/hs-fs/hubfs/impact-fig5.jpg?width=650&name=impact-fig5.jpg) If we go to the detail documentation of that report we see the data lineage for all of the items used in the report. The item *PhoneNo* is highlighted in red indicating broken lineage. The green triangle shown beside the item enables the user to identify any other objects across the Content Store using this same item and to fix them all at the same time by doing a mass update. ![impact-fig6](https://www.envisn.com/hs-fs/hubfs/impact-fig6.jpg?width=768&name=impact-fig6.jpg) ## **Object Failure History ** Being able to look across the entire Content Store and identify object failure history is another means of insuring that all objects available to the user base are functional. Objects that have a high or consistent failure rate need to be addressed. We can run an analysis to see how many objects in the Content Store have failed. ![cognos content store analysis](https://www.envisn.com/hs-fs/hubfs/impact-fig7.jpg?width=700&name=impact-fig7.jpg) *Figure 8* shows the results of the analysis. There are a total of 125 reports that have a history of failure. The next step will be to look at some detail. ![content store analysis cognos](https://www.envisn.com/hs-fs/hubfs/impact-fig8.jpg?width=600&name=impact-fig8.jpg) *Figure 9* shows the details for a single report labeled *Gross Profit by Region*. The item Gross Profit does not exist and this is causing the report failure. ![cognos object causing report failure](https://www.envisn.com/hs-fs/hubfs/impact-fig9.jpg?width=700&name=impact-fig9.jpg) ## Why It Matters With the examples we’ve highlighted here it is difficult or impossible to easily identify these issues within Cognos Analytics itself. Troubleshooting these types of problems is often be a tedious process of trial and error unless you’re able to do these types of analyses quickly and in a manner that can trap all of the problem issues at once. And this is what your user base expects. All objects that are available should be fully functional at all times. Nothing less! For more on this subject check out a related blog series on the [***Cognos Metadata Universe***](https://www.envisn.com/envisn-cognos-blog/cognos-metadata-universe). With the right tools to use all of this metadata, impact analysis and the change that goes with it becomes a routine set of tasks to be done on whatever basis is needed. *©  [Envisn, Inc.](https://www.envisn.com/) – All rights reserved. Read more: [**Impact Analysis in Cognos Analytics - Part I**](https://www.envisn.com/envisn-cognos-blog/impact-analysis-in-cognos-analytics)*   [*![cognos data lineage ](https://www.envisn.com/hs-fs/hub/70307/file-901664760.png?width=65&name=file-901664760.png)*](https://www.envisn.com/cognos-data-management) **Learn more about [Cognos Data Lineage](https://www.envisn.com/cognos-data-management) in [NetVisn](https://www.envisn.com/cognos-data-management)**   Topics: [Cognos Analytics](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics), [cognos data lineage](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-lineage), [cognos impact analysis](https://www.envisn.com/envisn-cognos-blog/topic/cognos-impact-analysis) *Your feedback is very important to us - we’d love to hear your comments!* ### Subscribe to Envisn's IBM Cognos Blog ### Posts by Category - [Cognos Content Store (22)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-content-store) - [Cognos BI Best Practices (21)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-best-practices) - [Cognos Analytics (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-analytics) - [Cognos BI administration (19)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-bi-administration) - [Cognos Security (18)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-security) - [Cognos Tools (14)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-tools) - [Cognos Audit Data (11)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-data) - [Cognos Reporting (9)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-reporting) - [Cognos Auditing (8)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-auditing) - [Cognos 10 (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-10) - [Cognos Framework Manager (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-framework-manager) - [Cognos Metadata (7)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-metadata) - [BI Trends (6)](https://www.envisn.com/envisn-cognos-blog/topic/bi-trends) - [IBM Information on Demand (6)](https://www.envisn.com/envisn-cognos-blog/topic/ibm-information-on-demand) - [Cognos Audit Log (5)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-audit-log) - [cognos impact analysis (4)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-impact-analysis) - [Big Data (3)](https://www.envisn.com/envisn-cognos-blog/topic/big-data) - [Cognos Data Sources (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-sources) - [Cognos Documentation (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-documentation) - [Cognos Scheduling (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-scheduling) - [Product Information (3)](https://www.envisn.com/envisn-cognos-blog/topic/product-information) - [cognos data lineage (3)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-lineage) - [Archiving Cognos Content (2)](https://www.envisn.com/envisn-cognos-blog/topic/archiving-cognos-content) - [Cognos FM Model (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model) - [Cognos migration (2)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-migration) - [Announcements (1)](https://www.envisn.com/envisn-cognos-blog/topic/announcements) - [Cognos Change Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-change-management) - [Cognos Data Provenance (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-data-provenance) - [Cognos Hotfiles (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-hotfiles) - [Cognos Powerplay (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-powerplay) - [Cognos Triggers (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-triggers) - [Consolidating Cognos Environments (1)](https://www.envisn.com/envisn-cognos-blog/topic/consolidating-cognos-environments) - [Impromptu (1)](https://www.envisn.com/envisn-cognos-blog/topic/impromptu) - [Merging Content Stores (1)](https://www.envisn.com/envisn-cognos-blog/topic/merging-content-stores) - [Remote Cognos Management (1)](https://www.envisn.com/envisn-cognos-blog/topic/remote-cognos-management) - [cognos deployments (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-deployments) - [cognos fm model documentation (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-fm-model-documentation) - [cognos workspace (1)](https://www.envisn.com/envisn-cognos-blog/topic/cognos-workspace) - [netvisn (1)](https://www.envisn.com/envisn-cognos-blog/topic/netvisn) [see all](https://www.envisn.com/envisn-cognos-blog/impact-analysis-in-cognos-analytics-part-ii#) ### Posts by Popularity [![free download expert guide to cognos audit data](https://www.envisn.com/hs/cta/cta/default/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644.png)](https://www.envisn.com/hs/cta/cta/redirect/70307/6933ba0f-4664-4d5d-9413-edf64d7b2644) ### [Cognos Tools from Envisn](https://www.envisn.com/envisn-products) [NetVisn](https://www.envisn.com/netvisn) [AutoVisn](https://www.envisn.com/autovisn-cogos-scheduler) [UniVisn](https://www.envisn.com/univisn-cognos-performance-management) [DocuVisn](https://www.envisn.com/docuvisn-cognos-documentation) ### [Cognos Resources](https://www.envisn.com/resources) [Envisn’s IBM Cognos Blog](https://www.envisn.com/envisn-cognos-blog) [Custom Query Library](https://www.envisn.com/custom-query-library) [Tutorial Videos](https://www.envisn.com/cognos-demo-videos) [Mastering Cognos Security](https://www.envisn.com/mastering-ibm-cognos-security) [Content Store Survival Guide](https://www.envisn.com/content-store-survival-guide) [Expert Guide to Cognos Audit Data](https://www.envisn.com/cognos-audit-data-expert-guide) ### [Contact Envisn](https://www.envisn.com/contact) [Request a Demo](https://www.envisn.com/request-a-demo) [Support](https://www.envisn.com/support) 512-991-3999 [info@envisn.com](mailto:info@envisn.com) ### Latest Cognos Posts | [![youtube](https://www.envisn.com/hs-fs/hubfs/youtube.png?width=30&name=youtube.png)](https://www.youtube.com/user/envisn) | [![linkedin](https://www.envisn.com/hs-fs/hubfs/linkedin.png?width=30&name=linkedin.png)](https://www.linkedin.com/company/envisn-inc./) | [![twitter](https://www.envisn.com/hs-fs/hubfs/twitter.png?width=30&name=twitter.png)](https://twitter.com/Envisn) | [![facebook](https://www.envisn.com/hs-fs/hubfs/facebook.png?width=30&name=facebook.png)](https://www.facebook.com/envisn/) | | --- | --- | --- | --- | [![Real Time Analytics](https://static.getclicky.com/media/links/badge.gif)](http://clicky.com/101126274) ![Clicky](https://in.getclicky.com/101126274ns.gif) 3000 Polar Lane, Suite 901, Cedar Park, TX 78613 USA *Serving North America, Europe, and the UK with plans to expand to other areas in the near future. **[Privacy, Copyright & Liability](https://www.envisn.com/privacy-copyright-liability)*