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

Question

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.

Answer 1

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