Go to primary content

Oracle Product Lifecycle Analytics Installation and Setup Guide Release 3.5 E70274-01 |
| Contents

Previous | Next |

# 7 Troubleshooting

This chapter lists common errors and troubleshooting guidelines for your reference. If you experience errors other than those listed here, contact Oracle Support.

Note All issues are applicable for Agile PLM and Agile PLM for Process, unless stated otherwise.

## 7.1 Installation Issues

Unsupported Operating systems error

I use Windows XP operating system. I get a warning that states 'Unsupported Operating System' when I run the OPLASetup.exe file. There are options to quit or continue the installation. If I continue the installation what is the impact?

Cause:

You are running the installer on a computer that is not a Server. This warning indicates that Oracle does not support any issues that might come up after the installation of the software on a desktop at work or a Personal Computer (PC) used for software demonstrations.

Action:

There are no known adverse impacts if you continue with the installation. This warning does not appear if you install OPLA on a Server.

You can choose to quit the installation if you do not want to install the application on your work desktop or Home PC.

Installation Unsuccessful

During the installation of OPLA, I get an error message: Installation unsuccessful.

Action:

If the Database and ETL are installed together, check the Logs\DataMartInstall.log file. If the Database and ETL are installed separately, including on different machines, check the database install log at logs\DatamartDBInstall.log and the ETL install log at logs\DataMartETLInstall.log.

Repeat the installation using the latest download of the OPLASetup file.

Unable to select the same installation directory if I install Oracle Product Lifecycle Analytics database and ETL components separately

I have installed the OPLA database. I am unable to install the OPLA application in the same system and in the same directory where the database is installed.

Action:

If you are installing both the database and ETL on the same system, you can select both options together in the installer. If you install them separately in the same system, you will need to use two separate install folders.

Page cannot be displayed

I completed the installation successfully but when I launch the OPLA application URL, I get a 'Page cannot be displayed' screen.

Action:

Make sure to start the following services in the listed order:

1. OC4J

2. Oracle BI Java Host

3. Oracle BI Server

4. Oracle BI Presentation Server

Installer failed to create Data Mart schema, ODI Work repository and/or ODI Master repository schemas

Look for possible root causes in DatamartInstall.log, located in the logs folder of the Oracle PLA Data Mart install home directory.

Possible root causes could be:

- Database version specified is different from the one installed in the system. For example, Oracle 11g option is selected during installer while the machine has Oracle 12c.

- Path specified for Oracle Target DB Tablespaces could be invalid.

- Oracle Database path specified is incorrect.

- Database Instance exists, but the System user does not have proper privileges required to create and grant appropriate roles to schema users.

Incorrect installation of Oracle database

Database name specified when you create the database, may pre-exist. Choose another data base name to resolve the issue.

Installer failed to create ODI Work repository and ODI Master repository

Look for possible root causes under ODIRepCreation: tag in DatamartInstall.log:

- Work Repository and Master Repository schemas are not created for possible root causes outlined in #1.

- Tablespace specified for Work & Master repository are invalid.

- JAVA_HOME and JAVA_ODI_HOME environment variables are incorrect.

- Specified ODI directory is incorrect or ODI is not installed at specified path.

ODI Project "AGILE PLM ANALYTICS" does not have any packages

Besides the root causes outlined in #2, look for errors under ODI-PHY-Creation section in DatamartInstall.log for other issues:

- OdiImportObject failed to execute for incorrect JRE specified

- JDK version specified is either less than 1.5.x or 1.6 or above.

- Specified Work Repository Name is already used in existing ODI

- ODI already has projects that have conflicting Work and Master Repository IDs. Oracle PLA Data Mart uses following repository IDs:

Work Repository ID = 102

Master Repository ID = 103

Data Mart installation failed in Solaris.

If you are using Solaris installer for ODI, the Data Mart Installation fails. To avoid this installation error, use ODI Linux installer and manually install ODI as outlined in the ODI Installation Guide.

Installation fails with non-default Listener

If you are installing OPLA Data Mart on a database with a non-default listener on a non-default port, make sure the listener is added to the listener.ora file in order to be recognized by the installer.

Installer unable to find Oracle Database Server

If you are installing OPLA Data Mart on a 64-bit Windows system, an error message may display stating that the Oracle Database server was not found, even though it is installed. Ignore this message and continue with the installation.

Data Mart database instance not recognized by Oracle Database Configuration Assistant when using the Oracle Product Lifecycle Analytics Installer.

A user with Admin privileges must manually add the database as an entry to the oratab file, located in either the /etc or var/opt/oracle/ directory, based on the operating system.

Unable to update RPD and Web Catalog

The Oracle Product Lifecycle Analytics Installation is unsuccessful. I am unable to update RPD and Web Catalog.

Action:

Ensure that the OC4J server is running before you begin the installation.

My OC4J server is not starting after deploying the RPD.

Make sure that you have configured appropriate Connection Pool settings in OBIEE Administrator.

To configure connection pool settings:

1. Log in to the OBIEE Administration tool.

2. Verify in the Physical layer that Data Source Name is PLMA and its username/password is PLMBIMDS/PLMBIMDS.

   Note The login details provided are default logins and may differ from those on your system, if changed during installation.

3. In the Connection Pool window of Physical Layer, if the Data Source Name is not PLMA, then replace the Name in the Data Source Name field.

4. In the Connection Pool window of Physical Layer, if the username and password of the MDS Database are not PLMBIMDS, then replace the username and password in the User name and Password fields. Click OK.

5. Confirm the new password.

## 7.2 ETL Runtime Issues

Connection Identifier error on ETL run with Agile PLM source (Agile PLM)

When I run ETL, the ODI_INT_CREATE_DBLINK task displays a connection identifier error message.

Cause:

The TNSNAMES.ORA file does not have the correct information that enables connection to the source database.

Action:

Add a TNSNAME entry in the target database that points to the source database before you run the ETL.

If the database SID name of the source and target database are different (Example: Source SID = AGILE9 and Target SID = PLMDM), then modify the TNS Service name to the name of the source database name in the tnsname.ora file, like AGILE9, in this example.

If the database SID name of the source and target database are the same (Example: Source SID = AGILE9 and Target SID = AGILE9), to eliminate DBLINK errors:

1. Modify the TNS entry as follows:

   AGILE9_LAB1 =

   (DESCRIPTION =

   (ADDRESS_LIST =

   (ADDRESS = (PROTOCOL = TCP)(HOST = LAB1)(PORT = 1521))

   )

   (CONNECT_DATA =

   (SERVICE_NAME = AGILE9)

   )

   )

2. Start > Oracle > Oracle Data Integrator > Topology Manager

   In the Topology Manager select Physical Architectures >Technologies>Oracle>SRC_CONN_PHYSICAL.

3. Replace the added TNSNAME (Example: AGILE9_LAB1) in the DB link column.

Credential retrieval failure error on ETL run (Agile PLM)

My Database server and ODI/ETL systems are in two different domains. When I run ETL, the ODI_INT_CREATE_DBLINK scenario returns the following message:

ORA-12638: Credential retrieval failed.

Cause:

The source DB and target DB are in different domains.

Action:

To eliminate the DBLINK errors:

1. Navigate to the %oracle_home%\network\admin directory.

2. Modify the SID and HOSTNAME in the TNSNAME entry to reflect the domain name.

3. Start > Oracle > Oracle Data Integrator > Topology Manager.

4. In the Topology Manager, select

   Physical Architectures >Technologies>Oracle>SRC_CONN_PHYSICAL.

5. Replace the added TNSNAME ( Example: AGILE9.ALAB01) in the DB link column.

To verify DBLINK:

Execute the scenario ODI_INT_CREATE_DBLINK from ODI operator in ODI.

If the scenario fails, the following message appears again:

Link AGILE9.ALAB01 error: ORA-12638: Credential retrieval failed

To resolve this issue:

1. Navigate to the %oracle_home%\network\admin directory

2. Modify the value of SQLNET.AUTHENTICATION_SERVICES in sqlnet.ora file as follows:

   Original Entry - SQLNET.AUTHENTICATION_SERVICES= (NTS)

   Modified Entry - SQLNET.AUTHENTICATION_SERVICES= (NONE)

3. Restart the database instance.

4. Re-run the scenario ODI_INT_CREATE_DBLINK from ODI operator in ODI.

Unable to run ETL after a configuration change

If there are any PLM configuration changes, such as the renaming of an attribute, it is recommended that you run a full ETL. Consult Oracle Support if you need help in resetting your ETL to full load.

Errors when using external .csv files

Do not add deleted Projects to the prj_cost.csv and prj_forecast.csv files.

If any ETL task fails during run-time the best option is to check the Execution tab of the ETL task in ODI Operator:

1. Log in to ODI Operator.

2. Select the Sessions List tab.

3. Expand All Executions in the left pane.

4. Select the task that is failing by double-clicking on it.

5. Select the Execution tab to view error details. Optionally, you can also export entire log file as an XML file thru Operator to check for multiple errors.

6. If the scenario name starts with ODI_PRO, look for PL/SQL errors logged in the VLOG table. See PL/SQL Logging section for more details on how to enable "debug mode" for detailed PL/SQL traces. Debug Mode for PL/SQL should be enabled if you need to further debug the issue.

If any ETL task hangs during run-time, check the Execution tab of the ETL task in ODI Operator:

1. Log in to ODI Operator.

2. Select the Sessions List tab.

3. Expand All Executions in the left pane.

4. Identify the task that is hanging by double-clicking on it.

5. Consult your DBA and provide the details noted in the previous step to help research and possibly identify any long-running SQL in the Data Mart schema.

6. Enable the Debug Mode for PL/SQL and look for errors in the VLOG table.

## 7.3 PL/SQL Logs

The log details are stored in the following table/view in the Data Mart schema:

- TLOG (Table)—This table contains information like timestamp, ID, etc.

- VLOG (View)—This is a vew created for the TLOG table and contains only the ERROR messages.

The values for LOG_LEVEL in the ETL_parameter table can be set as follows:

LOG_LEVEL | Mode | Value
OFF | 10
FATAL | 20
ERROR | 30
WARN | 40
INFO | 50
DEBUG | 60
ALL | 70
The default value of LOG_LEVEL is '30'.

## 7.4 Database Issues

Connectivity Errors

- Agile PLM or Agile PLM for Process source database is available and accessible from the Oracle PLA Staging machine

- Verify source database schema details

- Target (OPLA Data Mart) database is available

- Verify Target database schema details

DB Link does not work when source and target schema are created in the same database (Agile PLM)

Create a TNS name that is different from the database name and SID. In the ODI Topology Manager, go to Physical Architecture>Technologies>Oracle>SRC_CONN_PHYSICAL. Manually update the Instance/Data Server field.

Data Issues such as column width

Check the column in both Source and Target schema (refer to Schema documentation for table/column details).

Disk space

Check the Target database machine to ensure enough space is available for ETL to execute and add data.

Database Sessions to execute ETL

Check the database for enough sessions (>500) with which the ODI will run smoothly. To check database session and process parameters:

1. Login as sys/<PWD> as sysdba in command prompt using sqlplus.

SHOW PARAMETER SESSIONS

SHOW PARAMETER PROCESSES

2. Alter system set processes=1000 scope=spfile; OR

3. Alter system set processes=1000 scope=both;

4. After altering the Database, restart the instance.

Linux/Unix Specific only

- If you receive a 'cannot execute' message, re-run the command with the following options: chmod u+x OPLASetup*.bin

- Make sure the TNS Listener is running with the ps -ef | grep tns command. If nothing shows, then it is not running.

- If the TNS Listener is running, check the status with the lsnrctl status command.

Unable to view reports

When I login to the Oracle Product Lifecycle Analytics Application, I am unable to view any report. The window displays ODBC Driver errors.

Action:

If either TNSNAMES or MDS schema names or both are not default, reconfigure the TNSNAMES.ORA file, CONNECTION POOL details and MDS Schema Name in OBIEE Administrator, as appropriate.

## 7.5 OBIEE 11g Privilege Issues

Unable to view the Edit Dashboard option even though relevant privileges are set to edit the dashboard

Perform the following steps to enable the dashboard:

1. Deploy system-jazn-data.xml file

2. Import LDIF file into the Embedded LDAP server

3. Refresh the user GUIDs

To deploy system-jazn-data.xml file

1. Shutdown all processes in the BI EE system, specifically the following:

   - Administration server

   - All managed servers in the cluster (bi_cluster)

   - All OPMN managed processes

2. Backup and rename the existing <DOMAIN_HOME>\config\fmwconfig\system-jazn-data.xml.

   For example, if the BI EE root folder is named OracleBIEE11g, then the domain folder location (on Windows) will be <OracleBIEE11g>\user_projects\domains\bifoundation_domain\config\fmwconfig.

3. Copy the system-jazn-data.xml file from <PLMBI>\olap\OBIEEPrivilegeIssue to <DOMAIN_HOME>\config\fmwconfig.

   Note <PLMBI> refers to Oracle Product Lifecycle Analysis Business Intelligence application temp directory where the RPD and Web Catalog folders are also located.

4. Start all the processes in the BI EE system for the Oracle BI Applications security policy to take effect, specifically the following:

   - Administration server

   - All managed servers in the cluster (bi_cluster)

   - All OPMN managed processes

To import the OPLA Identity Store (LDIF) File into the Embedded LDAP Server:

Perform the following steps to import the OPLA LDIF file:

1. Log in to the WebLogic Server Administration Console. For example: http://<hostname>:7001/console.

2. Select the name of the security realm into which the LDIF file is to be imported. For example, myrealm.

3. Select Providers > Authentication and choose the provider into which the LDIF file is to be imported. For example, DefaultAuthenticator.

4. Select Migration > Import. Enter the full path of LDIF file in the text box Import File on Server. For example, <PLMBI>\olap\OBIEEPrivilegeIssue.

5. Click Save.

   Note You need to import the standard (out-of-the-box) OPLA LDIF file into the WebLogic Server (embedded LDAP server) available in the installer location (<PLMBI>\olap\OBIEEPrivilegeIssue).

To refresh the user GUIDs

Perform the following steps to refresh the user GUIDs:

1. Open the NQSConfig.INI file in the Edit mode. For more information, refer to the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

2. Locate FMW_UPDATE_ROLE_AND_USER_REF_GUIDS and set its value to YES.

3. Modify the instanceconfig.xml file to instruct the Presentation Services to refresh GUIDs on restart. Edit the file to add the last line in the following instruction.

   <ps:Catalog xmlns:ps="oracle.bi.presentation.services/config/v1.1">

   <ps:UpgradeAndExit>false</ps:UpgradeAndExit>

   <ps:UpdateAccountGUIDs>UpdateAndExit</ps:UpdateAccountGUIDs>

4. From a terminal window, stop and restart the managed processes using the opmnctl parameters stopall and startall.

   Note You can use the parameter status to verify process status throughout.