Cloning Discoverer End-User Layers
By Steven Chan-Development-Oracle on Aug 30, 2006
Given its utility, I'm highlighting a recent blog comment from Steve Fitzgerald, one of our Oracle BI specialists. This was in response to our In-Depth: Cloning OracleAS 10g + E-Business Suite Environments article.
For the Discoverer users of the E-Business Suite, I will point your readers to "some old-fashioned elbow grease" to fill in the gaps. This will apply to
import/export of an End-User Layer (EUL) at the database level. It may not be necessary when cloning the entire database and not modifying the EUL, but will be if creating a DEV/TEST/PROD type clone. It might save a headache or two down the line :-).
Discoverer recognizes EULs using unique reference numbers. However, if you use the database export and import utilities to copy an EUL, the new EUL (including its reference number) will be identical to the original EUL. When EULs have the same reference number, EUL consistency issues can arise if you do both of the following:
- If you modify objects in both the original EUL and in the new EUL
- Having modified objects in both EULs, if you then attempt to copy objects between the two EULs using the Discoverer Export Wizard and Import Wizard (or the Discoverer /export and /import commands)
issues, run the eul5_id.sql script as the owner of the new EUL. The eul5_id.sql script gives a new refererence number to the new EUL and thereby avoids any potential EUL consistency issues.