8
Managing OracleAS Discoverer preferences

8.1 Managing OracleAS Discoverer preferences

This chapter explains how to manage OracleAS Discoverer preferences, and contains the following topics:

• Section 8.2, "What are Discoverer preferences?"

• Section 8.3, "About Discoverer system preferences"

• Section 8.4, "About Discoverer user preferences"

• Section 8.5, "About migrating Discoverer preferences"

• Section 8.6, "How to set user preferences for all users"

• Section 8.7, "How to set individual preferences for specific users"

• Section 8.8, "List of Discoverer user preferences"

8.2 What are Discoverer preferences?

Discoverer preferences are settings that define the Discoverer environment and control the behavior of Discoverer Plus and Discoverer Viewer.

There are two types of Discoverer preference:

• Discoverer system preferences (for more information, see Section 8.3, "About Discoverer system preferences")

• Discoverer user preferences (for more information, see Section 8.4, "About Discoverer user preferences")

8.3 About Discoverer system preferences

Discoverer system preferences are created and set during installation. Typically you will never have to modify the Discoverer system preferences. System preferences are stored as follows:

• On UNIX systems, the Discoverer system preferences are stored in the opmn.xml file.

• On Windows systems, the Discoverer system preferences are stored in the Windows Registry and the opmn.xml file.

  The script file discwb.sh is used to set the Discoverer environment. For more information about the location of configuration files, see Section A.2, "List of Discoverer file locations".

Figure 8-1 Discoverer System preferences

Text description of the illustration pref2.gif

For more information about Discoverer system preferences, see Section A.1, "OracleAS Discoverer configuration files".

8.4 About Discoverer user preferences

During OracleAS installation, Discoverer uses factory supplied default values (stored in defaults.txt) to create user preferences for all Discoverer users (stored in pref.txt).

Figure 8-2 Discoverer user preferences

Text description of the illustration pref1.gif

When a new user starts an OracleAS Discoverer session for the first time, the settings in the pref.txt file take effect as that user's default settings.

After installation, the user preferences can be changed in a number of ways:

• Discoverer end users can change their own user preferences using options within Discoverer Plus or Discoverer Viewer. For example, a Discoverer Viewer end user might click Preferences and change their personal preferences. These changes are stored in the reg_key.dc file on the Discoverer middle tier.

  Note: Updates made when Discoverer end users change their preferences are lost if preferences are re-applied (using the applypreferences script).

• When an individual user changes a preference, the setting of that preference for that user is saved in the reg_key.dc file (to find out the location of this file, see Section A.2, "List of Discoverer file locations").

  Individual preferences are stored for each user as a unique combination of database and userid in the reg_key.dc file, and loaded whenever the user starts a new session. Therefore, users can log on from different client machines and still have their individual settings take effect.

  For example, a Discoverer Plus end user might select Tools | Options to display the Options dialog and change the Number of rows per page value to 15. The following entry might be stored in reg_key.dc for that user (:

  "RowsPerHTML"=D4:4:00,00,00,0F

  where '0F' is the hexadecimal value of 15.

  Note: Unless a user changes a preference value, the value of that preference is as specified in the pref.txt file.

• You can change the default values of user preferences for all Discoverer users by changing the values in the pref.txt file. For the changes to take effect, you must 'apply' the preferences (for more information about the applypreferences scripts, see Section A.2, "List of Discoverer file locations"). The new default values are then written to the reg_key.dc file (for more information, see Section 8.6, "How to set user preferences for all users").

  Note: Where a user has specified their own value for a preference, that value continues to override the new default.

• You can change an individual user's preferences using the Discoverer preferences command line utility (to find out the location of this utility, see Section A.2, "List of Discoverer file locations"). Changes that you make are stored in the reg_key.dc file (for more information, see Section 8.7, "How to set individual preferences for specific users").

Notes

• Never edit the reg_key.dc directly. You must only change values in reg_key.dc using the Discoverer preferences command line utility dis51pr or dis51pre (to find out the location of this file, see Section A.2, "List of Discoverer file locations").

• If you delete the reg_key.dc file, you lose preferences set by Discoverer end users or preferences set using the Discoverer preferences command line utility. Default preferences stored in pref.txt are applied.

• The factory supplied default values for pref.txt are contained in the defaults.txt file (to find out the location of this file, see Section A.2, "List of Discoverer file locations"). If you make a mistake when editing the pref.txt file (or lose or corrupt the file), refer to defaults.txt to restore the content of pref.txt to the original values.

• Maximum values for preferences are documented in the pref.txt file.

• You can edit the pref.txt file without shutting down the Preferences component. In other words, users can continue working while you edit the pref.txt file.

• On UNIX implementations, the reg_key.dc is a hidden UNIX file (i.e. the filename is prefixed with a '.'). Type the command ls -al to list hidden files.

• If you want to deploy Discoverer on multiple machines, you might want to use a centralized set of Discoverer preferences. You do this by specifying one Discoverer Preference Server machine and turn of the Discoverer Preferences component on the other machines. For more information, see Section 5.7, "About the Discoverer Preferences component in a multiple machine environment".

8.5 About migrating Discoverer preferences

You migrate OracleAS Discoverer preferences when you want to upgrade to a new version of Discoverer. For example, you might want to upgrade from OracleAS Discoverer Version 9.0.2 to OracleAS Discoverer Version 9.0.4.

How you migrate Discoverer preferences depends on which version of Discoverer you are using, as follows:

• if you are upgrading from OracleAS Discoverer Version 9.0.2 to OracleAS Discoverer Version 9.0.4, use the OracleAS Upgrade Assistant (for more information about using the OracleAS Upgrade Assistant, see Section D.2, "Upgrading from Discoverer Version 9.0.2 to Discoverer Version 9.0.4")

• if you are upgrading from OracleAS Discoverer Release 4.1 to Discoverer Version 9.0.4, you need to migrate Discoverer Preferences manually (for more information, see Section D.3.1, "Upgrading preferences")

8.6 How to set user preferences for all users

You set user preferences for all users when you want to globally configure Discoverer. To set user preferences for all users you edit the pref.txt file on the Discoverer Preference server (for more information about the Discoverer Preference server, Section 5.7, "About the Discoverer Preferences component in a multiple machine environment").

To set user preferences for all users:

1. On the host machine, open the pref.txt file in a text editor (to find out the location of this file, see Section A.2, "List of Discoverer file locations").

   Hint: If you are using Windows, you can open the pref.txt file in Notepad from the Windows Start menu by choosing Programs | Oracle Application Server | Discoverer | Edit Preferences.

2. Edit the items in the pref.txt file as required.

3. Save the pref.txt file.

4. Run the applypreferences script to apply the preference changes you have made (for more information about the applypreferences script, see Section A.2, "List of Discoverer file locations").

   Hint: Check for error messages in the error.txt file in the current directory to verify that the preferences were applied correctly (for more information about the location of configuration files, see Section A.2, "List of Discoverer file locations").

5. Stop and restart the OracleAS Discoverer service (for more information, see Section 4.4, "About starting and stopping the Discoverer Service").

   Note: You must run the applypreferences script from the host machine.

8.7 How to set individual preferences for specific users

To set individual preferences for specific users:

1. From the command prompt, navigate to the directory containing the Discoverer preferences command line utility dis51pr or dis51pre (to find out the location of this file, see Section A.2, "List of Discoverer file locations").

2. Type a Discoverer preferences command line utility command at a command prompt, using the following syntax:

   dis51pr | dis51pre -user <user> -setpref <"preference category"> 
   <"preference name"> <"preference value">
   
   

   where:

   • dis51pr | dis51pre means type either dis51pr on a UNIX machine or dis51pre on a Windows machine

   • <user> is the name of the user for which you want to set the preference value, followed by the @ symbol, followed by the name of the database (e.g. jchan@salesdb)

   • <"preference category"> is the category of the preference you want to change (e.g. "Database")

   • <"preference name"> is the name of the preference you want to change (e.g. "DefaultEUL")

   • <"preference value"> is the value you want the preference to have

   Hint: Before running the Discoverer preferences command line script, set the Discoverer environment by running the discwb script (to find out the location of this file, see Section A.2, "List of Discoverer file locations").

   Examples:

   • if you want to set the default EUL to Sales for the user jchan, type the following at a command prompt (on UNIX):

     dis51pr -user jchan@salesdb -setpref "Database" "DefaultEUL" \\"Sales\\"
     
     

   • if you want to set the maximum amount of heap memory allowed for the data cache to 512000 for a user jchan, type the following at a command prompt (on UNIX):

     dis51pr -user jchan@salesdb -setpref "Application" "MaxVirtualHeapMem" 
     512000
     

Notes

• To display online help for the Discoverer preferences command line utility, type the name of the script followed by -help (e.g. dis51pr -help).

• Preference names and values are case-sensitive.

• When specifying a string preference value, prefix the string with \\" and end the string with \\". For example, if the preference value is Sales, type \\"Sales\\".

• For a list of Discoverer preferences that you can set using the Discoverer preferences command line utility, see Section 8.8, "List of Discoverer user preferences".

8.8 List of Discoverer user preferences

This table shows the category, description, default value, and valid values of Discoverer user preferences.

Note: Maximum values for preferences are documented in the pref.txt file.

User preference name	Category	Description	Default value	Valid values
AllowAggregationOverRepeatedValues	Application	Specifies whether to aggregate repeated values. If set to 0, Discoverer displays the non-aggregable label (e.g. N/A).	0	0 = do not aggregate repeat values 1 = aggregate repeat values
AppsFNDNAM	Database	Specifies the schema in which Oracle Applications data is stored.	APPS	Valid Apps foundation name
AppsGWYUID	Database	Specifies the public user name and password for the AOL security DLL.	APPLSYSPUB/PUB	Valid Apps user name and password
AvoidServerWildcardBug	Database	Specifies which database Discoverer is running against.	0	0 = not running against RDBMS 7.3.2 with NLS_LANG set to Japanese_Japan 1 = running against RDBMS 7.3.2 with NLS_LANG set to Japanese_Japan
AxisLabelBehavior	Application	Specifies whether Discoverer exports axis labels as part of a worksheet.	`	1 = export axis labels 2 = do not export axis labels 3 = use the same export format as Discoverer Desktop
Axis Style	Crosstab	Specifies the crosstab axis position.	2	1 = inline 2 = outline
BusinessAreaFastFetchLevel	Database	Specifies the amount of pre-caching that occurs for components and items whenever a Business Area is fetched.	1	1
CacheFlushPercentage	Application	Specifies the percentage of cache flushed if the cache is full.	25	User specified
CellPadding	Application	Specifies the amount of space (in pixels) that appears around each cell value in the table or crosstab when displayed or printed. For example, 0 = no pixels, 1 = one pixel, 2 = two pixels. Note: Set this value to 0 to reduce the size of printed reports by removing extra spaces. Hint: For more information about reducing the size of a printed report, see the PrintHeadersOnce preference.	1	User specified Hint: To avoid worksheet layout problems, do not specify a value greater than 5.
Cell XGridline	Crosstab/ Table	Specifies whether to show horizontal and vertical gridlines. Note: To hide both horizontal and vertical gridlines, both Cell XGridline and Cell YGridline must be set to 0. If either XGridline or YGridline is set to 1, both horizontal and vertical gridlines are displayed.	0	0 = no 1 = yes
Cell YGridline	Crosstab/ Table	Specifies whether to show horizontal and vertical gridlines. Note: To hide both horizontal and vertical gridlines, both Cell XGridline and Cell YGridline must be set to 0. If either XGridline or YGridline is set to 1, both horizontal and vertical gridlines are displayed.	0	0 = no 1 = yes
Data Format	Application	Specifies whether to apply HTML formatting to worksheet data cells.	"<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="255, 255, 255" halign="right" valign="top"></fontFormat>"	User specified
DefaultEUL	Database	Specifies the EUL to which you want all users to connect. Each user can override this default from the Discoverer Plus Options dialog.	Any EUL you have created.	Any valid EUL
DefaultUserTypeIsApps	Application	Specifies whether the default Discoverer login type is Oracle Applications (i.e. the "Applications User" check box on the Create Connection page is selected by default). If set to 1, the "Applications User" check box is selected by default.	1	0 = Apps check box is cleared by default 1 = Apps check box is selected by default
DisableAlternateSortOptimization	Database	Specifies whether Discoverer writes optimized Alternate Sort queries. Hint: Set to 1 only if you use external registered summaries.	0	0 = Do not write optimized Alternate Sort queries 1 = Do write optimized Alternate Sort queries
DisableAutoOuterJoinsOnFilters	Database	Specifies the behavior of Discoverer when running queries involving an outer join with a condition (or conditions) applied. The effect of this setting is fully explained in the Oracle Discoverer Administrator Administration Guide.	0	0 = Do not disable outer joins on filters 1 = Disable outer joins on filters
DisableAutoQuery	Database	Specifies whether to automatically run queries and display worksheet data when a worksheet is opened.	0	0 = Run queries 1 = Do not run queries
DisableFanTrapDetection	Database	Specifies whether to disable fan trap detection in user queries.	0	0 = Enable fan trap detection 1 = Disable fan trap detection
DisableFanTrapResolution	Database	Specifies whether to resolve fan traps. For a detailed description of fan trap resolution in Discoverer, see Discoverer Administrator Administration Guide.	0	0 = turn on fan trap resolution 1 = turn off fan trap resolution - you get a pure cartesian product
DisableMultiJoinDetection	Database	Specifies whether to use multiple join path detection when creating worksheets in Discoverer Plus. When this setting is equal to 1, Discoverer Plus selects all join options when creating a worksheet. When this setting is equal to 0 and multiple joins exist, Discoverer Plus displays the Join Folders dialog where you choose the join(s) to use for the worksheet. Note: It is recommended that Discoverer Plus users select all available joins for Discoverer to display accurate results data.	0	0 = Do not disable multiple join detection 1 = Disable multiple join detection
EnhancedAggregationStrategy	Database	Specifies whether to use Enhanced Data Aggregation and if it is, what SQL generation strategy to use. For more information about setting this value, see Section 8.8.1, "About the EnhancedAggregationStrategy user preference setting".	1	0 = Off 1 = Strict Grouping Sets 2 = Optimized 3 = Cube 4 = Auto Determine
EuroCountries	Application	Specifies a comma-separated list of Java locales (e.g. en_IE) for countries whose currency is the Euro.	A list of countries using the Euro (e.g. de,de_AT,de_DE,de_LI...)	Comma-separated list of Java locales (e.g. en_IE) for countries whose currency is the Euro.
ExcelExportWithMacros	Application	Specifies whether macros are exported with the exported Excel file. Note: Macros must be enabled for pivot tables to work.	1	0=Export without macros 1=Export with macros
ExcelVersion	Application	Specifies the version of Excel to export to. Different versions of Excel impose different limits on the number of rows per sheet: the Excel97 limit is 65536 rows per sheet the Excel2000 limit is 65536 rows per sheet If the limit is exceeded, Discoverer places additional rows on additional Excel sheets.	Excel95	Excel97 Excel2000
ExportGroupSortedItemsAsBlank	Application	Specifies whether repeated values on the left side of a Discoverer crosstab worksheet are displayed, or replaced as NULL. For example, if you display Month in the left axis, you might want to repeat the month for each row so that when you export the worksheet to CSV format you export all required data.	1	0 = display repeated values 1 = display repeated values as NULL
GraphAxesAutoScaledFromZero	Application	Specifies whether default minimum value for the Graph axis scale is 0 or not. If set to 1, the minimum value of scale is set to 0, otherwise Discoverer chooses the minimum scale value automatically.	1	0 = do not scale to 0 1 = scale to 0
GraphShowRollupAggregates	Application	Specifies whether to plot 'rolled up' aggregates in graphs. For example, for an outline crosstab worksheet, you might want the graph to plot drilled down values but not the rolled up aggregate values. In other words, if you drill down into sales figures for 2003 to display monthly values, you might want the graph to have the monthly values (e.g. January, February) but not the aggregate value for 2003.	1	0 = no 1 = yes
Heading Format	Application	Specifies which HTML formatting to apply to heading cells in worksheets.	"<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="204, 204, 204" halign="left" valign="top"></fontFormat>"	User specified
ItemClassDelay	Database	Specifies a timeout value in seconds for fetching a list of values.	15	User specified
MaterializedViewRedirectionBehavior	Database	Specifies whether to use materialized view redirection.	0	0=always when available 1=always when summary data not stale 2=never
MaxRowsPerFetch	Database	Specifies the number of database rows retrieved in each fetch from the database, as follows: If the MaxRowsPerFetch value is greater than the RowsPerFetch value, use the RowsPerFetch value. If the MaxRowsPerFetch value is less than or equal to the RowsPerFetch value, use the MaxRowsPerFetch value. If the RowsPerFetch value is not set, use the MaxRowsPerFetch value. See also RowsPerFetch.	250	User specified Minimum=1 Maximum=1000
MaxVirtualDiskMem	Application	Specifies the maximum amount of disk memory allowed for the data cache.	1024000000	User specified
MaxVirtualHeapMem	Application	Specifies maximum amount of heap memory allowed for the data cache.	5120000	User specified
NonAggregableValue	Application	Specifies the default value that is displayed for non-aggregable cells in worksheet. A cell is classified as non-aggregable if the aggregation function being applied does not make sense for the values being aggregated.	"N/A"	User specified
NofityNewRunsOnConnect	Application	Specifies whether to notify an end user on login if new scheduled results are available.	0	0 = Do not notify when new scheduled workbook results are available 1 = Notify when new scheduled workbook results are available
NullValue	Application	Specifies how null values are displayed in worksheets, for example, 'NULL', 'N/A', '0'.	NULL	User specified
ObjectsAlwaysAccessible	Database	Specifies whether to verify that Business Area objects and items exist in the database.	1	0=verify 1=do not verify and assume that the objects and items exist
OutOfFetch	Session Manager	Specifies the delay in seconds between successive database fetches. Set this value if you are getting the following error while running a query: ORA-1002 Fetch out of sequence. If set to bigger value will increase the time taken to run the report. So use only if you get the error mentioned above	0	0 - No delay 1 - 1 second delay 2 - 2 second delay
PredictionThresholdSeconds	Database	Specifies a time threshold for warning Discoverer end users that the predicted query time will exceed this number of seconds.	60	User specified
PredictionThresholdSeconds Enabled	Database	Specifies whether to use the Query prediction threshold.	1	0 = disabled 1 = enabled
PrintHeadersOnce	Application	Specifies whether column headers are printed for each page, or only for the first page. Note: Set this value to 1 to reduce the number of pages that Discoverer Plus generates (e.g. in a crosstab worksheet where headers are repeated often). Hint: For more information about reducing the size of a printed report, see the CellPadding preference.	0	0 = Print column headers for each page 1 = Print column headers once
PrintPercentageOfTitle	Application	Specifies the percentage of a worksheet title to print if the worksheet title is too long to print on a single page. For example, if set to 60, Discoverer truncates a long title to take up 60% of the page. If set to 0, no title is printed. If set to a value that is outside the range, Discoverer defaults to the nearest minimum or maximum value. For example, if set to 80, Discoverer defaults to the maximum value (i.e. 60).	60	User specified Minimum value is 0. Maximum value is 60.
QPPAvgCostTimeAlgorithm	Database	Specifies how to calculate the query prediction time based on query statistics.	2	1 = use five statistics above and below the computed estimate irrespective of cost 2 = use the nearest ten statistics based on the cost
QPPCBOEnforced	Database	Specifies whether to enforce cost based optimizer for query prediction SQL.	2	0 = Cost based optimizer not enforced for query prediction SQL 1 = Cost based optimizer enforced for query prediction SQL 2 = Cost based optimizer for query prediction SQL only enforced for databases older than version 8.1.7
QPPCreateNewStats	Database	Records new statistics if set to 1.	1	0 = false 1 = true
QPPEnable	Database	Uses query prediction/performance (QPP) if set to 1.	1	0 = false 1 = true
QPPLoadStatsByObjectUseKey	Database	Records statistics for same objects first if set to 1.	1	0 = false 1 = true
QPPMaxObjectUseKey	Database	Affects the amount of statistics to cache in memory for query prediction.	30	User specified
QPPMaxStats	Database	Only loads this many previous statistics.	500	User specified
QPPMinActCpuTime	Database	Only records or uses statistics with a CPU time greater than this value.	0	User specified
QPPMinActElapsedTime	Database	Only records or uses statistics with an actual elapsed time greater than this value.	0	User specified
QPPMinCost	Database	Only records or uses statistics with a cost greater than this value.	0	User specified
QPPMinEstElapsedTime	Database	Only records or uses statistics with an estimated elapsed time greater than this value.	0	User specified
QPPObtainCostMethod	Database	Controls how the cost of a query is obtained.	1	0 = uses explain plan to obtain the cost 1 = uses dynamic views to obtain the cost
QPPUseCpuTime	Database	Query prediction uses CPU time within its algorithm.	1	0 = false 1 = true
QueryBehavior	Application	Action to take after opening a workbook.	0	0 = Run Query Automatically 1 = Do not Run Query 2 = Ask for Confirmation
QuerySQLFastFetchLevel	Database	Controls the amount of pre-caching that occurs during SQL generation.	1	0 = no fast fetch 1 = fast fetch (slowest) 2 - fast fetch (medium) 3 - fast fetch (fast) 4 - fast fetch (super fast)
QueryTimeLimit	Database	Limit on query time in seconds.	1800	User specified Minimum=1 Maximum=N/A
QueryTimeLimitEnabled	Database	Query time limit disabled (0) or enabled (1).	1	0 = disabled 1 = enabled
RdbFastSQLOff	Database	Controls wether fast sql option is turned off for an RDB oracle database (applicable only for an Admin session).	0	0 = off 1 = on
Row Headings	Table	Display row numbers on table worksheets.	0	0 = no 1 = yes
RowFetchLimit	Database	The maximum number of rows fetched.	10000	User specified Minimum=1 Maximum=N/A
RowFetchLimitEnabled	Database	RowFetchLimit parameter is disabled (0) or enabled (1).	1	0 = disabled 1 = enabled
RowsPerFetch	Database	The number of rows to fetch from the database at once. If the RowsPerFetch value is less than or equal to the MaxRowsPerFetch value, use the RowsPerFetch value. If the RowsPerFetch value is greater than the MaxRowsPerFetch value, use the MaxRowsPerFetch value. If the RowsPerFetch value is not set, use the MaxRowsPerFetch value.	250	User specified Minimum=1 Maximum=10000
RowsPerHTML	Session Manager	Number of data rows to display on one HTML page. For example, if you have 10 rows of data, they are displayed over two pages in Discoverer Viewer.	25	User specified
SaveLastUsedParamValue	Application	When a workbook is saved, this preference specifies whether to save the most recently used parameter values, or to revert to the default parameter values when the workbook is next opened.	0	0 = Do not save the most recently used parameter values; use the default parameter value when the workbook is next opened. 1 = Save the most recently used parameter value and apply this value when the workbook is next opened.
ShowDialogBitmaps	Application	End users see the bitmap graphics on Discoverer Plus dialogs.	1	0 = off 1 = on
ShowExpiredRunsOnExit	Application	Specifies whether to notify an end user on exit about expired and deleted scheduled results.	0	0 = Do not notify about expired and deleted scheduled workbook results 1 = Notify about expired and deleted scheduled workbook results
ShowUserTypeChoice	Application	Specifies whether to display the "Applications User" check box on the Create Connection page. If set to 1, Discoverer users can specify the type of login to use by selecting this check box.	1	0 = false 1 = true
SQLTrace	Database	Specifies whether Discoverer copies SQL statements to a trace file for analysis. For more information, see the Oracle Discoverer Administrator Administration Guide.	0	0 = false 1 = true
SQLFlatten	Database	Specifies whether Discoverer attempts to flatten the SQL, minimizing the use of inline views in the query SQL. For more information, see the Oracle Discoverer Administrator Administration Guide.	1	0 = false 1 = true
SQLItemTrim	Database	Specifies whether Discoverer attempts to trim the SQL for irrelevant or unused items. For more information, see the Oracle Discoverer Administrator Administration Guide.	1	0 = false 1 = true
SQLJoinTrim	Database	Specifies whether Discoverer attempts to remove the unused joins from the SQL. For more information, see the Oracle Discoverer Administrator Administration Guide.	1	0 = false 1 = true
SummaryObjectsUseCachedAccessibility	Database	Specifies whether to access the summary-derived objects in the cache.	0
SummaryThreshold	Database	Use summary table only if it is no older than this number of days.	60	User specified or 0 = do not use summary at all
SummaryThresholdEnabled	Database	If enabled (1), will use the value specified by SummaryThreshold. Otherwise, Discoverer will always use summary tables if they are available.	1	0 = disabled 1 = enabled
Timeout	Session Manager	Amount of time (in seconds) after which Discoverer Plus disconnects an idle session. Minimum time is 180 seconds (for more information, see Section 8.8.2, "About setting the timeout value for Discoverer"). To set the timeout for Discoverer Viewer, you set the session-timeout value in the web.xml file (for more information, see Section 8.8.3, "How to set the timeout value for Discoverer Viewer").	1800	User specified
Title	Crosstab	Displays worksheet titles.	1	0 = no 1 = yes
Title	Table	Displays worksheet titles.	1	0 = no 1 = yes
Totals Format	Application	Applies HTML formatting to cells that contain totals in worksheets.	"<fontFormat fontName="Dialog" pitch="10" bold="false" italic="false" underline="false" strikethrough="false" foreground="0,0,0" background="255, 255, 255" halign="left" valign="top"></fontFormat>"	User specified
UseOptimizerHints	Database	Specifies whether to add optimized hints to SQL.	0	0 = off 1 = on

8.8.1 About the EnhancedAggregationStrategy user preference setting

The EnhancedAggregationStrategy user preference controls how Discoverer Plus and Discoverer Viewer make use of the Oracle9i database's enhanced aggregation functionality.

The settings control the SQL that is generated for the query, and specify whether there should be an exact match between client request and the aggregation levels retrieved from the database, or whether more aggregation levels are retrieved from the database than are requested by the client.

The table below explains the EnhancedAggregationStrategy user preference settings in more detail:

Value	Description
0	Off The generated SQL contains an ordinary GROUP BY clause.
1	Strict Grouping Sets The generated SQL contains GROUPING SET requests that exactly match the GROUPING SET requests made by Discoverer. The requests that Discoverer makes are determined by how the end user created the worksheet. For example, the generated GROUP BY clause might be similar to the following: GROUP BY GROUPING SETS((Department, Region, Year),(Department),()) Note: This value (the default) might be used if you want to maximize performance.
2	Optimized The generated SQL contains GROUPING SET requests with additional ROLLUP functions. The use of ROLLUP functions enables the SQL to fetch more aggregation levels than requested by Discoverer. This typically enables the end user to add totals or pivot without needing to re-query the database. For example, the generated GROUP BY clause might be similar to the following: GROUP BY GROUPING SETS(ROLLUP(Department, Region, Year), ROLLUP(Region, Year)) Note: This value might be used if worksheet users do a lot of drilling or pivoting when using worksheets.
3	Cube The generated SQL contains a Grouping Set request for a CUBE of the items requested. This is the highest pre-fetch strategy for aggregation levels from the database and should be used with caution as there might be a severe performance overhead in increased query time and resource usage. For example, the generated GROUP BY clause might be similar to the following: GROUP BY GROUPING SETS(CUBE(Department, Region, Year))
4	Auto Determine Discoverer automatically determines which of the above strategies to use (i.e. 1, 2, or 3 above).

8.8.2 About setting the timeout value for Discoverer

You specify a Discoverer timeout if you want Discoverer sessions to shut down automatically after a time specified period if no user interaction has occurred during that time. Before Discoverer shuts down, a warning message is displayed. For example, if a Discoverer session is not used for ten minutes, the Discoverer session will shut down. The Discoverer end user will have to reconnect to use Discoverer again.

Discoverer timeout values are specified as follows:

• In Discoverer Plus, the Timeout value in the pref.txt file specifies the timeout value (for more information, see the Timeout preference in Section 8.8, "List of Discoverer user preferences").

• In Discoverer Viewer, the session-timeout value in the web.xml files specifies the timeout value (for more information, see Section 8.8.3, "How to set the timeout value for Discoverer Viewer").

8.8.3 How to set the timeout value for Discoverer Viewer

To set the timeout value for Discoverer Viewer:

1. Open the web.xml file in a text editor or XML editor (for more information about the location of configuration files, see Section A.2, "List of Discoverer file locations").

2. Look for a session-timeout tag, e.g.

   <session-timeout>10</session-timeout>

3. Update the session-timeout value as required (in minutes).

   For example, to set the timeout to twenty minutes, change the session-timeout value to 20.

4. (optional) If the web.xml file does not contain a session-config tag add the following text to the end of the file, immediately before the closing </web-app> tag:

   <session-config>

   <session-timeout>10</session-timeout>

   </session-config>

   Note: Change the value '10' (i.e. ten minutes) as required.

5. Save the web.xml file.

6. Using Application Server Control, restart the Business Intelligence and Forms component (for more information about restarting instances, see Section 4.7, "How to start and stop the Discoverer servlets").

   When users next start Discoverer Viewer, Discoverer will impose the timeout value specified.