Blog
Oracle Autonomous Database and DevOps: A simple usage approach – Part 2
Category: Cloud Author: BRUNO REIS Date: 5 years ago Comments: 0

Oracle Autonomous Database and DevOps:
A simple usage approach – Part 2

            This article is the second part of the series of articles about Oracle Autonomous Database and DevOps. For a better understanding, I recommend reading the article “Oracle Autonomous Database and DevOps: A Simple Usage Approach – Part 1” before proceeding with the steps in this article.
 
As in the previous article the Docker configuration was handled, we will begin to provision the Oracle Autonomous Database version 18c in the Oracle Cloud.
 
– Provisioning the Oracle Autonomous Database in the Cloud: Before provisioning the database it is necessary to create a Compartment. If you have not yet created click on “Identity” and later on “Compartments” under the “Governance and Administration” tab of the menu:

 

 

Then click “Create Compartment” if there is no existing compartment: The root compartment is the first compartment created. From this it is possible to create other compartments by using it as an option in the “Parent Compartment” tab.
Fill in the required fields as the Name of the compartment, any description in the Description field and click on the “Create Compartment” link.
In the above example the name “brunoreis” was chosen as the name of the compartment. In addition, because Oracle recommends creating databases in compartments other than root, a compartment called TECHDATABASKET was created, represented by the image below:

 

Now with the compartment created we will proceed with the creation of the Autonomous Transaction Processing (ATP) instance.
 
On the Oracle Cloud menu, click Autonomous Transaction Processing:

 

Click the Create Autonomous Database button:
In the Create Autonomous Database tab fill in all requested information such as database name, CPU core, storage etc. An important note in this topic is that you can choose the type of workload as AUTONOMOUS DATA WAREHOUSE or AUTONOMOUS TRANSACTION PROCESSING. However, in this article we are only using the AUTONOMOUS TRANSACTION PROCESSING option.
Make sure you have provided all the information correctly and click on “Create autonomous database”:
 
 
During the creation of the database, we will be shown the status “Provisioning”
Once the provisioning is finalized, the status is changed to “Available”:
            In the next article we will discuss the connection between Oracle SQL Developer using the database wallet file created in the Oracle Cloud and also the creation of a Linux machine where the application will be implemented.
 
 
References:
 
https://www.oracle.com/databaose/autnomous-database.html
https://docs.cloud.oracle.com/

 

 

 

Bruno Reis da Silva is a Database Cloud Support Engineer and professionally Certified Oracle Database Administrator who has worked on the South American continent and is now working at the European continent. He was awarded the first Oracle Ace Associate of Hungary in 2017. His interests are in RDBMS, mainly Oracle, operating systems (Linux, AIX, HPUX and Solaris) and High Availability Solutions implementations. In his free time he enjoys playing sports , going to the gym and traveling. His blog www.techdatabasket.com is dedicated to his sister Laura Vitoria and the main reason for blogging is because he believes in the quote “giving back to get back” . He also enjoys continuous learning and the interaction with others who share his interest.

 

 

 

Carlos Magno de Andrade Júnior is an  Database Architect at eProseed Europe, with more than 15 years of experience in Oracle database on complex projects in countries such as Brazil , India , the Netherlands, Luxembourg , France and Italy, having worked in companies such as Oracle Corporation, IBM, HSBC, among others. Also shares information on his blog ezdba.wordpress.com. Certifications : OCM 12c OCP 10g , 11g OCP , OCP 12c, OCE RAC , Exadata , ITIL and OEM 12c Cloud Control Implementation Specialist.

 


RMAN, Allocate channel, CDB, and CLOSE, bug
Category: Database Author: Fernando Simon (Board Member) Date: 5 years ago Comments: 0

RMAN, Allocate channel, CDB, and CLOSE, bug

Allocate channel for RMAN is used in various scenarios, most of the time is useful when you use tape as device type or you need to use some kind of format. The way to do the allocation not changed since a long time ago, but when you run the database in container mode you can hit a bug that turns your channel unusable. I will show you the bug and how to avoid it with a simple trick.
This bug hit every version since 12 and I discovered it last year when testing some scenarios, but I was able to test and post just recently. It just occurs for CDB databases and exists just one one-off solution published for 12.2. But there is one workaround more useful and works for every version.
The most interesting part is that everything that we made until now when allocate channel will not work. You can search in all doc available for allocate channel since 9i until 19c the first thing that you made after open the run{} is allocate channel. This is the default and recommended in the docs:

 

 

https://docs.oracle.com/en/database/oracle/oracle-database/19/rcmrf/ALLOCATE-CHANNEL.html#GUID-9320BFF7-0728-4B3D-85B9-2184557ECDCE,
 
https://docs.oracle.com/en/database/oracle/oracle-database/18/rcmrf/ALLOCATE-CHANNEL.html#GUID-9320BFF7-0728-4B3D-85B9-2184557ECDCE

 

https://docs.oracle.com/cd/A97630_01/server.920/a96566/rcmconc1.htm
My environment for this post is 18c database (last update from April 2019) with just one PDB:

 

 

[oracle@orcloel7 ~]$ sqlplus / as sysdba




SQL*Plus: Release 18.0.0.0.0 - Production on Sun Jun 30 23:24:23 2019

Version 18.6.0.0.0




Copyright (c) 1982, 2018, Oracle.  All rights reserved.







Connected to:

Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production

Version 18.6.0.0.0




SQL> show pdbs




    CON_ID CON_NAME                       OPEN MODE  RESTRICTED

---------- ------------------------------ ---------- ----------

         2 PDB$SEED                       READ ONLY  NO

         3 ORCL18P                        READ WRITE NO

SQL> exit

Disconnected from Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 - Production

Version 18.6.0.0.0

[oracle@orcloel7 ~]$

And for rman I show the schema and the backup for one datafile (#12) just to have smaller output.

RMAN> report schema;




Report of database schema for database with db_unique_name ORCL18C




List of Permanent Datafiles

===========================

File Size(MB) Tablespace           RB segs Datafile Name

---- -------- -------------------- ------- ------------------------

1    870      SYSTEM               YES     /u01/app/oracle/oradata/ORCL18C/system01.dbf

3    490      SYSAUX               NO      /u01/app/oracle/oradata/ORCL18C/sysaux01.dbf

4    330      UNDOTBS1             YES     /u01/app/oracle/oradata/ORCL18C/undotbs01.dbf

5    290      PDB$SEED:SYSTEM      NO      /u01/app/oracle/oradata/ORCL18C/pdbseed/system01.dbf

6    340      PDB$SEED:SYSAUX      NO      /u01/app/oracle/oradata/ORCL18C/pdbseed/sysaux01.dbf

7    5        USERS                NO      /u01/app/oracle/oradata/ORCL18C/users01.dbf

8    100      PDB$SEED:UNDOTBS1    NO      /u01/app/oracle/oradata/ORCL18C/pdbseed/undotbs01.dbf

9    300      ORCL18P:SYSTEM       YES     /u01/app/oracle/oradata/ORCL18C/ORCL18P/system01.dbf

10   360      ORCL18P:SYSAUX       NO      /u01/app/oracle/oradata/ORCL18C/ORCL18P/sysaux01.dbf

11   100      ORCL18P:UNDOTBS1     YES     /u01/app/oracle/oradata/ORCL18C/ORCL18P/undotbs01.dbf

12   5        ORCL18P:USERS        NO      /u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf




List of Temporary Files

=======================

File Size(MB) Tablespace           Maxsize(MB) Tempfile Name

---- -------- -------------------- ----------- --------------------

1    37       TEMP                 32767       /u01/app/oracle/oradata/ORCL18C/temp01.dbf

2    62       PDB$SEED:TEMP        32767       /u01/app/oracle/oradata/ORCL18C/pdbseed/temp012019-05-25_23-51-33-086-PM.dbf

3    62       ORCL18P:TEMP         32767       /u01/app/oracle/oradata/ORCL18C/ORCL18P/temp01.dbf




RMAN> list backup of datafile 12 completed after "sysdate - 60/1440";




starting full resync of recovery catalog

full resync complete




List of Backup Sets

===================







BS Key  Type LV Size       Device Type Elapsed Time Completion Time

------- ---- -- ---------- ----------- ------------ ----------------

4610    Incr 1  40.00K     SBT_TAPE    00:00:02     02-07-2019_00-03

        BP Key: 4611   Status: AVAILABLE  Compressed: YES  Tag: TAG20190701T235918

        Handle: VB$_4142545763_4609I   Media:

  List of Datafiles in backup set 4610

  File LV Type Ckp SCN    Ckp Time         Abs Fuz SCN Sparse Name

  ---- -- ---- ---------- ---------------- ----------- ------ ----

  12   1  Incr 1714757    02-07-2019_00-03              NO    /u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf




BS Key  Type LV Size       Device Type Elapsed Time Completion Time

------- ---- -- ---------- ----------- ------------ ----------------

4614    Incr 0  36.50K     SBT_TAPE    00:00:02     02-07-2019_00-03

        BP Key: 4615   Status: AVAILABLE  Compressed: YES  Tag: TAG20190701T235918

        Handle: VB$_4142545763_4609_12   Media:

  List of Datafiles in backup set 4614

  File LV Type Ckp SCN    Ckp Time         Abs Fuz SCN Sparse Name

  ---- -- ---- ---------- ---------------- ----------- ------ ----

  12   0  Incr 1714757    02-07-2019_00-03              NO    /u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf




RMAN>

But look the example below where I try to restore the datafile (maybe because was corrupted – whatever the reason):

RMAN> run{

2> ALLOCATE CHANNEL CH1 DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS  "SBT_LIBRARY=/u01/app/oracle/product/18.6.0.0/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/product/18.6.0.0/dbhome_1/dbs/ra_zdlra credential_alias=zdlra-scan:1521/zdlra:orcl')";

ALTER PLUGGABLE DATABASE ORCL18P CLOSE IMMEDIATE INSTANCES=ALL;

RESTORE DATAFILE 12;

RECOVER DATAFILE 12;

}3> 4> 5> 6>




allocated channel: CH1

channel CH1: SID=72 device type=SBT_TAPE

channel CH1: RA Library (ZDLRA) SID=8CA6E4CA5A751068E053010310AC0A07




Statement processed

starting full resync of recovery catalog

full resync complete




Starting restore at 02-07-2019_00-18

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=72 device type=DISK




RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 07/02/2019 00:18:08

RMAN-06026: some targets not found - aborting restore

RMAN-06100: no channel to restore a backup or copy of datafile 12




RMAN>

And now this:

RMAN> run{

ALTER PLUGGABLE DATABASE ORCL18P CLOSE IMMEDIATE INSTANCES=ALL;

ALLOCATE CHANNEL CH1 DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS  "SBT_LIBRARY=/u01/app/oracle/product/18.6.0.0/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/product/18.6.0.0/dbhome_1/dbs/ra_zdlra credential_alias=zdlra-scan:1521/zdlra:orcl')";

RESTORE DATAFILE 12;

RECOVER DATAFILE 12;

} 2> 3> 4> 5> 6>




Statement processed

starting full resync of recovery catalog

full resync complete




allocated channel: CH1

channel CH1: SID=63 device type=SBT_TAPE

channel CH1: RA Library (ZDLRA) SID=8CA703A063E7127DE053010310ACC85B




Starting restore at 02-07-2019_00-18




channel CH1: starting datafile backup set restore

channel CH1: specifying datafile(s) to restore from backup set

channel CH1: restoring datafile 00012 to /u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf

channel CH1: reading from backup piece VB$_4142545763_4609_12

channel CH1: piece handle=VB$_4142545763_4609_12 tag=TAG20190701T235918

channel CH1: restored backup piece 1

channel CH1: restore complete, elapsed time: 00:00:25

Finished restore at 02-07-2019_00-19




Starting recover at 02-07-2019_00-19




starting media recovery

media recovery complete, elapsed time: 00:00:01




Finished recover at 02-07-2019_00-19

starting full resync of recovery catalog

full resync complete

released channel: CH1




RMAN> ALTER PLUGGABLE DATABASE ORCL18P OPEN INSTANCES=ALL;




Statement processed

starting full resync of recovery catalog

full resync complete




RMAN>

 

Saw the bug? YES, the bug occurs when you allocate the channel and after execute a close command. When you do the “close”, rman internally cleans everything related for the session (including allocated channels) and you can hit the “RMAN-06100: no channel to restore a backup” or others similar errors like RMAN-06012: channel: CH1 not allocated.

 

 

The bug is Bug 28076886 – RMAN: RMAN-06012: “channel: %s not allocated” after ALTER PLUGGABLE DATABASE CLOSE command (Doc ID 28076886.8)
https://support.oracle.com/epmos/faces/DocContentDisplay?id=28076886.8.

 

The error occurs even for disk channels too (look full example):

 

 

RMAN> RUN {

ALLOCATE CHANNEL CH1 DEVICE TYPE DISK;

ALTER PLUGGABLE DATABASE ORCL18P CLOSE;

RECOVER DATABASE PREVIEW;

RELEASE CHANNEL CH1;

}2> 3> 4> 5> 6>




allocated channel: CH1

channel CH1: SID=110 device type=DISK




Statement processed

starting full resync of recovery catalog

full resync complete




Starting recover at 01-07-2019_00-34

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=110 device type=DISK

using channel ORA_DISK_1




no channel to restore a backup or copy of archived log for thread 1 with sequence 5 and starting SCN of 1552035

no channel to restore a backup or copy of archived log for thread 1 with sequence 6 and starting SCN of 1608615

no channel to restore a backup or copy of archived log for thread 1 with sequence 7 and starting SCN of 1669357

no channel to restore a backup or copy of archived log for thread 1 with sequence 8 and starting SCN of 1681533

no channel to restore a backup or copy of archived log for thread 1 with sequence 9 and starting SCN of 1681555

no channel to restore a backup or copy of archived log for thread 1 with sequence 10 and starting SCN of 1682610

List of Archived Log Copies for database with db_unique_name ORCL18C

=====================================================================




Key     Thrd Seq     S Low Time

------- ---- ------- - ----------------

3516    1    11      A 26-05-2019_19-13

        Name: /u01/app/oracle/oradata/ORCL18C/archivelog/2019_06_30/o1_mf_1_11_gklbz4oh_.arc




recovery will be done up to SCN 1603932

Media recovery start SCN is 1603932

Recovery must be done beyond SCN 1692620 to clear datafile fuzziness

Finished recover at 01-07-2019_00-35




RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of release command at 07/01/2019 00:35:01

RMAN-06012: channel: CH1 not allocated




RMAN> RUN {

ALTER PLUGGABLE DATABASE ORCL18P CLOSE;

ALLOCATE CHANNEL CH1 DEVICE TYPE DISK;

RECOVER DATABASE PREVIEW;

RELEASE CHANNEL CH1;

}2> 3> 4> 5> 6>




Statement processed

starting full resync of recovery catalog

full resync complete




allocated channel: CH1

channel CH1: SID=110 device type=DISK




Starting recover at 01-07-2019_00-35




no channel to restore a backup or copy of archived log for thread 1 with sequence 5 and starting SCN of 1552035

no channel to restore a backup or copy of archived log for thread 1 with sequence 6 and starting SCN of 1608615

no channel to restore a backup or copy of archived log for thread 1 with sequence 7 and starting SCN of 1669357

no channel to restore a backup or copy of archived log for thread 1 with sequence 8 and starting SCN of 1681533

no channel to restore a backup or copy of archived log for thread 1 with sequence 9 and starting SCN of 1681555

no channel to restore a backup or copy of archived log for thread 1 with sequence 10 and starting SCN of 1682610

List of Archived Log Copies for database with db_unique_name ORCL18C

=====================================================================




Key     Thrd Seq     S Low Time

------- ---- ------- - ----------------

3516    1    11      A 26-05-2019_19-13

        Name: /u01/app/oracle/oradata/ORCL18C/archivelog/2019_06_30/o1_mf_1_11_gklbz4oh_.arc




recovery will be done up to SCN 1603932

Media recovery start SCN is 1603932

Recovery must be done beyond SCN 1693086 to clear datafile fuzziness

Finished recover at 01-07-2019_00-36




released channel: CH1




RMAN>

But can be trickier to discover the failure. Look the example below that I try to backup datafile #12:

RMAN> run{

ALLOCATE CHANNEL CH1 DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS  "SBT_LIBRARY=/u01/app/oracle/product/18.6.0.0/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/product/18.6.0.0/dbhome_1/dbs/ra_zdlra credential_alias=zdlra-scan:1521/zdlra:orcl')";

ALTER PLUGGABLE DATABASE ORCL18P CLOSE IMMEDIATE INSTANCES=ALL;

BACKUP INCREMENTAL LEVEL 1 DATAFILE 12;

}2> 3> 4> 5>




allocated channel: CH1

channel CH1: SID=156 device type=SBT_TAPE

channel CH1: RA Library (ZDLRA) SID=8CBA2C4600D309E8E053010310AC3E17




Statement processed

starting full resync of recovery catalog

full resync complete




Starting backup at 02-07-2019_23-25

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=106 device type=DISK

channel ORA_DISK_1: starting incremental level 1 datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00012 name=/u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf

channel ORA_DISK_1: starting piece 1 at 02-07-2019_23-25

channel ORA_DISK_1: finished piece 1 at 02-07-2019_23-25

piece handle=/u01/app/oracle/oradata/ORCL18C/89BE7E168E3D28BDE053010310AC2497/backupset/2019_07_02/o1_mf_nnnd1_TAG20190702T232547_gkqlyx8j_.bkp tag=TAG20190702T232547 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01

Finished backup at 02-07-2019_23-25




Starting Control File and SPFILE Autobackup at 02-07-2019_23-25

piece handle=/u01/app/oracle/oradata/ORCL18C/autobackup/2019_07_02/o1_mf_s_1012605951_gkqlz1vm_.bkp comment=NONE

Finished Control File and SPFILE Autobackup at 02-07-2019_23-25




RMAN> list backup of datafile 12 summary;







List of Backups

===============

Key     TY LV S Device Type Completion Time  #Pieces #Copies Compressed Tag

------- -- -- - ----------- ---------------- ------- ------- ---------- ---

4270    B  0  A SBT_TAPE    01-07-2019_00-42 1       1       YES        TAG20190701T003820

4610    B  1  A SBT_TAPE    02-07-2019_00-03 1       1       YES        TAG20190701T235918

4614    B  0  A SBT_TAPE    02-07-2019_00-03 1       1       YES        TAG20190701T235918

5197    B  1  A DISK        02-07-2019_23-25 1       1       NO         TAG20190702T232547




RMAN>

And now:

RMAN> run{

ALTER PLUGGABLE DATABASE ORCL18P CLOSE IMMEDIATE INSTANCES=ALL;

ALLOCATE CHANNEL CH1 DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%U' PARMS  "SBT_LIBRARY=/u01/app/oracle/product/18.6.0.0/dbhome_1/lib/libra.so, ENV=(RA_WALLET='location=file:/u01/app/oracle/product/18.6.0.0/dbhome_1/dbs/ra_zdlra credential_alias=zdlra-scan:1521/zdlra:orcl')";

BACKUP INCREMENTAL LEVEL 1 DATAFILE 12;

}2> 3> 4> 5>




Statement processed

starting full resync of recovery catalog

full resync complete




allocated channel: CH1

channel CH1: SID=105 device type=SBT_TAPE

channel CH1: RA Library (ZDLRA) SID=8CBAA68CCD751232E053010310AC374B




Starting backup at 02-07-2019_23-44

channel CH1: starting incremental level 1 datafile backup set

channel CH1: specifying datafile(s) in backup set

input datafile file number=00012 name=/u01/app/oracle/oradata/ORCL18C/ORCL18P/users01.dbf

channel CH1: starting piece 1 at 02-07-2019_23-44

channel CH1: finished piece 1 at 02-07-2019_23-44

piece handle=ORCL18C_3pu5ma33_1_1 tag=TAG20190702T234435 comment=API Version 2.0,MMS Version 12.2.0.2

channel CH1: backup set complete, elapsed time: 00:00:03

Finished backup at 02-07-2019_23-44




Starting Control File and SPFILE Autobackup at 02-07-2019_23-44

piece handle=c-551670416-20190702-02 comment=API Version 2.0,MMS Version 12.2.0.2

Finished Control File and SPFILE Autobackup at 02-07-2019_23-44

released channel: CH1




RMAN>

 

Look that because of the bug, in the first example, the backup was made to disk and not in the tape as requested. In the last, you can see that backup was made correctly in tape. But as you saw, no error was reported.

 

Conclusion

 

As you saw a tricky bug can change everything that we already know (and need to do) for a daily basis activity. One simple “close” for a PDB can destroy your backup/restore policy that you use from decades. Besides that even without “RMAN-06100: no channel to restore a backup” or other similar errors like RMAN-06012: channel: CH1 not allocated you can have problems.
Luckily if you are running affected version (everything below 19.2) the workaround is very simple to deploy.
 
This post was published in my personal blog too: http://www.fernandosimon.com/blog/rman-allocate-channel-cdb-and-close-bug/
 

Disclaimer: “The postings on this site are my own and don’t necessarily represent my actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications were removed to allow reach the generic audience and to be useful for the community.”


Oracle Autonomous Database and DevOps: A simple usage approach – Part 1
Category: Cloud Author: BRUNO REIS Date: 5 years ago Comments: 0

Oracle Autonomous Database and DevOps:
A simple usage approach – Part 1

            This article explains the creation of an Oracle Autonomous Database instance in the Oracle Cloud  for the usage of programmers(some tests examples with some programming languages and Oracle SQL Developer). Let’s build some concept to start:

 

What is the Oracle Autonomous Database?

 

            According  to Oracle Corp, it is “the first standalone cloud data manager that provides application for patches, upgrades and tuning, including performing maintenance tasks on the database without human intervention.”. In addition, Oracle itself explains 3 features of this new database model that are:
  • According to the Oracle Corp. this is “
  • Self-Driving: Thus reducing human labor;
  • Self-Securing: Protecting yourself from third-party attacks;
  • Self-Repairing: Will try to keep the database running regardless of the error, as it will attempt to resolve the issue autonomously.

 

What is Docker?

 

It is a computer program that performs virtualization at the operating system level.
 
            Now that you have a brief understanding of what is the Oracle Autonomous Database we will begin to configure the database in the Oracle Cloud for programming purposes. To do this, we will follow the following steps:

 

Account configuration in the Oracle Cloud: In this step you will need to create the account  in the Oracle Cloud through the https://cloud.oracle.com/home link. I will not go into detail in this topic because  someone recently had an article published in OTN Brazil that details step by step this topic. The name of the article is “Using Oracle Autonomous Transaction Processing” and can be found on the following link:
https://www.oracle.com/technetwork/pt/articles/cloudcomp/utilizando-oracle-atp-5462247-ptb.html .

 

– Docker Software Installation: This software can be found on the manufacturer’s official website https://www.docker.com/ and the installation depends on the type of operating system. In this article we will be using the Red Hat 7 operating system. Here is an example below:

 

 

[root@oc8226237722 ~]# yum install docker

Loaded plugins: downloadkvmonly-background, techdatabasketblog-check-lotus-updates, techdatabasketblog-check-

              : upgrade, techdatabasketblog-check-xorg-updates, techdatabasketblog-repository, langpacks,

              : post-transaction-actions, refresh-packagekit, versionlock

RHEL-76-x86_64                                           | 4.1 kB     00:00    

RHEL-76-x86_64-techdatabasketblog-updates                               | 3.3 kB     00:00    

RHEL-76-x86_64-updates                                   | 3.3 kB     00:00    

RHEL7-x86_64-techdatabasketblog-upgrade                                 | 3.3 kB     00:00    







Resolving Dependencies

--> Running transaction check

---> Package docker.x86_64 2:1.13.1-75.git8633870.el7.centos will be installed

--> Processing Dependency: docker-common = 2:1.13.1-75.git8633870.el7.centos for package: 2:docker-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: docker-client = 2:1.13.1-75.git8633870.el7.centos for package: 2:docker-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: subscription-manager-rhsm-certificates for package: 2:docker-1.13.1-75.git8633870.el7.centos.x86_64

--> Running transaction check

---> Package docker-client.x86_64 2:1.13.1-75.git8633870.el7.centos will be installed

---> Package docker-common.x86_64 2:1.13.1-75.git8633870.el7.centos will be installed

--> Processing Dependency: skopeo-containers >= 1:0.1.26-2 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: oci-umount >= 2:2.3.3-3 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: oci-systemd-hook >= 1:0.1.4-9 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: oci-register-machine >= 1:0-5.13 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: container-storage-setup >= 0.9.0-1 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: container-selinux >= 2:2.51-1 for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

--> Processing Dependency: atomic-registries for package: 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64

---> Package subscription-manager-rhsm-certificates.x86_64 0:1.21.10-3.el7_6 will be installed

--> Running transaction check

---> Package atomic-registries.x86_64 1:1.22.1-25.git5a342e3.el7.centos will be installed

--> Processing Dependency: python-pytoml for package: 1:atomic-registries-1.22.1-25.git5a342e3.el7.centos.x86_64

---> Package container-selinux.noarch 2:2.68-1.el7 will be installed

--> Processing Dependency: policycoreutils-python for package: 2:container-selinux-2.68-1.el7.noarch

---> Package container-storage-setup.noarch 0:0.11.0-2.git5eaf76c.el7 will be installed

---> Package oci-register-machine.x86_64 1:0-6.git2b44233.el7 will be installed

---> Package oci-systemd-hook.x86_64 1:0.1.17-2.git83283a0.el7 will be installed

---> Package oci-umount.x86_64 2:2.3.3-3.gite3c9055.el7 will be installed

---> Package skopeo-containers.x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos will be installed

--> Running transaction check

---> Package policycoreutils-python.x86_64 0:2.5-29.el7_6.1 will be installed

--> Processing Dependency: policycoreutils = 2.5-29.el7_6.1 for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: setools-libs >= 3.3.8-4 for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libsemanage-python >= 2.5-14 for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: audit-libs-python >= 2.1.3-4 for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libqpol.so.1(VERS_1.4)(64bit) for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libqpol.so.1(VERS_1.2)(64bit) for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libapol.so.4(VERS_4.0)(64bit) for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: checkpolicy for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libqpol.so.1()(64bit) for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libapol.so.4()(64bit) for package: policycoreutils-python-2.5-29.el7_6.1.x86_64

---> Package python-pytoml.noarch 0:0.1.14-1.git7dea353.el7 will be installed

--> Running transaction check

---> Package audit-libs-python.x86_64 0:2.8.4-4.el7 will be installed

--> Processing Dependency: audit-libs(x86-64) = 2.8.4-4.el7 for package: audit-libs-python-2.8.4-4.el7.x86_64

---> Package checkpolicy.x86_64 0:2.5-8.el7 will be installed

---> Package libsemanage-python.x86_64 0:2.5-14.el7 will be installed

--> Processing Dependency: libsemanage = 2.5-14.el7 for package: libsemanage-python-2.5-14.el7.x86_64

---> Package policycoreutils.x86_64 0:2.5-22.el7 will be updated

---> Package policycoreutils.x86_64 0:2.5-29.el7_6.1 will be an update

--> Processing Dependency: libsepol >= 2.5-10 for package: policycoreutils-2.5-29.el7_6.1.x86_64

--> Processing Dependency: libselinux-utils >= 2.5-14 for package: policycoreutils-2.5-29.el7_6.1.x86_64

---> Package setools-libs.x86_64 0:3.3.8-4.el7 will be installed

--> Processing Dependency: libselinux >= 2.5-14.1 for package: setools-libs-3.3.8-4.el7.x86_64

--> Running transaction check

---> Package audit-libs.i686 0:2.8.1-3.el7_5.1 will be updated

---> Package audit-libs.x86_64 0:2.8.1-3.el7_5.1 will be updated

--> Processing Dependency: audit-libs(x86-64) = 2.8.1-3.el7_5.1 for package: audit-2.8.1-3.el7_5.1.x86_64

---> Package audit-libs.i686 0:2.8.4-4.el7 will be an update

---> Package audit-libs.x86_64 0:2.8.4-4.el7 will be an update

---> Package libselinux.i686 0:2.5-12.el7 will be updated

---> Package libselinux.x86_64 0:2.5-12.el7 will be updated

--> Processing Dependency: libselinux(x86-64) = 2.5-12.el7 for package: libselinux-python-2.5-12.el7.x86_64

--> Processing Dependency: libselinux(x86-64) = 2.5-12.el7 for package: libselinux-devel-2.5-12.el7.x86_64

---> Package libselinux.i686 0:2.5-14.1.el7 will be an update

---> Package libselinux.x86_64 0:2.5-14.1.el7 will be an update

---> Package libselinux-utils.x86_64 0:2.5-12.el7 will be updated

---> Package libselinux-utils.x86_64 0:2.5-14.1.el7 will be an update

---> Package libsemanage.x86_64 0:2.5-11.el7 will be updated

---> Package libsemanage.x86_64 0:2.5-14.el7 will be an update

---> Package libsepol.i686 0:2.5-8.1.el7 will be updated

---> Package libsepol.x86_64 0:2.5-8.1.el7 will be updated

--> Processing Dependency: libsepol(x86-64) = 2.5-8.1.el7 for package: libsepol-devel-2.5-8.1.el7.x86_64

---> Package libsepol.i686 0:2.5-10.el7 will be an update

---> Package libsepol.x86_64 0:2.5-10.el7 will be an update

--> Running transaction check

---> Package audit.x86_64 0:2.8.1-3.el7_5.1 will be updated

---> Package audit.x86_64 0:2.8.4-4.el7 will be an update

---> Package libselinux-devel.x86_64 0:2.5-12.el7 will be updated

---> Package libselinux-devel.x86_64 0:2.5-14.1.el7 will be an update

---> Package libselinux-python.x86_64 0:2.5-12.el7 will be updated

---> Package libselinux-python.x86_64 0:2.5-14.1.el7 will be an update

---> Package libsepol-devel.x86_64 0:2.5-8.1.el7 will be updated

---> Package libsepol-devel.x86_64 0:2.5-10.el7 will be an update

--> Finished Dependency Resolution




Dependencies Resolved




================================================================================

 Package                 Arch   Version                    Repository      Size

================================================================================

Installing:

 docker                  x86_64 2:1.13.1-75.git8633870.el7.centos

                                                           RHEL-76-x86_64  16 M

Installing for dependencies:

 atomic-registries       x86_64 1:1.22.1-25.git5a342e3.el7.centos

                                                           RHEL-76-x86_64  35 k

 audit-libs-python       x86_64 2.8.4-4.el7                RHEL-76-x86_64  76 k

 checkpolicy             x86_64 2.5-8.el7                  RHEL-76-x86_64 295 k

 container-selinux       noarch 2:2.68-1.el7               RHEL-76-x86_64  36 k

 container-storage-setup noarch 0.11.0-2.git5eaf76c.el7    RHEL-76-x86_64  35 k

 docker-client           x86_64 2:1.13.1-75.git8633870.el7.centos

                                                           RHEL-76-x86_64 3.8 M

 docker-common           x86_64 2:1.13.1-75.git8633870.el7.centos

                                                           RHEL-76-x86_64  93 k

 libsemanage-python      x86_64 2.5-14.el7                 RHEL-76-x86_64 113 k

 oci-register-machine    x86_64 1:0-6.git2b44233.el7       RHEL-76-x86_64 1.1 M

 oci-systemd-hook        x86_64 1:0.1.17-2.git83283a0.el7  RHEL-76-x86_64  33 k

 oci-umount              x86_64 2:2.3.3-3.gite3c9055.el7   RHEL-76-x86_64  32 k

 policycoreutils-python  x86_64 2.5-29.el7_6.1             RHEL-76-x86_64-updates

                                                                          456 k

 python-pytoml           noarch 0.1.14-1.git7dea353.el7    RHEL-76-x86_64  18 k

 setools-libs            x86_64 3.3.8-4.el7                RHEL-76-x86_64 620 k

 skopeo-containers       x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos

                                                           RHEL-76-x86_64  17 k

 subscription-manager-rhsm-certificates

                         x86_64 1.21.10-3.el7_6            RHEL-76-x86_64 212 k

Updating for dependencies:

 audit                   x86_64 2.8.4-4.el7                RHEL-76-x86_64 250 k

 audit-libs              i686   2.8.4-4.el7                RHEL-76-x86_64 101 k

 audit-libs              x86_64 2.8.4-4.el7                RHEL-76-x86_64 100 k

 libselinux              i686   2.5-14.1.el7               RHEL-76-x86_64 166 k

 libselinux              x86_64 2.5-14.1.el7               RHEL-76-x86_64 162 k

 libselinux-devel        x86_64 2.5-14.1.el7               RHEL-76-x86_64 187 k

 libselinux-python       x86_64 2.5-14.1.el7               RHEL-76-x86_64 236 k

 libselinux-utils        x86_64 2.5-14.1.el7               RHEL-76-x86_64 152 k

 libsemanage             x86_64 2.5-14.el7                 RHEL-76-x86_64 151 k

 libsepol                i686   2.5-10.el7                 RHEL-76-x86_64 294 k

 libsepol                x86_64 2.5-10.el7                 RHEL-76-x86_64 297 k

 libsepol-devel          x86_64 2.5-10.el7                 RHEL-76-x86_64  77 k

 policycoreutils         x86_64 2.5-29.el7_6.1             RHEL-76-x86_64-updates

                                                                          916 k




Transaction Summary

================================================================================

Install  1 Package  (+16 Dependent packages)

Upgrade             ( 13 Dependent packages)




Total size: 26 M

Total download size: 23 M

Is this ok [y/d/N]: y

Downloading packages:







(1/17): atomic-registries-1.22.1-25.git5a342e3.el7.centos. |  35 kB   00:00    

(2/17): container-storage-setup-0.11.0-2.git5eaf76c.el7.no |  35 kB   00:00    

(3/17): audit-libs-python-2.8.4-4.el7.x86_64.rpm           |  76 kB   00:00    

(4/17): container-selinux-2.68-1.el7.noarch.rpm            |  36 kB   00:00    

(5/17): checkpolicy-2.5-8.el7.x86_64.rpm                   | 295 kB   00:00    

(6/17): docker-common-1.13.1-75.git8633870.el7.centos.x86_ |  93 kB   00:00    

(7/17): docker-client-1.13.1-75.git8633870.el7.centos.x86_ | 3.8 MB   00:01    

(8/17): oci-systemd-hook-0.1.17-2.git83283a0.el7.x86_64.rp |  33 kB   00:00    

(9/17): oci-register-machine-0-6.git2b44233.el7.x86_64.rpm | 1.1 MB   00:00    

(10/17): oci-umount-2.3.3-3.gite3c9055.el7.x86_64.rpm      |  32 kB   00:00    

(11/17): python-pytoml-0.1.14-1.git7dea353.el7.noarch.rpm  |  18 kB   00:00    

(12/17): setools-libs-3.3.8-4.el7.x86_64.rpm               | 620 kB   00:00    

(13/17): skopeo-containers-0.1.31-1.dev.gitae64ff7.el7.cen |  17 kB   00:00    

(14/17): subscription-manager-rhsm-certificates-1.21.10-3. | 212 kB   00:00    

(15/17): libsemanage-python-2.5-14.el7.x86_64.rpm          | 113 kB   00:02    

(16/17): policycoreutils-python-2.5-29.el7_6.1.x86_64.rpm  | 456 kB   00:00    

(17/17): docker-1.13.1-75.git8633870.el7.centos.x86_64.rpm |  16 MB   00:10    

--------------------------------------------------------------------------------

Total                                              2.1 MB/s |  23 MB  00:11    




Running transaction check

Running transaction test

Transaction test succeeded

Running transaction




  Updating   : libsepol-2.5-10.el7.x86_64                                  1/43

  Updating   : libselinux-2.5-14.1.el7.x86_64                              2/43

  Updating   : audit-libs-2.8.4-4.el7.x86_64                               3/43

  Updating   : libsemanage-2.5-14.el7.x86_64                               4/43

  Updating   : libselinux-utils-2.5-14.1.el7.x86_64                        5/43

  Updating   : policycoreutils-2.5-29.el7_6.1.x86_64                       6/43

  Installing : libsemanage-python-2.5-14.el7.x86_64                        7/43

  Installing : audit-libs-python-2.8.4-4.el7.x86_64                        8/43

  Installing : setools-libs-3.3.8-4.el7.x86_64                             9/43

  Installing : 2:oci-umount-2.3.3-3.gite3c9055.el7.x86_64                 10/43

  Installing : 1:oci-systemd-hook-0.1.17-2.git83283a0.el7.x86_64          11/43

  Updating   : libselinux-python-2.5-14.1.el7.x86_64                      12/43

  Updating   : libsepol-devel-2.5-10.el7.x86_64                           13/43

  Installing : subscription-manager-rhsm-certificates-1.21.10-3.el7_6.x   14/43

  Installing : 1:oci-register-machine-0-6.git2b44233.el7.x86_64           15/43

  Installing : python-pytoml-0.1.14-1.git7dea353.el7.noarch               16/43

  Installing : 1:atomic-registries-1.22.1-25.git5a342e3.el7.centos.x86_   17/43

  Installing : checkpolicy-2.5-8.el7.x86_64                               18/43

  Installing : policycoreutils-python-2.5-29.el7_6.1.x86_64               19/43

  Installing : 2:container-selinux-2.68-1.el7.noarch                      20/43

  Installing : 1:skopeo-containers-0.1.31-1.dev.gitae64ff7.el7.centos.x   21/43

  Installing : container-storage-setup-0.11.0-2.git5eaf76c.el7.noarch     22/43

  Installing : 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64     23/43

  Installing : 2:docker-client-1.13.1-75.git8633870.el7.centos.x86_64     24/43

  Updating   : libsepol-2.5-10.el7.i686                                   25/43

  Installing : 2:docker-1.13.1-75.git8633870.el7.centos.x86_64            26/43

  Updating   : libselinux-devel-2.5-14.1.el7.x86_64                       27/43

  Updating   : audit-2.8.4-4.el7.x86_64                                   28/43

  Updating   : libselinux-2.5-14.1.el7.i686                               29/43

  Updating   : audit-libs-2.8.4-4.el7.i686                                30/43

  Cleanup    : policycoreutils-2.5-22.el7.x86_64                          31/43

  Cleanup    : libselinux-devel-2.5-12.el7.x86_64                         32/43

  Cleanup    : libsepol-devel-2.5-8.1.el7.x86_64                          33/43

  Cleanup    : libselinux-2.5-12.el7                                      34/43

  Cleanup    : libsemanage-2.5-11.el7.x86_64                              35/43

  Cleanup    : libselinux-utils-2.5-12.el7.x86_64                         36/43

  Cleanup    : libselinux-python-2.5-12.el7.x86_64                        37/43

  Cleanup    : libselinux-2.5-12.el7                                      38/43

  Cleanup    : audit-2.8.1-3.el7_5.1.x86_64                               39/43

  Cleanup    : libsepol-2.5-8.1.el7                                       40/43

  Cleanup    : audit-libs-2.8.1-3.el7_5.1                                 41/43

  Cleanup    : audit-libs-2.8.1-3.el7_5.1                                 42/43

  Cleanup    : libsepol-2.5-8.1.el7                                       43/43

  Verifying  : 2:docker-common-1.13.1-75.git8633870.el7.centos.x86_64      1/43

  Verifying  : 2:container-selinux-2.68-1.el7.noarch                       2/43

  Verifying  : container-storage-setup-0.11.0-2.git5eaf76c.el7.noarch      3/43

  Verifying  : policycoreutils-2.5-29.el7_6.1.x86_64                       4/43

  Verifying  : 1:skopeo-containers-0.1.31-1.dev.gitae64ff7.el7.centos.x    5/43

  Verifying  : libselinux-2.5-14.1.el7.i686                                6/43

  Verifying  : checkpolicy-2.5-8.el7.x86_64                                7/43

  Verifying  : audit-libs-2.8.4-4.el7.x86_64                               8/43

  Verifying  : audit-2.8.4-4.el7.x86_64                                    9/43

  Verifying  : 2:docker-client-1.13.1-75.git8633870.el7.centos.x86_64     10/43

  Verifying  : python-pytoml-0.1.14-1.git7dea353.el7.noarch               11/43

  Verifying  : setools-libs-3.3.8-4.el7.x86_64                            12/43

  Verifying  : policycoreutils-python-2.5-29.el7_6.1.x86_64               13/43

  Verifying  : libsemanage-python-2.5-14.el7.x86_64                       14/43

  Verifying  : libsemanage-2.5-14.el7.x86_64                              15/43

  Verifying  : 1:oci-register-machine-0-6.git2b44233.el7.x86_64           16/43

  Verifying  : 2:oci-umount-2.3.3-3.gite3c9055.el7.x86_64                 17/43

  Verifying  : libsepol-2.5-10.el7.x86_64                                 18/43

  Verifying  : audit-libs-2.8.4-4.el7.i686                                19/43

  Verifying  : libsepol-2.5-10.el7.i686                                   20/43

  Verifying  : 1:oci-systemd-hook-0.1.17-2.git83283a0.el7.x86_64          21/43

  Verifying  : libsepol-devel-2.5-10.el7.x86_64                           22/43

  Verifying  : 1:atomic-registries-1.22.1-25.git5a342e3.el7.centos.x86_   23/43

  Verifying  : libselinux-python-2.5-14.1.el7.x86_64                      24/43

  Verifying  : audit-libs-python-2.8.4-4.el7.x86_64                       25/43

  Verifying  : libselinux-utils-2.5-14.1.el7.x86_64                       26/43

  Verifying  : subscription-manager-rhsm-certificates-1.21.10-3.el7_6.x   27/43

  Verifying  : libselinux-devel-2.5-14.1.el7.x86_64                       28/43

  Verifying  : 2:docker-1.13.1-75.git8633870.el7.centos.x86_64            29/43

  Verifying  : libselinux-2.5-14.1.el7.x86_64                             30/43

  Verifying  : libsemanage-2.5-11.el7.x86_64                              31/43

  Verifying  : libselinux-python-2.5-12.el7.x86_64                        32/43

  Verifying  : libsepol-devel-2.5-8.1.el7.x86_64                          33/43

  Verifying  : policycoreutils-2.5-22.el7.x86_64                          34/43

  Verifying  : audit-2.8.1-3.el7_5.1.x86_64                               35/43

  Verifying  : libsepol-2.5-8.1.el7.x86_64                                36/43

  Verifying  : libselinux-2.5-12.el7.i686                                 37/43

  Verifying  : libselinux-devel-2.5-12.el7.x86_64                         38/43

  Verifying  : libsepol-2.5-8.1.el7.i686                                  39/43

  Verifying  : audit-libs-2.8.1-3.el7_5.1.x86_64                          40/43

  Verifying  : audit-libs-2.8.1-3.el7_5.1.i686                            41/43

  Verifying  : libselinux-2.5-12.el7.x86_64                               42/43

  Verifying  : libselinux-utils-2.5-12.el7.x86_64                         43/43




Installed:

  docker.x86_64 2:1.13.1-75.git8633870.el7.centos                              




Dependency Installed:

  atomic-registries.x86_64 1:1.22.1-25.git5a342e3.el7.centos                    

  audit-libs-python.x86_64 0:2.8.4-4.el7                                       

  checkpolicy.x86_64 0:2.5-8.el7                                               

  container-selinux.noarch 2:2.68-1.el7                                        

  container-storage-setup.noarch 0:0.11.0-2.git5eaf76c.el7                     

  docker-client.x86_64 2:1.13.1-75.git8633870.el7.centos                       

  docker-common.x86_64 2:1.13.1-75.git8633870.el7.centos                       

  libsemanage-python.x86_64 0:2.5-14.el7                                       

  oci-register-machine.x86_64 1:0-6.git2b44233.el7                             

  oci-systemd-hook.x86_64 1:0.1.17-2.git83283a0.el7                            

  oci-umount.x86_64 2:2.3.3-3.gite3c9055.el7                                   

  policycoreutils-python.x86_64 0:2.5-29.el7_6.1                               

  python-pytoml.noarch 0:0.1.14-1.git7dea353.el7                               

  setools-libs.x86_64 0:3.3.8-4.el7                                             

  skopeo-containers.x86_64 1:0.1.31-1.dev.gitae64ff7.el7.centos                

  subscription-manager-rhsm-certificates.x86_64 0:1.21.10-3.el7_6              




Dependency Updated:

  audit.x86_64 0:2.8.4-4.el7                                                    

  audit-libs.i686 0:2.8.4-4.el7                                                

  audit-libs.x86_64 0:2.8.4-4.el7                                              

  libselinux.i686 0:2.5-14.1.el7                                                

  libselinux.x86_64 0:2.5-14.1.el7                                             

  libselinux-devel.x86_64 0:2.5-14.1.el7                                       

  libselinux-python.x86_64 0:2.5-14.1.el7                                       

  libselinux-utils.x86_64 0:2.5-14.1.el7                                       

  libsemanage.x86_64 0:2.5-14.el7                                              

  libsepol.i686 0:2.5-10.el7                                                    

  libsepol.x86_64 0:2.5-10.el7                                                 

  libsepol-devel.x86_64 0:2.5-10.el7                                           

  policycoreutils.x86_64 0:2.5-29.el7_6.1                                      




Complete!



– Using an image for virtualization with the Docker software: After installing Docker you need to pull an existing image for virtualization. In this article we will use the image phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient:full

 

 

[root@oc8226237722 ~]# docker pull phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient:full

Trying to pull repository phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient ...

full: Pulling from phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient

4c851099615d: Pull complete

f22562ec5726: Pull complete

ecaf948a6376: Pull complete

0523cfba9a7b: Pull complete

5cc059e87718: Pull complete

40fde7f8968a: Pull complete

8257cc2c348c: Pull complete

006c509ee636: Pull complete

327ac893dadd: Pull complete

df8f385b3400: Pull complete

942ed172ad5e: Pull complete

000ecb121309: Pull complete

21ca946a8b49: Pull complete

585313811f7d: Pull complete

9472199e9ad7: Pull complete

53a7553bad7f: Pull complete

485560c4134a: Pull complete

e152e9eb3b79: Pull complete

464039b4cdc2: Pull complete

6910ba0139a1: Pull complete

1206d486d92c: Pull complete

Digest: sha256:490cf9de59a35c46cad5421a4013e91c09ea65e2bec07422d2a8c377c17123d1

Status: Downloaded newer image for phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient:full

 

Creating a directory to store the wallet file:

 

[root@oc8226237722 ~]# mkdir -p /tmp/wallet

 

Initialize the container while the wallet file directory is being created:

 

[root@oc8226237722 ~]# docker run -it -p 3050:3050 -v ~/tmp/wallet:/opt/oracle/techdatabasketvm/database/wallet  phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient:full /bin/bash

bash-4.2#

bash-4.2#


Checking the status of Docker: Some information about the command
  • docker info: Provides information about Docker software;
  • systemctl status docker.service: Checks the status of the Docker software;
  • systemctl start docker.service: Initializes the service if it is not initialized.
  • docker images -a: Provides information about existing virtualized images.

 

root@oc8226237722 ~]# docker info

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?




[root@oc8226237722 ~]# systemctl status docker.service
  • docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)

   Active: inactive (dead)

     Docs: http://docs.docker.com




[root@oc8226237722 ~]# docker images -a

REPOSITORY                                      TAG                                                   IMAGE ID            CREATED             SIZE

docker.io/docker                                latest                                          6742c45f63ej        5 days ago          171 MB

phx.ocir.io/oradbcloudtechdatabasket/openworld/atpclient:full   full                         338e9abb4e77        7 weeks ago         1.14 GB




[root@oc8226237722 ~]# systemctl start  docker.service




[root@oc8226237722 ~]# systemctl status docker.service
  • docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled)

   Active: active (running) since Thu 2019-04-04 12:10:31 CEST; 6s ago

     Docs: http://docs.docker.com

 Main PID: 30161 (dockerd-current)

    Tasks: 21

   CGroup: /system.slice/docker.service

           ├─30161 /usr/bin/dockerd-current --add-runtime docker-runc=/usr/libexec/docker/docker-runc-current --default-runtime=docker-runc --exec-opt native.cgroupdriver=systemd --userland-proxy-path=...

           └─30168 /usr/bin/docker-containerd-current -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/co...




Apr 04 12:10:29 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:29.654282057+02:00" level=info msg="libcontainerd: new containerd process, pid: 30168"

Apr 04 12:10:30 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:30.755627224+02:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"

Apr 04 12:10:30 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:30.756764713+02:00" level=info msg="Loading containers: start."

Apr 04 12:10:30 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:30.787906039+02:00" level=info msg="Firewalld running: true"

Apr 04 12:10:30 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:30.973371092+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16... IP address"

Apr 04 12:10:31 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:31.150353744+02:00" level=info msg="Loading containers: done."

Apr 04 12:10:31 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:31.194265410+02:00" level=info msg="Daemon has completed initialization"

Apr 04 12:10:31 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:31.194546603+02:00" level=info msg="Docker daemon" commit="8633870/1.13.1" graphdriver=overlay2 version=1.13.1

Apr 04 12:10:31 oc8226237722.techdatabasketblog.com dockerd-current[30161]: time="2019-04-04T12:10:31.202468424+02:00" level=info msg="API listen on /var/run/docker.sock"

Apr 04 12:10:31 oc8226237722.techdatabasketblog.com systemd[1]: Started Docker Application Container Engine.

Hint: Some lines were ellipsized, use -l to show in full.

 

 

So we finished the first part of the series of articles about Oracle Autonomous Database in Oracle Cloud for DevOps. In the next article we will continue with the provisioning of the database.

 

References:

 

https://www.oracle.com/database/autonomous-database.html
https://www.docker.com/

 

 

 

 

Bruno Reis da Silva is a Database Cloud Support Engineer and professionally Certified Oracle Database Administrator who has worked on the South American continent and is now working at the European continent. He was awarded the first Oracle Ace Associate of Hungary in 2017. His interests are in RDBMS, mainly Oracle, operating systems (Linux, AIX, HPUX and Solaris) and High Availability Solutions implementations. In his free time he enjoys playing sports , going to the gym and traveling. His blog www.techdatabasket.com is dedicated to his sister Laura Vitoria and the main reason for blogging is because he believes in the quote “giving back to get back” . He also enjoys continuous learning and the interaction with others who share his interest.

 

Carlos Magno de Andrade Júnior is an  Database Architect at eProseed Europe, with more than 15 years of experience in Oracle database on complex projects in countries such as Brazil , India , the Netherlands, Luxembourg , France and Italy, having worked in companies such as Oracle Corporation, IBM, HSBC, among others. Also shares information on his blog ezdba.wordpress.com. Certifications : OCM 12c OCP 10g , 11g OCP , OCP 12c, OCE RAC , Exadata , ITIL and OEM 12c Cloud Control Implementation Specialist.

 


Webniar – Patching Like a Hero
Category: Database Author: Andre Luiz Dutra Ontalba (Board Member) Date: 5 years ago Comments: 0

Webinar - Patching like a Hero

Hi guys !!

 

Yesterday we had our first Webinar and we are posting the webinar here for you.

 
 
Follow the link in the PDF presentation: Click here

 

 

 

See you next time.

André Ontalba – Board Member

 
 
 
 

1 … 24 25 26 27 28 … 32
LUXOUG – LUXEMBOURG ORACLE USERS GROUP
© 2024 LUXOUG – LUXEMBOURG ORACLE USERS GROUP