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): 12.2.0.1.0 

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

Primary ORACLE_SID/DB_UNIQUE_NAME: ORCL1/ORCL1PRM 

Standby ORACLE_SID/DB_UNIQUE_NAME: ORCL1/ORCL1STB 

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

Blueprint:

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

Introduction

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!

 

Oracle Forms & Reports 12.2.1.2.0: Create and Configure on the OEL 7.2 Server

Introduction

This post focuses on the creation, configuration and tuning of an initial Forms & Reports 12.2.1.2.0 Domain on the OEL 7.2 Server.

The WebLogic Server is a necessary requirement, and must already be installed. For instruction how to install the WebLogic Server 12.2.1.2 please refer to my previous post: WebLogic Server 12.2.1.2.0: Installation on the Linux OEL 7: step by step instruction

The following tasks will be implemented:

  • Preparing the Operating System for the installation of the WebLogic Server 12.2.1.2, Installation JDK 1.8 and the WebLogic Server 12.2.1.2:
  • Creating of database schemas
  • Installing and Configuring a Forms & Reports Domain
  • Post-Installation Tasks:
    • Configuring of components
    • Creating of Start & Stop scripts for the automatic start/stop of components
  • Tuning and Troubleshooting

The Domain will be created on the one OEL 7.2 server: host03.example.com (IP 192.168.75.35)

Installation Forms & Reports 12.2.1.2

Weiterlesen „Oracle Forms & Reports 12.2.1.2.0: Create and Configure on the OEL 7.2 Server“

DOAG Conference 2016

the DOAG conference will happen this year again, from 15.11.2016 to 17.11.2016 in Nuremberg. My colleagues Sven Bernhardt, Mohammad Esad-Djou, Stefan Seck and myself are scheduled to do three presentations:

We are looking forward to seeing you all there!

SOA Suite 12.2.1.1.0: Create, configure and tune a SOA/OSB Domain

Introduction

This post focuses on the creation, configuration and tuning of an initial SOA Suite 12.2.1.1.0 Domain.

The WebLogic Server is a necessary requirement, and must already be installed. For instruction how to install the WebLogic Server 12.2.1.1 please refer to my previous post:  WebLogic Server 12.2.1.1.0: Installation on the Linux OS

The following tasks will be implemented:

  • Preparing the Operating System for the installation of the WebLogic Server 12.2.1.1, Installation JDK 1.8 and the WebLogic Server 12.2.1.1: WebLogic Server 12.2.1.1.0: Installation on the Linux OS
  • Creating of database schemas
  • Creating a SOA Suite Domain
  • Post-Installation Tasks:
    • Configuring of components
    • Creating of Start & Stop scripts for the automatic start/stop of components
  • SOA Suite Domain Tuning and Troubleshooting

The SOA/OSB Domain will be installed without BAM (different Domain) because of:

–    Oracle Best Practices and our experience

–    In order to stabilize the system (BAM is unstable at the moment)

The Domain will be created on two servers (OS OEL 6.7):

  • host01.example.com
  • host02.example.com

We will configure four clusters:

  • OWSM Cluster (Oracle Web Services Management)
  • ESS Cluster (Enterprise Scheduler Services)
  • SOA Cluster
  • OSB Cluster (Oracle Service Bus)

Installation SOA / OSB 12.2.1.1

Note: All tasks described in this chapter must be running on both servers: host01 and host02

Weiterlesen „SOA Suite 12.2.1.1.0: Create, configure and tune a SOA/OSB Domain“