Jay-Rajput/oci_data huggingface dataset:
Moving API Gateways and API Deployments Between Compartments


Find out how to move API gateways and API deployments between compartments with the API Gateway service.

Having created an API gateway, and deployed an API on the API gateway by creating an API deployment, you might decide to move either or both from one compartment to another. An API gateway and the individual API deployments deployed on it can be in different compartments.

Note that calls to an API deployment will be disrupted while the API deployment (or the API gateway on which it is deployed) is being moved to a different compartment. Do not call the API deployment until the move operation is complete.

Console
CLI
API

To move an API gateway or an API deployment to a different compartment using the Console:

In the Console, open the navigation menu and click Developer Services. Under API Management, click Gateways.
Choose a Compartment you have permission to work in.
On the Gateways page, click the name of the API gateway that you want to move (or that contains the API deployment you want to move) to show the Gateway Details page.

On the Gateway Details page:

To move the API gateway, click Move Resource, select the compartment to which you want to move the API gateway, and click Move Resource to start the process of moving the API gateway. Note that API deployments on the API gateway are not moved to the new compartment.
To move an API deployment, select Deployments from the Resources list, click Move Resource, select the compartment to which you want to move the API deployment, and click Move Resource to start the process of moving the API deployment.

Do not call an API deployment while the API deployment (or the API gateway on which it is deployed) is in the process of being moved to the new compartment.

On the Gateway Details page, select Work Requests from the Resources list and confirm the move operation is complete.

When the move operation is complete, resume calls to the API deployment.
Clearing All Keep Me Signed-In Sessions for a User


If Keep me signed-in has been set for an OCI IAM identity domain, you can delete the Keep me signed-in sessions for a user.

Keep me signed in must be enabled and the user has active Keep me signed-in sessions.

Open the navigation menu and click Identity & Security. Under Identity, click Domains.
Click the name of the identity domain that you want to work in. You might need to change the compartment to find the domain that you want. Then, click Users.
Click the user for which you want to clear all signed-in sessions.
On the details page for the user, click More Actions and then select Clear all signed-in sessions.
Confirm that you want to clear all sessions.
Using the CLI

Command Line Syntax
Basic Examples
Getting Help with Commands
Determining the Installed Version of the CLI
Authenticating Using Instance Principals
Using a Proxy Server
Using Dates and Times in CLI Commands
Managing CLI Input and Output
Advanced JSON Options
Advanced Examples
Data Assets

Getting Data Asset Details
Editing a Data Asset
Deleting a Data Asset
Moving a Data Asset Between Compartments



For more information click here https://docs.oracle.com/en-us/iaas/data-integration/using/data-assets.htm
Supported Versions of Kubernetes

Currently Supported Kubernetes Versions
Planned Support for Future Kubernetes Versions
Previously Supported Kubernetes Versions
File Storage
 Network Ports
Deleting File System Resources Overview



For more information click here https://docs.oracle.com/en-us/iaas/compute-cloud-at-customer/topics/file/file-storage.htm
Autoscaling Kubernetes Node Pools and Pods


Find out about autoscaling Kubernetes node pools and pods you've created using Container Engine for Kubernetes (OKE).

You can automatically scale the node pools and pods of clusters you create using Container Engine for Kubernetes to optimize resource usage.

To enable cluster autoscaling by autoscaling node pools, you can deploy the Kubernetes Cluster Autoscaler (see Using the Kubernetes Cluster Autoscaler). You can deploy the Kubernetes Cluster Autoscaler on a Kubernetes cluster in two ways:

as a standalone program (see Working with the Cluster Autoscaler as a Standalone Program)
as a cluster add-on (see Working with the Cluster Autoscaler as a Cluster Add-on)

To enable autoscaling by autoscaling pods, you deploy the Kubernetes Metrics Server to collect resource metrics from each worker node in the cluster (see Deploying the Kubernetes Metrics Server on a Cluster Using Kubectl). Having deployed the Kubernetes Metrics Server, you can then use:

the Kubernetes Horizontal Pod Autoscaler to adjust the number of pods in a deployment (see Using the Kubernetes Horizontal Pod Autoscaler)
the Kubernetes Vertical Pod Autoscaler to adjust the resource requests and limits for containers running in a deployment's pods (see Using the Kubernetes Vertical Pod Autoscaler)

You can use the Kubernetes Cluster Autoscaler in a cluster with both the Kubernetes Horizontal Pod Autoscaler and the Kubernetes Vertical Pod Autoscaler.

 Note



You can use the Kubernetes Cluster Autoscaler and the Kubernetes Vertical Pod Autoscaler with managed node pools only. You can use the Kubernetes Metrics Server and the Kubernetes Horizontal Pod Autoscaler with both virtual node pools and managed node pools.
Install Management Agents

Download the Agent Software
Create Install Key
Configure a Response File
Install Management Agent
Verify the Management Agent Installation
Troubleshoot Management Agent Installation Issues
CEMLI File Header Format


Learn the correct format for CEMLI file headers.

When inserting a header into a CEMLI file, ensure that the header uses the following format:

Copy
$Header: <file name> <version> <date> [<time>] <coder name> $


where:

<file name> is the CEMLI file name.

<version> is the CEMLI file version number.

<date> is the date when the CEMLI file was last changed, in one of the following formats - MM/DD/YYYY or YYYY/MM/DD, where MM is the month, DD is the day, and YYYY is the year.

<time> (optional) is the time at which the CEMLI file was last changed, in the format HH:MM, where HH is the hour and MM is the minute.

<developer name> is the name of the CEMLI file developer, with no spaces or blank characters.

For example:

Copy
$Header: XXAKDAPREG.fmb 115.3 2006/05/08 15:46 matery $


When including the header in SQL scripts, shell scripts, and other text files, use REM, # or similar comment syntax, for example:

Copy
REM %Header XXGERTTLS.sql 115.23.2 07/14/2008 joe Exp $
# $Header: XXREP.ldt 115.30 2009/08/24 13:32:38 mondev $


If your CEMLI file is a form, which has the extension .fmb, include the header using the FDRCSID function call in the When-New-Form-Instance Trigger.

If the file is a library, with extension .pll, include the header when using the FDRCSID function call in a program unit. For example:

Copy
FDRCSID('$Header: XXPPSND.fmb 120.6.120.3 2008/08/01 09:42 joe ship$')


For reports, with extension .rdf, include the header in the comment field property of the report module.
Scenario: Sending Streaming Data to Logging Analytics

Required IAM Policy
Goal
Setting Up This Scenario
Using the Console
Using the CLI
Using the API
IP Address Ranges

Public IP Addresses for VCNs and the Oracle Services Network
Public IP Addresses for the Oracle YUM Repos
Managing Inventory

Required IAM Policies
Using Inventory Assets with Oracle Cloud Migrations
API Gateway Internal Limits

API Gateway Resource Limits
API Deployment Resource Limits
API Gateway Certificate Resource Limits
HTTP Back End Resource Limits
API Gateway Invocation Limits
SDK Resource Limits
Usage Plan and Subscriber Resource Limits
API Limits
Preparing for Functions

Availability by Region
Manage Users, Groups, Application Roles, and Data Access

Manage Users
Manage Groups
Manage Application Roles
Manage Data Access through Security Assignments
Configure Permissions for Metadata and Front-End Objects
View Activity History
Manage Uploads and Downloads
Set Up Custom Security
Retaining and Deleting Images Using Retention Policies

Using the Console to Edit the Global Image Retention Policy
Using the Console to Create a New Custom Image Retention Policy to Override the Global Policy
Using the Console to Remove a Repository from a Custom Image Retention Policy
Using the Console to Add a Repository to a Custom Image Retention Policy
SDK for Ruby

Installing with yum
Services Supported
Contact Us
Security Zones
 learning videos
Scaling Cluster Resources


Scaling Big Data Service clusters includes adding Worker and Edge nodes, Block Storage, and updating autoscaling options.

Adding Nodes to a Cluster
Changing Kafka Profiles
Adding Block Storage to a Cluster
Managing Cluster Autoscaling Configurations
Quota Policy Syntax

Scope
Permissions and Nesting
Quota Evaluation and Precedence
Wildcards
Applying Free-form Tags and Defined Tags to Repositories, Images, and Image Signatures

Using the Console to Specify the Free-form Tags and Defined Tags to Apply to Repositories
Using the Console to Specify the Free-form Tags and Defined Tags to Apply to Images
Using the Console to Specify the Free-form Tags and Defined Tags to Apply to Image Signatures
Notes on the use of tags to control access to Repositories, Images, and Image Signatures
Work with Dashboards


You can use dashboards to visualize, explore, and analyze data in easy-to-interpret charts.

Dashboards are data visualization tools that gather real-time and historic data from various tiers of an application and display them in charts and widgets. They provide insight into the health and performance of your resources and help identify potential problems. You can either use the Oracle-defined dashboards and widgets for Management Agent or create custom dashboards to meet your specific requirements.

The Management Dashboard service is a visualization framework that provides a quick insight into the health and performance of your resources. The visual representation of information in a dashboard makes the information easy to interpret and helps identify outliers, isolate issues and take corrective action.

Topics:

Perform Dashboard Prerequisite Tasks
Access Dashboards
Oracle-defined Dashboards for Management Agent



For more information click here https://docs.oracle.com/en-us/iaas/management-agents/doc/work-dashboards.html
Adding a User to a Group

Using the Console
Creating a File System, Mount Target, and Export


On Compute Cloud@Customer, you can use this task flow to perform all the tasks that are required to create a file system and make it available for instances.

Task Flow
No.	Description	Links to Procedures
1.	

Ensure a mount target is available that's assigned to the VCN and subnet of your choice. Create a mount target if one doesn't exist.

Only one mount target can be created per VCN. A mount target can be used for many file systems.

Note – the file system and mount target must be in the same compartment when you create an export.

	

Creating a Mount Target


2.	

Create the file system.

	

Creating a File System


3.	

Create a file system export in the mount target.

	

Creating an Export for a File System


4.	

Enable Security Rules for File Storage.

	

Controlling Access to File Storage


5.	

Change NFS export options to control access to the file system.

	

Setting NFS Export Options

After the file system is exported, on the NFS client, perform these tasks to mount the file system:

(If needed) Install NFS client software.

Create a mount point.

On the client, mount the file system to the mount point.

On the client, add whatever files, directories, and data that you want in the file system.

For more information about mounting file systems, see Mounting File Systems on UNIX-based Instances.
VCN Flow Logs

Flow Log Contents
Flow Logs Tasks
Federating with Identity Providers

Overview
General Concepts
Experience for Federated Users
Required IAM Policy
Supported Identity Providers



For more information click here https://docs.oracle.com/en-us/iaas/Content/Identity/Concepts/federation.htm
Bring Your Own Image (BYOI)

Bringing Your Own Image
Limitations and Considerations
Launch Modes
Windows Images
Linux Images
Bringing Your Own Hypervisor Guest OS
Bringing Your Own KVM
Bringing Your Own Hyper-V
NTP Service
Opening Cloudera Manager


You can open Cloudera Manager in a browser window, but the cluster must first be configured to allow it.

 Note

Cloudera Manager is available only in clusters that use Cloudera Distribution including Hadoop.
Prerequisites

Cloudera Manager runs on the utility node of a cluster (or on the first utility node of a secure, highly-available (HA) cluster). Before you can access Cloudera Manager from a browser, an administrator must:

Make the node available to incoming connections from users. The node's private IP address can be mapped to a public IP address, which permits access from the public internet. Alternatively, the cluster can be set up to use a bastion host or Oracle FastConnect. See Connecting to Cluster Nodes with Private IP Addresses.

You can also create a load balancer to provide a secure front end for accessing services, including Clouder Manager. See Connecting to Services on a Cluster Using Load Balancer.

Open port 7183 on the node by configuring the ingress rules in the network security list. See Defining Security Rules.
Open Cloudera Manager from a Browser

To open Cloudera Manager (after the above prerequisites are satisfied):

Open a browser window.
Enter the following URL:

https://<ip_address_or_hostname>:7183
Troubleshooting DNS


Use troubleshooting information to identify and address common issues that can occur while working with service-name.

Common Private DNS Issues
Querying For a Private Zone After Creation Returns an NXDOMAIN Error Message or Public IP Address
Network Connectivity Issues With Private DNS Resolution Between VCNs or Between a VCN and an On-premises Network
Health Checks

SDKs and the CLI
Cloud Shell
Risk and Compliance

Goal
Roles
Implementation
Additional Considerations
Constraints and Blockers
Upgrading an App


Whenever a new version of an app that you got from Oracle Cloud Marketplace is available, the app provider usually sends you an email with upgrade information. The My Account application, which is a component of Cloud Portal that lets you manage your Oracle Cloud services, includes an Upgrade link next to each app that has a new version available. To upgrade an app, you must be an account administrator for the Oracle Cloud service instance that has the app.

To upgrade an app:

Go to the Oracle Cloud website.http://cloud.oracle.com
Click Sign In at the top of the page.
Click Sign In to My Account.
Enter your Oracle account user name and password, and then click Sign In.
Find the Oracle Cloud service that has the app you want to upgrade.
Click the service name to open the details page.
Click the PARTNER APPS tile to list all the partner apps that have been installed to the selected Oracle Cloud service.
Click Manage Apps.
Click Upgrade next to the app you want to upgrade. The Upgrade link is available only if a new version of the app is available.
Review the installation and version information displayed for the app.
Click Upgrade and follow the instructions for upgrading the app.

Be sure to check your email for messages about the upgrade. You can also go back to My Account to check the upgrade status, monitor the progress, confirm the version number changed, and view the upgrade history.
Securing OS Management

Security Responsibilities
Initial Security Tasks
Routine Security Tasks
IAM Policies
Software Sources
Oracle Autonomous Linux
Scheduling Patching
Auditing
Introduction

Management Agent Concepts
Workflow for Installing Management Agents



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
Private Endpoints

Prerequisites
Analyzing with the API


You can use the Document Understanding API to analyze documents.

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

APIs to Analyze Documents with Pretrained Models:
CreateProcessorJob
GetProcessorJob
CancelProcessorJob
Getting Started with Load Balancing

Before You Begin
Tutorial Overview
Add Two Subnets to Your VCN to Host Your Load Balancer
Create the Load Balancer
Create a Backend Set
Add Backends (Servers) to Your Backend Set
Create the Listener for Your Load Balancer
Update Load Balancer Security Lists and Allow Internet Traffic to the Listener
Verify Your Load Balancer
Update Rules to Limit Traffic to Backend Servers
Delete Your Load Balancer
Known Issues for OCI Functions


OCI Functions has no known issues.
Managing Build Pipelines


A build pipeline contains the stages that define the build process for successfully compiling, testing, and running software applications before deployment.

A stage is an action in the build pipeline. The DevOps service includes the following pre-defined stages that you can use in a build pipeline:

Managed Build: Build and test your software applications.
Deliver Artifacts: Store your software applications created from the Managed Build stage in the Oracle Cloud Infrastructure (OCI) Artifact Registry or OCI Container Registry repositories.
Trigger Deployment: Start a deployment pipeline to deploy the output from the build pipeline.
Wait: Pause a specific duration for testing the build pipeline.

You can add multiple stages to a pipeline. Stages can be added in a sequence or in parallel. You can remove any stage from the pipeline. When you do, the stage and its associated resources are deleted.
Oracle Integration Roles and Privileges


Roles define the privileges available to users and the tasks that they can perform. You can assign predefined roles to users to allow them to work with feature sets of Oracle Integration.

Topics:

What Users Can Do in the Integrations Design Section by Role

What Users Can Do in the Monitoring Section by Role

What Users Can Do in the Settings Section by Role

What Users Can Do in Processes by Role

What Users Can Do in Insight by Role

What Users Can Do in File Server by Role

What Users Can Do in Visual Builder by Role

What Users Can Do in B2B for Oracle Integration by Role



For more information click here https://docs.oracle.com/en-us/iaas/integration/doc/oracle-integration-roles-and-privileges.html
Kubernetes Versions and Container Engine for Kubernetes

New Versions of Kubernetes
Language Overview

Ways to Access Language
Regions and Availability Domains
Knowledge Content Reference


Topics:

Entity Types Modeled in Logging Analytics

Oracle-Defined Sources

OCI Parser Details

List of Non-Facetable Fields
Troubleshooting
 Network Configuration Issues for Kubernetes Clusters Using Network Path Analyzer



For more information click here https://docs.oracle.com/en-us/iaas/operations-insights/doc/operations-insights-troubleshooting.html

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

For more information click here https://docs.oracle.com/en-us/iaas/analytics-for-applications/doc/troubleshooting-fawag.html

For more information click here https://docs.oracle.com/en-us/iaas/jms/doc/troubleshooting.html

For more information click here https://docs.oracle.com/en-us/iaas/disaster-recovery/doc/troubleshooting.html

For more information click here https://docs.oracle.com/en-us/iaas/data-science/using/troubleshooting.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengtroubleshooting.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/applications-manager/troubleshooting-apps.htm
Troubleshooting Replication


This topic provides troubleshooting solutions for issues you might encounter using replication.
Creating and Managing Clusters

Planning a Cluster
Understand Instance Types and Shapes
Plan Your Cluster Layout, Shape, and Storage
Creating a Cluster
Creating a Secure and Highly Available Cluster
Define Security Rules
Establishing Connections to Nodes with Private IP Addresses
Adding Worker and Edge Nodes to a Cluster
Adding Block Storage to Worker Nodes
Adding Cloud SQL to a Cluster
Configuring an External Metastore
Creating an external metastore
Viewing metastore details
Testing the local or external metastore configuration
Updating API key for an external metastore
Activating the local metastore
Deleting an external metastore
Install Ext JS to Support Oozie UI
Oracle Enterprise Landing Zone v2 Architecture

Primary Objectives
Key Design Principles
Architecture Overview
Functional Modules
Tutorials


For step-by-step instructions and examples of using Terraform and Oracle Cloud Infrastructure, see the following tutorials:

Set Up the OCI Terraform Provider
Create a Compartment
Create a Compute Instance
Create a Virtual Cloud Network
Set Up a Simple Infrastructure
Create a Kubernetes Cluster
Set Up Resource Discovery
Create Scripts and State Files with Resource Discovery
HashiCorp Learn: Get Started with Oracle Cloud Infrastructure
For More Information

For more information, see the following resources:

Blog: Getting Started Using Terraform with OCI
Data Handling


Questions related to Document Understanding's data handling.

Does Oracle look at the files that I input to Document Understanding?

No, Oracle doesn’t use any of your content for any purpose except to provide you with the results.

Does Oracle use my data for improve the service?

No, Oracle doesn’t use the content you input to train and improve any AI services.

Are the images that I send to the Document Understanding API, the results, or other information about the request itself stored on Oracle servers?

Customer data privacy is respected. When you send an image to the Document Understanding 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?

ocal file storage and Oracle Object Storage are supported. Find out more about Oracle Object Storage from the Object Storage web page. If your data isn’t in Object Storage, consider using Data Integration to move your data to Object Storage. See the Data Integration web page for more information about it.
Managing OCI Database with PostgreSQL Configurations

Required IAM Policy
Disaster Recovery

DR Concepts
Choosing a DR Approach
Manage DR Orchestration with Full Stack DR
DR Design Considerations
Explore More



For more information click here https://docs.oracle.com/en-us/iaas/Content/File/Tasks/replication-disaster-recovery.htm#replication-disaster-recovery
Working with Pipeline Tasks


A pipeline task lets configure parameter values you want to use at runtime in a Data Integration pipeline.

The following pages describe how you can create, edit, and delete pipeline tasks:

Creating a Pipeline Task
Editing a Pipeline Task
Deleting a Pipeline Task

The following pages describe other management tasks that can be performed after a pipeline task is created:

Duplicating a Task
Moving a Task
Supported SQL*Plus and SQLcl Commands in SQL Worksheet

Supported SQL*Plus Commands
Supported SQLcl Commands
Model Deployment Policies

Authorize Access to Predict Endpoint Policy
Give Model Deployment Access to a Published Conda Bucket
Give Model Deployment Access to the Logging Service
Give Model Deployment Access to an Object Storage Bucket
Give Model Deployment Access to a Custom Container Using Resource Principal
Other Methods of Authentication and Authorization
Starting a Container Instance

Start a container instance.
Console
CLI
API
Open the navigation menu and click Developer Services. Under Containers & Artifacts, click Container Instances.
Under List Scope, select the compartment that contains the container instance.
Click the name of the container instance that you're interested in.

Click Start.

The container instance and all containers in it start.