Migrating Planning 4-11

Similar Questions

• 9.3.3 update/migration planning apps to 11.1.2.2

  I'm at the next step in our upgrade of 9.3.3 11.1.2.2 and ready to migrate our planning applications. I have read many of the posts related to it and have a general list of the steps, but I have a slightly different situation than what I've seen posted before.

  To summarize, we have installed 11.1.2.2 on new servers.  Our old 9.3.3 is still running on different environment.  I have correctly completed the following:

  1 Foundation Services Shared Services installed and up and running, and users/groups correctly migrate.

  2 Essbase and EAS and up and running.  All Essbase applications (except for planning applications), were migrated successfully of 9.3.3 to 11.1.2.2.

  3. the planning has been installed and is operational.  While there is no apps planning in the new system, I can open planning via the workspace administrator.

  So the next step is to get my apps of moved/transferred the 9.3.3 planning environment for the new 11.1.2.2.

  To complicate matters, we are through to the SQL Server repository 9.3.3 to Oracle in our new 11.1.2.2.  So the first thing we did was to create a new Oracle schema for our planning app repository and using the developer SQL migrate Wizard, we have migrated/copied tables and data from the old Oracle's SQL Server.  It seems that all the tables and data have been properly copied to Oracle.

  Our old planning application is called PlanTest. The owner of the application is a native user called planadm.  My planned migration plan (and my questions) are:

  1. create a new empty planning called PlanTest into account application planamd 11.1.2.2 native?

  2. If I use my new Oracle repository for this soft white, it will eliminate the old data converted or he will try to upgrade/migrate it?

  3 or... should I take a backup of my new first converted repository.  Then drop/recreate the Oracle schema (so no tables) and let Planning to build the repository when I create the Virgin Planning application?  Then capture the owner SID in the new table HSP_USER.  Stop planning. The backup of the overlay on the newly created repository 9.3.3, then replace the owner SID info. Then restart Planning.

  * My concern: the structures of repository planning app table matches between 9.3.3 and 11.1.2.2?

  4. open Planning and hope that the PlanTest application appears!

  5. use Planning Upgrade Wizard to complete the migration and upgrade of the repository.

  6 push/Create app to Essbase.

  7 export data from old app in .txt file loading and reloading in planning new cube.

  8 convert/migration of business rules using information from John's blog.

  I don't know that I missed something.  Suggestions or comments on these steps would be appreciated.  Bottom line is I need to get this app (and several others) migrated successfully with all the metadata, rules of security, forms, etc..  Their reconstruction from scratch is NOT an option.

  In addition, to clarify.  It is a classic planning application.  We do not use EPMA.

  Thank you

  Mike

  It would probably make things even simpler if the owner of the application has been changed to the default Administrator account before the upgrade.

  In any case, it has been included before, but

  create a blank planning application (any options) with planadm

  store the SID code in the table HSP_USERS

  stop planning, dropping the schema, import the 9.3.3 the same pattern,.

  updated the SID in the HSP_USER to that stored.

  Start planning

  Update app

  and so on

  See you soon

  John

  http://John-Goodwin.blogspot.com/

• EPMA Migration Planning Application

  Hello
  
  We are migration planning EPMA from Dev to QA application. After you import the application, the application is shown as a UNICODE application in environmental assessments in QA.
  Please let me know why this is happening and how to change it to the format NOT UNICODE.
  
  Version 11.1.2.1
  
  Thank you
  Nainitha

  You will need to remove the app, and then update the parameter then recreate it again, I know it's possible to hack the table to update the setting but because the application is already created I'm not sure it would make much difference.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Data form question - LCM Migration Planning

  Hello

  I am using Hyperion Essbase & planning version 11.1.1.3 applications. I exported QA dataforms and tried to import in the Prod environment, using LCM. But the dataforms do not migrate due to the long name of the dataforms.

  Thank you

  Michel K

  Have you tried to use the formdefutil instead to see if it works better, for your trial version, import and export of data forms

  See you soon

  John

• Migrating planning 11.1.1.3 extract file 11.1.2.3 LCM LCM

  
  I need to migrate a 11.1.1.3 app a new 11.1.2.3 planning environment.  I read that LCM now supports the former extracts of application but have not been able to successfully view Shared Services application artifacts.  Anyone have this working?  I heard that the old version should be patched to allow this works but have not seen the patches published.

  Requires 11.1.1.4.500 and 11.1.2.3.050 +

  See you soon

  John

  http://John-Goodwin.blogspot.com/

• Migration planning of LCM

  I wonder what kind of LCM migration times people know about 11.1.2.1 for planning applications. I have one who is running for 20 minutes now and I wonder if it is blocked or if for some reason any planning takes a lot of time longer than Essbase.

  Personally, I was still running a refreshment after the migration.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• This migration plan will work?

  Infrastructure of "old":

  2 x ESX v3.5 hosts

  vCenter v2.5

  iSCSI SAN storage

  'New' infrastructure:

  3 x ESXi hosts v4.1

  vCenter v4.1

  Shared SAS storage

  Hosts/vCenter OLD can speak of NEW hosts/vCenter via 1 Gbps ethernet LAN (they are on different IP subnets, but routing is enabled via the intermediate firewall).

  FORMER storage is quite different/separate from the NEW storage.

  I guess my best/more sure bet is a kind of migration cold.  Perhaps something like the following:

  1. close the old VM reviews OLD infrastructure

  2. start using Converter CD

  3 convert the VM (virtual to virtual) and bring it up to more on the NEW infrastructure

  4 tinker with things like (VMXNET3) network card and so forth if necessary

  with my 'out back' strategy being simply initialize the guest VM still on the OLD infrastructure if something does not work.

  Is to be too careful?  I have problems I have not planned?

  Second question:

  I have a 1 virtual Windows Server 2003 domain controller that must also be migrated.  He is the owner of all the roles of "PDC".  My secondary DC at this time is a physical machine.  My migration to this VM DC plan would be as follows:

  1. close all virtual machines on the OLD network (weekend break) including vCenter 2.5 VM

  2. turn off too physical DC

  3. connect the host to ESX v3.5 using credentials of 'root '.

  4. start the VM OLD DC with Converter CD

  5 convert the virtual machine (virtual to virtual) and bring it up to more on the NEW infrastructure

  6. tinker with the network card, etc.

  7. If he's fine, starts replication DC and physical verification

  8. If it's fine, remaining boot VMs

  with my 'out back' strategy being simply start the domain controller in VM still on the OLD infrastructure if something does not work.

  I'm worried about it.  Y at - it no chance that this 'material change' will cause the DC is to lose communication with each other?  I'd be better to:

  A. build a new DC on the NEW infrastructure

  FSMO roles (b) transfer to the new domain controller

  C. remove the old DC on the OLD infrastructure (avoiding thus have to migrate)

  Would appreciate any suggestions.

  With converter, you can make a copy of the host to host so I wouldn't bother start the virtual machines with the cold clone CD.

  Personally I add 3.5 hosts to vCenter 4.1 and clone virtual machines.  Do not change the HW version if you don't want this weekend.

• Migration Planning Application 11.1.2.1 to 11.1.2.2

  Gurus
  
  I'm trying to migrate a version 11.1.2.1 Hyperion Planning application version 11.1.2.2. Is it possible that I can use LCM? I tried to export the application to version 11.1.2.1 and its import in 11.1.2.2 but all forms are saved as invalid.
  
  The application also uses business rules and LCM gave the following errors:
  
  Error in migration artifact, "/ Global artifacts/Business rules / Global Variables/XXXXX".
  Cannot process the artifact (XXXXXX). Type of artifact not taken in charge (Global Variable).
  
  Given that Calc Manager is the only tool of support would this cause the problem with the migration process? If so, how can I migrate the application successfully.
  
  I saw the option upgrade in the Administration of planning, but how is application to the situation.
  
  Thanks in advance.

  If you create an empty application, then stop planning and migrate the 11.1.2.1 relational database planning on top, update the SID if it isn't the user admin by default and different between the versions, start planning, you should then be able to upgrade by using the wizard.
  It was just a quick overview, because the process is roughly the same as previous versions and it was taken over several times here.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Migration planning from one server to another

  We are in 11.1.1.3. I had the planning repository copied from one server (server1) to another (Server2). had also shared services and copied the server 1 Server 2 EAS repository. When I opened the planning in Server 2, I see the name of the planning application in 1 server, and data source connection also shows the connection to server 1. How can I fix to point to Server 2? Thank you.

  You just cannot change the application like this name. If you need to change the application name, you need to do before the migration.

  Let's say your app source is S and target is owners of T. Application for S and T MUST be the same (use external if possible user)

  1. create the application T
  2. database of report copy of S to T
  3 copy of database Essbase, S to T
  4. connect to T and ensure that its pointing to the correct instance of shared services

  This will ensure that the application has been upsized excluding security and business rules. It was the old way to do this. You should use LCM in v11. It can be kind of weird if you have duplicates of names (for example, the list of tasks, web forms), but it does not work. We used LCM to migrate the application with success and its very easy to use.

• Application Migration Planning

  Hello
  
  I mentioned the previous post of migration Migration of Hyperion Planning Application
  and come out with something associated with SID, if the owner of the application to the target application is different:
  

  Go to the tables of database to the planning application and look at the HSP_USERS table, store the value of the SID user 50001

  means that I should go to the schema of the target server and copy the SID against user 50001 for later use.
  

  8 go in the HSP_USERS table and update the SID of the user 50001 id

  means paste SID against 50001 target server that I copied in the previous step (after the replacement of the schema to the target server from a schema of the source) (scheme are similar to the source and target)

  These steps are necessary, if the owner of the source/target application is not the default Administrator account.
  Once you create your empty planning on the target application, go to the table and keep the SID.

  After you migrate the schema, go and then paste the sid your stored above.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Migrating Planning 4.1 planning 11.1.3

  Try to collect some information on PMCS system 11 Upgrade.
  
  (1) is it possible to migrate from 4.1 planning to 11.1.3.
  (2) old application planning only deployed via classic Mode.
  (3) advantage of EPMA based palnning against classic mode? is it just head of Calc or do we any accessory on the performance and usability.

  Hello

  I lost count how many times ask the question of migration on here, everything you need to do is do a search
  Quick overview
  Create a new database for your planning application
  Create a data source to the database
  Create a new planning application to ensure that the admin is the same name as your old app sourceplanning
  If the owner of the application is not the default Administrator account hyperion then
  : - Go in the database for the planning tables app and HSP_USERS table, store the value of the SID user 50001
  Stop planning
  Restore the database from the application sourceplanning on the one created in the first step
  Go to the HSP_USERS table and update the SID of the user 50001 id if you were to keep the front SID
  Start planning
  Go to the web planning and you should see your app when you try and newspapers that it brings you to a screen to migrate.
  If you are demanding to migrate users as well, you need to make sure that you create in the Shared Services and then use the updateusers utility in the bin planning directory.

  You can migrate and convert from a classic application of EPMA mode if you wish.
  The choice is all yours if you want to use Classic or EPMA, boils down to how you want to control your metadata.
  Calc Manager is available for both classic and EPMA, although I wouldn't call Calc Manager a selling point for the moment.

  Don't forget that you can mark messages useful or correct.

  Ok?

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• My Migration Plan

  I inherited a vcenter 4.1 with 6 guests esxi environment.  The vcenter server resides on a physics 2008 R2 server running SQL 2005 express db on the same box.  I've got 80 VMS autour, 65ish or so are production servers.  Thereby a lot of vms and b & BS, I'm worried about the current db express and even the express bundle 2008 on an upgrade will start to have problems.  Let's add a little more guests in the near future for some projects as well.  What I want to do is to build a SQL server 2008R2 House the database on a separate virtual computer and build a new server vcenter 5.1 on a separate virtual machine.  This virtual machine contains the SSO and its default db, the inventory server and vcenter Server (connected to the new SQL 2008R2 server).  I know that I can take backups of dbs on the existing vcenter and import the data to the new sql server as I have already done this with success in tests.  I managed to install SSO and a new virtual machine inventory, but I get a certificate error that says that my CERT does not exist even if they do.  It occurred to me that copied the existing vcenter Server CERT is built with the name of the existing vcenter server and I am doing a test to install on a server by any other name.  So my plan is this:

  1. stop vcenter Server service

  2. take all my necessary backups db, vcdb, umdb, adam and CERT and move them to a network share

  3. import my dbs on sql server

  4. turn the existing the vcenter Server

  5 remote control for my new vm vcenter and rename it to the old name of vcenter and give the IP address of the old vcenter

  6 copy the CERT to the appropriate location

  7. start installing vcenter 5.1 and install sso, inventory and vcenter on the new virtual machine and vcenter point on the new sql server.

  8. once the work I would HA for the new vcenter VM and sql server.

  This plan will even work or I go about it the wrong way or do I just do the place in upgrade?  What I don't want, it is of course things go BOOM!  It is an environment of the county hospital.

  While this did not therefore plan B which was much easier.  I built a virtual machine for SS and his PB (used the sql bundle for ssodb), service inventory and vcenter server, an another vm for vcenter db (used full sql 2008r2) and a 3rd vm for the Update Manager and his PB (full sql 2008r2).  5.1 fresh installed on virtual machines that reside on the 4.1 current hosts.  the new vcenter server vm, distance to open the client and added the hosts for the new vcenter.  This disconnected the physical vcenter 4.1 server hosts and now all my virtual machines are running under vcenter server 5.1.  Now that I'm improving to 5.1 esxi hosts.  Using this method, I didn't have to worry about import and conversion of databases with old data.  When the 4.1 hosts were connected to the new server vcenter 5.1 the new database is filled with fresh information.  So, in summary, I went from a 4.1 Server physical where everything was on a single server, a virtual machine entirely would be vcserver environment with components separated between 3 servers. No error and no interruption of service for my users made for privileged business hours.  We have about 80 virtual machines on this configuration 65ish or so are production servers.

• Migration planning in 11.1.2.1 application

  Hi all
  I did not go to a total migration through LCM 11.1.2.1 of an application to another. After a little research I found a few steps to export the application, but I have not found how to import it. Perhaps I have missed.
  
  Steps I did:
  
  1 > I have created a new empty application with the admin user.
  2 > select artifact List (including security) of the source application.
  3 > set migration
  4 > save the file with a name of CopyRev system
  5 > save the file .xml on my desk
  6 > run the Migration
  
  and it was completed.
  
  Now my question is how to import it to my destination application.
  
  Thanks in advance

  Hello

  First, if your environment for source and target are the same, then you will all users and groups of shared services, in this case simply at the disposal of users for this new application so that your security is migrated when you migrate the application source. If the surroundings are different, then you must migrate users and groups first and their disposal prior to importing the security using LCM.

  To return to the import process the artifacts in the application target using LCM, you must place the file migrated in the @admin native Oracle/Middleware/epmsystem1 directory.
  Console open SSP-> file system and you'll see your file under that name.
  Select the file and you will see all of your exported artifacts. Select all if you want to complete the migration to the target.
  Follow the steps, choose the application target to which you want to migrate and perform the migration.

  Open the application and you will see that all your artifacts are migrating to the target.

  If you encounter an error during migration, we will see in the migration report.

  Thank you
  Sourabh

• Import business in the context of migration planning rule

  Hello
  
  
  I imported the Server001 business rule to server002. Import was successful. When I right click to open the business rule, it gives below error
  
  "Connection to the planning Server001 Server error."
  
  are there any extra parameter?

  Open the file in a text editor.
  say your old server was called sourceserver and your target targetserver

  Do a find and replace tiny ServerName find:-replace sourceserver:-targetserver
  Do a find and replace uppercase ServerName find:-replace SOURCESERVER:-TARGETSERVER

  This means that the applications are the same name between the servers.

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Migration planning schema (Oracle DB)

  When migrtating underlying planning schema from one environment to another, it wont bring all the metadata and the forms from the old to the new environment?

  Yes, it will certainly restart.

  See you soon

  John
  http://John-Goodwin.blogspot.com/