Forum Stats

  • 3,782,750 Users
  • 2,254,684 Discussions
  • 7,880,152 Comments

Discussions

How does the system rename objects when using eulapi to import EUL objects?

TR7
TR7 Member Posts: 17 Blue Ribbon
edited Oct 9, 2019 9:53AM in Discoverer

I am trying to determine which objects were renamed and what the new names are after execution of the the Discoverer EUL Command Line for Java (running the eulapi script with -import command to import an .eex file).

Is there documentation that describes how the system determines the new name? Does the system simply append a number to the old name?

Also, are there logging options that can generate more detailed logs that will show what objects were determined to match, which were renamed, and what the old and new names are?

Using Oracle BI Discoverer Viewer V11.1.1.7.0.

TR7

Best Answer

  • sbeck-Oracle
    sbeck-Oracle Member Posts: 116
    edited Oct 2, 2019 7:41AM Accepted Answer

    Hello,

    There is a number appended to the actual name of the item being "renamed".  Whether that is the object being imported or the existing object.  Please be aware that every object contained in the EUL has an internal identifier.  The internal identifier does not change for existing items being renamed.  Items being imported are given a new identifier.
    In order to keep the EUL "cleaner", it is recommended to use the Refresh option.  This will prevent "duplicates" of anything being imported that already exists in the EUL (Item, Folder, BA, Item Class, etc.).  Refresh also maintains the original internal identifier. 
    The only drawback to using Refresh is anything removed from the "FROM" EUL that was exported, will still remain in the "TO" EUL.  For example, if Field1 was removed from FolderX in EULa prior to export, when you import into EULb with refresh option, Field1 will still exist in EULb FolderX.  The import does not "match" content that exists against that being imported.  Just refreshes the objects of the same name.

    There is no other logging that will provide added information.

    Regards,
    Sharon

    Please be aware premier support for Discoverer 11g ended June 2014.  Version 11.1.1.7.0 is the final / terminal release of the Discoverer product.  Discoverer is under sustaining support, which limits our ability to assist you.  Please review the alert section at the bottom of this update.

    Discoverer is at end of life.  Any software update (OS, browser, Java, WLS, EBS, etc.) released after June 2014 has not specifically been certified or tested and may cause issues for Discoverer.  Therefore, it is important to maintain a stable Discoverer environment for as long as it takes to move to OBIEE or other replacement.

    TR7TR7

Answers

  • sbeck-Oracle
    sbeck-Oracle Member Posts: 116
    edited Oct 2, 2019 7:41AM Accepted Answer

    Hello,

    There is a number appended to the actual name of the item being "renamed".  Whether that is the object being imported or the existing object.  Please be aware that every object contained in the EUL has an internal identifier.  The internal identifier does not change for existing items being renamed.  Items being imported are given a new identifier.
    In order to keep the EUL "cleaner", it is recommended to use the Refresh option.  This will prevent "duplicates" of anything being imported that already exists in the EUL (Item, Folder, BA, Item Class, etc.).  Refresh also maintains the original internal identifier. 
    The only drawback to using Refresh is anything removed from the "FROM" EUL that was exported, will still remain in the "TO" EUL.  For example, if Field1 was removed from FolderX in EULa prior to export, when you import into EULb with refresh option, Field1 will still exist in EULb FolderX.  The import does not "match" content that exists against that being imported.  Just refreshes the objects of the same name.

    There is no other logging that will provide added information.

    Regards,
    Sharon

    Please be aware premier support for Discoverer 11g ended June 2014.  Version 11.1.1.7.0 is the final / terminal release of the Discoverer product.  Discoverer is under sustaining support, which limits our ability to assist you.  Please review the alert section at the bottom of this update.

    Discoverer is at end of life.  Any software update (OS, browser, Java, WLS, EBS, etc.) released after June 2014 has not specifically been certified or tested and may cause issues for Discoverer.  Therefore, it is important to maintain a stable Discoverer environment for as long as it takes to move to OBIEE or other replacement.

    TR7TR7
  • TR7
    TR7 Member Posts: 17 Blue Ribbon
    edited Oct 4, 2019 8:39AM

    Thank you Sharon.

    I have a follow up question: if you are importing an .eex file, and the only difference between the object being imported and the existing object is an update to custom SQL, and you use the refresh/merge option, then does the import replace the custom sql in the existing object with the updated custom sql; i.e., the custom SQL is replaced?

  • sbeck-Oracle
    sbeck-Oracle Member Posts: 116
    edited Oct 9, 2019 9:53AM

    The SQL will be replaced.

    Regards,
    Sharon

    TR7TR7