Jay-Rajput/oci_data huggingface dataset:
Pretrained Foundational Models 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.

You can use the following pretrained models in Generative AI:

Capability	Models and Key Features	Playground Parameters
Text Generation

Give instructions to generate text or extract information from your text.

	
cohere.command
Version 14.2
Model has 52 B parameters.
User prompt and response can be up to 4096 tokens for each run.
cohere.command-light
Version 14.2
Model has 6 B parameters.
User prompt and response can be up to 4096 tokens for each run.
	

Generation Model Parameters:

Maximum tokens
Temperature
Top k
Top p
Stop sequences
Frequency penalty
Presence penalty
Show likelihoods

Text Summarization

Summarize text with your instructed format, length, and tone.

	
cohere.command
Version 14.2
Model has 52 B parameters.
User prompt and response can be up to 4096 tokens for each run.
	

Summarization Model Parameters:

Length
Format
Extractiveness
Temperature
Additional commands

Text Embeddings

Convert text to vector embeddings to use in applications for semantic searches, text classification, or text clustering.

	
embed-english-light-v2.0
Version 2.0
Language: English
Model has 355 M parameters.
Model creates a 1024-dimensional vector for each embedding.
Max 512 tokens per embedding.
Max 96 sentences per run.
	

Embedding Model Parameter:

Truncate
Function Development Kits (FDKs)

Examples
Behavior in Earlier Versions of the Fn Project CLI (prior to version 0.6.7)
How to find out the language versions supported by FDKs
How to find out the version of the FDK build-time and runtime base images used for an existing function
How to find out the default FDK build-time and runtime base image versions for a given language
How to find out the latest FDK build-time and runtime base image versions for a particular supported language version
How to upgrade an existing function to use the latest FDK build-time and runtime base image version for a supported language
Using Cloud SQL with Big Data

About Cloud SQL Query Server
Important Terms and Concepts
Specifying Hive Databases to Synchronize with Query Server
Configuring the CDN


Configure the CDN for a distribution channel in Media Streams.

Media Streams supports OCI Edge or a CDN such as Akamai. To use Akamai, you must use your own account.

Console
CLI
API
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 which you want to configure the CDN.
Click the name of the channel for which you want to configure the CDN.
On the Distribution Channel details page, in the CDN Configuration field of the Details tab, click the current CDN configuration.
The CDN configuration details page appears. You can view the details here.
To modify the CDN details, navigate back to the Distribution Channel details page, and in the CDN Configuration field of the Details tab, click Configure.
In the Configure CDN Configuration panel, provide the following details (OCI Edge or Akamai):
Enter a name for the CDN.
Select the configuration type for the CDN. If you select Akamai, provide the following details:
Edge hostname: The host name of the CDN edge server used for building CDN URLs.
Edge path prefix: The path to prepend when building CDN URLs.
Edge auth token: Select if the token authentication must be used at the CDN edge.
Edge token key: The encryption key to use for edge token authentication.
Edge token salt: The salt to use when encrypting authentication token.
Authentication secret key A: The shared secret key A for precise key rotation.
Authentication secret key A nonce: The Nonce identifier for originAuthSecretKeyA (used to determine the key for signing).
Authentication secret key B: The shared secret key B for precise key rotation.
Authentication secret key B nonce: The Nonce identifier for originAuthSecretKeyB (used to determine key for signing).
Click Submit.
The configuration is updated.
Get started


Learn how to get started with Oracle Cloud Infrastructure GoldenGate, including how and where to access the service, guided workshops and tutorials to lead you through common use cases, and a basic taskflow of operations to complete when using OCI GoldenGate for the first time.

Articles in this section

Access OCI GoldenGate
OCI GoldenGate workshops
Basic taskflows
Create Oracle Cloud resources
Integrating Oracle Application Express with Email Delivery

More Information
Container Instances

SDKs and the CLI
Cloud Shell
Support
Get help and contact Support
Create a service request
Connecting to Sessions in Bastion

Required IAM Policy
Allowing Network Access From the Bastion
Supported Shapes

Shape	OCPUs	RAM (GB)	Maximum Network Bandwidth
PostgreSQL.VM.Standard.E4.Flex.2.32GB	2	32	2 Gbps
PostgreSQL.VM.Standard.E4.Flex.4.64GB	4	64	4 Gbps
PostgreSQL.VM.Standard.E4.Flex.8.128GB	8	128	8 Gbps
PostgreSQL.VM.Standard.E4.Flex.16.256GB	16	256	16 Gbps
PostgreSQL.VM.Standard.E4.Flex.32.512GB	32	512	32 Gbps
PostgreSQL.VM.Standard.E4.Flex.64.1024GB	64	1024	40 Gbps
Applications Services


This section describes how you can interact with your application subscriptions using the Oracle Cloud Console. These features are currently available only to select applications.

Activating Your Oracle Cloud Applications Order

Using the Oracle Cloud Console

Adding Oracle Cloud Console Users

Exploring Your Application Service Details

Fusion Applications Environment Management

Applications Environment Management

For documentation on using your application, see your application-specific documentation at Oracle Cloud Fusion Applications Suite.
Managing Private Endpoints

Required IAM Policy
Scenarios
Request Routing for Load Balancers


Learn how to route incoming requests to various backend sets. You can assign virtual hostnames to a listener  or create route rules.

View the following sections for more information on request routing for a load balancer:

Virtual Hostnames

Routing Policies

Path Route Sets

Rule Sets

Virtual Hostname and Path Route Rules Combinations
Introduction


Learn about Oracle Managed Cloud Self-Service Platform.

The following topics are covered in this section:

About Oracle Managed Cloud Self-Service Platform
Requirements
Signing into the Oracle Managed Cloud Self-Service Platform



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
Overview of Compliance Documents

Types of Compliance Documents
Types of Services
Regions and Availability Domains
Ways to Access Oracle Cloud Infrastructure
Developer Guide

What's In This Guide



For more information click here https://docs.oracle.com/en-us/iaas/logging-analytics/doc/developer-guide.html
Managing External Asset Discovery

Required IAM Policies
Troubleshoot Database Management
 for External Database Systems
CPE Configuration

Requirements and Prerequisites
Site-to-Site VPN Best Practices
Confirming the Status of the Connection
Device Configurations
Common Database Management Tasks


These are the tasks that can be performed to manage your database using Oracle Database Service for Azure.

Managing your database is done from the OracleDB for Azure portal, by selecting the icon that represents the database type that you want to manage, either an Oracle Autonomous Database, an Oracle Exadata Database, an Oracle Base Database, or Oracle MySQL HeatWave Cluster.

Figure 1-115 Selecting a Database Type for Management Tasks







While there are different management tasks for each database type and those tasks are performed differently, there is a commonality on how those management functions are accessed from the OracleDB for Azure Portal. After selecting the database type from the OracleDB for Azure Portal, you will see a blade similar to these.

Figure 1-116 Oracle Autonomous Database Blade








Figure 1-117 Oracle Exadata Database Blade








Figure 1-118 Oracle Base Database Blade








Figure 1-119 Oracle MySQL HeatWave Cluster Blade







 Note

If a function is available for that database type, the icon representing that tasks will be active and highlighted. For example, the Delete task is not active until you select a database to delete.
The management functions directly on the blades are limited. To get to the additional management functions, unique to the database, select the link to the database you wish to managed. As an example, here are the database details and management functions available to an example Oracle Autonomous Database.

Figure 1-120 Example Oracle Autonomous Database Management Blade







Starting a Database
Stopping a Database
Deleting a Database
Restarting a Database
Download a Wallet
Rotate a Wallet
Changing Database Password
Using Database Actions
Database Metrics
Scale a Database
Restore a Database
Editing a Database
Cloning a Database
Setting Account UI Settings
Tagging Data Assets


Tag a data asset with keywords.

Console
CLI
API
On the Home tab of the instance for which you want to add tags, click Data Assets.
On the Data Assets page, click the data asset that you want to tag.
On the data asset details page, under the Tags section, click Tags.
Enter the keywords with which you want to tag the data asset. You can also select from the list of existing tags.
 Note

To remove a tag, click the remove icon next to the tag.
Concepts for Generative AI

Generative AI
Playground
Dedicated AI Clusters
Custom Model
Custom Model Endpoint
Tokens
Embedding
Likelihood
Temperature
Top k
Top p
Frequency Penalty
Presence Penalty
Prompts and Prompt Engineering
Metrics for Custom Models
Running Applications on Arm-based Nodes

Defining a pod to run only on Arm-based nodes
Viewing Recommendation History


This section of Implementing Recommendations describes the history table and how to view the recommendation status changes that it contains.

Click Console, CLI, or API to display the instructions to list active recommendations and their status.

Console
CLI
API
Open the navigation menu and click Governance & Administration. Under Cloud Advisor, click History.
The Cloud Advisor History dashboard opens. This page tracks recommendation status changes. For example, it lists information about recommendations that have been implemented, postponed, and dismissed.
(Optional) Use one or more of these filters to return a subset of results.
Filter by resource type
Filter by Cloud Advisor status
Filter by recommendation
Managing Work Requests

Required IAM Policy
Tasks
Work Request States



For more information click here https://docs.oracle.com/en-us/iaas/Content/connector-hub/workrequests.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/CloudAdvisor/Tasks/work-requests.htm#work-requests
Data Labeling

Support
Get help and contact Support
Create a service request
Network Command Center Services


Learn about the abilities of the Network Command Center services.

The following diagnostic and troubleshooting services are considered part of the Network Command Center:

Inter-Region Latency
Network Path Analyzer
Network Visualizer
Virtual Test Access Points
Network Load Balancer

SDKs and the CLI
Cloud Shell
Support
Get help and contact Support
Create a service request
Moving a Metastore


Move a metastore from one compartment to another.

 Note

Before moving the metastore, review its usage in other services. The new compartment name must be available to the service accessing this metastore.
Console
CLI
API
On the Data Catalog service page, click Metastores.
On the Metastores page, click the name of the metastore that you want to move.
On the metastore details page, click Move resource.
In the Move resource dialog box, select the new compartment and click Move resource.
Troubleshooting Console Connections


When the Console displays error messages that begin with "Error retrieving" followed by a resource name, it means that the Console cannot connect to the Object Storage APIs to retrieve and display the requested resources. There are multiple reasons why this can happen. Walk through these steps to determine why the Console cannot connect to the APIs.

Step 1: Try to connect to the Object Storage API endpoint in the region containing the buckets you are trying to access using the Console.
Open a browser.
Go to the API endpoint: https://objectstorage.<region_identifier>.oraclecloud.com.

See https://docs.oracle.com/iaas/api/#/en/objectstorage/latest/ for the list of API endpoints. If you are able to connect to the API endpoint, a JSON object is returned. For example:

{"code":"NotFound","message":"Not Found"}
If you can connect to the API endpoint, create a support ticket. If you cannot connect to the API endpoint, continue to Step 2.
Step 2: Make sure your VPN is not blocking Console access to the Object Storage APIs.
Disconnect from any connected VPNs.
Open a browser.
Go to the API endpoint that contains the buckets you are trying to access in the Console: https://objectstorage.<region_identifier>.oraclecloud.com.

See https://docs.oracle.com/iaas/api/#/en/objectstorage/latest/ for the list of API endpoints. If you are able to connect to the API endpoint, a JSON object is returned. For example:

{"code":"NotFound","message":"Not Found"}
If you can connect to the API endpoint, contact your security team about your VPN blocking URL access to the Object Storage APIs. If you cannot connect to the API endpoint, continue to Step 3.
Step 3: Make sure your Web proxy servers are not blocking Console access to the Object Storage APIs.
Disable any configured proxies.
Open a browser.
Go to the API endpoint that contains the buckets you are trying to access in the Console: https://objectstorage.<region_identifier>.oraclecloud.com.

See https://docs.oracle.com/iaas/api/#/en/objectstorage/latest/ for the list of API endpoints. If you are able to connect to the API endpoint, a JSON object is returned. For example:

{"code":"NotFound","message":"Not Found"}
If you can connect to the API endpoint, contact your security team about your proxies blocking URL access to the Object Storage APIs. If you cannot connect to the API endpoint, continue to Step 4.
Step 4: Make sure DNS filtering is not blocking Console access to the Object Storage APIs.
Open a terminal window.
Run the following command to test DNS resolution to the API region:
host objectstorage.<region_identifier>.oraclecloud.com
If the hostname resolves successfully, create a support ticket. If the hostname does not resolve successfully, contact your security team about your DNS-based security filtering blocking access to the Object Storage APIs.
Considerations and Support Information

OCI Vault Secrets and Oracle Wallets
Supported Data Sources for Data Assets
Hierarchical Data Types
Unicode Support
Understanding Data Type Mappings
Network Configurations
Overview of Block Volume

Typical Block Volume Scenarios
Volume Attachment Types
Volume Access Types
Device Paths
Regions and Availability Domains
Resource Identifiers
Ways to Access Oracle Cloud Infrastructure
Authentication and Authorization
Security
Monitoring Resources
Moving Resources
Tagging Resources
Creating Automation with Events
Block Volume Encryption
Block Volume Data Eradication
Block Volume Performance
Volume Replication
Block Volume Durability
Block Volume Capabilities and Limits
Always Free Resources

Infrastructure
Database
Networking
Observability and Management
Additional Services
Service Usage and Limits
Signing in to Compute Cloud@Customer

Signing in to the Compute Cloud@Customer Console
Accessing the Compute Cloud@Customer CLI
Accessing the Compute Cloud@Customer API
Creating Kubernetes Clusters Using Console Workflows


Find out about the two ways to create a Kubernetes cluster using Container Engine for Kubernetes (OKE).

You can use Container Engine for Kubernetes to create new Kubernetes clusters. To create a cluster, you must either belong to the tenancy's Administrators group, or belong to a group to which a policy grants the CLUSTER_MANAGE permission. See Policy Configuration for Cluster Creation and Deployment.

Using the Console, you first specify basic details for the new cluster (the cluster name, and the Kubernetes version to install on control plane nodes). You can then create the cluster in one of two ways:

Using default settings in the 'Quick Create' workflow to create a cluster with new network resources as required. This approach is the fastest way to create a new cluster. If you accept all the default values, you can create a new cluster in just a few clicks. New network resources for the cluster are created automatically, including regional subnets for the Kubernetes API endpoint, for worker nodes, and for load balancers. The regional subnet for load balancers is public, but you specify whether the regional subnets for the Kubernetes API endpoint and for worker nodes are public or private. To create a cluster in the 'Quick Create' workflow, you must belong to a group to which a policy grants the necessary permissions to create the new network resources (see Create One or More Additional Policies for Groups).

Using custom settings in the 'Custom Create' workflow. This approach gives you the most control over the new cluster. You can explicitly define the new cluster's properties, including encryption settings. And you can explicitly specify which existing network resources to use, including the existing public or private subnets in which to create the Kubernetes API endpoint, worker nodes, and load balancers.

Note that although you will usually define node pools immediately when defining a new cluster in the 'Custom Create' workflow, you don't have to. You can create a cluster with no node pools, and add node pools later. One reason to create a cluster that initially has no node pools is if you intend to install and configure a network policy provider like Calico to support Kubernetes NetworkPolicy resources. If you install Calico on a cluster that has existing node pools in which pods are already running, you'll have to recreate the pods when the Calico installation is complete. For example, by running the kubectl rollout restart command. If you install Calico on a cluster before creating any node pools in the cluster (recommended), you can be sure that there will be no pods to recreate. See Example: Installing Calico and Setting Up Network Policies.

In addition to using the 'Quick Create' and 'Custom Create' workflows in the Console, you can also create clusters using the CLI and the API. For more information, see Creating a Cluster.
Creating API Gateways and Resources


Find out how to create API gateways and other related resources with API Gateway.

Read about how to use the API Gateway service to create API gateways and other related resources:

Creating an API Gateway
Creating an API Resource with an API Description
Creating an API Deployment Specification
Deploying an API on an API Gateway by Creating an API Deployment
Generating SDKs for an API Resource
Creating and Training a Model


Use a Language project to contain a model that describes the labelled data.

Console
CLI
API
Open the navigation menu and click Analytics & AI. Under AI Services, click Language.
In the left-side navigation menu, click Projects.
Select the compartment that contains the project that you want to use, or select the compartment that you want to create a project in.
Perform one of the following actions:
To use an existing project, click its name.
To create a new project, click Create Project.
On the project's details page, click Create custom models.
Choose the model type:

Text classification: Select the classification model type. Single label is the default.

Named entity recognition
For Training data, select one of the followingoptions and provide the additional information:
Object Storage

First, ensure that the dataset is allowed and is uploaded in a bucket in Object Storage. Then, select the following values:

Select the bucket that the dataset is in.

Select a training data file for the model to use.

Data Labeling

From the list, select a dataset for the model to use.

(Optional) Click Change Compartment to select a different compartment for the bucket or dataset.
(Optional) Click here to create a new dataset with the Data Labeling service.
Enter the specifics for the dataset.
Create the dataset.
Return to the Language service.

For guidance on how to create and label datasets for Data Labeling, see text labeling, document labeling, and creating datasets for Data Labeling.

(Optional) To set the validation and test data, click Show advanced options, then select the validation and test datasets to use.

Change the compartment if the dataset resides in a different one.

If you select a validation dataset, you must have a corresponding test dataset.

Click Next.
Select a compartment to host the custom model. We recommend that you save it in the same compartment as the project.
(Optional) Enter a unique name (255 character limit) for the resource.

If you don't provide a name, one is automatically generated. For example, ailanguage<resource>20230825155844.

(Optional) Enter a description (400 character limit) for the resource.
Click Next.
Review the selections.
(Optional) Click Edit to change the choices by returning to the Select data or Model detail step, and then complete the steps again.
Click Create and train.
This step might take as long as 30 minutes depending on the dataset. The model metrics are populated after the model is active.
Pod Networking
 CNI plugin.
Overview of the Email Delivery Service

Email Delivery Service Components
Regions and Availability Domains
Ways to Access Oracle Cloud Infrastructure
Authentication and Authorization
SMTP Authentication and Connection Endpoints
Monitoring Resources
Email Delivery Service Capabilities and Limits
Required IAM Service Policy
Dedicated IP Addresses
Tagging Resources
Integration with Oracle Cloud Infrastructure Services
Deleting a Data Asset


Delete a data asset using the Console, CLI, or API.

When you delete a data asset, all the harvested data entities or attributes in the data asset are deleted. All the jobs and schedules associated with the data assets are also deleted.

Console
CLI
API
On the Data assets page, click the data asset that you want to delete.
On the details page of the data asset, click Delete.
To confirm the data asset deletion, in the Delete Data Asset dialog box, type Delete and then click Delete.