Jay-Rajput/oci_data huggingface dataset:
Using the Search Field


You use the Search within this data catalog in the Home tab or the Search within <data object> boxes in the various data catalog objects tabs to enter a search text and retrieve all data objects matching the search text in the data catalog.

Console
CLI
API
Access the Search within <data object> field from the Home tab or the Data Assets, Data Entities, Attributes, Filename Patterns, Custom Attributes, Glossary, Terms, Jobs, or Schedules tabs.
Enter the search text. This text can be a complete or partial text. In the search bar of the Home tab, when you type the first three characters, the system suggests the possible texts. If a suggestion matches your requirement, you can select the text.
 Note



The search is not case-sensitive.

You can use * anywhere in your search text as a wildcard. For example, you can use resource* to search for resource_type, resource_name, resource_uri and so on.

Use *res* to search for resource_type, resource_name, resource_uri and schedule_cron_expression.

More search examples: *cust*, customer_*, cust*_*, and *cust*_t*.

Click the search icon in the Search within <data object> box, or press enter. The results matching the search text are listed.
Use Filters and Custom Filters to refine your search results.
Use the sort drop down to display the results in order of Relevance, Name - Ascending, Name - Descending, Last Updated - Ascending, or Last Updated - Descending.
Use the Delete button to delete one or more selected data entities from the search results.
 Note

When you delete more than 10 data entities at a time, a delete job is created. You can view the job details by clicking the job link in the notification message that appears when the delete job is initiated or by clicking Jobs on the Home tab.
Installing and Configuring Compute Cloud@Customer


Before you can use Compute Cloud@Customer, you must prepare your site for the installation of the rack, prepare your tenancy, and initialize the connection of the Compute Cloud@Customer infrastructure to Oracle Cloud Infrastructure.

The following table describes the steps you perform to install Compute Cloud@Customer. Oracle performs some steps. Steps 3 and 4 can be performed at the same time, or in reverse order, depending on when the hardware arrives at your site.

No.

	

Task

	

Links


1.	

Prepare your data center for the Compute Cloud@Customer rack installation.

	Preparing Your Site and Site Checklists for Compute Cloud@Customer
2.	Oracle validates site requirements in your data center.	
3.	Prepare your OCI tenancy by setting up these items:
Federated identity provider
Users and groups
Compartments
Policies
Virtual cloud network (VCN) with a subnet
	Preparing Your Tenancy
4.	The Compute Cloud@Customer rack is delivered to your site.

Oracle installs the rack in your data center and works with you to connect it to your network.

Oracle initializes Compute Cloud@Customer and configures it with site-specific details such as network parameters.

	
5.	

Work out an upgrade schedule for the infrastructure and define this in an upgrade schedule resource.

	Creating a Compute Cloud@Customer Upgrade Schedule
6.	

Create an infrastructure in the compartment for the physical infrastructure in the data center.

	Creating a Compute Cloud@Customer Infrastructure in OCI
7.	

Connect to the infrastructure using a bootstrap process that involves the exchange of provisioning information to ensure a secure connection.

	Connecting a Compute Cloud@Customer Infrastructure to OCI

You can now use Compute Cloud@Customer to provide compute, storage and other resources. See Signing in to the Compute Cloud@Customer Console
Getting Started with OS Management

General Workflow for Setting Up Managed Instances
Supported Images
Prerequisites
Setting Up IAM Policies for OS Management
Required Dynamic Group
Required User Group
Example: Dynamic Group
Required IAM Policies
Detailed Steps
Enabling OS Management for a New Compute Instance
Enabling the OS Management Service Agent Plugin for an Existing Compute Instance
Disabling the OS Management Service Agent Plugin
Verifying the Status of the OS Management Service Agent Plugin
What to Do Next
Scaling Kubernetes Clusters and Node Pools


Find out about scaling up and scaling down the Kubernetes node pools and clusters you've created using by Container Engine for Kubernetes (OKE).

You can scale the clusters you create using Container Engine for Kubernetes to optimize resource usage.

Scaling Clusters with Managed Node Pools

In the case of managed node pools, you have responsibility for adjusting cluster capacity in response to changing requirements. You can:

Change the number of managed node pools in a cluster to scale the cluster up and down (see Adding and Removing Node Pools to Scale Clusters Up and Down).
Change the number of managed nodes in a managed node pool to scale the node pool up and down (see Scaling Node Pools).
Enable autoscaling to automatically scale managed node pools and pods (see Autoscaling Kubernetes Node Pools and Pods).
Scaling Clusters with Virtual Node Pools

In the case of virtual node pools, much of the operational overhead of cluster capacity management is handled for you.

A virtual node pool scales automatically, and can support up to 1,000 pods per virtual node.

In the event that 1,000 pods per virtual node is insufficient, you can:

Increase the number of virtual node pools in a cluster to scale up the cluster (see Adding and Removing Node Pools to Scale Clusters Up and Down).
Increase the number of virtual nodes in the virtual node pool to scale up the node pool (see Scaling Node Pools). For the maximum number of virtual nodes, see Container Engine for Kubernetes Limits.

Note that because virtual nodes automatically scale to support so many pods, it's not necessary to use the Kubernetes Cluster Autoscaler (which is not yet supported with virtual nodes in any case).
Set Up Users
 and Groups for Oracle Analytics Cloud
Migrating to OCI Big Data Service

Benefits of Migrating to Big Data Service
Starting a Job Run


Use Data Science job runs to apply various use cases to created jobs.

Job creation sets the infrastructure and the actual use case artifact, but the job run actually runs the job with the specified parameters. Job runs provision the specified infrastructure, run the job artifact, and then deprovision and destroy the used resources when the job run ends.

Console
CLI
API
Use the Console to sign in to a tenancy with the necessary policies.
Open the navigation menu and click Analytics & AI. Under Machine Learning, click Data Science.
Select the compartment that contains the project with the jobs.

All projects in the compartment are listed.

Click the name of the project.

The project details page opens and lists the notebook sessions.

Under Resources, click Jobs.

A tabular list of jobs in the project is displayed.

Click the name of the job to work with.
Click Start a job run.
(Optional) Select a different compartment for the job.
(Optional) Enter a unique name for the job run (limit of 255 characters). If you don't provide a name, a name is automatically generated.

For example, jobrun20210808222435.

(Optional) To use logging, click Select, and then ensure that Enable logging is selected.
Select a log group from the list. You can change to a different compartment to specify a log group in a different compartment from the job.
Select one of the following to store all stdout and stderr messages:
Enable automatic log creation

Data Science automatically creates a log when the job starts.

Select a log

Select a log to use.

Click Select to return to the job run creation page.
(Optional) Override the default job configuration that was defined when the job was created by using these options:
Custom environment variable key

The environment variables that control the job.

Value

The value for the custom environment variable key.

You can click Additional custom environment key to specify more variables.

Command line arguments

The command line arguments that you want to use for running the job.

Maximum runtime (in minutes)

The maximum number of minutes that the job can run. The service cancels the job run if its runtime exceeds the specified value. The maximum runtime is 30 days (43,200 minutes). We recommend that you configure a maximum runtime on all job runs to prevent runaway job runs.

(Optional) Click Show advanced options to add tags to the job run.
(Optional) Enter the tag namespace (for a defined tag), key, and value to assign tags to the resource.

To add more than one tag, click Add tag.

Tagging describes the various tags that you can use organize and find resources including cost-tracking tags.

Click Start.
Console Announcements

Types of Announcements
Required IAM Policy
Using the Command Line Interface (CLI)
Editing a Pipeline


Update deployment pipeline information.

For accessing DevOps using the Oracle Cloud Console, REST API, and CLI, see Accessing DevOps.

Console
CLI
API
Open the navigation menu and click Developer Services. Under DevOps, click Projects.
On the DevOps Projects page, click the project for which you want to update the pipeline.
On the project details page, from the Latest deployment pipelines section, click the View all deployment pipelines link.
On the Deployment pipelines page, click the Actions menu () to the right of the pipeline that you want to update and select Edit pipeline.
In the Edit pipeline panel, update the details as required. You can update the name and description of the pipeline.
Click Save.
Configuring Oracle and Third-Party Applications


Configure the Oracle Cloud and third-party applications to send email through the Email Delivery service.

Integrating Oracle Application Express with Email Delivery
Integrating Postfix with Email Delivery
Integrating Oracle Enterprise Manager with Email Delivery
Integrating Mailx with Email Delivery
Integrating MailKit with Email Delivery
Integrating Swaks with Email Delivery
Integrating JavaMail with Email Delivery
Integrating Sendmail with Email Delivery
Integrating PeopleSoft with Email Delivery
Integrating Python with Email Delivery
Managing Your Domains

Required IAM Policy
Adding and Verifying Domains
Domain Revocation
Using the API
Function Runtimes


Find out about the Function Development Kits (FDKs), language versions, and base images supported by OCI Functions.

Read about managing Function Development Kits (FDKs) and supported language versions:

Function Development Kits (FDKs)
Languages Supported by OCI Functions
FDK Base Images and Linux Distributions
Adding a Block Volume

Creating a Volume
Attaching the Volume to an Instance
Connecting to the Volume
What's Next
Object Storage Buckets

Required IAM Policy
Security Zones
Pre-Authenticated Requests
Object Versioning
Object Lifecycle Policies
Retention Rules
Replication Policy
Tagging Resources
Monitoring Resources
Usage Reports
Creating Automation for Buckets and Objects Using the Events Service
Bucket Names
Default Storage Tiers
Public Buckets
Limitations Common to all Models


Learn about the Language limitations common to all pretrained and custom models.

Ensure that input text records follows correct grammar and punctuation to avoid model performance degradation.

Spelling isn't checked or corrected so the results might not be as you expect when spelling mistakes exist.

Single Requests

A record can be up to 1,000 characters. We encourage you to use batch requests that support records up to 5,000 characters and support more than one record in a single request.

There's no minimum number of characters that must be provided, but the output quality is highly dependent on the amount of information provided to the models.

Batch Requests

A batch can have up to 100 records.

A record can be up to 5,000 characters long.

The total number of characters to process in a request can be up to 20,000 characters.
Choosing a Compartment

What's Next
Policy Details for Database Management

Resource-Types
Supported Variables
Details for Verb + Resource-Type Combinations
Permissions Required for Each API Operation
Using Object Lifecycle Management

Required IAM Policies
Options
Using Object Name Filters
Scope and Constraints
Working with Object Lifecycle Management Policies
Logging Metrics

Overview of the Logging Service Metrics
Prerequisites
Available Metrics: oci_logging
Using the Console
Using the API
Custom Model Datasets

Uploading the Datasets
Adding an HTTP or HTTPS URL as an API Gateway Back End

Using the Console to Add HTTP or HTTPS Back Ends to an API Deployment Specification
Editing a JSON File to Add HTTP or HTTPS Back Ends to an API Deployment Specification
Using Notebook Sessions to Build and Train Models

Authenticating to the OCI APIs from a Notebook Session
Working with Existing Code Files
Installing Additional Python Libraries
Using the Provided Environment Variables in Notebook Sessions
Using Custom Environment Variables
Using the Oracle Accelerated Data Science SDK
Data Handling in Generative AI

 Important



Pre-General Availability: 2023-09-18

The following legal notice applies to Oracle pre-GA (Beta) releases. For copyright and other applicable notices, see Oracle Legal Notices.

Pre-General Availability Draft Documentation Notice

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

This documentation is not a commitment by Oracle to deliver any material, code, functionality or services. This documentation, and Oracle Pre-GA programs and services are subject to change at any time without notice and, accordingly, should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality for Oracle’s Pre-GA programs and services remains at the sole discretion of Oracle. All release dates or other predictions of future events are subject to change. The future availability of any future Oracle program or service should not be relied on in entering into any license or service agreement with Oracle.

How is data handled in OCI Generative AI (Beta)?

Customer data privacy is respected. No other customer can look at your data or models.

Are the files that I send to Generative AI API, the results, or other information about the request itself stored on Oracle servers?
Customer data privacy is respected. When you send data to the Generative AI API, it’s processed in memory and no customer data is stored. Oracle temporarily logs some metadata about your API requests to improve the service, for billing and metering, and to combat abuse. The metadata is, for example, the time and size of the request.
Which file storage locations are supported?
Local file storage for text embeddings and Oracle Object Storage for fine-tuning custom models are supported. Find out more about Oracle Object Storage from the Object Storage web page.
Data Transfer Supported Regions

Appliance- and Disk-Based
Disk-Based Only
Oracle Linux Utilities


A set of utilities is available for Oracle Linux images. These utilities can help with tasks such as working with Oracle Cloud Infrastructure resources, mounting object storage buckets, migrating systems to Oracle Cloud Infrastructure, or setting up KVM instances.

OCI Utilities
OCIFS Utility
OCI Image Migrate Utilities
OCI-KVM Utilities
Inter-Region Latency

Using the Console
Editing the Management Policy of a Database System


Change the management policy of an OCI Database with PostgreSQL database system. The database system management policy specifies its backup and maintenance policies.

For more information, see Managing Backups of an OCI Database with PostgreSQL and Maintenance.
Console
CLI
API
Open the navigation menu and click Databases. Under PostgreSQL, click Databases.
(Optional) In the List scope section, under Compartment, select a compartment.
Click the name of the database system that you want to edit.
On the DBSystem details page, click More actions and choose Edit management policy.
In the Edit management policy panel, make selections for the following:
Automatic backups: Select Enable automatic backups to enable automatic backups. If you don't select automatic backups, you must manage backups manually. We recommend that you enable automatic backups. After enabling this option, you can set the backup frequency.
Maintenance: Select a Maintenance type option. For more information, see Maintenance.

Set by Oracle: Oracle chooses the best day and time to start any essential maintenance.

Schedule your own maintenance: Specify the day of the week and the maintenance start time (in UTC timezone) that you want to schedule any essential maintenance activity, such as OS or instance upgrades. If you don't specify a day and time, Oracle chooses it for you.
Click Save changes to update the database system management policy.
Big Data Service Versions


Different versions of Big Data Service are available, including ODH 0.9, 1.0, 1.0.3, and 2.0.

ODH 0.9 (BDS 3.0.7+)
ODH 1.0 (BDS 3.0.3+)
ODH 1.1.0.351 (BDS 3.0.7+)
ODH 2.0 (BDS 3.0.20+)
 Expand All Expandable Areas
Customizing Trust Stores for TLS Certificate Verification

Adding Custom CAs and CA Bundles to an API Gateway's Trust Store
Removing Custom CAs and CA Bundles from an API Gateway's Trust Store
Outbound Replication
 Scenarios
Distributed Tracing for Functions

Using the Console to Enable Tracing and View Function Traces
Tracing a Chain of Functions
Adding Custom Spans to Functions
Using the API
Creating an Environment


Create a source environment within Oracle Cloud Migrations as the first step for discovery and migration.

Console
CLI
API
Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Remote Connections. On the Source environments page, click Create source environment.
In the Create source environment panel, provide the following details:
Enter a name.
Select the compartment where you want to create the environment.
(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 source environment.
You are redirected to the environment details page.

You can now download an appropriate remote agent appliance Open Virtualization Application (OVA) file and install the agent. See Installing a Remote Agent Appliance for VMware vCenter.
Read Replica
 Metrics
Limitations
Listing Status of Alarms

Before You Begin
What to Do Next
OS Management Metrics

Overview of Metrics for an Instance and Related Resources
Prerequisites
Available Metrics: oci_osms
Using the Console
Using the API
Editing a Job Schedule


Edit a job schedule to change its schedule information such as frequency, start time, or end time.

Console
CLI
API
On the Home tab of the instance for which you want to edit a schedule, click Schedules.
On the Schedules page, click the Actions menu to the right of the schedule that you want to modify and select Edit.
In the Edit Schedule panel, modify the details as required. You can update the frequency, start time, or end time of the schedule.
Click Save changes.
Known Issues for Compliance Documents


Compliance Documents has no known issues.
Getting a File System's Details


Get details about a File Storage file system.

For more information, see Details About Your File System.

Console
CLI
API
Open the navigation menu and click Storage. Under File Storage, click File Systems.
In the List scope section, under Compartment, select a compartment.
Click the name of the file system to view detailed information about it.
Example Alarm Messages

Notifications Destination
Email (Formatted)
Email (Pretty JSON)
Email (Raw)
Slack
SMS
Streaming Destination
Access to Your On-Premises Network


The following topics have information about ways to privately connect your cloud network to your existing on-premises network. Regardless of which method you use, you need a dynamic routing gateway (DRG) attached to your cloud network.

Dynamic Routing Gateways (DRGs)
Routing Details for Connections to Your On-Premises Network

Site-to-Site VPN:

Site-to-Site VPN Overview
Site-to-Site VPN Quickstart
Routing Details for Connections to Your On-Premises Network
Supported IPSec Parameters
Supported Encryption Domain or Proxy ID
Setting Up Site-to-Site VPN
Working with Site-to-Site VPN
CPE Configuration
Verified CPE Devices
Using the CPE Configuration Helper
Working with Site-to-Site VPN
Site-to-Site VPN FAQ
Using the API for Site-to-Site VPN
Site-to-Site VPN Metrics
Site-to-Site VPN Troubleshooting

FastConnect:

FastConnect Overview
FastConnect Requirements
FastConnect Redundancy Best Practices
Routing Details for Connections to Your On-Premises Network
FastConnect: With an Oracle Partner
FastConnect: With a Third-Party Provider
FastConnect: Colocation with Oracle
FastConnect Metrics
FastConnect Troubleshooting
Available Quotas by Service


All available quotas by service.

Analytics Cloud
Autonomous Recovery Quotas
Big Data
Block Volume Quotas
Blockchain Platform Quotas
Cloud Guard Quotas
Compute Quotas
Compute Cloud@Customer Quotas
Container Instances Quotas
Content Management Quotas
Data Catalog Quotas
Data Integration Quotas
Data Labeling Quotas
Data Science Quotas
Data Transfer Quotas
Database Quotas
Database Migration Quotas
Database Tools Quotas
DevOps Quotas
Digital Assistant Quotas
DNS Quotas
Events Quotas
Email Delivery Quotas
File Storage Quotas
GoldenGate Quotas
Health Checks Quotas
Integration Quotas
Java Management Quotas
Load Balancing Quotas
Management Agent Quotas
Media Services Quotas
Networking Quotas
NoSQL Database Cloud Quotas
Notifications Quotas
Object Storage Quotas
Process Automation Quotas
Resource Manager Quotas
Secure Desktops Quotas
Connector Hub Quotas
Streaming Quotas
Vault Quotas
Vulnerability Scanning Quotas
WAF Quotas
Configuration API Specifications


Learn about the supported configuration APIs.

The following Configuration API specifications are supported:

Configuration Execution API Specifications
Configuration Metadata API Specifications
Preparing for API Gateway

Availability by Region
Working with Notebooks

Creating a Notebook
Overview of the Notebooks User Interface
Importing a Notebook
Searching for a Notebook
Cloning a Notebook
Supported Interpreters
Creating Paragraphs
Overview of Paragraphs User Interface
Accesing HDFS from Spark and PySpark
Accessing Hive from Spark and PySpark
Creating Versions of a Notebook
Exporting a Notebook
Deleting a Notebook
Keyboard Shortcuts for Notebooks
Using the Code Editor

Setting Up the Data Flow Spark Plug-In
Oracle Cloud Agent
 Software