1 Feature Summary
This chapter describes the feature enhancements in this release.
Scheduled Noteworthy Enhancements
This guide outlines the information you need to know about new or improved functionality in the Oracle Retail Data Store update and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.
Column Definitions
-
Feature: Provides a description of the feature being delivered.
-
Module Impacted: Identifies the module impacted associated with the feature, if any.
-
Scale: Identifies the size of the feature. Options are:
-
Small: These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
-
Medium: These UI or process-based features are typically comprised of field, validation, or program changes. Therefore, the potential impact to users is moderate
-
Large: These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
-
Delivered: Is the new feature available for use immediately after upgrade or must the feature be enabled or configured? If no, the feature is non-disruptive to end users, and action is required (detailed steps below) to make the feature ready to use.
-
Customer Action Required: You must act before these features can be used. These features are delivered disabled, and you choose if and when to enable them.
| Feature | Module Impacted | Scale | Delivered | Customer Action Required? |
|---|---|---|---|---|
|
New and Updated Options |
||||
| RDOC Usage Monitoring and Session Management |
RDS |
Medium |
Yes |
Review settings to use the enhancements |
| RDOC Operational Email Notifications |
RDS |
Medium |
Yes |
Yes, to receive notifications |
| Additional Grants for Custom Schemas |
RDS |
Small |
Yes |
No |
| Preserve Customer-Defined ORDS Schema Aliases |
RDS |
Small |
Yes |
No |
New and Updated Options
This release enhances the Retail DB Ops Console (RDOC) with historical usage monitoring, session monitoring, and operational email notifications. Settings and Email Settings are now separate pages, and several new settings support capacity planning and operational notifications.
Monitoring is available after upgrade. Review the RDOC properties to ensure that capacity estimates and warning thresholds suit your environment. Email notifications require notification recipients and email delivery to be configured.
RDOC Usage Monitoring and Session Management
The RDOC Usage Monitoring page provides historical database CPU utilization and allocated storage usage across customer schemas. Customers can review the past 24 hours, 7 days, 30 days, or 90 days to identify changes and investigate workload patterns. Available history begins when measurements are collected.
CPU utilization is presented as a 15-minute trailing mean. The 7-day range preserves the highest trailing mean within each hour; the 30-day and 90-day ranges preserve the highest trailing mean within each day.
Storage usage includes reference lines for the configured Storage Soft Max and its fixed 75% warning level. These references support capacity planning; they do not represent physical storage limits or automatically increase capacity.
The Session Management page combines Session Count History, the All Sessions report, and the Session Management Log. Customers can compare session counts and long-running SQL activity with the configured pool-capacity estimate, then use AWR Reports, Top SQL, and DBMS Jobs to investigate. Customer database session counts indicate possible connection pressure; they do not directly measure checked-out ORDS connections.
RDOC Operational Email Notifications
Settings and Email Settings are now separate pages. The Settings page includes properties for the ORDS pool-capacity estimate, storage planning baseline, session warning threshold, open-transaction age threshold, and notification contacts. The session warning threshold is a percentage of the configured pool-capacity estimate. To receive notifications, review these properties and enter notification contact email addresses on Settings, then configure SMTP delivery on Email Settings and send a test email. Note existing email settings are preserved.
RDOC adds email notifications for:
-
Mean customer session utilization above the configured warning percentage in each of four consecutive 15-minute periods over the preceding hour, provided sufficient recent samples are available.
-
Open transactions in RDS Custom schemas that exceed the configured age threshold.
-
Allocated storage across customer schemas reaching 75% of the configured Storage Soft Max.
Notifications direct customers to review the affected workload and relevant settings. They do not automatically change capacity, end sessions, or commit or roll back transactions.
Additional Grants for Custom Schemas
Custom schemas now have direct SELECT grants on V_$SQL,
V_$SESSION, and GV_$SESSION. These grants allow customers to
compile permitted views and stored procedures that reference SQL and session information.
Preserve Customer-Defined ORDS Schema Aliases
RDS patch upgrades preserve existing customer-defined ORDS RESTful Services schema aliases for auxiliary APEX workspaces. This prevents patching from replacing a configured alias with the default value and changing the endpoint paths used by customer extensions and integrations.
No customer action is required to enable this change.