This discussion is archived
3 Replies Latest reply: Jul 8, 2013 4:22 PM by Michael Armstrong-Smith RSS

Discoverer reports failing after import from another instance

user518071 Newbie
Currently Being Moderated
I've migrated Discoverer reports using export/import option.After opening reports in new instance,I'm getting the following error for some reports :

Can not join tables used in the work book Item dependency not found in the EUL,Attempt to open workbook failed?

I checked disco administrator for these reports and all these reports are based on custom folders.These custom folders are based on query and they are not joined with any other folders.


Thanks,
Kiran.
  • 1. Re: Discoverer reports failing after import from another instance
    barrym Newbie
    Currently Being Moderated
    I have encountered this. I think the problem is caused by EUL IDs not being identical between the instances. EUL IDs are sequential IDs so if you are doing development in one instance not done in another, the EUL IDs may not match. The same EUL ID value may exist in both instances but refer to different things. When you import, there is an option to select matching by name or by EUL ID. I normally choose the by name option.

    You can try running the Discoverer Workbook Dump Utility D51WKDMP.EXE which lists all of the Workbook components and will list errors if the EUL_IDs have problems. This may help you identify what may need to be changed to get the workbook imported successfully.
  • 2. Re: Discoverer reports failing after import from another instance
    1008509 Newbie
    Currently Being Moderated

    Hi Kiran,

    why u are getting the problem is we are doing mistake in the  naming convention of the custom  folder and as well as item clauses names which are u given in the one instance is not equal to another instance .so

    what i am suggesting is please copy the files names and try it will definitely work.

     

     

    Regards

    Salemula

  • 3. Re: Discoverer reports failing after import from another instance
    Michael Armstrong-Smith Oracle ACE
    Currently Being Moderated

    Hi Kiran

    Try re-importing and matching on Names and see if that helps.

     

    Having End User Layer metadata out of sync and maintained in more than one place is a recipe for disaster. The best way to develop Discoverer metadata is to have a three-stage environment using Development, Test and Production.

     

    You should never add new Production metadata without migrating from Test which in turn is migrated from Development. Adding new metadata in Production will cause the unique IDs to be updated. The next time you migrate from Test, checking the box to match on identifiers will cause problems. Of course if you also take the time to make sure than even identifiers are unique then you will not have any issues.

     

    Best wishes

    Michael

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points