Workbook Migration Restore

Hi All,
I am working on migration of workbooks to BI 7 enviornment.
I want to know the answer or pointers for the following questions,
1. What is the best strategy to migrate -
     Open the workbook in each system in Bex 7 analyzer and 
     save it.
   or Save in new tool in development system and transport to production.
2. How to restore the migrated workbook to old BW 3.5 version.
3. What kind of common issues are faced in workbook migration.
Regards,
Niraj

Hi Chetan.
Thanks for the response.
I have already read the blog sent by you. But it does not  answers the questions which I raised.
I s there any way to restore workbook to 3.5. We can restore the queries using program COMPONENT_RESTORE.

Similar Messages

  • Workbook Migration-System error in program CL_RSR_XLS_VIEW and from ASSIGN_

    Hi Experts,
    We are migrating workbooks from 3.x to BI 7. While opening the workboon from BI 7 Analyzer we are getting the following System Error  and Disconnecting from BW server.
    'Program Error in class SAPMSSY1 method UNCAUGHT_EXCEPTION. System error in program CL_RSR_XLS_VIEW and from ASSIGN_QUERY_2_DP03'."
    We are at support pack level 17 and GUI - 710 with patch level 8.
    If you have experienced with the above errors. Please respond.
    Thanks
    DB

    Hi Naveen,
    In migration you will get all these errors related to Front end. First save the Existing 3.x workbook   so that the old version of the workbook will be saved into new Excel version (2003). now try to migrate the workbook , this time you will not get this error.
    The root cause for this problem would be all your workbboks have been created erlier in very old version of  Excel.
    Thanks
    DB

  • Workbook migration BEx 3.5 to Analysis 1.4 SP3

    Hi togther,
    we are currently in the migration phase at customer site. And we have many performance issue when we start the migration of  bex workbooks to analysis workbooks. And we would like to know how we could monitor the migration.
    Is there any possibility to create a trace file for the migration where i can see the reason of the system crash?
    And the second question is:
    Is there a possibilitity to get an progress bar for the migration? I mean the user dont know is the application crashed or is the migration still in progress.
    Thanks in advance and best regards
    Christian

    Hello Christian,
    On the first question, are you seeing the log for the conversion? (shown in Figure 4 here SAP BusinessObjects Analysis Office 1.3 – BEx Workbook Conversion Details + Q&A )
    Maybe the log will help with the crash?
    I don't work for SAP so I can't answer your second question.  Maybe enter this in Idea Place as an idea (ideas.sap.com)
    Tammy

  • 3.5 to NW2004s : Workbooks migration

    Hi ,
    Is there any program to migrate  workbooks from 3.5 to NW2004s version or do we need to this manually ( i.e opening every workbook in NW2004s and resaving it).
    Regards
    MB

    See the below link,
    http://gnanamax.com/Documents/BI%207.0%20Functional%20Upgrade%20-%20Migration%20points.pdf
    Hope this will help you..?
    MSR

  • Migrate, restore from Time Machine or fresh install

    Folks
    Getting an MBP today and migrating from MBA. Should I fresh install, use the migrate tool or restore from Time Machine?

    You are going to get several answers here depending on users' opinion and experiences. My own view, having done the Time Machine backup as demo in a class, is that, if you have the time and all the settings written down, the best way is to start from scratch. Indeed, the last two Macs I bought, I even installed the OS myself, despite them being out of the box.
    Having written that, I do find Time Machine a useful facility and it is possible to selectively bring the data back, which is really quite useful with a new machine. This would be a great tool in the case of a stolen computer or if a hard disk had crashed and it was necessary to get up and running quickly. As a note, I still found that with the TM restore, certain parts (such as Mailboxes and some other network related security stuff) still needed setting up again.
    I did use the migrate tool once and was not over-convinced although I understand it has been updated. Someone else should offer an opinion on that.
    If time is of the essence, go for the TM or Migrate tool. If you want a more stable and secure environment (perhaps that backup could bring over a problem), go from scratch with a selective backup.

  • Report and workbook migration

    Hi all,
    what are the steps that need to be followed to migrate 3.X queries and workbooks to BI 7.0(2004s)? Or do they automatically get converted?
    And is it possible to upgrade the frontend to BI 7.0 and use the new reporting (front end)functionalities, while the back end is still on 3.X?
    Any insight or help would be appreciated and rewarded.
    Thanks,
    Mav

    This question is a little ambiguous then as Heike and I have different interpretations. When you say "2004s backend", what do you mean? You need a 2004s spack to use the new functionalities (both backend and frontend).
    Within this new stack, the old 3.x runtime exists and you can use it. Within the 2004s stack, you can use 3.x Infosource, transfer rules, update rules. I view this as a 3.x backend in a 2004s environment. So if your dataflow is using 3.x, that doesn't limit you to use only the 3.x tools. You can use the new tools.
    I consider using transformations, DTP, etc as 2004s backend functionality.
    So to clarify, what are you considering a 3.x backend? The technical requirement is to be on a 2004s stack, which I outlined in my original post... The delineation is the 3.x backend concept or 2004s backend concept in the new stack can both be used and that doesn't influence which frontend tools you can use.

  • Workbook Migration Issues

    Hi Experts,
    We are migrating 3.5 workbooks to 7.0 .  Can anyone please let me know what could be the issues in the new workbooks due to migration.
    Thanks,
    AM

    Hi,
    There will be various issues like; Format issue( lost format, vba,macro codes etc.), design Issues etc.
    To retain the fromat after migrating the workbook to 7.0: I did this, in following way:
    -save it. At this stage the format is going to be exactly same as 3.x workbook. If you start refreshing, you loose format.
    -Go to design mode and deselect 'apply format' option and save it again. Here you can see that you have lost the format.
    -Format it again and save it.
    -This will work now when you refresh. Refreshing takes.
    Pls chk this links;
    /people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools
    /message/3502939#3502939 [original link is broken]
    /message/3693377#3693377 [original link is broken]
    /message/3502939#3502939 [original link is broken]
    http://www.techonthenet.com/excel/macros/refresh_pt2.htm
    http://www.dicks-blog.com/archives/2004/09/27/ask-to-refresh/
    Re: Where are the BEx variable stored
    http://help.sap.com/saphelp_nw04/helpdata/en/f1/0a55f9e09411d2acb90000e829fbfe/frameset.htm
    Hope it Helps
    Regards
    CSM Reddy

  • How does migrating/restoring Mac OS X Server compare to Mac OS X?

    I’m thinking of reinstalling the system software on our server (we have a bunch of problems we can’t get rid of) and I was wondering what the process is like.
    We have a Time Machine backup and I was wondering how similar the process is to reinstalling/migrating a client installation of Mac OS X?
    For instance does it give you the option to only restore files and data (such as Wiki content), or are you forced to restore all settings, users and preferences as well?
    I’d prefer to just restore files and data and then manually recreate users and settings, in the hope of ridding ourselves of some of the problems we have (such as iCal server constantly asking for passwords and an inability to add or remove users using Server Preferences).

    It's more a case of looking at the logs and not really knowing what I'm doing. Suffice to say I've taken the trouble-shooting road to my limit.
    Mainly we have issues with iCal Server which keeps asking users for their passwords:
    http://discussions.apple.com/thread.jspa?messageID=5936657
    And now we have this error 14120, since 10.5.6, that causes us not to be able to add or remove users in Server Preferences:
    http://discussions.apple.com/thread.jspa?messageID=8773646
    I assume by the advice I'm getting from both of you that the migration tool for Mac OS X Server doesn't include the ability to bring only data files over minus all the settings and users?
    I'm happy to do a clean wipe. I just want to be sure I can pull across calendars and Wiki data reasonably easily if I do it manually, as I'm not an IT pro. I'm only a CAD Manager and all my knowledge with these things is only through day-to-day experience.

  • Error while migrating discoverer Workbook

    Hi All,
    I am migrating Business Area and Work book from one instance(QA) to another(Production) DB instance.
    I have successfully did export of business area and import in production instance.
    For workbook migration I have followed the below mentioned steps.
    1) Open QA instance and open the required workbook.
    2) Do "Save As" of the workbook to local machine as ".DIS".
    3)Then Login to Prodcution Open the workbook from the local machine. But in that case it gives following error
    " Cannot join tables.Item dependency "" not found in EUL. "
    "Attempt to open workbook failed" Anyone can help me to solve this issue. Please.
    Thanks
    Alaka

    Hi Janet
    Here are some more notes from my private collection of tips and tricks:
    Discoverer workbooks are very picky when it comes to opening up against an end user layer. Basically, here is what happens:
    All EUL objects have an ID number and a name. When Discoverer saves a workbook it saves both the ID number and the name of every essential object (business area, folders, items and joins) that is used within the workbook. The next time Discoverer opens the workbook it looks at the ID numbers of the objects and tries to find them in the EUL. If it cannot find an object by its ID number it tries to locate it using the object's name. If an object cannot be located either by its ID number or by its name you will get the dreaded Item Dependency error.
    OK, having got that out of the way, if you delete a folder from within the EUL and re-create it you will lose the ID number of the folder and all of its associated objects (items and joins). The only way Discoverer will be able to open this workbook now is if everything within the folder is named EXACTLY the same way (including underscores and casing of the name), otherwise the workbook will not open. Discoverer will report the error message that you are seeing.
    So what can you do? Well, you need to have some way of finding out what the old folder name(s), item names and join names were. Also, you need to make sure that all items that were not hidden are not hidden now. There is no need to worry about the names of hierarchies or lists of values. These are not stored within a workbook and are only hooked in at runtime.
    Seems like you have to somehow painstakingly determine what all of the item and join names were in your old folder(s) and re-create them 100% the same way in the new folder(s). By the way, when the workbook gives you the error message does it also give you an opportunity to assign al alternative item to the item that it can no longer find a value for? This may work but, in my experience, usually doesn't!! It only works if the missing dependency is an item, it won't work if the error is being caused because you have got a join name wrong. Unfortunately, joins MUST have the same name exactly otherwise there is just no way to open the workbook.
    Best wishes
    Michael

  • New ID for migrated Workbook

    Hi Experts,
    As per the Migration Stratagies that SAP has provided says that the Migatred workbook will save with Name/ ID. But, I Observed that It is saving with the OLD Name/ID only. If you have same experience with Workbook Migration Please share your ideas 
    Thanks
    DB

    That is for standard workbooks (business content).
    For user generated it does not.

  • DB2 migration v8.1 to v9.5 in SAP 6.40

    Hello Sirs,
    I'm planning the migration of the databases of v8.1 to v9.5 in SAP 6.40.
    I have a few questions regarding this issue... if anyone knows please tell me.
    1. Is there any inconvenience of having DEV system under DB2 9.5 and the other systems Productive and Quality with DB2 8.1?
    2. Does anyone found any tricky problem in this database migration 8.1 -> 9.5?
    thanks.
    regards,
    Filipe Vasconcelos

    Hi Filipe,
    Once the instance is migrated to a higher release (V9.5 from V8.2) there is no way to "demigrate" it. You would need to do the following:
    1. Uncatalog the database IF IT IS NOT MIGRATED (Drop if it is migrated).
    2. From the new software directory (for eg: /opt/IBM/db2/V9.5/instance), drop the instance using the db2idrop command.
    3. From the old software directory (for eg: /usr/opt/db2_08_01/instance), recreate the instance using the db2icrt command.
    4. Recatalog the database IF IT WAS NOT MIGRATED (Restore if it was migrated).
    5. Reimport the configuration that was backed up.
    6. Reinstall db2 license files.
    This is obviously at a high level but covers the basic idea. Procedurally, I would suggest that you perform and document this process in the sandbox environment before upgrading your Q and P environments.
    Hope this helps,
    Sameer

  • Thinking of a new mac, will TM history migrate over?

    I am looking at switching from my mbp to an iMac. I know that I can use migration assistant to move my docs, apps, etc to the new computer, but I would like to know if this includes TM.
    I sure do hope so, because it would be very unfortunate if I had to start TM from scratch.
    I would obviously be using the same drive to which my current TM back-ups are stored.
    If this option is not native to migration assistant, are there any how-to that I could be pointed to?

    in a different scenario, whereby the MBP had died, you could Migrate the most recent TM back-up into the new Mac (there are 4 options at the Migrate/Restore from TM) and so resume at where you left off (PPC and Intel limitations notwithstanding on some apps), but the history of backups from the MBP would then be unavailable on the new Mac.
    So, if you used TM as a device to archive old files, restore them in TM if you needed them, you'd be stuffed in the scenario of dead MBP.
    Unless, I guess, you do the hack of making both Macs have the same MAC code (sorry about the pun) which seems very fiddly and not wholly successful.
    So, on the one hand TM is heaven sent. On the other hand, in the event of hardware failure or misunderstanding of the concept, all history is lost.
    Hmmmm.

  • Cannot join tables used in the workbook. Join "" not found in the EUL. Atte

    Trying to migrate workbooks from one instance to other using discoverer 10.1.2.48.18 i am getting the following error
    Unable to open the worksheet requested.
    - OracleBI Discoverer was unable to find the worksheet that was requested.
    - BIB-10310 An unknown exception occurred.
    - Cannot join tables used in the workbook. Join "" not found in the EUL. Attempt to open workbook failed.
    but its fine one instance , and in prod i am getting above weird error.
    does anybody know how to rectify this.

    Note:267476.1 - for those who can't get into metalink but still need to know the answer
    Subject: Discoverer Workbook Fails With 'Cannot join tables.Item dependency "" not found in EUL' After EUL Migration, Importing Or Cloning
    Doc ID:      Note:267476.1      Type:      PROBLEM
    Last Revision Date:      28-APR-2005      Status:      PUBLISHED
    The information in this document applies to:
    Oracle Discoverer - Version: 4.1 to 10.1
    This problem can occur on any platform.
    Symptoms
    Opening a workbook migrated from one instance to another results in the following errors:
    * Unable to load EUL item ...
    * Cannot join tables. Item dependency "" not found in EUL.
    * Illegal operation... DIS4USR OR DIS5USR caused an invalid page fault in module....
    If using the workbook dump utility, you may notice:
    * Found in EUL by id *** Name has changed to .. where the new name is really the wrong column
    It seems that items are matched by internal item identifiers (IDs) and not by developer keys and names.
    Changes
    Migrating from one environment to another. For example, you may have performed a database export / import of the EUL schema from DEV to TEST
    Cause
    The timestamp is the same for both EULs, what can be confirmed by the following SQL statement:
    * Discoverer 4:
    SQL> select ver_eul_timestamp from eul4_versions;
    * Discoverer 9.0.2 , 9.0.4, 10.1 the script is:
    SQL> select ver_eul_timestamp from eul5_versions;
    If the result of the sql output is the same in both EULs, it means that timestamp of both EULs are the same. Discoverer assumes that the EUL are exactly the same (e.g. this can happedn when one of them is created with export/import of the other EUL schema using database export/import utilities) and this is the reason it tries to match items by identifiers and not by developer keys or names.
    Solution
    Change the column ver_eul_timestamp in the eul4_versions (4.1) or eul5_versions(9.0.2 - 10.1)tables to be something different in the destination EUL. The format of this column is like year:month:day:seconds:milliseconds
    Example:
    * Discoverer 4.1:
    sql> update EUL4_VERSIONS set VER_EUL_TIMESTAMP =TO_CHAR(SYSDATE, 'YYYYMMDDHH24MISS');
    sql> commit;
    * Discoverer 9.0.2:
    SQL> update EUL5_VERSIONS set VER_EUL_TIMESTAMP = TO_CHAR(SYSDATE, 'YYYYMMDDHH24MISS');
    sql> commit;
    * Discoverer 9.0.4 -10.1:
    Run the script: EUL5_id.sql as the eulowner ID
    o For 9.0.4 -- This is found on a PC with the Discoverer Administrator installed in drive:\Oracle Home\discoverer\sql
    o For 10.1.0 -- This is found on a PC with the Discoverer Administrator installed in drive:\Oracle Home\discoverer\util
    This is documented in:
    Oracle® Business Intelligence Discoverer
    Administration Guide
    10g Release 2 (10.1.2.0.0)
    Part No. B13916-02
    http://download.oracle.com/docs/pdf/B13916_02.pdf
    Chapter 4 "About copying EULs and EUL objects by exporting and importing"
    Oracle® Discoverer Administrator
    Administration Guide
    10g (9.0.4)
    Part No. B10270-01
    http://download.oracle.com/docs/pdf/B10270_01.pdf
    Chapter 3 "About copying EULs and EUL objects by exporting and importing"
    References
    Bug 3202329 - Migrating Workbooks Between Instances Shows Incorrect Column

  • Date of alerts after migration

    After migration - restore of backup (from 2.6 to 4.0), alerts are restored, but not with original date of creation on old system, but all of them with same date&time of restoration on new system? Can it be fixed somehow?

    Alerts will migrate along with data. Couple of things make sure after upgrade.
    Your WFE servers are in exchange relay to send emal to out of network users.
    If URL of web application / site collection change then some case you have to update the url.
    It is highly recommended that test your migration before performing in production.
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • How to export / import workbook by discoverer plus

    Hi,
    I am an new user of oracle discoverer. We have two database there DB_DEV and DB_PROD. After doing our development in DB_DEV we need to release this development to DB_PROD. But here i am not able to do this. I had tried Export facility of discoverer desktop, but it create export as excel/png file. Could you please guide me how can i resolve the problem.
    Thanks
    Soumen

    Hello
    I have a free document on my downloads page at: http://ascbi.com/downloads.htm called Workbook Migration Guidelines. It is a PDF and while it specifically talks about migrating from Discoverer 4i to 10g you could easily use the information inside to export from one EUL to another EUL at the same level using different users. I think you might find this a useful document.
    Rather than export using the command line, in 10g you can use Administrator and export workbooks using selected objects from the database.
    Best wishes
    Michael

Maybe you are looking for