You can access the Autonomous Database Free Container Image from a repository and run it in your local environment.

Autonomous Database provides a fully managed Oracle Database that is available on Oracle Cloud Infrastructure. On Oracle Cloud Infrastructure, you perform lifecycle management operations and run Autonomous Database using the Oracle Cloud Infrastructure Console and you connect to your database through the public internet or through a private network that you set up (depending on your network configuration and security needs).

The Autonomous Database Free Container Image provides an alternative to run Autonomous Database in a container in your own environment, without requiring access to Oracle Cloud Infrastructure Console or to the internet. When you run Autonomous Database in a container, the container provides a local, isolated environment with additional options for development, testing, and exploration of Oracle Autonomous Database features.

• Autonomous Database Free Container Image License
  Describes licensing for Autonomous Database Free Container Image.
• Autonomous Database Free Container Image Features
  The Autonomous Database Free Container Image provides many of the features available with Autonomous Database Serverless.
• Autonomous Database Free Container Image Recommendations and Restrictions
  Describes requirements and restrictions for Free Container Image.

There are multiple locations where you can obtain Autonomous Database Free Container Image, including: Oracle Cloud Infrastructure Registry (Container Registry) and GitHub.

1. Start a podman virtual machine.
   For example:

   podman machine init 
   podman machine set --cpus 4 --memory 8192 
   podman machine start 

2. Obtain the Free Container Image.

   Oracle Cloud Infrastructure Registry:

   For example, use podman command to pull the latest Free Container Image image:

   podman pull container-registry.oracle.com/database/adb-free:latest-23ai

   Note
   
   

   Oracle Autonomous Database Serverless also supports 19c container images.

   • For 19c container image names, specify latest tag as your database version.

   • In the above example, to pull the Autonomous Database Free Container Image 19c , use the following command in the image name tag:

     podman pull container-registry.oracle.com/database/adb-free:latest

   Throughout the document, the image name tag refers to the latest-23ai version.

   For more details and additional information, search for "Oracle Autonomous Database Free" on Oracle Cloud Infrastructure Registry.

   GitHub Packages:

   For example, use podman command to pull the Free Container Image from: GitHub Packages:

   podman pull ghcr.io/oracle/adb-free:latest-23ai

3. Verify the image.

   For example:

   podman images container-registry.oracle.com/database/adb-free:latest-23ai

After you download Autonomous Database Free Container Image, you can start the image in a container.

1. Start a container to run Free Container Image.

   For example, with podman:

   podman run -d \
   -p 1521:1522 \
   -p 1522:1522 \
   -p 8443:8443 \
   -p 27017:27017 \
   -e WORKLOAD_TYPE='ATP' \
   -e WALLET_PASSWORD=*** \
   -e ADMIN_PASSWORD=*** \
   --cap-add SYS_ADMIN \
   --device /dev/fuse \
   --name adb-free \
   container-registry.oracle.com/database/adb-free:latest-23ai

   Command notes:

   • Autonomous Database Serverless also supports 19c container images.

     • For 19c container image names, specify latest tag as your database version.

     • In the above example, to start a container to run the Autonomous Database Free Container Image 19c, use the following command in the image name tag:

       container-registry.oracle.com/database/adb-free:latest

   • Throughout the document, the image name tag refers to the latest-23ai version.

   • The WORKLOAD_TYPE can be either ATP or ADW. The default value is ATP.

   • By default, the database is named either MYATP or MYADW, depending on the passed WORKLOAD_TYPE value. Optionally, if you want a different database name than the default, you can set the DATABASE_NAME parameter. The database name can contain only alphanumeric characters.

   • On container startup, the corresponding MY<WORKLOAD_TYPE>.pdb is downloaded and plugged in from a public Object Storage bucket.

   • The wallet is generated using the provided WALLET_PASSWORD.

   • It is necessary to change the ADMIN_PASSWORD upon initial login.

   • Ensure you check the following requirements when you create or modify the ADMIN_PASSWORD:
     • The password must be between 12 and 30 characters long and must include at least one uppercase letter, one lowercase letter, and one numeric character.
     • The password cannot contain the username.
   • Ensure you check the following requirements when you create or modify the WALLET_PASSWORD:
     • The password must be between 8 and 30 characters long and include alphabetic characters combined with numeric characters or special characters.

   • For an OFS mount, the container starts with SYS_ADMIN capability. Also, virtual device /dev/fuse must be accessible.

   • This -p options specify that the following ports are forwarded to the container process:

     Port	Description
     1521	TLS
     1522	mTLS
     8443	HTTPS port for ORDS / APEX and Database Actions
     27017	Mongo API

   If you are behind a corporate proxy, include -e options to specify environment variables for proxies. For example, with podman:

   podman run -d \
   -p 1521:1522 \
   -p 1522:1522 \
   -p 8443:8443 \
   -p 27017:27017 \
   -e WORKLOAD_TYPE='ATP' \
   -e WALLET_PASSWORD=*** \
   -e ADMIN_PASSWORD=*** \
   -e http_proxy=http://example-corp-proxy.com:80/ \
   -e https_proxy=http://example-corp-proxy.com:80/ \
   -e no_proxy=localhost,127.0.0.1 \
   -e HTTP_PROXY=http://example-corp-proxy.com:80/  \
   -e HTTPS_PROXY=http://example-corp-proxy.com:80/  \
   -e NO_PROXY=localhost,127.0.0.1 \
   --cap-add SYS_ADMIN \
   --device /dev/fuse \
   --name adb-free \
   container-registry.oracle.com/database/adb-free:latest-23ai

The adb-cli command-line utility can be used to perform database operations after the container is up and running.

alias adb-cli="podman exec <container_name> adb-cli"

adb-cli --help 
Usage: adb-cli [OPTIONS] COMMAND [ARGS]... 
    ADB-S Command Line Interface (CLI) to perform container-runtime database operations 
Options: 
    -v, --version Show the version and exit. 
    --help Show this message and exit. 
Commands: 
    add-database 
    change-password 

adb-cli add-database --workload-type "ATP" --admin-password "Welcome_MY_ATP_1234" 

adb-cli change-password --database-name "MYATP" 
    --old-password "Welcome_MY_ATP_1234" --new-password "Welcome_12345"

When the Free Container Image is running in a container, you can connect to an Autonomous Database instance.

To connect to an Autonomous Database instance running in a container, you can either setup the wallet and connect or use a TLS walletless connection.

• Connect to ORDS, APEX, or Database Actions from an Autonomous Database Container Image
  The container hostname is used to generate self-signed SSL certificates to serve HTTPS traffic on port 8443. Oracle APEX and Database Actions can be accessed using the container host (or simply localhost).
• Available TNS Aliases for Connecting to an Autonomous Database Container Image
  You can use any one of the following aliases to connect to an Autonomous Database Container Image.
• Connect to an Autonomous Database Container Image with a Wallet
  Describes the steps to connect to an Autonomous Database container image with a Wallet.
• Connect to an Autonomous Database Container Image without a Wallet (TLS)
  Describes the steps to connect to an Autonomous Database container image without a Wallet (TLS).

1. Create a podman volume.

   For example:

   podman volume create adb_container_volume

2. Verify the volume mountpoint.

   The mountpoint is a podman managed directory location.

   podman inspect adb_container_volume
    
   [
        {
             "Name": "adb_container_volume",
             "Driver": "local",
             "Mountpoint": "/share/containers/storage/volumes/adb_container_volume/_data",
             "CreatedAt": "2023-09-11T21:23:34.305877073Z",
             "Labels": {},
             "Scope": "local",
             "Options": {},
             "MountCount": 0,
             "NeedsCopyUp": true,
             "NeedsChown": true
        }
   ]

3. Start the source container, mounting the volume to /u01/data in the container.

   For example:

   podman run -d \
   -p 1521:1522 \
   -p 1522:1522 \
   -p 8443:8443 \
   -p 27017:27017 \
   -e WORKLOAD_TYPE='ATP' \
   -e WALLET_PASSWORD=*** \
   -e ADMIN_PASSWORD=*** \
   --cap-add SYS_ADMIN \
   --device /dev/fuse \
   --name source_adb_container \
   --volume adb_container_volume:/u01/data \
   container-registry.oracle.com/database/adb-free:latest-23ai

   Note
   
   

   Autonomous Database Serverless also supports 19c container images.

   • For 19c container image names, specify latest tag as your database version.

   • In the above example, to start the Autonomous Database Free Container Image 19c , use the following command in the image name tag:

     container-registry.oracle.com/database/adb-free:latest

   Throughout the document, the image name tag refers to the latest-23ai version.

4. This example assumes you have previously created your data in schema, app_user.
5. Export the data from app_user's schema to the container volume.
   1. Connect as ADMIN and create ORA_EXP_DIR directory pointing to /u01/data.

      sqlplus admin/**************@myadw_high
       
      SQL> exec DBMS_CLOUD_CONTAINER_ADMIN.create_export_directory('/u01/data');
      

      SQL> select directory_path from dba_directories where directory_name='ORA_EXP_DIR';
      
      DIRECTORY_PATH
      --------------------------------------------------------------------------------
      /u01/data

   2. Run the export job in schema mode and for both ADMIN and APP_USER schemas.

      SET scan off
      SET serveroutput ON
      SET escape off
        
      DECLARE
          h1 NUMBER;
          s VARCHAR2(1000):=NULL;
          errorvarchar VARCHAR2(100):= 'ERROR';
          tryGetStatus NUMBER := 0;
          success_with_info EXCEPTION;
          PRAGMA EXCEPTION_INIT(success_with_info, -31627);
      BEGIN
          h1 := dbms_datapump.OPEN(operation => 'EXPORT', job_mode => 'SCHEMA', job_name => 'EXPORT_MY_ADW_4', version => 'COMPATIBLE');
          tryGetStatus := 1;
          dbms_datapump.add_file(handle => h1, filename => 'EXPORT_MY_ADW.LOG', directory => 'ORA_EXP_DIR', filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE);
          dbms_datapump.metadata_filter(handle => h1, name => 'SCHEMA_EXPR', VALUE => 'IN(''ADMIN'', ''APP_USER'')');
          dbms_datapump.add_file(handle => h1, filename => 'MY_ADW_%L.DMP', directory => 'ORA_EXP_DIR', filesize => '500M',  filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE);
          dbms_datapump.start_job(handle => h1, skip_current => 0, abort_step => 0);
          dbms_datapump.detach(handle => h1);
          errorvarchar := 'NO_ERROR';
      EXCEPTION
          WHEN OTHERS THEN
          BEGIN
              IF ((errorvarchar = 'ERROR')AND(tryGetStatus=1)) THEN
                  DBMS_DATAPUMP.DETACH(h1);
              END IF;
          EXCEPTION
          WHEN OTHERS THEN
              NULL;
          END;
          RAISE;
      END;
      /

6. Verify the export.

   List the files in the container /u01/data.

   podman exec -it source_adb_container bash
   cd /u01/data

   Verify the export log (export log), check for any errors and successful completion.

7. Stop and remove the source container.

   podman stop source_adb_container
   podman rm source_adb_container

   Note
   
   The adb_container_volume will live across container restarts and removals
8. Start a destination container mounting the same volume to /u01/data in the container.

   podman run -d \
   -p 1521:1522 \
   -p 1522:1522 \
   -p 8443:8443 \
   -p 27017:27017 \
   -e WORKLOAD_TYPE='ATP' \
   -e WALLET_PASSWORD=*** \
   -e ADMIN_PASSWORD=*** \
   --cap-add SYS_ADMIN \
   --device /dev/fuse \
   --name dest_adb_container \
   --volume adb_container_volume:/u01/data \
   container-registry.oracle.com/database/adb-free:latest-23ai

9. Import data in destination container.

   Connect as ADMIN and create ORA_EXP_DIR directory pointing to /u01/data.

   SQL> exec DBMS_CLOUD_CONTAINER_ADMIN.create_export_directory('/u01/data');
    
   PL/SQL procedure successfully completed.
    
   SQL> select directory_path from dba_directories where directory_name='ORA_EXP_DIR';
    
   DIRECTORY_PATH
   --------------------------------------------------------------------------------
   /u01/data

10. Run the import PL/SQL commands.

    SET scan off
    SET serveroutput ON
    SET escape off
      
    DECLARE
        h1 NUMBER;
        s VARCHAR2(1000):=NULL;
        errorvarchar VARCHAR2(100):= 'ERROR';
        tryGetStatus NUMBER := 0;
        success_with_info EXCEPTION;
        PRAGMA EXCEPTION_INIT(success_with_info, -31627);
    BEGIN
        h1 := dbms_datapump.OPEN(operation => 'IMPORT', job_mode => 'SCHEMA', job_name => 'IMPORT_MY_ADW_4', version => 'COMPATIBLE');
        tryGetStatus := 1;
        dbms_datapump.add_file(handle => h1, filename => 'IMPORT_MY_ADW.LOG', directory => 'ORA_EXP_DIR', filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE);
        dbms_datapump.metadata_filter(handle => h1, name => 'SCHEMA_EXPR', VALUE => 'IN(''ADMIN'', ''APP_USER'')');
        dbms_datapump.add_file(handle => h1, filename => 'MY_ADW_%L.DMP', directory => 'ORA_EXP_DIR', filesize => '500M',  filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE);
        dbms_datapump.start_job(handle => h1, skip_current => 0, abort_step => 0);
        dbms_datapump.detach(handle => h1);
        errorvarchar := 'NO_ERROR';
    EXCEPTION
        WHEN OTHERS THEN
        BEGIN
            IF ((errorvarchar = 'ERROR')AND(tryGetStatus=1)) THEN
                DBMS_DATAPUMP.DETACH(h1);
            END IF;
        EXCEPTION
        WHEN OTHERS THEN
            NULL;
        END;
        RAISE;
    END;
    /

11. Verify the import log.
12. Verify the import data.