Skip navigation.
spilling the beans

news aggregator

@8__tm1 @aki_okr044 それ!!(笑)読み方すら分からないww

Twitter TM1 - Mon, 2012-02-20 08:10
@8__tm1 @aki_okr044 それ!!(笑)読み方すら分からないww

@8__tm1 何かと思ってぐぐったら…数えたんだ(笑)すごいね(笑)偶然だよねー( ̄▽ ̄)笑

Twitter TM1 - Mon, 2012-02-20 08:10
@8__tm1 何かと思ってぐぐったら…数えたんだ(笑)すごいね(笑)偶然だよねー( ̄▽ ̄)笑


Twitter TM1 - Mon, 2012-02-20 08:10

RT @YoungWan_7: ™1⃣0⃣3⃣

Twitter TM1 - Mon, 2012-02-20 08:10
RT @YoungWan_7: ™1⃣0⃣3⃣


Twitter TM1 - Mon, 2012-02-20 08:10

Predictive Analytics for Business, Marketing and Web - 2012

comp.databases.olap newsgroup - Sun, 2012-02-19 08:10
Hi Everyone:

Mark your calendars for Predictive Analytics for Business, Marketing
and Web in 2012. Three events in NYC, São Paulo, Brazil and San
Francisco. More info below.

Predictive Analytics for Business, Marketing and Web - 2012


March 22-23, 2012 in New York City

IBM Cognos Fix Packs and Hot Fixes

Fabica blog - Sat, 2011-12-17 04:34

What is Fix Pack?
A Fix Pack is a product update that contains a cumulative collection of code fixes that have been made since the last release of the product. These code fixes may be a result of several interim fixes as well as other code fixes identified to be important to our customers.

Fix packs within a release are always cumulative; for example, 8.4.0 FP2 includes all the fixes from 8.4.0 FP1. Fix Packs are language independent.

You can find the list of Fix Pack for different Cognos components from

What is Hot Fix?
A hotfix is a single, cumulative package that includes one or more files that are used to address a problem in software product. Typically, hotfixes are made to address a specific customer situation and may not be distributed outside the customer organization.

I will be focusing here more towards TM1 HF. The latest TM1 HF is 9.5.2 HF8 having a build number 9.5.20008.17515( for 32 bit ) and 9.5.20008.17510 ( for 64 bit). The latest TM1 FP is 9.5.2 FP1 released on Oct 3, 2011. You can find a list of Cognos TM1 9.5.2 Fix List from

Understanding the Build Number String
According to IBM, All TM1 build strings are formatted as A.B.CDDEE.xxxxx where

  • A is the first octet ( usually 1 digit)
  • B is the second octet (usually 1 digit)
  • CDDEE is the third octet(always 5 digit)
  • xxxxx is the fourth octet(usually 4 or 5 digits, but can anywhere between 1-5 digits)

9.4.10304.3790 = 9.4 Maintenance Release 1 Fix pack 3 Hot Fix 4 build 3790
9.5.10000.5424 = 9.5 Refresh Pack 1 build 5424
From the latest TM1 HF8 9.5.20008.17515 = 9.5 Maintenance Release 2 Hot Fix 8 build 17515

Recommended location for Build Number string
The recommended location to find the TM1 build number string is to look at the file properties.

  • For Perspective or Architect – look in the tm1api.dll
  • For TM1 Server – look in tm1s.exe or tm1sd.exe

[Note: if you have taken a Hot Fix, you may have different version strings for these two files]

Find the Build Number for CQ
When you have a TM1 issue related to Cognos query(CQ), you need to report the CQ Build Number.

  • Determine the correct TM1 build number as outlined above.
  • The CQ version is equal to the first two octets in the TM1 Build number string.
  • The CQ build number is equal to the third and fourth octet in the TM1 build number string.

Example, For TM1 build number 9.5.10000.5424, the CQ build number is 10000.5424.

Find the Build number for TM1 Package Connector (Tm1 9.5.1 and up)
When you have a TM1 issue related to TM1 package connector, you need to report the Package Connector build number.

  • Determine the correct TM1 build number as outlined in the section above.
  • Go to the directory <TM1 Package Connector Installation Location>\vers
  • Look for a file with the name
    • LL = Language Version (i.e. en, de, ln …)
    • A.B = version
    • CCCC.xxxx = Build number

Example, for file cogtr_tm1integration_en-win32-app-8.4.6013.183-inst.ver, the TM1 Package connector build number string is 8.4.6013.183.

Regarding Installation for TM1 HF
In order to install HF for TM1, IBM gives you set of files for each component – server, client, web, and Contributor – 32 and 64 bit. You need to replace those files for each component depending on if you have 32 bit or 64 bit. First you stop the TM1 services, then take the backup for the particular directory you replacing files to and then you copy the new files.

  • For TM1 server, you replace the files for \\tm1server\\d$\Program Files\Cognos\TM1\bin.
  • For TM1 web, the directory is \\webserver\c$\inetpub\wwwroot\TM1Web. Make sure you move the custom settings if you have any for web.config.
  • For TM1 Contributor for Apache Tomcat Server, you need to deploy the war file for new HF and before this you need to undeploy the previous war file for old HF version. The directory to follow is \\webserver\d$\Program files\Apache Software Foundation\Tomcat 6.0\webapps\pmpsvc. Make sure you export the tm1 contributor applications first, then stop the Apache Tomcat service, and then take backup of the directory.
  • Then undeploy the war file. After undeploying, make sure the files and folders are deleted. You can get the exact location for files and folders to check from Also run the TI process }tp_admin_delete_all from Architect in order to fully delete all tm1 applications.
  • If you have IBM Cognos 8 security with TM1 contributor, you also have to delete the apps that exist in BI Portal in Public Folder->IBM Cognos TM1 Contributor Applications thru cognos connection. You can get the exact steps how to deploy the war file with Apache Tomcat from
  • After deploying the war file, either you can copy the pmpsvc_config file from the backup you take OR you can start from the beginning entering admin host, server name, gateway uri, and dispatcher uri.
  • Then in the end, you have to import the applications.

TM1 Rules Vs TI Processes

Fabica blog - Thu, 2011-11-03 19:44

One of the most important decision that TM1 Developers need to make during design phase is to decide whether to use Rules or TI processes to move data between cells or cubes.

Below are some of the important things to consider while making this decision:-

Frequency of data movement:-

If the changes in data need to be reflected in real time, Rules will need to be used. If real time data is not a requirement  then developers can use Turbo Integrator Processes.

Even if developers are using Feeders efficiently, calculating cells using rules will still add some overhead in terms of processing power. If too many cells need to be calculated, loading a cube can take too long. Turbo Integrator processes on the other hand will place calculated values in the target cells and there would be no additional overhead while the cubes are being loaded or views are being changed by the user.

Memory Usage:-
Rules and their corresponding feeders add to the memory usage on the server when the calculated cells are accessed directly or through other cells which might require values from calculated cells.

All these parameters should be considered all together and not in isolation while deciding between Rules and TI Processes.

Syndicate content