Configure dimension server is failed in EPMA Configuration

In this page we are going to see how to resolve the configuration dimension server failed issue while configuring the EPMA Component in EPM 11.1.2.4

Note : We get this issue if we use MS SQL Express edition as a source for Hyperion 

Please check the diagnostics logs as below

Navigation : Start- AllProgramms-OracleEPM System-FoundationServices - EPMSystem Daignostics

FAILED DimEditorLoadAdf Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_35/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.DimEditorLoadAdf
Error: DimEditorLoadAdf failed on initialization. Please check all registry information is valid and that HSS is running. 

Recommended Action: Make sure external checker is working.

FAILED EnumApplications Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_35/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumApplications
Error: EnumApplications failed on initialization. Please check all registry information is valid and that HSS is running.
Recommended Action: Make sure external checker is working.

FAILED EnumDataSyncs Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_35/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.repository.EnumDataSyncs
Error: EnumDataSyncs failed on initialization. Please check all registry information is valid and that HSS is running. 

Recommended Action: Make sure external checker is working.

FAILED EnumDimensions Launch external checker with next command: C:\Oracle\Middleware\EPMSystem11R1\..\jdk160_35/bin/java -DEPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1 -DEPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1 -Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration -Doracle.core.ojdl.logging.config.file=C:\Oracle\Middleware\user_projects\epmsystem1\config\validation\11.1.2.0\validationTool-logging.xml com.oracle.epm.epma.config.validations.dimeditor.EnumDimensions
Error: EnumDimensions failed on initialization. Please check all registry information is valid and that HSS is running. 

Recommended Action: Make sure external checker is working. 

Please change the TCP/IP Port to 1433 as SQL Express Database is running on that port as shown below 

How to resolve Fragmentation in Essbase

 What is Fragmentation?

Fragmentation is unused disk space

 When does Fragmentation occur?

Fragmentation is likely to occur with the following

Read/write databases that users are constantly updating with data

Databases that execute calculations around the clock

Databases that frequently update and recalculate dense members

Data loads that are poorly design

Databases that contain a significant number of Dynamic Calc and Store members

Databases that use an isolation level of uncommitted access with commit block set to zero

 How can you measure fragmentation?

You can measure fragmentation using the average clustering ratio or average fragmentation Quotient.

Using the average fragmentation quotient

Any quotient above the high end of the range indicates that reducing fragmentation may help

performance, with the following qualifications:

The reported value of the Fragmentation Quotient is more accurate when there are no other write

transactions running on the database.

For databases less than 50 MB using the Direct I/O access mode, the fragmentation quotient tends to

 be high. A high fragmentation quotient does not necessarily indicate a need to

 reduce fragmentation, because the free space is created in 8 MB chunks and all of it might not 

get used right away.

Database Size	Fragmentation Quotient Threshold
Small (up to 200 MB)	60% or higher
Medium (up to 2 GB)	40% or higher
Large (greater than 2 GB)	30% or higher

Using the average clustering ratio:

The average clustering ratio database statistic indicates the fragmentation   

level of the data (.pag) files. The maximum value, 1, indicates no fragmentation.

 How do you can prevent and remove fragmentation?

You can prevent and remove fragmentation:

To prevent fragmentation, optimize data loads by sorting load records based upon

sparse dimension members. For a comprehensive discussion of optimizing data load by                                             grouping sparse members.

To remove fragmentation, perform an export of the database, delete all data in the database

with CLEARDATA, and reload the export file.

To remove fragmentation, force a dense restructure of the database.

Shared Services MSAD Configuration setup

In this page we are going to see an usual activity which we perform when the client users are facing an issue to login into the Hyperion Applications.

We are going to see how to setup an MSAD Configuration in HSS

Shared Services- MSAD Configuration

Screen 1:

Screen 2:

 

Shared Services- MSAD Configuration

You can configure MSAD so that Shared Services can perform a static host name lookup or DNS lookup to identify MSAD. Static host name lookup does not support MSAD failover without updating the MSAD configuration in Shared Services.

Using the DNS lookup ensures high availability of MSAD in scenarios where MSAD is configured on multiple domain controllers to ensure high availability. When configured to perform a DNS lookup, Shared Services queries the DNS server to identify registered domain controllers, and connects to the domain controller with the greatest weight. If the domain controller to which Shared Services is connected fails, Shared Services dynamically switches to the next available domain controller with the greatest weight.

Global Catalogue

A global catalog is a domain controller that stores a copy of all MSAD objects in a forest. It stores a complete copy of all objects in the directory for its host domain and a partial copy of all objects for all other domains in the forest, which are used in typical user search operations.

Note: Also refer to Microsoft Docs for how to configure a Global Catalogue

Methods to configure your MSAD user directories while using a “Global Catalogue”.

·        Configure the global catalog server as the external user directory (recommended)

·        Configure each MSAD domain as a separate external user directory

Note: Configuring the global catalog instead of individual MSAD domains allows EPM System products to access local and universal groups within the forest.

Individual Parameters to be entered in the above screens is explained below.

Steps in configuration of MSAD to a HSS :-

1) Host Name

Name of the user directory server. Use the fully qualified domain name if the user directory is to be used to support SSO from Site Minder

2) DNS Lookup or Hostname options

Note:

DNS Lookup - Do not select this option if you are configuring a global catalog.

Hostname - Use this option to enable static host name lookup

3) Port

The port number where the user directory is running.

Note: If you are configuring an MSAD global catalog, specify the port used by the

Global catalog server (default is 3268)

4) SSL Enabled

The check box that enables Secure Socket Layer (SSL) communication with this user

directory. The user directory must be configured for secure communication.

5) Base DN

The distinguished name (DN) of the node where the search for users and groups should begin. You can also use the Fetch DNs button to list available base DNs and then select the appropriate base DN from the list.

Note: If you are configuring a global catalog, specify the base DN of the forest.

6) ID Attribute

A unique user attribute. The recommended value of this attribute is automatically set

For MSAD (ObjectGUID). You may change the default value if necessary.

7) Maximum Size

Maximum number of results that a search can return. If this value is greater than that

supported by the user directory settings, the user directory value overrides this value.

For MSAD, set this value to 0 to retrieve all users and groups that meet the search

Criteria.

8) Trusted

The check box to indicate that this provider is a trusted SSO source. SSO tokens from

trusted sources do not contain the user's password.

9) Anonymous Bind

The check box to indicate that Shared Services can bind anonymously to the user

Directory

Note: Oracle recommends that you do not use anonymous bind.

10) User DN

The distinguished name of the user that Shared Services should use to bind with the

User directory. This distinguished name must have read privileges within the Base DN.

Special characters are not allowed in the User DN value.

Example: cn=admin,dc=example,dc=com

11)Append Base DN

The check box for appending the base DN to the User DN. If you are using Directory

Manager account as the User DN, do not append Base DN.

12)Password

   User DN password

13) CLICKNEXT

The User Configuration screen opens. Shared Services uses the properties set in this screen to

create a user URL that is used to determine the node where search for users begins. Using this

URL speeds up the search.

Caution

User URL should not point to an alias. EPM System security requires that the user URL points to an actual user and not its alias.

Oracle recommends that you use the Auto Configure area of the screen to retrieve the required information.

Test:

------

1)      Edit the Configured MSAD from Shared Services à Administration à Configure User Directories.

2)      Click on Test to test the MAD Connection

3)      Query for any existing user from the configured MSAD to check if the interface of HSS to MAD is available.

Please read this and let me know if you have any questions ...

Validating Hyperion Web Applications

Hi,

In this page we are going to see how we used to validate the Hyperion components using an URL 

We should able to access all the components w.r.t the URL and its respective port number,If we are unable to access the Web URL we should check the Hyperion services status in services.msc 

Logs Location :

Daignostics logs : " Oracle/middleware/user projects/epmsystem1/bin/diagnostics/logs"

Server Logs :  " Oracle/Middleware/user_projects/domains/EPMSystem/servers "

1)      Pre requisites for Health Check

Below are the software’s needed to perform this Health check

Java Version      :  Java 6 or less

Browser               :  IE 9 or less

MS Office            :  Office 2013 or less

Smart view         :  11.1.2.5.610 or less

2)      Validate Workspace is up and running

This test validates that users can log into the Workspace and Reporting and shared services, this would indicate that all critical services are running. This should be the first test to determine if the application is functioning. If any errors occur here more diagnostics are needed to determine what is wrong.

Environment	URL
Training Envt	http://servername:19000/workspace/

 Log into the Workspace application with your corporate credentials

Navigate ->Administer ->Reporting and Analysis ->Services (Green mark indicates in below screen services are up and running)

Navigate ->Explore

Navigate ->Administer ->Shared Services Console

4) Validating Essbase Administration Services (EAS)

Environment	URL
DEV	http://servername:10080/easconsole/console.html

Click on Launch and login with your user details

Here we are using "admin" details

Validating the Applications and its databases by expanding the Essbase server a below

5) Validating Smart View Shared Connection (Provider services)

Environment	URL
DEV	http://servername:13080/aps/SmartView

6) Smart View Connectivity Validation:

Url to connect to the Hyperion Applications using Smart View :

    "http://servername:19000/workspace/SmartViewProviders"

7) Validating Financial Reporting

Environment	URL
DEV	http://servername:8200/hr/status.jsp

Validating the FR Services