Click Next to display the

4-22 Oracle Fusion Middleware Administrators Guide for Oracle Business Intelligence Discoverer ■ About creating EULs in Logical and Physical Standby or read-only databases 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. Identifiers enable 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 must be re-created with the same identifier In 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 lowercase ■ the numbers 0 to 9 ■ the underscore character _ However, the following characters will be de-supported in future releases of Discoverer: ■ the exclamation mark ■ the tilde symbol ~ ■ the asterisk symbol ■ the left and right parentheses characters: and ■ the single quotation mark ’ ■ the hyphen character - For this release: ■ if you create an identifier that contains a de-supported character, a warning will appear ■ if you import an EEX file that has identifiers that contain de-supported characters, a warning will appear in the import log ■ if you upgrade an EUL that has identifiers that contain de-supported characters, messages will be displayed indicating the identifiers that contain the invalid characters Creating and Maintaining End User Layers 4-23 You do not need to modify any identifiers that use de-supported characters, Discoverer will automatically modify these identifiers to make them valid in future releases. Note: To locate the identifier of a workbook or worksheet in Discoverer Plus, see the Oracle Fusion Middleware Users Guide for Oracle Business Intelligence Discoverer Plus. What are the space requirements and storage parameters for a typical EUL? The minimum default tablespace of 3MB suggested in the Create EUL Wizard: Step 2 dialog 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 data The 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 for example, 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. Therefore, the default tablespace required could be larger, or smaller than the amount available in the tablespace that you select. The database table storage parameters for EUL tables are as follows: ■ EUL5_DOCUMENTS and EUL5_QPP_STATS are created with the following storage parameters: STORAGE INITIAL 1064960 NEXT 1024000 PCTINCREASE 0 ■ all other EUL tables are created with the following storage parameters: STORAGE INITIAL 1064960 NEXT 81920 PCTINCREASE 0 The database index storage parameters for EUL indexes are as follows: STORAGE INITIAL 4096 NEXT 8192 PCTINCREASE 0 There are two factors that might cause the EUL to use up more space: ■ block size