BI Data Analytics

Some of the features changes:- Now we can upload Extension/Views at our end in Cloud Environment. In CA 11.0.9, Downloading in Excel opens up new tab and doesn't close it. Now in new version, it closes automatically. Now Data Module can have Native SQL embedded. Now Dataset can be scheduled via Job making it easier to refresh in data layer approach for reporting. Job is available to all Users now with embedded as well as classic View. Now, When the upload was initiated from a specific folder, the files are saved to that folder.

Typically on-premise environment, we keep a shared drive of deployment folder to share across environment so that  we don't need to copy them over each dispatchers and it's readily available for import in target environment. In Current IBM Cognos Cloud on 11.0.9, now there is script to sync up between environments and  it copies the deployment archive. We need to create new import for each new import and wait for 10-15 minutes before it will appear in new environment.  This was not the case in C10.2.2 Cloud Environment.

Issue:   Going to Cognos Admin Console is taking very long time. Analysis: The reason is for cache parameter was set to default for OpenID. Changes Summary: Change this parameter to address slow login issue cacheSize=1048576 

After Upgrade to Cognos 11.0.9 where content was migrated using export method in Cloud by IBM, we lost all My Content even though namespace are kept same. Users were not got imported over in Okta Namespace. Work around is to add users in Okta instead of using Cognos - Okta Namespace. Have users put Adding Users using export is still not working for Bulk update and we can add anyone in a namespace without any validation. Finally Audit DB  showing Timzone in local timezone after the change done in backend.  This is continuous thing to check out with each upgrade.

Below IBM document explains behavior of copy/move or overwriting impact of objects:- https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.wig_cr.doc/c_gtstd_copy_move_items.html If you copy and overwrite an existing report, the copied report ID and links replace those of the existing report. In this case, you might need to update links, such as links to job schedules. If you move and overwrite an existing report, the existing report ID and links are maintained. In this case, references to the moved entry are broken. However, this doesn't work in all cases and we see drill through links broken in some cases. Best approach in such case is to use cognos deploy method where you update reports in separate folder in same environment and import it to destination location. You can create single export and import tasks to use for all such updates.

Below are the properties to set to keep column size and width with text wrapping: Column Merge issue  http://www-01.ibm.com/support/docview.wss?uid=swg21674298 Set the advanced server property RSVP.EXCEL.XLS2007_COLUMN_WIDTH_CONTROL to TRUE for both BatchReportService and ReportService services.        Row Merge issue http://www-01.ibm.com/support/docview.wss?uid=swg21440556 RSVP.EXCEL.XLS2007_ALLOW_WRAPPING_SINGLE_CELL also to be set to TRUE  for both BatchReportService and ReportService services.   Once done, you can set any column width to be fixed and see same result in Excel as well as HTML. Please note that above properties will not be honored if you have unchecked Grouping repeating cells Report property in Report Properties menu. 

If anyone is using IBM Cognos Analytics Version 11.0.0.0 to 11.0.5.0, there is security bulletin released by IBM to notify vulnerability where sensitive information can be revealed in its logs files:- http://www-01.ibm.com/support/docview.wss?uid=swg22000095 The recommended solution is to apply version 11.0.6.0 as soon as viable.

Many times it's necessary to create multiple connections within Data Sources; for example, DB migration, multiple changes to keep in different DBs but same schema for parallel project. However, in IBM Cloud we have one single environment for UAT and Development so as soon as we enable it, it's not transparent to users and it adds additional step to select Data source and test. To resolve this, we can create separate group for each UAT users and change permission to specific Data source connection to deny for Read/Execute/Traverse. With this, they won't be prompted for Data source connections while running a report.

Issue Symptoms: After installing Life Cycle Manager, when clicking on start window, we get error that path not specified. Also, clicking on URI and trying to create project gives HTTP Not found error  Solution Create  "projects" folder under  C:\apps\ibm\cognos\LifecycleManager\data Make sure have full access on  C:\apps\ibm\cognos\LifecycleManager Restart  IBM Cognos Lifecycle Manager Startup and you should see below for successful start Using CATALINA_BASE:   "..\tomcat" Using CATALINA_HOME:   "..\tomcat" Using CATALINA_TMPDIR: "..\temp" Using JRE_HOME:        "..\bin\jre\7.0" Using CLASSPATH:       "..\tomcat\bin\bootstrap.jar" How to start and stop LCM Windows -> Start menu - navigate to the Lifecycle Manager entry and select " IBM Cognos Lifecycle Manager Startup" option.   Default: http://localhost:4797/LifecycleManager Lifecycle Manager s...

IBM has provided version numbers at below link:- http://www-01.ibm.com/support/docview.wss?uid=swg21343355 By looking at FM - About menu, it is not apparent what's fix pack applied. It just shows 10.2.2 You can check cmpls.txt file on FM install path and open in text editor. locate below line:- C8BISRVR_UPDATE_version=C8BISRVR-AW32-ML-RTM-10.2.6107.28-0 As per above link: 10.2.6107.28 - 10.2.2 FP7 You can also check instlog files to see this version number in file name itself. just after update.

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. 

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...

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.

There are multiple factors which come in place when we look at performance tuning. Below are two broad categories to investigate:   Environment: Cognos, Database, OS, Network. Application - Report, FM, Database, Data model, Data   Depending on how old application/changes happened, you can target specific area to find out issues quicker.   Quick things to check Environment compatibility Client Drivers are higher version than DB version. Generally Client Drivers are backward compatible and have new features as well if DB is up to date O/S Patches, Application Server are compatible with Cognos Applications Queries running from DB client vs Cognos - may be Cognos is doing more local processing Enable IPF trace to see how queries are being sent and getting responses

Often there are different set of users to perform different activities using Cognos - Consumer of report but should be able to schedule report or use existing reports to build Cognos workspace or modify Cognos workspace. Based on set up of organization, one  user may have to play different roles and there is need to customize Role to suit to this security need. In Cognos 10, Customized Roles can be created and capabilities can be assigned to it. Various Groups or individuals can be added to it. As admin, it's always to have a test account to test the security set up while creating custom roles so that no additional access are provided and at the same time, to check that all functions are working correctly.

Most of the time Cognos system can be tuned in-house if time is spent in below Failure Analysis by using Audit database Reports performance analysis - schedule vs on demand How much data is read by Users queries Cognos Logs analysis to capture any model errors Scheduled Jobs analysis Packages based error trend Space/RAM utilization to identify peak times With these inputs, first see queries, usages are appropriate and any governance is required. What's being run at peak time and can we distribute schedules (run "all at once" vs in sequence).  This would be start point to configure Cognos advanced settings, Cognos Environment settings, JVM Tuning for memory, concurrent threads, OS Tuning, DB Tuning and need for any regular Maintenance. These are quite involved steps but with these checked, we were able to reduce errors, failures by 100 % and pave way towards working on real issues and stabilize BI Platform.