Part 2: Create the Oracle APEX Database in Amazon Relation Data Service (RDS)

This is the second part of my blog series about the installation and configuration an APEX database in the Amazon Cloud. Refer to following posts for the explanation of the whole solution:

Create the Virtual Private Cloud (Network) in AWS

At first, I will create my customer network in AWS.

In the AWS Console navigate to VPC and click on „Create VPC“. Specify the IPv4 IP Range (CIDR Block) and try „Create“:

Weiterlesen „Part 2: Create the Oracle APEX Database in Amazon Relation Data Service (RDS)“

Create Oracle APEX Environment in the Amazon Cloud with RDS: Part 1 – Overview

In this article I will describe the installation of APEX Environment in Amazon Web Service (AWS).

The whole environment includes following components:

  • AWS RDS: Oracle Database with activated APEX
  • VM (EC2 Container) with:
    • Oracle Rest Data Service (ORDS)
    • Apache Tomcat for the Hosting of the ORDS
    • Nginx: http Server

The major challenge is to install APEX without SYSDBA privilege, because the Oracle Database in the RDS is Vendor-Managed. Users cannot access the OS and do not have the database DBA role.

Blue Print of the APEX environment in the AWS:

In my next Posts I will cover the following topics:

Part 2: Create the APEX Database in Amazon Relation Data Service (RDS)

Part 3: Configure APEX with Oracle Rest Data Service (ORDS) in the new EC2 Container

Part 4: Configuration APEX with ORDS, Apache-Tomcat und Nginx

Cloud Control: the Graph in the Performance Top Activity view shrinks to left

Some time I have the problem with the vies of the Top Activity Page in the Cloud Control:

The Graf shrink to left and you can see only the part of the picture:

Weiterlesen „Cloud Control: the Graph in the Performance Top Activity view shrinks to left“

Upgrade Grid Infrastructure 12.1 to 12.2 + Install the 2017 August Release Update (RU) on Exadata


This document describes the upgrade of the GI from 12.1 to 12.2 with installation of the RU August 2017.

The Exadata consists of:

  • Two db nodes: exadb1/exadb2
  • Three cell servers

The software release of Exadata components:

Infiniband Software version:    2.2.6-2 (Juli 2017)
Storage cells version:
DB node versioin:     
GI Version:           
RDBMS Version:        

The order of the action:

  • Out of the place installation of the Grid Infrastructure 12.2 on all database servers
  • Installation RU Patch August 2017 on all database servers
  • Upgrade Gird Infrastructure to 12.2

Weiterlesen „Upgrade Grid Infrastructure 12.1 to 12.2 + Install the 2017 August Release Update (RU) on Exadata“

Steps to configure Oracle Data Guard 12.2 for non-multitenant database

This document describes the configuration of the Oracle Data Guard Version 12.2. We will configure a standby for a non-multitenant database.

Our test environment consists of two Linux (OEL 7.3) servers: oradg1 and oradg2. I already created the non-multitenant database on the server oradg1. We will configure the standby database on the server oradg2. We will use a new feature of 12.2 by creating a physical standby via dbca – oracle database creation assistant.

Environment overview:

Primary server name/os: oradg1/Oracle Linux Server 7.3 (64 bit)

Standby server name/os: oradg2/Oracle Linux Server 7.3 (64 bit) 

RDBMS Version (primary and standby): 

ORACLE_HOME (primary and standby): /u01/app/oracle/product/12.2.0/dbhome_1 



Listener name/port (primary and standby): LISTENER/1521 

Path to DB files (primary and standby): /u01/app/oracle/oradata/orcl1 

Recovery area (primary and standby): /u01/app/oracle/fast_recovery_area/orcl1


Preparing the primary database

Weiterlesen „Steps to configure Oracle Data Guard 12.2 for non-multitenant database“

How to configure the WebLogic AdminServer for High Availability


The high availability of applications in the WebLogic environment is realized by clustering. Managed servers in the cluster work together. The information about transactions is distributed cluster-wide. If a cluster member fails, another server takes over the tasks of the failed server and executes them. In this way, the applications are kept running without interruption.

The AdminServer is a single point of failure: if the server fails, the Domain is no longer administrable:

– Configuration changes cannot be performed

– The administration console is not available

The managed servers are still running and can continue to work, even if the AdminServer is not available: this requires the activation of MSI (Managed Server Independence) Mode.

How can the AdminSevrer be protected from failure? In this blogpost I will describe all the steps that are necessary to keep your server running safely.

Weiterlesen „How to configure the WebLogic AdminServer for High Availability“