DRM – How to create a workflow model


The new request tab under worklist is greyed out for the user as workflow model was not created.

Scenario: Create a Workflow Model(WFM) which has two stages one is Submit and the other is Commit. This WFM is used for adding new base node.

1.Create users with the below roles:

Governance user, governance manager and workflow user

2.Create required Node Access Group(NAG).

3.Create the workflow task.

4.Create the workflow model.

–Click on Edit of Submit Stage in Action column and assign Workflow Task and Node Access Group to that Stage.

–Select the respective Workflow Task in the available list and push to selected list.

–Select the respective NAG in available list and push to selected list.

–Click on Save which is on the right-hand side

–Click on Edit of Commit Stage in Action column and assign Node Access Group to that Stage

–Select the respective NAG in Available list and push to selected list

Note: No Workflow Task will be there in Commit Stage.

–After completion of all Stages updates, Click on Save.

5.Assigning Hierarchy Node Access to NAGs
–Login to DRM.

–Select Version and open respective hierarchy.

–Go to Nodes->Assign->Node Access

–Select respective NAG group and select the appropriate access level and click on Save.

 

The new request tab in the work list will be available now.

FDMEE: Where Are The Logs For FDMEE


What are the logs for FDMEE and where are they stored?

 

When providing logs for support please ensure you have set the logging level to 5. This can be done inside FDMEE in the System Settings.

 

11.1.2.3

1) ERPIntegrator0.log

Stored under: \Oracle\Middleware\user_projects\domains\domain\servers\ErpIntergrator0\logs

Often referred to as the FDMEE or ERPI log

 

2) Process Log  (<EPM Application Name>_<processid>.log)

Stored under: FDMEE Root Folder\Outbox\Logs  (to see the location of the Root Folder please check the System Settings or Application Settings within FDMEE)

This log can also be seen from with FDMEE on the Process Details screen. Check the Show Log option for the process

 

3) ODI Agent Log

Stored under: \Oracle\Middleware/user_projects/domains/EPMSystem/servers/ErpIntegrator0/logs/oracledi

 

11.1.2.4

1) aif-webapp.log

Stored under: \Oracle\Middleware\user_projects\domains\domain\servers\ErpIntergrator0\logs

 

2) Process Log  (<EPM Application Name>_<processid>.log)

Stored under: FDMEE Root Folder\Outbox\Logs  (to see the location of the Root Folder please check the System Settings or Application Settings within FDMEE)

This log can also be seen from with FDMEE on the Process Details screen. Check the Show Log option for the process

 

3) ODI Agent Log

Stored under: \Oracle\Middleware/user_projects/domains/EPMSystem/servers/ErpIntegrator0/logs/oracledi

Thanks,

~KKT~

Hyperion Planning – Steps to Clear the EPM Oracle Instance Temporary Directories


This document is to provide information and recommendations on clearing the TMP and CACHE directories.

Each time an import or export occurs, Planning generates temporary files which are placed in the EPM Oracle Instance tmp directory. These files are not deleted, and over time, they can build up and affect performance. Oracle recommends that you periodically clear the EPM Oracle Instance tmp directory.

This is also recommended after upgrades and patches are applied.

Clearing the TMP directory may help resolve issues similar to the following:

  • Blank page while accessing Planning directly: (http://plan_server:8300/HyperionPlanning/)
  • Blank page while opening Planning Administration from within WorkSpace
  • “Internal Server Error” while opening Calculation Manager from within Workspace

 

Please follow the steps below to clear the temporary files and folders:

1. Shutdown EPM services.

2. On Foundation Server delete folders:
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\CalcMgr0\logs\cache
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\CalcMgr0\logs\tmp
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\Foundation0\logs\cache
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\Foundation0\logs\tmp

3. On Planning Server delete folders:
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\Planning0\logs\cache
%MIDDLEWARE_HOME%\user_projects\domains\EPMSystem\servers\Planning0\logs\tmp

Or
\Oracle\Middleware\User_projects\domains\EPMSystem\Servers\Planning0\Cache

\Oracle\Middleware\User_projects\domains\EPMSystem\Servers\Planning0\tmp
4. Restart EPM services.
5. Clear browser cache and retest.

Thanks,

~KKT~

Essbase Auditing Feature To Report Users Currently Logged Into The System


Does Essbase have an auditing feature to report on the users currently logged into the system?

The Generate Log Charts/Log Analyzer feature on EAS can be used to generate a chart based on the Essbase log entries.

To enable Log Analyzer:

1.  In EAS, right click on the Essbase Server and select “Generate log charts”.
2.  Right click on the Essbase server once again and now select “View” -> Log Charts.
3.  There will be a dropdown for View by Filter and select the value “Logged users”.
4.  Click on the refresh button to refresh the entries displayed.

Other options to retrieve user login details:

1.  Check the Essbase log files for login information.
2.  Use the GETUSERINFO command via ESSCMD to retrieve the last login information.
3.  The LISTLOGINS command in Esscmd will provide a listing of currently logged in users.

In the essbase.cfg file setting PERSISTUSERATLOGIN TRUE adds the user to the security file, and tracks user information (such as the time the user last logged into Essbase) and named connections.
Thanks,
~KKT~

FDM Error – Unable to create Load Balance Manager object Error=cannot create activex componenent


When accessing FDM via the web, the following error message is returned:

Unable to Create Load Balance Manager Object!
When launching the FDM Load Balance Server Configuration and attempting to update with the service account password receive error message:

“Unable to create Load Balance Manager object!
Please verify that the user name, password, and domain are correct
Error=Cannot create ActiveX component.”

The software is unable to create the FDM Load Balance Manager DCOM object and results in the error.

This error message is caused by one of three items:

1) The Account entered in the Load Balance Config has been locked out
2) The Id/Pwd entered into the load balance configuration is invalid
3) There is an invalid id set in the Security Tab of the Load Balance Manager DCOM object.

Any of these items would result in being unable to create the Active X component necessary.

Reset Identity and Security on FDM Load Balance Server DCOM object

Perform the following:

1) Choose Start/Run and type Dcomcnfg
2) Expand Component Services\Computers\My Computer\Dcom Config and locate the object {E652643D-6CC1-48AC-915D-01842B04F292}
3) Right-click on this item and choose “Properties” and click on the “Security” tab
4) Click the “Edit” button and remove all users/groups and click OK, then set the radio button to “Use Default”
5) Click the “Edit” button under Access Permissions and remove all users/groups and click OK, and set the radio button to “Use Default”
6) Click on the “Identity” tab and remove the ID in the “This User” field and set the radio button to “The Launching User” and click “Apply” and “OK”
7) Re-launch the FDM Load Balance Config and reset the service account, application servers, and MSAD Configuration.

Essbase Administration Services (EAS) Crashing While Editing Outline


EssbaseAdminService crashes frequently during outline editing while plenty of JVM memory available and JRE used is jrockit.  The jrocket dump file can be found under:

<MIDDLEWARE_HOME>/user_projects/domains/EPMSystem/jrockit.xxx.dump

A dump file has file name such as jrockit.12826.dump.

If you review the jrocket dump, there is no out-of-memory issue but contain following message on a Linux system:

Error Message: Illegal memory access. [54]
Signal info : si_signo=11, si_code=1 si_addr=0x1cd
Version : Oracle JRockit(R) R28.2.5-50-153520-1.6.0_37-20121220-0843-linux-x86_64

The default size of a thread stack in jrockit is 320K for win64 and 1M for Linux64.  Depending on the request, the default may not be large enough.  When the stack overflows, there really is nothing obvious in the core or dump file.

To Fix –

Increase the size of the thread stack by adding/modifying the -Xss setting.

Windows:

The -Xss setting will need to be added/modified in two locations:

1.  Navigate to <EPM_ORACLE_INSTANCE>\bin\deploymentScripts.

2.  Edit the setCustomParamsEssbaseAdminServices.cmd and add/modify the -Xss1M to the USER_MEM_ARGS setting.  For example:

USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx4096m -Xss1M

3.  Add/Modify the -Xss setting to the Windows Registry.

a. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\EssbaseAdminServices0\HyS9eas_epmsystem1.  If there is a JVMOption for -Xss, increase the value to 1m.  If a JVMOption for -Xss does not exist:

b. Create a new “String Value” entry with following name and value:

Name:JVMOptionY
Value: Value:-Xss1M
With Y being equal to (current value of JVMOptionCount) + 1

c. Increase the value of the JVMOptionCount parameter by 1.

4.  Restart the EAS server.

 

Unix/Linux: 

1.  Navigate to <EPM_ORACLE_INSTANCE>/bin/deploymentScripts.

2.  Edit the setCustomParamsEssbaseAdminServices.sh.  Add/modify the option -Xss2m to the USER_MEM_ARGS setting.  For example:

USER_MEM_ARGS=-Xms128m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx4096m -Xss2M

3.  Restart EAS server.

What Is The Basic Setup Of The Changed Data Capture (Journalization) Feature In ODI


What is the basic setup procedure for implementing the CDC (Journalization) feature in Oracle Data Integrator (ODI)?

Details of ODI CDC setup can be found in the documentation library under the “Change Data Capture” topic.

  1. In the Model move to the Journalizing tab and choose the Journalizing Mode.
    • Double-click Model – Journalizing tab – Journalizing Mode, click radio button there for Simple or Consistent Set.
    • Simple Journalizing tracks changes in individual Datastores in a Model by the use of triggers (Simple) and crated views and tables (consistent).
    • Consistent Set Journalizing tracks changes to a group of Model Datastores and takes into account the referential integrity between these Datastores. The group of Datastores journalized in this mode is called a Consistent Set.
  2. Then select the Journalizing Knowledge Module (KM).
    • Double-click Model – Journalizing tab – Journalizing KM – Choose from the drop down list.
    • This Knowledge module must be imported into the Project’s Journalization JKM branch to be available for selection.
  3. The Options window should appear below and presents the options associated with the JKM.
    • Click in the Value section of the Options window to get a drop down menu of values, which can be chosen or left as default.
  4. After Journalization is set up, drill down in the Models panel to the Datastores of the journalized Model.
  5. Add the Datastore(s) to CDC.
    • Right click on the Model, click on Changed Data Capture and then on the Add to CDC.
  6. For Consistent Set Journalization, the order of those Datastores must be set in the Model on the Journalized Tables tab.
  7. Add the subscriber(s) to CDC.
    • Right click on the Model – Changed Data Capture – Subscriber – Subscribe…
    • Add subscriber to the text box on upper right and click on arrow button to add to list click OK.
    • The Execution pop up window shows and click OK button to execute subscriber addition.
    • Check Operator for success in addition of subscriber.
    • Subscribers: CDC uses a publish/subscribe model. Subscribers are the consumers of the data or entities that use the changes tracked on a datastore or on a consistent set. They subscribe to a model’s CDC to have the changes tracked for them. Changes are captured only if there is at least one subscriber to the changes. When all subscribers have consumed the captured changes, these changes are discarded from the journals.
  8. Then from the Model start the Journal.
    • Right click on the Model – Changed Data Capture – Start Journal
    • The Execution pop up window shows and click OK button to execute the journal startup.
    • Check Operator for success of journal startup.
    • This operation creates views for CDC and either triggers and/or the tables for CDC in consistent set.
    • Following are examples of those names created by the Journal.
      • Tables
        • SNP_CDC_*
        • J$
      • Views
      • Triggers
        • DT$
  9. From the Datastore icons, look for the tiny green clock that represents a journalized Datastore, click the refresh button if necessary.
  10. If the clock persists as yellow:
    • Right click on the Model – Changed Data Capture – Stop Journal
    • Determine the issue with the journal and restart journal.
  11. To view changes made, right click on the journalized Datastore – Changed Data Capture – Journal Data.
  12. Restart Changed Data Capture (CDC) processing:
    • The Model / Datastore in question is already journalized, and the ODI journalizing infrastructure still exists in the respective Working schema.
    • One should not re-start the journalization of a Model and/or Datastore if a previous journalization is still active.
    • The re-journalization is not possible without having stopped the already active one.
    • Hence, first stop the existing journalization, then start the new journalization.

Journalizing Status

Datastores in Models or Mappings / Integration Interfaces have an icon marker indicating their journalizing status in Designer’s current context:

  • (green clock icon) OK:Journalizing is active for this Datastore in the current context, and the infrastructure is operational for this Datastore.
  • (yellow clock icon) No Infrastructure:Journalizing is marked as active in the model, but no appropriate journalizing infrastructure was detected in the current context.

    Journals should be started.

    This state may occur if the journalizing mode implemented in the infrastructure does not match the one declared for the Model.

  • (white clock icon) Remnants:Journalizing is marked as inactive in the model, but remnants of the journalizing infrastructure such as the journalizing table have been detected for this datastore in the context.

    This state may occur if the journals were not stopped and the table has been removed from CDC.

Thanks,

~KKT~

Import ODI Objects From Older Versions


Is it possible to export ODI objects from previous release and import them in ODI newer release?

For example: export ODI 10g objects and import them in ODI 11.1.1.5.0 (or from 11.1.1.3.0 to 11.1.1.6.0 etc …)

If so, how can this be performed?

It is technically possible to import ODI older objects into ODI Repositories 11.1.1.5.0 or higher version, using:

  • The Smart Export / Smart Import feature, or
  • Export / Import of Topology and Security components in the form of XML export files, or
  • Export / Import of Work Repository versionable components, such as:
    • Models and Model Folders,
    • Projects, and Project Folders
    • Packages
    • Scenarios
    • Integration Interfaces
    • Procedures and Knowledge Modules
    • Sequences
    • User Functions
    • Variables
    • Solutions
    • Load Plans
The full import of a Master Repository though is not supported, and would lead to issues such as the one described in Note 1674134.1 – “This action is forbidden. Master repositories must be upgraded” Signaled When Attempting To Import Components Into ODI Repositories Rather Than Upgrading.

Such operations are supported but not recommended as full update will always bring more benefits such as KM bug fixes.

Also, additional restrictions concern the version of ODI from where objects are exported, and into where they are imported:

Import
To ODI 10g To ODI 11g To ODI 12c
From ODI 10g Yes Yes (1) No
From ODI 11g No Yes Yes (2) (3)
From ODI 12c No No Yes

 

(1) The import from ODI 10g to ODI 11g requires at minimum ODI 10.1.3.5.0 to be used.
For moving from ODI 10.1.3.4 and older to ODI 11g, a preliminary/intermediate upgrade/import to ODI 10.1.3.5 (or ODI 10.1.3.6) is required.

(2) The import from ODI 11g to ODI 12c requires at minimum ODI 11.1.1.7.0 to be used.

(3) Due to the introduction of GLOBAL_IDs, the import from previous version requires an Upgrade Key be specified in order to be able to generate consistent GLOBAL_ID values for the objects as they are upgraded before they are imported.

Thanks,

~KKT~