Thursday, February 27, 2014

Upgrade from MDM to DRM in 10 steps


1. Download Software from Oracle for DRM 11.1.2.2.302  . It can be installed on Windows 2003 and 2008R2.  I recommend 2008 R2 for best results.

2. Login as admin user/creator

3. Create a Schema with SYSDBA rights

4. Run the software and install DRM product. This step is quite straightforward.

5. Run the Repository Wizard.
 a. Provide Source Connection Information
 b. Provide Target  Connection Information
 c. Provide UNC path information
 d. Wait for Repository creation information

6. Click on Upgrade.

7. Create an Application and confirm the configuration with the drm_admin user and Save it.

8. Start the service.

9. Place Web client on Desktop and allow access for essbase users.

10. Login to Web Client to verify the hierarchy . Default login id is admin/Welcome!

Essbase Agent Issue on 11.1.2.2.102

I have Essbase running on 11.1.2.2 upgraded from 11.1.1.3 on Windows 2008 R2 64 bit platform.
On 11.1.2.2 , I would often run into an issue with the Essbase Agent suddenly starting to freeze and would not allow any new requests.
On the MaxL Client, Once I logged in , There would be no response . It would just stay right there and nothing would happen.

The Essbase.log file would not populate any new information at that moment the freeze occurs and previous messages would contain numerous references to the following 2 messages:


Local/ESSBASE0///14460/Warning(1051003)
Error -1 processing request [Multiple Async Logout] - disconnecting

Local/ESSBASE0///14460/Error(1042013)
Network error [10053]: Failed to receive data

NETDELAY AND NETRETRYCOUNT tweaking did not help much.


Root Cause:

Issue found Closing and re-initialize the mutex while it is in use during certain race conditions.T

Solution:

PSU 11.1.2.2.104


WebAnalysis Installation on a Patched EPM Platform

I had a unique situation present itself in front of me when business wanted me to install WebAnalysis on top of a complete with patches, pretty looking platform.  I got to it with much gusto and was able to get through with the installation smoothly.

The Configuration went fine as well except for the "Reregistration of Scripts",which failed. This is essential for creation of the WebAnalysis Tables in the BI+ Schema.

That didn't preven't me from logging into WebAnalysis Studio however and when I tried to create a connection and save it, it would never happen and the java console gave messages like

Java Plug-in 1.6.0_29
Using JRE version 1.6.0_29-b11 Java HotSpot(TM) Client VM
User home directory = C:\Users\XXXXXX
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to
---------------------------------------------------
load: class com.hyperion.analyzer.usersession_base.AnalyzerClient not found.
java.lang.ClassNotFoundException: com.hyperion.analyzer.usersession_base.AnalyzerClient
at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

The following was the solution:


1. Update 'EPM_ORACLE_HOME\upgrades\webanalysis\update_registry.bat' script:
"%JAVA_HOME%\bin\java" -DEPM_ORACLE_HOME=%EPM_ORACLE_HOME%
"%JAVA_HOME%\bin\java" -DEPM_ORACLE_HOME=%EPM_ORACLE_HOME%


Replace:

-DEPM_ORACLE_INSTANCE=%EPM_ORACLE_INSTANCE% %ODL_PROP% %LOCALEPROP%
com.hyperion.analyzer.upgrade.HYARegistryMigrator %SOURCE_SYSTEM% "  with

-DEPM_ORACLE_INSTANCE=%EPM_ORACLE_INSTANCE% %ODL_PROP% %LOCALEPROP%
com.hyperion.analyzer.upgrade.HYARegistryMigrator  "

and rerun the EPM System Configurator. The "Process Reregistration Script" portion should go through perfectly after this.

2. Run analyzer_upgrades.sql line by line on your BI plus schema.

3. Run your Web Server Config as the last step .


How to set DB Schema password to 'never expire'

As a Hyperion admin, I have time and again run into this issue with my hyperion schemas where the password sometimes expires and wreaks havoc on the application.

The key indicator for these error messages are the log files. They are quite descriptive .

Basic test to make sure that the schema is working correctly will be to login to the DB hosts and issue this command:

conn username/password;

To resolve this issue ,

connect to your DB as sysdba and run

ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;


Restart all Services and ensure all the log files under diagnostics\logs\services directory startup properly.

This should resolve the issue.

Update/Replace Hyperion MSAD with new MSAD

 I had an organizational need for updating my current active directory and replace it with a new active directory.
We have a rather simple structure in our provisioning data, mostly controlled by native groups and AD users being part of those groups.

These are the steps I followed to make that happen:

1. Export a good working copy of current Foundation project from LCM. To do this, navigate to Application groups->Foundation->Shared Services->Native Directory. Highlight everything and export it to the server.
2. Open Groups.csv and scroll to #groups_children tree section.
A typical section will look something like this.

#group_children
id,group_id,group_provider,user_id,user_provider
Sample Group,,,Username,DomainNameX

Do a find and replace for DomainNameX with DomainNameY
and save the file. Repeat for all the files inside the Export.

3.  Login to Shared Services and navigate to Administration->Configure User Directories and add the information for the New MSAD

4. Verify that the old MSAD is moved to search order 3 and is "Excluded" . Save the Settings.

5. Perform a full restart of all the products.

6. Login as admin to Shared Services and Import the file updated in Step 2.

7. You should now find updated provisioning information on Shared Services.

Spl Note for Planning Apps:

You will need to "Refresh Database->Security" for each planning application. Otherwise you are likely to encounter 'unable to sync provisioning error' when you login to planning.

Hope this helps.