Essbase – Where are Smart Slice File Locations Stored?


Smart View slice locations are stored in the EPM System registry database in the Analytic Provider Services (APS) section.

1.  Generate the EPM System registry report.  Run \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat/sh.

2.  Open the \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html file.

3.  Locate the PROVIDER_SERVICES_LWA (LOGICAL_WEB_APP) section.  Smart Slices are listed in the ‘Files’ section.  For example, NewSmartSlice1.xml and SSS.xml are the Smart Slices:

PROVIDER_SERVICES_LWA (LOGICAL_WEB_APP)

Files:
WorkspaceConfig
domain.db
essbase/EssbaseCluster-1/Demo/Basic/NewSmartSlice1.xml
 essbase/EssbaseCluster-1/Demo/Basic/SSS.xml

Essbase – Rounding function Differences Between 11.1.1.x and 11.1.2.3


The default behavior now is the C-Round function. Essbase had two earlier implementations of Round function. The first implementation was supported until v11.1.2.1, the second from v11.1.2.1 and v11.1.2.3.  Later releases switched to basic C-Round implementation.

There are provisions to support both the earlier implementations for those customers who may be using these implementations.

On Essbase 11.1.2.4, the @ROUND function now has a compatibility setting:

@ROUND (expression, numDigits [, compatibility])

Possible compatibility keyword values:

  • COMPATPREV11121—Original rounding algorithm, in use up until Release 11.1.2.1. The integer part of the number is used to generate the rounding margin of error. Limitation: aggregate values are only accurate up to the 15th decimal place.  Only some decimal numbers can be represented perfectly in binary. For example, if the value 1234.725 is loaded, it may be represented in binary as 1234.72499999999991. Using the COMPATPREV11121 algorithm to round this number to two decimal places returns 1234.72, though you may prefer 1234.73.
  • COMPATPREV11123—Alternate rounding algorithm, in use between Release 11.1.2.1 and 11.1.2.3, to negate the representational error discussed above. The rounding margin of error was changed for better precision, which in some cases returned different results than the original algorithm.

This has also been documented in the Essbase v11.1.2.4 Readme:

14191566 — Calculation. Data values may be different than expected because of rounding differences between older versions of Essbase and release 11.x. See the help topic for the @ROUND function in the Oracle Essbase Technical Reference, to optionally select a compatibility setting.

Thanks,

~KKT~

EPMA Application Deploy Button is Greyed Out – Deployment issues


Hi,

Changes have been made to an EPMA Planning application.  The EPMA Application status is “Out of Sync”, “Pending Deployment”. Running a “Compare” report to compare with the deployed application, shows the correct pending updates.

  1. In EPMA Application Library, right-click on the application and select ‘Run Diagnostics’ – run all the tests.
  2. Adjust the AWBConfig.properties (located in %MIDDLEWARE_HOME%\EPMSystem11R1\products\Foundation\BPMA\config\Webtier) and reduce the deploy timeout. The default is 8 hours (480), change it to 10 minutes.
  3. Restart EPMA Web.

I have been working with EPMA and faced deployment issue many times. Please feel free to contact me in case you face issues related to any deployment for Planning, Essbase (ASO, BSO), HPCM and HFM app.

Thanks,

~KKT~

How To Reset the ‘Administrator’ Password in OBIEE 10g, BI Publisher and BI Scheduler


You need to reset the ‘Administrator’ password for:

  • ‘OBIEE’
  • ‘BI Publisher’
  • ‘BI Scheduler’.

How can you do that?

  1. Start by creating a BI Publisher superuser.

    On both OBIEE and BI Publisher.

    Start username/password:    Administrator/Administrator
    After username/password    Administrator/admin3

    BI Publisher superuser username/password admin2/admin2

    Follow the exact steps below and create the same usernames and passwords to start off with.

    1. Take a back up copy of the xmlp-server-config.xml file (i.e. c:\OracleBI\xmlp\XMLP\Admin\Configuration\xmlp-server-config.xml).
    2. Log in to BI Publisher.
    3. Select Admin > Security Center > Security Configuration.
    4. Enable a Local Superuser called: admin2 with the password admin2.
    5. Click <Apply>.
    6. Restart OC4J.
    7. Sign in to BI Publisher as  admin2/admin2  This should log in successfully.
    8. Log in to OBIEE Admintool (Online) and change the Administrator password to ‘admin3’.
    9. Check in and save the changes.
    10. Log in to OBIEE Answers as Administrator/admin3.
    11. Change the ‘Administrator’ password under the ‘Security Model’ to ‘admin3’. Click <Apply>.
    12. Restart OC4J.
    13. Log in to BI Publisher as Administrator/admin3 This should log in successfully.
    14. Log in to OBIEE Answers as Administrator/admin3.
    15. Click on More Products > BI Publisher.
    16. This should go straight through to BI Publisher without prompting for a username and password.

    If the above method still fails attach your c:\OracleBI\xmlp\XMLP\Admin\Configuration\xmlp-server-config.xml file for comparison. It is expected that the encrypted password strings exactly match your environment.

    ** BI Scheduler password **

    This password can be changed in ‘schconfig’ from the DOS/UNIX command line/shell.

    C:\>schconfig
    Copyright (c) 1997-2006 Oracle Corporation, All rights reserved

    ***** Delivers Configuration Menu *****
    1 – Configure Scheduler

    >>> Enter Choice: 1

    ***** Scheduler Configuration *****
    1 – Database
    2 – General
    3 – Advanced
    0 – Quit

    >>> Enter Choice:

    >>> Enter Choice: 2

    ***** Scheduler General Configuration *****
    10 – Administrator Name : Administrator
    11 – Administrator Password : *****
    0 – Quit

    >>> Enter Choice: 10, then 11

    0 – Quit
    0 – Quit
    0 – Quit
    >>>>>>>>

Quit 3 times and restart all Analytics Services (To bring them back in synchronisation. Restarting the BI Scheduler on its own also works, but Job Manager connections may exhibit stale behaviour depending on what has been changed) .

Thanks,

~KKT~

How to Restart PBCS Services


You can use EPMAutomate utility to restart services, using the resetservice command

Please refer to the Using Oracle Planning and Budgeting Cloud Service guide > Using the EPM Automate Utility > Command Reference which contains the following information:

resetservice

Restarts the service instance. Use this command only when you observe severe performance degradation or if you receive error messages indicating that the instance is unusable. Service reset does not affect your application customization (for example, locale change, settings related to theme and currency, etc.). Reset takes up to 15 minutes.
Note:
Comments must be enclosed in quotation marks.
Usage: epmautomate resetservice “comment”

Example: epmautomate resetservice “Users experience unacceptably slow connections”

For usage details of any command, type ‘epmautomate <commandname> help’, eg:
epmautomate uploadfile help

1. Download the latest version of EPM Automate
Login to your PBCS Service
Tools -> Install -> EPM Automate

2. Install EPM Automate
Run the EPM Automate.exe downloaded in step 1

3. Use EPM Automate using a command prompt

– Open Command Prompt
– Navigate to the install Location
Example: CD C:\Oracle\”EPM Automate”
– Login to EPM Automate
Usage: epmautomate login username password/<password file> url identitydomain
Example: epmautomate login admin_user PasSw0Rd https://myservice-mydomain.pbcs.us2.oraclecloud.com mydomain
– Run reset Service Command
Example: epmautomate resetservice “Users experience unacceptably slow connections”

Thanks,

~KKT~