New Job! Cognos SDK Developer

http://c8jobs.blogspot.com/2008/10/cognos-sdk-developer.html

New Job! Cognos SDK Developer

http://c8jobs.blogspot.com/2008/10/cognos-sdk-developer.html

PDF on ITIL

http://www.itsmfi.org/files/itSMF_ITILV3_Intro_Overview.pdf

PDF on ITIL

http://www.itsmfi.org/files/itSMF_ITILV3_Intro_Overview.pdf

ITIL

http://itilblues.wordpress.com/2007/11/15/itil-v3-overview-excellent-summary-and-free/

ITIL

http://itilblues.wordpress.com/2007/11/15/itil-v3-overview-excellent-summary-and-free/

Relational filter is dropped for specific queries when WITH clause syntax is disabled

This issue affects specific queries against relational data sources authored in Report Studio, Query Studio, and Analysis Studio. End user could potentially see more data than originally anticipated.

 

Supported Product(s) Affected

• IBM Cognos 8 Business Intelligence Server 8.1
• IBM Cognos 8 Business Intelligence Server 8.2
• IBM Cognos 8 Business Intelligence Server 8.3
• IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship

 

Description

This is a specific case that is encountered when multiple nested queries (SELECT) and WHERE clauses are generated in a particular order. As a result of this issue, a WHERE clause is potentially eliminated causing the end user to see more data than originally anticipated. The issue is due to a defect in the query optimization engine that is eliminating a filter clause. The query engine optimizer prefers to do as much filtering as possible in the Native SQL, pushing the work to the data base server, rather than performing it locally to improve performance. This specific transformation defect occurs when the WITH clause syntax is turned off. This is a global setting available as a governor in the FM model and can be controlled per report in Report Studio.

 

Problem pre-conditions:

1. The SQL must have a derived (aka "nested") table query, and that derived table must still exist after exiting from a transform step known within UDA as XFormAll. Otherwise, no push operation would be possible when the problem code is executed.
   
   NB* Precondition 1 EXISTS if the projection list (i.e. the "SELECT" statement) from the reporting query contains any expressions. (COLUMN + ' ' is an expression)
   
   NB* Precondition 1 does NOT exist if the projection list contained no expressions. (COLUMN by itself is a simple database reference, and is not an expression). In this case, the entire query has already been flattened into the single native query in prior code, and no derived table structure exists at the relevant point in time.
   
   
2. The reporting query must have a filter condition of its own, and must fetch directly from the derived table, such that filters can be pushed from one to the other for useful gain. The use of WITH syntax eliminates the need to push filter conditions and thereby avoids the pushNode problem.
   
   
3. The derived table must then have two or more separate (i.e. from different sources) filter conditions of its own. This is not in any sense "typical" but neither is it extraordinary: in the current scenario it happens because the table definition has a WHERE clause AND a join where the join condition is appended based on join rules. (These two filter conditions have not yet been merged together internally). 
   

Structurally, the precondition looks just like this:

select ( B from
  ( select expressionA AS "B" from TBLX,
                    // pre-condition 1: this is a complex
                    // expression, not a simple column.
          (select C from TBLY
            where cond1) FA
    where cond2 ) DT
                    // pre-condition 3: DT had two separate
                    // filter conditions. (cond2 will get lost as
                    // "cond3 AND cond1" are generated). 
where cond3
                    // pre-condition 2: cond3 filters directly
                    // the result of

 

Problem:

The filter clause from the reporting query will be successfully pushed into the native (derived table) query, however if the derived table already had two or more un-merged filter clauses, then the second filter clause only (based on internal ordering) belonging to the derived table is dropped. Depending on the type of filter (WHERE clause) being dropped, the end user could potentially see more data than originally anticipated.

 

Suggested Action(s):

Install Product Download updates provided below to correct the issue. For IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship, contact Customer Support.

 

Workaround: Enabling the WITH clause syntax will also resolve the issue.

 

Failure to follow these important recommendations may result incorrect data provided to users. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Relational filter is dropped for specific queries when WITH clause syntax is disabled

This issue affects specific queries against relational data sources authored in Report Studio, Query Studio, and Analysis Studio. End user could potentially see more data than originally anticipated.

 

Supported Product(s) Affected

• IBM Cognos 8 Business Intelligence Server 8.1
• IBM Cognos 8 Business Intelligence Server 8.2
• IBM Cognos 8 Business Intelligence Server 8.3
• IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship

 

Description

This is a specific case that is encountered when multiple nested queries (SELECT) and WHERE clauses are generated in a particular order. As a result of this issue, a WHERE clause is potentially eliminated causing the end user to see more data than originally anticipated. The issue is due to a defect in the query optimization engine that is eliminating a filter clause. The query engine optimizer prefers to do as much filtering as possible in the Native SQL, pushing the work to the data base server, rather than performing it locally to improve performance. This specific transformation defect occurs when the WITH clause syntax is turned off. This is a global setting available as a governor in the FM model and can be controlled per report in Report Studio.

 

Problem pre-conditions:

1. The SQL must have a derived (aka "nested") table query, and that derived table must still exist after exiting from a transform step known within UDA as XFormAll. Otherwise, no push operation would be possible when the problem code is executed.
   
   NB* Precondition 1 EXISTS if the projection list (i.e. the "SELECT" statement) from the reporting query contains any expressions. (COLUMN + ' ' is an expression)
   
   NB* Precondition 1 does NOT exist if the projection list contained no expressions. (COLUMN by itself is a simple database reference, and is not an expression). In this case, the entire query has already been flattened into the single native query in prior code, and no derived table structure exists at the relevant point in time.
   
   
2. The reporting query must have a filter condition of its own, and must fetch directly from the derived table, such that filters can be pushed from one to the other for useful gain. The use of WITH syntax eliminates the need to push filter conditions and thereby avoids the pushNode problem.
   
   
3. The derived table must then have two or more separate (i.e. from different sources) filter conditions of its own. This is not in any sense "typical" but neither is it extraordinary: in the current scenario it happens because the table definition has a WHERE clause AND a join where the join condition is appended based on join rules. (These two filter conditions have not yet been merged together internally). 
   

Structurally, the precondition looks just like this:

select ( B from
  ( select expressionA AS "B" from TBLX,
                    // pre-condition 1: this is a complex
                    // expression, not a simple column.
          (select C from TBLY
            where cond1) FA
    where cond2 ) DT
                    // pre-condition 3: DT had two separate
                    // filter conditions. (cond2 will get lost as
                    // "cond3 AND cond1" are generated). 
where cond3
                    // pre-condition 2: cond3 filters directly
                    // the result of

 

Problem:

The filter clause from the reporting query will be successfully pushed into the native (derived table) query, however if the derived table already had two or more un-merged filter clauses, then the second filter clause only (based on internal ordering) belonging to the derived table is dropped. Depending on the type of filter (WHERE clause) being dropped, the end user could potentially see more data than originally anticipated.

 

Suggested Action(s):

Install Product Download updates provided below to correct the issue. For IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship, contact Customer Support.

 

Workaround: Enabling the WITH clause syntax will also resolve the issue.

 

Failure to follow these important recommendations may result incorrect data provided to users. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Content may be removed when republishing PowerCube Packages from Transformer 8.3

Reports, folders and all other content under a package may be removed when republishing a PowerCube package from Transformer.

 

Supported Product(s) Affected

• Cognos 8 Business Intelligence 8.3

 

Description

Transformer allows the ability to publish packages for PowerCubes using three separate methods:

• Start publish wizard
• Publish the PowerCube using current settings
• Create the publish specification: This allows publishing options to be used in the Transformer command line for batch jobs after cube builds

When a package is replaced, content under the package including reports and folders will be removed in Cognos Connection. This happens under the following conditions:

• A package with the same name already exists in Cognos Connection
• The modeler or administrator performing the publishing chooses to "replace the existing entry" during the package publish. This action can be done through the Transformer UI or through the command line options in a batch script.

When rebuilding and republishing PowerCubes it is not necessary to replace the package since it is simply the data source connection that needs to be updated to enable the refreshed cube. Cubes being rebuilt and refreshed will not be impacted by this behavior unless the Transformer user or batch script explicitly chooses to replace the package.

 

Symptoms of this issue may include:

• After a publish from Transformer using the "publish the PowerCube using current settings" option, content under a package in Cognos Connection is missing or inaccessible
• Users report that content under a package in Cognos Connection is suddenly missing or inaccessible
• During a publish from Transformer, you are provided the following warning: (TR0165) A package already exists with the same name: 'Package Name'
  • Do not choose to replace the existing entry. You should enter a new name for the package otherwise content under the original package will be lost.
• After a cube rebuild is completed as part of a batch script, content under the package is missing or inaccessible.

 

Suggested Workaround:

Once a package has been overwritten in this manner and content has been removed, there is no workaround to restore this content other than to restore the content store from a backup copy.

The following steps should be followed by any Transformer modeler or Cognos Administrator:

• When prompted in Transformer to replace the existing entry for a package name during publish:
  • Never choose to replace the existing entry. You should enter a new name for the package otherwise content under the original package will be lost.
• When scripting cube build and deployment scenarios in a batch file, do not alter the default value of the "package overwrite" flag in the command line specification.
  • Changing this flag to true would allow the package name to be replaced if it already exists in Cognos Connection – losing all content in the process.
  • Not altering this flag from the default will cause publishing to fail where the package name already exists but the content under the package will be safe.

 

Suggested Action(s)

Cognos recognizes this as a defect (583153.0) which can be addressed in one of two ways:

1. Download Transformer 8.3.81.25 or later install kit from Product Downloads , or
2. If you have a 8.3 version of Transformer lower than 8.3.821.0 installed already, you can apply the Hotsite (updater) download available below.

Backups of Cognos 8 content stores are always strongly recommended by Cognos to ensure customers business intelligence assets are protected.

Failure to follow these important recommendations may result in loss of reports, folders, shortcuts, scheduled jobs or other content stored under a package in Cognos Connection. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Content may be removed when republishing PowerCube Packages from Transformer 8.3

Reports, folders and all other content under a package may be removed when republishing a PowerCube package from Transformer.

 

Supported Product(s) Affected

• Cognos 8 Business Intelligence 8.3

 

Description

Transformer allows the ability to publish packages for PowerCubes using three separate methods:

• Start publish wizard
• Publish the PowerCube using current settings
• Create the publish specification: This allows publishing options to be used in the Transformer command line for batch jobs after cube builds

When a package is replaced, content under the package including reports and folders will be removed in Cognos Connection. This happens under the following conditions:

• A package with the same name already exists in Cognos Connection
• The modeler or administrator performing the publishing chooses to "replace the existing entry" during the package publish. This action can be done through the Transformer UI or through the command line options in a batch script.

When rebuilding and republishing PowerCubes it is not necessary to replace the package since it is simply the data source connection that needs to be updated to enable the refreshed cube. Cubes being rebuilt and refreshed will not be impacted by this behavior unless the Transformer user or batch script explicitly chooses to replace the package.

 

Symptoms of this issue may include:

• After a publish from Transformer using the "publish the PowerCube using current settings" option, content under a package in Cognos Connection is missing or inaccessible
• Users report that content under a package in Cognos Connection is suddenly missing or inaccessible
• During a publish from Transformer, you are provided the following warning: (TR0165) A package already exists with the same name: 'Package Name'
  • Do not choose to replace the existing entry. You should enter a new name for the package otherwise content under the original package will be lost.
• After a cube rebuild is completed as part of a batch script, content under the package is missing or inaccessible.

 

Suggested Workaround:

Once a package has been overwritten in this manner and content has been removed, there is no workaround to restore this content other than to restore the content store from a backup copy.

The following steps should be followed by any Transformer modeler or Cognos Administrator:

• When prompted in Transformer to replace the existing entry for a package name during publish:
  • Never choose to replace the existing entry. You should enter a new name for the package otherwise content under the original package will be lost.
• When scripting cube build and deployment scenarios in a batch file, do not alter the default value of the "package overwrite" flag in the command line specification.
  • Changing this flag to true would allow the package name to be replaced if it already exists in Cognos Connection – losing all content in the process.
  • Not altering this flag from the default will cause publishing to fail where the package name already exists but the content under the package will be safe.

 

Suggested Action(s)

Cognos recognizes this as a defect (583153.0) which can be addressed in one of two ways:

1. Download Transformer 8.3.81.25 or later install kit from Product Downloads , or
2. If you have a 8.3 version of Transformer lower than 8.3.821.0 installed already, you can apply the Hotsite (updater) download available below.

Backups of Cognos 8 content stores are always strongly recommended by Cognos to ensure customers business intelligence assets are protected.

Failure to follow these important recommendations may result in loss of reports, folders, shortcuts, scheduled jobs or other content stored under a package in Cognos Connection. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Relational filter is dropped for specific queries when WITH clause syntax is disabled

This issue affects specific queries against relational data sources authored in Report Studio, Query Studio, and Analysis Studio. End user could potentially see more data than originally anticipated.

 

Supported Product(s) Affected

• IBM Cognos 8 Business Intelligence Server 8.1
• IBM Cognos 8 Business Intelligence Server 8.2
• IBM Cognos 8 Business Intelligence Server 8.3
• IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship

 

Description

This is a specific case that is encountered when multiple nested queries (SELECT) and WHERE clauses are generated in a particular order. As a result of this issue, a WHERE clause is potentially eliminated causing the end user to see more data than originally anticipated. The issue is due to a defect in the query optimization engine that is eliminating a filter clause. The query engine optimizer prefers to do as much filtering as possible in the Native SQL, pushing the work to the data base server, rather than performing it locally to improve performance. This specific transformation defect occurs when the WITH clause syntax is turned off. This is a global setting available as a governor in the FM model and can be controlled per report in Report Studio.

 

Problem pre-conditions:

1. The SQL must have a derived (aka "nested") table query, and that derived table must still exist after exiting from a transform step known within UDA as XFormAll. Otherwise, no push operation would be possible when the problem code is executed.
   
   NB* Precondition 1 EXISTS if the projection list (i.e. the "SELECT" statement) from the reporting query contains any expressions. (COLUMN + ' ' is an expression)
   
   NB* Precondition 1 does NOT exist if the projection list contained no expressions. (COLUMN by itself is a simple database reference, and is not an expression). In this case, the entire query has already been flattened into the single native query in prior code, and no derived table structure exists at the relevant point in time.
   
   
2. The reporting query must have a filter condition of its own, and must fetch directly from the derived table, such that filters can be pushed from one to the other for useful gain. The use of WITH syntax eliminates the need to push filter conditions and thereby avoids the pushNode problem.
   
   
3. The derived table must then have two or more separate (i.e. from different sources) filter conditions of its own. This is not in any sense "typical" but neither is it extraordinary: in the current scenario it happens because the table definition has a WHERE clause AND a join where the join condition is appended based on join rules. (These two filter conditions have not yet been merged together internally). 
   

Structurally, the precondition looks just like this:

select ( B from
  ( select expressionA AS "B" from TBLX,
                    // pre-condition 1: this is a complex
                    // expression, not a simple column.
          (select C from TBLY
            where cond1) FA
    where cond2 ) DT
                    // pre-condition 3: DT had two separate
                    // filter conditions. (cond2 will get lost as
                    // "cond3 AND cond1" are generated). 
where cond3
                    // pre-condition 2: cond3 filters directly
                    // the result of

 

Problem:

The filter clause from the reporting query will be successfully pushed into the native (derived table) query, however if the derived table already had two or more un-merged filter clauses, then the second filter clause only (based on internal ordering) belonging to the derived table is dropped. Depending on the type of filter (WHERE clause) being dropped, the end user could potentially see more data than originally anticipated.

 

Suggested Action(s):

Install Product Download updates provided below to correct the issue. For IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship, contact Customer Support.

 

Workaround: Enabling the WITH clause syntax will also resolve the issue.

 

Failure to follow these important recommendations may result incorrect data provided to users. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Relational filter is dropped for specific queries when WITH clause syntax is disabled

This issue affects specific queries against relational data sources authored in Report Studio, Query Studio, and Analysis Studio. End user could potentially see more data than originally anticipated.

 

Supported Product(s) Affected

• IBM Cognos 8 Business Intelligence Server 8.1
• IBM Cognos 8 Business Intelligence Server 8.2
• IBM Cognos 8 Business Intelligence Server 8.3
• IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship

 

Description

This is a specific case that is encountered when multiple nested queries (SELECT) and WHERE clauses are generated in a particular order. As a result of this issue, a WHERE clause is potentially eliminated causing the end user to see more data than originally anticipated. The issue is due to a defect in the query optimization engine that is eliminating a filter clause. The query engine optimizer prefers to do as much filtering as possible in the Native SQL, pushing the work to the data base server, rather than performing it locally to improve performance. This specific transformation defect occurs when the WITH clause syntax is turned off. This is a global setting available as a governor in the FM model and can be controlled per report in Report Studio.

 

Problem pre-conditions:

1. The SQL must have a derived (aka "nested") table query, and that derived table must still exist after exiting from a transform step known within UDA as XFormAll. Otherwise, no push operation would be possible when the problem code is executed.
   
   NB* Precondition 1 EXISTS if the projection list (i.e. the "SELECT" statement) from the reporting query contains any expressions. (COLUMN + ' ' is an expression)
   
   NB* Precondition 1 does NOT exist if the projection list contained no expressions. (COLUMN by itself is a simple database reference, and is not an expression). In this case, the entire query has already been flattened into the single native query in prior code, and no derived table structure exists at the relevant point in time.
   
   
2. The reporting query must have a filter condition of its own, and must fetch directly from the derived table, such that filters can be pushed from one to the other for useful gain. The use of WITH syntax eliminates the need to push filter conditions and thereby avoids the pushNode problem.
   
   
3. The derived table must then have two or more separate (i.e. from different sources) filter conditions of its own. This is not in any sense "typical" but neither is it extraordinary: in the current scenario it happens because the table definition has a WHERE clause AND a join where the join condition is appended based on join rules. (These two filter conditions have not yet been merged together internally). 
   

Structurally, the precondition looks just like this:

select ( B from
  ( select expressionA AS "B" from TBLX,
                    // pre-condition 1: this is a complex
                    // expression, not a simple column.
          (select C from TBLY
            where cond1) FA
    where cond2 ) DT
                    // pre-condition 3: DT had two separate
                    // filter conditions. (cond2 will get lost as
                    // "cond3 AND cond1" are generated). 
where cond3
                    // pre-condition 2: cond3 filters directly
                    // the result of

 

Problem:

The filter clause from the reporting query will be successfully pushed into the native (derived table) query, however if the derived table already had two or more un-merged filter clauses, then the second filter clause only (based on internal ordering) belonging to the derived table is dropped. Depending on the type of filter (WHERE clause) being dropped, the end user could potentially see more data than originally anticipated.

 

Suggested Action(s):

Install Product Download updates provided below to correct the issue. For IBM Cognos 8 Business Intelligence Server 8.4 First Customer Ship, contact Customer Support.

 

Workaround: Enabling the WITH clause syntax will also resolve the issue.

 

Failure to follow these important recommendations may result incorrect data provided to users. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Daylight Savings Time Update

In August of 2005 the United States Congress passed the Energy Policy Act (EPA), which changes the date of both the start and end of daylight savings time (DST). When this law goes into effect in 2007, DST will start three weeks earlier (2:00 am on the second Sunday in March) and will end one week later (2:00 am on the first Sunday in November) than what had traditionally occurred. This DST change is being adopted in the United States, Canada, Mexico, Western Australia and many other countries who observe DST. This is the first change to DST in 20 years and some systems will require coding updates and patches.

 

Before applying any DST updates, customers who want be DST ready will need to be on one of the following Cognos product versions:

• Cognos ReportNet 1.1 MR4
• Cognos 8 Business Intelligence Server 8.1 MR2
• Cognos 8 Business Intelligence Server 8.2 RTM

Customers wishing to leverage the DST changes will be required to install the DST Hotsite and/or a Non-Cumulative Updater Kit, and update their JRE.

 

SUN JRE Recommended Versions

SUN JRE Version	Minimum Required Version
1.3	1.3.1_20
1.4	1.4.2_13

 

Cognos ReportNet 1.1 customers will be required to upgrade to Cognos ReportNet 1.1 MR4 and then install the Cognos ReportNet 1.1 MR4 DST Hotsite update on top of MR4. Cognos 8 MR2 and Cognos 8.2 Business Intelligence customers will be required to apply only the DST non-cumulative updater kit.

Updated (Sep 25/07)! Cognos 8.1 RTM and MR1 customers will be required to upgrade to Cognos 8.1 MR2 and then install the Cognos 8.1 MR2 non-cumulative updater kit on top of Cognos 8.1 MR2. Cognos 8.1 MR2 and Cognos 8.2 Business Intelligence customers will be required to apply only the DST non-cumulative updater kit.

Both the MR4 hotsite and Cognos 8 non-cumulative updaters contain only DST related fixes. Refer to the Cognos Product Table- DST Advisory for the list of compatible versions and fix format.

 

Cognos Product Table- DST Advisory

Cognos Release Version	DST Hotsite	DST Non-Cumulative Updater Kit
Cognos ReportNet 1.1 MR4	X
Cognos 8 Business Intelligence MR2		X
Cognos 8 Business Intelligence RTM		X

Note:
Customers who have applied Hotsite kits at or greater than the following do not need to apply the kits associated with the DST advisory:

• Cognos ReportNet 1.1 MR4: 1.1.601.101
• Cognos 8.1 MR2: 8.1.209.129
• Updated (Sep 25/07)! Cognos 8.2: 8.2.43.252

 

Suggested Action(s):

Cognos recommends customers install the DST Hotsite (Cognos ReportNet 1.1 MR4) or DST Non-Cumulative Updater Kit (Cognos 8). See Available Downloads at the end of this advisory after the FAQ.

Customers should also review the outstanding JDBC driver issue and the DST fixes detailed below.

 

Outstanding Issue:

Display Dates in Cognos Connection

Cognos has issued a series of hotsite fixes and non-cumulative updater kits to make the required changes necessary for the new DST rules but there may be some issues encountered prior to the transition period to DST in March 2008. During the period equal to the offset from GMT (5 hours for customers in EST for example) preceding 2 AM EST up until the transition to DST, timestamps used to display the created or modified times of an object in Cognos Connection may be incorrect. Environments using Microsoft SQL Server or Apache Derby will be the only environments affected by this behavior.

This issue is due to a third party issue with the JDBC driver that is used in Cognos ReportNet and Cognos 8.  At the time of publishing ADVC808_0207, Cognos is awaiting a fix from the third party vendor of the JDBC driver.

Details of the defect include:

• Vendor: JNetDirect
• Driver Name: JSQLConnect
• Bug Number: TSR 502
• Third Party Defect: 568271

NOTE: This does not affect time zones with positive offsets from GMT, GMT +2 for example.

 

Symptoms of this issue may include:

A report is modified at 10 PM EST on March 8th, 2008. The modified timestamp that will appear in Cognos Connection will show 11 PM March 8th, 2008. Any reports modified prior to 9 PM EST March 8th, 2008 will show the correct modified timestamp.

 

Suggested Workaround:

Cognos recommends customers be aware of this issue (timestamps of objects are off +/- 1 hour during the DST transition period). Customers need to consider the impact to the work planned for this period, and potentially adjust their report schedules to compensate or avoid scheduling reports during the transition period.

 

Suggested Action(s):

Cognos does not recommend customers take the fix directly from the vendor.  Cognos expects that after the vendor supplies us with the fix, additional code changes and testing will be required prior to release.

Composite Information Server 3.7.1.3 requires patch 3.7.1.6 to Ensure Compatibility with Cognos 8.2

Due to a change in Cognos 8.2 as a result of a corresponding change in Composite Information Server 4.0.1, incompatibilities may be found if/when using CIS 3.7.1.3 (which shipped with Cognos 8.1.2 MR2) with Cognos 8.2.

 

Product(s) Affected

• Composite Information Server 3.7.1.3
• Cognos Business Intelligence 8.2

Description

Composite Information Server 3.7.1.3 is not supported with Cognos 8.2. Composite Information Server 3.7.1.6 is considered compatible with Cognos 8.2.

Errors may be encountered when attempting to use Composite Information Server 3.7.1.3 with Cognos 8.2.

 

Suggested Action(s)

It is recommended that an upgrade to Composite Information Server 4.0.1 (which is available with Cognos 8.2) be applied or if upgrade is not feasible, that the corresponding CIS 3.7.1.6 patch be installed. No additional changes are required to the Cognos 8.2 installation.

Failure to follow these important recommendations may result in products failing to run. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Daylight Savings Time Update

In August of 2005 the United States Congress passed the Energy Policy Act (EPA), which changes the date of both the start and end of daylight savings time (DST). When this law goes into effect in 2007, DST will start three weeks earlier (2:00 am on the second Sunday in March) and will end one week later (2:00 am on the first Sunday in November) than what had traditionally occurred. This DST change is being adopted in the United States, Canada, Mexico, Western Australia and many other countries who observe DST. This is the first change to DST in 20 years and some systems will require coding updates and patches.

 

Before applying any DST updates, customers who want be DST ready will need to be on one of the following Cognos product versions:

• Cognos ReportNet 1.1 MR4
• Cognos 8 Business Intelligence Server 8.1 MR2
• Cognos 8 Business Intelligence Server 8.2 RTM

Customers wishing to leverage the DST changes will be required to install the DST Hotsite and/or a Non-Cumulative Updater Kit, and update their JRE.

 

SUN JRE Recommended Versions

SUN JRE Version	Minimum Required Version
1.3	1.3.1_20
1.4	1.4.2_13

 

Cognos ReportNet 1.1 customers will be required to upgrade to Cognos ReportNet 1.1 MR4 and then install the Cognos ReportNet 1.1 MR4 DST Hotsite update on top of MR4. Cognos 8 MR2 and Cognos 8.2 Business Intelligence customers will be required to apply only the DST non-cumulative updater kit.

Updated (Sep 25/07)! Cognos 8.1 RTM and MR1 customers will be required to upgrade to Cognos 8.1 MR2 and then install the Cognos 8.1 MR2 non-cumulative updater kit on top of Cognos 8.1 MR2. Cognos 8.1 MR2 and Cognos 8.2 Business Intelligence customers will be required to apply only the DST non-cumulative updater kit.

Both the MR4 hotsite and Cognos 8 non-cumulative updaters contain only DST related fixes. Refer to the Cognos Product Table- DST Advisory for the list of compatible versions and fix format.

 

Cognos Product Table- DST Advisory

Cognos Release Version	DST Hotsite	DST Non-Cumulative Updater Kit
Cognos ReportNet 1.1 MR4	X
Cognos 8 Business Intelligence MR2		X
Cognos 8 Business Intelligence RTM		X

Note:
Customers who have applied Hotsite kits at or greater than the following do not need to apply the kits associated with the DST advisory:

• Cognos ReportNet 1.1 MR4: 1.1.601.101
• Cognos 8.1 MR2: 8.1.209.129
• Updated (Sep 25/07)! Cognos 8.2: 8.2.43.252

 

Suggested Action(s):

Cognos recommends customers install the DST Hotsite (Cognos ReportNet 1.1 MR4) or DST Non-Cumulative Updater Kit (Cognos 8). See Available Downloads at the end of this advisory after the FAQ.

Customers should also review the outstanding JDBC driver issue and the DST fixes detailed below.

 

Outstanding Issue:

Display Dates in Cognos Connection

Cognos has issued a series of hotsite fixes and non-cumulative updater kits to make the required changes necessary for the new DST rules but there may be some issues encountered prior to the transition period to DST in March 2008. During the period equal to the offset from GMT (5 hours for customers in EST for example) preceding 2 AM EST up until the transition to DST, timestamps used to display the created or modified times of an object in Cognos Connection may be incorrect. Environments using Microsoft SQL Server or Apache Derby will be the only environments affected by this behavior.

This issue is due to a third party issue with the JDBC driver that is used in Cognos ReportNet and Cognos 8.  At the time of publishing ADVC808_0207, Cognos is awaiting a fix from the third party vendor of the JDBC driver.

Details of the defect include:

• Vendor: JNetDirect
• Driver Name: JSQLConnect
• Bug Number: TSR 502
• Third Party Defect: 568271

NOTE: This does not affect time zones with positive offsets from GMT, GMT +2 for example.

 

Symptoms of this issue may include:

A report is modified at 10 PM EST on March 8th, 2008. The modified timestamp that will appear in Cognos Connection will show 11 PM March 8th, 2008. Any reports modified prior to 9 PM EST March 8th, 2008 will show the correct modified timestamp.

 

Suggested Workaround:

Cognos recommends customers be aware of this issue (timestamps of objects are off +/- 1 hour during the DST transition period). Customers need to consider the impact to the work planned for this period, and potentially adjust their report schedules to compensate or avoid scheduling reports during the transition period.

 

Suggested Action(s):

Cognos does not recommend customers take the fix directly from the vendor.  Cognos expects that after the vendor supplies us with the fix, additional code changes and testing will be required prior to release.

Composite Information Server 3.7.1.3 requires patch 3.7.1.6 to Ensure Compatibility with Cognos 8.2

Due to a change in Cognos 8.2 as a result of a corresponding change in Composite Information Server 4.0.1, incompatibilities may be found if/when using CIS 3.7.1.3 (which shipped with Cognos 8.1.2 MR2) with Cognos 8.2.

 

Product(s) Affected

• Composite Information Server 3.7.1.3
• Cognos Business Intelligence 8.2

Description

Composite Information Server 3.7.1.3 is not supported with Cognos 8.2. Composite Information Server 3.7.1.6 is considered compatible with Cognos 8.2.

Errors may be encountered when attempting to use Composite Information Server 3.7.1.3 with Cognos 8.2.

 

Suggested Action(s)

It is recommended that an upgrade to Composite Information Server 4.0.1 (which is available with Cognos 8.2) be applied or if upgrade is not feasible, that the corresponding CIS 3.7.1.6 patch be installed. No additional changes are required to the Cognos 8.2 installation.

Failure to follow these important recommendations may result in products failing to run. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Detail Filter May Return Incorrect Results

Product(s) Affected

• Cognos 8 Business Intelligence Server 8.1.2 MR2

This issue affects specific queries against OLAP⁽¹⁾ and Dimensionally Modeled Relational⁽²⁾ (DMR) data sources authored in Report Studio only. It does not affect Analysis Studio or Query Studio reports.

 

Description

Detail filters on measures may be applied incorrectly to crosstabs or charts with multiple member sets on an edge resulting in incorrect data.

This problem only applies where the crosstab or chart has more than one member sets from different hierarchies on the same edge.

For example⁽³⁾ given this crosstab report with member sets of Year and Quarters on the row edge:

 

Applying the detail filter [Quantity sold] >= 10000 will correctly remove all cell values less than 10,000:

 

This is correct behavior. The filter causes the correct cell values for Months to be removed from the report.

Were we to use members set from different hierarchies, we will see incorrect behavior.

For example, consider this report where the edge items Year and Order method come from different hierarchies.

 

Applying the filter [Quantity sold] >= 10000 will incorrectly remove the Order method Special which has cell values greater than 10000:

 

Suggested Action

OLAP Data Sources

To minimize the potential of a data integrity problem, we strongly recommend that you apply hot site correction for Product Issue 538299. See Available Downloads below

Dimensionally Modeled Relational Data Sources

To minimize the potential of a data integrity problem, we strongly recommend that you apply hot site correction for Product Issue 540307. See Available Downloads below.

 

Suggested Workaround

None

Failure to follow these important recommendations may result in incorrect data returned. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Detail Filter May Return Incorrect Results

Product(s) Affected

• Cognos 8 Business Intelligence Server 8.1.2 MR2

This issue affects specific queries against OLAP⁽¹⁾ and Dimensionally Modeled Relational⁽²⁾ (DMR) data sources authored in Report Studio only. It does not affect Analysis Studio or Query Studio reports.

 

Description

Detail filters on measures may be applied incorrectly to crosstabs or charts with multiple member sets on an edge resulting in incorrect data.

This problem only applies where the crosstab or chart has more than one member sets from different hierarchies on the same edge.

For example⁽³⁾ given this crosstab report with member sets of Year and Quarters on the row edge:

 

Applying the detail filter [Quantity sold] >= 10000 will correctly remove all cell values less than 10,000:

 

This is correct behavior. The filter causes the correct cell values for Months to be removed from the report.

Were we to use members set from different hierarchies, we will see incorrect behavior.

For example, consider this report where the edge items Year and Order method come from different hierarchies.

 

Applying the filter [Quantity sold] >= 10000 will incorrectly remove the Order method Special which has cell values greater than 10000:

 

Suggested Action

OLAP Data Sources

To minimize the potential of a data integrity problem, we strongly recommend that you apply hot site correction for Product Issue 538299. See Available Downloads below

Dimensionally Modeled Relational Data Sources

To minimize the potential of a data integrity problem, we strongly recommend that you apply hot site correction for Product Issue 540307. See Available Downloads below.

 

Suggested Workaround

None

Failure to follow these important recommendations may result in incorrect data returned. Cognos will not be liable for any loss or damages arising from the failure to implement these recommended directions.

Project Management Templates

You can now use PayPal to buy project management templates for your next BI solution. Just visit the http://bicentre.blogspot.com blog and view the right hand side to request your copies today!

Project Management Templates

You can now use PayPal to buy project management templates for your next BI solution. Just visit the http://cognos8help.blogspot.com blog and view the right hand side to request your copies today!

Cognos 8 Migration documentation templates

We will be providing some templates that can be used as a starting point to help plan your Cognos migration from Cognos Series 7 to Cognos 8. The templates will help capture all of the critical business, architectural and planning elements that you must consider during your next Cognos migration project.

You will be able to customize the template to match your corporate solutions documentation centre. This will help you to save time and be able to focus more on your migration tasks. The templates will take you through the Analysis, Design, Build and Deploy stages of the project lifecycle.

Why would you waste more time generating documentation when you can focus your energies on getting the job done, also having the templates readily accessible can help your Project Management Office spend more time on generating the documents instead of duplicating unnecessary effort.

Cognos 8 Migration documentation templates

We will be providing some templates that can be used as a starting point to help plan your Cognos migration from Cognos Series 7 to Cognos 8. The templates will help capture all of the critical business, architectural and planning elements that you must consider during your next Cognos migration project.

You will be able to customize the template to match your corporate solutions documentation centre. This will help you to save time and be able to focus more on your migration tasks. The templates will take you through the Analysis, Design, Build and Deploy stages of the project lifecycle.

Why would you waste more time generating documentation when you can focus your energies on getting the job done, also having the templates readily accessible can help your Project Management Office spend more time on generating the documents instead of duplicating unnecessary effort.

http://nasdaqpicks.blogspot.com/

http://nasdaqpicks.blogspot.com/

http://nasdaqpicks.blogspot.com/

http://nasdaqpicks.blogspot.com/

Cognos in Mauritius

http://c8jobs.blogspot.com/2008/10/cognos-in-mauritius.html

Cognos in Mauritius

http://c8jobs.blogspot.com/2008/10/cognos-in-mauritius.html

Cognos Framework Manager and cardinality

Cardinality is combined with dimensions to control how queries are generated so that you can

• prevent double-counting

• automatically resolve loop joins

• enable cross-fact querying for reporting and analysis

You can create model dimensions and data source dimensions. Model dimensions are built on a foundation of query subjects that use determinants and relationships with cardinality. Data source dimensions contain their own SQL and use hierarchy and level information as well as relationships with cardinality to define query granularity.

Cardinality drives query behavior by allowing rules to be applied regarding the granularity of data that is returned by an individual object and the consequence of joins between objects. The cardinality specified in the relationship between query subjects or dimensions determines how and when Cognos 8 generates stitched queries. Stitched queries are needed for multiple-fact querying across conformed dimensions and across different levels of granularity.

Cognos Framework Manager and cardinality

Cardinality is combined with dimensions to control how queries are generated so that you can

• prevent double-counting

• automatically resolve loop joins

• enable cross-fact querying for reporting and analysis

You can create model dimensions and data source dimensions. Model dimensions are built on a foundation of query subjects that use determinants and relationships with cardinality. Data source dimensions contain their own SQL and use hierarchy and level information as well as relationships with cardinality to define query granularity.

Cardinality drives query behavior by allowing rules to be applied regarding the granularity of data that is returned by an individual object and the consequence of joins between objects. The cardinality specified in the relationship between query subjects or dimensions determines how and when Cognos 8 generates stitched queries. Stitched queries are needed for multiple-fact querying across conformed dimensions and across different levels of granularity.

Cognos 8 and UNIX tips

If Cognos 8 is installed on a Windows platform, you can install the modeling tools on the same computer. If Cognos 8 is installed on a UNIX or Linux platform, you must install the Windows-based modeling tools on a separate computer that runs under Windows.

When creating reports, you must select fonts that your Cognos server or users have installed.  Microsoft delivers a broad selection of fonts with different language packs, so this will likely not be an issue in Windows. However, UNIX servers rarely have fonts installed. You should be prepared to purchase and install the fonts you need on both the server and browser clients.

When generating a PDF, Cognos 8 embeds only the glyphs that are used in the report.  If you plan to use different fonts, you must license and install those fonts on each server computer in your authoring environment and production system. You must also ensure that the fonts used in the authoring environment match the fonts used on your Windows and UNIX server computers.

The console attached to the UNIX or Linux computer on which you are installing Cognos 8 may not support a Java-based graphical user interface. You must

❑

manually change default configuration settings by editing the cogstartup.xml file, located in the c8_location/configuration directory

❑

manually change language or currency support, or locale mapping by editing the coglocale.xml file, located in the c8_location

/configuration directory

❑

apply the configuration and the locale settings to your computer by running Cognos Configuration in silent mode

For all installations, some configuration tasks are required so that Cognos 8 works in your environment. If you distribute Cognos 8 components across several computers, the order in which you configure and start the computers is important.

Other configuration tasks are optional and depend on your reporting environment. You can change the default behavior of Cognos 8 by editing the cogstartup.xml file to change property values. You can also use sample files that enable Cognos 8 to use resources that already exist in your environment.

Cognos 8 and UNIX tips

If Cognos 8 is installed on a Windows platform, you can install the modeling tools on the same computer. If Cognos 8 is installed on a UNIX or Linux platform, you must install the Windows-based modeling tools on a separate computer that runs under Windows.

When creating reports, you must select fonts that your Cognos server or users have installed.  Microsoft delivers a broad selection of fonts with different language packs, so this will likely not be an issue in Windows. However, UNIX servers rarely have fonts installed. You should be prepared to purchase and install the fonts you need on both the server and browser clients.

When generating a PDF, Cognos 8 embeds only the glyphs that are used in the report.  If you plan to use different fonts, you must license and install those fonts on each server computer in your authoring environment and production system. You must also ensure that the fonts used in the authoring environment match the fonts used on your Windows and UNIX server computers.

The console attached to the UNIX or Linux computer on which you are installing Cognos 8 may not support a Java-based graphical user interface. You must

❑

manually change default configuration settings by editing the cogstartup.xml file, located in the c8_location/configuration directory

❑

manually change language or currency support, or locale mapping by editing the coglocale.xml file, located in the c8_location

/configuration directory

❑

apply the configuration and the locale settings to your computer by running Cognos Configuration in silent mode

For all installations, some configuration tasks are required so that Cognos 8 works in your environment. If you distribute Cognos 8 components across several computers, the order in which you configure and start the computers is important.

Other configuration tasks are optional and depend on your reporting environment. You can change the default behavior of Cognos 8 by editing the cogstartup.xml file to change property values. You can also use sample files that enable Cognos 8 to use resources that already exist in your environment.

stand alone versus embedded calculations

Use a stand-alone calculation when you want to reuse the expression. You can apply a stand-alone calculation to one or more dimensions or query subjects to provide calculated data to a report, or include it in a package to make it available to your users. By moving a stand-alone calculation or a shortcut to it into a folder, you can better organize your model objects.

Use an embedded calculation when you want to use a calculation with only one dimension or query subject. You can create an embedded calculation when modifying a relational data source query subject, model query subject, or dimension.

stand alone versus embedded calculations

Use a stand-alone calculation when you want to reuse the expression. You can apply a stand-alone calculation to one or more dimensions or query subjects to provide calculated data to a report, or include it in a package to make it available to your users. By moving a stand-alone calculation or a shortcut to it into a folder, you can better organize your model objects.

Use an embedded calculation when you want to use a calculation with only one dimension or query subject. You can create an embedded calculation when modifying a relational data source query subject, model query subject, or dimension.

XML Data Source

If you create an XML data source, you must use XML as the type of connection and specify the location of the XML document in the connection string.

You can specify the connection string for an XML data source as

• an HTTP URL that identifies the content store required to connect to the XML document.

An example is HTTP://xmltestserver.cognos.com/XML/country.xml.

Ensure that you create a Web alias for the directory that contains the XML file and that you enable directory browsing.

• a file path

A Windows file path example is \\

servername\XML\country.xml.

A UNIX file path example is /

servername/XML/country.xml.

• a local file

An example is C:\XML\country.xml;VALIDATE=ON.

To access a local file, use a file path that uses platform-specific syntax.

To test an XML connection string, you must type the following code at the end of the string:

;VALIDATE=ON

The text of this code is not case sensitive.

Parameterized XML Connection Strings

In an HTTP URL connection string for an XML data source, you can use parameters to send additional information. You can embed a prompt definition string in the parameter component. If the prompt definition is specified in the report, that value is used. Otherwise, the user is prompted to supply a value. Prompting is not supported for other types of connection strings.

An example of a URL component is addressing_scheme://

network_location/path;parameters?query#fragment_identifier

Encode the parameter component with the definition string in between two sets of question marks. A prompt cannot cross a component boundary.  An example of a parameterized XML string is

http://

My_Network_Location/My_Path/myxml.asp?countrysid=??CanadaPrompt??

Parameterized XML connection strings have these restrictions:

• When a URL component is a prompt, it cannot contain other data.

• Prompts embedded in XML connection strings do not work in Framework Manager. You cannot import data from a parameterized XML connection string.

• When you set up a parameterized XML connection string in Cognos Connection, the Test button does not work.

• Validation of the query specification in Report Studio does not work if you are connected to a parameterized XML connection string.

XML Data Source

If you create an XML data source, you must use XML as the type of connection and specify the location of the XML document in the connection string.

You can specify the connection string for an XML data source as

• an HTTP URL that identifies the content store required to connect to the XML document.

An example is HTTP://xmltestserver.cognos.com/XML/country.xml.

Ensure that you create a Web alias for the directory that contains the XML file and that you enable directory browsing.

• a file path

A Windows file path example is \\

servername\XML\country.xml.

A UNIX file path example is /

servername/XML/country.xml.

• a local file

An example is C:\XML\country.xml;VALIDATE=ON.

To access a local file, use a file path that uses platform-specific syntax.

To test an XML connection string, you must type the following code at the end of the string:

;VALIDATE=ON

The text of this code is not case sensitive.

Parameterized XML Connection Strings

In an HTTP URL connection string for an XML data source, you can use parameters to send additional information. You can embed a prompt definition string in the parameter component. If the prompt definition is specified in the report, that value is used. Otherwise, the user is prompted to supply a value. Prompting is not supported for other types of connection strings.

An example of a URL component is addressing_scheme://

network_location/path;parameters?query#fragment_identifier

Encode the parameter component with the definition string in between two sets of question marks. A prompt cannot cross a component boundary.  An example of a parameterized XML string is

http://

My_Network_Location/My_Path/myxml.asp?countrysid=??CanadaPrompt??

Parameterized XML connection strings have these restrictions:

• When a URL component is a prompt, it cannot contain other data.

• Prompts embedded in XML connection strings do not work in Framework Manager. You cannot import data from a parameterized XML connection string.

• When you set up a parameterized XML connection string in Cognos Connection, the Test button does not work.

• Validation of the query specification in Report Studio does not work if you are connected to a parameterized XML connection string.

User Acceptance and System Test Exit Criteria

This section contains a set of exit criteria that can be used to control the quality of the deliverables related to the test

Use this checklist to understand when the test is considered complete.

Criteria Met?

•

Ensure solution performs all functionality as defined.

•

Make sure the solution meets quality requirements.

•

Determine whether one can gain a basic understanding of the solution from the documentation.

Documentation Complete?

•

Actual results

•

Problems remaining to be resolved

• Resolved problems

•

Stakeholder consent

Standards Met?

•

Ensure the actual results show proof of testing.

•

Create cross-references to the test cycles and conditions.

•

Ensure the flow of the test is clear.

•

Complete point sheets with problems, and include resolutions.

•

Ensure environment is clean for the next cycle.

Process Followed?

•

Ensure actual results match expected results.

•

Ensure all conditions are successfully tested.

•

Submit data and migration requests as necessary.

•

Update test cycles and test conditions with testing status.

•

Update status of system.

•

Collect appropriate metrics.

•

Obtain final consent by test lead, project sponsor, or other authority.

User Acceptance and System Test Exit Criteria

This section contains a set of exit criteria that can be used to control the quality of the deliverables related to the test

Use this checklist to understand when the test is considered complete.

Criteria Met?

•

Ensure solution performs all functionality as defined.

•

Make sure the solution meets quality requirements.

•

Determine whether one can gain a basic understanding of the solution from the documentation.

Documentation Complete?

•

Actual results

•

Problems remaining to be resolved

• Resolved problems

•

Stakeholder consent

Standards Met?

•

Ensure the actual results show proof of testing.

•

Create cross-references to the test cycles and conditions.

•

Ensure the flow of the test is clear.

•

Complete point sheets with problems, and include resolutions.

•

Ensure environment is clean for the next cycle.

Process Followed?

•

Ensure actual results match expected results.

•

Ensure all conditions are successfully tested.

•

Submit data and migration requests as necessary.

•

Update test cycles and test conditions with testing status.

•

Update status of system.

•

Collect appropriate metrics.

•

Obtain final consent by test lead, project sponsor, or other authority.

Gathering report requirements

Requirements Checklist

S is the requirement

specific?

Is it clear what is asked of the solution?

In other words, will different readers understand the requirement in the same way?

M is the requirement

measurable?

Can a test be devised as to whether the solution actually implements the requirement?

For example, if the requirement talks of maximizing, is there a way of determining that the solution s result is really a maximum?

A is the requirement

attainable?

Can the solution do what s asked of it?

Does reasonable evidence exist that the requirement is within the limits of the available technology?

R is the requirement

realizable?

Can the requirement be implemented given the project s constraints?

For example, is the budget large enough to create the conditions necessary for the requirement to be implemented (e.g., buy enough disk space or change the organization s business processes)?

T is the requirement

traceable?

Does the requirement support the objectives of the project?

In other words, does the requirement have value given the expectations for the project?

Gathering report requirements

Requirements Checklist

S is the requirement

specific?

Is it clear what is asked of the solution?

In other words, will different readers understand the requirement in the same way?

M is the requirement

measurable?

Can a test be devised as to whether the solution actually implements the requirement?

For example, if the requirement talks of maximizing, is there a way of determining that the solution s result is really a maximum?

A is the requirement

attainable?

Can the solution do what s asked of it?

Does reasonable evidence exist that the requirement is within the limits of the available technology?

R is the requirement

realizable?

Can the requirement be implemented given the project s constraints?

For example, is the budget large enough to create the conditions necessary for the requirement to be implemented (e.g., buy enough disk space or change the organization s business processes)?

T is the requirement

traceable?

Does the requirement support the objectives of the project?

In other words, does the requirement have value given the expectations for the project?

Powerplay Error Messages

Message TR0210

<n> data input conversion or overflow errors occurred. See the log file for details.

Within one of the source data files that is associated with a model data source, the value specified

for a measure is either too large or uses an invalid storage type.

If you check the log file associated with the model you are updating, you will find a line that looks

something like this:

(TR1703) A data input conversion or overflow error occurred at source record

number 100 for measure 'Revenue' in source file

'c:\trnsfrmr\data\national.asc'.

You can use this information to identify which input data records contain invalid source values.

Message TR0214

The temporary file for source file < > and PowerCube < > is empty. Check that your

source file contains data.

During the PowerCube creation process, Transformer has been unable to find data for use in a PowerCube. This can happen if

• your source data file is empty.

• you have applied a view to the PowerCube that excludes all of the data for a given dimension.

Excluding all data for a dimension using a dimension view will cause the PowerCube to be empty.

• the timing for all data sources is such that none of them are used to create PowerCubes.

Powerplay Error Messages

Message TR0210

<n> data input conversion or overflow errors occurred. See the log file for details.

Within one of the source data files that is associated with a model data source, the value specified

for a measure is either too large or uses an invalid storage type.

If you check the log file associated with the model you are updating, you will find a line that looks

something like this:

(TR1703) A data input conversion or overflow error occurred at source record

number 100 for measure 'Revenue' in source file

'c:\trnsfrmr\data\national.asc'.

You can use this information to identify which input data records contain invalid source values.

Message TR0214

The temporary file for source file < > and PowerCube < > is empty. Check that your

source file contains data.

During the PowerCube creation process, Transformer has been unable to find data for use in a PowerCube. This can happen if

• your source data file is empty.

• you have applied a view to the PowerCube that excludes all of the data for a given dimension.

Excluding all data for a dimension using a dimension view will cause the PowerCube to be empty.

• the timing for all data sources is such that none of them are used to create PowerCubes.

PowerPlay error messages

Message TR0114

Transformer can't write in the model temporary file.

This error is usually caused by insufficient disk space to write the temporary work files. For a

rough estimate of how much disk space you need to create a cube, multiply the size of the data

source(s) by 3.5.

You can find the location of temporary work files in the Directories tab of the Preferences dialog

box (File menu). Free up more space on the work file drive and retry.

For more information, see the

Administrator's Guide.

Message TR0116

Transformer can't open the file < >.

Make sure that the path and file name are correct.

There may be incorrect information in the Directories tab of the Preferences dialog box (File

menu).

If this error occurs when you are running an MDL script in the command line, the problem may

be that the MDL script contains the command SavePY and you are also using the -s command line

switch to save the file to .py? format. Try removing the -s option.

PowerPlay error messages

Message TR0114

Transformer can't write in the model temporary file.

This error is usually caused by insufficient disk space to write the temporary work files. For a

rough estimate of how much disk space you need to create a cube, multiply the size of the data

source(s) by 3.5.

You can find the location of temporary work files in the Directories tab of the Preferences dialog

box (File menu). Free up more space on the work file drive and retry.

For more information, see the

Administrator's Guide.

Message TR0116

Transformer can't open the file < >.

Make sure that the path and file name are correct.

There may be incorrect information in the Directories tab of the Preferences dialog box (File

menu).

If this error occurs when you are running an MDL script in the command line, the problem may

be that the MDL script contains the command SavePY and you are also using the -s command line

switch to save the file to .py? format. Try removing the -s option.

Cognos 8 with Lotus Notes

The Data Modeler permits Cognos ReportNet or Cognos 8 BI to access data held in IBM Lotus Domino Databases. The Data Modeler employs a Notes based, Graphical Wizard to generate hidden Notes Views and associated XML data models, then inserts these elements into target Notes databases.

Real time queries from Cognos reporting to Domino is now possible utilizing a Notes SQL connection for true enterprise reporting, portal content, and composite applications.

 

Optionally, Data Modeler can now be used with the Sun & Son DataBridge to shape and export Notes data to a variety of relational data stores.

The Data Modeler for Notes is contained in a Notes database which can be installed on a Domino server or on a local Notes client. This documentation assumes that the database is installed on the Domino server. Should you choose to install the Data Modeler on a separate administrative client make sure that the Notes SQL configuration and connection are relative to the resident Notes SQL connection that will be used on an ongoing basis.

Cognos 8 with Lotus Notes

The Data Modeler permits Cognos ReportNet or Cognos 8 BI to access data held in IBM Lotus Domino Databases. The Data Modeler employs a Notes based, Graphical Wizard to generate hidden Notes Views and associated XML data models, then inserts these elements into target Notes databases.

Real time queries from Cognos reporting to Domino is now possible utilizing a Notes SQL connection for true enterprise reporting, portal content, and composite applications.

 

Optionally, Data Modeler can now be used with the Sun & Son DataBridge to shape and export Notes data to a variety of relational data stores.

The Data Modeler for Notes is contained in a Notes database which can be installed on a Domino server or on a local Notes client. This documentation assumes that the database is installed on the Domino server. Should you choose to install the Data Modeler on a separate administrative client make sure that the Notes SQL configuration and connection are relative to the resident Notes SQL connection that will be used on an ongoing basis.