1. Administering Oracle Analytics Server
  2. Manage Your Installation
  3. Perform Common Administration Tasks
  4. About Advanced Configuration Options

About Advanced Configuration Options

You can configure several advanced service-level options by clicking System Settings in the Oracle Analytics Server Console.

Topics:

Analytic Content Options

You use these options to set defaults and customizations for dashboards, analyses, and reports. For example, you can configure the analysis editor to open by default to the Criteria tab or the Results tab.

Note:

If you change an analytic content setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

System Setting More Information
Analytics Publisher Reporting Toolbar Mode

Configures an alternate toolbar for pixel-perfect reports that are included in a dashboard.

See Configure an Alternate Toolbar for Oracle Analytics Publisher

  • 1 — Doesn't display a toolbar for pixel-perfect reports.
  • 2 — Displays the URL to the report without the logo, toolbar, tabs, or navigation path.
  • 3 — Displays the URL to the report without the header or any parameter selections. Controls such as Template Selection, View, Export, and Send are still available.
  • 4 — Displays the URL to the report only. No other page information or options are displayed.
  • 6 — Displays parameter prompts for the report in a toolbar.

Valid Values: 1,2,3,4,6

Default: 1
Answers Editor Start Tab

Specifies whether the analysis editor opens by default to the Criteria tab or the Results tab.

This setting applies when users click an Edit link for an analysis from a dashboard, the Home page, or the Catalog page.

Users can override this default setting by specifying the Full Editor option in the My Account dialog.

  • answerResults — Opens the analysis editor by default to the Results tab.

  • answerCriteria — Opens the analysis editor by default to the Criteria tab.

Valid Values: answerResults, answerCriteria

Default: answerResults
Answers Subject Area Sorting Order

Sets the default sort order for subject area content trees. Users can override this default setting in the My Account: Subject Area Sort Order dialog.

  • asc — Sorts A to Z.

  • desc — Sorts Z to A.

  • rpd — Uses the subject area sort order specified in the original analyses.

Valid Values: asc, desc, rpd

Default: rpd
Custom Links XML

Specifies the XML code containing Classic Home page header customizations.

You can use this XML code to customize the global header section of the Home page to better meet the needs of your users. For example, you can disable certain links or add custom ones.

See Provide Custom Links in Presentation Services
Writeback Template XML

Defines the XML configuration for performing writeback on data elements.

For example, you can use an XML template to enable users of a dashboard page or an analysis with the ability to modify, or write back, the data that they see in a table view.

See Create Write-Back Template Files

Connection Options

Connection externalization isn't supported in Oracle Analytics Server.

System Setting More Information
Connection Externalization Enabled This option isn't used.

Email Delivered by Agents Options

You can use these options to customize the way agents deliver email.

System Setting More Information
Maximum Email Size (KB)

Specifies the maximum size (KB) of a single email.

If you set a maximum email size, you can avoid situations when SMTP servers reject emails that are too large, and in the event that an email exceeds the set limit, the email recipients receive an error message instead of the agent failing and just alerting the email author.

Valid Values: 0-20480

Default: 0 (unlimited email size)

Maximum Number of Recipients per Email

Specifies the maximum number of recipients allowed in the To: or Bcc: line for a single email.

You can set the maximum number of email recipients to avoid some SMTP servers from filtering out these emails as spam. If the recipient list exceeds the set limit, the list is split into smaller lists with the maximum number of allowed recipients in each list.

Valid Values: 0-1024

Default: 0 (unlimited number of email recipients)

Safe Domains

If you want to restrict the email domain that Oracle Analytics can send emails to, enter the name of the domain. For example, examplemaildomain.com.

Use a comma to separate multiple domain names. For example, exampledomain1.com,exampledomain2.com. By default, there are no restrictions.

Use BCC

Specifies whether to include the names of email recipients in the To: or Bcc: line. By default, email recipients are added to the Bcc: line.

  • On — Add email recipients to the Bcc: line. Names of email recipients are hidden.

  • Off — Add email recipients to the To: line. Everyone who receives the email sees the recipient list.

Default: On
Use RFC 2231 Encoding

Specifies how to encode MIME email parameters. By default, RFC 2047 is used.

  • On — Use RFC 2231 to encode MIME email parameter values. RFC 2231 supports multi-byte languages. Select On if you deliver emails that contain multi-byte characters and use an email server that supports RFC 2231, such as Microsoft Outlook for Office 365 or Google Gmail.

  • Off — Use RFC 2047 to encode MIME email parameter values.

Default: Off

Format Options

You use these options to configure default currency and time zone settings for analyses and dashboards.

These options apply only to analyses and dashboards. They don't apply to data visualizations.

Note:

If you change a format setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

System Setting More Information
Currencies XML

Defines the default currency that's displayed for currency data in analyses and dashboards. For example, you can change from American dollars ($) to Euros (E). See Change the Default Currency for Analyses.
Default Data Offset Time Zone

Specifies a time zone offset of the original data that users see in analyses and dashboards. Enter an offset value that indicates the number of hours away from Greenwich Mean Time (GMT) time.

For example, to display values in United States Eastern Standard Time (EST), which is Greenwich Mean Time (GMT) - 5 hours, enter the value GMT-05:00 or the equivalent value in minutes -300.

If you don't set this option, no time zone conversion occurs because the value is "unknown".

Specifying a different offset value for each user

If you want to specify a different offset value where session variables can be used (for example, expressions, calculations), don't use the Default Data Offset Time Zone setting. Instead, set the system session variable DATA_TZ in the semantic model. See About Session Variables.

Default Time Zone for Date Calculations

Specifies the time zone used for evaluating date calculations such as getting the current date/time, truncating datetime values to a date, and extracting time fields from date/time expressions.

If you leave this field blank, Oracle Analytics uses the operating system time zone when evaluating date calculations.

Default User Preferred Time Zone

Specifies a default preferred time zone that users see in analyses and dashboards before they select their own in the My Account Preferences dialog.

If you don't set this option, Oracle Analytics uses the local time zone.

Specifying a different time zone for each user

If you want to specify a different offset value where session variables can be used (for example, expressions, calculations), don't use the Default User Preferred Time Zone setting. Instead, set the system session variable TIMEZONE in the semantic model. See About Session Variables.

User Currency Preferences XML

Determines whether users see a Currency option in their My Account preferences dialog and the list of currencies available to them. If you provide the Currency option, users can select in which currency they prefer to view columns of currency data in analyses and dashboards. See Define User-Preferred Currency Options.

Other Options

These options enable you to set the behavior for a variety of actions such as database queries, default URLs, display defaults, and sorting.

Note:

If you change one of these settings, you must apply the change for the new value to take effect unless we note it otherwise.
System Setting More Information
Disable Right Trim for VARCHAR Data

Specifies whether the automatic removal of trailing spaces from varchar columns is enabled (Off) or disabled (On). For example, when this property is enabled (Off), when a user starts entering values in a field, the filter dialog automatically trims any trailing spaces.

  • On — Preserves trailing whitespaces in varchar columns. If you primarily use Oracle Database sources, you might want to keep the default Oracle Database behavior of preserving trailing whitespaces rather than removing them. When you toggle this property on, you avoid the overhead of trimming spaces, and this can improve performance.

    If you disable this property (set it to On) and you construct a filter such as PRODUCT_DESCRIPTION = 'My Product '), you must make sure the amount of trailing whitespace used exactly matches the varchar column value. If you don't, the filter won't correctly match the data values.

  • Off — Trims trailing whitespaces in varchar columns when processing queries. This is the default for Oracle Analytics. For example, if a user enters the text 'My Product ', it trims it to 'My Product'.

Default: Off
Enable Subrequest Shipping

Specifies if sub-requests to source databases are executed separately as standalone queries or executed together. By default, sub-requests are shipped separately which can improve performance if you execute complex reports with a large group of sub-requests, that is, you prefer to ship the sub-requests separately in multiple simplified queries rather than ship a large single complicated query all at once.

In Oracle BI Enterprise Edition, the default is set to NO. If you used Oracle BI Enterprise Edition and want to retain the previous default behavior, set this property to NO to continue executing database sub-requests together.

  • Default — Database sub-requests are shipped separately. This is the same as the value YES.
  • YES — Database sub-requests are shipped separately.
  • NO — Database sub-requests are shipped together, all at once.

Default: Default
Enforce Safe Domains in Actons

Determines whether action links that users add to analyses and dashboards can invoke any URL or only URLs that administrators specify in the safe domains list.

  • On — Don't allow actions to invoke any URL that's not in the safe domain list.
  • Off — Allow actions to invoke any URL, even if the URL isn't listed as a safe domain.

Default: On for a brand new service and Off for an existing service.

Apply Change Required: No

Hide EPM Cloud Members with No Access

Specifies if users can view all EPM dimension members in a hierarchy prompt list of values or when adding the hierarchy to a canvas, even if they don't have data access to some of the members.

  • On —Show only those members of an EPM dimension that users have data access to.

    If this setting is On, users who don't have access to the root member of the dimension hierarchy won't see any EPM members in hierarchies or hierarchy prompts.

  • Off — Users can view all the members in an EPM dimension even if they don't have access to view data for some members.

Default: Off
Hide Loading Messages

Specifies if a detailed message is displayed during data load processing.

  • On — Detailed loading messages are hidden and a simplified message Loading... is displayed instead.

  • Off — Detailed loading messages are displayed.

Default: Off
Locale

Applies to content migrated from Oracle BI Enterprise Edition.

After you migrate content from your Oracle BI Enterprise Edition environment to Oracle Analytics, you may see a different language in messages, dates, or currencies within analyses.

For example, if you look at a migrated analysis in Polish, the currencies or dates might display based on the Oracle Analytics default locale, not the original Oracle BI Enterprise Edition locale. To preserve the Oracle BI Enterprise Edition currencies and dates in Oracle Analytics, change this setting to Polish.

Portal Path

Specifies the path of the dashboard page that's displayed by default when users sign in to Oracle Analytics. For example, /shared/<folder>/_portal/<name>.

You can specify a single path for all users and multiple paths by user role, for example {"application role 1":"catalog dashboard path 1","application role 2":"catalog dashboard path 2","default":"catalog dashboard path 3"}.

This setting applies to all users, but users can override it after they've signed in.

You can enter a maximum of 5,000 characters in this field.
Recursive Datetime Type Checking

Specifies whether to enforce strict recursive data type checking for comparisons between identical data types (for example, integer to integer) or non-compatible data types (for example, integer to short integer) on all data sources or with all datasets.

  • On — Enforces strict recursive checking for identical or non-compatible data types on all data sources or datasets.

  • Off — Relaxes strict recursive checking for date and time data types on all data sources or datasets. However, if there are too many data type inconsistencies, you may want to change the data types to be compatible or use constants of the correct data type when comparing a column to a value. For example, after you migrate content from Oracle BI Enterprise Edition 11g to Oracle Analytics, you might start seeing this type of check error in your reports because Oracle BI Enterprise Edition 11g didn't enforce strict checks:

    [nQSError: 22024] A comparison is being carried out between non-compatible types <type1> and <type2>.

Default: On
Repeat Rows on Excel Exports for Tables and Pivots

Specifies whether cells that span rows and cells that span columns are repeated when exporting tables and pivot tables to Excel.

  • On — If switched on, cells that span rows and cells that span columns are repeated, regardless of the Value Suppression setting in the Analysis editor.
  • Off — If switched off, the Value Suppression setting in the Analysis editor is honored and cells that span rows and cells that span columns don't repeat when exporting tables and pivot tables to Excel.

Default: Off
Sort Null Values First

Specifies whether to sort NULL values before other values (On) or after (Off). Select the value that matches your database. If this setting doesn't match your database setting, then the database setting takes precedence.

  • On — Sorts NULL values before other values.
  • Off — Sorts NULL values after other values.

Default: Off
Sort Order Locale

Applies to content migrated from Oracle BI Enterprise Edition.

After you migrate content from your Oracle BI Enterprise Edition environment to Oracle Analytics, you may experience different sorting behaviors in analyses.

For example, if you look at a migrated analysis in Polish, the upper case and lower case letters might sort based on the Oracle Analytics default locale, not the original Oracle BI Enterprise Edition locale. To preserve the Oracle BI Enterprise Edition sort behavior in Oracle Analytics, change this setting to Polish.

Performance and Compatibility Options

You use these options to configure performance and compatibility settings between Oracle BI Enterprise Edition and Oracle Analytics. For example, you can set the maximum temporary file size.

Note:

If you change a performance and compatibility setting, you must apply the change for the new value to take effect unless we note it otherwise.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

System Setting More Information
Brushing Enabled for Datasets

Specifies whether brushing is enabled by default for workbooks that use dataset data.

  • On — Brushing is on by default for workbooks that use dataset data.

  • Off — Brushing is off by default for workbooks that use dataset data.

Users can override this setting in the workbook and canvas properties.

Default: On
Brushing Enabled for Subject Areas

Specifies whether brushing is enabled by default for workbooks that use data from subject areas.

  • On — Brushing is on by default for workbooks that use subject area data.

  • Off — Brushing is off by default for workbooks that use subject area data.

Users can override this setting in the workbook and canvas properties.

Default: On
Cache Dashboard Listing Dropdown Menu

Specifies how often the Dashboards menu list on the Oracle Analytics Classic Home page is populated during a user session.

  • On — Dashboards menu lists are only populated once per user session. This improves performance but may result in stale lists until the user logs out and back in which refreshes the lists.

  • Off — Dashboards menu lists are populated every time they’re opened.

Default: Off
Cache Enable

Specifies whether data query caching is enabled or disabled.

  • On — Data caching is enabled.

  • Off — Caching is disabled.

See Configure Query Caching.

Default: On
Enable Auto Insights on Datasets

Specifies whether the Auto Insights feature is available when datasets are created or modified.

  • On — The Enable Insights option is available in the Dataset Inspect dialog and insights are automatically generated and available for workbooks that use datasets with the Enable Insights option selected.

  • Off — Auto Insights and its related features are disabled.

Default: On

Apply Change Required: No, but when you change this setting, it may take a few minutes to take effect.

Enable Database Analytics Node in Data Flows

Specifies whether the Database Analytics node is displayed in data flows.

  • On — The Database Analytics node is available in data flows so that data flow designers can apply database analytics functions to the data.

  • Off — The Database Analytics node isn't available in data flows. This prevents data flow designers from generating a potentially high number of SQL statements and slowing database performance.

Default: On

Enable Immediate Dashboard Rendering

Specifies whether to display available dashboard content immediately or wait until all the dashboard content is ready.

  • On — Display dashboard content immediately even if some content is unavailable.

  • Off — Wait for all the dashboard content to be ready before displaying content.

Default: Off
Evaluate Support Level

Specifies who can issue database functions: EVALUATE, EVALUATE_ANALYTIC, EVALUATE_AGGR, and EVALUATE_PREDICATE.

By default (0), the EVALUATE database functions are disabled.

See EVALUATE_SUPPORT_LEVEL

  • 1 — Service administrators only. Users with the BI Service Administrator application role can invoke EVALUATE database functions.

  • 2 — Anyone. Any user who signs in to Oracle Analytics can invoke EVALUATE database functions.

  • 0 (or any other value) — No one. All EVALUATE database functions are disabled in Oracle Analytics.

Valid Values: 0, 1, 2

Default: 0
Maximum Working File Percent Size

Specifies that the temporary file doesn't exceed a specified percentage of the global work directory size limit.

See MAX_WORK_FILE_SIZE_PERCENT.

The size limit defaults for temporary files is 5% (of 100 GB), equivalent to 5 GB. The file limit applies individually to each temporary file, while the size specified for the total global work directory applies collectively to all temporary files created.

You can increase or decrease this value within the range of 5% to 50%. This enables temporary file sizes between 5GB and 50GB. Raising this setting above 50% limits concurrency for large operations.

Valid Values: 5-50

Default: 5
Mobile Watch Service Enabled

Specifies if the Data Watch service is active.

  • On — The Data Watch service is active and all mobile users can specify the threshold value for bring backs.

  • Off — The Data Watch service is inactive.

Default: On
Mobile Watch Service Frequency

Specifies the frequency at which the Data Watch service must scan the server for changes based on the frequency of changes in your data sources.

The default is 240 (4 hours). You can disable this service by changing this setting frequency to 0 or by toggling the Mobile Watch Service Enabled setting to off.

Valid Values: 0-10139

Default: 240
OBIEE Compatibility Release

Specifies the on-premise Oracle BI Enterprise Edition version number for feature compatibility. This only applies if you upgrade from Oracle BI Enterprise Edition to Oracle Analytics, and you want to use a feature from a specific on-premises release in Oracle Analytics.

Valid Values: 11.1.1.9, 11.1.1.10, 11.1.1.11, 12.2.1.0, 12.2.1.1, 12.2.1.3, 12.2.1.4, 12.2.2.0, 12.2.3.0, 12.2.4.0, 12.2.5.0

Override Database Features

Specifies if users can use request variables to override database features.

  • 1 — Only administrators can override database features.

  • 2 — Any user can override database features.

  • 0 — No user can override database features.

Valid Values: 0, 1 , 2

Default: 0
Strong Datetime Type Checking

Specifies whether to enforce strict checking for date and time data types and whether to reject queries that contain incompatibilities in date and time data types.

  • On — Enforces strict checking for date and time data types.

  • Off — Relaxes strict checking for date and time data types. However, invalid queries or queries with severe date and time incompatibilities may still be still rejected. For example, date and time incompatibilities might be rejected if your relational database uses strict checking for those data types.

See STRONG_DATETIME_TYPE_CHECKING.

Default: On

Prompt Options

You use these options to configure prompt behavior in analyses and dashboards. For example, you can enable search results to automatically display as highlighted when users enter search parameters, without the need to click Search.

These options apply only to analyses and dashboards. They don't apply to data visualizations.

See Configure for Prompts.

Note:

If you change a prompt setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

System Setting More Information
Auto Apply Dashboard Prompt Values

Enables the option to hide the Apply button so that prompt values can be applied without clicking any button.

If this is property is On:

  • Displays the Show Apply Button and Show Reset Button fields in the Edit Page Settings dialog.

  • Displays the Prompts Apply Buttons and Prompts Reset Buttons fields in the Dashboard Properties dialog.

  • Displays the Prompt Buttons on Current Page option on the dashboard builder's Tools menu.

Default: On
Auto Search on Prompt Value Search Dialog

Enables search results to automatically display and highlight when users enter search parameters, without the need to click Search.

Default: On
Case Insensitive Auto Complete

Specifies whether, when a user enters a prompt value in analyses and dashboards, the auto-complete functionality is case-insensitive.

  • On — Case isn't considered when a user enters a prompt value such as "Oracle" or "oracle."

  • Off — Case is considered when a user enters a prompt value, so the user must enter "Oracle" and not "oracle" to find the Oracle record.

Default: On
Show Null Value When Column Is Nullable

Specifies whether to show the term "NULL" at runtime in the column prompt above the column separator in the drop-down list when the database allows null values.

  • always — Always shows the term "NULL" above the column separator in the drop-down list.

  • never — Never shows the term "NULL" in the drop-down list.

  • asDataValue — Displays the data value in the drop-down list, not the term "NULL" above the separator in the drop-down list.

Valid Values: always, never, asDataValue

Default: always
Support Auto Complete

Enables or disables the auto-complete functionality available in prompts.

  • On — Enables auto-complete, which means that the Prompts Auto-Complete field is displayed and set to On in the My Account dialog and in the Dashboard Properties dialog.

  • Off — Disables auto-complete, which means that the auto-complete fields in the My Account and Dashboard Properties dialogs aren't available.

Default: Off

Security Options

Use Security options to control how users can perform specific actions in analyses and dashboards.

These options apply only to analyses and dashboards. They don't apply to data visualizations.

Note:

If you change a security setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

System Setting More Information
Allow HTML/JavaScript/CSS Content

Determines whether users can apply and save HTML, JavaScript, and CSS markup in various text fields for analyses and dashboards, and how any previously saved markup is used.

  • Always — Enables users to apply markup. Displays the Contains HTML/JavaScript/CSS Markup option in dialogs where additional formatting might be useful. For example:

    • For analyses: Various dialogs in the analysis editor, Analysis Properties dialog, Column Properties (Column Format) dialog, Edit Column Formula dialog, Narrative dialog, Ticker dialog, Static Text dialog, and New Calculated Measure dialog.
    • For dashboards: Various dialogs in the dashboard editor, Text Properties dialog, and Edit Header and Edit Footer dialogs (under Print and Export Options).

    Note: The Always option was previously named "On".

  • Never — Prevents users from applying markup. Hides the Contains HTML/JavaScript/CSS Markup option. Users can only enter plain text. Oracle Analytics ignores any markup that users previously entered and saved for their analyses and dashboards.

  • HTML Only — Enables users to apply HTML markup. Displays the Contains HTML/JavaScript/CSS Markup option in dialogs where additional formatting might be useful but only safe HTML is allowed (no JavaScript or CSS). When an analysis or dashboard opens, Oracle Analytics sanitizes any markup that users have entered and applies only the HTML markup.
  • On Open — Prevents users from applying additional markup (existing markup is retained). Hides the Contains HTML/JavaScript/CSS Markup option so users can enter only plain text. Any previously saved markup for analyses and dashboards continues to be applied.

    Note: The On Open option was previously named "Off".

For security reasons, markup is not allowed when you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE. To turn the feature on in Oracle BI EE, you must enable Allow HTML/JavaScript/CSS Content.

Enable Push Notifications

Specifies if mobile application push notifications are enabled (on) or disabled (off).

  • On — Enables mobile application push notifications to receive alerts and messages.

  • Off — Disables mobile application push notifications to stop receiving alerts and messages.

Default: On
Save Workbook Thumbnails

To help people identify workbook content, Oracle Analytics can display thumbnail images for workbooks on the Home page. The information that’s shown in these thumbnails is blurred to protect sensitive data from being exposed to users that don't have the same access as data authors.

This system property overrides any Save thumbnails value set in the Workbook Properties dialog at the individual workbook level.

  • On — Display blurred workbook thumbnails on the Home page. If this setting is On, workbook owners can hide the thumbnail for individual workbooks if they need to. See Set WorkbookThumbnails.

  • Off — Don’t display any workbook thumbnails on the Home page. Instead, show the standard icon for all workbooks.

Default: On
URL for Browser Script Actions

Specifies the URL for the JavaScript file containing custom Browser Script Actions.

Usage Tracking Options

You use these options to specify how you want to monitor system usage. For example, you can set the number of rows that you want stored in the usage tracking tables.

Note:

If you change an usage tracking setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you set options in configuration files to configure usage tracking. If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, usage tracking settings are preserved and usage tracking continues to work but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter your usage tracking details through System Settings but, for clarity, you might decide to do so.

See Set Usage Tracking Parameters.

System Setting More Information
Usage Tracking Connection Pool

Specifies the name of the connection pool you created for your usage tracking statistics database. For example, <database name>.<connection pool name>.

Usage Tracking Init Block Table

Specifies the name of the fully-qualified database table you use for inserting records that correspond to the initialization block statistics, as it appears in the physical layer of your semantic model. For example, <database name>.<catalog name >.<schema name >.<table name> or <database name>.<schema name >.<table name>.

Usage Tracking Logical Query Logging Table

Specifies the name of the database table you want to use to store logical query details. For example, <database name>.<catalog name >.<schema name >.<table name> or <database name>.<schema name >.<table name>.

Usage Tracking Maximum Rows

Indicates the number of rows allowed in usage tracking tables, with a value of 0 indicating an unlimited number of rows.

Valid Values: Any positive number (up to 64-bit integer)

Default: 0
Usage Tracking Physical Query Logging Table

Specifies the name of the database table you want to use to store physical query details. For example, <database name>.<catalog name >.<schema name >.<table name> or <database name>.<schema name >.<table name>.

Note: See Recommended Configuration Settings for Usage Tracking using SQL Server.

View Options

You use these options to configure default search and viewing settings for users working with analyses and dashboards.

These options apply only to analyses and dashboards. They don't apply to data visualizations.

Note:

If you change a view setting, you must apply the change for the new value to take effect.

Note:

In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle BI EE, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle BI EE, your configuration file settings are preserved but no values are displayed on the System Settings page, that is, they appear blank. You don't have to re-enter values on the System Settings page but, for clarity, you might decide to do so.

See Configure and Manage Analyses and Dashboards.

System Setting More Information
Default Scrolling Enabled

Specifies how data scrolls in these views: table, pivot table, heat matrix, and simple and advanced trellis views.

  • On — Data displays with a fixed header and content scrolling controls for users to browse the data.

  • Off — Data displays with content paging controls for users to browse the data.

Default: On
Prompt Auto Complete Matching Level

Specifies whether the auto-complete functionality uses matching to find the prompt value that the user enters into the prompt field. This setting doesn’t apply if the user accesses the Search dialog to locate and specify a prompt value.

  • StartsWith — Searches for a match that begins with the text that the user types. For example, the user types "M" and the following stored values are displayed: "MicroPod" and "MP3 Speakers System".

  • WordStartsWith — Searches for a match at the beginning of a word or group of words. For example, the user types "C" and the following values are displayed: "ComCell", "MPEG Camcorder", and "7 Megapixel Digital Camera".

  • MatchAll — Searches for any match within the word or words.

Valid Values: StartsWith, WordStartsWith, MatchAll

Default: MatchAll
Table/Pivot View: Maximum Visible Rows

Specifies the maximum number of rows you want displayed for content paging in table and pivot table views in analyses and dashboards.

The minimum number of rows you can specify to display is 100.

Valid Values: 100-5000

Default: 5000
View Interactions: Add/Remove Values

Specifies whether the Add/Remove Values option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Add/Remove Values option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Add/Remove Values option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Create/Edit/Remove Calculated Items

Specifies whether the Create/Edit/Remove Calculated Items option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Create/Edit/Remove Calculated Items option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Create/Edit/Remove Calculated Items option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Create/Edit/Remove Groups

Specifies whether the Create/Edit/Remove Groups option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Create/Edit/Remove Groups option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Create/Edit/Remove Groups option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Display/Hide Running Sum

Specifies whether the Display/Hide Running Sum option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Display/Hide Running Sum option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Display/Hide Running Sum option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Display/Hide Sub-totals

Specifies whether the Display/Hide Sub-totals option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Display/Hide Sub-totals option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Display/Hide Sub-totals option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Drill

Specifies whether the Drill (when not a primary interaction) option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Drill (when not a primary interaction) option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Drill (when not a primary interaction) option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: Off
View Interactions: Include/Exclude Columns

Specifies whether the Include/Exclude Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Include/Exclude Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Include/Exclude Columns option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: On
View Interactions: Move Columns

Specifies whether the Move Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Move Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Move Columns option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: On
View Interactions: Sort Columns

Specifies whether the Sort Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • On — The Sort Columns option is selected by default in the Analysis Properties dialog: Interactions tab.

  • Off — The Sort Columns option isn't selected by default in the Analysis Properties dialog: Interactions tab.

Default: On