1. Click the Setting link located at the resource's overview page. To clone your Autonomous Database from a backup, select the Backups link, and then click Create clone from backup.
2. Click the Overview link, and then click Create clone.

1. Select your Subscription. The current Subscription field is automatically selected. If you have any other subscriptions that your account can assess, those will be available in the drop-down list.
2. Select your Resource group from the drop-down list.
3. Enter a Name for your Oracle Autonomous Database instance clone.
4. Select the Region from the drop-down list. The current Region is automatically selected.
5. The current Source database name is automatically selected.
6. Select the Clone type from the drop-down list. If you want to create a new database with source database's data and metadata, select Full Clone. If you want to create a new database that includes all source database schema metadata but not the source database data, select Metadata Clone.
7. The Clone source is a drop-down list containing two existing options. To create a clone from a backup, select Clone from a backup. To create a clone of a running database, select Clone from database instance.
8. The Backup timestamp field is drop-down list that allows you to select the timestamp of the backup to clone.
9. The Backup time ended field provides the end time of the backup. This field is automatically changed based on your Backup timestamp selection.
10. Click the checkbox next to Latest backup timestamp, if you want to use the latest backup timestamp.
11. Select Next to continue.

1. Name - Enter a name of your choice used to save your connection.
2. Username - Enter ADMIN.
3. Password - Enter the password used when creating the Autonomous Database.
4. Role - Select default.
5. Save Password - Select the box if you security rules allow. If not, you will need to enter the PDB password every time you use this connection in SQL Developer.
6. Connection Type - Select Cloud Wallet.
7. Configuration File - Select Browse, and select the wallet you downloaded.
8. Select the Test button. The Status at the bottom of the connections list, should show as Success. If the connection is not a success, the wallet is out of date, or the ADB is not currently running.
9. Select the Save button.
10. Select the Connect button.

1. At the top of the page, select the Help (?) icon at the top-right of the menu bar.
2. On the right-side of the page, select the floating Support icon. NOTE: This icon can be moved by the user, and the precise horizontal location can vary from user to user.

1. Critical outage for critical production system outage or a critical business function is unavailable or unstable. You or an alternate contact must be available to work this issue 24x7 if needed.
2. Significant impairment for critical system or a business function experiencing severe loss of service. Operations can continue in a restricted manner. You or an alternate contact are available to work this issue during normal business hours.
3. Technical issue where functionality, errors, or a performance issue impact some operations.
4. General guidance where a product or service usage question, product or service setup, or documentation clarification is needed.

ALTER DATABASE PROPERTY SET ROUTE_OUTBOUND_CONNECTIONS =
    'PRIVATE_ENDPOINT';

1. Mount the NFS Share on the source database server using one of the following methods.
   Note
   
   You must mount the NFS share on both the source database host and the target Autonomous Database.
   1. As root:

      mkdir /nfstest mount -t nfs
          odaamigration.file.core.windows.net:/odaamigration/testmigration /nfstest -o
          vers=4,minorversion=1,sec=sys

   2. Using IP:

      mount -t nfs aa.an.fs.pe:/odaamigration/testmigration /nfstest -o
          vers=4,minorversion=1,sec=sys 

2. To make sure your Oracle user has access to NFS mount, run the following command.

   chown oracle:oinstall /nfstest

3. To create an empty file named test.txt in the /nfstest directory, run the following script as an Oracle user:

   touch /nfstest/test.txt

4. On the source PDB:

   create directory DATA_PUMP_DIR_NFS as '/nfstest';

1. From the Microsoft Azure portal, select Oracle Database@Azure application.
2. From the left menu, select Autonomous Database.
3. Click the Go to OCI link located on the resource's overview page.
4. From the OCI console, select Networking, and then click Virtual cloud networks.
5. From the Virtual Cloud Network Details page, select Details, and then click on the DNS Resolver.
6. From the Private resolver information, select the Default private view.
7. Click the Create zone button to create a new private zone. Enter Zone name as file.core.windows.net.
8. Select the previously created Zone name, and then click on the Manage records to create a record. Enter your preferred Name. From the drop-down list, select A-IPv4 address and set the TTL in seconds to 3600. Replace the e aa.an.fs.pe by the actual IP address, and then save the changes.
9. Update the Network Security Group in OCI to allow network traffic flow the VNet where the NFS private endpoint resides.

1. Use the DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE procedure to append an Access Control Entry (ACE) to the Access Control List of a network host. For more information, see APPEND_HOST_ACE Procedure.
2. Change the host parameter with your own host name.
3. Run the following SQL script on your database.

   exec
                 DBMS_NETWORK_ACL_ADMIN.APPEND_HOST_ACE(
                             host =>'odaamigration.file.core.windows.net', 
                             ace => xs$ace_type(privilege_list => xs$name_list('connect', 'resolve'),
                             principal_name => 'ADMIN',
                             principal_type =>xs_acl.ptype_db));
   

CREATE or replace DIRECTORY FSS_DIR AS 'fss';

1. Run the DBMS_CLOUD_ADMIN.ATTACH_FILE_SYSTEM procedure to attach a file system to a directory in your Autonomous Database.
   Note
   
   You must be logged in as the ADMIN user or have EXECUTE privilege on DBMS_CLOUD_ADMIN.
   The following attributes must be set to run this procedure.

   • file_system_name: Specify your file system name.
   • file_system_location: Specify your file system location.
   • directory_name: Specify your directory name for the attached file.
   • description:Specify a description for your task.
   • params: Specify your nfs_version.
     1. Use value 4 to specify NFSv4.

    exec
                 DBMS_CLOUD_ADMIN.ATTACH_FILE_SYSTEM(   
                          file_system_name => 'AZUREFILES', 
                          file_system_location =>'odaamigration.file.core.windows.net:/odaamigration/testmigration', 
                          directory_name => 'FSS_DIR',
                          description => 'Attach Azure Files',   
                          params => JSON_OBJECT('nfs_version' value 4) );
          
       

   For more information, see ATTACH_FILE_SYSTEM Procedure.

2. To retrieve information about the attached file system, run the following query.

   SELECT object_name FROM DBMS_CLOUD.LIST_FILES('FSS_DIR');