Jay-Rajput/oci_data huggingface dataset:
Connecting to Your Instance

Before You Begin
Connecting to Your Linux Instance Using SSH
Connecting to a Linux Instance from a Unix-Style System
Connecting to a Linux Instance from a Windows System Using OpenSSH
Connecting to a Linux Instance from a Windows System Using PuTTY
Running Administrative Tasks on the Instance
What's Next
Replicate data


Learn to create and run GoldenGate processes.

Articles in this section:

Create data replication resources
Explore the deployment console
Add Extracts
Add a Distribution Path
Add a Receiver Path
Add Replicats
Using Admin client
Replicating a Migration Asset Manually


Replicate a migration asset manually.

Console
CLI
API
Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Migrations.
On the Migrations page, click the active migration project that has the migration assets that you want to replicate.
On the Migration project details page, from Resources, click Migration assets.
Click the active migration asset that you want to replicate.
On the Migration asset details page, click Replicate.
In the Replicate asset dialog box, click Replicate.
Workflow for Using Data Catalog


Take a look at the tasks that you perform as a data catalog user.

Task	Description
Accessing a Data Catalog instance	Open your Data Catalog instance.
Creating a Data Asset	Register your data sources in the Data Catalog as data assets.
Harvesting a data asset	Harvest technical metadata from data assets.
Creating a business glossary	Create a business glossary to define your company concepts and establish common understanding.
Linking glossary terms to data objects	Link business terms to data objects.
Linking tags to data objects	Annotate data objects with free-form tags.
Finding relevant data	Search, browse, or explore the Data Catalog to find useful and trusted data.
Managing Multifactor Authentication

Required IAM Policy
About Multifactor Authentication
General Concepts
Supported Authenticator Apps
Working with MFA
Restricting Access to Only MFA-Verified Users
Sign in Process After Enabling MFA
What To Do If You Lose Your Registered Mobile Device
Unblocking a User After Unsuccessful Sign-in Attempts
Disabling MFA
Deleting Inactive MFA TOTP Devices
Using the Console
Using the API
Managing Stacks and Jobs

Required IAM Policy
Viewing Metric Properties


OCC enables you to view the metadata for the available metrics.

Console
CLI
API

This task can't be performed using the Console.
Manage Widgets


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

The topics in this section provide information on the custom widgets you can create in Management Dashboard. In addition, you can:

Create and execute a search query in the Logging Analytics Log Explorer, save the search as a widget and add it to a dashboard. For information, see Save a Log Search and Add It to a Dashboard.
Save a SQL query in the Operations Insights Data Object Explorers, share it as a widget and add it to a dashboard. For information, see Save and Share SQL Queries.

Topics:

View Widgets

Create a Metric Data Explorer Widget

Create a Query-based Widget

Add a Widget Group

Add Tabs to a Widget Group
Service Limits

Bastion Limits
Big Data Limits
Block Volume Limits
Blockchain Platform Limits
Certificates Limits
Cloud Guard Limits
Cloud Shell Limits
Compute Limits
Compute Cloud@Customer Limits
Connector Hub Limits
Container Engine for Kubernetes Limits
Container Instances Limits
Container Registry Limits
Content Management Limits
Console Dashboards Limits
Data Catalog Limits
DevOps Limits
Data Flow Limits
Data Integration Limits
Data Labeling Limits
Data Safe Limits
Data Science Limits
Data Transfer Limits
Database Limits
Database Migration Limits
Database Tools Limits
Digital Assistant Limits
DNS Limits
Email Delivery Limits
Events Limits
Exadata Fleet Update Limits
File Storage Limits
Flexible Network Load Balancer Limits
Full Stack Disaster Recovery Limits
Functions Limits
GoldenGate Limits
Health Checks Limits
IAM With Identity Domains Limits
IAM Without Identity Domains Limits
Integration Limits
Java Management Limits
License Manager Limits
Load Balancer Limits
Logging Analytics Limits
Logging Limits
Management Agent Limits
Management Dashboard Limits
MySQL Heatwave Limits
Media Services Limits
Monitoring Limits
Networking Limits
NoSQL Database Cloud Limits
Notifications Limits
Object Storage and Archive Storage Limits
OCI Database with PostgreSQL Limits
Operations Insights Limits
Organization Limits
Queue Limits
Resource Manager Limits
Scheduled Reports Limits
Search with OpenSearch Limits
Secure Desktops Limits
Security Zones Limits
Service Mesh Limits
Streaming Limits
Threat Intelligence Limits
Traffic Management Limits
Vault Limits
VMware Solution Limits
Vulnerability Scanning Limits
WAF Limits
Using the API
Fractional Usage and Availability
Deleting a Repository in Artifact Registry


Delete an empty repository in Artifact Registry.

 Important

You can only delete empty repositories. Before you delete a repository, you must delete its artifacts. See Deleting an Artifact in Artifact Registry.
Console
CLI
API
Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Artifact Registry.
Under List scope, choose a compartment that contains the repositories.
Click the name of the repository that you want to delete.
Click Delete.
When prompted for confirmation, click Delete.
Backend Sets for Network Load Balancers


Use backend sets to create logical entities consisting of a network load balancing policy, health check policy, and a list of backend servers for a network load balancer.

A backend set is a logical entity defined by a load balancing policy, a health check policy, and a list of backend servers. To create a backend set, you must specify a load balancing policy and health check script, and then add a list of backend servers (compute instances). A backend set must be associated with one or more listeners for the network load balancer to work.

You can perform the following backend set management tasks:

Creating a Backend Set

Listing Backend Sets

Getting a Backend Set's Details

Editing a Backend Set

Enabling Backend Set Source Preservation

Getting a Backend Set's Health Details

Deleting a Backend Set
Creating an Asset Source


Use a phrase or use values as tags to organize and track asset source tags within your tenancy.

Before you create an asset source, ensure that you have defined the required vSphere privileges. See Required vSphere Privileges.
Console
CLI
API
Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Discovery.
On the Asset sources page, click Create asset source.
In the Asset source information section, provide the following details:
Enter a name for the asset source.
The path to the VMware vCenter SDK endpoint of the external environment.
Select a compartment for the asset source.
Select the compartment where the inventory assets are created.
In the Remote connections source environment section, select the source environment.
In the Discovery credentials section, use one of the following options:
To read the metadata of assets from the source environment, click Use existing secret and select a vault and secret containing the login credentials of the vSphere client.
Click Create secret and enter the username and password for the vSphere login credentials.
(Optional) In the Replication credentials section, use one of the following options:
Click Use discovery credentials to continue with the selected discovery credentials.
Click Use existing secret and select a vault and secret for discovery credentials.
Click Create secret and enter the username and password for discovery credentials.
In the Discovery schedule section, click one of the following options to perform the discovery job:
To perform an on-demand or manual asset discovery, click No discovery schedule.
To use an existing discovery schedule, click Select existing schedule.
To create the wanted discovery schedule, click Create schedule.

You can keep asset information up to date by using the discovery scheduling mechanism as a recurring task. After creating a discovery schedule, you can attach or detach it from an existing asset source to begin or stop scheduling discovery jobs for external asset discovery and metadata collection.

In the Metrics section, select one of the following options:
To collect historical metrics of the assets, select Enable collection of historical metrics
To collect real-time metrics of the assets, select Enable collection of real-time metrics
(Optional) Add tags to organize your 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 are not sure whether to apply tags, skip this option (you can apply tags later) or ask your administrator.
Click Create asset source.
You are redirected to the Asset source details page after the asset source is created successfully.

Under Connections, you can view each connector to the source environment. These connectors are automatically instantiated using the discovery plugin in the external environment. The connectors change their state to active after they have verified their connection and credentials with the vCenter server.

You can now create a discovery work request.
Managing Snapshots

Managing Clone and Replication Snapshots
Monitoring Snapshots
Details About Your Snapshot
Required IAM Service Policy
Known Issues for Automated CEMLI Execution


Automated CEMLI Execution has no known issues.
Archive Storage
 resources
Support
Get help and contact Support
Create a service request
Performance Tiers


OCI Database with PostgreSQL uses database optimized storage that scales independently of Compute resources. When configuring a database system, select a performance tier for storage.

The performance tier provides guaranteed performance in terms of IOPS (input/output operations per second), irrespective of the database size. For example, 300 K IOPS provides a storage performance of up to 300,000 IOPS.

Currently, the only supported performance tier is 300,000 IOPS.

IOPS values map to volume performance units (VPUs). For more information, see Volume Performance Units. For specific pricing details, see Cloud Storage Pricing.
Migrate Oracle SOA Cloud Service

Plan the Migration
Prepare the Source Environment
Prepare the Target Environment
Database Tools
 Events
SDK Examples
SDKs and the CLI
Prerequisites
IAM Policies and Vaults
Troubleshooting
Troubleshoot Connections
Community
Database Insider Blog
Cloud Infrastructure Community Forum
Use Cases
Oracle Connections
MySQL Connections
Private Endpoints
SQL Worksheet
Support
Get Help and Contact Support
Create a Service Request
Disaster Recovery Support


Learn about the disaster recovery capabilities of Fusion Applications.

Disaster Recovery (DR) services for Oracle Fusion Applications environment management are intended to provide service restoration capability in the event of a major disaster, as declared by Oracle. Oracle will determine whether an event constitutes a disaster requiring the execution of the DR plan.

What to Expect During and After Switchover

While the environment switchover to the standby region is in progress, you can't make any updates to the environment or perform environment lifecycle management activities. Your Fusion Applications are unavailable until the switchover is complete. A banner message on the environment details page notifies you that a switchover is in progress.

When the environment is live in the standby region, your Fusion Applications are available, but environment lifecycle management capabilities are disabled. A banner message on the environment details page notifies you that the environment is running in the standby region.

DR Phase	Health Status	Lifecycle State
Switchover in progress	Unavailable	Updating
Live from standby region	

Available

	

Active

When Fusion Applications are live from the standby region, environment lifecycle management activities are not allowed.

Disaster Recovery Region Pairings

The following table shows the standby region designated for each primary region in the event of Oracle's declaration of a disaster in the primary region.

Region	Disaster Recovery/Standby Region
Australia East (Sydney)	Australia Southeast (Melbourne)
Australia Southeast (Melbourne)	Australia East (Sydney)
Brazil East (Sao Paulo)	Brazil Southeast (Vinhedo)
Brazil Southeast (Vinhedo)	Brazil East (Sao Paulo)
Canada Southeast (Montreal)	Canada Southeast (Toronto)
Canada Southeast (Toronto)	Canada Southeast (Montreal)
Chile Central (Santiago)	Brazil East (Sao Paulo)
Germany Central (Frankfurt)	Netherlands Northwest (Amsterdam)
Netherlands Northwest (Amsterdam)	Germany Central (Frankfurt)
India South (Hyderabad)	India West (Mumbai)
India West (Mumbai)	India South (Hyderabad)
Japan Central (Osaka)	Japan East (Tokyo)
Japan East (Tokyo)	Japan Central (Osaka)
Saudi Arabia West (Jeddah)	Netherlands Northwest (Amsterdam)
Singapore (Singapore)	Japan East (Tokyo)
Switzerland North (Zurich)	Germany Central (Frankfurt)
UAE Central (Abu Dhabi)	UAE East (Dubai)
UAE East (Dubai)	UAE Central (Abu Dhabi)
UK South (London)	UK West (Newport)
UK West (Newport)	UK South (London)
US East (Ashburn)	US West (Phoenix)
US West (Phoenix)	US East (Ashburn)
Using File Storage Parallel Tools

Installing the Parallel File Tools
Using the Tools - Basic Examples
Using the Tools - Advanced Examples
Compute Metrics and Monitoring


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.

For details about enabling monitoring for compute instances, see Compute Health Monitoring for Bare Metal Instances and Enabling Monitoring for Compute Instances.

There are multiple Monitoring service metric namespaces related to compute resources:

oci_computeagent: Metrics related to the activity level and throughput of compute instances, as emitted by the Compute Instance Monitoring plugin. See Compute Instance Metrics. To enable monitoring for compute instance metrics, see Enabling Monitoring for Compute Instances.
oci_instancepools: Metrics related to the lifecycle state of instances in instance pools. See Instance Pool Metrics.
oci_compute_instance_health: Metrics related to the accessibility and health of instances. See Compute Instance Health Metrics.
oci_compute_infrastructure_health: Metrics related to the up/down status, health, and maintenance status of instances. This namespace focuses specifically on the underlying infrastructure for instances. See Infrastructure Health Metrics.
oci_compute: Metrics related to the instance metadata service (IMDS) that provides information about running compute instances. See Compute Management Metrics.
Overview of Resource Manager

Key Concepts
Features
Templates
Start with a Resource Creation Page
CI/CD with Resource Manager
Resource Discovery
State Management
Drift Detection
Deploy to Oracle Cloud Button
Private Endpoints
Custom Providers
Dependency Lock Files
Roll Back Jobs
Availability
Generalized Workflow
Ways to Access Resource Manager
Default Provider
Authentication and Authorization
Security
Limits on Resource Manager Resources
Custom Metrics Walkthrough


Walk through common use cases with custom metrics: publishing, querying, creating an alarm, and triggering the alarm to observe its Firing status.

Task 1: Publish Custom Metrics

See Publishing Custom Metrics.

Task 2: Query the Published Custom Metrics

See Creating a Query for a Custom Metric.

Task 3: Create an Alarm

Create an alarm to get an email when the number of product orders (productOrder) in a 5-minute time period is higher than 100.

The following instructions show how to use Basic mode in the Console. For basic alarm instructions, see Editing the MQL Expression When Creating an Alarm (for Advanced mode, including MQL) and Creating an Alarm (for CLI and API).

Open the Create alarm page:
Open the navigation menu and click Observability & Management. Under Monitoring, click Alarm Definitions.
Click Create alarm.
Provide values for the following fields:
Alarm name (under Define alarm): Too Many Product Orders
Alarm severity: Info
Alarm body: High number of product orders received (over 100 in a five-minute period).
Compartment (under Metric description): The compartment containing the resources that you want to monitor. By default, the first accessible compartment is selected.
Metric namespace: mymetricsnamespace
Resource group: divisionX
Metric name: productOrder
Interval: 5m
Statistic: Sum
Trigger rule:
Operator: greater than
Value: 100
Trigger delay minutes: 1
Destination (under Define alarm notifications): Select Notifications.

Create a topic: Provide values for the following fields:

Topic name: extreme-product-order-volume
Topic description: Channel to notify of high number of product orders received (over 100 in a five-minute period).
Subscription protocol: Email
Subscription email: (enter your email address)

The metric chart under the Define alarm section dynamically displays the last six hours of emitted metrics for productOrder under the resource group DivisionX.

Click Save alarm.

Notifications sends a confirmation request to the email address configured in the new subscription.

Confirm the new email subscription. See Confirming a Subscription.
Trigger the Alarm

Trigger the alarm to observe its Firing status.

Publish a set of data points to trigger the alarm. Send a request that shows over 100 orders within 5 minutes.

For instructions, see Publishing Custom Metrics.

Get the alarm's details.

For instructions, see Getting an Alarm's Details.

The alarm is in Firing state.

Check your email.

For reference, see Email (Formatted) on the overview page.

The email indicates that the alarm is in Firing state.
Creating Migration Assets in a Migration Project


Add assets to a migration project using the Oracle Cloud Migrations inventory. You can add only those assets that are not associated with any other migration projects.

Console
CLI
API
Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Migrations.
On the Migrations page, click the active migration project for which you want to add migration assets.
On the Migration project details page, from Resources, click Migration assets, and then click Add migration assets.
On the Add assets from OCM inventory page, click Add from OCM inventory.
In the Add migration assets window, select the assets that you want to add, and click Add migration assets. You are redirected to the Add assets from OCM inventory page.
Click Next.
For the Replication location step, in the Default replication location box, select the volume availability domain, replication compartment, and replication bucket, and then click Select. To modify an existing replication location, select the asset and click Edit replication location. To reset, click Reset to default.
 Note

You can't modify the replication compartment or bucket after creating a migration asset.
Click Submit.
You can now modify the migration plan, if required.
DHCP Options

Using the Console
Using the API
File System Usage and Metering

Overview
Space Allocation
Metering and Service Cost
Using DF and DU Commands
Enterprise Scenarios for Design and Implementation

Enterprise Scenarios Guidance
Adding Oracle Cloud Users with Specific Job Functions

Understanding the Difference Between Environment Management User Roles and Application User Roles
Add a Tenancy Administrator
Using Compartments to Group Resources for Job Roles
Add a User with Specified Access for a Job Role
Policy Reference for Job Roles
Best Practices for Using Database Tools

Isolating Database Connections with Compartments
Using Private Endpoints
Known Issues
Viewing Reports
 for a Lifecycle Environment
Using console to manage tables

Modifying Table Data Using Console
Managing Table Data Using Console
Managing Tables and Indexes Using Console
Create Your First Resources


After you create your Free Trial account, use these tutorials to get started.

Autonomous Database Quickstart

Create an instance in just a few clicks. Then load data into your database from Object Storage and query it.

	

Analyze data with Autonomous Database

Use Oracle Analytics Desktop (OAD) to visualize data in Autonomous Database. Use Oracle Machine Learning (OML) to try your hand at predictive analytics.




Launch a Linux or Windows VM.

Create your first virtual cloud network and launch an instance. Optionally, attach block storage to your instance

	

Launch a VM with the CLI

Use the command line interface to launch a Linux instance or a Windows instance. This tutorial includes working with a compartment, creating a virtual cloud network.




Get started with Object Storage

Create your first bucket and upload some objects.

	

Launch and test a load balancer

Create a VCN and load balancer, then test it out.
Introduction

The Default Identity Domain
Using Multiple Identity Domains
Limits on Identity Domains
Recovering Domains
Disaster Recovery and Identity Domains



For more information click here https://docs.oracle.com/en-us/iaas/management-agents/doc/you-begin.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/managed-cloud-self-service/mgdcloudss_introduction.htm
Traffic Management
 Tasks
Migrate Oracle Integration Cloud, Oracle Integration Cloud Service, or Oracle Process Cloud Service

Prerequisites
Plan the Migration
Creating a Source
Creating a Migration
Oracle Linux
 documentation
Unbreakable Enterprise Kernel documentation
Community
Oracle Cloud Infrastructure blog
Cloud infrastructure community forum
Limiting the Number of Requests to API Gateway Back Ends

Using the Console to Add Rate-Limiting Request Policies
Editing a JSON File to Add Rate-Limiting Request Policies