1. Installation and Configuration Troubleshooting Guide
  2. General Tips and Solutions
  3. Configuration Tips and Solutions

Configuration Tips and Solutions

For help with installation issues, see Installation Tips and Troubleshooting.

Tip:

If your configuration process is blocked by a prerequisite check, and you believe you understand the warning and can proceed with the configuration despite it, you can ignore the prerequisite checks and try to proceed by running EPM System Configurator with the -ignoreChecks option.

Configuration Fails in a Distributed Environment

Issue:

The Deploy to Application Server task fails for web applications in a distributed environment.

In a distributed environment, you must run RCU and edit RCUSchema.properties on each machine in the environment. Each machine requires a unique Prefix when running RCU. If you perform this step incorrectly, configuration fails.

Solution:

If configuration fails due to a mistake or incorrect entry in RCUSchema.properties, perform the steps below in order to ensure a successful configuration:

  1. Cancel and exit EPM System Configurator.
  2. Correct the entries in RCUSchema.properties and make sure that all values are correct. The prefix must be unique on each machine in the environment.

    Use the SID not the service name in the JDBC URL.

  3. Drop all database users—those created using RCU (use the RCU drop schema option) as well as the database user that you used for Oracle Enterprise Performance Management System configuration.
  4. Create new database users:
    • Run RCU again and provide a unique prefix for each machine in the environment.
    • Create the database user for EPM System configuration
  5. Rename the user_projects folder, for example to user_projects_old. By default the location is C:\Oracle\Middleware\user_projects.
  6. Re-run EPM System Configurator and complete required tasks.

    Because you renamed the user_projects folder, you are performing a new configuration rather than reconfiguring.

  7. Delete the user_projects_old folder.

Creating the RCU schema on Oracle Database Without SYSDBA Rights

You must create RCU schemas before configuring EPM System. Use this procedure if you don't have SYSDBA rights:

  1. Log in to SQL Plus using a db user with sys or sysdba privileges and complete the following steps:
    1. Create user testrcu IDENTIFIED BY password (for example with a user named testrcu).

    2. Privileges testrcu

      Create Session

      Select Any Dictionary

      Select_catalog_Role

    3. Grant the following permissions to the user:
      grant select_catalog_role to testrcu;
grant select any dictionary to testrcu;
grant create session to testrcu;
grant select on schema_version_registry to testrcu;

    Note:

    If you encounter a Table or view does not exist error message when you execute the last command, you can ignore it.

  2. Navigate to ORACLE_HOME/oracle_common/bin and start RCU:

    • Windows: For example: C:\Oracle\Middleware\oracle_common\bin\rcu.bat

    • Linux/Unix: ./rcu

  3. Select Prepare Scripts for System Load. (Don't select System Load and Product Load.).

  4. There must be two scripts generated, by default the scripts are located in ORACLE_HOME/oracle_common/rcu/log/logdir.[date_timestamp].

    • script_systemLoad.sql

    • script_postDataLoad.sql

  5. Log in to SQL Plus using a db user with sys or sysdba privileges and complete the following steps, or give the scripts to your DBA to run:

    1. Execute the script_systemLoad.sql script.
    2. Before performing the product load phase, the user (in this example testrcu) must be granted the following:
      • grant REGISTRYACCESS to testrcu;
      • grant STBROLE to testrcu;
  6. Start RCU again and select Perform Product Load as Non DBA user to complete the data load.

  7. Log in to SQL Plus using a user with sys or sysdba privileges and execute the script_postDataLoad.sql script to complete the Product load phase, or give the scripts to your DBA to run.

  8. Update the RCUschema.properties file, using this as an example:
    sysDBAPassword=<password created in step one>
schemaPrefix=testrcu1
rcuSchemaPassword=<you are prompted for schema password in the script>
dbURL=jdbc:oracle:thin:@dbserver:1521:ORCL
sysDBAUser=testrcu <user you created in step one>

Distributed Environments

In a distributed environment, after completing the configuration of EPM System products on any machine, close EPM System Configurator before beginning configuration another machine.

Java Heap Size Changes

You can change Java heap sizes when using services to start and stop Java web application servers in Windows environments. You can make the changes in batch files or in the Windows registry. After making the changes for a product, you must restart the Java web application server. For details, see the Oracle Enterprise Performance Management System Deployment Options Guide.

Product Databases

Oracle recommends that you put each EPM System product in its own database schema to provide flexibility in database backup and recovery. In prototype and development environments, configuring one database for all products may be satisfactory.

EPM System Configurator Startup

Issue: After a successful EPM System installation and configuration, you cannot start EPM System Configurator from the Windows Start menu, and you get this message:

FATAL ERROR: Environment variables check failed with message "Environment variables aren't set correctly"

Solution: Restart the computer.

Oracle HTTP Server Configuration

Issue: When trying to open the exported ewallet.p12 file while configuring Oracle HTTP Server for SSL, you get this error message even though you entered the correct password:

The password is incorrect. Try again.

Solution: Inability to open the wallet results from a defect in Oracle Wallet Manager. Oracle Wallet Manager 11g cannot read the PKCS12 keystore created from third-party tools such as OpenSSL. Until this issue is resolved, use the Oracle Wallet Manager that is shipped with the Oracle 10g Client to read the new ewallet.p12 file and save it for use with Oracle HTTP Server 11gR1.

Out-of-Memory Error with Multiple Java Web Application Deployments

Issue: When several Java web applications are deployed, an out-of-memory message is displayed at deployment.

Solution:

Increase the default memory setting in the Oracle WebLogic Server Administration Server.

First-Time Configuration of the Shared Services Database

Issue: When EPM System Configurator is run for a first-time configuration, the Perform 1st-time configuration of Shared Services database option is unavailable.

Solution: To configure EPM System in this scenario:

  1. Start EPM System Configurator from the command line using the –forceRegistry option.

  2. Configure Oracle Hyperion Foundation Services:

    Select the Foundation Services tasks Common Settings, then Configure Database, and then Deploy to Application Server.

  3. Exit EPM System Configurator.

  4. Restart EPM System Configurator in the usual way to configure the remaining EPM System products.

Connection to a Clustered SQL Server Deployment

Issue: You need to configure EPM System to connect to a clustered SQL Server deployment.

Solution: In EPM System Configurator, enter the virtual host of the SQL Server cluster in the Server field on the Configure Database screen.

Missing JAR Files

Issue: Errors about missing JAR files are generated when you launch EPM System Configurator after installing several EPM System products, and EPM System Configurator closes in about 30 seconds.

Solution: Error messages about missing JAR files indicate that the installation is incomplete. Check for these messages.

If you see error messages about missing JAR files or errors related to oracle_common jars, then the WebLogic Server installation is incomplete.

Look in the ohs and oracle_common subfolders of MIDDLEWARE_HOME. If ohs contains only one or two subfolders, or if oracle_common is empty, then the Oracle HTTP Server, WebLogic Server, or Application developer installation is incomplete. Check the minimum swap space on the system, which must be at least 512 MB.

Review the log files to find more-specific reasons for the failure. Start by reviewing the OUI logs in the Central Inventory logs folder. See Central Inventory Logs.

Configuration Error Messages

Note:

For troubleshooting purposes, perform configuration tasks individually for one product or component at a time.

  • Issue: Configuration fails, or you receive error messages during configuration.

    Solution: Review the configtool_summary.log file in EPM_ORACLE_INSTANCE/diagnotics/logs/config.

  • Issue: This error message is added to configtool.log file in EPM_ORACLE_INSTANCE/diagnotics/logs/config when Oracle Database is configured for the first time:

    ORA-00917: missing comma

    This error can occur if the database is configured with the US7ASCII database character set.

    Solution: Recreate the database with the UTF-8 character set or another character set that has Unrestricted Multilingual Support. EPM System Release 11.1.3 supports only such character sets, as documented in Oracle Enterprise Performance Management System Installation and Configuration Guide.

Configuration Task Panel: Missing Products

Issue: A component or product is not displayed on the Configuration Task panel. This behavior can happen with an incomplete installation.

Solution: Review installTool-install log and product-install.log in EPM_ORACLE_HOME/diagnostics/logs/install to see if any component was not completely installed.

Unavailable Database Configuration Options

Issue: The options on the Database Configuration panel are unavailable.

Solution: Ensure that you are configuring the system with the same user account that was used for the installation.

Remote Deployment Timeout

Issue: Remote deployment of a Java web application fails, and EPM_ORACLE_INSTANCE/diagnostics/logs/config/configtool.log shows this exception: The action you performed timed out after 60,000 milliseconds.

Solution: Follow these steps:

  1. Create a file EPM_ORACLE_HOME/common/config/11.1.2.0/configTool-options.properties that includes this line:

    deployment.remote.timeout=timeout in milliseconds

    For example, deployment.remote.timeout=300000 specifies a timeout after 5 minutes (300,000 milliseconds).

  2. Redeploy the Java web application.

Failure Deploying to Application Server Without Configuration Errors

Issue: A product is not deployed to the application server, but there are no configuration errors.

Solution: Review configtool.log in EPM_ORACLE_INSTANCE/diagnostics/logs/config. This file records any errors in the deployment process. If no errors are identified, redeploy to the application server.

Moving Java Web Applications to a Single Domain

Issue: EPM System Java web applications are deployed to different WebLogic Server domains, and you want to move them to a single domain for better management and monitoring.

Note:

All EPM System products should be deployed to one domain. See the Oracle Enterprise Performance Management System Installation and Configuration Guide.

Solution: Use one of these procedures:

  • If the domain for Foundation Services works correctly, deploy all EPM System Java web applications to that domain:

    1. Run the WebLogic Server Administration Server on the Foundation Services machine for the domain.

    2. Redeploy the Java web applications that are deployed to domains other than the Foundation Services domain.

      In EPM System Configurator, select Deploy web applications to an existing domain, and then enter the host, port, and domain name for the Foundation Services machine.

    3. Redeploy any Java web applications on the Foundation Services machine that were already deployed on that machine.

  • To deploy all EPM System Java web applications to a new domain:

    1. Use the WebLogic Server Configuration Wizard to create a basic domain.

    2. Start WebLogic Server Administration Server for the new domain.

    3. Redeploy the Java web applications that were deployed on machines other than the Foundation Services machine.

      In EPM System Configurator, select Deploy web applications to an existing domain, and then enter the host, port, and domain name for the new domain.

    4. Redeploy any Java web applications on the Foundation Services machine to the new domain.