Skip Headers

Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Part Number B10270-01 |
Home | Contents | Index

# 20
Discoverer registry settings

## Discoverer registry settings

This chapter describes the Discoverer registry settings, and contains the following topics:

- "What are Discoverer registry settings?"

- "About Discoverer Plus and Discoverer Viewer registry settings"

- "About Discoverer Administrator and Discoverer Desktop registry settings"

- "Which registry settings improve Discoverer Desktop performance?"

- "What are the Discoverer Administrator and Discoverer Desktop registry settings?"

- "How to edit Discoverer Administrator and Discoverer Desktop registry settings"

## What are Discoverer registry settings?

Discoverer registry settings control how Discoverer behaves under certain conditions. A Discoverer registry setting comprises:

- the name of the registry setting, which is usually a character string (e.g. QPPEnable)

- the value of the registry setting (e.g. 1, 0, a character string)

By default, each registry setting is set to the most commonly required value. However, in some cases you might want to change the value of a registry setting.

The location of Discoverer registry settings depends on the Discoverer product you are using:

- Discoverer Plus and Discoverer Viewer registry settings are held in a registry file called .reg_key.dc

- Discoverer Administrator and Discoverer Desktop registry settings are held in the Windows registry

## About Discoverer Plus and Discoverer Viewer registry settings

Discoverer Plus and Discoverer Viewer use registry settings stored in a registry file called .reg_key.dc. The .reg_key.dc file is located on the middle tier server machine in one of the following locations:

- the \bin directory (the default)

- the directory specified by the environment variable DC9_REG

When an end user changes a user preference in Discoverer Plus or Discoverer Viewer, Discoverer writes the change (for the current user) to the .reg_key.dc file under the following registry key:

\\HKEY_LOCAL_MACHINE\Software\Oracle\WebDisco 9\...

The username of the current user is included in the registry key.

For more information about the Discoverer Plus and Discoverer Viewer registry settings, see the Oracle Application Server Discoverer Configuration Guide.

## About Discoverer Administrator and Discoverer Desktop registry settings

Discoverer Administrator and Discoverer Desktop use registry settings stored in the Windows registry.

When an end user changes a user preference in Discoverer Administrator or Discoverer Desktop, Discoverer writes the change (for the current user) to the Windows registry under the following registry key:

`\\HKEY_CURRENT_USER\Software\Oracle\discoverer9\...`

If you want to change Windows registry settings:

- take a copy of the Windows registry before making any changes

- be careful not to make any unintended modifications

- if in any doubt about what to do, contact your system administrator

## Which registry settings improve Discoverer Desktop performance?

The following registry settings can affect the performance of Discoverer Desktop:

- BusinessAreaFastFetchLevel

- ObjectsAlwaysAccessible

For more information about these settings, see the appropriate entry in "What are the Discoverer Administrator and Discoverer Desktop registry settings?".

## What are the Discoverer Administrator and Discoverer Desktop registry settings?

The following table contains the Discoverer Administrator and Discoverer Desktop registry settings in the Windows registry that you might need to change.

Hint: To change the value of a registry setting or to add a registry setting that is not visible in the Windows Registry Editor, see "How to edit Discoverer Administrator and Discoverer Desktop registry settings". The following table displays Discoverer Administrator and Discoverer Desktop registry settings`:`

``

Directory\Item Key Name | Description | Default/Values
--- | --- | ---
Database\ArchiveCacheFlushInterval | This setting controls the interval between EUL cache flushes during Export and Import of .eex files. Used to avoid excessive memory usage during the Exp or Imp of a very large archive | Default: 1000 >=0 The number of objects that are processed between EUL cache flushes when importing and exporting .eex files
Database\BusinessAreaFastFetchLevel | This setting controls the amount of pre-caching that occurs for folders and items whenever a business area is fetched. In general terms, the lower the value, the fewer folders and items are immediately fetched into the Navigator dialog. | Default: 1 0 - No Fast Fetch 1 - Fast Fetch the folders within each business area 2 - Fast Fetch folders within each business area and items in Discoverer Desktop only 3 - Fast Fetch folders within each business area and items in Discoverer Administrator only 4 - Fast Fetch folders and items within each business area
Administrator\CreateJoinInOtherBAs | This setting enables you to control the extent to which Discoverer Administrator generates joins when you load or refresh a folder. By default, joins are only generated automatically between folders within the same business area. However, you can specify that joins are created automatically across business areas as well. This setting controls that option. | Default: 0 0 - Do not generate/check joins to folders outside the current business area. >0 - Generate/check joins to folders outside the current business area.
Debug\DiagLevel | This setting specifies what trace information to write to the EUL trace file in <ORACLE_HOME>\discoverer\bin\dcediag.out. You specify one or more of the valid values and give each value an integer (e.g. OB=1). If you specify more than one value integer pair, separate each pair with a comma (e.g. OB=1, OL=3). The higher the integer, the more detailed the information. For example, to create trace information at a high level of granularity, you might specify the following values: OL=6,OM=5,DC=10,DCOV=10 Other useful examples: OL=0 logs all SQL statements which fail execution on the database OL=2 logs all SQL statements executed, as well as numbers of rows fetched and basic cursor lifecycle (in addition to the information logged by OL=0) OL=3 logs all cursor bind variables (in addition to the information logged by OL=2) DCIE=2 logs actions and elements processed by an import/export operation DC=15 logs various important Discoverer actions For more information, see "Using SQL files and trace files". | No default DC - General important events DCBL - Bulk load details DCIE - Import/export details DCOV - Metadata validation OB - Proces of posting data to the database when a transaction is committed OL - Database interactions (SQL statements, bind variables, etc) OM - Database connect/disconnect
Database\DisableAutoOuterJoinsOnFilters | This setting toggles the behaviour of Discoverer when running queries involving an outer join with a condition (or conditions) applied. The effect of this setting is explained in an example in Chapter 9, "Creating and maintaining joins" | Default: 0 0 - Do not disable outer joins on filters 1 - disable outer joins on filters
Database\DisableMultiJoinDetection | This setting toggles multiple join path detection when creating worksheets in Desktop. If this setting is set to 1, Desktop selects all join options when creating a worksheet. If this setting is set to 0 and multiple joins exist, Desktop displays the Join Folders dialog where you choose the join(s) to use for the worksheet. Note: It is recommended that Desktop users select all available joins for Discoverer to display accurate results data. | Default: 0 1 - Disable multiple join detection. 0 - Do not disable multiple join detection.
Database\EULUpgradeForceCommitForAllSteps | This affects the commit processing and hence rollback space usage during the upgrade of a previous version EUL. If you are having problems upgrading an EUL due to limited rollback space, it is possible to commit more frequently using this setting. | 0
Database\EULUpgradeRollbackSegment | If this setting is defined then it should be the name of the rollback segment that you want to be used for the duration of the upgrade. In other words, if set to "Large_RB1", a "SET TRANSACTION USE ROLLBACK SEGMENT Large_RB1" statement would be issued. | No default
Database\FormatXML | Set the value to 1 if you want the XML export file to include spaces that make the file more readable, but larger. If the value is 0 or the entry is not present, the export file will not use indentation thus reducing file size. | Default: 0 0 = not use indentation 1 = include spaces
Database\MaxNumberJoinPredicates | During bulk load you have an option to create an automatic join based on column names (rather than primary/foreign keys). If you have the same table already loaded, then a join will be created that matches every column in the table. You can stop these being created by specifying the maximum number of predicates in one join using matching column names during bulk load. | Default: 20
Database\ObjectsAlwaysAccessible | By default, when Desktop displays folders and items in the Item Navigator, it validates that the tables/views they refer to exist and that the user has access to them. This setting enables you to disable this validation. Disabling this validation speeds up the display of folders and items in the Item Navigator. When a user executes a query, if the database objects do not exist or the user does not have access to them and this setting is set to 1, Desktop displays an error (e.g. "ORA 942 Table or View does not exist") | Default: 1 0 - Enable object accessibility validation 1 - Disable object accessibility validation
Database\QPPCBOEnforced | Will use cost-based optimizer if set to 1. Will use default optimizer if set to 0. Query Prediction needs to parse statements to obtain their cost. The cost is only available when parsing with the cost based optimizer (it is not produced if parsing with the rule based optimizer). The default behavior in Discoverer is to force the use of the cost based optimizer when parsing these statements. If this registry setting is set to 0 Discoverer will use the default optimizer for the database and for the tables involved in the query. In other words if the default optimizer is rule-based and the tables have not been analyzed, query prediction will not be available. | Default: 1 0 - use the default query optimizer 1 - use the cost based optimizer
Database\QPPCreateNewStats | Records new statistics if set to 1. These statistics are used by Query Prediction If you set this to zero, Discoverer does not create any new statistics for query prediction. | Default: 1 0 - false 1 - true
Database\QPPEnable | Enables you to turn Query Prediction on or off. Uses Query Prediction (QPP) if set to 1. | Default: 1 0 - false 1 - true
Database\RdbFastSQLOff | This only applies to Discoverer against RDB. If set to 1, it turns off "fast sql" on the RDB server. Only use this registry setting if errors are encountered against Oracle Rdb because it might help avoid some types of problems. See Chapter 22, "Discoverer support for non-Oracle databases and Oracle Rdb" for further information about support for Oracle Rdb. | Default: 1 0 - false 1 - true
Application\ShowReadOnlyPrompt | You can set the operating system privilege for a file-based workbook to read-only. In this instance, when a user opens the workbook they get a warning message informing them that the workbook cannot be opened for read/write and to save any changes to another workbook. This registry setting enables you to switch this warning on and off. | Default: 0 0 - false 1 - true
Database\SQLFlatten | Controls whether Discoverer attempts to flatten the SQL, minimizing the use of inline views in the query SQL. | Default: 1 1 - enabled 0 - disabled
Database\SQLItemTrim | Controls whether Discoverer attempts to trim the SQL for irrelevant or unused items. | Default: 1 1 - enabled 0 - disabled
Database\SQLJoinTrim | Controls whether Discoverer attempts to remove the joins from the SQL (for more information, see "What effect do joins have on query results and query performance?"). | Default:1 1 - enabled 0 - disabled
Database\SqlTrace | Creates an Oracle server trace file and all Discoverer SQL statements sent to the database server are written to the trace file. The default locations for the server trace files (extension .trc) are as follows: <ORACLE_HOME>\rdbms\trace (on Windows machines) $ORACLE_HOME/log (on UNIX machines) Note: After the trace file is created and the required SQL statements are written to the trace file, you must reset the value of SqlTrace to the numeric value zero (0) to stop any further SQL statements being written to the file. Resetting the value of SqlTrace to zero (0) avoids unnecessary processing after the trace file is written. Note: The database user must have the dba privilege to use Discoverer with this setting enabled. For more information, see "Using SQL files and trace files". | Default: 0 1 - enabled
Database\SQLType | This entry determines how SQL is displayed in the SQL Inspector dialog. | Default: 0 0 - flattened SQL, (i.e standard Oracle format) 2 - native SQL (i.e. Discoverer SQL sent to the kernel, with inline views)
Database\SummariesAlwaysAccessible | This setting displays summary folders quickly from the Summaries tab and makes them all appear to be accessible (regardless of whether they are or not). This setting avoids validation and checks (which can be slow) and enables users to display/modify summary folders quickly. Only setups with large numbers of summary folders are likely to need to use this setting. Note: Be aware that if you enable this setting, invalid summary folders are not shown as being invalid in the UI and the UI will not reflect this until this setting is disabled. This might cause the Discoverer manager to miss required action. Set this to "1" for faster display of summary folders from the Summaries tab. Set this to "0" to validate summary folders before displaying them at the Summaries tab. | Default: 0 0:-false 1-true
Administrator\TablespaceForMVS | Controls which tablespace a user points to on DB2. This registry setting is typically used when installing the End User Layer. | No default
Administrator\UserRoleFilter | Enables Discoverer Administrator to display only users and roles that start with the value used for this setting. This setting is case sensitive. This setting can improve the time it takes for Discoverer to display very large lists of database users and roles in the Privileges and Security dialogs. For example, if you set the value to SYS, Discoverer will only display users and roles that begin with the letters SYS (e.g. SYS, SYSMAN, SYSTEM). For changes to take effect, you do not have to restart Discoverer Administrator. It is sufficient to just close the Security or Privileges dialog, update the registry, and display the dialog. When this setting has no value (i.e. the default), Discoverer displays all users and roles. Note: This setting does not affect display of users, roles that are granted a privilege or the PUBLIC user (i.e. they are displayed regardless of this setting). | No default

## How to edit Discoverer Administrator and Discoverer Desktop registry settings

You edit Discoverer Administrator and Discoverer Desktop registry settings using the Windows registry editor.

How to start the Registry Editor and edit registry settings will depend on the environment you are using.

To start the Registry Editor and edit Discoverer Administrator and Discoverer Desktop registry settings in a Windows environment:

1. Choose Run... from the Windows Start menu.

2. In the Run dialog box, type `regedt32` and click OK.

3. Open the`\\HKEY_CURRENT_USER\Software\Oracle\Discoverer9\ registry key to view the` Discoverer Administrator and Discoverer Desktop registry settings.

4. If you want to edit the value of a Discoverer Administrator or Discoverer Desktop registry setting shown in the Registry Editor:

   1. Double click on the registry setting in the right-hand pane of the Registry Editor to display the DWORD Editor dialog.

   2. Replace the existing value of the registry setting with a new value and click OK.

5. If you want to edit the value of a Discoverer Administrator or Discoverer Desktop registry setting and the registry setting is not currently shown in the Registry Editor:

   1. Click on the key name below which the registry setting should appear.

      For example, if you want to set QPPEnable to 0, and QPPEnable does not appear in the Registry Editor, click on the \\HKEY_CURRENT_USER\Software\Oracle\Discoverer9\Database\ key to select it. For more information about the registry key for a particular registry setting, see "What are the Discoverer Administrator and Discoverer Desktop registry settings?".

   2. Choose Edit | Add Value to display the Add Value dialog.

   3. Enter the name of the Discoverer registry setting you want to add (e.g. QPPEnable) and click OK.

      The String Editor dialog appears.

      Note: Discoverer Administrator Registry settings must be in the case specified in the table in the section "What are the Discoverer Administrator and Discoverer Desktop registry settings?".

   4. Enter the value you want the Discoverer registry setting to have (e.g. 1) and click OK.

      The registry setting appears in the Registry Editor with the value you specified.

6. Choose Registry | Exit to close the Registry Editor.

| Copyright © 1996, 2003 Oracle Corporation. All Rights Reserved. |
Home | Contents | Index