Jay-Rajput/oci_data huggingface dataset:
Exporting and Importing a Glossary


You can export and import glossaries created from one Data Catalog instance to another.

The glossary file is exported to a bucket in Object Storage and you can download this exported file in the Microsoft Excel file format.

Exported Excel file column headers
Creating your own import Excel file
 Note



You can get started with creating your own import file using this Excel template file. The Excel sheet named Metadata has information on creating the import file.

 Note


When exporting or importing a glossary, all the data is preserved. Some rich text formatting may be modified or lost.
Format loss details
 Expand All Expandable Areas
Mounting File Systems
 From an Instance
Mount Command Samples
Required IAM Service Policy
Getting Started with Email Delivery


Configure Oracle Cloud Infrastructure Email Delivery to use the functionalities of the Email Delivery service. You can configure using the Console, REST API, SDKs, CLI, or Terraform.

To get started with Email Delivery using the console, complete the following steps:

Create a group
Create a user
Add a user to a group
Create user permissions
Create SMTP credentials
Create email domain
Enable logs for troubleshooting
Configure SPF
Configure DKIM
Create an approved sender
Configure SMTP connection
Send an email
Validate email delivery
Creating a Public DNS Zone


Create a public DNS zone to hold the trusted DNS records that reside on Oracle Cloud Infrastructure’s nameservers.

You can create public zones with publicly available domain names reachable on the internet. For more information, see Public DNS.

Create a primary zone to manage zone records. To pull records for the zone from an external primary server, create a secondary zone.
Console
CLI
API
Open the navigation menu and click Networking. Under DNS management, click Zones.
On the Public zones tab, click Create zone.
On the Create public zone panel, choose the method to use to create the zone, Manual or Import.
If you chose the manual method, enter the zone information:
Zone type: Select Primary.
Zone name: Enter a descriptive name for the zone. Avoid entering confidential information.
Create in compartment: Specify the compartment to create the zone in. Be sure you have permission to work in the compartment.
If you chose the import method, then drag, select, or paste a valid zone file into the panel.

The zone is imported as a primary zone.

(Optional) Configure one or more secondary servers to receive zone transfers.
Click Add additional server IP.
Enter a valid IPv4 or IPv6 address.
Select a TSIG key.
For more information, see Secondary DNS and Adding Downstream Servers to a Primary DNS Zone.
(Optional) Click Show Advanced Options: to apply tags to the zone.
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 (you can apply tags later) or ask an administrator.
Click Create.

The zone is created and published with the necessary SOA and NS records, and its details page is displayed.

Next, you can delegate the public zone with a registrar or add records to the zone.
Oracle Cloud Infrastructure US Government Cloud with FedRAMP Authorization

Authorizations
Regions
Console Sign-in URLs
US Government Cloud with FedRAMP Authorization API Reference and Endpoints
Oracle YUM Repo Endpoints
SMTP Authentication and Connection Endpoints
SPF Record Syntax
Services Not Supported in US Government Cloud with FedRAMP Authorization
Additional Information for US Government Cloud with FedRAMP Authorization Customers
Known Issues for Managed Access


Managed Access has no known issues.
Editing Attribute Name and Custom Properties


Modify the business name and custom properties for an attribute.

Console
CLI
API
On the Home tab, click Data Entities to access the Data Entities tab.
In the Data Entities list, select the entity for which you want to edit the attributes.
In the Data Entities details page, click Attributes.
In the Attributes list, select the row that you want to edit and click the Edit icon.
Make the required edits to the business name and custom properties.
 Note

A custom property appears in the Attribute list table only if you have enabled the Quick edit check box while creating the custom property. You can configure up to three custom properties for quick edit option. For more information, see Creating Custom Properties.
Click Save.
 Note

Alternatively, you can edit the attribute custom properties the following way:
Click + from tabs and select Attributes.
In the Attributes list, click the business name link that you want to edit. The attribute details tab opens.
Click the Edit link from the Custom Properties section. The Edit Custom Properties panel opens as an overlay.
Make the required edits to the attribute custom properties.
Click Save Changes.

A notification displays indicating that the changes were saved successfully and the Edit Custom Properties panel closes.
Managing Lifecycle Environments

Promoting a Versioned Custom Software Source to a Lifecycle Stage
Detaching an Instance from a Lifecycle Environment
Attaching an Instance to a Lifecycle Environment
Editing a Lifecycle Stage Name
Editing the Basic Details of a Lifecycle Environment
Deleting a Lifecycle Environment
Viewing Lifecycle Environment Information
Listing Lifecycle Environments
Listing the Stages for a Lifecycle Environment
Viewing a Lifecycle Environment's Details
Listing Jobs Associated with a Lifecycle Environment
Viewing Reports for a Lifecycle Environment
Creating Jobs


Create a job to automate the detection of anomalies in Anomaly Detection.

Console
CLI
API

Prerequisites:

You must have a project that contains a trained model for use in an asynchronous anomaly detection job.

Open the navigation menu and click Analytics & AI. Under AI Services, click Anomaly Detection.
In the left-side navigation menu, click Projects.
Select the compartment that contains the project that you want to create a job in.
Click the name of the project.

The project details page opens.

Under Details, click Jobs.
Click Create job.
(Optional) Enter a unique name (255 character limit) for the resource. If you don't provide a name, one is automatically generated.

For example:

aianomalydetection<resource>20230825155844

(Optional) Enter a description (400 character limit) for the resource.
Select the model that you want to run this job in.
(Optional) Select the amount of sensitivity for the anomaly detection to use from 0 to 1.
Select the input request type that you want to use for the job.
Inline:

Drag a JSON or CSV file into the File box, or use Select file to locate and select it from a local drive.

Object store:

Select the Object Storage bucket that contains the detection data file, and then select the file you that you want to use for this job. Only CSV files are supported.

You can use multiple input buckets and detection data files by clicking Additional input bucket and making further selections.

Select an Object Storage output bucket to store the output files in.

The namespace shows you the tenancy that the job is being created in.

(Optional) Enter a prefix to use to easily identify the results.

For example, if myModel is the prefix, then the result file is myModel/results-file.json.

Click Create job.

The asynchronous job status is initially Accepted until the job starts running; then it's In Progress. When the job finishes the status changes to Succeeded. The time it takes to run the job depends on the size of the detection datasets.

Click the completed asynchronous job to view its details and review the job results.

The anomaly detection results file is saved in a separate folder in the selected Object Storage output bucket. The file name uses the <model-OCID>/<output_bucket_name> naming convention.

<model-OCID> is the OCID of the Anomaly Detection model.

<output_bucket_name> is the Object Storage bucket name.

The anomaly detection results file name is the same as the detection dataset file name suffixed with -results.
Moving a Vulnerability Audit


Move a vulnerability audit from one compartment to another.

If you attempt to move a vulnerability audit to a compartment for which you don't have authorization, an error message appears.

Before moving a vulnerability audit, contact the administrator to get the required authorization.

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 that you want to move.
In the Vulnerability audit details page, click Move resource.
In the Move resource dialog box, select the destination compartment.
Click Move resource.
Checking Your Expenses and Usage

Billing and Cost Management Required IAM Policy
Console Dashboards Integration
Working with Costs Analysis Tools
Securing Container Engine for Kubernetes

Multi-Tenant Clusters
Encrypt Secrets at Rest in Etcd
Role-Based Access Control (RBAC)
Cluster Security
Node Pool Security
Network Security
Workload Security Best Practices
Disabling the Tiller Add-on
Disabling the Kubernetes Dashboard Add-on
Data Catalog Events

Event Types for Harvest Jobs
Event Type for Logical Data Entities
Event Type for Custom Property Value Update
Additional Resources
Managing Bastions

Required IAM Policy
Creating an API Deployment Specification

Using the Console to Create an API Deployment Specification
Using a JSON Editor to Create an API Deployment Specification in a Separate JSON File
Using an API Description File to Create an API Deployment Specification
Example API Deployment Specification with Multiple Back Ends
Data Safe

Register a Target Database
Assess Database Security
Assess User Security
Discover Sensitive Data
Mask Sensitive Data
Audit Database Activity
Generate Alerts
Related Content
Videos
Common Tasks
Known Issues for Console Dashboards


The Console Dashboards service has no known issues.
Physical Architecture Concepts

Regions
Availability Domains
Fault Domains
Realms
Overview of Artifact Registry

Accessing the Artifact Registry Service
Regions and Availability Domains
Service Limits for Artifact Registry
Integration with the DevOps Service
Resource Identifiers
Networking

Support
Get help and contact support
Create a service request
Ask the community



For more information click here https://docs.oracle.com/en-us/iaas/mysql-database/doc/networking.html
Using the DNS Management Overview to Manage DNS Services

Manage DNS Services Section
Service Health and Documentation Section
Supporting Services Section
Getting Started Section
Cloud Guard
 learning videos
Networking Metrics


You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring and Notifications.

There are multiple Monitoring service metric namespaces related to networking resources.

For instance connectivity:

oci_vcn: Metrics related to VNICs . See VNIC Metrics.

For cloud connectivity:

oci_fastconnect: Metrics related to FastConnect . See FastConnect Metrics.
oci_vpn: Metrics related to an IPSec connection . See Site-to-Site VPN Metrics.
oci_service_gateway: Metrics related to a service gateway.  See Service Gateway Metrics.
oci_nat_gateway: Metrics related to a NAT gateway  See NAT Gateway Metrics.
Known Issues

Files required for each application should be in the same region where the application is created.
Spark UI errors



For more information click here https://docs.oracle.com/en-us/iaas/osmh/doc/known-issues.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/control-center/known-issues.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/media-services/mediaflow/known-issues-mediaservices.htm

For more information click here https://docs.oracle.com/en-us/iaas/language/using/known-issues.htm

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

For more information click here https://docs.oracle.com/en-us/iaas/Content/DNS/Tasks/known-issues.htm

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

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

For more information click here https://docs.oracle.com/en-us/iaas/data-flow/using/known-issues.htm

For more information click here https://docs.oracle.com/en-us/iaas/Content/anomaly/using/known-issues-root.htm
Editing an Artifact


Update the reference information of an artifact.

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

 Note

An artifact cannot be updated if it's referenced in more than 20 deployment pipelines.
Console
CLI
API
Open the navigation menu and click Developer Services. Under DevOps, click Projects.
On the DevOps Projects page, select the project for which you want to update an artifact.
On the details page of the project, from the left side, click Artifact.
On the Artifacts page, click the artifact that you want to update.
On the details page of the artifact, click Edit.
In the Edit artifact panel, update the details, as required. You can modify artifact name and change artifact type and source.
Click Save.
Connecting to a Managed SSH Session

Connect to a Compute Instance using a Managed SSH Session
Creating a Project


Create a DevOps project to group the resources required to implement a CI/CD workflow.

Each service in Oracle Cloud Infrastructure (OCI) integrates with Identity and Access Management (IAM) for authentication and authorization, for all interfaces (the Console, SDK and CLI, and REST API). Before you begin using the DevOps service, you must create policies to control who has access to DevOps, and the type of access for each group of users.

For details about writing policies for the DevOps service and policy examples, see DevOps IAM Policies.

You must create a topic  for project notification. See Creating a Topic.

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.
From the left-side menu, select a compartment that you have permission to work in.
For more information, see Authentication and Authorization.
On the DevOps Projects page, click Create devops project.
On the Create new devops project panel, enter the following information:
Enter a name for the project.
(Optional) Enter a description.
To set up project notifications, click Select Topic.
 Note

Project notifications keep you apprised of important events and the latest project status. They also alert you if you need to take any necessary action such as approving a workflow. You must create a topic  and add subscription  to the topic. See Creating a Topic and Creating a Subscription.
For selecting topic using topic name, select a Compartment and an associated Topic.
For selecting topic using Oracle Cloud Identifier (OCID), enter OCID of the topic.
(Optional) To add tags to the project, 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 DevOps project.

The DevOps project is created successfully. You can configure required resources such as code repositories, build pipelines, artifact references, target environments, and deployment pipelines.

 Note

To run build and deployment pipelines, you must enable logging for the project. To enable logging, see DevOps Logs.



For more information click here https://docs.oracle.com/en-us/iaas/Content/devops/using/create_project.htm#create_a_project
Analyze Database Resources

Typical Goals
Database Capacity Planning
Analyze Database CPU Usage
Analyze Database Storage Usage
Analyze Database Memory Usage
Analyze Database I/O Activity
Data Science Tutorials
 show you how to complete tasks with step-by-step instructions.

Manually Configuring a Data Science Tenancy

Copying a Conda Environment to Another Region

Scheduling Data Science Job Runs
Viewing Job Details


View the details of a job.

Console
CLI
API
On the Home tab of the instance for which you want to view the jobs, click Jobs.
On the Jobs page, click the job for which you want to view the details.

On the job details page, you can view the following details:

Details of the data asset that was harvested, such as the connection used, if incremental harvest was enabled, and the data entities selected for harvest. Click the number link for Data Entities Selected to view all the data entities selected.
A list of all Job Runs for the selected job. You can locate a specific job by the date and timestamp used to display the job runs. Click each timestamp to view details specific to that run.

Details for each job run, which is listed in three different sections:

Summary: Displays general job information such as job status and the date and time the job was created, started, and completed. You also view the job statistics such as Data Entities Harvested, Unrecognized Files Harvested, Harvest Errors, and Time to Harvest (seconds).

Schedule: Displays scheduling information for the job. The Schedule section displays only if you have created a schedule for a job.

Log Messages: Displays all timestamped logs for the job. The Message column displays the log message. Some log messages are long. To view the complete log message, click the Actions menu for the job log and select View Details. The complete log message opens in a Log Message panel as an overlay.

Additionally, from the job details tab, you can run, schedule, or delete the job.
API Reference and Appendices


This section covers general SDK concepts and references.

REST APIs
Client-Side Encryption - Discusses how client-side encyption works for the Oracle Cloud Infrastructure SDK for Python and the SDK for Java.
Deploying a Sample Nginx App on a Cluster Using Kubectl


Find out how to use kubectl to deploy an Nginx app on a cluster you've created using Container Engine for Kubernetes (OKE).

Having created a Kubernetes cluster using Container Engine for Kubernetes, you'll typically want to try it out by deploying an application on the nodes in the cluster. For convenience, the Quick Start tab (available from the Cluster page) makes it easy to view and copy the commands to:

set up access to the cluster
download and deploy a sample Nginx application using the Kubernetes command line tool kubectl from the instructions in a manifest file

To deploy the sample nginx application:

If you haven't already done so, follow the steps to set up the cluster's kubeconfig configuration file and (if necessary) set the KUBECONFIG environment variable to point to the file. Note that you must set up your own kubeconfig file. You cannot access a cluster using a kubeconfig file that a different user set up. See Setting Up Cluster Access.

In a terminal window, deploy the sample Nginx application by entering:

Command
Copy
Try It
kubectl create -f https://k8s.io/examples/application/deployment.yaml
 Tip

If the command fails to connect to https://k8s.io/examples/application/deployment.yaml , go to the url in a browser and download the manifest file deployment.yaml to a local directory. Repeat the kubectl create command and specify the local location of the deployment.yaml file.
Confirm that the sample application has been deployed successfully by entering:
Command
Copy
Try It
kubectl get pods

You can see the Nginx sample application has been deployed as two pods, on two nodes in the cluster.
Logging Overview

How Logging Works
Connector Hub Integration
Logging Workshop
Logging APIs
Logging Concepts
Log Encryption
Resource Identifiers
Ways to Access Oracle Cloud Infrastructure
Authentication and Authorization
Adding OracleDB for Azure Users in Azure After Completing Your Sign Up

Instructions
Creating a Resource


The Oracle Database Service for Azure (OracleDB for Azure) Portal focuses on primary Oracle Databases. There are other resources that are created through the Create a resource blade.

Select Create a resource from OracleDB for Azure Portal.

Figure 1-2 OracleDB for Azure Portal







From the list of available resources, shown in the image, select the resource you wish to create.

Figure 1-3 Create a resource Blade







The Oracle Autonomous Database, Oracle Exadata Database, Oracle Base Database, and Oracle MySQL HeatWave Cluster icons on OracleDB for Azure use a similar UI with slightly different options. There are Create links for those objects on those blades.
The Oracle Exadata System Create flow is a combination of the Oracle Exadata Infrastructure, Oracle Exadata VM Cluster, and Oracle Exadata Database Create flows.
You can individually create an Oracle Exadata Infrastructure, Oracle Exadata VM Cluster, or Oracle Exadata Database.
Oracle Exadata VM Clusters require Oracle Exadata Infrastructure.
Oracle Exadata Databases require an Oracle Exadata VM Cluster.
The MySQL HeatWave Create flow provisions a Oracle MySQL HeatWave Cluster.
Using Application Dependency Management with the OCI DevOps Service


This section describes the steps to set up Oracle Cloud Infrastructure for Application Dependency Management.

Before you begin, review the prerequisites and the overview of the steps.

You have created a compartment for your DevOps project. (See Setting up Your Tenancy.)

You have created a DevOps project. (See Creating a Project.)

You have created a Build Pipeline. (See Creating a Build Pipeline.)

Overview

Sign in to Oracle Cloud Infrastructure.
Create a user group for your users.
Create a new Knowledge Base.
Create policies for your user group to access and manage knowledge bases in the compartment you created.

Steps

Sign in to the Oracle Cloud Console as an administrator using the credentials provided by Oracle.

Create a user group.
In the Oracle Cloud Console, open the navigation menu and click Identity & Security. Under Identity, click Groups.
Click Create Group.
In the Create Group dialog box, enter a name for the group (for example, ADM_MANAGERS), and a description.
Click Create.
For more information, see Managing Groups.

Create a knowledge base to contain the results of ADM. (See Creating a Knowledge Base.)

You can use the same compartment as the one you use for your DevOps project.

Create policies for the user group to access and manage knowledge bases.

A policy allows members of a user group to access and manage OCI resources.
In the Oracle Cloud Console, open the navigation menu and click Identity & Security. Under Identity, click Policies.
Click Create Policy.
In the Create Policy dialog box, enter a name for the policy (for example, ADM_Policy), and a description.
Select the root compartment for your tenancy from the drop-down list.
Click Show manual editor.
In the text box, enter the following statement:
Copy
Allow group ADM_MANAGERS to manage adm-knowledge-bases-family in compartment <KB_Compartment>

Where <KB_Compartment> is the name of the compartment that contains the knowledge base that you created in step 3.

Click Create.
I don’t have an Oracle Account


With an Oracle account, you can get apps and services from Oracle Cloud Marketplace. In addition, an Oracle account gives you access to Oracle online applications, support, events, communities, and more.

To register for a free Oracle account:

Go to the Oracle Cloud Marketplace website.http://cloud.oracle.com/marketplace
Click Sign In at the top of the page.
Click Create Account.
Follow the instructions.