SDK - IBM Cognos Analytics - Content Store Version and CS Schema

Answer

IBM Cognos Content Store Build number

These values are Build numbers , and will be changed over the course of the IBM Cognos Product Developement and Maintenance.

Content Store version is tied to the point Release of the Software, and is formatted as Major.Minor.Release+Fixpack.Sequence number.

Example IBM Cognos 10.2.2 with FixPack 7 installed : 10.2.6107.5 is the CS Build number.

The Content Store Build version , will be always be changed with a new FixPack number for the Content Manager component.

Several Options on how to find the Content Store Build number :

- cogserver.log contains in the startup section of CM the CS Build number including the Schema version.

- with a URL against a running IBM Cognos Server :

http://Server.Domain:Port/p2pd/servlet

- find the line in the component list cmplst.txt file of the CM install : CM_version=CM-LX64-ML-RTM-10.2.6107.5-0

Example for Cognos Analytics CA1105 : CM_version=11.0.5.33

IBM Cognos Content Store Schema number

The CS Schema version is the version of the Database layout and does not change as frequently as the CS Build number. Each Major release get a new major number with a minor.

Example IBM Cognos 10.2.2 Initial Release has Schema 7.0026 , while the above IBM Cognos 10.2.2 with FixPack 7 has 7.0027

This indicates that there was a Schema change, somewhere between the Initial Release for 10.2.2 and the FixPack 7 for C1022.

This number is also used to ensure that the CS Database stays in Sync with the Product Design.

Changes to the CS Schema in the product, will be automatically Upgraded by Content Store startup scripts, and Tables and their entries can be changed with each new Version or FixPack installation as is shown.

Several options on how to find the Schema number :

- cogserver.log contains in the startup of CM the CS Build number including the Schema version.

- with SQL statement against CM : SELECT * FROM CMSYSPROPS

- the last line in <install>/configuration/schemas/content/<database>/dbInitScript_<database>.sql

Note : To roll back a CS Version and its Schema after the upgrade is done , although not impossible is a difficult thing for any Database Production System.

Basically a New Content Store has to be created for and in the version to roll back to.

The CS Export Deployments from a newer version may also not match what the old Schema contained, and Importing deployments going back in this manner , may cause issue for the overall systems.