Every cloud administrator wants to administer and monitor their cloud resources from a central location. The Cloud (OCI) Command-Line interface OCI CLI enables this. In this blog post I will describe the installation and configuration of the Cloud CLI on an Linux Server with OS Oracle Enterprise Linux.
To install and use the Cloud CLI you must have the following data:
OCI User: Users for connecting to cloud services
A SSH Keypair used for signing API requests, with the public key uploaded to Oracle OCI
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.
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): 126.96.36.199.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
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.