Which Discoverer Eul Tables Stores The Folder Query
Why is the End User Layer useful?The EUL insulates Discoverer end users from the complexity usually associated with databases. It provides an intuitive, business-focused view of the database using terms that Discoverer end users are familiar with and can easily understand. This enables Discoverer end users to focus on business issues instead of data access issues.What does the EUL contain?The EUL contains the metadata that defines one or more business areas. A business area is a conceptual grouping of tables and/or views that apply to a user's specific data requirements. Business areas can be set up to reflect the needs of the user or group of users accessing the EUL.For example, an accounting department might have an accounting business area that represents data about budgets and finance, while project leaders in an engineering department might have a business area specifically for projects requiring budget information. Although some of the columns may be the same, the exact combination of tables and views for each department may be different.Discoverer creates the EUL tablesThe EUL Manager dialog enables you to create or delete the set of tables that make up an EUL.When a Discoverer manager defines folders and items in a business area using Discoverer Administrator, Discoverer generates the appropriate SQL statements (that define the selections from a table, view, or column) and stores them in the EUL tables.
When a Discoverer end user executes a query (in Discoverer Plus or Discoverer Viewer), Discoverer generates the corresponding SQL statement and sends it to the database, which in turn returns the results to display in Discoverer. The Discoverer end user does not have to understand any SQL to access, analyze, and retrieve data. It is all handled by Discoverer.Discoverer exports/imports EUL objectsYou can export EUL objects (e.g.
Business areas, workbooks, folders, items) from one database and import them into another database. For example, you might want to move EUL objects when transitioning from a development environment to a production environment.You can import and export EULs and EUL objects in the following ways:.using the Discoverer Export Wizard and Import Wizard.using the Discoverer command line interface.using the standard database export/import commandsFor more information, see.Notes.The EUL preserves the database's data integrity.
Which Discoverer Eul Tables Stores The Folder Query In Word
Nothing that you or the Discoverer end user does with Discoverer affects the application data in the database; Discoverer only affects the metadata held in the EUL. There are however, certain PL/SQL functions that can affect the data in the database (for more information, see your database administrator).Although it is possible to edit EUL tables (e.g. By using SQL.Plus), Oracle is unable to support such edits, and therefore recommends that you do not attempt to make edits to EUL tables. What are End User Layer owners?An End User Layer (EUL) owner is the database user that an EUL is created for.A database user can only own one EUL.
If you are connected to your own EUL and you attempt to create a new one, Discoverer Administrator prompts you to delete your existing EUL. If you create an EUL for a database user that already owns an EUL, Discoverer Administrator prompts you to delete the existing EUL before creating the new one.The EUL owner maintains and modifies their own EUL and can grant access to the EUL to other users. Depending on the privileges given to the other users, those users can use and make changes to the EUL.When you create an EUL, you specify who has access to it, as follows:.every user in the database (PUBLIC access).only the EUL owner (PRIVATE access)Note: It is recommended that you specify PRIVATE access, where security is an issue. You can subsequently define business area access and privileges for users and roles as required.To change access to an existing EUL, you must be logged in as the owner of the EUL or as a user who has the following Discoverer task privileges:.Administrator.Set PrivilegesFor more information, see. How to create an End User Layer in a new database userNote: This feature is not available with non-Oracle databases.
Figure 4-3 Create EUL Wizard Step 2 dialog.Specify the default and temporary tablespaces for the new database user.If you are unsure which to choose, see your database administrator. For more information, see the.Click Finish.Discoverer Administrator displays the Creating EUL progress bar and creates a new database user and new EUL in that database user.When the new database user and EUL have been created, Discoverer gives you the option to install the Discoverer sample data in the new EUL. For more information, see.
How to delete an End User LayerYou might want to delete an EUL for a number of reasons. How to view or change the default End User LayerYou can view or change which EUL is the default EUL for the current database user (i.e. The EUL used when the current database user connects to Discoverer Administrator).Note: You can only select an alternative EUL if the database user has access to more than one EUL.To view or change the default EUL:.Choose Tools Options Default EUL tab to display the.(optional) Click the EUL that you want to use next time you connect as the current database user and click OK. About copying EULs and EUL objects by exporting and importingTypically, you will want to:.backup or archive EULs.distribute EULs to other locations.copy business areas between EULs (for more information, see ).copy EUL objects (e.g.
Business areas, folders, hierarchies, calculations) from one EUL to another.apply patches to a production environmentThere are a number of different ways to copy EULs and EUL objects, depending on whether you want to:.copy specified EUL objects into another EUL.copy an entire EUL and recreate it as a new EUL.copy the database user that is the EUL ownerIn all these cases, you perform an export operation followed by an import operation. For more information, see.If you use Discoverer Administrator to export EULs or EUL objects, you will create a Discoverer EUL export file (with an.EEX suffix). Having created an.EEX file, you can then use Discoverer Administrator to import the.EEX file.Note that you can import.EEX files:.that have been exported from Discoverer Release 3.1 and earlier (these EUL export files are standard text files).that have been exported from Discoverer Release 4.1 and later (these EUL export files are in XML format, although they still have an.EEX extension).
About using the Discoverer Export Wizard and Import WizardYou use the Discoverer Export Wizard to export EUL objects to an EUL export file (with a suffix.EEX). About using the Discoverer command line interface to export/import EUL objectsYou use the Discoverer command line interface to export/import EUL objects without using the Discoverer user interface. Figure 4-5 Export Wizard: Step 2 dialogYou use the above dialog to specify a name and location for the export file.Click Browse to display the Save As dialog.This enables you to browse for a location to save the EUL export file.Enter a suitable name for the exported EUL.(optional) Select the Generate XML for exported workbooks check box to save any workbook definitions in XML format.This enables you to view workbook definitions in an XML browser.Note: The export file (.EEX) is always in XML format but workbooks by default are saved inside it as a binary to save space and time. Select this check box to save the workbook definitions additionally as XML inside the export file.(optional) Select the Save export commands to a text file (.txt) check box to save the export commands that created this export to a text file.This creates an additional file containing the commands used to create this export and applies the file extension.txt. This file can then be used in conjunction with the command line interface (for further information about the command line interface, see ).Click Finish to create the export file (and any additional files selected) in the specified location and display the Export Log. Figure 4-9 Export Wizard: Step 2 dialog.Use the Which objects do you want to export? Drop down list to display the EUL object types that you want to export to a file.For example, folders, item classes and item hierarchies.Note: If you select a business area above, Discoverer exports just the definition of the business area and not its folders and items.
Dead effect 2 offline or online. How to export End User Layer objects using the Discoverer command line interfaceUse this option to copy EUL objects typically from one database to another, by exporting them to a Discoverer export file (.EEX) and then importing the.EEX file (possibly to another database) using the command line interface. This is the first of two tasks that enable you to copy EUL objects. How to import End User Layer objects using the Discoverer command line interfaceUse this option to import EUL objects, possibly into a new database. Before you can complete this task you must export the EUL objects to a Discoverer export file (.EEX) (for more information, see ). This is the second of two tasks enabling you to copy EUL objects.To import End User Layer objects using the Discoverer command line interface:.Use the Discoverer command line interface /import option to import the EUL objects into the new EUL owner.For example, to import the vidstr.eex file, created above you might type the following:D:orantbindis51adm.exe /connect eulowner/eulowner@orcl.world /import 'D:vidstr.eex'For more information about importing EUL objects using the Discoverer command line interface, see.
How to export an EUL using the standard database export utilityUse this option to export all business areas, EUL tables and saved workbooks to a database dump file (.DMP).To export an EUL using the standard database export utility (assuming the EUL resides on an Oracle9 i (or later) database and you are using a machine on which you have installed Oracle Developer Suite):.Display a command line window (e.g. How to import an EUL using the standard database import utilityUse this option to import the EUL business areas, EUL tables and saved workbooks from a database dump file (.DMP) into a new EUL owner on the new database.Note: It is recommended that this database user owns no other tables.To import an EUL using the standard database import utility (assuming the EUL resides on an Oracle9i database and you are using a machine on which you have installed Oracle Developer Suite):.Display a command line window (e.g. How to import EUL objects from a file using the Import WizardUse this option to import EUL objects (e.g. Business areas, folders, hierarchies, calculations) from one EUL in order to re-use them in another EUL.
You use an export file (.EEX) to update an existing EUL with selected EUL objects. For example, when applying a change to a production business area. For more information about exporting EUL objects, see.To import EUL objects from a file using the Import Wizard:.Choose File Import to display the.
Figure 4-12 Import Wizard: Step 2 dialogThis dialog enables you to specify how Discoverer Administrator processes matching objects from another EUL. For more information about matching objects from another EUL, see.Specify what action should occur if two objects match.An object means any EUL object, for example, folder, item, calculated item.Specify whether to preserve display related properties (only available if the Refresh the object radio button is selected).Specify how you would like objects to be matched up.Specify whether the current user should take ownership of imported workbooks.Click Next to display the. Figure 4-13 Import Wizard: Step 3 dialogThis dialog enables you to start the import and monitor its status as each EUL object is processed.Click Start to begin the import.Hint: You can abort the import at any point by clicking Cancel. For example, you might want to abort the import if there are warning messages in the Import Log.(optional) After a completed import, click Save log.
To save the status information to a text file in a specified location.Click Finish to close the.Notes.If you perform a complete import, the Data tab in the Workarea is updated to reflect the EUL objects imported, according to the match options that you have chosen.During the import of an EEX file where Discoverer Administrator cannot find joined folders a warning message is displayed in the Import Log dialog (for more information about exporting EUL objects and joins see. What are identifiers?Identifiers are unique names that Discoverer Administrator uses to identify unique EUL objects (and workbook objects in Discoverer Plus and Discoverer Viewer).Discoverer Administrator uses identifiers to recognize when an object imported from another EUL refers to the same business object in the EUL you are importing into. This enables customized (or patched) EUL objects to be preserved. For example, a folder named Sales in EUL A may refer to the same folder named Sales Figures in EUL B. Both folders have the same identifier and can therefore be recognized as referring to the same EUL object.Identifiers are visible in Discoverer Administrator but are hidden from Discoverer Plus users.Typically, you will never need to alter an identifier. Indeed, changing identifiers is not advisable because it can affect the relationships between EUL objects. However, in some cases you might want to modify identifiers.
For example, you might want to modify identifiers:.to comply with strict naming conventions.to re-create an object with a specific identifier because the object was incorrectly deleted from the EUL and needs to be re-created with the same identifierIn a future release of Discoverer, there will be a change to the valid characters that can be used in identifiers. The following characters will continue to be supported for use in identifiers in future releases of Discoverer:.the letters A to Z in upper case.the letters a to z in lower case.the numbers 0 to 9.the underscore character (i.e. )However, the following characters will be de-supported in future releases of Discoverer:.the exclamation mark (i.e.!).the tilde symbol (i.e. ).the asterisk symbol (i.e. ).the left and right parentheses characters (i.e. ( and ) ).the single quotation mark (i.e. ' ).the hyphen character (i.e.
What are the space requirements and storage parameters for a typical EUL?The minimum default tablespace of 3MB suggested in the is based upon storage parameters that the EUL specifies when creating database objects for the EUL. If you install the tutorial, the figure of 3MB will be exceeded.A newly created EUL has the following space requirements:.approximately 2.8MB without tutorial data.approximately 3.8MB with tutorial dataThe amount of space that is actually used will depend on other factors, including the block size specified for the tablespace in which the EUL is created.As an approximate guide, adding a typical business area to an EUL will increase the size of the EUL by 1MB. The more complicated the business area (e.g. The more summary folders and complex items it contains), the more space the business area will require.A default tablespace of 10-20MB will be adequate under normal conditions, but the amount of default tablespace required is determined by the amount of metadata that defines your EUL. What is a suggested workflow for initial EUL development and ongoing maintenance?There are typically three steps in the EUL creation and maintenance lifecycle:.Step 1: Prototype and design a new EUL in a development environmentAs the Discoverer manager, you will usually want to create the first-cut of a new EUL in a development environment rather than on the production database. To enable you to do this, the development environment must contain the same data tables that are to be used on the production database.Creating the EUL in a development environment enables you to develop business area design without compromising the performance of production systems.Having created business areas, folders, and items, you can create prototype workbooks. Get these prototypes reviewed by end user representatives in the development environment.
When you have agreed on the workbook definitions, save them to the development environment database.Step 2: Move the new EUL from a development environment to a production environmentWhen you and the end user representatives are satisfied with the EUL, you are ready to move the EUL from the development environment to the production database.The first time you move the EUL from the development environment to the production database, we recommend you use the database export/import tools. Take a database export of the EUL schema from the development database and import the EUL schema into the production databaseWhen you have imported the EUL to the production database, run the eul5id.sql script to give the new EUL a unique reference number.
Using the Discoverer workbook dump utilityDiscoverer Administrator includes a workbook dump utility (d51wkdmp.exe) that enables you to inspect the EUL elements used by a workbook without having to open the workbook in Discoverer Desktop. This utility is particularly useful if you are unable to open a workbook (for example, because of missing joins).To analyze a workbook, run the d51wkdmp.exe file from a command prompt window. The d51wkdmp.exe file is located in the%ORACLEHOME%bin directory.The syntax for using the workbook dump utility is:d51wkdmp -fThe parameters are described in more detail in the table below. About creating EULs in Logical Standby (or read-only) databasesTo improve performance, Discoverer stores statistics about end user queries in the EUL. For this reason, Discoverer requires that the database containing the EUL is writeable. Specifically, Discoverer does not support the creation of EULs in Logical Standby (or read-only) databases. To prevent Discoverer end users having write access to:.business data, store the data in a read-only database and use database links to access the data from the writeable database that contains the EUL.the EUL itself, do not grant the Create/Edit Workbook privilege to any users, and only grant the Administration privilege to the EUL owner.