Cognos data model for an agent loads into Framework Manager but testing a table causes a table or view not found error

The Cognos data model for an agent loads into Framework Manager, but the testing a table causes a table or view not found error.

This problem could have two different causes and solutions:

• The agent's tables do not exist in the Tivoli Data Warehouse database.

  Install and configure the agent, start historical collections, and configure summarization. Allow time for the agent to export data to the warehouse proxy and for the Summarization and Pruning agent to summarize data.

• The schema name used in the data model's data source does not match the schema used in the Tivoli Data Warehouse database.

  Change the schema value in the data source to match the schema used.

Testing any of the tables in the IBM_TRAM schema in Framework Manager results in an error on DB2

Testing any of the tables in the IBM_TRAM schema in Framework Manager results in following error on DB2:

This query contains an error 
and can not be executed. 
[IBM][CLI Driver][DB2/AIX64] SQL0551N
"ITMUser" does not have the required 
authorization or privilege to perform 
operation "SELECT" an object  
"IBM_TRAM.ComputerSystem".SQLSTATE=42501

Grant select permission on all the Tivoli Reporting and Analytics Model tables. Change <IBM_TRAM> to the schema used for Tivoli Reporting and Analytics Model and <Tivoli Data Warehouse user ID> to the Tivoli Data Warehouse user ID.

1. Connect to the Tivoli Data Warehouse as a user with SYSDBA privileges.
2. Issue the following grants:
   1. Grant select on <IBM_TRAM>."ComputerSystem" to <Tivoli Data Warehouse user ID>
   2. Grant select on <IBM_TRAM>.MONTH _LOOKUP to <Tivoli Data Warehouse user ID>
   3. Grant select on <IBM_TRAM>.TIMEZONE_ DIMENSION to < Tivoli Data Warehouse user ID>
   4. Grant select on <IBM_TRAM>.TIME_DIMENSION to <Tivoli Data Warehouse user ID>
   5. Grant select on <IBM_TRAM>. WEEKDAY_LOOKUP to <Tivoli Data Warehouse user ID>
   6. Grant execute on procedure <IBM_TRAM>. CREATE_TIME_DIMENSION to <Tivoli Data Warehouse user ID>

When running on Windows, testing an Oracle data source in Tivoli Common Reporting fails

When running on Windows, testing an Oracle data source in Tivoli Common Reporting fails with an error similar to the following:

QE-DEF-0285 The logon failed.
QE-DEF-0325 The logon failed for the 
following reason:
RQP-DEF-0068 Unable to connect at least 
one database during
a multi-database attach to 1 database(s) 
in: testDataSourceConnection  
                                         

The Oracle client libraries are not in the system PATH environment variable. Edit the PATH environment and add the directory that contains the Oracle client DLL files. Restart the Tivoli Common Reporting server.

The ManagedSystem dimension can not be utilized when creating reports for an agent

I am not able to utilize the ManagedSystem dimension when creating reports for my agent.

• Make sure you have created or altered the ManagedSystem table in the Tivoli Data Warehouse. For more information, see Create or alter the ManagedSystem Table and Stored Procedure in the Tivoli Data Warehouse.
• Make sure you have created the stored procedure that populates the ManagedSystem table for Agent Builder agents. For more information, see Create or alter the ManagedSystem Table and Stored Procedure in the Tivoli Data Warehouse.
• Make sure you have run the stored procedure using your agent's product code. For more information, see Running the stored procedure.
• Examine the ManagedSystem table to ensure that entries for your agent type exist in the table.

Warnings when Model Advisor is run against the Cognos data model

When the Model Advisor is run against the Cognos data model the following warnings appear:

Issue 1: Facts identified by cardinality

The query subject is identified as a fact because of the cardinality of its relationships. It is recommended that you review the implications of this to SQL generation and, if appropriate, change the usage of the query subject or its relationships.

Problem Description: The query subject TEST_1 is on the many side of all its referencing relationships.

Issue 2: Query subjects that can behave as facts or dimensions

This query subject can behave as a fact or a dimension. It is recommended that you evaluate this query subject in the context of the model to ensure queries will not be split improperly or unnecessarily.

Problem Description: The query subject ManagedSystem is referenced by relationship ends of different cardinalities.

Issue 3: Determinants that conflict with relationships

There is a determinant specified that conflicts with the relationship you have defined. This ambiguity can cause a query to be split unnecessarily. It is recommended that you examine and resolve this in the model.

Problem Description: The relationship 'TIME_DIMENSION <- -> WEEKDAY_LOOKUP’ does not reference all the keys of any uniquely identified determinant in the query subject 'TIME_DIMENSION’. The relationship has a 0:1 or 1:1 cardinality, indicating that its keys should be an exact match to the keys of a uniquely identified determinant. Please review the cardinality of the relationship and the determinant information to determine if adjustments are required.

(continued on the next page)

Warnings when Model Advisor is run against the Cognos data model

(continued)

Issue 4: Factors that will override the Minimized SQL setting

A query subject has attributes that will override the SQL Generation type setting of Minimized. Relationships between model query subjects, determinants on model query subjects and data source query subjects with modified SQL will override the Minimized SQL Generation type.

Problem Description: There may be problems generating minimized SQL for the object Time Dimension. The object is set to use minimized SQL.

Problem Description: There may be problems generating minimized SQL for the object ManagedSystem. The object is set to use minimized SQL.

Problem Description: There may be problems generating minimized SQL for the object ManagedSystemName. The object is set to use minimized SQL.