Search

Top 60 Oracle Blogs

Recent comments

February 2018

Post GI / RDBMS Installation Configuration Steps

Introduction

This is the third article in a series of blog posts on building a test environment to closely match a Production environment so we could then upgrade the test environment from Oracle Database 12.1 to Oracle Database 12.2. In the first post, I covered performing a silent installation of the grid infrastructure software. In the second post, I followed that by performing a similar silent installation of the RDBMS software. In this post, I’ll be covering the rest of the configuration work for this environment.

Docker and Windows 10 with 1709 Patch aka Killing Me Slowly

So I transitioned in the last years from having a development lab, to VMs, to the cloud and now, tired of slow WiFi, been happily using Docker for most of my demos.  As of January, the latest upgrade to Windows 10, aka patch version 109, has been like a bad cat fight.

Silent Installation of the RDBMS

Introduction

In my last post, I walked you through the silent installation of the Grid Infrastructure software. In this post, we’re moving on to the next stage of the environment build for this customer, doing a silent installation of the RDBMS software.

RDBMS Installation

The silent installation of the RDBMS software is fairly similar to that of the Grid Infrastructure software. You create a response file that contains the responses you would normally provide interactively, and use that with the runInstaller program to perform the installation. The response file I used for that is as follows:

Silent Installation of the RDBMS

Introduction

In my last post, I walked you through the silent installation of the Grid Infrastructure software. In this post, we’re moving on to the next stage of the environment build for this customer, doing a silent installation of the RDBMS software.

RDBMS Installation

The silent installation of the RDBMS software is fairly similar to that of the Grid Infrastructure software. You create a response file that contains the responses you would normally provide interactively, and use that with the runInstaller program to perform the installation. The response file I used for that is as follows:

Silent Installation of Grid Infrastructure

Introduction

Recently I had a requirement to install the Grid Infrastructure and Oracle RDBMS on a completely new VM. The customer I was doing this work for wanted to take a copy of their Production environment to another server so they could test an upgrade of their existing environment from Oracle GI / RDBMS 12.1 to 12.2. So they built a VM for me, copied the 12.1 installation media for both GI and the RDBMS and said “Go for it!”

I decided to log everything I did and write a series of blog posts based on my experience, in case it was of use to others. There were a few issues I needed to deal with for this customer. Some of those issues were:

Silent Installation of Grid Infrastructure

Introduction

Recently I had a requirement to install the Grid Infrastructure and Oracle RDBMS on a completely new VM. The customer I was doing this work for wanted to take a copy of their Production environment to another server so they could test an upgrade of their existing environment from Oracle GI / RDBMS 12.1 to 12.2. So they built a VM for me, copied the 12.1 installation media for both GI and the RDBMS and said “Go for it!”

I decided to log everything I did and write a series of blog posts based on my experience, in case it was of use to others. There were a few issues I needed to deal with for this customer. Some of those issues were:

12cR2 PDB archive

In 12.1 we had the possibility to unplug a PDB by closing it and generating a .xml file that describes the PDB metadata required to plug the datafiles into another CDB.
In 12.2 we got an additional possibility to have this .xml file zipped together with the datafiles, for an easy transport. But that was not working for ASM files.
The latest Release Update, Oct 17 includes the patch that fixes this issue and is the occasion to show PDB archive.

Here is Oracle 12.2.0.1 with Oct 2017 (https://updates.oracle.com/download/26737266.html) applied (needs latest OPatch https://updates.oracle.com/download/6880880.html)
With a PDB1 pluggable database:

[oracle@VM106 ~]$ rman target /
 

Extending a Logical Volume Group

Introduction

Today I ran into the situation where I needed to extend a logical volume group so I could complete an installation. I’d already installed the Grid Infrastructure, but there wasn’t enough room remaining to install the Oracle kernel on the same device. This is for a test environment which was being built on a VM that had just been created, and performance is not the issue we’re looking at here, so installing the Grid Infrastructure and RDBMS on the same device is not a concern for me. I’ve been around the Oracle database for way too many years, but my sysadmin skills leave a lot to be desired, so I did what anyone in this situation would do – I googled “resize volume linux” and followed someone else’s instructions.

Extending a Logical Volume Group

Introduction

Today I ran into the situation where I needed to extend a logical volume group so I could complete an installation. I’d already installed the Grid Infrastructure, but there wasn’t enough room remaining to install the Oracle kernel on the same device. This is for a test environment which was being built on a VM that had just been created, and performance is not the issue we’re looking at here, so installing the Grid Infrastructure and RDBMS on the same device is not a concern for me. I’ve been around the Oracle database for way too many years, but my sysadmin skills leave a lot to be desired, so I did what anyone in this situation would do – I googled “resize volume linux” and followed someone else’s instructions.

RMOUG Training Days 2018

So Training Days is coming up in two weeks.  You haven’t registered to attend?  How you feeling about that?

Rocky Mountain Oracle User Group, (RMOUG) has the largest Oracle user group grassroots conference each February.  For the 2018 year, we decided to shake it up with: