To connect to a MySQL DB system from an OCI Cloud Shell session when the VCN is not configured with VCN peering, VPN access, or FastConnect, the following must be true:

A.You must attach the Cloud Shell session to a VCN subnet that can connect to the MySQL DB system: The Cloud Shell must be in the same network or have a route to the network containing the MySQL DB system. C.The MySQL DB system subnet must be in theCloud Shell tenancy home region: Cloud Shell sessions operate within the OCI home region, so the target MySQL DB system must be accessible from within the same region.

Before deleting a DB system in Oracle Cloud Infrastructure (OCI), you mustdisable delete protection if it is enabled(Answer C). Delete protection is a feature that prevents accidental deletion of DB systems. If enabled, it must be turned off before the DB system can be deleted.

Steps:

Navigate to the DB system in the OCI Console.

Check if delete protection is enabled.

If enabled, disable it by updating the DB system settings.

Proceed with deleting the DB system.

References:

OCI Console Documentation on DB System Management

MySQL Database Service Documentation

To prepare data for a new DB system with data import in OCI, you shouldexport the data into an Object Storage bucket with a MySQL Shell dump utility(Answer B). This method allows you to store the data in a scalable and durable object storage service before importing it into the new DB system.

Steps:

Use MySQL Shell dump utility to export the data.

Save the export files to an Object Storage bucket in OCI.

Import the data from the Object Storage bucket into the new DB system.

References:

MySQL Shell Documentation

OCI Object Storage Documentation

A.Reduce query latency: By distributing read queries across multiple replicas, the load on the primary instance is reduced, which can decrease query latency. D.Scale read queries: Read replicas allow scaling of read operations by providing additional instances to handle read queries, improving overall performance and throughput.

To migrate an on-premises MySQL database to a MySQL DB system on OCI with the least amount of application downtime,use inbound replication to synchronize the MySQL database transactions to the DB system(Answer C).

Inbound Replication: This method involves setting up replication from your on-premises MySQL database to the MySQL DB system in OCI. This ensures that all changes and transactions are continuously replicated, keeping the DB system up to date with minimal downtime.

Steps to Implement:

Set up the MySQL DB system in OCI.

Configure the on-premises MySQL database as the master and the OCI DB system as the slave.

Start the replication process to keep the DB system synchronized with the on-premises database.

When ready, switch the application to the DB system with minimal downtime as the data is already synchronized.

References:

MySQL Replication Documentation

OCI MySQL Database Service Replication

To enable high availability for a stand-alone DB system, the following conditions are required:

The DB system must be active(Answer D): The DB system needs to be in an active state to enable high availability features.

The DB system automatic backup must be enabled(Answer E): Automatic backups must be enabled to ensure data protection and facilitate failover operations.

Steps:

Ensure the DB system is running and operational.

Enable automatic backups through the OCI Console or API.

References:

MySQL High Availability Documentation

Automatic Backups Documentation

When exporting data to Object Storage withMySQL Shell util.dumpInstance,you must specifyociParManifest: true(Answer B). This option creates a pre-authenticated request (PAR) manifest file, which allows for secure access and upload to Object Storage without requiring direct credentials.

References:

MySQL Shell Documentation

OCI Object Storage Documentation