E
Registry Settings

AppsFNDNAM 

Used on an Oracle Applications EUL and defines the schema that owns the core Applications tables and views 

"APPS" 

AppsGWYUID 

Used on an Oracle Applications EUL and defines the Username and Password of the public Gateway used in the Applications Login. Separate the username and password using a slash (/) character. 

"APPLSYSPUB/PUB" 

ArchiveCacheFlushInterval 

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 

1000

>0 = The number of elements that are processed between EUL cache flushes when importing and exporting .eex files 

BusinessAreaFastFetchLevel 

Controls the amount of pre-caching that occurs for components and items whenever a Business Area is fetched.

In general terms, the lower the value, the less folders and items are immediately fetched into the Navigator dialog.  

1

Possible values are:

0 - No Fast Fetch

1 - Fast Fetch the objects within each business area

2 - Fast Fetch objects within each business area and items in user mode only

3 - Fast Fetch objects within each business area and items in admin mode only

4 - Fast Fetch objects and items within each business area  

CreateJoinInOtherBAs 

This setting enables you to control the extent to which Discoverer Administration Edition 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: 

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). 

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 13.6.3, "Outer Join with Conditions behavior" 

0

(0 = Do not disable outer joins on filters,

1=disable outer joins on filters) 

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. 

default 0 

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. I.E. If set to "Large_RB1" then a "SET TRANSACTION USE ROLLBACK SEGMENT Large_RB1" statement would be issued 

type - string, default "" 

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. 

0, 1 

MaterializedViewRedirectionBehaviour 

This controls (For 8.1.6+ databases) when a Discoverer query will be rewritten to go against materialized view. 

2 = never redirect the query to a materialized view  

MaxNumberJoinPredicates 

type dword, default 20

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 (for example) 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 1 join using matching column names in bulk load. 

type dword, default 20 

ObjectsAlwaysAccessible 

By default, when Discoverer Plus 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. You can enable or disable this validation using this setting.

Disabling this validation speeds up the display of folders & items in the Item Navigator. When a user executes a query, if the database objects don't exist or the user does not have access to them and this setting is set to 1, Discoverer Plus displays an error (for example, "942 Table or View does not exist") 

0

(0 = Enable object accessibility validation

1 = Disable object accessibility validation) 

QPPCBOEnforced 

Will use cost-based optimizer if set to 1. Will use default optimizer if set to 0.

Query Prediction needs to parse statements in order 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 then Discoverer will use the default optimizer for the database and for the tables involved in the query, (i.e. if the default optimizer is rule-based and the tables have not been analyzed then query prediction will not be available.) 

1

(0 = use the default query optimizer,

1 = use the cost based optimizer) 

QPPCreateNewStats 

Records new statistics if set to 1. These statistics are used by Query Prediction

If you set this to zero, Discoverer doesn't create any new statistics for query prediction. 

1 (0 = false, 1 = true) 

QPPEnable 

This setting enables you to turn Query Prediction on or off.

Uses query prediction/performance (QPP) if set to 1 

1 (0 = false, 1 = true) 

RdbFastSQLOff 

This only applies to Discoverer against RDB. If set to 1 then it turns off "fast sql" on the RDB server.

This registry setting should only be used if errors are encountered against RDB and may help avoid some types of problems. See Appendix F.1 for further information about support for rdb. 

0 (0, 1) 

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

read/write and to save any changes to another workbook. In release 3.1.26, a new registry setting is available that enables you to switch this warning off.

HKEY_CURRENT_USER\Software\ORACLE\Discoverer 3.1\Application\ShowReadOnlyPrompt 

0 (0, 1) 

SQLType 

This entry determines how SQL is displayed in the SQL-dialog.

The valid values for this entry are 0, 1 and 2:

0 = flattened SQL, (i.e standard Oracle format - the default)

1 = odbc SQL,

2 = native SQL. (i.e Discoverer SQL sent to the kernel, with Inline Views) 

0 

TablespaceForMVS 

Controls which tablespace a user points to on DB2. This registry setting would typically be used by the administrator when installing the End User Layer. The registry setting is:

HKEY_CURRENT_USER\Software\Oracle\Discoverer 3.1\Administrator\TablespaceForMVS 

No default.