About System Settings
Administrators can set a range of advanced, service-level options through the Advanced System Settings page. For example, you might want to change the default currency and time zone for analyses and dashboards to values that better suit your organization.
When Do System Settings Take Effect?
When you change your system settings, the time it takes for the changes to take effect can vary. Some setting changes happen right away, but most take a few minutes.
After the changes take effect, it's a good idea to refresh your browser to see any visible differences in the user interface. If other users are signed in when you make system setting changes, they must refresh their browsers too. In some cases, users might need to sign out and sign back in to see the changes.
- Look for the Change Effective item in the More Information column. This tells you the time it takes to change the setting.
- See the Apply Required item to understand whether you need to click Apply to implement your changes.
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:
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: 1,2,3,4,6 Default: 1 Apply Required: No Change Effective: After a few minutes API Key: AnalyticsPublisherReportingToolbarMode |
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: answerResults, answerCriteria Default: answerResults Apply Required: No Change Effective: After a few minutes API Key: AnswersEditorStartTab |
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: asc, desc, rpd Default: rpd Apply Required: No Change Effective: After a few minutes API Key: AnalysisSubjectAreaSortingOrder |
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 Customize Links on the Classic Home Page. Apply Required: No Change Effective: After a few minutes API Key: CustomLinksXml |
URL for Blocking Queries in Analyses |
Specifies the URL for the JavaScript file to validate query criteria and block queries. See Validate and Block Queries in Analyses Using Custom JavaScript. Apply Required: No Change Effective: After a few minutes API Key: QueryBlockingScriptURL |
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 Apply Required: No Change Effective: After a few minutes API Key: WriteBackTemplateXML |
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) Apply Required: No Change Effective: Immediately API Key: EmailMaxEmailSizeKB |
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) Apply Required: No Change Effective: Immediately API Key: EmailMaxRecipients |
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, Use a comma to separate multiple domain names. For example,
Apply Required: No Change Effective: Immediately API Key: EmailSafeDomains |
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.
Default: On Apply Required: No Change Effective: Immediately API Key: EmailUseBcc |
Use RFC 2231 Encoding |
Specifies how to encode MIME email parameters. By default, RFC 2047 is used.
Default: Off Apply Required: No Change Effective: Immediately API Key: EmailUseRFC2231 |
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:
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. Apply Required: No Change Effective: After a few minutes API Key: AnalysisCurrenciesXml |
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 semantic model. See About Session Variables. Apply Required: No Change Effective: After a few minutes API Key: DefaultDataOffsetTimeZone |
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. Apply Required: Yes Change Effective: After a few minutes API Key: DefaultTimeZoneforDateCalculations |
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. Apply Required: No Change Effective: After a few minutes API Key: DefaultUserPreferredTimeZone |
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. Apply Required: No Change Effective: After a few minutes API Key: UserCurrencyPreferencesXml |
Other Options
These system setting options in the Console enable you to set the behavior for a variety of actions such as database queries, default URLs, display defaults, and sorting.
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: Off Apply Required: Yes Change Effective: After a few minutes API Key: DataQueryDisableRightTrimVARCHARData |
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
Default: Default Apply Required: Yes Change Effective: After a few minutes API Key: EnableSubrequestShipping |
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: On for a brand new service and Off for an existing service. Apply Required: No Change Effective: After a few minutes API Key: EnforceSafeDomainsActions |
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: Off Apply Required: Yes Change Effective: After a few minutes API Key: HideEPMCloudMembersWithNoAccess |
Hide Loading Messages |
Specifies if a detailed message is displayed during data load processing.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: HideLoadingMessages |
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. Apply Required: Yes Change Effective: After a few minutes API Key: DataQueryLocale |
Portal Path |
Specifies the path of the dashboard page that's
displayed by default when users sign in to Oracle Analytics. For example,
You can specify a single path for all users and multiple paths by
user role, for example 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. Apply Required: No Change Effective: After a few minutes API Key: PortalPath |
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: On Apply Required: Yes Change Effective: After a few minutes API Key: RecursiveDatetimeTypeChecking |
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: Off Apply Required: No Change Effective: After a few minutes API Key: AnalysisRepeatRowsExcelExportsTablesPivots |
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: Off Apply Required: Yes Change Effective: After a few minutes API Key: SortNullValuesFirst |
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. Apply Required: Yes Change Effective: After a few minutes API Key: DataQuerySortOrderLocale |
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:
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 |
---|---|
Always Use DBMS_RANDOM in Oracle Data Sources |
Specifies whether Contextual
Insight algorithms use the
Default: On Apply Required: Yes Change Effective: After a few minutes API Key: AlwaysUseDBMSRANDOMOracleDataSources |
Brushing Enabled for Data Sets |
Specifies whether brushing is enabled by default for workbooks that use data from datasets.
Users can override this setting in the workbook and canvas properties. Default: On Apply Required: No Change Effective: Immediately API Key: EnableBrushingSubjectAreas |
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: On Apply Required: No Change Effective: Immediately API Key: EnableBrushingSubjectAreas |
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.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: CacheDashboardListingDropdownMenu |
Cache Enable |
Specifies whether data query caching is enabled or disabled.
Default: On Apply Required: Yes Change Effective: Immediately API Key: EnableDataQueryCache |
Default Limit Values By for Filter |
Determines the default behavior of the workbook filter option Limit Values By.
Users can override the default that you select here, within their workbooks. Default: Auto Apply Required: No Change Effective: After a few minutes API Key: DefaultLimitValuesByForFilters |
Enable Auto Insights on Datasets |
Specifies whether the Auto Insights feature is available when datasets are created or modified.
Default: On Apply Required: No Change Effective: After a few minutes API Key: EnableAutoInsightsDatasets |
Enable Database Analytics Node in Data Flows |
Specifies whether the Database Analytics node is displayed in data flows.
Default: On Apply Required: Yes Change Effective: After a few minutes API Key: EnableDatabaseAnalyticsNodeDataFlows |
Enable Immediate Dashboard Rendering |
Specifies whether to display available dashboard content immediately or wait until all the dashboard content is ready.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: EnableImmediateDashboardRendering |
Evaluate Support Level |
Specifies who can issue database functions: By default (
Valid Values: 0, 1, 2 Default: 0 Apply Required: Yes Change Effective: After a few minutes API Key: EvaluateSupportLevel |
Load Semantic Models Using Multiple Threads |
Specifies if semantic models load using multiple threads. If you find that your large datasets load slowly and impact system processing times, enabling this option may improve performance.
Default: Off Apply Required: Yes Change Effective: After a few minutes API Key: LoadSemanticModelsWithMultipleThreads |
Maximum Query Limit (seconds) |
Specifies the maximum length of time a single query can run before it's canceled and users see a timeout message. The default is 660 seconds (11 minutes). Valid Values: 60-660 Default: 660 Apply Required: No Change Effective: After a few minutes API Key: MaximumQueryLimit |
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 Apply Required: Yes Change Effective: After a few minutes API Key: MaximumWorkingFilePercentSize |
Mobile Data Watch Service Enabled |
Specifies if the Data Watch service is active.
Default: On Apply Required: No Change Effective: Immediately API Key: EnableMobileDataWatchService |
Mobile Data 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 Apply Required: No Change Effective: Immediately API Key: MobileDataWatchServiceFrequency |
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 Apply Required: Yes Change Effective: After a few minutes API Key: OBIEECompatibilityRelease |
Override Database Features |
Specifies if users can use request variables to override database features.
Valid Values: 0, 1 , 2 Default: 0 Apply Required: Yes Change Effective: After a few minutes API Key: OverrideDatabaseFeatures |
Query Limit Extension |
Determines whether the query limit can extend to 60 minutes to accommodate the occasional, longer running query.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: QueryLimitExtension |
Restrict Data Export and Delivery |
Restricts the maximum number of rows users can export or deliver by email in formatted and unformatted content. Data export and delivery limits depend on the size of your Oracle Analytics service. Valid Values: Maximum - no restriction, 90% of Maximum, 80% of Maximum, 70% of Maximum, 60% of Maximum, 50% of Maximum, 40% of Maximum, 30% of Maximum, 20% of Maximum, 10% of Maximum, Minimum - 1000 rows Default: Maximum - no restriction Apply Required: No Change Effective: After a few minutes API Key: RestrictDataExportAndDelivery |
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: On Apply Required: Yes Change Effective: After a few minutes API Key: StrongDatetimeTypeChecking |
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:
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 On:
Default: On Apply Required: No Change Effective: After a few minutes API Key: AutoApplyDashboardPromptValues |
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 Apply Required: No Change Effective: After a few minutes API Key: EnableAnalysisAutoSearchPromptDialog |
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: On Apply Required: No Change Effective: After a few minutes API Key: AutoCompletePromptDropDownsCaseInsensitive |
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: always, never, asDataValue Default: always Apply Required: No Change Effective: After a few minutes API Key: AnalysisPromptsShowNullValueWhenColumnIsNullable |
Support Auto Complete |
Enables or disables the auto-complete functionality available in prompts.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: EnableAnalysisAutoCompletePrompt |
Security Options
Use Security options to control how users can perform specific actions in analyses and dashboards.
Most of these options apply only to analyses and dashboards. They don't apply to data visualizations or pixel-perfect reports. The exception is User Inactivity Timeout, which applies to analyses, dashboards, and data visualizations.
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 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.
For security reasons, markup is not allowed 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: On Open Apply Required: No Change Effective: After a few minutes API Key: AllowHTMLJavaScriptCSSContent |
Enable Push Notifications |
Specifies if mobile application push notifications are enabled (on) or disabled (off).
Default: On Apply Required: No Change Effective: Immediately API Key: EnableMobilePushNotifications |
Export Data to CSV and Tab-Delimited Files as Text |
Specifies if leading apostrophes are added when data is exported to CSV or tab-delimited files, so all fields are treated as text.
See Export the Results of
Analyses.
Note: This setting applies only to visualizations and analyses. It doesn't apply to pixel-perfect reports.Default: Off Apply Required: No Change Effective: After a few minutes API Key: ExportDataToCSVFilesAsText |
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 setting overrides any Save thumbnails value set in the Workbook Properties dialog at the individual workbook level. Note: This setting doesn't apply to watchlists because they don't use thumbnails. Instead, watchlists display miniaturized visualizations that reload whenever you refresh the Home page.
Default: On Apply Required: No Change Effective: After a few minutes API Key: SaveWorkbookThumbnail |
Sign Out Inactive Users Automatically |
Specifies whether to automatically sign out users after the inactivity timeout is reached.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: SignOutInactiveUsersAutomatically |
TLS Connection Mode |
Specifies the security configuration that's used on external data source connections that use TLS.
This setting applies to both public and private data source connections. Default: Legacy Apply Required: Yes Change Effective: After a few minutes API Key: TLSConnectionMode |
URL for Browser Script Actions |
Specifies the URL for the JavaScript file containing custom Browser Script Actions. Apply Required: No Change Effective: After a few minutes API Key: URLBrowserScriptActions |
User Inactivity Timeout (minutes) |
Specifies the number of minutes users are inactive before their browser or mobile connection must be re-authenticated. This system setting applies to analyses, dashboards, and data visualizations. Valid Values: 5 - 480 Default: 60 Apply Required: No Change Effective: After a few minutes API Key: UserInactivityTimeout |
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:
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 |
---|---|
Enable Usage Tracking |
Specifies whether usage tracking is enabled. You must enable this setting to activate all other settings in the Usage Tracking section of this page.
Default: On Apply Required: Yes Change Effective: After a few minutes API Key: EnableUsageTracking |
Usage Tracking Connection Pool |
Specifies the name of the connection pool you
created for your usage tracking statistics database. For
example, API Key: UsageTrackingConnectionPool Apply Required: Yes Change Effective: After a few minutes |
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, Apply Required: Yes Change Effective: After a few minutes API Key: UsageTrackingInitBlockTable |
Usage Tracking Logical Query Logging Table |
Specifies the name of the database table you want to use to store logical query details. For example, Apply Required: Yes Change Effective: After a few minutes API Key: UsageTrackingLogicalQueryLoggingTable |
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 Apply Required: Yes Change Effective: After a few minutes API Key: UsageTrackingMaximumRows |
Usage Tracking Physical Query Logging Table |
Specifies the name of the database table you want to use to store physical query details. For example, Apply Required: Yes Change Effective: After a few minutes API Key: UsageTrackingPhysicalQueryLoggingTable |
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 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 tables, pivots, heat matrix, and simple and advanced trellis visualizations.
Default: On Apply Required: No Change Effective: After a few minutes API Key: |
Enable Enrichments in Workbooks |
Specifies whether workbook editors can add dataset enrichments to a visualization directly from the Data Panel. This setting enables enrichments in workbooks for all users. Workbook editors who own a dataset or have editing privileges for it can enable or disable knowledge enrichments for that dataset using the Enable Knowledge Enrichments option. See Enable Knowledge Enrichments in the Workbook Editor.
Default: On Apply Required: No Change Effective: After a few minutes API Key: |
Enable Personalization in Workbooks |
Specifies whether users can personalize workbooks.
Default: On Apply Required: No Change Effective: After a few minutes API Key:
|
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: StartsWith, WordStartsWith, MatchAll Default: MatchAll Apply Required: No Change Effective: After a few minutes API Key: |
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 Apply Required: No Change Effective: After a few minutes API Key: |
View Interactions: Add/Remove Values |
Specifies whether the Add/Remove Values option is selected by default in the Analysis Properties dialog: Interactions tab.
Default: Off Apply Required: No Change Effective: After a few minutes API Key: |
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: Off Apply Required: No Change Effective: After a few minutes API Key: |
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: Off Apply Required: No Change Effective: After a few minutes API Key: |
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: Off Apply Required: No Change Effective: After a few minutes API Key: |
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: Off Apply Required: No Change Effective: After a few minutes API Key: |
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: Off Apply Required: No Change Effective: After a few minutes API Key: |
View Interactions: Include/Exclude Columns |
Specifies whether the Include/Exclude Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default: On Apply Required: No Change Effective: After a few minutes API Key: |
View Interactions: Move Columns |
Specifies whether the Move Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default: On Apply Required: No Change Effective: After a few minutes API Key: |
View Interactions: Sort Columns |
Specifies whether the Sort Columns option is selected by default in the Analysis Properties dialog: Interactions tab.
Default: On Apply Required: No Change Effective: After a few minutes API Key: |