After Installing SmartView 11.1.2.5, Excel 2013 Does Not Start

Hi,

Came across one of the issues that after installing Smart View 11.1.2.5, Excel 2013 not starting. However, Excel does start by selecting an existing spreadsheet or new sheet.

To Fix this –

In Excel uncheck the option ‘Show the Start Screen when this application starts’

1. In Excel Menu, click File > Options
2. Under Start up options, uncheck ‘Show the Start screen when this application starts’ box.
3. Close Excel.
4. Open Smart View and proceed working on spread sheet.

Thanks,

~KKT~

How to Configure an Existing EPM 11.1.2.4 With Java 7

To configure an existing EPM 11.1.2.4 Environment to use Java 7.  This document applies to all EPM Products.  If your product is not specifically mentioned, then it probably does not require any additional steps besides those mentioned in the provided solution.

This document is for both Unix and Windows and assumes that you already have a working EPM 11.1.2.4 environment. Reconfiguring EPM to use Java7 is a manual process. Java7 replaces both jdk1.6 and jrocket1.6.  There are two ways to upgrade EPM to use Java 7.  Each has its own caveats.

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

The paths shown are for Windows. Just change the slashes if you are on Unix.

Preparing for Java 7

1. Create a folder in the Middleware directory called Java6 and move both the jdk160_35 and jrockit_160_37 to the Java6 directory.
2. 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, which resulted in the creation of F:\Oracle\Middleware\jdk1.7.0_161.  You can use any version of Java 7 your wish.

After completion of the above steps, you have two choices for configuration of EPM 11.1.2.4 to use Java 7

Choice One – The Easier Way

This method creates links in the Oracle\Middleware directory so that any reference to jdk160_35 and jrockit_160_37 goes to jdk1.7.0_161.  The upside for this approach is that you do not have as many modifications to make to the various EPM configuration files that reference jdk160_35 and jrockit_160_37.  Any reference to jdk160_35 and jrockit_160_37 will go to Java 7.  If you upgrade to a later patch level of Java7 at a later time, you will not have to make any modifications except for recreating the links.  The only downside is that when you get a listing from task manager or via the Unix PS command it will appear that you are still running Java 6.

1. Create a links in the Middleware directory so that both Oracle/Middleware/jdk160_35 and Oracle/Middleware/jrockit_160_37 both refer to jdk1.7.0_161

On Windows:
a. From a cmd prompt change directory to Drive:\Oracle\Middleware and execute the following two commands:
mklink /D jdk160_35 jdk1.7.0_161
mklink /D jrockit_160_37 jdk1.7.0_161
b. Change Directory to F:\Oracle\Middleware\jdk1.7.0_161\jre\bin and execute the following command:
mklink /D jrockit server

On Unix:
a. From a shell prompt change directory to /Oracle/Middleware and execute the following two commands:
ln -s jdk1.7.0_161 jdk160_35
ln -s jdk1.7.0_161 jrockit_160_37

2. For both Windows and Unix, Change directory to /Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts and backup all scripts.  Modify each of the setCustomParamsProduct.sh scripts and add the -XX:+UnlockCommercialFeatures option before the existing -XX:-FlightRecorder parameter.  In Java 7 you need to add the -XX:+UnlockCommercialFeatures parameter in order to use FlightRecorder.
Failure to add the new option may result in your WebLogic Web Apps failing to start.

3. The following steps are necessary to run the WebLogic Admin Server and to be able to start an App via the startManagedWebLogic.cmd script.  All Windows Services should already be functional at this point.

Change directory to F:\Oracle\Middleware\user_projects\domains\EPMSystem\bin

a. Windows ONLY – Make a backup of the startWebLogic.cmd file and then make the following modification:
Add the line set JAVA_VM=-server directly below the line that reads @REM START WEBLOGIC

@REM START WEBLOGIC
set JAVA_VM=-server

b. Windows ONLY – Make a backup of the setDomainEnv.cmd file and then make the following modification:
Change: set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=F:\Oracle\Middleware\oracle_common -Djava.awt.headless=true
To:  set EXTRA_JAVA_PROPERTIES=-XX:PermSize=64m -XX:MaxPermSize=256m %EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=F:\Oracle\Middleware\oracle_common -Djava.awt.headless=true

c.  Make a backup of the setEpmEnv.cmd (Windows) or setEmpEnv.sh (Unix) file and then make the following modification:
Change: set JAVA_OPTIONS=%JAVA_OPTIONS%
To: set JAVA_OPTIONS=-XX:+UnlockCommercialFeatures -XX:-FlightRecorder %JAVA_OPTIONS%

4. Windows ONLY – Make a backup of startManagedWeblogic.cmd and then make the following modification:
Uncomment this line:   @REM Set JAVA_VM=-server
Comment this line: set JAVA_VM

5. Start all services and Test

If using EAL and or FCM see steps 11 & 12 below.

If you have a compact Web Logic Deployment see possible issues and solutions at end of this document.

Choice Two – Changing EPM configuration files that reference Java

This approach requires several file modifications to EPM configuration files.  This method does not use links which means you have to replace all occurrences of jdk160_35 and jrockit_160_37 in the files where they are referenced. The upside to this approach is that when you get a listing from task manager or via the Unix PS command, you will see that you are running Java 7.  The downside is that there are quite few changes that would have to be made each time you upgrade Java7 to a later version.

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

2. Change Directory to F:\Oracle\Middleware\user_projects\domains\EPMSystem\bin
a. Backup the setDomainEnv.cmd (Windows) or setDomainEnv.sh (Unix) file and then change all occurrences of jrockit_160_37 to jdk1.7.0_161
b. Backup the setEpmEnv.cmd (Windows) or setEmpEnv.sh (Unix) file and then make the following modification:
Change: set JAVA_OPTIONS=%JAVA_OPTIONS%
To: set JAVA_OPTIONS=-XX:+UnlockCommercialFeatures -XX:-FlightRecorder %JAVA_OPTIONS%

3. Windows Only – Backup the Hyperion Solutions Branch of the Windows Registry via the regedit command

4. Windows Only – Update the Windows Registry via the regedit.  For ALL EPM Services under HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions
a. Change the JavaDLL to F:\Oracle\Middleware\jdk1.7.0_161\jre\bin\server\jvm.dll
b. Identify the JVMOption that starts with -Djava.class.path= and then locate and change jrockit_160_37\lib\tools.jar to jdk1.7.0_161\lib\tools.jar
c. Identify the JVMOption that starts with -Djava.library.path= and then locate and change jrockit_160_37\jre\bin to jdk1.7.0_161\jre\bin

5. Change directory to /Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts and backup all scripts.  Modify each of the setCustomParamsProduct.sh scripts and add the -XX:+UnlockCommercialFeatures option before the existing -XX:-FlightRecorder parameter. In Java 7 you need to add the -XX:+UnlockCommercialFeatures parameter in order to use FlightRecorder.
Failure to add the new option -XX:+UnlockCommercialFeatures may result in your WebLogic Web Apps failing to start.

6. Windows Only – The following step is necessary to run the WebLogic Admin Server.

Change directory to F:\Oracle\Middleware\user_projects\domains\EPMSystem\bin

a. Make a backup of the startWebLogic.cmd file and then make the following modification:
Add the line set JAVA_VM=-server directly below the line that reads @REM START WEBLOGIC

@REM START WEBLOGIC
set JAVA_VM=-server

7. Windows ONLY – Make a backup of startManagedWeblogic.cmd and then make the following modification:
Uncomment this line:   @REM Set JAVA_VM=-server
Comment this line: set JAVA_VM

8. Update the JAVA_HOME values in the following file.
Linux/Unix: /Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh                           Change JAVA_HOME=”../Oracle/Middleware/jrockit_160_37″ TO JAVA_HOME=”../Oracle/Middleware/jdk1.7.0_161″
Windows: DRIVE:\Oracle\Middleware\wlserver_10.3\common\bin\commEnv.cmd                Change set JAVA_HOME=D:\Oracle\Middleware\jrockit_160_37 TO set JAVA_HOME=D:\Oracle\Middleware\jdk1.7.0_161

Note that the commEnv.sh(cmd) file is used during java application redeployment

9. For Essbase –
a. Change directory to F:\Oracle\Middleware\user_projects\epmsystem1\config\OPMN\opmn and backup the opmn.xml file. Open the opmn.xml file and change the one occurrence of jdk160_35 to jdk1.7.0_161
b. Change directory to F:\Oracle\Middleware\EPMSystem11R1\opmn\bin and backup the opmnctl and opmnctl.tmplt files.  Modify the opmnctl and opmnctl.tmplt files changing two occurrences of jdk160_35 to jdk1.7.0_161 in each file.
c. Unix only – Backup the opmnctl file in /Oracle/Middleware/user_projects/epmsystem1/bin.  Edit the opmnctl file in this location changing two occurrences of jdk160_35 to jdk1.7.0_161
d. By default Essbase gets the location of Java from OPMN, but you should modify the references to Java in the essbase.cfg and setEssbaseEnv.sh anyway.
Change Directory to F:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin and backup both the the essbase.cfg and setEssbaseEnv.bat file.  Change jdk160_35 to java1.7.0_161 in both files

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

11.  For EPMA Server – Modify the Path to the jvm.dll in F:\oracle\Middleware\user_projects\epmsystem1\config\EPMA\BPMA_Server_Config.xml

Change From: <JvmPath>%EPM_ORACLE_HOME%\..\jdk160_35\jre\bin\server\jvm.dll</JvmPath>
Change To:     <JvmPath>%EPM_ORACLE_HOME%\..\jdk1.7.0_161\jre\bin\server\jvm.dll</JvmPath>

12. For EAL – If you have EAL AnalyticsLink installed on the machine you should continue to use Java 6 for the EAL Analytics Link Service Only as Java 7 is not supported on EAL <Doc Id 2529126.1>

13. For FCM – SOA is still in use for FCM Task Scheduling and Automation. If you do not update the setSOADomainEnv.cmd when changing to JDK 7, then “java.lang.OutOfMemoryError: PermGen space” may occur when starting soa_server1. The steps to address the error are as follows:

a) Go to X:\Oracle\Middleware\user_projects\domains\EPMSystem\bin
b) Create a backup copy the existing setSOADomainEnv.cmd file
c) Edit the current setSOADomainEnv.cmd file to include -XX:PermSize=256m -XX:MaxPermSize=768m for line with EXTRA_JAVA_PROPERTIES as follows:
set EXTRA_JAVA_PROPERTIES=-XX:PermSize=256m -XX:MaxPermSize=768m %EXTRA_JAVA_PROPERTIES% -da:org.apache.xmlbeans…
d) Remove the -XXcompressedRefs:enable=false parameter from the same file

14. 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

15. Start all services and Test

Additional Information:  Step 5 for Windows would have to be repeated each time you apply a patch that updates the JavaDLL.  Step 6 for both Windows and Unix would have to be repeated each time you apply a patch that requires that you redeploy as this typically updates the setCustomParams for that Web Application.  Step 1 -11 would need to be repeated if you upgrade to a later version of Java 7.

Possible Issues and Solutions:

• If you are on Unix and have a compact WebLogic Deployment you must remove the parameter -XXcompressedRefs:size=32GB from the /Oracle/Middleware/user_projects/epmsystem1/bin/deploymentScripts/setCustomParamsEPMServer.sh file or else EPMServer0 will fail to start.
• If you have configured SOA to start as windows service, replace the existing CmdLine parameters (Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services) in the Windows Registry for the SOA Service with the following parameters:

  1. change -jrockit to -server
  2. change Xms and Xmx and add Maxpermsize minimum to -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=768m

  The resulting start of the CMDLINE is: -server -Xms768m -Xmx1536m -XX:PermSize=256m -XX:MaxPermSize=768m

  Note: If you still have issues starting your SOA Service you may just have to recreate it using the following KM (Doc Id 1415946.1)

• If you have configured the WebLogic Admin to start as a windows service, replace the CmdLine (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services) in the Windows Registry for the WL Admin Service with the following parameters:

  1. change -jrockit to -server
  2. change Xms and Xmx and add Maxpermsize minimum to  -Xms1024m -Xmx2048m -XX:MaxPermSize=512m
  3. Add  -XX:+UnlockCommercialFeatures

  The resulting start of the CMDLINE is: -server -Xms1024m -Xmx2048m -XX:MaxPermSize=512m -Dweblogic.ProductionModeEnabled=true -XX:+UnlockCommercialFeatures -XX:-FlightRecorder

  Note:  If you still have issues starting your WebLogic Admin Service you may just have to recreate it using the following KM (Doc Id 1415946.1)

• Regarding EAS Console browser access on a windows server:

  Normally users run the EAS client from a browser on a client machine, not on the server.  That said, if you wish to run the EAS console via a browser on the server, I suggest installing another version of jre1.7 in the default C:\Program Files (x86)\Java location.  Note that you should install an earlier version of the jre.  As of 7u161 and 6u171, Java SE 7 and Java SE 6 No Longer Contain Deployment Technology.   This means it does not include javaws which the EAS client needs to run.

• Additional step if SSL is used and SSL certs were imported to the previous Jrockit/JDK keystores.  Remember to import the certificate(s) into the Java 7 keystore.

 

Thanks,

~KKT~

How to configure Essbase 11.1.2.4 to work with the IBM Netezza driver

To configure Essbase to connect to an IBM Data warehouse via the Netezza driver, follow the next steps.

1. Ensure the odbc.ini in the /Oracle/Middleware/EPMSystem11R1/common/ODBC-64/Merant/7.1 location exist with the proper information to the Netezza driver (i.e. /opt/nz/lib64/libnzodbc.so)

— Filename: odbc.ini —
[ODBC Data Sources]
NZSQL=NetezzaSQL

[NZSQL]
Driver=/opt/nz/lib64/libnzodbc.so
Description=NetezzaSQL
Servername=<SERVERNAME>
Port=<PORT>
Database=<DB-NAME>
Username=<USERID>
Password=
ReadOnly=false
FastSelect=false
ShowSystemTables=false
LegacySQLTables=false
LoginTimeout=0
QueryTimeout=0
DateFormat=1
NumericAsChar=false
SQLBitOneZero=false
StripCRLF=false
securityLevel=preferredUnSecured
caCertFile=

[ODBC]
IANAAppCodePage=4
InstallDir=/Oracle/Middleware/EPMSystem11R1/common/ODBC-64/Merant/7.1
Trace=0
TraceFile=odbctrace.out
TraceDll=/Oracle/Middleware/EPMSystem11R1/common/ODBC-64/Merant/7.1/lib/ARtrc27.so

2. Ensure the odbcinst.ini in the /Oracle/Middleware/EPMSystem11R1/common/ODBC-64/Merant/7.1 location exist with the proper information to the Netezza driver (i.e. /opt/nz/lib64/libnzodbc.so)

— Filename: odbcinst.ini —
[ODBC Drivers]
NetezzaSQL=Installed

[Administrator]
HelpRootDirectory=/Oracle/Middleware/EPMSystem11R1/common/ODBC-64/Merant/7.1/adminhelp

[NetezzaSQL]
Driver=/opt/nz/lib64/libnzodbc.so
Setup=/opt/nz/lib64/libnzodbc.so
APILevel=1
ConnectFunctions=YYN
DriverODBCVer=03.51
DebugLogging=false
LogPath=/tmp
UnicodeTranslationOption=utf8
CharacterTranslationOption=all
PreFetch=256
Socket=16384

3. Ensure the OPMN.xml in the /Oracle/Middleware/user_projects/epmesystem1/config/OPMN/opmn has the following 2 new entries, usually added after the last LD_LIBRARY_PATH variable entry in the file:

— Filename: opmn.xml —
## Netezza Driver Location ##
<variable append=”true” id=”LD_LIBRARY_PATH” value=”/opt/nz/lib64″/>

## Netezza ODBC INI location pointing to the ODBC-64/Merant/7.1 location ##
<variable id=”NZ_ODBC_INI_PATH” value=”$EPM_ORACLE_HOME/common/ODBC-64/Merant/7.1″/>

4. Create a text file called esssql.cfg in the $ARBORPATH/bin, with the following information

— Filename: esssql.cfg —
[
Description “NetezzaSQL”
DriverName libnzodbc
UpperCaseConnection 0
UserId 1
Password 1
Database 1
SingleConnection 0
IsQEDriver 0
ConvertUTF16toUTF8 0
]

NOTE: No symbolic links should be created between the $USER_HOME and the Merant directory not between the $USER_HOME and $ARBORPATH/bin. All the information is provided via the OPMN.xml variables.

5. Restart the Essbase service

6. Login to Essbase via EAS

7. Open an existing rule file or a new one (EAS > File > New > Script > Rules > OK)

8. Once the Data Prep Editor is opened, Go to File > Open SQL > Application + Database names > OK

9. On the Open SQL Data Sources window, select the “SQL data sources” radio button and pick the name of the Netezza data source from the drop-down list (i.e. NZSQL)

10. Configure the Select, From and Where panels with the corresponding information, click OK/Retrieve

11. Provide the Netezza server name and password, click OK

12. Wait some time for the query to return. Some customers have spent up to 15 minutes depending on the complexity of the sql statement.

Thanks,

~KKT~

How To Connect To an Essbase v11.1.2.x Cluster via MaxL, ESSCMD or Planning?

Connect using single Analytic Provider Services (APS) URL node or VIP of load balanced APS environment:

MaxL:

login admin password on “http://<HOST_NAME_OR_VIP&gt;:<PORT>/aps/Essbase?ClusterName=<ESSBASECLUSTER>”;

ESSCMD:

login “http://<HOST_NAME_OR_VIP&gt;:<PORT>/aps/Essbase?ClusterName=<ESSBASECLUSTER>” admin password;

To connect using EssbaseCluster,  the Essbase server(s) in the cluster need to be resolved using the APS resolver entries:

1.  Add the following line to the essbase.cfg on the Essbase Server:

ApsResolver http://<APS_SERVERNAME&gt;:13080/aps

2. On the APS server, add the following line to the <user_projects>\<epmsystem instance>\aps\bin\essbase.properties:

ApsResolver=http://<APS_SERVERNAME>:13080/aps

3.  Restart both the Essbase Server and the APS Server.

Note:  If the Essbase Client is on a different server, you will need to add the essbase.cfg with the apsresolver entry in the ARBORPATH/bin folder.

Connect using one of the following:

MaxL:

MAXL> login <USERNAME> <PASSWORD> on <ESSBASESERVER_NAME>;

ESSCMD:

login <ESSBASE_SERVERNAME> <USERNAME> <PASSWORD>;

Thanks

~KKT~

Improving Performance Of Hyperion Planning

There are three things you can do to improve the performance of the Planning application.

I. Increase the Java heap size

You can increase the heap to a maximum of 1Gb (1024Mb). If you have the available RAM to dedicate to Planning, it is recommended to increase both the minimum (Xms) and maximum (Xmx) heap size to 1024Mb. Inceasing the minimum heap size will help because it lowers the overhead needed to manage garbage collection in a dynamically expanding heap. The step by step procedure for modifying the Java heap size varies from one web application server to another. Contact your web application administrator for assistance.

II. Turn off process management for Version and Scenario members for which it is not needed

By default, new Scenario and Version members are enabled for process management. Each Entity-Scenario-Version combination (each Planning unit) costs resources because Planning must check who currently owns the Planning unit and check the security settings. If you have many Scenarios and Versions the number of combinations increases rapidly.

Decide what Versions and Scenarios need to be available for process management, and then disable the others. If you are not using process management at all then you can disable process management support for all Version and Scenario members. To disable process management support, edit a member of the Scenario or Version dimension. In the member properties, uncheck the “Enable for process management” checkbox. Repeat for each member you want to disable process management for. When finished, do a database refresh using the Administration> Manage Database page and restart the Planning service.

III. Optimize the design of web forms

Large web forms impose by far the heaviest load on the Planning JVM. Optimizing the design of forms can make a big difference to how fast a form opens and how many users can open it concurrently. Web form design is a complex area.

Refer earlier post

Thanks,

~KKT~

Designing Hyperion Planning data forms

Recommended Design

• Keep dense dimensions in rows and columns.
• Place sparse dimensions in the Page and Point of View (POV).
• Place static dimensions in POV and hide these dimensions where not relevant to the form.
• Place Scenario, Version, and Year dimensions in the Page wherever possible.
• Use dynamic user variables and substitution variables as much as possible.
• Use Run on Save and Run on Load for business rules on data forms only where business rules can complete execution within a short timeframe (say less than 30 sec.). All other business rules should be set to launch manually.
• For Planning release 9.3.1 and later, set long-running business rules to run in the background. See the Hyperion Planning Administrator’s Guide for details on these settings.
• Limit composite data forms to two data forms where possible
• Use the Suppress Missing Data option to skip #MISSING values from resultant data forms.
• Split single larger data forms into multiple smaller data forms with fewer rows and columns.
• Minimize using account annotations on data forms.
• For Planning release 9.3 and later, enable the Mass Allocate feature on data forms only where absolutely necessary. This feature runs calculation scripts that can impact data values at intersections to which the end user may not have access.

Optimal Design Example

Rows: Account
Columns: Time Period
Page/POV: Entity and other dimensions

Sub-optimal Design Example

Rows: Entity
Columns: Year
Page/POV: Account, Time Period, and other dimensions

Performance Considerations

• The Run on Save and Run on Load calculation options place an additional demand on resources within the Essbase server for each save or load operation performed by end users. If it is necessary to use Run on Save or Run on Load, runtime prompts should be used to restrict the scope of the calculation and minimize the impact on users of the Essbase server.
• Review the Hyperion Planning Administrator’s Guide for steps that detail the execution of large calculations in batch mode. For example, you can set Planning properties to have business rules switch to background processing after a threshold that you configure. In addition, you can run business rules in batch mode using the options under Tools > Business Rules.
• When users access data form members that are dynamically calculated or have member formulas, an additional load is placed on the Essbase server. The impact is more acute during heavier user load.
• The biggest impact on data form performance is the grid size. Grid size consists of the number of rows, multiplied by the number of columns. The grid size doubles if an application uses multiple currencies.
• Adjust the number of cells retrieved to the memory on end users’ client machines. To determine the number of cells, multiply the number of rows by the number of columns.
• The Suppress Missing Blocks option for rows allows placing large sparse dimensions in rows, while providing good response time if the density of the query is low. Only blocks with data are retrieved. For example, when using this option, you can place an employee dimension consisting of thousands of members in the rows, and place the entity in the page or POV. Then, only employees of the selected entity are retrieved.
• Using Suppress Missing Data can improve performance. Before using this feature however it is recommended that you test the impact on performance.
• Using account annotations impacts performance. Use this option only if account annotations are required.
• If the Supporting Detail Detection Cache reaches 75% or higher, the cache size should be increased.
• Enabling shared member security impacts performance. Use this option only if you want the base member’s security to be based on its own security and that of all of its shared members. If this option is not enabled, users with access to the base member still have access to all of its shared members.
• The administrator should define data forms using dynamic user variables, to narrow the data form display to the dimensionality required by users. End users can set the value for the user variable in preferences. Review the Hyperion Planning Administrator’s Guide for these settings.
• For areas with low bandwidth, it is recommended that users access Planning data forms using Smart View for Office for faster response time.
• When Planning is first loaded, the first few requests to Planning can take longer because caches might not be loaded. It is recommended that an administrator or power user pre-load the most commonly used data forms before the general community uses the Planning server after each reboot to the Planning server.
• It is highly recommended that administrators conduct performance tests on data forms to ensure that they meet user expectations. Data forms should be tested in both single and multi-user environments before they are deployed to production.
• Data form definitions are cached when users log on to a Planning application. Because one cache is created for data form definitions, memory usage is not affected by the number of users viewing data forms. However, memory usage goes up if multiple users enter data in data forms at the same time.

 

Data Form Size Estimation

To get a rough estimate of data form size,  open the data form and select File > Save As from the browser. The size of the .HTML file is the portion of the data form that changes based on grid size. The .JS files remain the same size and can be cached, depending on browser settings. Information such as data form definitions, pages, and .gif files are not compressed when data forms are opened and sent to the Web browser.

About Suppression

Planning follows this basic sequence to suppress information in data forms, depending on suppression settings for Suppress Missing Blocks and Suppress Missing Data.

1. First, Planning evaluates the data form definition and creates a grid to send to Essbase.
2. If Suppress Missing Blocks is selected for data form rows:

a. Planning queries Essbase to determine which members in the data form definition have data blocks. This query typically takes only a few milliseconds. (This setting is most effective for sparse dimensions, and should not be used for dense dimensions.)
b. Planning then determines which members have data blocks available in Essbase, and filters out members for which the user does not have access permissions.

3. Next, Planning constructs a grid, and sends information to Essbase to fill in the data. (The constructed grid is generally very small, so the result is returned quickly from Essbase.)
4. If Suppress Missing Data is selected, Planning suppresses data for any #MISSING data element. (This operation generally occurs quickly. However, if a large volume of data is set to #MISSING, or blocks are created but have no data, this can take some time.)
5. Planning then queries the relational database, and marks every cell to show whether it has supporting details and cell text.
6. The Web data form is then presented to the user.

Thanks,

~KKT~

Smart View Error – “Invoked application hasn’t started up completely yet, do you want to wait?”

Dears,

I have this problem with so many users and finally found a solution to deal with this.

while launching Smart View using Internet Explorer browser, an error message may appear –
“Invoked application hasn’t started up completely yet, do you want to wait?”
1. Open Internet Explorer. Go to Tools > Internet Options > Click on Security Tab > Uncheck the option ‘Enable Protected Mode’
2. Click on Trusted Sites > Click on Sites button and Remove if your site is added already.
3. Turn off Pop Up blocker – Go to Tools > Internet Options > Privacy Tab > Uncheck the option Turn on Pop up blocker.

Kindly comment if this helps.

Thanks,

~KKT~

Smartview -Year and Quarter Data Spread To Months Is Not Working

We cannot spread numbers from year total or from quarters to month in Smartview
Some Machines do not have the issue at the SAME data intersection point, and it works fine for all of the users though Planning web, so form and members are setup properly.

In other cases Q1 & Q2 open and editable and NOT locked out.  When they log into another laptop & open the same form Q1 & Q2 are read only and locked.

If data is entered at the month, the year total or quarter does not automatically update.
If data is entered at the year total, the values are not spread to the months automatically.

This issue can be replicated in office 2010 and 2013 as well.  Smartview and excel options and versions are the same

Reason – Possible Recent installation or registry updates

Solution – Certain required files were not registered properly, for example hsspread.dll

If there was a difference between the way the two users INSTALLED the new Smart View software some files may not have been properly registered.

Maybe one user has restricted rights to the registry when installing
Maybe one user used “run as administrator”

Please compare installation steps and registry rights and try the installation again.

Consider using “run as administrator” if possible.

Feel free to message in case you face any issue.

 

Thanks,

~KKT~

How To Purge FDMEE Files – 11.1.2.4

Under FDMEE instance, there is data and outbox directory which is getting bigger (80GB). How do we clean up those directories? What is the standard process? There are some some other files such as .ind and .dat direxctly under FDMEE instance. How do we clean those up?

In-order to purge the FDMEE files, there is an option under “workflow” > Go to > Script Execution > Click on System Maintenance Tasks > there you have the scripts to Purge files.

These scripts run based on the application, you need to select the start and the end period along with the category.

This will help you to purge files.

Maintain Application Folder
======================

The Maintain Application Folder process purges files from the inbox, outbox, and data folders directory. Oracle Hyperion Financial Data Quality Management, Enterprise Edition accepts a separate Days to Keep parameter for each of the folders. If the value is not specified for a specific folder, FDMEE skips the folder.

In addition, FDMEE checks the inbox and outbox sub-directories under the respective folders and deletes any files. In the data, FDMEE skips the scripts directory because it holds customer scripts.

Maintain Process Table

This process maintains the following execution tables:

AIF_PROCESSES

AIF_PROCESS_DETAILS

AIF_PROCESS_LOGS

AIF_PROCESS_PARAMETERS

AIF_PROCESS_PERIODS

AIF_PROCESS_STEPS

AIF_BAL_RULE_LOADS

AIF_BAL_RULE_LOAD_PARAMS

AIF_BATCH_JOBS

AIF_BATCH_LOAD_AUDIT

AIF_TEMP

It accepts the number of days to keep as a parameter.

Thanks,

~KKT~

FDMEE Memory usage

How much memory should get consumed by FDMEE , is it only Xms and Xmx settings?

Xms and Xmx is settings for heap memory however the JVM still will consume memory for Non heap like Garbage collection,JIT optimization,…etc
So it is normal behavior to see FDMEE service consume more than Xmx,to set the correct value for Xmx you need to monitor you actual heap usage NOT allocation

Please start your admin server then
Go to :Oracle Enterprise Manager Fusion Middleware Control:
From a browser, type: http://servername:7001/em
Replace the “servername” with your WebLogic server name or IP address

1.From the Login to Oracle Fusion Middleware Control screen,enter the WebLogic administrator user name and password

2.Navigate to ErpIntegrator from the menus on the left, expand an item, and click the right arrow.
Click WebLogic Server, and then select Performance Summary
You can select the resource graphs to display by clicking Show Metric Palette button, and selecting the metrics by clicking
the appropriate check boxes

3. Monitor the Heap Usage , this will reflect what is actual used, monitor it for 1 week or more and check the Heap Usage during the job running so you can get a the real maxmim usage for Heap so you can allocate it correctly.

Thanks,

~KKT~