Archive for February, 2009

Cognos Planning 8.4

February 4, 2009


I had found a chance to install and use Cognos Planning 8.4 sometime ago. Cognos Analyst is nearly the same as always, but there are lots of enhancements in the Cognos Contributor side.


I will try to write about these enhancements later on, but today I am only writing about what I liked most in the new version: new Contributor web-client.


It is finally renewed, now it at least looks like a real OLAP tool! (Figure 1)


Appearance is similar to Analysis Studio –which is very pretty. And now users are able to change dimensions in rows, columns and pages. Moreover, users are also able to use nested dimensions.





Figure 1



As an end-user, you are not restricted to the navigation that is defined by the administrator anymore.    








Migration of Analyst Libraries

February 2, 2009


Analyst migration is generally a straightforward process, at least it should be! 

In the migration process apart from migrating application files (Libraries for Analyst) it is crucial to review:

  • Links & files between Cognos Planning System and its environment. (TXT files or  Databases)
  • Links & files inside the Cognos Planning System. (between Analyst and Contributor)

 So if we summarize all the points we need to check:     


  • ODBC: It is always easy to recreate ODBC connections in the new server.
  • File Maps: Cognos Best Practise for File Maps is to put the TXT files in a directory under related library (where the File Map to be created) and then use (LIB) or (LIBNO) functions to select the file.
  • DCE (DCube Export):  Best Practise for “DCubeExport” Macro Command is to put the file that will be filled with data after export in a directory under related library (the same library with the D-Cube to be exported) and then use (LIB) or (LIBNO) functions to select the file.
  • D-Lists: To update D-lists not from ODBC or File Maps but directly from TXT Files is the worst thing to do. Use ODBC or File Maps.
  • A>C or C>A Links:  Another problematic area; avoid using A>C Links. Otherwise in the migration you will need to update and reappoint each one of them.

In one of my latest client I simply did not complete the migration of Analyst Libraries since they were using hundreds of Files Maps and “DCubeExport” Macro Commands with TXT files that are selected with their Actual File Paths without using (LIB) or (LIBNO) functions (Figure 1) in Cognos Planning.

I advised them to use existing server and upgrade the version on the server.

Figure 1

Figure 1

 That is how important to use best practises in the initial development stage!