My thoughts after successful Oracle Cloud Infrastructure 2019 Certified Architect Professional exam

mattia_rossi_oci_certified_solution_architect_professional_2019Right, last 2 weeks I was silent. I am so sorry about that, but believe me… I had to focus on 1Z0-997 final preparation. It was a really hard exam. Mostly because of the wide range of topics to be explored in detail. On one hand, I was sure about my knowledge after building my Terraform+OCI tutorial plus some howtos for OCI compute autoscaling or OKE deployment. But frankly speaking still there was a lot of things where I was not fully familiar or let’s say I have forgotten details after a few months with no practicing. So if you ask me how to pass this exam the answer is rather simple. You need to put yourself in front of your computer and watch all videos which are available at Oracle University (OU)Although I guess it is also good to practice with Terraform for most of the OCI services and not count only on theoretical knowledge from learning paths in OU. I have been also asked many times about brain dumps usage… well… honestly speaking I am not a big fan of that approach. Mostly because it is just a shortcut approach. Learning answers for the particular set of questions will not make you capable of architecting OCI cloud topologies for the real customers. You need to know all of the topics well. This is the only way to be really professional. I know it is hard, especially when there is no time, but this is only way 🙂 Good luck on your exams! I know from Rohit’s message that OCI certs are now extremely popular! It is another sign that our OCI community is growing! :)))

Bon Appetit,

Martin, The Cook.

TF_VAR variables – how to collect it from the OCI Cloud Console…

Recently one of my subscribers has asked me about this topic. How to collect all TF_VAR variables values for Terraform OCI Provider before starting into the first lesson? A small thing, but very important, right? In this short video, I am explaining how to do it step by step 🙂 BTW. I have added this video to my Terraform OCI course.

Bon Appetit,

Martin, The Cook.




How to clone ATP in OCI…

About the flexibility of ATP instances in OCI I have written so far two times. For the first time, it was just a short ride to show how it easy to create this autonomous database in OCI. For the second time, I have shown a new feature of ATP – Private Endpoint. It means ATP instance will be completely separated from the public Internet and visible exclusively in the private subnet. Today I will show you yet another feature of ATP. Now you can quickly clone ATP instance. You can do it in two different ways. The basic is just a clone from the existing instance. A more sophisticated clone is based on ATP automatic backups. In the video below you can watch both use-cases coded with Terraform. I hope it will be a tasty thing as previous recordings 🙂

Bon Appetit,

Martin, The Cook.


Every story should have the beginning…

Every story should have the beginning, right? Recently I have had two zoom sessions with great mates, followers of my blog and YT channel. Such talk is an excellent thing, especially now, in this COVID-19 self-isolation period. Both discussions have made me realize that my tutorial has a significant gap… there is no introduction to this training. I guess it is a common and stupid mistake of experienced people who are focused on the essence and sophisticated details, forgetting that for newbies it’s really hard to start. Shame on me! 😉 Let me fix it immediately! Below you can find the introduction. Hope it will be tasty for newbies in Terraform+OCI field 🙂

Bon Appetit,

Martin, The Cook.

OCI Subcompartments support in Terraform

Nested subcompartments in OCI has been introduced more than one year ago. So frankly speaking feedback about my course was valid. Yes, it should have proper code for nesting all of the examples somewhere in a subcompartment structure instead of the root compartment. Recently I have fixed the code for each and every lesson. Here is a video on how to use it in practice (lesson1). A pinch of spices for our dish! 🙂

Bon Appetit!

Martin, The Cook.


How to use Terraform and OCI – lesson 2a

Recently someone has told me, that my course is great but … it will not work in OCI’s single AD regions. Well… yeah… unfortunately that is true, but I believe we can fix it, right?… so I have introduced additional lesson2a, which is an extension to the original lesson2 where web servers have been deployed in two different ADs. In this short and additional lesson, I am deploying everything in one AD and I am using the fault domain concept, just to achieve hardware failure protection to some extent. In the video below, I am trying to show how to make all of that with Terraform. Please taste it 🙂 I hope you will like it. 🙂

Bon Appetit,

Martin, The Cook.

How to use Terraform and OCI – lesson 7a

A few days back I have written a post about a new feature in OCI related to the DBSystem. Now you can change the shape of your VM where your database is deployed. This level of elasticity is crucial. But what to do in case of a Disaster Recovery scenario. What to do when one AD is not working properly. In that case, you can deploy DataGuard technology. In the on-prem era it was somehow complicated. I do remember well how much time does it has taken to the setup primary-standby database configuration. Now in OCI, it is a matter of few clicks in the Cloud Console or few lines of code in Terraform (check updated repo content in GitHub for lesson 7a).  In the video below you will see how to use this code in practice. Additionally, I will use the network security groups (NSG) approach instead of security lists (SL). Hope this dish will be very tasty 🙂

Bon Appetit,

Martin, The Cook.


Subscribe to get access

For now video is blocked, but you can watch it immediately when you subscribe!

Changing the shape of a virtual machine DB System in OCI with Terraform

True public cloud means the elasticity of the cloud resources. The newest feature related to OCI DBSystem enhanced a few days back means exactly this, true database resource elasticity. I can imagine that in many cases your current DBSystem shape is too small or too large for the workload which is executed. In that case, it would be great to have some simple way to change CPU power by alternative VM shapes. That is why recently I was extremely excited about the dynamic option for DBSystem in case of virtual machine shape change.  You know that for sure, I am a huge fan of automation, Infrastructure as Code approach and Terraform runtime. So I have checked immediately if we can find the corresponding change in the Terraform OCI Provider code. Guess what? Version 3.65.0 supports this new OCI feature. Below a short video shows how it was easy to use this new feature in brand new Terraform OCI Provider.

Bon Appetit,

Martin, The Cook.

Create a custom OCI image using Packer and the OCI Cloud Shell

Today we would like to show you how to bake a custom image in OCI using packer, a tool that complements terraform in creating Infrastructure as a code deployment.
We will use an OCI standard Oracle Autonomous Linux Image, and create a custom one that consists of the original image, plus the Oracle instant client libraries and tools like sqlplus and impdp/expdp. At the end of the process, a new custom image will be available for you to deploy in your OCI tenancy.

What is Packer?

Packer is an open-source tool for creating identical machine images for multiple platforms from a single source configuration. Packer is lightweight, runs on every major operating system, and is highly performant, creating machine images for multiple platforms in parallel. Packer does not replace configuration management like Chef or Puppet. In fact, when building images, Packer is able to use tools like Chef or Puppet to install software onto the image. A machine image is a single static unit that contains a pre-configured operating system and installed software which is used to quickly create new running machinesPacker supports natively creating OCI images by the way of the oracle-oci builder

Required components:

An Active Oracle Cloud Tenancy

If you do not have one, you can enroll here for a trial subscription that includes $300 of free credits

An Oracle Cloud Shell Instance

The OCI Cloud Shell is a web browser-based terminal accessible from the Oracle Cloud Console. Cloud Shell is free to use (within monthly tenancy limits), and provides access to a Linux shell, with a pre-authenticated Oracle Cloud Infrastructure CLI and other useful tools for following Oracle Cloud Infrastructure service tutorials and labs. Cloud Shell is a feature available to all OCI users, accessible from the Console. Your Cloud Shell will appear in the Oracle Cloud Console as a persistent frame of the Console and will stay active as you navigate to different pages of the Console. You can find detailed instructions on how to get started with the OCI Cloud Shell herecloudshell-1.png

mrossi@cloudshell:~ (us-phoenix-1)$ mkdir packer-cloud-test
mrossi@cloudshell:~ (us-phoenix-1)$ cd packer-cloud-test/

An Existing public subnet in an existing Virtual Cloud network

In order to create a custom image, packer needs to deploy an OCI instance, and then connect to it and apply the customizations defined in the configuration file, so you will need to deploy a VCN and set it up so that you are able to ssh into it from the cloud console instance,
For an example of how to do that using terraform, you can use this tutorial: OCI cli Practice 4: Create another VCN with one public subnet


Download and uncompress the Packer binary

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ wget ""
--2020-03-05 12:59:15--
Resolving (, 2a04:4e42:6::439
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 48051150 (46M) [application/zip]
Saving to: ‘’

100%[===============================================================================================================================================>] 48,051,150  53.2MB/s   in 0.9s   

2020-03-05 12:59:16 (53.2 MB/s) - ‘’ saved [48051150/48051150]

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ unzip
  inflating: packer                  
mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ ./packer
Usage: packer [--version] [--help] <command> [<args>]

Available commands are:
    build       build image(s) from template
    console     creates a console for testing variable interpolation
    fix         fixes templates from old versions of packer
    inspect     see components of a template
    validate    check that a template is valid
    version     Prints the Packer version

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$


Packer build file

Download the Packer build file from here

mrossi@cloudshell:oci-packer-customimage (us-phoenix-1)$ wget
--2020-03-05 12:04:15--
Resolving (
Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1698 (1.7K) [text/plain]
Saving to: ‘packer-oci-autonomous-instantclient.json’

100%[==============================================================================================================================================================================================================================>] 1,698       --.-K/s   in 0s      

2020-03-05 12:04:15 (7.32 MB/s) - ‘packer-oci-autonomous-instantclient.json�� saved [1698/1698]

mrossi@cloudshell:oci-packer-customimage (us-phoenix-1)$ cat packer-oci-autonomous-instantclient.json
  "variables": {
      "user_ocid":"{{env `user_ocid`}}",
      "tenancy_ocid": "{{env `tenancy_ocid`}}",
      "fingerprint":"{{env `fingerprint`}}",
      "private_key_path":"{{env `private_key_path`}}",
      "availability_domain": "{{env `availability_domain`}}",
      "region": "{{env `region`}}",
      "base_image_ocid": "{{env `base_image_ocid`}}",
      "compartment_ocid": "{{env `compartment_ocid`}}",
      "subnet_ocid": "{{env `subnet_ocid`}}"

  "builders": [
      "user_ocid":"{{user `user_ocid`}}",
      "tenancy_ocid": "{{user `tenancy_ocid`}}",
      "fingerprint":"{{user `fingerprint`}}",
      "key_file":"{{user `private_key_path`}}",
      "availability_domain": "{{user `availability_domain`}}",
      "region": "{{user `region`}}",
      "base_image_ocid": "{{user `base_image_ocid`}}",
      "compartment_ocid": "{{user `compartment_ocid`}}",
      "image_name": "autonomous-instantclient-demo",
      "shape": "VM.Standard2.1",
      "ssh_username": "opc",
      "ssh_password": "aaaaatrbfgyreyuuyreb",
      "subnet_ocid": "{{user `subnet_ocid`}}",
      "type": "oracle-oci"
  "provisioners": [
      "type": "shell",
      "inline": [
        "sudo -u root yum-config-manager --add-repo",
        "sudo -u root yum -y erase oracle-instantclient18.3-basic",
        "sudo -u root yum -y install oracle-instantclient19.5-devel     oracle-instantclient19.5-tools     oracle-instantclient19.5-jdbc     oracle-instantclient19.5-sqlplus",
        "sqlplus -v",
        "/usr/lib/oracle/19.5/client64/bin/imp HELP=Y"
      "pause_before": "5s"

Setup Environment Variables needed by Packer:

The Packer build file uses some environment variables to deploy the custom image in the proper OCI tenancy.
You will have to follow these instructions to create valid API keys:
Once you have successfully created valid API keys, you will have the following details handy:

  • user_ocid : ID of the user that has been configured with valid API keys
  • tenancy_ocid: ID of the tenancy where the Custom image needs to be created, if it is the same as the Cloud console tenancy use the provided script to retrieve it directly
  • fingerprint: your API key Fingerprint
  • private_key_path: a copy of the private key that has been configured for API access

In addition to that, some other env variables will need to be set up to point the Packer builder to the correct OCI environment

  • compartment_ocid : ID of the Compartment that will host the temporary Instance
  • base_image_ocid : ID of the base image that will be used as a source, in our case: Autonomous Linux 7
  • subnet_ocid : ID of the Subnet that will host

You can use this shell file as an example

mrossi@cloudshell:oci-packer-customimage (us-phoenix-1)$ cat
export user_ocid="ocid1.user.oc1..<your user ocid>"
export tenancy_ocid="`cat /etc/oci/config  | grep tenancy | uniq | cut -d "=" -f 2`"
export compartment_ocid="ocid1.compartment.oc1..<id of the compartment that will host the temporary instance>"
export fingerprint="<your API key fingerprint>"
export private_key_path="<path to your OCI api private key>"
export region="us-phoenix-1"
#Use `oci iam  availability-domain list` to get a list ov the availability domains in the current region
export availability_domain="zTzD:PHX-AD-1"

#OCID of the base image
#oci compute image list --compartment-id $compartment_ocid | jq '.data[] | {image:."display-name", id:."id"}| select ( .image | contains("Autonomous"))'
# to get a list of the available ocids in the current region, if you need to deploy an image in a different region, adjust the oci cli command or get the id from the Web console
export base_image_ocid="ocid1.image.oc1.phx.aaaaaaaa3ocrbp42shmxitpk5nqphpptnnvtk2grrkzfnap4idejfcpv2q4a"

#Subnet id of a suitable OCI Subnet, the packer client needs to be able to SSH to it in order to deploy additional configuration
#oci network subnet list --compartment-id $compartment_ocid --vcn-id $vcn_id | jq '.data[] | {subnet:."display-name", id:."id"}'
#to get a list of subnets in a given VCN
export subnet_ocid="ocid1.subnet.oc1.phx....v7q7ybja"

And, once all fields have been updated, you need to source it:

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ .

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ env | grep -e ocid -e key

Run packer

Now we are ready to run Packer and create our custom image

mrossi@cloudshell:packer-cloud-test (us-phoenix-1)$ ./packer build packer-oci-autonomous-instantclient.json
oracle-oci: output will be in this color.

==> oracle-oci: Creating temporary ssh key for instance...
==> oracle-oci: Creating instance...
==> oracle-oci: Created instance (ocid1.instance.oc1.phx.anyhqljtu24ak7acd3vzqmhazefic7zo6bebsbqz3xvmnq7e23vqexiex2hq).
==> oracle-oci: Waiting for instance to enter 'RUNNING' state...
==> oracle-oci: Instance 'RUNNING'.
==> oracle-oci: Instance has IP:
==> oracle-oci: Using ssh communicator to connect:
==> oracle-oci: Waiting for SSH to become available...
==> oracle-oci: Connected to SSH!
==> oracle-oci: Pausing 5s before the next provisioner...
==> oracle-oci: Provisioning with shell script: /tmp/packer-shell958521454
    oracle-oci: Loaded plugins: langpacks
    oracle-oci: adding repo from:
    oracle-oci: []
    oracle-oci: name=added from:
    oracle-oci: baseurl=
    oracle-oci: enabled=1
    oracle-oci: Loaded plugins: langpacks, ulninfo
    oracle-oci: Resolving Dependencies
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package oracle-instantclient18.3-basic.x86_64 0: will be erased
    oracle-oci: --> Processing Dependency: oracle-instantclient18.3-basic >= for package: python-cx_Oracle-7.0-1.0.1.el7.x86_64
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package python-cx_Oracle.x86_64 0:7.0-1.0.1.el7 will be erased
    oracle-oci: --> Processing Dependency: python-cx_Oracle = 7.0 for package: python-oci-cli-2.9.0-1.el7.noarch
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package python-oci-cli.noarch 0:2.9.0-1.el7 will be erased
    oracle-oci: --> Processing Dependency: python-oci-cli for package: al-config-1.0-3.el7.noarch
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package al-config.noarch 0:1.0-3.el7 will be erased
    oracle-oci: --> Finished Dependency Resolution
    oracle-oci: Dependencies Resolved
    oracle-oci: ================================================================================
    oracle-oci:  Package                            Arch       Version           Repository
    oracle-oci:                                                                            Size
    oracle-oci: ================================================================================
    oracle-oci: Removing:
    oracle-oci:  oracle-instantclient18.3-basic     x86_64      @al7     220 M
    oracle-oci: Removing for dependencies:
    oracle-oci:  al-config                          noarch     1.0-3.el7         @al7      37 k
    oracle-oci:  python-cx_Oracle                   x86_64     7.0-1.0.1.el7     @al7     1.3 M
    oracle-oci:  python-oci-cli                     noarch     2.9.0-1.el7       @al7     9.9 M
    oracle-oci: Transaction Summary
    oracle-oci: ================================================================================
    oracle-oci: Remove  1 Package (+3 Dependent packages)
    oracle-oci: Installed size: 232 M
    oracle-oci: Downloading packages:
    oracle-oci: Running transaction check
    oracle-oci: Running transaction test
    oracle-oci: Transaction test succeeded
    oracle-oci: Running transaction
    oracle-oci:   Erasing    : al-config-1.0-3.el7.noarch                                   1/4
    oracle-oci:   Erasing    : python-oci-cli-2.9.0-1.el7.noarch                            2/4
    oracle-oci:   Erasing    : python-cx_Oracle-7.0-1.0.1.el7.x86_64                        3/4
    oracle-oci:   Erasing    : oracle-instantclient18.3-basic-           4/4
    oracle-oci:   Verifying  : python-oci-cli-2.9.0-1.el7.noarch                            1/4
    oracle-oci:   Verifying  : python-cx_Oracle-7.0-1.0.1.el7.x86_64                        2/4
    oracle-oci:   Verifying  : al-config-1.0-3.el7.noarch                                   3/4
    oracle-oci:   Verifying  : oracle-instantclient18.3-basic-           4/4
    oracle-oci: Removed:
    oracle-oci:   oracle-instantclient18.3-basic.x86_64 0:
    oracle-oci: Dependency Removed:
    oracle-oci:   al-config.noarch 0:1.0-3.el7         python-cx_Oracle.x86_64 0:7.0-1.0.1.el7
    oracle-oci:   python-oci-cli.noarch 0:2.9.0-1.el7
    oracle-oci: Complete!
    oracle-oci: Loaded plugins: langpacks, ulninfo
    oracle-oci: Resolving Dependencies
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package oracle-instantclient19.5-devel.x86_64 0: will be installed
    oracle-oci: --> Processing Dependency: oracle-instantclient19.5-basic >= for package: oracle-instantclient19.5-devel-
    oracle-oci: ---> Package oracle-instantclient19.5-jdbc.x86_64 0: will be installed
    oracle-oci: ---> Package oracle-instantclient19.5-sqlplus.x86_64 0: will be installed
    oracle-oci: ---> Package oracle-instantclient19.5-tools.x86_64 0: will be installed
    oracle-oci: --> Running transaction check
    oracle-oci: ---> Package oracle-instantclient19.5-basic.x86_64 0: will be installed
    oracle-oci: --> Finished Dependency Resolution
    oracle-oci: Dependencies Resolved
    oracle-oci: ================================================================================
    oracle-oci:  Package                          Arch   Version      Repository           Size
    oracle-oci: ================================================================================
    oracle-oci: Installing:
    oracle-oci:  oracle-instantclient19.5-devel   x86_64
    oracle-oci:                                                                           598 k
    oracle-oci:  oracle-instantclient19.5-jdbc    x86_64
    oracle-oci:                                                                           1.5 M
    oracle-oci:  oracle-instantclient19.5-sqlplus x86_64
    oracle-oci:                                                                           686 k
    oracle-oci:  oracle-instantclient19.5-tools   x86_64
    oracle-oci:                                                                           818 k
    oracle-oci: Installing for dependencies:
    oracle-oci:  oracle-instantclient19.5-basic   x86_64
    oracle-oci:                                                                            51 M
    oracle-oci: Transaction Summary
    oracle-oci: ================================================================================
    oracle-oci: Install  4 Packages (+1 Dependent package)
    oracle-oci: Total download size: 55 M
    oracle-oci: Installed size: 236 M
    oracle-oci: Downloading packages:
    oracle-oci: --------------------------------------------------------------------------------
    oracle-oci: Total                                               44 MB/s |  55 MB  00:01
    oracle-oci: Running transaction check
    oracle-oci: Running transaction test
    oracle-oci: Transaction test succeeded
    oracle-oci: Running transaction
    oracle-oci:   Installing : oracle-instantclient19.5-basic-           1/5
    oracle-oci:   Installing : oracle-instantclient19.5-devel-           2/5
    oracle-oci:   Installing : oracle-instantclient19.5-jdbc-            3/5
    oracle-oci:   Installing : oracle-instantclient19.5-tools-           4/5
    oracle-oci:   Installing : oracle-instantclient19.5-sqlplus-         5/5
    oracle-oci:   Verifying  : oracle-instantclient19.5-devel-           1/5
    oracle-oci:   Verifying  : oracle-instantclient19.5-basic-           2/5
    oracle-oci:   Verifying  : oracle-instantclient19.5-jdbc-            3/5
    oracle-oci:   Verifying  : oracle-instantclient19.5-tools-           4/5
    oracle-oci:   Verifying  : oracle-instantclient19.5-sqlplus-         5/5
    oracle-oci: Installed:
    oracle-oci:   oracle-instantclient19.5-devel.x86_64 0:
    oracle-oci:   oracle-instantclient19.5-jdbc.x86_64 0:
    oracle-oci:   oracle-instantclient19.5-sqlplus.x86_64 0:
    oracle-oci:   oracle-instantclient19.5-tools.x86_64 0:
    oracle-oci: Dependency Installed:
    oracle-oci:   oracle-instantclient19.5-basic.x86_64 0:
    oracle-oci: Complete!
    oracle-oci: SQL*Plus: Release - Production
    oracle-oci: Version
==> oracle-oci:
==> oracle-oci: Import: Release - Production on Thu Mar 5 11:02:37 2020
==> oracle-oci: Version
==> oracle-oci:
==> oracle-oci: Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved.
==> oracle-oci:
==> oracle-oci:
==> oracle-oci:
==> oracle-oci: You can let Import prompt you for parameters by entering the IMP
==> oracle-oci: command followed by your username/password:
==> oracle-oci:
==> oracle-oci:      Example: IMP SCOTT/TIGER
==> oracle-oci:
==> oracle-oci: Or, you can control how Import runs by entering the IMP command followed
==> oracle-oci: by various arguments. To specify parameters, you use keywords:
==> oracle-oci:
==> oracle-oci:      Format:  IMP KEYWORD=value or KEYWORD=(value1,value2,...,valueN)
==> oracle-oci:      Example: IMP SCOTT/TIGER IGNORE=Y TABLES=(EMP,DEPT) FULL=N
==> oracle-oci:                or TABLES=(T1:P1,T1:P2), if T1 is partitioned table
==> oracle-oci:
==> oracle-oci: USERID must be the first parameter on the command line.
==> oracle-oci:
==> oracle-oci: Keyword  Description (Default)       Keyword      Description (Default)
==> oracle-oci: --------------------------------------------------------------------------
==> oracle-oci: USERID   username/password           FULL         import entire file (N)
==> oracle-oci: BUFFER   size of data buffer         FROMUSER     list of owner usernames
==> oracle-oci: FILE     input files (EXPDAT.DMP)    TOUSER       list of usernames
==> oracle-oci: SHOW     just list file contents (N) TABLES       list of table names
==> oracle-oci: IGNORE   ignore create errors (N)    RECORDLENGTH length of IO record
==> oracle-oci: GRANTS   import grants (Y)           INCTYPE      incremental import type
==> oracle-oci: INDEXES  import indexes (Y)          COMMIT       commit array insert (N)
==> oracle-oci: ROWS     import data rows (Y)        PARFILE      parameter filename
==> oracle-oci: LOG      log file of screen output   CONSTRAINTS  import constraints (Y)
==> oracle-oci: DESTROY                overwrite tablespace data file (N)
==> oracle-oci: INDEXFILE              write table/index info to specified file
==> oracle-oci: SKIP_UNUSABLE_INDEXES  skip maintenance of unusable indexes (N)
==> oracle-oci: FEEDBACK               display progress every x rows(0)
==> oracle-oci: TOID_NOVALIDATE        skip validation of specified type ids
==> oracle-oci: FILESIZE               maximum size of each dump file
==> oracle-oci: STATISTICS             import precomputed statistics (always)
==> oracle-oci: RESUMABLE              suspend when a space related error is encountered(N)
==> oracle-oci: RESUMABLE_NAME         text string used to identify resumable statement
==> oracle-oci: RESUMABLE_TIMEOUT      wait time for RESUMABLE
==> oracle-oci: COMPILE                compile procedures, packages, and functions (Y)
==> oracle-oci: STREAMS_CONFIGURATION  import streams general metadata (Y)
==> oracle-oci: STREAMS_INSTANTIATION  import streams instantiation metadata (N)
==> oracle-oci: DATA_ONLY              import only data (N)
==> oracle-oci: VOLSIZE                number of bytes in file on each volume of a file on tape
==> oracle-oci:
==> oracle-oci: The following keywords only apply to transportable tablespaces
==> oracle-oci: TRANSPORT_TABLESPACE import transportable tablespace metadata (N)
==> oracle-oci: TABLESPACES tablespaces to be transported into database
==> oracle-oci: DATAFILES datafiles to be transported into database
==> oracle-oci: TTS_OWNERS users that own data in the transportable tablespace set
==> oracle-oci:
==> oracle-oci: Import terminated successfully without warnings.
==> oracle-oci: Creating image from instance...
==> oracle-oci: Creating image from instance...
==> oracle-oci: Image created.
==> oracle-oci: Terminating instance (ocid1.instance.oc1.phx.anyhqljtu24ak7acd3vzqmhazefic7zo6bebsbqz3xvmnq7e23vqexiex2hq)...
==> oracle-oci: Terminated instance.
Build 'oracle-oci' finished.

Verify our Custom image is available

We can use either the console or the oci cli to check the availability of our newly created image:

oci compute image list  --compartment-id $compartment_ocid | jq -r '.data | map(select(."time-created" != null)) | sort_by(."time-created")[]| [."display-name",."operating-system",."time-created"]'


  "Oracle Autonomous Linux",



This pattern applies to an infinite set of possibilities to automate the creation of custom images in OCI (and other Cloud and Legacy Platforms), the limit is your fantasy (and possibly the time you have to play with it …..) Have Fun!




Private Endpoints for OCI Autonomous Database

Pic. Topology Diagram for Private Endpoint for ATP

It is not the first blog post about ATP, but I think this one is even more interesting. For your information, a few days back at OCI Release Notes webpage I have found information about new features for OCI Autonomous DB offering. I am talking about Private Endpoints for ATP or ADW databases. This feature has been awaited for a very long time. Previously your ATP or ADW databases were available only via public IPs. Now you can nest them inside a particular VCN and subnet. It means your database will be available under private IP enclosed in your subnet’s CIDR. Of course, you need to prepare some Network Security Groups (NSG) on ATP/ADW level and VM level. Since that moment VM can connect to ATP/ADW with SQLNet connection via private IP. For testing purposes I have created small GitHub repo and below you can find a video about how to use that repo. I believe you will find this dish very delicious. 🙂

Bon Appetit,

Martin, The Cook.

Subscribe to get access

For now video is blocked, but you can watch it immediately when you subscribe!