Jay-Rajput/oci_data huggingface dataset:
Transferring Data To and From File Storage

Transferring On-Premises Data to File Storage
For Linux Users
For Windows Users
Using Instance-to-Instance Streaming to Transfer File Storage Data
Licensing Information User Manuals


Access licensing information.

Oracle Cloud Infrastructure Licensing Information User Manual

Licensing Information User Manual for Exadata Cloud at Customer

Infrastructure Migration Tools Third Party License Attribution File
Paths in File Systems


The File Storage service uses three kinds of paths :

Export Paths are part of the information contained in an export that makes a file system available through a mount target. The export path uniquely identifies the file system within the mount target, letting you associate up to 100 file systems behind a single mount target. The export path is used by an instance to mount (logically attach to) the file system. This path is unrelated to any path within the file system or the client instance. It exists solely as a way to distinguish one file system from another within a single mount target.

In this mount command example, 10.0.0.6 is the mount target IP address./FileSystem1 is the unique export path that was specified when the file system was associated with a mount target during creation.

sudo mount 10.0.0.6:/FileSystem1 /mnt/mountpointA

 Important



The export path must start with a slash (/) followed by a sequence of zero or more slash-separated elements. If there are many file systems associated with a single mount target, the export path sequence for the first file system can't contain the complete path element sequence of the second file system export path sequence. Export paths can't end in a slash. No export path element can be a period (.) or two periods in sequence (..). No export path can exceed 1024 bytes. Lastly, no export path element can exceed 255 bytes.

Valid examples:

/example and /path
/example and /example2

Invalid examples:

/example and /example/path
/ and /example
/example/
/example/path/../example1
 Caution

If one file system associated with a mount target has '/' specified as an export path, you can't associate another file system with that mount target.
 Note

Export paths can't be edited after the export is created. To use a different export path, you must create a new export with the appropriate path. Optionally, you can then delete the export with the old path.

See Managing Mount Targets for more information about mount targets and exports.

Mount Point Paths are paths within a client instance to a locally accessible directory to which the remote file system is mounted.

In this mount command example, /mnt/mountpointA is the path to the directory on the client instance on which the external file system is mounted.

sudo mount 10.0.0.6:/FileSystem1 /mnt/mountpointA

See Mounting File Systems for more information.

File System Paths are paths to directories within the file system, and contain the contents of the file system. When the file system is mounted, you can create any directory structure within it you like. Snapshots of the file system can be accessed using the file system path, under the file system's root directory at .snapshot/name.

The following example shows the path to a snapshot called 'January 1' when navigating from the instance:

/mountpointA/.snapshot/January1
Network Resources

Understanding Networking
Customer Network and the Cluster Private Network
Attaching a Private Endpoint


Attach a private endpoint to a data catalog to enable its data assets  to be harvested  using the configured private network. You can attach only one private endpoint to a data catalog, and a private endpoint can be attached only to one data catalog.

Console
CLI
API
Before you attach a private endpoint to a data catalog, you must create a private endpoint.
On the Data Catalogs page, click the Actions menu to the right of the instance to which you want to attach a private endpoint and select Attach private endpoint.
In the Attach private endpoint dialog box, select the private endpoint. If there are no private endpoints in the current compartment, select a compartment that contains a private endpoint.
Click Attach.
Functions
/home.htm
Get Started with Administration

About Oracle Analytics Cloud on Gen 2
Typical Workflow for Administrators
Before You Begin with Oracle Analytics Cloud on Gen 2
Signing In to the Oracle Cloud Infrastructure Console
Security Architecture


Protect your organization's assets with a security architecture that prevents misconfiguration errors and implements mandatory security best practices.

We recommend that you understand the foundations of security at Oracle Cloud Infrastructure, and use this approach as a model when you develop your organization's own guiding principles for security. Oracle Cloud Infrastructure's security approach is based on seven core pillars. Each pillar has multiple solutions designed to maximize the security and compliance of the platform.

Oracle Cloud Infrastructure Security Pillar	Description	Example Solutions
Customer isolation	

Deploy applications and data assets in an environment that commits full isolation from other tenants and Oracle's staff.

In the context of the Cloud Adoption Framework, your organization's enterprise architecture should define how to isolate application data and resources.

	
Bare metal and virtual machine (VM) instances
Virtual cloud networks (VCNs)
Oracle Cloud Infrastructure Identity and Access Management (IAM)
Compartments

Data encryption	Protect data at-rest and in-transit in a way that lets you meet your security and compliance requirements.	
Default encryption for storage
Oracle Cloud Infrastructure Vault service
Database encryption

Security controls	Reduce risks associated with malicious and accidental user actions by managing access to services and segregating operational responsibilities.	
User authentication and authorization
Instance principals
Network security control
Oracle Cloud Infrastructure Web Application Firewall (WAF)

Visibility	Reduce security and operational risks by auditing and monitoring actions through comprehensive log data and security analytics.	
Audit logs
Cloud access security broker (CASB) based monitoring and enforcement

Secure hybrid cloud	Use existing security assets, such as user accounts, policies, and third-party security solutions, when accessing cloud resources and securing data and application assets.	
Identity federation
Third-party security solutions
Site-to-Site VPN
FastConnect

High availability	Ensure consistent uptime for workloads with fault-tolerant data centers that are resilient against network attacks.	
Availability domains and fault domains
Service level agreements (SLAs)

Verifiably secure infrastructure	Use verifiably secure infrastructure that implements rigorous processes and security controls in all phases of development and operation.	
Security operations
Compliance certification and attestation
Customer penetration and vulnerability testing
Creating a Redis Cluster


Create a Redis cluster with Cache with Redis.

When you create an Redis cluster, Cache with Redis creates the set of Compute instances that provide the Redis caching functionality. Each cluster is composed of one primary node and optionally one or more data nodes, based on the options that you specify when you create the cluster.
Console
CLI
API

Open the navigation menu and click Databases. Under Redis, click Clusters.

Click Create Cluster.

Specify a name for the cluster, select the compartment to create the cluster in, and then click Next.

Optionally change the cluster node configuration options, including the amount of memory in GB configured per node and the number of nodes for the cluster. After you're done updating the settings, click Next.

In Configure networking specify the virtual cloud network (VCN) and subnet for the cluster. Decide whether you want to use an existing VCN and subnet, create a new VCN or subnet, or specify the OCID for an existing subnet.

Click Next, review the cluster confirmation details on the Summary page, and then click Create Cluster.
Publishing Community Applications

Required IAM Policy
Getting Started


Before you can create and use Big Data Service clusters in a new account review the prerequisites and list of tasks

When you sign up for Oracle Cloud Infrastructure, Oracle creates a tenancy for the account. The tenancy is a secure and isolated partition within Oracle Cloud Infrastructure where you can create, organize, and administer your cloud resources.

Big Data Service uses Oracle Cloud Infrastructure Identify and Access Managment (IAM) for authentication and authorization through Oracle Cloud Infrastructure. Create Identity and Access Management (IAM) users, groups, and policies to control access to resources used in your Big Data Service environment. Manage authentication and authorization to Big Data Service by using Oracle Cloud Infrastructure services and by using Linux OS services and accounts.

To set up access controls for Big Data Service through IAM, an administrator must:

Optionally create compartments in the tenancy to organize and isolate resources and services.

Configure the Virtual Cloud Network (VNC) for the service including subnets and network resources. Network access rules control access to the network and resources on the network.

Create groups and add users to the group. At a minimum, create an administrators group and a users group.

Create policies to control access. Policies can be written, for example, to say which groups can perform what actions on which resources in which compartments.

 Note

Every tenancy has one or more users in the Administrators group. These users are cloud administrators and can perform the preceding actions, even if no administrator is defined for Big Data Service.

For information about users, groups, and policies defined through IAM, see Overview of Oracle Cloud Infrastructure Identity and Access Management and subsequent topics.

For more information on getting started, see:

Typical Workflow
Setting Up the Required Resources
Planning and Understanding ODH Clusters
Accessing Big Data Service
Defining Security Rules
Connecting to Cluster Nodes with Private IP Addresses
Ports Used by ODH Cluster Components
Connecting to a Cluster Node Using SSH
Connecting to Services on a Cluster Using Load Balancer



For more information click here https://docs.oracle.com/en-us/iaas/Content/cloud-marketplace/what-do-i-need-to-know-to-get-started.htm#what-do-i-need-to-know-to-get-started

For more information click here https://docs.oracle.com/en-us/iaas/mysql-database/doc/getting-started.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/document-understanding/using/getting_started.htm#getting_started

For more information click here https://docs.oracle.com/en-us/iaas/Content/data-labeling/using/getting-started.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/bigdata/get-started.htm

For more information click here https://docs.oracle.com/en-us/iaas/access-governance/doc/getting-started.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/ansiblegetstarted.htm#Getting_Started_with_Oracle_Cloud_Infrastructure_and_Ansible
Setting Up Data Sources

Required IAM Policies for Data Integration Data Asset
Required IAM Policies for Metastore
Required IAM Policies for MySQL Data Asset
Required IAM Policies for Oracle Object Storage Data Asset
Required IAM Policies for using OCI Vault
Deleting a Private Endpoint


Delete a private endpoint that is detached from a data catalog.

 Caution

If you attempt to delete a private endpoint that is still attached to a data catalog, you receive a warning that the private endpoint can't be deleted. You must first detach the private endpoint from that data catalog and then delete the private endpoint.
Console
CLI
API
On the Data Catalog service page, click Private Endpoints.
From the private endpoints list, select the private endpoint you want to move.
On the private endpoints details page, click Delete.
In the Delete Private Endpoint dialog box, type DELETE to confirm and click Delete.
A notification displays indicating that the private endpoint is deleted successfully.
 Important

The data catalog data assets that use the private endpoint that you deleted can no longer be harvested again.
Partner Portal

Community
Oracle Cloud Infrastructure blog
Cloud infrastructure community forum
Policies
Tax and Marketplace Transactions by Publisher policies
Territory and export compliance policy
Government policy
Troubleshooting
Need some help? Check here for answers
FAQs
Click here for frequently asked questions
Securing Object Storage

Security Responsibilities
Initial Security Tasks
Routine Security Tasks
IAM Policies
Access Control
Cloud Guard
Security Zones
Data Encryption
Data Durability
Data Security
Network Security
Auditing
Creating a Repository


Create code repositories in the DevOps service.

Each service in Oracle Cloud Infrastructure (OCI) integrates with Identity and Access Management (IAM) for authentication and authorization. To grant users permission to access the DevOps code repositories and other resources, you have to create dynamic groups and IAM policies.

For creating dynamic groups and policies for code repositories, see Code Repository Policies. For more details, see DevOps IAM Policies.

An authentication (auth) token is required for each user who uses Git to interact with the code repositories in Oracle Cloud.

Before you create a code repository, you must have a DevOps project.

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.
Select a project and from the left-side menu, click Code Repositories.
Click Create Repository.
In the Create repository panel, provide the following information:
Enter a name and description for the repository. Entering a description is optional.
Enter a default branch name.
If the value is not provided, then the branch is named as "main".
(Optional) To add tags to the repository, click Show tagging options.

Tagging is a metadata system that lets you organize and track the resources in your tenancy.

If you have permissions to create a resource, you also have permissions to add free-form tags to it.

To add a defined tag, you must have permissions to use the tag namespace.

For more information, see Resource Tags.

Click Create Repository.
An empty code repository is created on the main branch.

To add files to the repository, you must clone the repository. For more information, see Cloning a Repository.



For more information click here https://docs.oracle.com/en-us/iaas/Content/devops/using/create_repo.htm#create_repo
Managing Kubernetes Clusters


Find out about managing the Kubernetes clusters, node pools, and nodes you've created using Container Engine for Kubernetes (OKE).

Read about how to use Container Engine for Kubernetes to manage Kubernetes clusters:

Cluster Management
Node Pool Management
Node Management
Configuring Cluster Add-ons
Configuring IMDS for Kubernetes Clusters
Using Custom Cloud-init Initialization Scripts to Set Up Managed Nodes
Managing Worker Node Capacity Types
Tagging Kubernetes Cluster-Related Resources
Managing Secrets for Kubernetes Clusters
Configuring DNS Servers for Kubernetes Clusters
Creating Worker Nodes with Updated Properties
Migrating to VCN-Native Clusters
Generated Worker Node Name Formats
Copyright © 2023, Oracle and/or its affiliates.
About Oracle
Contact Us
Legal Notices
Terms of Use & Privacy
Document Conventions
Viewing Data Assets


View the data assets created in a Data Catalog repository to review or edit the data asset and connection information.

All data assets created in your data catalog are listed on the Data Assets tab. When you click a data asset, the data asset details page appears. Apart from the Summary tab, the rest of the tabs that appear depend on the type of data asset that you create. For example:

For an Object Store data asset, the following tab appears:
Buckets
For an Autonomous Data Warehouse data asset, the following tab appears:
Schemas
For a Metastore data asset, the following tab appears:
Catalogs
 Note

In the catalog details page, the Databases tab lists the available databases in the catalog. However, if you find the table empty, the possible reasons are as follows:
Sync is not enabled
The sync job schedule is at a later time
There are no databases under the selected catalog
The schedule is in progress and the databases are yet to be listed
Sync failed
An update in Metastore is in progress. The databases that are added during this update get reflected in Data Catalog only in the next schedule of the sync job.

You can explore data assets and data entities. The data entities are available for exploring after you have harvested the data asset.
Best Practices for Your Alarms

Create a Set of Alarms for Each Metric
At-Risk Example
NonOptimal Example
Resource is Up or Down Example
Select the Correct Alarm Interval for Your Metric
Suppress Alarms During Investigations
Routinely Tune Your Alarms
Get Started with Oracle Platform Services

Supported Platform Services
Understand the Infrastructure Prerequisites
Learn About Service-Specific Differences and Workflows
REST API Endpoints for Platform Services
Policies

Tasks



For more information click here https://docs.oracle.com/en-us/iaas/Content/network-firewall/policies.htm
Digital Assistants
?
High Availability

Failover
Switchover
Limitations
Billing



For more information click here https://docs.oracle.com/en-us/iaas/mysql-database/doc/high-availability.html
Mounting File Systems From UNIX-Style Instances

Prerequisites
Mounting File Systems
Mounting File System Subdirectories
Writing to File Systems
Unmounting File Systems
Getting a Vulnerability Audit's Details


Describes how to get the details of a vulnerability audit.

Console
CLI
API
Open the navigation menu and click Developer Services. Under App Dependency Management, click Vulnerability Audits.
On the Vulnerability audits page, from the list of compartments on the left side, select a compartment.
From the list of vulnerability audits, click the vulnerability audit for which you want to view the details.
On the Vulnerability audit details page, you can view the details of the vulnerability audit. In the Application dependencies table, you can view the list of the associated application dependencies. The table displays the dependency name, version, and criticality score. When you click the vulnerability link, it opens the National Vulnerability Database page.
Email Delivery
 with service logs
Integrations
Oracle Application Express
Postfix
JavaMail
PeopleSoft
Support
Get help and contact support
Create a service request
Ask the community
Getting Started with OS Management Hub

Prerequisites
Compartment Considerations
Required IAM Policy
What's next
Migrate to Later Versions of Spark


Find out how to use Data Flow with a later version of Spark.

Migrate Data Flow to Spark 3.2.1
Migrating Data Flow Applications from Using Spark 2.4 to Using Spark 3.0.2
Administering Managed Instance Groups

Creating Managed Instance Groups
Adding Managed Instances to Groups
Removing Managed Instances from Groups
Deleting Managed Instance Groups
Using the API
Working with Console Dashboards Groups

Sharing Dashboards with Groups
Federating with Identity Providers


Learn about and use identity federation.

This section contains information about federating with identity providers:

Managing Identity Providers: Learn how to set up federated login between an identity domain and external identity provider so that users can sign in and access Oracle Cloud Infrastructure resources using existing logins and passwords managed by the identity provider.
Managing Identity Provider Policies: Find out how to use identity provider policies to define which identity providers are visible in the Sign In page.
Managing User Capabilities for Federated Users: Manage the user capabilities available to federated users, including API keys, auth tokens, SMTP credentials, customer secret keys, and OAuth 2.0 client credentials.



For more information click here https://docs.oracle.com/en-us/iaas/Content/Identity/Concepts/federation.htm
Database Management

Monitor Oracle Databases
Oracle Database fleet
Single External Database and Oracle Cloud Database
Single Autonomous Database
Dashboards
Metrics for Oracle Databases
Alarms for Oracle Databases
Monitor External Database Systems
External Database Systems
Clusters
ASM instances
Listeners
Metrics for External Database Systems
Alarms for External Database Systems
Monitor Exadata Infrastructure
Exadata Infrastructure fleet
Single Exadata Infrastructure resource
Storage server grid
Single storage server
Metrics for Exadata Infrastructure
Alarms for Exadata Infrastructure
Monitor MySQL HeatWave
MySQL DB system fleet
Single MySQL DB system
Performance Hub for MySQL DB systems
Metrics for MySQL DB systems
Alarms for MySQL DB systems
Creating Support Request


Learn how to create and manage support requests on the Marketplace console. There are various support options to help you with your queries which include documentation, chatting with the support team, visiting the support center, posting your question to our forum, and submitting your feedback.

Some services allow you to create support requests for individual resources while viewing them in the Oracle Cloud Infrastructure Console. When you create a support request from the resource details page, the support ticket automatically includes relevant details about the resource from the General Information section of the page. If you are contacting support for the first time, ensure you add an email ID to your user account.

To create and manage support requests on the Marketplace console, do the following:

On the console, click the Support button () .

Under Request Help, Click Create Support Request to open the Support Options form.

Enter the following:

Issue Summary: Enter a title that summarizes your issue. Avoid entering confidential information.
Describe Your Issue: Provide a brief overview of your issue.
Include all the information that My Oracle Support requires to route and respond to your request. For example, "I am unable to connect to my compute instance."
Include troubleshooting steps taken and any available test results.
Select the severity level for this request.
 Note

Optionally, you can include the tenancy, region of launch, opc-request-id displayed on the console, listingId attempted to launch details in the description, to help resolve your query effectively.

Optionally, click Show the information we've gathered to see the resource details included in the support request.

Click Create Request.
Big Data Tutorials and Workshops

Big Data Clusters with Oracle Distribution including Apache Hadoop
Get Started with Big Data (non-HA Cluster)
Get Started with Big Data (HA Cluster)
Big Data Clusters with Cloudera Distribution including Hadoop
Get started with Big Data (Non-HA Cluster)
Get started with Big Data (HA Cluster)
Use a load balancer to access services on Big Data (HA Cluster)
Use a load balancer to access services on Big Data (Non-HA Cluster)
Connecting Oracle DataSource for Apache Hadoop and Big Data to Autonomous Data Warehouse
Business Continuity


Refer to the recovery time objective and recovery point objective for business continuity.

Recovery Time Objective (RTO) and Recovery Point Objective (RPO)

Related Topics

High Availability
Backing Up a DB System
Point-In-Time Recovery
Selecting, Searching, and Filtering

Understanding Compartments
Filtering the Displayed List of Resources