Migration Essbase 7.x

A step for the migration is..execute alter database validate command in MaxL against database, what is this command? what is your sintaxis? because in the documentation dont appear.

Look in the Technical Reference installed with Essbase documentation.Example:alter database sample.basic validate data to local logfile 'invalid_blocks';Hope this helps.

Similar Messages

Migrating Essbase from 7.1.6 to 11.1.2.2 in Unix Environment

Hi Experts,
we are going to migrate Essbase from 7.1.6 to 11.1.2.2 in unix environment. We have heard that we cant migrate directly from 7.X to 11.X Version. If so, then how can we proceed. Please suggest the steps to follow and documents to proceed in Unix Environment. I am new to unix environment.
Your suggestions will be more helpful...
Thanks,
Chinnu

Thanks Celvin,
But my doubt is can we migrate 7.1.6 version Essbase to 11.2.2 version in a single shot? I have heard like If we want migrate 7.1.6 to 11.1.2.2
1. we have to migrate 7.1.6 to 11.1.3 and then
2. 11.1.3 to 11.1.2.2.
Will the migration utility work to migrate 7.1.6 to 11.2.2? Please suggest on this am not getting a clear clarification on this.
Thanks,
Chinnu

Upgrade Path for migrating Essbase 7.1 to Essbase 11.1.2.1??

Can any one tell me the upgrade path (and related documents) for migrating Essbase 7.1 to Essbase 11.1.2.1??

Thanks Nathan for your response.
Will the below Essbase Upgrade steps work (From version 7.1 to Version 11.1.2.1 directly)?
1. Install Essbase 11.1.2.1 in one server (new) and Shared Services in another server (new). Both the new servers with Win 2008 OS.
2.Login to EAS console in the new server. Open the outline version 7.1 and then migrate to version 11.1.2.1.
3. Copy the artifacts (such as Calc Scripts and Rule Files etc.) from the Old Essbase directory (Version 7.1) to the new Essbase directory (Version 11.1.2.1).
4. Extract data from the old system and import into the new system.
5. Export Essbase security from old system and import to the shared services of the new system. This might requires some manual interventions.
Or, do I have to upgarde from version 7.1 to 11.1.1.3 and then from 11.1.1.3 to 11.1.2.1?

Migrate essbase analytic services 7.1.2 to 9 . 3 . 1

Hi,
We are quite new to hyperion and we have a client who has deployed essbase 7.1.2 with Hyperion planning.
We want to know, is it possible to migrate essbase directly into latest release 11.x or system 9. Appreciate your advice!
Nilaksha.

You can migrate directly to 9.3.1. When you open the 71.2 outilne and save to the 9.3.1 server it will upgrade it for you.
Gee

Tools to migrate Essbase cubes to SSAS and Hyperion reports to SSRS

Hi,
Is there any tool available to migrate
1)Essbase cubes to SSAS
2) Hyperion reports into SSRS
I appreciate your guidance here.
Thanks
Naveen

Hi Naveen,
I provided the following articles for your reference.
1)Essbase cubes to SSAS
http://blogs.msdn.com/b/mtcdata/archive/2008/06/17/migrating-essbase-shared-members-to-sql-server-analysis-services.aspx
2) Hyperion reports into SSRS
Using SQL Server 2005 Reporting Services with Hyperion Essbase
http://go.microsoft.com/fwlink/?LinkId=81970
Hyperion Essbase Connection Type (SSRS)
https://msdn.microsoft.com/en-us/library/dd207026.aspx

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

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.

Data issues in Migrating Essbase(BSO and ASO apps)from Server 7 to Server 9

I was able to copy application one is BSO another one is Aso
Both APPS ARE CLEARED IN BATCH FILE.
Budget data excel and flat files is loaded to BSO, calcualation for current year data is done the some for budget files loaded and then calcs are executed.
Then the data for curent year is extracted from bso
then this data all such previus yr and prev exports are loaded to ASO
Then agg is enabled in ASo
All this is done using a batch which call s 10 maxl and which in turn load data and run staggered calcs.
But the issues is Data is not matching after perform these steps in Server 9 at many intersections
Every artifact/var are copied, batch logs are success but still data does not match vs Server 7.
I believe some extra data is generated by Creteblockoneq, createnonmissblock and other calc functions.
I tried copy/Migrate/Manual copy but nothing worked.
Data analysis shows atleast some extra recored are generated after calc in export file
Help needed?

Hi
Thanks for the reply.
There are no rejects.
I am exporting level 0 data and loaading it to ASO.
And, the issue includes both points-
1)Extra data points coming in
2)Some intersections data is missing
It is like 80% data is matching
It seems some essbase Calcs calculation way is modified although not sure.

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

Migration Essbase Studio Application form 11.1.1.3 to 11.1.2.1

Hi All,
Could please provide the steps or any documents related to the below issue
Migrate 1 Essbase Studio Application (Dimension elements, Schema, Hierarchies, Model, Drill through report) from 11.1.1.3 environment to 11.1.2.1 environment
Thanks in Advance
Venu

Have a read of - Essbase studio Upgrade from 11.1.1.3 to 11.1.2.1 or how to Migrate 1 Essbase Studio Application from 11.1.1.3 to 11.1.2.1
Cheers
John
http://john-goodwin.blogspot.com/

Migrate essbase app from 6 to 9

planning to migrate the app from essbase 6 to esbase 9.to a whole new server.
Any issues with that...any doc on migration from 6 would be useful.
its urgent

I started to migrate from 6.6 to 9.3.1 and it went quite smooth. What I have done:
Installed the server.
Used the config tool and removed shared services registration.
Copied essbase.cfg to new installation.
Had to add the env variables manually on AIX from the hyperionenv.doc.
Installed the eas server.
Used config tool for config and deployment of eas on std settings.
Installed the eas client and used the migration tool to migrate some databases to the new server from a 6.6 (6.6 running on different machine than 9.3)
Tested our batch processing for data load, security transfers, data staging etc. which uses some api interfaces and ESSCMD and maxl scripts. All without any problems. All settings were kept the same as on the old systems (essbase.cfg, db settings, app settings).

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/

Migration Essbase OS

Hello to everybody:
My client has Hyperion 9.2 with Essbase, Planning, Workspace and Shared Services. They have Essbase in a Solaris server and the rest in another Windows server and they are considering to change from Solaris to Windows.
I think that only Essbase is not difficult, but when Essbase is used by Planning, I don't know if it is possible to do such a migration.
Does somebody know how to do this? Any kind of wizard or guide? Does Oracle still support this version?
Thank you for your help
Regards,
Javier

The planning side will not be too much of an issue as the applications are stored in a relational database and by the sounds of it that wouldn't be changing, it should be just a case of updating the planning datasources to point at the new instance of essbase for each application. It has been a while since I have worked on 9.2 so my mind is a bit rusty on all the required steps.
John
http://john-goodwin.blogspot.com/

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

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

Migration Essbase 7.x

Similar Messages

Maybe you are looking for