About Charles Kim

Oracle Multitenant plugin
the file names in the multitenant manifest or in the full transportable database import command must match all files exactly for the operation to complete

There are some difficulties when OMF/ASM is used, files are copied, and a physical standby database is in place. There have been improvements made to the multitenant plugin operation on both the primary and standby environments, however at this time additional work must still be done on the standby database when a full transportable database import operation is performed.

RMAN has been enhanced so that, when copying files between databases it recognizes the GUID and acts accordingly when writing the files.

* If the clone/auxiliary instance being connected to for clone operations is a CDB root, the GUID of the RMAN target database is used to determine the directory structure to write the datafiles. Connect to the CDB root as the RMAN clone/auxiliary instance when the source database should be a 12c non-CDB or PDB that is going to be migrated and plugged into a remote CDB as a brand new PDB. This will ensure that the files copied by RMAN will be written to the GUID directory of source database for the migration.

* If the clone/auxiliary instance being connected to for clone operations is a PDB, the GUID of the auxiliary PDB will be used to determine the directory structure to write the datafiles. Connect to the destination PDB as the RMAN clone auxiliary instance when the source database is a 12c non-CDB or PDB that requires a cross platform full transportable database import and the data and files will be imported into an existing PDB. This will ensure the files copied by RMAN will be written to the GUID directory of the PDB target database for the migration.

Posted in ASM

It’s time for the the annual IOUG Collaborate Conference again, April 7-11 in Las Vegas at the Venetian and Sands Expo Center.

We have a line up of great tracks and speakers focused on Cloud Computing, and this is a mini-compilation of the sessions focused on Cloud Tracks.

Enjoy and look forward to meeting everyone at Collaborate (#C14LV).

Best Wishes,

Charles Kim and the Cloud SIG Team (George, Bert, Kai, Ron, Steve).


Oracle’s Application Express platform (APEX) has emerged as the most compelling RAD platform available in the Oracle ecosystem. It is easy to learn, provides broadly useful functionality and is free to develop and use for existing Oracle customers. However, it has never been positioned as a “serious” development platform for mission critical enterprise (and certainly not commercial) product development. After all, it’s free and it doesn’t support Java. How important a platform could it be whose language underpinnings are SQL and PL/SQL? Why would I trust a platform for critical product development that’s not encouraged or even considered for such things by its own sales force?

Yet development trends are telling a different story. Organizations across industry boundaries and of every size and profile increasingly rely on APEX’s predictable ROI to create not just internal one-off applications and utilities but full-scale, enterprise-critical and even commercial cloud-based offerings.

Come to this session and see how we are leveraging APEX with FOEX as the preferred enterprise development tool and how it can be used to create compelling applications across full spectrums of criticality and enterprise expectation.


Book Title:
Successfully Virtualize Business Critical Oracle Databases

VMware iBook Cover

Here’s the book Description:
Written by VMware vExperts (Charles Kim (VCP), Viscosity North America, and George Trujillo (VCI), HortonWorks) and leading experts within VMware VCI and Learning Specialist (Steve Jones) and Chief Database Architect in EMC’s Global IT organization (Darryl Smith), this book will provide critical instructions for deploying Oracle Standalone and Real Application Cluster (RAC) on VMware enterprise virtualized platforms. You will learn how to setup an Oracle ecosystem within a virtualized infrastructure for enterprise deployments. We will share industry best practices to install and configure Linux, and to deploy Oracle Grid Infrastructure and Databases in a matter of hours. Whether you are deploying a 4 node RAC cluster or deploying a single standalone database, we will lead you to the foundation which will allow you to rapidly provision database-as-a-service. We will disseminate key details on creating golden image templates from the virtual machine to the Oracle binaries and databases. You will learn from industry experts how to troubleshoot production Oracle database servers running in VMware virtual infrastructures.

Audience:
Database Admins/Architects, VMware Admins, System Admins/Architects, Project Architects
This book designed for Oracle DBAs and VMware administrators needing to learn the art of virtualizing Oracle.


Posted by Charles Kim, Oracle ACE Director, VMware vExpert

We will review the basics of installing Red Hat Linux Enterprise 6 Update 4 for the Intel 64-bit platform in a virtualized infrastructure to prepare an environment to install an Oracle cluster and database(s). To simplify the process and to demonstrate package installation procedures, we will select the option to install the Basic Server and required packages to create a local yum repository from the installation media to install packages with dependencies.

If you have a Red Hat subscription, you can download RHEL 6 ISO image files from Red Hat’s Software & Download Center customer portal. If you do not already have a subscription, you can obtain a free 30 evaluation subscription from https://access.redhat.com/downloads. Each of the DVD ISO images are about 3-4 GB in size. After you download the ISO image, create a bootable DVD and USB and reboot the system to start the installation.

RHEL64_1.png
In the Boot Menu, if there is no response within 60 seconds, the default option to Install or upgrade an existing system using the GUI will be executed.

RHEL_2.png
You will be given the option to perform a disk check on the installation media. Click on Skip.

RHEL_3.png
The Welcome screen does not accept any actionable inputs to respond to. Click on Next to continue.

RHEL_4.png
Select the language preference to be used for the installation. Please choose English from this option and click on Next

Rhel keyboard
Please select the default U.S. English and click on Next

Rhel basic storage
Select the Basic Storage type and click on Next

Rhel storage device warning

Since this is a fresh install, click on Yes, discard any data button

Enter computer name

Add hostname for the node
Click on Configure Network
Click on Edit

Edit system eth0

Change the Method to Manual
Supply IP and Netmask
Click on Apply
Then click on Close
Then Click on Next

Enter time zone

Select your timezone
Click on Next

Enter root password

Enter the password for root
Click on Next

Weak password

If this is a non-development environment, you will want to choose a more secure password. Since this is my lab, I will choose to Click on Use Anyway and continue.

Installation

Click on Review and Modify partition layout
Click on Next

Select a device

Click on Create

Add a partition

Select /tmp for Mount Point
Enter 4096 for Size (MB)
Click on OK

Format warnings

Click on Format

Warning storage configuration

Click on Write changes to disk

Boot loader

Click Next from the Boot loader list screen

Basic server

Select Basic Server and click on Next
It will perform a dependency check and start to perform the installation

Packages completed

Congratulations

Let’s remount our DVD so that we can copy all the RPMs from the DVD to a centralized location on the file system:
Mount cd

In order to setup a local Yum repository, we need to install the createrepo package. The createrepo package has dependencies on two additional packages: deltarpm and python-deltarpm. To successfully install the createrepo package, we will invoke the rpm command with the -ihv option and provide the names of all three packages:
Rpm install

We have successfully installed the createrepo package. The next step will be to copy all the RPMs from the DVD to an area on the local file system. In my example, I am copying the files to the /tmp file system but you will want to select a more permanent location. After the files are copied, we will invoke the createrepo command and provide the location of the directory where the RPMs were copied to:
Createrepo

We have successfully created our local yum repository. Now we are ready to install and update packages with yum.