Migrating Essbase Application

Hello,
I am trying to Migrate the Applications between two different environments . I started using Migration Wizard in EAS and when Source Essbase server and Target were selected , it is not continuing with Migration . Instead it is throwing out an Error saying Invalid Login Credentials. Any comments !!
Thanks.

If I understand your problem correctly, you add the DEV essbase server and the PROD essbase serving to the Essbase Server's in EAS. When you connect to one of them, you get "invalid credentials" correct so far?
Does both Essbase servers share the same Shared Services server?
Does the EAS server share the same Shared Services server?
If EAS and both essbase servers use the same Shared Services server, then all should be able to connect to one another usign the same credentials. If they are all provisioned within the same Shared Services server, you will see all the server names in the dropdown when you add an Essbase Server.
If one or more of the Essbase servers (developement for instance) has a different development Shared Services environment for security and you have to type in the Essbase server name to add to the EAS Essbase Server node, then the "single sign-on" between applications cannot work (such is my case). In this case, when you add the essbase server, make sure to uncheck the "sign sign-on" option and enter a valid admin user id and password.
You will have to edit the user properties under the "Adminstration Servers" node if your password changes.
Hope this helps

Similar Messages

Error while migrating Essbase application

HI i am on 9.3 trying to migrate an Essbase application from one server to another.
But in selection page I could find only one server name in both source and target?
Thanks

Hi John,
I am using the migration wizard, but its showing the same server name in both source and target.
If i am migrating the app from Development to UAT its showing only Development server in both source and target. i did tried it in reverse from UAT to DEV then i could find only UAT server in both source and target.
Thanks.

Migrating essbase application through shared services

Hi All,I want to migrate my essbase application (11.1.2.2) from dev to prod.
please suggest me the steps to migrate

This is a question that has been asked many times and with a little research you will have all the info you need.
As you mention Shared Services I take it you are wanting to use LCM, if so then it should be pretty easy and just read through - About Lifecycle Management
Or have a look at First-Time Lifecycle Management Migration for Essbase 11.1.1 with Shared Services Lifecycle Management 11.1.1 it is based on an older version but you get the idea.
You can even go to your favourite internet search engine and type LCM essbase and you should get lots of information to look through.
Alternatively you could user the EAS migration wizard - Migration Wizard and then you will need to export/import the data either through EAS or Maxl.
Cheers
John

Migrating Essbase Application from QA to Production

Hi Experts,
I need to migrate an Essbase application (PLNG) from QA to Production system. This migration include business rules, calc scripts, load rules, and report scripts. The metadata repository resides in an Oracle DB. I am following step:
Shutdown the Essbase application PLNG.
Move the complete files under $ARBORPATH/app/PLNG from QA to Production
Move all the Essbase data files for Essbase PLNG databases pag and ind files from QA to Production
Export the PLNG user from QA and import it to the Production Oracle DB (metadata)
I need comments whether I am following the right procedure or not. Also the PLNG application contains one database PLNG1 which I want to keep as is , so in that case, how do I need to import the metadata from QA to Prod.
Thanks
-Samar-

Hello Nome02:
I would test first what dhowehughes has said. You can find this wizard on File->Wizards->Migration menu in Essbase Administration Services Console. This usually works for all metadata with two exceptions:
1) Security issues. If you are using Shared Services, you will not be able to migrate users, provisioning,... with this method. You must use Shared Services instead. If your Essbase installation is stand-alone, then you can use this wizard to migrate security.
2) Data. You have to export data to a file/s. Transfer this/these file/s to Prod environment and import them.
Regards
Javier

Migration of application from Oracle Express 6.3.4 to Essbase 9

I got a requirement to migrate an application from Oracle Express to Essbase.Can any one help me if there is any documentation for migration or else do I have to rebuild a new application in Essbase with the same functionality as in Oracle Express.
Rgrds,
G.K

As far as I am aware there is no migration tool to convert to essbase and you will have to build a new application in essbase.
On a side note this campaign from Oracle back in 1998 amuses me - http://books.google.co.uk/books?id=4VEEAAAAMBAJ&lpg=PA17&ots=Amg-YO3m5X&pg=PA17#v=onepage&q&f=false
The line "Oracle Express Server slaughtered Arbor Essbase in both load and calculation times and query times" is a classic.
I wonder if Oracle feel the same way now :)
Cheers
John
http://john-goodwin.blogspot.com/

Migrate Hyperion Essbase Application into .rpd

Dear all
Is there any tool to migrate Hyperion Essbase Application into .rpd file. If possible means i will import the .rpd file in BI.

Yes u can import data from Essbase to Bi .. there is built in function to do that in Bi
version :Oracle Business Intelligence Enterprise Edition 10.1.3.4 or latest
once u have installed and opened ur .rpd file u can see 3 layers Physical, bmm, and presentationlayer
go to file >import>multidimensional
u get popup windows where u need to input u informations
Provider tye: Essbase
Essbase server: localhost(if ur using same pc )
username: admin
password: admin password
then if ur ceredentcails are correct u can login in essbase and u get all application which u ahve in ur essbase server
chose which one u need and then import
hope this helps

After Upgrade from 11.1.1.3 to 11.1.2.2 Essbase Application Not Shown in Calculation Manager

I have upgraded from EPM 11.1.1.3 to 11.1.2.2 and now want to import Business Rules to Calculation Manager for use with Essbase.
However I cannot see my Essbase Application in Calculation Manager; (only the provided sample applications are shown in the hierarchy)
How do I check my configuration? How does Calculation Manager connect to Essbase and find my app?
I haven't knowingly altered Essbase server/port details during the upgrade as I opted not to re-host.

Yes the EAS schema was upgraded by the configurator.
I ran upgrade_ps2.sh (unix) without changing any configuration just to see what it does and (after I had to manually create the directory structure for the log file) it created an HBRrules.xml file successfully fo the first time under EPMData/planning (The missing log file directory structure may have been why the configurator didn't create the HBrrules.xml file at the first attempt during the Planning upgrade)
Anyway not entirely sure where upgrade_ps2.sh got its rules information but the file it created was very similar to the HBR file exported from EAS prior to starting the upgrade.
I attempted a 'migrate' again with Calculation Manager but still get the "No objects were found in the document for importing", i.e. kind of back to square one.
I really need to understand what is Calc Managers problem?
Q .What server should the upgrade_ps2.sh be run on? Planning or Shared Services? (I did it in on both)
Q. How can I get Calc Manager to tell me more with logging or tracing somehow?
Any other suggestions gratefully received
Many Thanks

Migrating Essbase cube across versions via file system

A large BSO cube has been taking much longer to complete a 'calc all' in Essbase 11.1.2.2 than on Essbase 9.3.1 despite all Essbase.cfg, app and db settings being same (https://forums.oracle.com/thread/2599658).
As a last resort, I've tried the following-
1. Calc the cube on the 9.3.1 server.
2. Use EAS Migration Wizard to migrate the cube from the 9.3.1 server to the 11.1.2.2 server.
3. File system transfer of all ess*.ind and ess*.pag from 9.3.1\app\db folder to 11.1.2.2\app\db folder (at this point a retrieval from the 11.1.2.2 server does not yet return any data).
4. File system transfer of the dbname.esm file from 9.3.1\app\db folder to 11.1.2.2\app\db folder (at this point a retrieval from the 11.1.2.2 server returns an "unable to load database dbname" error and an "Invalid transaction status for block -- Please use the IBH Locate/Fix utilities to find/fix the problem" error).
5. File system transfer of the dbname.tct file from 9.3.1\app\db folder to 11.1.2.2\app\db folder (and voila! Essbase returns data from the 11.1.2.2 server and numbers match with the 9.3.1 sever).
This almost seems too good to be true. Can anyone think of any dangers of migrating apps this way? Has nothing changed in file formats between Essbase 9.x and 11.x? Won't not transferring the dbname.ind and dbname.db files cause any issues down the road? Thankfully we are soon moving to ASO for this large BSO cube, so this isn't a long term worry.

Freshly install the Essbase 11.1.2.2 on Window server 2008 r-2 with the recommended hardware specification. After Installation configure 11.1.2.2 with the DB/Schema
Take the all data back up of the essbase applications using script export or directly exporting from the cube.
Use the EAS Migration wizard to migrate the essbase applications
After the Migrating the applications successfully,reLoad all the data into cube.
For the 4th Point
IBH error generally caused when there is a mismatch in the index file and the PAG file while e executing the calculation script .Possible solutions are available
The recommended procedure is:
a)Disable all logins.
alter application sample disable connects;
b)Forcibly log off all users.
alter system logout session on database sample.basic;
c)Run the MaxL statement to get invalid block header information.
alter database sample.basic validate data to local logfile 'invalid_blocks';
d)Repair invalid block headers
alter database sample.basic repair invalid_block_headers;
Thanks,
Sreekumar Hariharan

Upgrade/Migrate Essbase Standalone from 9.3.1.0 to 11.1.2.2

I've got a standalone 9.3.1 instance that we want to take to 11.1.2.2. For us, the most cost-effective way is to patch 9.3.1 to a release we can migrate from, compatible with 11.1.2.2. So it's 9.3.1 to 9.3.1.6/9.3.1.7 in place and then to 11.1.2.2 on new hardware.
My concern is the move to 9.3.1.6. Has anyone done this, and what are the pain points? My users are only in Essbase (security). I believe I've read they need to get out of Essbase before going to the 11.1.2.2 HSS/Essbase scenario (HSS required for install/startup?)
Anything that I *shouldn't* do?
Thanks in advance,
-Vince

If it is standalone and only Essbase personally I see no point in patching and then upgrading to 11.1.2.2, I would prefer to have a clean install and then migrate the application as if you moving to 11.1.2.2 then no doubt it will be new hardware and OS.
One possible method would be to install and configure 11.1.2.2 then use the EAS migration wizard to migrate the Essbase applications, data would need to be migrated separated.
You would also need to consider security if you are moving to Shared Services security in 11.1.2.2
It may be worth discussing your options with a consultant as there important points that should be covered which is probably not for a forum.,
Cheers
John
http://john-goodwin.blogspot.com/

Migrating Essbase Objects

While migrating essbase objects from one essbase server to another, i copy the whole applciation folder in NT environment.this invariably copies the app.app and app.apb files.
I opened the .app file and saw the database setup details in there and realized that the target app essbase server is different.
Does this mean that copying of .app and .apb files are not needed while migration?
Also, in the target environment, there is not .apb file. i guess this is because it is a newly created blank application upon which the migration is done. In that case, when in the .apb file created as this is the app backup file.

Hi,
The Best thing you can do during migration is, Export Level 0 data first. If you want to use the wizard, it will copy all the Essbase objects. Copy the security file from Dev to QA (assume you are migrating from Dev to QA). If you do not want to use the wizard, just simply create the application in the new server, open the outline (Dev outline) and save it in QA. Now you can import the data and run the calc script. Hope this helps and i did this process many times

Migrating Essbase App from SUN to LINUX

Dear Essbase Members,
Can you please help me in answering the below questions.
We are soon to migrate our essbase applications from Current : Sun Solaris SPARC 64 bit OS - Essbase 11.1.1.3 to Target : Oracle Linux 4 64 bit OS - Essbase 11.1.2.2 .
can i migrate my essbase applications by create all essbase applications on the target servers and just copying all essbase objects like ( .otl, .rul ), level 0 export from source and import in the target and aggregate the cube.
I know we have a migrating utility, but was thinking about the above approach. will i be able to copy files and make it work , as the OS and essbase version are different on both the servers.
or is there a better way to do this.
Thanks
MS

Yes you can use that approach or use the EAS migration wizard, personally I would choose the migration wizard as it will migrate more information like filters, substitution variables.
For a list of what is and not migrated using the wizard have a read of - http://docs.oracle.com/cd/E17236_01/epm.1112/eas_help/dbwzmigrpost-migration.html
Remember security will not be migrated if in Shared Services mode.
Cheers
John
http://john-goodwin.blogspot.com/

How to migrating planning applications version 9.2.0 to 11.1.1.3 directly

Hi All
Please help.
Can be migrated Planning applications from version 9.2.0 to version 11.1.1.3 directly?
There is documentation that explains the process?
Attentive to your comments
Regards
Pedro
Edited by: user13040806 on 06-feb-2013 5:48

Hi Pedro,
The quick way, assuming you are using Classic Planning Administration in 11.1.1.3 is to export the application schema and Essbase data & objects from the 9.2.0 environment and import into the new environment.
Thanks,
Andy

Essbase Applications 32 bit vs 64 bit

Hi,
just wondering if Planning & Essbase applications running on 32 bit servers will also run once migrated to 64 bit servers ?
Has anyone had any problems doing this before?
Any pointers will be helpful.
Thanks in advance

user-456 wrote:
Hi,
Thanks for the reply.
The support matrix (Hyperion Version 11) has the following for Intel / AMD x86-64 Windows 2003 SP1, Server Enterprise x64 Edition* (R2 is also supported) processor :
32-BIT BINARIES ONLY FOR: Data Relationship Management, EPM Workspace Services, FDM, Financial Reporting Services, Interactive Reporting Services, Shared Services (embedded Native Directory OpenLDAP service), Smart Search, and Strategic Finance.
Does it mean that we cant run workspace, financial reports, shared services Interactive reporting, strategic finance on our 64 bit machines ??
Thanks in Advance...No it means there are no 64bit components, they are all 32 bit but still should run on a 64bit O/S you just don't get the benefits of 64bit.
Cheers
John
http://john-goodwin.blogspot.com/

OIM11gR2 - How to migrate an Application Instance Form

Hello,
I'm trying to migrate an Application Instance Form from my Dev env to my QA env.
My target system is SAP
I performed the following steps in Dev:
1. Installed and configured the SAP Connector (no problem here)
2. Created a sandbox
3. Created an Application Instance
4. Created the Application Instance Form
5. Ran a target reconciliation to confirm everything is working properly
6. Exported the sandbox
7. Published the sandbox
8. Via Deployment Manager I exported all objects related to SAP (Resource object, Process Forms, Lookups etc.)
In QA I did:
9. Installed and configured the SAP Connector (no problem here)
10. Via Deployment Manager I imported the objects related to SAP
11. Imported the sandbox
Problem:
To my surprise, the Application Instance does not have a Form in the QA env.
I had to create it manually by performing the following:
12. Create a sandbox
13. Open the Application Instance definition
14. Click on create (to create a form)
15. Entered the same name I used in my Dev environment
16. Received an error message saying that the form already exists
17. Entered a different name for the Form
18. Saved
19. Exported the sandbox (to import in Prd)
20. Published the sandbox
21. Ran a target reconciliation to confirm everything is working properly
I tried to reproduce the problem with another (test) destination environment because I don't want to have the same problem when migrating to Prd.
I repeated the steps 9,10,11 except that I imported the sandbox exported from QA (step 19) instead.
The same problem: Application Instance definition has no Form attached to it in my test destination environment.
If I try to create the form with the same name, it gives an error message saying it is already there.
Is my procedure wrong?
Is there an official procedure explaining how to migrate only Application Instance Form from one env to another?
My env:
OS: Windows 2008 R2 SP1
OIM: 11gR2 BP7
SAP connector: 9.1.2.2.0
Thanks,
Adr

This is a bug: Bug:16027176
Check the [Article ID 1515225.1] which proposes a workaround that might be useful in your case (it was not in mine).
In short the workaround is:
The following order should be observed to export :
- IT Resource & Application instance in one xml
- Request DataSet in another xml
- SysAdmin Sandbox (the one defined while creating the Application Instance and the Form)
- Identity URL Sandbox (defined while customizing the fields on the Form, in the Catalogue page)
Adr

Info : Migrating Apex Application from Non-SSO to SSO environment

Hi All,
This post is to share my experience while working on APEX. This may be useful to some apex developer.
If we migrate an apex application from a non-sso (i.e. http) to sso (i.e. https) environment, the flash chart doesn't work.
I found that in the source of a Flash Chart region, we use #HOST# variable to locate the swf file. The environment variable takes the correct path but with "http" as prefix. But to access application pages "https" is used. Because of which, the swf file couldn't be located by the application.
Work-around Solution : If I hard code the value i.e. the application path having "https" replacing #HOST# variable then the flash chart works fine. I couldn't found a way by which the #HOST# parameter value can be updated to take "https".
The same environment host other non-sso applications as well.
Any comments on this are welcomed.
Regards,
Mangal

Hi Dirk,
Thanks for the reply.
As I mentioned earlier, by Non-SSO I mean "http" and by SSO I mean "https". This is because, before migration the application was accessible using "http" and now we have to use "https" alongwith SSO to access the application. I only want to highlight the Flash Chart issue with this migration.
The problem doesn't solves with your solution as I am getting correct instance/environment name with #HOST# but prefixed with "http" and not "https". Hence the application won't be able to locate the required swf file.
Even the workaround I mentioned is only feasible, if an application has only few Flash Charts. However, if there are large no. of Flash charts in an application, then it would be a tedious task to update all flash chart source either by an application item (as you mentioned in your post) or hard coding the path itself. Also, every new Flash Chart source needs to be updated by a developer to fix this.
A better solution is required by which the Flash chart source is not touched and the #HOST# variable for the application is updated to take the "https" prefixed to the swf file path.
Regards,
Mangal
Edited by: Mangal on Mar 5, 2009 11:31 PM

Migrating Essbase Application

Similar Messages

Maybe you are looking for