You are on page 1of 15

Hello everybody, I've got a similar problem like francois's one.

I made a new Metric Extract from a Molap source. In the new Metric Extract wizard, I'm able to set scorecard tree, time mapping, mew metric type and measure field (calculated in transformer) like a metric. I'm also able to execute the new Metric Extract without errors and after that to run the tranfer data from staging areas into Metric store. The problem is that when I open Metric Studio I'm only able to see metadata and not values in metrics: it means it shows correctly all scorecard tree and metric features for each one, but each metric is without values. I can't understand why it can't load data in metrics....hope anybody can halp me!! Hi Valentin, Obviously, there is something which is not working as desired. When you execute your Metrics Extract and it is successful, go and check the table 'KPI_VALUE_STAGE' in the metric store. It should have all the data you want to see in the Metric Studio. Make sure you do the distinct count on the rows and make a note of it. Then run your command 'Transfer data from staging area into metric store'. After this is run completely. Go to the metric store and check the table 'KPI_VALUE_STAGE_REJECTS' and check the number of rows. This is going to give you an idea and starting point for you troublehsooting. Make sure the Metric Mapping for all the measures/KPIs are done properly. Actual, Target etc....I hope this helps you. I have the same problem, however I have managed to identify this as a mapping problem between metrics and metric types in Metric Designer. I am using v8.4. When the mapping is done by hand - all works OK and all values appear as it should. However, I have hundreds of metric types and hundreds of metrics, therefore am looking for a some sort of automation for this mapping. Does anybody of you gurus know a solution to this? I have connected the metric_type_ID for the DIM_Metric_Type in Framework to the metric_type_ID in the Fact table - no use. I am clueless and need a solution or a workaround of any kind to this ASAP. If Metric Designer doesn't support it - this is also an answer. I am truly stuck because of it e: mertic modelling using metric designer etting error "This program cannot display
Reply #2 on: 30 Dec 2008 09:39:46 pm

I never like the feature of being able to create a metric store via Metric Designer. Its a death trap, and support call generator more than anything. The best thing to do is to start with creating your metric store data source inside your Cognos 8 portal. This will force you to overcome any datasource configuration issues first.

Metrics Studio is very sensitive to the permission set and configuration properties of your database in SQL Server, or Schema for Oracle, and its black magic to get it to work with IBM's DB2. I'm not slamming the product. Its great, but the Metric Studio professional must pay extra attention to the explicit requirements for the database settings to have Metrics work properly with the database. Its a one time hardship, and once done, you can focus on learning about how to use the metric studio package to your hearts content. Take your time, and step through the manual.

metric studio vs report studio

Reply #1 on: 20 Jun 2007 09:36:49 am

Metrics Studio is for presenting Scorecards of Metrics, rather then reporting on data.

For example, if you have Revenue of 10K, what does that mean. Revenue of 10K only becomes a metric if it has a Period of Time, eg. 10K Revenue for May. But it is still not a metric until it has a target. If you were expecting 100K then 10K is terrible, if you were expecting 5K, then 10K is great. A metric also needs someone to be "accountable". Someone who is responsible for the metric (good or bad results).

Metrics Studio, collects the Metrics onto a Scorecard for analysis, comparision, charting, variance and visualization.

Report Studio is the "reporting tool" and is fully capable of formatting reports in any manner the business might choose.

Report Studio Reports can be linked to Metrics and Scorecards within the Metrics Studio product.

Hope this helps a bit.

IBM Cognos Metric Studio

IBM Cognos Metric Studio is the scorecarding and metrics tool in IBM Cognos Business Intelligence.Metric Studio is a performance tool for managing monitoring and analysing metrics, projects, and other performance measures within an organisation.

It is used to create a scorecard application and monitor the metrics within the applications.It helps you ensure that your organisations performance is consistent with its targets and goals.You can use Metric Studio to create a customized scorecarding environment to monitor and analyze business metrics throughout your organization. A metric is a key performance indicator (KPI) related to time.In other words you use Metric Studio to monitor KPIs between one period and the next.A scorecard shows graphically how a metric is performing.This is typically done by using red, orange and green status notations.

IBM Cognos Metric Studio Metric Studio helps you translate your organization's strategy into relevant, measurable goals that align each employee's actions with a strategic plan. A scorecard shows graphically whether the metric has improved, got worse or stayed the same. Metrics have both status (whether the metric is within scope) and trend (performance relative to last period).The rich scorecarding environment of Metric Studio shows you where your organization is successful and where it needs improvement. The application is quite unique in the market given it specific support for Strategy Execution programs like the Balanced Scorecard.

It tracks performance against predetermined targets(metrics) and indicates the current status of the business so that decision makers at every level of the organization can react and plan. What improved and got worse actually mean is defined when the metric is set up. In other words, a bigger number might mean performance has improved or slipped, depending on what it is measuring.Metrics means just setting a value to compare the status over a period of time or we can define metrics as A system or standard of measurement.

With Metric Studio, you can readily see how the organization is progressing against its strategy. You can set priorities for your own actions and understand how your decisions affect the performance of the company.You can navigate to Metric Studio content in the Contenttab and add the following Metric Studio content to a dashboard.

Watch lists Scorecards Strategies Metric types Individual metrics When you add an individual metric to the dashboard, historical data for the metric displays in the form of a bar chart.For any other IBM Cognos Metric Studio content that you add, the content displays as a list of metrics for the selected item.You can use the flexibility of Metric Studio to model metrics and their relationships based on any standard or proprietary scorecarding and management methodology that you already use.
1. 2. 3. 4. 5.

Cognos Metric Studio With Metric Studio, performance can be displayed either as a list report or a line chart. Often a chart makes it easier to spot trends.Actions can be set up to improve performance of a metric.The application delivers out of the box support for concepts like ownership, themes, objectives, strategy map, project-& initiative follow up, filing of attachments etc.
You might also like:
Basically you have two components: 1> Metrics Designer - It's like a Framework Manager tool. You create the Metric Package, define the Metrics and create the metric extract here. It does not only read the data from the source but also writes the data to another database called Metric Store. This process is called extract (like an ETL). 2> Once you have your metrics defined, then you open the metrics in Metrics Studio and do all the fancy stuff like creating diagrams, reports etc. Reporting implementations on Metric Studio?
Reply #1 on: 06 Sep 2010 04:53:49 am

Hi Paul,

I usually use the framework model found in cognosinstalllocation\temp\metricstudio\Yourmetricstudioapplication\fmprojecttemplate.cpf and then change that as necessary to create the reporting package I need.

Also you may want to look take a look at the scripts below to see if these with improve your performance

"IBM Cognos 8 provides a script called cmm_update_stats that updates your metric store database indexes, which improves performance. Typically, you use this script before or after loading data when the volume or distribution of data has changed significantly. For example, performance may improve if you run this script after increasing the number of scorecards from 100 to 1000.

Steps 1.Ensure that there is no activity in the metric store database.

2.Go to the following directory:


3.Go to the appropriate database directory.

4.Depending on the database type, run one of the following scripts from the command line:

For Microsoft SQL Server or DB2:

cmm_update_stats host_name metric_store_name Admin_user_name password

For Oracle:

cmm_update_stats metric_store_name Admin_user_name password"

Kind Regards


Populate metric values from same metric types in sub-scorecards

on: 10 Dec 2009 02:15:20 pm

Hi, I'm new to metric studio. I'm just wondering if it is possible to somehow compute metric values from metrics with the same metric type in the sub-scorecards.


scorecard Region1 contains 3 scorecards Area1, Area2, Area3.

Each of those 4 scorecards has a Revenue Metric, but since Region1 is the higher level scorecard, I want the Revenue in Region1 to be the sum of Area1, Area2, Area3Revenue metrics.

Is there an option in Metric studio that allows me to do this, instead of added the revenues up manually and inserting them?

I tried to do this with the derived metric option, but the values generated are based from the status of these revenue metrics, rather than the actual revenue values.

Thanks in advanc

Hi there. If you have 8.4 all you need to do is create a database schema in SQL Server (assuming of course that you have checked that the version of SQL Server is compatible with your Cognos 8 installation) Add a data source in IBM Cognos Connection The last stage of the data source wizard provides you an option to create a metric package. Check this option and then this will take you through to the Metric Store initialization wizard. Are you on 8.4? If you are not then you will need to follow the steps as per the technote for SQL Server using cmm_create_db. The most important aspect of this is that the database must use a collation of Latin Case Insensitive d1152inst_CreatetheMetricStore.html#inst_CreatetheMetricStore _cr_winux_id8931c8bi_SetUpDatabaseClientforMetricSt.html#c8bi_SetUpDatabaseClientforMetricStoreonAppTierCo mponentsComputer Hope this helps Cheers Peter B

Can't initialize the metric store

Reply #1 on: 20 Aug 2008 04:54:45 pm

Metrics uses oraoledb.dll which is not installed with the light oracle client. Then make sure you have the correct rights set for the schema user, as metrics is very picky on this (roles are NOT enough) GRANT CREATE ANY PROCEDURE TO "cmmuser" WITH ADMIN OPTION GRANT CREATE ANY SEQUENCE TO "cmmuser" WITH ADMIN OPTION GRANT CREATE ANY TABLE TO "cmmuser" WITH ADMIN OPTION GRANT CREATE ANY TRIGGER TO "cmmuser" WITH ADMIN OPTION GRANT CREATE ANY TYPE TO "cmmuser" WITH ADMIN OPTION GRANT CREATE ANY VIEW TO "cmmuser" WITH ADMIN OPTION GRANT CREATE SESSION TO "cmmuser" WITH ADMIN OPTION GRANT CREATE TABLE TO "cmmuser" GRANT CREATE TRIGGER TO "cmmuser" GRANT CREATE VIEW TO "cmmuser" GRANT "CONNECT" TO "cmmuser"; GRANT "RESOURCE" TO "cmmuser"; GRANT UNLIMITED TABLESPACE TO "cmmuser" GRANT EXECUTE ON "SYS"."DBMS_LOCK" TO "cmmuser" GRANT EXECUTE ON "SYS"."DBMS_UTILITY" TO "cmmuser" Then to load the samples make sure the sqlldr.exe is present on the Cogos 8 server. (for simplicity sake, always install the administrator option of the Oracle client on the C8 server)

Metric Store View Maintenance

on: 07 Feb 2012 07:00:08 pm

Hi Everyone,

I am having no luck with Cognos Support or with Google so thought I would try and pick your brains.

In the Metric Store there are a number of Views that can be used for reporting off of the Metric Store such as:

1. 2. 3. 4. 5.


These views are built from the underlying Metric Store tables and other views. All views are combined with the USER_SESSION table meaning that their row count grows exponentially as the number of Cognos sessions increases over time. For example in my Metric Store I have 200 scorecards however the MOD_SCORECARD view has 55,000 records as it is combined with USER_SESSION information. The view continues to grow over time even though I have loaded no new Scorecards into the Metric Store. The cause of the growth is user interaction with the Metric Store and is on a per session basis.

I am concerned that these views are going to grow so large that they become unusable or could even grind the database to a halt.

Is anyone familiar with a mechanism for controlling the size of these views? i.e. A setting for stopping user session logging in the Metric Store?

Or am I worrying over nothing and the Metric Store will manage the size of the views itself? i.e delete user session information after a period of time or number of records?

Any help would be much appreciated

Cheers, Steve

I've been through shed loads of issues around similar things in the last year due to a big project where I've been reporting against the metric store. I've got some workarounds which I working great for us. These views are obviously complex for a reason and work for what they are intended for, browsing in MS, but the reports are crap at performing if you have loads of scorecards, we have over 1000! So what I did was created a view against the key tables just looking at the figures I wanted to pluck off. Try this out for size


tpn.SHORT_PERIOD_NAME, coalesce(kph.TARGET_VALUE,0) tl.level_id psc.object_nm kpi.qualifier_id "QUALIFIER" (


coalesce(kph.ACTUAL_VALUE,0) "ACTUAL_VALUE",





where object_type_cd = 'KPICL' and text_language_cd='EN') KCL, ( select * from time_period_names


where language_cd='EN' and name_type_cd = 'default' and short_period_name not like '%TD' ) tpn select * from content_object_lv where object_type_cd = 'SC' and text_language_cd='EN') SC, select * from content_object_lv where object_type_cd = 'SC' and text_language_cd='EN') PSC where kph.TIME_PERIOD_SID = tp.TIME_PERIOD_SID and kph.KPI_SID = KPI.KPI_SID and tl.time_level_sid=tp.time_level_sid and and kcl.external_object_id=kpi.kpi_class_id ( , (

tpn.TIME_PERIOD_SID=kph.time_period_sid and kpi.home_scorecard_sid=sc.content_object_sid and sc.parent_object_sid=psc.content_object_sid );

Now running this view on its own isn;t amazingly quick but once you started putting filters around the view in

cognos it's pretty damn lightening!

Let me know if this helps, you can email me at and share ideas, there's a shortage of Metric Studio knowledge out there!!


Re: Metric Store View Maintenance

Reply #2 on: 14 Feb 2012 06:01:08 pm

Hi Nick,

Thanks for sharing your solution, it's good to hear that it is not just myself suffering from a poorly designed product. My solution to the problem is very similar to what you have mentioned.

I am using a DB2 Metric Store so I replaced each of the views with materialised query tables (MQTs). This allowed me to apply indexes to the keys and remove all of the redundant ticket and multi-lingual data. The increase in reporting performance was over 95% using this method however it feels like a bit of a hack for something that should be "out of the box" functionality.

I am curious to see just how big the views in the Metric Store will get as they are already in the millions of rows. In the end the growth of the views will be dependant on the number of Cognos Sessions against the Metric Store.

Totally agree with the lack of expertise in the Metric Studio/Store space!

Cheers, Steve

taging Area
Reply #1 on: 29 Jul 2011 04:53:04 am

There are a number of reasons for having to load data via the staging tables. If a weekly load task is made up of 20 Metric Designer extracts, it is a lot more efficient to run each one to load into the staging tables and then run one task to take the data from the staging tables into the metric store. In Cognos Connection, you can design a Job entry to run the Metric Designer extracts followed by the load from staging tables to the metric store all to run in series. Also, it can be very useful when troubleshooting dataload issues by being able to split the load into stages to determine at exactly which point the dataload is failing. If a dataload fails at the transfer into staging tables step, it would be a waste of time and resources to then run the load from staging into metric store as the data would either not exist in the staging tables or would not contain the expected values.
SOLVED: Incorrect Status for Metric
on: 20 Jun 2011 08:17:05 am

The problem I am facing is related to status colours not being what they should within Metric Studio.

If Actual = 10 and Target = 10, the status is green. If Actual is between 9.5 and 10.5 and Target = 10, the status is green. If Actual = 8.5-9.4 or 10.6-11.5 and Target = 10, the status is yellow. If Actual = 8.4 and less or 11.6 and higher and Target = 10, the status is red.

Problem: The results I get back:

If Actual is above 10 is green If Actual is between 9 - 10 is yellow If Actual is below 9 is red

Some how my status results dont match what is being communicated to me via the IBM site.

Could anyone help me?

I have solved this little issue of mine. It turned out that I had not been instructed anywhere to change the Metric Type properties from:

Status Indicator -> 'Above Target is Positive' to 'On Target is Positive'

This is the only setting that has been changed to solve my issue. All the other settings remain as default. Wish IBM could have been a little clearer on this!

Re: How to create the structure of metric store database

Reply #1 on: 13 Jul 2009 05:04:43 pm

The user need the following privileges to create metric store


First you must create the metric content store as a distinct one from the Cognos content store :

In the Application Tier Components location, in the c8_location/configuration/schemas/cmm/sqlserver directory, run the cmm_create_db.cmd script by typing the following command:

path_to_script cmm_create_db host_name database_name user_name password [user_to_create]

then have a look there : 4.0.doc/qrc_mm_inst_id634inst_CreatetheContentStore.html E-Mail notification

Reply #1 on: 11 Jan 2011 10:34:02 am

Hi, It has ability to send email when threshold changes. i think u have not created a New integration task in u r metric maintenance package. try this steps may be it will help you.. 1) Go to Your metric maintenance package depend on u r scorecard. 2)At top u will see between New job and New url , u will see New Data integration task 3) Click on that and select new metric maintenance. 4) select u r metric package. 5)It will ask for Name, Type: - Email Alert Notification ,click next 6)under metric data options - select: recalculated derived values. and under Additional Options : select emails from watch list.

7) select option: save only. click finish. : Batch scripts

Reply #3 on: 25 Sep 2007 04:33:37 pm

Cognos gave us the control to create custom trigger's that will execute any of the metric mainance task indivudially or in any order/ grouping we want. Here's how you can do it.

1.Log into Cognos Connection as an admin.

2.Create a new job in Cognos Connection to run the desired Metric Maintenance task(s).

3.Click on the Schedule icon (under the action column) next to the job link in Cognos Connection.

4.Under Frequency, click on By Trigger.

5.Specify a Start and End time (during this time , if you run the Trigger.bat file, it will be executed).

6.Define a name for the trigger.

After you have created the trigger you may run it however you please, i run mine thru DTS in sql server 2000, but the process is the same if you use a cmd prompt or anything else. here is the syntax to run your trigger (s) from the cmd prompt

c:\..Cognos directory..> Trigger.bat <Gateway URL> <username> <password> <Namespace ID> <comma separated trigger list>

Just to be clear the Metric Store and the Content Store are completely seperate.

A Metric Store is used to store your metric data based on the calendar parameters you have set when you initially created the Metrics Package.

Unlike the content store which is a repository the Cognos tool uses to run the Metric Store will actually hold data values.

Additionaly if you have multiple Metrics Packages built based off of different rules, different data or even a different time frame can have multiple metric stores but still only a single content store.

It's a bad analogy so please forgive me in advance

A Metric Store could be viewed similar to a Cognos Cube. If you have like Data you can meet several different reporting requirements in a single location. But if the Business Rules or Time base or data is too different you will be forced to build a second Metric Store and Metric Package the same way you would have to build a seperate cube.

So if your looking at building your first Metrics Package I highly recommend you spend a good bit of time in the Analysis and Design phase and set the Metrics Package up accordingly. Metrics Store Connection issue
Reply #2 on: 31 May 2007 06:03:45 pm

In Cognos 8, you do not define the connection to your Metric Store inside of Cognos Configuration. As ReportNet Addict states, if you have not created a Metric Store you will be prompted to create one.

The prompt will show when you click on the Metric Studio link in Cognos Connection. You will first be required to create a connection to an database that will function as your Metric Store. It sounds as though you have already created the physical database. Now all you will have to do is provide the connection parameters, which will give you the raw connection. Once you have established the connection, you will asked to define the Business Calendar. After defining the Business Calendar, click on the Finish button. This is the point in which the Metric Studio specific database tables are created. Basically, this is the equivalent of initializing the Metric Store in the previous versions of Metric Manager. It is a little different from the previous version, but once you get used to it, much easier to use.

Does this answer your question? e: Metrics Store connection to Cognos 8 Config. Issue..
Reply #1 on: 13 Feb 2007 10:40:44 am


Metrics Store databases are not configured using Cognos Configuration. Simply add a connection to the database from Cognos Connection (Tools/Directory), then either launch Metrics Studio (if this is your first metrics database) or use the New Metrics Package button on the toolbar.

Best regards, Re: creating dashboards

Reply #1 on: 05 Aug 2008 10:26:37 am

Are you looking to use Metric Studio content within Cognos Connections to create a Dashboard page, or are you within Metric Studio asking how to build filters, groups and organize your metrics for a dashboard appearence?

In Cognos Connections you can either build Report Studio Reports from Metrics data and uses these on a portal tab

to create a Dashboard or you could simply selected several metrics and add them to your watch list - then within your portal page on Connections you would add a Metric Studio Container to display these metrics giving it a dashboard look and feel.

If your within Metric Studio I recommend setting up the metrics to best meet the business rules adding what groups are deemed necessary and then using the Diagraming tool to customize a "dashboard" page bringing the metrics you want to focus on and organizing them in a way that allows the business to follow their natural work flow.

For example show Corporate Metrics and allow them to drill in on these metrics down to state, branch or some other natural progression that follows the business flow.

if you installed the Go Metrics sample data there is a good example of this. they created Scorecards that follow a natural business hierarchy then created a Diagram that leverages this while filtering out all the noise to give a nice Dashboard feel.

Just an advanced warning if you install the Go Metrics sample you will need it to be in a seperate metric store, don't put the demo data in your primary metric store and wonder why you are having a hard time making your real data fit later Packages..?
Reply #1 on: 06 Dec 2007 02:49:32 pm


Yes it's normal to have a new set of tables/procedures/functions etc for each metrics package. Typically you would store each in a separate database/schema.

After you create a package, you can either use Metric Studio to create your metric types/metrics etc, and/or you can use Metrics Designer, and/or you can populate text files with the relevant data and import, and/or you could write the relevant entries direct to the staging tables using an ETL tool and then transfer to the live tables.