After Importing A Discoverer Applications Mode EUL Via EULAPI Utility Or Admin Client, Some Folders Are Missing (Doc ID 1082644.1)

Last updated on NOVEMBER 17, 2016

Applies to:

Oracle Discoverer - Version 10.1.2.1 to 11.1.1.6.0 [Release 10.1.2 to 11g]
Information in this document applies to any platform.
***Checked for relevance on 17-Nov-2016***

Symptoms

After importing an Apps mode EUL that was previously exported, via eulapi utility or Discoverer Admin client, (both) as a database user, you find several folders are missing.

You may also encounter errors like :

"No join predicate for this foreign key"

 

Changes

You have a valid EUL that contains many folders.
You have exported the EUL through eulapi utility. (Command line example:

  eulapi -connect eul_us/eul_us@db1 -export /oracle/thse_disc/test.eex -all -log /oracle/thse_disc/test_export.log



You have imported the EUL trough eulapi utility. (Command line example:

. eulapi -connect eul_us/eul_us@db1 -import /oracle/thse_disc/test.eex -identifier -preserve_workbook_owner -import_rename_mode refresh -auto_refresh -log /oracle/thse_disc/test_import.log)



When you open the EUL with OracleBI Discoverer Administrator, you find the EUL has been damaged with many folders not displaying.

 

Note: The same scenario is valid if the export / import was done using OracleBI Discoverer Administrator client as a database user e.g. EUL Owner.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms