Change the security settings on Exadata with the script host_access_control

About three months ago I found a script named host_access_control.

The script provides the API to managing several host access and security settings. The script is available on Compute Nodes and Storage Cells since the Exadata Software Version 11.2.3.3.0. The utility is located in /opt/oracle.cellos/host_access_control. The script is not documented in the Exadata Documentation, but in the Super Cluster documentation.

The script called with the Option „-h“ displays the help:

Weiterlesen „Change the security settings on Exadata with the script host_access_control“
Werbeanzeigen

KVM Virtualization on top of the vmware workstation 12 guest vm‘s

Kernel-based Virtual Machine (KVM) provides a possibility to use the Oracle (or Redhat/CentOS) Linux kernel as a hypervisor.

In my example, I will configure the KVM virtualization on top of the guest vm running OEL 7.4. The guest VM is running on top of the VMWare Workstation 12.

To enable the virtualization layer select VM settings and navigate to the Processor settings. Enable the setting „Virtualize Intel VT-x/EPT or AMD-V/RVI.“

The Guest VM is now enabled for the using of the nested virtualization (such kvm). Start the Guest VM.

Install and configure KVM virtualization on the OEL 7.4 Linux

Weiterlesen „KVM Virtualization on top of the vmware workstation 12 guest vm‘s“

Extend Filesystem /u01 on an Exadata ComputeNode

Do you know the problem: an Exadata does not have enough space in filesystem /u01? The Exadata has the locale storage and you can increase /u01.

Steps:

1. Check filesystem and associated volume:

[root@myexadb01]# df -h

Filesystem                      Size    Used    Avail    Use%    Mounted on
/dev/mapper/VGExaDb-LVDbSys1     30G    23G    5.7G    80%    /
tmpfs                           757G    4.0K    757G    1%    /dev/shm
/dev/sda1                       488M    48M    405M    11%    /boot
/dev/mapper/VGExaDb-LVDbOra1    158G    107G    43G    72%    /u01

Check the free space in the volume group:

[root@myexadb01]# pvs
PV         VG        Fmt    Attr    PSize    PFree
/dev/sda2    VGExaDb   lvm2   a—u     1.63t    1.38t

Weiterlesen „Extend Filesystem /u01 on an Exadata ComputeNode“

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

Preface

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:          12.2.1.1.2.170714
DB node versioin:               12.2.1.1.2.170714
GI Version:                     12.1.0.2.170418
RDBMS Version:                  12.1.0.2.170418

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“

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“

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:

/u01/app/oracle/product/FMW/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 12.2.1.2

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 12.2.1.2“