Jay-Rajput/oci_data huggingface dataset:
Projects and Folders


Projects are organizational resources within a workspace that you can use to organize your design-time resources, such as tasks or data flows. You can also create folders in a project to further organize the design-time resources into logical groups.

To work with projects and folders, on the home page of a workspace, click Projects. On the Projects page, create a project or select a project from the list to view or edit the project details, or access folders in the project.

The following pages describe how to create projects and folders:

Projects
Creating a Project (Blank or with Samples)
Creating a Project by Copying from Another Project
Monitoring Project Copy Requests
Viewing the Details of a Project Copy Request
Copying Source and Target Keys
Terminating a Project Copy Request
Viewing the Details of a Project
Editing a Project
Deleting a Project
Folders
Creating a Folder
Viewing the Details of a Folder
Editing a Folder
Moving a Folder
Deleting a Folder

The following pages describe how to export and import projects and folders:

Exporting a Project
Importing a Project
Exporting a Folder
Importing a Folder
Getting an Image's Details


Find out how to get details of an image in a repository in Container Registry.

To make sure you pull the correct image or to identify images that you no longer need, you can get detailed information about the images in Container Registry.

Your permissions control which images you can get information about (see Policies to Control Repository Access). You can get information about images in repositories that you've created, and in repositories that the groups to which you belong have been granted access by IAM policies. If you belong to the Administrators group, you can get information about images in any repository in the tenancy.

Console
CLI
API

To get details of an image in Container Registry using the Console:

Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Container Registry.
Select the region that contains the registry.

Select the compartment that contains the image.

The Repositories and images field lists the repositories in the selected region and compartment to which you have access.

Click the plus (+) button beside the name of the repository that contains the images you want to get detailed information about.

Below the name of the repository, the images in the repository are listed, identified by the version identifier of each image.

From the list, select the image for which you want to see detailed information, as follows:

Display the Image information tab to see the size of the image, when it was pushed and by which user, and the number of times the image has been pulled.
Display the Layers tab to see the SHA message digest of each layer in the selected image.
Display the Versions tab to see the full path for the image with the version identifier you select. Note that if you select a different version identifier, the summary details change accordingly.
Display the Tags tab to see the free-form tags and defined tags applied to the image. For more information, see Applying Free-form Tags and Defined Tags to Repositories, Images, and Image Signatures.
Display the Signatures tab to see details of signature(s) created if the image was signed. For more information, see Signing Images for Security.
Display the Scan Results tab to see a summary of each scan of the image for the last 13 months. For more information, see Scanning Images for Vulnerabilities.
(Optional) If you want to pull an image, click Copy pull command. The command you copy includes the fully qualified path to the image's location in Container Registry, in the format <region-key>.ocir.io/<tenancy-namespace>/<repo-name>:<version>. For example, docker pull iad.ocir.io/ansh81vru1zp/project01/acme-web-app:v2.0.test. See Pulling Images Using the Docker CLI.
Related Content


Use the listed resources to explore more about Access Governance capabilities, refer to OAG REST APIs to create, manage, and view GovernanceInstances, and read OAG Rel Notes to learn about new features and enhancements added recently to improve your experience.

Oracle Access Governance Release Notes
Access Governance REST APIs
Displaying the Console History for an Instance

Required IAM Policy
Tagging Resources
Managing Console History Data
Using the Console
Using the CLI
Using the API
API Gateway

Community
Oracle Cloud Infrastructure blog
Cloud infrastructure community forum
Listing Monthly Subscription Rewards


List the rewards for a subscription ID.

Console
CLI
API

To view the rewards summary and other details, open the navigation menu and click Billing & Cost Management. Under Programs and Rewards, click Oracle Support Rewards. The Oracle Support Rewards page opens.

 Note

If the subscription and products are eligible for rewards but there is no associated usage, a message is displayed to indicate that no rewards data was found (because no rewards data has accrued yet).

You can view rewards by subscription, which you can select from the corresponding Subscription list. The following rewards summary is shown:

Available Support Rewards: The total amount of accrued rewards that you can use.
Redeemed Support Rewards: The total amount of rewards that you have redeemed.
Current Contractual Accrual Rate: The rewards accrual rate. For example, customers can accrue rewards either at US$0.25 for every $1 of OCI usage, or $0.33 for every $1 of OCI usage if they have a ULA (Unrestricted License Agreement).
Ending Soon: The rewards amount that expires within 30 days.

Following the rewards summary, a more detailed tabular view of the rewards is listed:

Expiration Date: The date when rewards expire.
Accrual Date: The date when the rewards were earned.
Total Usage: The total usage amount evaluated for rewards (Eligible Usage + Non-Eligible Usage = Total Usage).
Eligible Usage: The amount of usage that's eligible for rewards spending.
 Note



Eligible usage details aren't available for months where reward information was uploaded manually.

Non-Eligible Usage: The amount of usage not eligible for rewards.
 Note



Not all usage accrues rewards. Consumption of third-party services and offerings, such as VMware, Microsoft, and Oracle Cloud Marketplace, aren't eligible to earn rewards. For more information, see https://www.oracle.com/cloud/rewards/faq/.

Accrued Rewards: The sum of any remaining rewards. Equivalent to the value of Available Support Rewards in the rewards summary.
Redeemed: The amount of redeemed rewards. Equivalent to the value of Redeemed Support Rewards in the summary.
Remaining: The amount of remaining (Accrued Rewards - Redeemed) rewards. Remaining rewards that are expiring soon are highlighted in red.
Frequently Asked Questions: Oracle Cloud Infrastructure Free Tier
Oracle Cloud Infrastructure Cloud Adoption Framework
Oracle Cloud's Free Tier
Always Free Resources
Quickly Launch Your Always Free Resources Using Resource Manager
Frequently Asked Questions
Oracle Database Service for Azure
Oracle Cloud Infrastructure Government Cloud
Oracle EU Sovereign Cloud
Applications Services
Infrastructure Services
Developer Resources
Security
More Resources
Glossary
Oracle Cloud Console
Skip to main content
Frequently Asked Questions

The OCI Free Tier product page has answers to frequently asked questions about the Free Tier program.

See Frequently Asked Questions for more information.
Enabling and Viewing Maintenance Notifications

About Notifications
Who Can Receive and View Maintenance Notifications
Viewing Maintenance Notification Announcements
Creating a Subscription for Maintenance Announcements
Adding Subscribers to an Existing Subscription
Speech
 API
SDKs and the CLI
Troubleshooting
Job and task failures
Media size and duration
File not supported or low sample rate
Large batch job
Creating a Metastore


Create a metastore in your tenancy. You can create only one metastore in a compartment in your tenancy.

Console
CLI
API
Open the navigation menu and click Analytics & AI. Under Data Lake, click Data Catalog.
On the Data Catalog service page, click Metastores.
Click Create Metastore.
In the Create Metastore panel, perform the following actions:
In Create in Compartment, select the compartment where you want to create the metastore.
In the Name field, enter a name for the metastore.
In the Default managed table location field, enter the Object Store URL of the location of the managed table. For more information, see Prerequisites.
 Note

We recommend that you do not use the same location for managed and external tables. If both the tables are in the same directory, deletion of data from managed table can result in loss of data from the external table also.
In the Default external table location field, enter the Object Store URL of the location of the external table. For more information, see Prerequisites.
(Optional) In the Tags section, add tags that can help to identify the metastore.
Choose one of the following:
To create the metastore, click Create.
To create the metastore later using Resource Manager and Terraform, click Save as Stack to save the resource definition as a Terraform configuration. For more information about saving stacks from resource definitions, see Creating a Stack from a Resource Creation Page.
Using Pipeline Operators

Start Operator and End Operator
Merge Operator
Expression Operator
Decision Operator
Data Loader Task Operator
Integration Task Operator
Pipeline Task Operator
SQL Task Operator
OCI Data Flow Task Operator
REST Task Operator
Parameters
 are names of placeholders that exist in DevOps resources. They’re available to all resources within the pipeline.

All parameters used in the pipeline must have a value before the pipeline is run. When the pipeline is run, you have the option to override the default value of the parameter with an argument value for that particular run. If a parameter has both argument and default value, then the argument value takes precedence.

Placeholders can be used as input in DevOps resources such as pipeline, stage, or artifact resource. For example, a placeholder can be used while adding a DevOps artifact resource such as in the artifact version or a Container Registry tag. Any placeholders in the artifacts are substituted by the corresponding parameter values by selecting Allow parameterization check box in the artifact configuration. For more details, see Managing Artifacts.

Placeholders can also be used in the content of an artifact, such as instance group deployment specification or a Kubernetes manifest. Consider the following two examples where you can use placeholders:
In Kubernetes manifest, you can define the replicas as replicas: ${nginxReplicaCount}.
In the instance group deployment specification, you can set an environment variable version as version: ${appVersion}. For more details, see deployment configuration file.
Calling and Parameterizing APIs


Find out how to call and parameterize APIs deployed using API Gateway.

Read about how to call and parameterize APIs that you've deployed using the API Gateway service:

Calling an API Deployed on an API Gateway
Adding Path Parameters and Wildcards to Route Paths
Adding Context Variables to Policies and HTTP Back End Definitions
Approval Templates


Use templates in Oracle Managed Access to identify users and groups who can approve requests for temporary access to resources in your organization's tenancy.

Approval templates can require up to three levels of approvals. You can also select to automatically approve requests for resource access. For more information, see Resource Settings.

You can perform the following approval template tasks:

Creating an Approval Template
Editing an Approval Template
Deleting an Approval Template
Viewing Access Requests
Changing the Compartment of an Approval Template
OCI Database with PostgreSQL Policies

Overview of Policy Syntax
Resource-Types
Supported Variables
Details for Verbs + Resource-Type Combinations
Permissions Required for Each API Operation
Policy Examples
Managing Dedicated AI Clusters

 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.

Dedicated AI clusters are compute resources that you can use for fine-tuning custom models or for hosting endpoints for custom models. The clusters are dedicated to your models and not shared with users in other tenancies.

If you have manage permissions to generative-ai-family, you can perform the following tasks for dedicated AI clusters:

Create a dedicated AI cluster for fine-tuning custom models
Create a dedicated AI cluster for hosting models
List the dedicated AI clusters
Get a dedicated AI cluster's details
Update a dedicated AI cluster
Delete a dedicated AI cluster
Connector Hub
 learning videos
QRadar Visualization of Log Data (blog)
Datadog Monitoring (blog)
SIEM in Splunk (architecture)
Cloning a File System


Clone a File Storage file system.

Before you can clone a file system, at least one snapshot must exist for the file system. For more information, see Creating a Snapshot. The clone is a copy of the file system data as it exists at the date and time that the selected snapshot was taken.

Hydration begins immediately upon instantiation of the clone. To view the clone's hydration status, source snapshot, parent file system, and other cloning information, visit the details page of the cloned file system. For more information, see Getting a File System's Details.

You can export, mount, and use the clone immediately for READ or WRITE operations after you create it. See Creating an Export and Mounting File Systems for more information. Cloned file systems are managed in the same way that any other file system is managed.

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 that you want to clone.
On the file system's details page, under Resources, click Snapshots.
In the Snapshots list, find the snapshot that you want to use as the source of the clone, click the Actions menu (), and then click Clone.
In the Create Clone panel, specify the details about the clone that aren't inherited from the parent file system. You can choose to accept the provided system defaults, or change them by clicking Edit details.
Name: File Storage service creates a default name using FileSystem-YYMMDD-HHMM. Optionally, change the default name for the file system. It doesn't have to be unique; an Oracle Cloud Identifier (OCID) uniquely identifies the file system. Avoid entering confidential information.
Create in Compartment: Specify the compartment you want to create the clone of the file system in.
Encryption: File systems use Oracle-managed keys by default, which leaves all encryption-related matters to Oracle. Optionally, you can encrypt the data in this file system using your own Vault encryption key.
 Note

Only symmetric Advanced Encryption Standard (AES) keys are supported for file system encryption.
To use Vault for your encryption needs, select Encrypt using customer-managed keys. Select the vault compartment and vault that contains the master encryption key that you want to use, and then select the master encryption key compartment and master encryption key.
 Caution

Be sure to back up your vaults and keys. Deleting a vault and key otherwise means losing the ability to decrypt any resource or data that the key was used to encrypt. For more information, see Backing Up and Restoring Vaults and Keys.

(Optional) To add tags to the file system, click Show tagging options.

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, skip this option or ask an administrator. You can apply tags later.
Click Create.
Perform Advanced Search


Using Oracle Logging Analytics, you can search any logs and drill down to specific log entries to resolve problems quickly.

Topics:

Search in UI

Query Search

Export Logs

Also, see Write Performant Queries for Searching and Exporting Logs.
Payment History
 Table
Viewing Invoices
Viewing Usage Associated with an Invoice
Opening a Support Request
Differences between OCI Functions and Fn Project

Differences in Authentication When Making API Calls
Differences When Invoking Functions
Additional Context Configuration Parameters in OCI Functions
Use of Annotations
Managing OracleDB for Azure Users and Groups in Azure


Learn how to manage users and groups for OracleDB for Azure after your onboarding is complete.

OracleDB for Azure creates user groups in Azure Active Directory (AAD) during the initial account linking stage of your OracleDB for Azure sign up. You must assign Azure users to the appropriate OracleDB for Azure user groups in AAD to enable access to database and infrastructure resources. You must also assign users to the OracleDB for Azure enterprise application and to the related ARM role for the application.

See the following topics for more information:

Adding OracleDB for Azure Users in Azure After Completing Your Sign Up
Azure User Groups for OracleDB for Azure Database Resources
Azure User Groups for OracleDB for Azure Networking, Cost Management, and Support Requests
Overview of Oracle Cloud Marketplace


Oracle Cloud Marketplace is an online store—a one-stop shop—selling hundreds of business apps and professional services that complement your existing Oracle Cloud implementation.

All apps and services on the marketplace are offered by approved, registered, and expert partners and developers. Plus, Oracle has vetted, reviewed, and approved each product.

Oracle Cloud Marketplace:

Offers a large collection of trusted and innovative apps in many business categories, including marketing, sales, customer service, social, and talent management.

Like add-on or plugin software, these apps provide enhanced functions or customizations for your existing Oracle Cloud implementation.

Offers an assortment of services, such as consulting, implementation, integration, and training, to help you transition to the cloud and improve the successful operation of your company.
Creating an Approved Sender

Using the Console
Creating and Deploying Functions

Using Fn Project CLI Commands
Certification Information

Certification - Supported Browsers
Secure


Learn the key areas to routinely audit to ensure your data remains secure.

Articles in this section:

Securing OCI GoldenGate
Service Limits, Quotas, Policies, and Events

Service Limits
Service Quotas
Service Policies
Service Events
Preparing for Container Registry

Availability by Region
Appendix: Configuration Notes for OCI Functions


Find out detailed information and notes about the high-level tasks to perform before you can use OCI Functions.

To get set up and running quickly with OCI Functions, use the Functions QuickStart Guides.

This section provides more information and notes about the tasks you perform using the Functions QuickStart Guides to configure your tenancy and development environment for OCI Functions:

Tenancy Configuration Notes for OCI Functions
Client Environment Configuration Notes for OCI Functions
Verifying Your Configuration for Function Development
Copyright © 2023, Oracle and/or its affiliates.
About Oracle
Contact Us
Legal Notices
Terms of Use & Privacy
Document Conventions
Cookie Preferences
Creating a Migration Plan


Create a migration plan to test different configurations, compare cost models, and so on.

Console
CLI
API
Open the navigation menu and click Migration & Disaster Recovery. Under Cloud Migrations, click Migrations.
On the Migrations page, select the active migration project for which you want to create a migration plan.
From the Migration project details page, under Resources, select Migration plans and then click Create migration plan.
On the Create migration plan page, in the Basic info section, provide the following information:
Enter a display name. For example, vSphere6.5MigrationPlan2
Select the compartment.
Select a target compartment.
Specify the migration strategy:
Resource type: Select Default, CPU, or Memory.

If you do not define any resource type, the strategy type is applied to CPU and memory.

Strategy type: Select As is, Average, Peak, or Percentile. By default, the strategy type used is As is. If you select Average or Peak, you can specify the metric type or metric type window.
If you select Percentile, you can specify the metric time window and percentile.
(Optional) Enter a numeric value as the adjustment multiplier.

To know more about the recommendation strategies based on migration strategies, see Understanding Recommendation Strategies and Cost Estimates. An example for a migration strategy type with resource type is as follows:

Use the following settings for a strategy based on the CPU utilization runtime metrics of the last 24 hours. The strategy is scaled up to 20% above average, so that any extra CPU usage is accounted for.

Set the resource type as CPU, strategy type as Average, metric-type as Runtime to use the metrics that are available from vCenter, metric-type window as one day, adjustment multiplier as 1.2.

In the Target environment section, provide the following information about the virtual machine:
Select the virtual machine shape. The available options are as follows:
Use system recommendation: Provides a virtual machine shape based on source metadata.
Select preferred shape type: Allows you to define the shape of the OCI virtual machine.

For information about changing a shape type, see Configuring a Target Asset.

Select a VCN and subnet in the target compartment.

You can use an OCI-managed host as a target for migration instead of using a shared OCI compute 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 migration plan.
You can now generate a Resource Manager stack or configure target assets.
Help Sheet - Disk Import Job Checklist

Firewall Information