About Advanced Configuration Options
You can configure several advanced service-level options by clicking System Settings in the Oracle Analytics Server Console.
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 restart the system for the new value to take effect.Note:
In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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
Valid Values: Default:
|
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.
Valid Values:
Default:
|
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.
Valid Values: Default: |
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. |
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. |
Connection Options
Connection externalization isn't supported in Oracle Analytics Server.
System Setting | More Information |
---|---|
Connection Externalization Enabled | This option isn't used. |
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 restart the system for the new value to take effect.Note:
In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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 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 repository. 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 repository. 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 restart the system for the new value to take effect unless 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.
Default:
|
Enable Subrequest Shippping |
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
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.
Default:
Restart 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.
Default:
|
Hide Loading Messages |
Specifies if a detailed message is displayed during data load processing.
Default:
|
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 |
Portal Path |
Specifies the URL of the dashboard page that's displayed by default when users sign in to Oracle Analytics. This setting applies to all users, but users can override it after they've signed in. |
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.
Default:
|
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.
Default:
|
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.
Default:
|
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 |
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 restart the system 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 Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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.
Users can override this setting in the workbook and canvas properties. Default:
|
Brushing Enabled for Subject Areas |
Specifies whether brushing is enabled by default for workbooks that use data from subject areas.
Users can override this setting in the workbook and canvas properties. Default:
|
Cache Dashboard Listing Dropdown Menu |
Specifies how much the Dashboards menu list on the Oracle Analytics Classic Home page is populated during a user session.
Default:
|
Cache Enable |
Specifies whether data query caching is enabled or disabled.
Default:
|
Enable Auto Insights on Datasets |
Specifies whether the Auto Insights feature is available when datasets are created or modified.
Default:
Restart 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.
Default:
|
Evaluate Support Level |
Specifies who can issue database functions: By default (
Valid Values: Default: |
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:
Default:
|
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-premise release in Oracle Analytics. Valid Values: |
Override Database Features |
Specifies if users can use request variables to override database features.
Valid Values:
Default:
|
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.
See STRONG_DATETIME_TYPE_CHECKING. Default:
|
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.
Note:
If you change a prompt setting, you must restart the system for the new value to take effect.Note:
In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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
Default:
|
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:
|
Case Insensitive Auto Complete |
Specifies whether, when a user enters a prompt value in analyses and dashboards, the auto-complete functionality is case-insensitive.
Default:
|
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.
Valid Values: Default: |
Support Auto Complete |
Enables or disables the auto-complete functionality available in prompts.
Default:
|
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 restart the system 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 Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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 the Contains HTML/JavaScript/CSS Markup option is displayed in various dialogs and editors where you can apply formatting. This option allows users to format content with valid HTML markup.
For security reasons, this option is turned off when you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server. To turn the feature on in Oracle Analytics Server, you must enable Allow HTML/JavaScript/CSS Content. Default:
|
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 restart the system 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 Analytics Server, 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, |
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 data model file (RPD). For example,
|
Usage Tracking Logical Query Logging Table |
Specifies the name of the database table you want to use to store logical query details. For example, |
Usage Tracking Maximum Rows |
Indicates the number of rows allowed in usage
tracking tables, with a value of Valid Values: Any positive number (up to 64-bit integer) Default:
|
Usage Tracking Physical Query Logging Table |
Specifies the name of the database table you want to use to store physical query details. For example, |
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 restart the system for the new value to take effect.Note:
In Oracle BI Enterprise Edition 12c, you use configuration files to customize various settings. In Oracle Analytics Server, you can use the Console (System Settings page). If you upgrade from Oracle BI Enterprise Edition 12c to Oracle Analytics Server, 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.
Default:
|
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.
Valid Values: Default: |
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:
Default:
|
View Interactions: Add/Remove Values |
Specifies whether the Add/Remove Values option is selected by default in the Analysis Properties dialog: Interactions tab.
Default:
|
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.
Default:
|
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.
Default:
|
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.
Default:
|
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.
Default:
|
View Interactions: Drill |
Specifies whether the Drill (when not a primary interaction) option is selected by default in the Analysis Properties dialog: Interactions tab.
Default:
|
View Interactions: Include/Exclude Columns |
Specifies whether the Include/Exclude Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default:
|
View Interactions: Move Columns |
Specifies whether the Move Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default:
|
View Interactions: Sort Columns |
Specifies whether the Sort Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default:
|