6 Troubleshooting Guidelines

The following sections highlight a few of the most common errors you can encounter and their solutions.

6.1 Troubleshooting Guidelines Related to Agile Product Lifecycle Management

In previous releases conformed dimensions (when the same dimension is used by two subject areas) did not work.In this release, OPLA is providing the ability to use conformed dimensions for multiple lists. To display a new multi-list user-defined attribute as a column in an existing dimension table in BI Reports use the Attribute ID or the Attribute Name.

To view and use the multi-list attribute in BI Reports, you must configure the multi-list attribute in the BMM layer, and then expose it in the OBIEE Repository's Presentation Layer. For the corresponding data to populate, you must map the column using OPLA Configurator.

The table below lists Agile PLM related errors and their solutions.

ISSUE	SOLUTION
The System cannot find the file specified.	Check if any of the following files are missing under the <install.dir>/config directory. If any are missing, reinstall BI. BIDataLayerConfig.properties Configurator.xml Configurator.xsd log4j.properties Messages_en_US.properties
TNS: listener does not currently know of SID given in connect descriptor.	Ensure that the SID provided in the following token within the BIDataLayerConfig.properties file is the same as the database SID. TGT_DB_URL =I jdbc:oracle:thin:@<machine name>:<port number>:<SID>
Invalid user name/password; login denied.	Check if the following tokens reflect the right user name and password information in the BIDataLayerConfig.properties file: ý ODM_UN - user name for Data Mart database schema ý <ODM_PASSWORD> - password for Data Mart database schema user ý BI_USER_NAME - user name for MDS database schema ý <BI_PASSWORD> - password for MDS database schema user Encode the Data Mart and MDS passwords and compare the values with the ODM_PASSWORD and BI_PASSWORD.
TNS: listener could not hand off client connection. OR Error while saving records.	Test your database connection and make sure the database server and listener have successfully started.
userid: following logging levels are used in application userid: fatal - The FATAL level designates very severe error events that will presumably lead the application to abort	ý INFO - The INFO level designates informational messages that highlight the progress of the application at coarse-grained level. ý ERROR - The ERROR level designates error events that might still allow the application to continue running. ý DEBUG - The DEBUG Level designates fine-grained informational events that are most useful to debug an application.

6.2 Troubleshooting Guidelines Related to Agile PLM for Process

Use the table below if you have mapped an Extended Attribute, or a Project Metric, via an insert to the appropriate mapping table, but it does not show up in OBIEE.

Did you ...	Solution
commit the insert?	By default, Oracle DB sessions does not automatically commit any changes.
run the ODI Operator after the commit?	See main guide for information on how to run ODI.
run the ODI Operator run to successful completion?	If the ODI Operator did not successfully complete, then check the TLOG table for mapping error messages.
also modify the RPD file (via the OBIEE Administrator) to enable the viewing of those fields in the appropriate Subject Area? Only if the text for the column you mapped to begins with USRDEF_.	If not, then modify the RPD file.
restart the OBIEE service and/or flush its cache after completing the above changes?	You must flush the cache and restart the OBIEE service.

You may receive a TLOG table error message. The table below lists some of the most frequent TLOG table error messages and their solutions.

TLOG Table Message	Solution
There is a config error in P4P_METRIC_CONFIG_MAP. Unsupported Table. Use one of the following tables: P4P_PRJ_SUM_FS, P4P_PRJ_DET_FS, P4P_PROJECT_DS and P4P_PRJ_METRICS_FS.	Inspect the records in the P4P_METRIC_CONFIG_MAP table for an unsupported table, and fix.
There is a config error in P4P_METRIC_CONFIG_MAP. Multiple metrics mapped into same column.	Inspect the records in the P4P_METRIC_CONFIG_MAP table for two rows where the table_name and column_name values are the same. Remove or fix duplicates.
There is a config error in P4P_METRIC_CONFIG_MAP. Project Metric mapped to same column as Extended Attribute.	Inspect and compare the table_name and column_name values of the records in the P4P_METRIC_CONFIG_MAP and P4P_CONFIG_EA tables. Remove or fix duplicates.
There is a config error in P4P_METRIC_CONFIG_MAP. XXXX.YYYY is not a valid column.	Please refer to the legal destination table and column names list elsewhere in this document.
Could not find Metric Definition for fully qualified metric: XXXXX.	Double-check the name of the NPD Project Metric in the Agile PLM for Process source projects. Remember it will probably have some underscore characters in it separating the Basis, Phase and Fiscal Year qualifications.
Could not find Metric Definition for metric base name: XXXXX.	Double-check the name of the NPD Project Metric in the Agile PLM for Process source projects. Remember it will have NO qualification suffixes attached to it for Basis, Phase nor Fiscal Year.
Attempt to map Text Metric to non-text column. OR Attempt to map numeric or date Metric to non-numeric column	Inspect and verify the data-types of the table_name and column_name values of the records in the P4P_METRIC_CONFIG_MAP table and the NPD Project Metrics that are mapped to them. Refer to the legal destination list elsewhere in this document.