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“

Save the Date: DOAG 2017 IMC (Infrastruktur-Middleware) Days

Am 07.09.2017 trifft sich die Middleware Community in Berlin, um spannenden Vorträgen zu lauschen und sich über aktuelle IT-Themen auszutauschen. Bekannte Referenten teilen ihre Erfahrungen in Themen rund um Oracle Middleware Administration mit und geben einen Überblick über die aktuellen Cloud Trends

Info und Agenda hier

Wir sehen uns in Berlin!


How to hide passwords and account information in WLST scripts (WebLogic Server)

If you are worried about your password showing up in clear text in the startup scripts, you can use the storeUserConfig command to generate encrypted userconfigFile and a userKeyFile that you can then use in the „nmConnect“ and „connect“ command.

Place there two files on the protected place and decide to set right permissions

Create storeUserConfig for the Node Manager

Start wlst via the shell script $ORACLE_HOME/oracle_common/common/bin/wlst.sh:


Weiterlesen „How to hide passwords and account information in WLST scripts (WebLogic Server)“

Advanced OHS Configuration in Oracle Forms

In this blog entry I will describe two topics:

  • Configuration OHS to listen on the Port 80
  • Configuration access to the AdminConsole / EM via HTTP Port

Configuration OHS to listen on the Port 80

After the initial installation of Forms is the OHS configured for the listening on the Port 7777. If you would change the listening to the Port 80 execute following steps

Change Permissions for the File launch (as root!!!):

chown root ${MIDDLEWAR_HOME}/Oracle_Home/ohs/bin/launch
chmod 4750 ${MIDDLEWAR_HOME}/Oracle_Home/ohs/bin/launch

Edit the file httpd.conf

Weiterlesen „Advanced OHS Configuration in Oracle Forms“