BI Data Analytics

Below issues were identified for MotioCI 3.0 upgrade   Content Store corruption --Engage MotioCI Regression Test cases going in Pending State - recycle MotioCI process Not able to sign in URL - IE Cache clearance

Steps for GC logs are as follows: 1) Navigate to /bin folder and locate a file named bootstrap_OSversion.xml file. 2) Make a backup copy of this file. 3) Edit the bootstrap_OSversion.xml file to put the following entry highlighted in bold. This settinng means that Cognos will create upto 10 files with 10MB size. ........ -Xms${dispatcherMaxMemory}m -Xverbosegclog:${install_path}/logs/gc.log,10,10000 -Xgcpolicy:gencon ........ 4) Implement the above setting in all components of the environment(CM, dispatcher) 5) Restart Cognos" Usage: Memory utilization by Cognos to identify patterns and detect rouge reports. Impact: Performance Overhead

Problem:   When Publisher task fails in between for large table due to any issue, it corrupts QVD file. When we try to rerun task after issue resolution, data is lost since QVD was actually incremental load and need to be restored completely.   Solution Best Practices: Set up QVD backups and restoration as Enteprise wide solution Identify QVDs having different types of load Document procedure for support and maintenance Steps: Restore QVD Restart failed task

Error: DPR-ERR-2002 Unable to execute the request because there were no connections to the process available within the configured time limit.   Troubleshooting:   Identify which server error is coming from Identify how frequent it is coming and which service throwing it. Identify type of reports (DQM Vs CQM)   Cause and Solution:   DQM report waiting  for a connection with report service longer than the specified timeout. The successful request flow is as follows   Run the interactive DQM report -> Get a connection with report service -> DQM report runs on Query service -> Query service gives the output to report service for rendering -> user received the output   In this case, the errors are generated at the second step i.e. getting a connection with the report service. This shouldn't be limited only to Query service i.e. your environment seems to be busy interactively which has little to do with the Query service memory. There are two possib

In my view, below are the steps involved in any type of BI project: Planning Prioritization Performing Tasks Iterate based on learning Better we are able to perform a step, subsequent steps become easier to achieve project deliverable and goals.  

  Problem: Even when using Auto generate test cases feature, it may take a while to generate test cases and it may fail for time out. Secondly, this would be frustrating if even after long time, no prompt parameters are imported.   Cause: It's possible its taking so long because there may be a large amount of prompts its going through.   Resolution: Deselect the "Attempt to Import Parameters from Reports, Views and Outputs" option Auto generate and do dry run to see which reports failed for prompts. Update those reports manually or cloning from other test cases to speed up process.      

MotioCI can be helpful to do impact analysis for any Backend DB changes. Steps: 1. Create queries for packages for each query subject. Please remember to put filters to limit data and have good performance. 2. Create test cases for each of them. 3. Run Test Scripts via MotioCI 4. Schedule them to run with comfortable frequency and failure notification. Once a test case fails, you can verify reason for failure (  table lock vs, DB changes) and get them corrected.

To keep up with upcoming Cognos fixes below links are useful: To check overall schedule: https://www-01.ibm.com/software/analytics/support/fixes/pbi_schedule.html Fix Pack lists ( below is latest Cognos BI 10.2.2 FP3): http://www-01.ibm.com/support/docview.wss?uid=swg27042898 Based on current versions, we need to evaluate fix list, open APAR, software version compatibility Environment and plan it. 

  Problem:   Content is spread over all folders and there is chance to keep getting new reports in Environment while upgrade testing is going on. Creating test cases and dividing in multiple scripts may be challenges and have more manual efforts as testing progress even with MotioCI.   Project Test execution approach steps Identify reports heavily used using Audit Reports. Identify reports not used in x months and exclude them from list for testing Move identified reports, queries, jobs, events, portal pages to a base project folders ( no need for application packages) Create test cases for data validation and scripts for each BIO execution Run a dry test and identify issues – prompt manual, report long runs If some reports taking longer time, they need to be parked in subfolder as long running reports and exclude from Reports test cases Identify assertions to be used for testing - typical is execution time stability and output comparison Repeat process to

Is there any change in Query Engine from current version to "To Be" version?  Any new components/services added and what fine tuning would be required for them or can we disable them? What's license cost for separating out roles as needed? How data lineage can be discovered in new solution? Is all Fix Packs/Interim fix included in the "To Be" version Is OS, DB, DB drivers, application server compatible with latest version? Are we focused on first more stability of existing report set or new features? Do we have data available for testing reports in Test environment? Which Tool to be used for Regression Testing and comparison Testing? How you will manage multiple environments and URL changes for any application integrations? Along with this, review fix list and known issues list to be aware and verify if any of the features are potential to be used at your end. Preparation is key and questions/demos required. FAQs should be created based on di

In large BI deployment, it is always challenging to define scope for Upgrade project testing as  new applications may be rolled out while upgrade testing is in progress as 80/20 rule. To define scope, we can follow this approach:- 1. Audit reports to collect all reports run in last 1 year covering different frequencies ( yearly, quarterly etc) 2. Audit reports heavily used by users - define more test cases for these reports 3. Identify key applications for Business and reports to have thorough testing including formatting, data and performance testing. Need to engage Busines stakeholders to identify each area to get test scenarios as well as reports that would have more complex logic and formatting

As number of product increases and provide features almost same but doing things differently, other than cost one critical question comes is skill set. Most of the time you would need to train your employees to work on it as hiring specialist may be costly and short term affair.  One thing I would think, organization or company should start looking is which type of people they have more (Left Brain Vs Right Brain). As top executive, you would need to see if a tool fits in mind set of people who would actually work on it. If a tool is associative ( Example), analysis requires people to be Right Brain oriented whereas if tool is based on relational or require programming, people using it for analysis should be Left Brain and you would see immediately difference. Either people can be trained or hired based on which way company decides to go in terms of tool selection. 

While setting up new data source connection ( SQL Server DB for example), we get errors in connecting with Cognos Framework Manager" Login failed Unable to attach to multi database   Few things required to check to resolve such issue Cognos FM is working fine for other data sources from Local Machine Cognos Data source is working fine User is able to connect from DB Client to DB with id. Local ODBC connection name should match with DSN name set up in Cognos Data source Use right ODBC connection file based on which one is set up in Registry. Examples:   Win 32-bit in Win64:  C:\Windows\SysWOW64\odbcad32.exe Win 32-bit in Win32:  C:\Windows\System32\odbcad32.exe    Create shotcut on local desktop for easy access and set up.

1. Check software OS/DB drivers/server compatibility with version you are installing http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/prereqsForProduct?deliverableId=1267644462529 DB DB2 Client - Only UDB LUW can be connected DB2Connect - can connect Mainframe DB2 as well. Apply Licenses for drivers and test connectivity IIS/Web Server O/S Version App Server version (if Tomcat is not used) 2. Plan to freeze Cognos Version to be installed (FP) http://www-01.ibm.com/software/analytics/support/fixes/pbi_schedule.html 3.  Plan to freeze Code and scope - Have parallel Development environment and after freeze date, all development should be done on. 4. Review Fix list and create test plan based on hot sites and specific issues environment has faced http://www-01.ibm.com/support/docview.wss?uid=swg27042898  5. Create Inventory List  using Audit report to clean up unused reports or define scope with frequent or

Database Migration impact Tasks checklist: 1. Account used should retain access to schemas 2. Verify if there is performance impact due to move 3. Is there any Data copy job need to be decommissioned and set up in new Server/DB 4. Catalog on Cognos servers and Cognos admin console 5. Catalog on Local machine or Citrix Clinets for FM, Transformer 6. Test for report functionality due to DB type change, FM in DQM, CQM mode 7. Validate version compatibility with Cognos for DB and drivers with correct license