Jay-Rajput/oci_data huggingface dataset:
Configure Oracle Fusion Analytics Warehouse Data


As the cloud account administrator with the Functional Administrator or System Administrator application role, you specify the data load and reporting configuration details, and create data pipelines for functional areas that determine how the source data from Oracle Fusion Cloud Applications is loaded and displayed in the data warehouse.

For example, you might specify the Initial Extract Date as January 1, 2019, specify the global currency as US Dollars (USD), and select the exchange rate to convert transactions to the global currency.
 Note

The times visible in the Console are in local time zone. However, Oracle Fusion Analytics Warehouse stores the values for the Warehouse Refresh Date Time and Scheduled Date in the Coordinated Universal Time (UTC) in the autonomous data warehouse.

Any data you load into the autonomous data warehouse in Oracle Fusion Analytics Warehouse is subject to the data access controls that may not always match those in the source system. For example, if User1 doesn't have the rights to access some data in your source system, then when you bring that data over to the autonomous data warehouse in Oracle Fusion Analytics Warehouse, this User1 can access that particular data. If you want to have the same controls on the data, then you must ensure that this particular User1 has the same data access rights as your source system in your Oracle Fusion Analytics Warehouse user setup.

Topics:

Typical Workflow to Configure Data

About Data Pipelines for Functional Areas

About Data Refresh Performance
About Pipeline Parameters
Set Up the Pipeline Parameters

Create a Data Pipeline for a Functional Area

Edit a Data Pipeline for a Functional Area

Activate a Data Pipeline for a Functional Area

About Global Parameters
Set Up the Global Report Parameters
About Reporting Configurations
Set Up the Reporting Configurations for Enterprise Resource Planning
Set Up the Reporting Configurations for Human Capital Management

Deactivate a Data Pipeline for a Functional Area

Delete a Data Pipeline for a Functional Area

Refresh a Data Pipeline for a Functional Area

Reset a Data Pipeline for a Functional Area

Reset the Data Warehouse
Reset the Cache
Reset the Data Source (Preview)
Reset and Reload the Data Source (Preview)
View Load Request History
View the Audit Log
View Records Rejected in Extraction
Prioritize Datasets for Incremental Refresh (Preview)
About Augmenting Your Data
Create a Dimension Alias
About Managing Data Connections
Disable Data Pipeline
Schedule Frequent Refreshes of Data
Schedule Periodic Full Reload of Functional Area Data
Schedule Frequent Refreshes of Warehouse Tables
Extend Data with Custom Data Configurations
Autoscaling
 Events
Required IAM Policy
Tagging Resources
Before You Begin
Using the Console
To create a metric-based autoscaling configuration
To create a schedule-based autoscaling configuration
To edit an autoscaling configuration
To edit an autoscaling policy
To view the pool size forecast
To enable or disable a schedule-based autoscaling policy
To disable an autoscaling configuration
To delete an autoscaling configuration
To manage tags for an autoscaling configuration
Using the API
Known Issues for ADM


Application Dependency Management has no known issues.
OCIFS Utility

Mounting and Unmounting with OCIFS
OCIFS Mounting Restrictions
OCIFS Mount Options
OCIFS Authentication
API Key-Based Authentication
Instance Principal Authentication
OCIFS Cache Options
cache
cache-fsfree
cache-keep
cache-purge
cache-reuse
Migrating Databases to the Cloud

Choosing a Migration Method
Migration Connectivity Options
Migration Methods
Use Trace Explorer


You can use Trace Explorer to view traces and spans and identify performance issues and bottlenecks in your monitored application, from browser to database.

Application Performance Monitoring includes an implementation of a Distributed Tracing system. It accepts OpenTracing and OpenTelemetry spans, combines them into traces and monitors both traces and individual spans. To enable an application for OpenTracing, each component (JVM, JavaScript, and so on) must be instrumented with a tracer. You can do so by embedding the tracer in the application code, or adding it during runtime using bytecode instrumentation. Application Performance Monitoring uses various data sources to upload traces and spans. Application Performance Monitoring is also integrated with Oracle Functions and can be enabled to upload and monitor function trace data in Trace Explorer. For information, see Application Performance Monitoring Data Sources.

Here's a diagram that illustrates how trace data is collected:

In the diagram:

The transaction begins with an AJAX call from a Browser and the browser agent injects a trace ID and a span ID for the operation into the HTTP header.
The next tracer, in Microservice A, extracts the trace ID and span ID, uses the same trace ID and injects a new span ID for the next downstream HTTP call.
The transaction progresses from one service to another till it reaches the last service, which in this case is a call to the database. Once the call to the database returns, the tracer sends the span data to Application Performance Monitoring. This data includes the trace and span IDs, the duration of the operation, and other dimensions such as the service and operation name, the SQL text and ID, and details specific to the operation.
As each call returns, the tracers send individual spans for each of the returned calls, containing relevant details about the specific operation that was completed. Eventually, the first AJAX call that initiated the trace is completed, the agent on the browser sends its data as the root span, which marks the trace as complete.

After trace data is uploaded, Trace Explorer enables you to explore traces for diagnostics and ensures visibility into all spans in all traces at all times. It provides the use of a simple query language that enables you to find, sort, and group spans. You can use Trace Explorer to:

Monitor individual traces, view their details, and analyze large sets of traces and spans to identify trends and anomalies.
Detect slow traces, traces with errors, and those using a specific server or data source.
Drill down into specific spans, such as page loads and AJAX calls to isolate and identify issues

You can also use dashboards to monitor your application servers and end-user experience in real time. For information on dashboards, see Work with Dashboards.

Topics:

Perform Trace Explorer Prerequisite Tasks

Monitor Traces in Trace Explorer

About Trace and Span Attributes
Getting Started with Oracle Cloud Infrastructure Database Migration

Before You Begin
Creating Resources
Giving Permissions to Database Migration Users
Configuring SUDO Access
Accessing the Database Migration Service
Comparable Services: OCI, AWS, Azure, and Google Cloud


Find the service you’re looking for with Oracle Cloud Infrastructure (OCI).

See Oracle, AWS, Microsoft Azure, and Google Cloud services compared to find the OCI services you can choose when migrating to Oracle's platform.
Using Cloud Shell

Getting Started with Cloud Shell
Transferring Files
Customizing the Cloud Shell OCI CLI Configuration
Managing Cloud Shell Regions
Resetting Your Cloud Shell Environment
Backing Up and Restoring Your Cloud Shell Home Directory using Object Storage
Working with Python Versions
Working with kubectl Versions
Managing Language Runtimes
Getting the Public IP Address for a Cloud Shell Session



For more information click here https://docs.oracle.com/en-us/iaas/Content/API/Concepts/devcloudshellgettingstarted.htm#Using_Cloud_Shell
Overview of Identity and Access Management

IAM Components
Services You Can Control Access To
The Administrators Group and Policy
Example Scenario
Viewing Resources by Compartment in the Console
The Scope of IAM Resources
Creating Automation with Events
Resource Identifiers
Ways to Access Oracle Cloud Infrastructure
Limits on IAM Resources
Basics of Oracle Cloud Migrations

Understanding Test Migration and Production Migration
Restoring Source Environment After Migration
Using Bounce


Learn how the OCI users can work with self-service Bounce to shut down, start up, and bounce DB Tier and MidTiers and/or MidTier components (individual or combination of components).

To use bounce:

In the dashboard, click the hamburger menu ( three horizontal lines) at the top-left corner.
From the navigation pane, click Bounce.
In the Bounce page, click Initiate Bounce.
In the Initiate Bounce page, select the RFC Details.
Select the Environment which needs to be bounced. This list is populated with all the environments associated with the support identifier (SI).
For Operation, select any of the following:
Bounce
Stop
Start (This option is visible only when previous RFC operation is stopped)
For Services, select any of the following:
All (Apps and DB) - This will Bounce/Stop/Start all MT and DB services.
All Apps - This will Bounce/Stop/Start all MT services.
Apps Components - This will allow users to select individual components like Apache, OPMN etc.

The Bounce/Stop field is automatically filled in with data on the host and service that need to be restarted/stopped.

For the Operation Stop, you must additionally select Blackout Duration. You must start the services before the Blackout duration by creating Start Services RFC.
Click Customer Note to add an action plan or any other relevant information you want included in the RFC.
Click Submit.

The Schedule Execution pop up opens.

If you click Not Now, you will be returned to the listings in the Bounce page.
If you click Yes, the Bounce will be scheduled for execution in 15 minutes.
If you click Pick Future, you will be taken to the Details page.



For more information click here https://docs.oracle.com/en-us/iaas/Content/managed-cloud-self-service/mgdcloudss_using_bounce.htm
Usage Limit Error During Provisioning


This topic describes how to resolve a usage limit error during database provisioning.

When you reach the service limit for a resource, you receive an error when you try to create a new resource of that type. You can submit a request to increase your limit using the OCI Console. You cannot create a new resource until you are granted an increase to your service limit or you terminate an existing resource.

 Note



OracleDB for Azure is subject to the standard OCI tenancy service limits for resources like Oracle Databases or MySQL database systems. There are no separate service limits for OracleDB for Azure resources.

When requesting a service limit increase for OracleDB for Azure resources, you will need to specify the corresponding OCI service, such as the OCI Database service (which covers Autonomous Database, Base Database, and Oracle Exadata Database) and the OCI MySQL Heatwave service.

See the following topics for more information:

Service Limits
Requesting a Service Limit Increase
Limits by Service
Burstable Instances
 Compared to Regular Instances
Limitations and Considerations
Billing
Creating a Burstable Instance
Overview of Flexible Network Load Balancer


Understand what network load balancers are, and how to get access to links that provide details on specific network load balancer topics.

The Oracle Cloud Infrastructure Flexible Network Load Balancer service (Network Load Balancer) provides automated traffic distribution from one entry point to multiple backend servers in your virtual cloud network (VCN). It operates at the connection level and load balances incoming client connections to healthy backend servers based on Layer 3/Layer 4 (IP protocol) data. The service offers a load balancer with your choice of a regional public or private IP address that is elastically scalable and scales up or down based on client traffic with no bandwidth configuration requirement.

Network Load Balancer provides the benefits of flow high availability, source and destination IP addresses, and port preservation. It is designed to handle volatile traffic patterns and millions of flows, offering high throughput while maintaining ultra low latency. Network load balancers have a default concurrent connection limit of 330,000 connections per Availability Domain (AD). In three AD regions, by default, network load balancers have a concurrent connection limit of one million. Network Load Balancer is the ideal load balancing solution for latency sensitive workloads.

Network Load Balancer is also optimized for long-running connections in the order of days or months. A given flow is always forwarded to the same backend for the lifetime of the connection, making it best suited for your database type applications. You can configure application-specific health checks to ensure that the load balancer directs traffic only to healthy backends.

The Network Load Balancer documentation contains the following major sections:

Introduction to Network Load Balancer

Network Load Balancer Management

Health Status for Network Load Balancers

Backend Sets for Network Load Balancers

Backend Servers for Network Load Balancers

Listeners for Network Load Balancers

Health Check Policies for Network Load Balancers

Work Requests for Network Load Balancers

Network Load Balancer Metrics
Managing Mount Targets

Overview
Details About Your Mount Target
Limitations and Considerations
Required IAM Policy
Overview of Fusion Applications Environment Management

Fusion Applications Environment Management Concepts
Region Availability
Setting the Console Time Zone for Fusion Applications
Understanding OCI Features Used by Fusion Applications Environment Management
Getting Started with Fusion Applications Environment Management
Management Agents Administration Tasks

Management Agents Console Overview
Deploy Service Plug-ins
Enable Agent Logs
Control Management Agents
Manage Install Keys
Upgrade Management Agents
Remove Management Agents
Management Agent Source Credentials
Management Agent Audit Logs
Using Java with Management Agent
Overview of Network Firewall

Security Features
Network Firewall Concepts
Ways to Access Network Firewall
Authentication and Authorization
Required IAM Service Policy
Moving Firewalls and Policies to a Different Compartment
Monitoring Resources
Creating Automation with Events
Tagging Resources
Next Steps
Manage Dashboards


Management Dashboard provides a set of Oracle-defined dashboards for the Observability & Management services it supports and enables you to create custom dashboards that meet your specific requirements.

Topics:

Access Dashboards

Create a Custom Dashboard

Customize an Oracle-defined Dashboard

Export and Import Dashboards

Set Up a Cross-region Dashboard

Enable Cross-service Dashboards
Using Custom Properties in Search


You can customize your search results to use the custom properties that you create in Data Catalog.

You can configure up to seven custom properties to be displayed in the search results list.

Consider a custom property named Data owner that is configured to show up in search results, Custom Filters, sort, and associated with all data entities in your data catalog.

Console
CLI
API
On the Home tab, click Data Entities.
In the Data Entities list, view the Data owner custom property for all the data entities in the search summery.
The Data owner custom property also shows up under Custom Filters. Select a data owner. The Data Entities list is updated to show only the results that match the selected data owner.
From the sort list, select either ascending or descending for Data owner. The Data Entities list is updated to show the results in the selected order by data owner.
Listing Vulnerability Audits


Describes how to list the vulnerability audits in your tenancy.

Console
CLI
API
Open the navigation menu and click Developer Services. Under App Dependency Management, click Vulnerability Audits.
On the Vulnerability audits page, from the list of compartments on the left side, select a compartment.
The page displays the list of vulnerability audits.
Creating a Preview URL


Create a preview URL in Media Streams and view your content asset in a browser.

 Note

The Safari browser can play the HLS natively. Other browsers require an extra plugin or supported application to preview the HLS format.
Console
CLI
API

You can generate a Preview URL of the playlist asset from the Playlist Asset details page.

Open the navigation menu and click Analytics & AI. Under Media Services, click Media Streams.
On the Distribution Channels list page, select the compartment that contains the distribution channel for where you want to generate the preview URL.
Click the name of the distribution channel from which you want to generate the Preview URL.
On the Distribution Channel details page, under Resources, click Playlist Assets.
In the Playlist Assets section, click the playlist asset for which you want to generate the preview URL.
On the Playlist Asset details page, in the Preview URL section, select a packaging.
Specify the session token expiration value between 10 minutes to 24 hours. The preview URL expires after the specified time period.
Click Generate.
A preview URL is generated for the asset.
Click Copy.
You can view the asset by playing it in a supported browser or application.
FastConnect: Colocation with Oracle

Getting Started with FastConnect
Managing Your Connection
Monitoring Your Connection
Troubleshooting
OCI Functions Support for Private Network Access


Find out about how OCI Functions supports private network access to enable private communication between functions and other resources.

OCI Functions supports private communication between a function in a VCN and other Oracle Cloud Infrastructure resources and supported services in the Oracle Services Network without the traffic going over the internet. You can:

enable a function in the VCN to access other resources and services
enable other resources and services to invoke functions in the VCN

To provide such private access:

create and deploy functions in private subnets
add a service gateway to the VCN

For more information, see Access to Oracle Services: Service Gateway.
Supported Images (Including Custom Images) and Shapes for Worker Nodes

Supported Images for Managed Nodes
Supported Shapes for Managed Nodes and Virtual Nodes
Supported Images and Shapes for Self-Managed Nodes
Managing Compartments

Required IAM Policy
Tagging Resources
Working with Compartments
Deleting Compartments
Moving a Compartment to a Different Parent Compartment
Using the Console
Using the API
Routing Traffic to a Network Firewall

To route on-premises traffic through a network firewall
To route internet traffic through a network firewall
To route intra-VCN traffic through a network firewall
Next Steps
Managing User Capabilities for Federated Users

About User Capabilities
Required IAM Policy
Prerequisites
Viewing Provisioned Federated Users in the Console
Using the Console
Using the API
Working with Block Volumes


Oracle Cloud Infrastructure Block Volume lets you dynamically provision and manage block storage volumes. You can create, attach, connect, and move volumes, as well as change volume performance, as needed, to meet your storage, performance, and application requirements. After you create a volume, you can attach and connect a volume to an instance, and then you can use the volume like a regular hard drive. You can also disconnect a volume and attach it to another instance without the loss of data.

This section includes the following tasks:

Creating a Block Volume

Attaching a Block Volume to an Instance

Connecting to a Block Volume

Listing Volumes

Listing Volume Attachments
Getting a Block Volume's Details

Editing a Block Volume's Settings

Replicating a Volume
Cloning a Block Volume
Disconnecting From a Volume

Detaching a Volume

Deleting a Block Volume

IAM Policy

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  to work in.

For administrators: The policy in Let volume admins manage block volumes, backups, and volume groups lets the specified group do everything with block volumes and backups.

If you're new to policies, see Getting Started with Policies and Common Policies. For reference material about writing policies for instances, cloud networks, or other Core Services API resources, see Details for the Core Services.
Monitoring Resources

You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring and Notifications.

Tagging Resources

Apply tags to your resources to help organize them according to your business needs. Apply tags at the time you create a resource, or update the resource later with the wanted tags. For general information about applying tags, see Resource Tags.
Creating a Group


Use groups in OS Management Hub to standardize and unify content across the instances.

Console
CLI
API
Open the navigation menu and click Observability & Management. Under OS Management Hub, click Groups.
Click Create.
On the Add basic details page, provide the following details, and then click Next:
Group name: Enter a name for the group. You change the name at any time. The name doesn't need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the group. Avoid entering confidential information.
Description: (Optional) Enter a description for the group. Avoid entering confidential information.

Show advanced options: Click to add tags to this resource.

If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, ask an administrator or skip this option. You can apply tags later.

On the Select software sources page, select software sources to use for the group, and then click Next. These sources determine which instances you can add to the group on the next page.

OS vendor: Select the vendor for the software source. For example, Oracle.

OS version: Select the version for the software source. For example, Oracle Linux 9.

Architecture: Select the architecture for the software source. For example, x86_64.

Available software sources: Select the software sources to add.

(Optional) On the Add instances page, select instances to add to the group.
 Note

Available instances match the OS vendor, version, and architecture of the group. Offline instances and instances assigned to another group or lifecycle environment aren't listed.
Select a compartment.
Select instances from the compartment to add to the group, and then click Select instances to attach.
Repeat the preceding steps to select instances from other compartments.
Review the instances and remove any instances from the selection that you don't want added to the group.
Click Next.
Review the details of the group, and then click Submit to create the group.



For more information click here https://docs.oracle.com/en-us/iaas/osmh/doc/create-group.htm#top
Policy Syntax

Subject
Verb
Resource-Type
Location
Conditions