DRM error – Request Operation Sent to net.tcp://Server:port/oracle/drm/engine/jobmgr Did not Receive a Reply Within the Configured Timeout (01:00:00)

1. When running an export via the DRM batch client, the following error is seen:

Error received from DRM Process Manager service using address: net.tcp://server:port/Oracle/Drm/ProcessManager/: This request operation sent to net.tcp://server:port/Oracle/Drm/Engine/JobMgr did not receive a reply within the configured timeout (01:00:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.”

2. The export takes a long time to run.
3. The export saves the results of the export to a local file.

This problem is resolved in


1. Set up an external connection in the DRM Web Client from Administer > New > External Connection.
2. Modify your export to use the external connection rather than a local file.
3. Make sure that the following have not been configured as they could override the external connection that has been set for the export:
a. The ‘/outfile=’ flag has not been used in the command line export parameters for the batch client.
b. The ‘OutFile=’ parameter has not been used in the configuration file .
5. Run your export via the batch client again.



DRM Web Service Test Fails With Error: “‘PolicySet Invalid: WSM-06102’ But the Policy Does Exist”

Testing the DRM web service in Enterprise Manager fails with an error like the following where the referenced security policy is a valid policy:

oracle.sysman.em.SDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException: PolicySet Invalid: WSM-06102 PolicyReference The policy reference URI “oracle/wss11_saml_token_with_message_protection_client_policy” is not valid.

The security polices can be validated by accessing the following URL if wsm-pm has been deployed to the FoundationServices cluster, is using the default port and you are testing from the admin server machine:


Reason – The Oracle Web Service Policy Manager (wsm-pm application) may not be started or may not be able to be contacted.

To fix-

1. Ensure that the domain has been extended to include the Oracle WSM Policy Manager using the Weblogic Domain Configuration utility: C:\Oracle\Middleware\wlserver_10.3\common\bin\config.exe. If the domain has not been extended then extend the domain using the Weblogic Domain Configuration utility.

Check domain is extended for wsm-pm.

2. If #1 has been confirmed and there are still problems then ensure that the wsm-pm web application that has been used to secure the DRM web service has been started in the Weblogic Administration Console (http://server:7001/console) > Domain Structure > Deployments.

Check that wsm-pm is started.

3. Ensure that the server where the DRM web service has been deployed is a target for the wsm-pm web application (note: FoundationServices is in the screenshot below but the DRM web service may have been deployed somewhere else). To do this from the Weblogic administration console go to: Domain Structure > Deployments > wsm-pm > Targets > Current Targets.

Check that wsm-pm is correctly targeted.

4. If the location where the DRM web service has been deployed is not a target then click Lock & Edit (top left) > tick the box next to wsm-pm Enterprise Application > click Change Targets > tick the relevant location > click Yes > then Activate Changes (top right).


When Upgrading DRM Repository Error: “ORA-03114: not connected to ORACLE”

When copying the DRM repository with the repository wizard the following error is seen whilst ‘Applying updates …’ has been running for some time (i.e. not immediately):

ORA-03114: not connected to ORACLE

Reason – A network device may be dropping idle connections after a certain period of time.

In order to see if this is the issue that you are facing:

1. Note how long it takes before the ‘ORA-03114: not connected to ORACLE’ error is seen when upgrading the DRM repository.
2. Ask your DBA to locate the server side copy of sqlnet.ora and set the SQLNET.EXPIRE_TIME parameter to a value lower than the time taken for the ORA-03114 to appear.

For example:

1. If the ORA-03114 is being seen after 60 minutes and the SQLNET.EXPIRE_TIME parameter has been set to 60 minutes (SQLNET.EXPIRE_TIME = 60) or higher try a setting like this:

2. If the ORA-03114 is being seen after 60 minutes and the SQLNET.EXPIRE_TIME parameter is not present in the sqlnet.ora then this means that the default value of SQLNET.EXPIRE_TIME = 0 will be used. In this case add a row like the following to the sqlnet.ora

The main thing here is that SQLNET.EXPIRE_TIME is set to a lower value than the time taken for the ORA-03114 to be seen.


PBCS / EPBCS: How To Clear 0’s From an ASO Cube

When you run Push Data with a CLEAR DATA option, it will change values to 0 instead of #MISSING.  When you manually delete a value through Smart View or Forms, it will turn it into a 0 instead of #MISSING.

How to clear 0’s from ASO cube, how can 0’s be changed to #missing in ASO cube for PBCS or EPBCS application?

The solution is to Merge Data in the ASO cube:

1.  Launch Calculation Manager:  Navigate -> Create and Manage -> Rules.

2.  Go to Database Properties for the ASO cube:  Actions -> Database Properties.

3.  Expand ASO app, select ASO cube

4.  Merge Data:

Right-click ASO cube -> Merge Data -> All -> Remove cells with zero values
Right-click ASO cube -> Merge Data -> Incremental -> Remove cells with zero values

5. Confirm confirmation message



Increase Essbase Server Java heap size

During installation, EPM System Installer installs OPMN and registers Essbase Server for OPMN. OPMN manages the Essbase Agent, which manages the Essbase Server.

If OPMN is used to start Essbase, navigate to MIDDLEWARE_HOME\user_projects\epmsystem1\config\OPMN\opmn and set or update below two minimum and maximum heaps parameters in opmn.xml file under tag <process-type id=”EssbaseAgent” module-id=”ESS”> <environment>

<variable id=”ESS_CSS_JVM_OPTION6″ value=”-Xms256M”/>

<variable id=”ESS_CSS_JVM_OPTION7″ value=”-Xmx1024M”/>

If ESS_CSS_JVM_OPTION6 and ESS_CSS_JVM_OPTION7 is already in use, set this value for the next available ESS_CSS_JVM_OPTION. For example: ESS_CSS_JVM_OPTION9. The values are implementation specific.

If Essbase is started without using OPMN and use startup script i.e. startEssbase.bat | .sh then set above parameters (ESS_CSS_JVM_OPTION) in setEssbaseEnv.bat | .sh file.

After making these changes re-start Essbase Server.



How to Configure an Existing EPM With Java 7

To configure an existing EPM Environment to use Java 7

This document is written for both Unix and Windows and assumes that you already have a working EPM environment. Reconfiguring EPM to use Java7 is a manual process. Java7 will replace both jdk1.6 and jrocket1.6.

Note that is the only EPM version currently certified for Java7.

The paths shown are for Windows. Just change them accordingly for if you are on Unix.

1. Download the latest Java7 patch provided in the quarterly Critical Patch Update Advisory for your OS and install to F:\Oracle\Middleware

In this instance, Patch 26916855 from the Oracle Critical Patch Update Advisory – October 2017 was used

2. Change Directory to F:\Oracle\Middleware\EPMSystem11R1\common\config\ and backup the setJavaRuntime.(bat/sh) script. Then change all occurrences of jdk160_35 to jdk1.7.0_161

3. Change Directory to F:\Oracle\Middleware\user_projects\domains\EPMSystem\bin and backup the WebLogic setDomainEnv.(cmd/sh) script. Then change all occurrences of jrockit_160_37 to jdk1.7.0_161

4. Windows Only – Backup the Hyperion Solutions Branch of the Windows Registry

5. Windows Only – Update the Windows Registry via the regedit.

For ALL EPM Services Change the JavaDLL to F:\Oracle\Middleware\jdk1.7.0_161\jre\bin\server\jvm.dll

6. Change directory to /Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts and backup all scripts. Modify each of the setCustomParamsProduct.sh and remove the

“-XX:-FlightRecorder” option in each one. This option is not valid in Java7.

7. For Essbase – Change directory to F:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn and backup the opmn.xml file. Open the opmn.xml file change the one occurrence of jdk160_35 to jdk1.7.0_161

8. For Essbase – (This step may not be required in your environment). By default Essbase gets the location of Java from OPMN, but if you have modified your essbase.cfg and hardcoded the Java location, then you must make a change to the essbase.cfg.

Change Directory to F:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin. If the JvmModuleLocation is not proceeded by a semi colon then you must modify the java location changing jdk160_35 to java1.7.0_161

9. For Profitability – the option “-XXcompressedRefs:size=32GB” should be removed from the corresponding setCustomParams file.

10. Client Changes

EssbaseAdministration Console
Change Directory to F:\Oracle\Middleware\EPMSystem11R1\products\Essbase\eas\console\bin\admincon.bat
Modify the admincon.bat and change jdk160_35 to jdk170_161

Financial Reporting Client
Change Directory to F:\Oracle\Middleware\EPMSystem11R1\products\financialreporting\bin
Modify the setJavaRuntime.cmd script changing jdk160_35 to jdk170_161

11. Start all services and Test


DRM External Connection Using TNS Alias Name for Oracle DataBase failover

How to setup TNS alias name with DRM to use failover with Oracle Database?

* Navigate to the Instant Client ODP.NET DB driver located in DRM app server:

* Create a TNSNAMES.ORA file with the TNS ALIAS information

* During the External connection creation for Application in DRM Console, Select the Database as ‘Oracle’ and in the connection string specify the value as :
” Data Source = ”

* Test and verify the DB connection.


How to set up FDMEE on premise connection to Cloud through proxy

Steps to add JVM Options so that an FDMEE server can connect to Cloud environments via proxy.

First, make sure the server you are going to configure is able to ping the Cloud url.

1. Edit the setCustomParamErpIntegrator.bat/sh under


and add the following options to the JAVA_OPTIONS section:

-Dhttps.proxyHost=<Proxy Server> -Dhttps.proxyPort=<Proxy Port>


set JAVA_OPTIONS=-Dhyperion.home=C:\Oracle\Middleware\EPMSystem11R1 -DHYPERION_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Dlogging.folder=C:\Oracle\Middleware\user_projects\domains\EPMSystem/servers/ErpIntegrator0/logs/ -Dserver.name=ErpIntegrator0 -Dsun.net.inetaddr.ttl=0 -Djava.io.tmpdir=C:\Oracle\Middleware\user_projects\epmsystem1/tmp -Doracle.jdbc.useFetchSizeWithLongColumn=true -Xrs -XX:-FlightRecorder -DcomponentId=e0fc20b3237d72e8S2ea8412e157c18cf1c3S7ed8 -DESS_ES_HOME=C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseJavaAPI/ -DDOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\EPMSystem -Dcom.hyperion.planning.datamodel=64 -Djava.library.path=C:\Oracle\Middleware\EPMSystem11R1/products/FinancialDataQuality/lib/64-bit;C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseRTC-64/; -DPATH=C:\Oracle\Middleware\EPMSystem11R1/products/FinancialDataQuality/lib/64-bit;C:\Oracle\Middleware\EPMSystem11R1/common/EssbaseRTC-64/; -Dhttps.proxyHost=<Proxy Server>; -Dhttps.proxyPort=<Proxy Port> %JAVA_OPTIONS%

** Note that your proxy server and proxy port should be substituted for <Proxy Server> and <Proxy Port> **

2. If this is a windows server, you should add two more JVMOptions to the windows registry. First you must update the JVMOptionCount and increase the decimal value by 2. Then add new keys:


JVMOption51 -Dhttps.proxyHost=<Proxy Server>

JVMOption52 -Dhttps.proxyPort=<Proxy Port>


after adding the entries restart the FDMEE Server. Review ErpIntegrator.log to make sure the JVM properties are getting set. System will print all the options set.


FDMEE connection to Teradata setup

Follow the below steps –

++ Download the JDBC driver

In order to access the Teradata database, first need a compatible Teradata JDBC driver.

Download Jdbc drivers(TeraJDBC__indep_indep. from the Teradata download website. Without these drivers, the connector will not function correctly.


++ Deploy the JDBC driver files to the appropriate location. Steps are given below.

i) Extract/Copy the downloaded files:


ii) Copy above files into FDMEE Server and location could be under /oracle/Middleware/user_projects/domains/EPMSystem/lib

iii) Set LD_LIBRARY_PATH environment variable to the directory path where jar files were placed (/oracle/Middleware/user_projects/domains/EPMSystem/lib)

++ Stop/Start FDMEE Services


How to create a SmartView data source connection to Oracle Analytics Cloud – Essbase

After you install Oracle Smart View for Office, you can create connections to Oracle Analytics Cloud – Essbase.

Connections require information about the server and port. Your cloud service administrator should provide you with the information you need to create the connection. Use the quick connection method to create a private connection to the cloud service.

To create a private connection using the quick connection method:

1. In Excel, select the Smart View ribbon, and then click Panel.

2. On the Smart View Panel, click the arrow next to of the Switch to button Image of the Switch to button., and then select Private Connections from the list.

3. Still in the Smart View Panel, in the text box, enter the URL for the data source to which you want to connect.

4. Enter he URL syntax:

5. Click Go. or press Enter.

On the login window, enter your login credentials, and then select a data source from the drop-down menu.