Oracle Database Deployment Using IBM Wave For ZVM

Oracle Database deployment using IBM
Wave for zVM

Installing Oracle in a private cloud with an IBM Wave script
. . . . . . . .
Terry Elliott
IBM Oracle International Competency Center
April 2015
© Copyright IBM Corporation, 2015. All Rights Reserved.

All trademarks or registered trademarks mentioned herein are the property of their respective holders
Table of contents
Abstract ........................................................................................................................................1
Introduction .................................................................................................................................1
Oracle Database install preliminary work .................................................................................1
IBM Wave configuration ........................................................................................................................... 2
IBM Wave RH65GOLD prototype ............................................................................................................ 5
Create CLONEORA as the base Linux image ......................................................................................... 6
Update CLONEORA Linux image ..............................................................................................8
Add Linux user/groups ............................................................................................................................. 8
Add swap space....................................................................................................................................... 8
Verify/add prerequisite RPMs ................................................................................................................ 12
Verify/add/change Linux kernel parameters .......................................................................................... 12
NFS mount the Oracle Database 12c libraries ...................................................................................... 13
Use dirmaint to add two 5GB mdisks..................................................................................................... 13
Create UDEV entries for the two mdisks ............................................................................................... 14
Add oracle user to /etc/sudoers ............................................................................................................. 15
Miscellaneous ........................................................................................................................................ 15
Run CLUVFY ......................................................................................................................................... 15
Add Oracle Restart install script ............................................................................................................ 15
Response files ....................................................................................................................................... 19
Deactivate CLONEORA ......................................................................................................................... 22
Oracle Database install using IBM Wave ................................................................................23
Clone “CLONEORA” .............................................................................................................................. 24
Oracle silent install using IBM Wave script ............................................................................................ 27
Summary ....................................................................................................................................30
Resources ..................................................................................................................................31
About the author .......................................................................................................................32
Trademarks and special notices ..............................................................................................33
Oracle Database deployment using IBM Wave for zVM

http://www.ibm.com/support/techdocs
© Copyright 2015, IBM Corporation
Abstract
With IBM Wave for z/VM® (IBM Wave), IT organizations can unleash the power of z/VM
virtualization, improve productivity, simplify management, and accelerate the cloud journey with
innovative technology that helps reduce the barriers to management of virtualized environments.
IBM Wave allows IT organizations and service providers to transform administration and operations
with an innovative graphical, content-rich approach for managing z/VM and Linux® virtual servers.
IBM Wave is designed to simplify operations, drive productivity, and extend the reach of existing
technical skills. IBM Wave makes administration highly intuitive by shielding staff from operational
complexity. In addition, IBM Wave also helps with cloning and provisioning of virtual servers and
resources, accelerating the journey to a private cloud infrastructure on IBM z Systems™ using z/VM.
Additional IBM Wave details are available in the documents listed in the Resources section.
In this paper IBM Wave is used to clone a Linux system on z/VM followed by using an IBM Wave
script to install an Oracle Database. The prerequisites for an Oracle Database 12c installation are
added to this newly cloned Linux environment. After the prerequisites are done, the Linux system is
shutdown (deactivated in IBM Wave terms). This deactivated Linux environment that has the Oracle
prerequisites is then the basis for the Linux clones that are used to install the Oracle Database. This
two-step clone process is used so that no modifications need to be made to the original Linux image
and also leave a Linux image available that contains the prerequisites for an Oracle Database
installation. The final step is using a Wave script to do a silent Oracle Database installation on the
Linux clone.
Introduction
The discussion that follows describes details of the steps that were done to install an Oracle Database in
silent mode on Linux using an IBM Wave script. The method uses Oracle Automatic Storage
Management (ASM) as storage for the Oracle Database. To use ASM the Oracle Grid Infrastructure for a
standalone server which includes both Oracle Restart and Oracle ASM is installed into an Oracle Restart
home. After this is done the Oracle Database binaries are installed into an Oracle Database home. Once
these two steps have been completed, the Oracle Database Configuration Assistant (DBCA) is used to
build an Oracle Database 12c multitenant database. The majority of the effort involved is preparing the
Linux image that has all the prerequisites required for the Oracle Database installation. Note that this is a
one-time effort and the Linux image will remain available and it can be cloned in minutes for subsequent
Oracle Database installs. The key is that the Linux image used as the source for the clones will have all
the prerequisites installed.
Oracle Database install preliminary work

This section provides a brief introduction to IBM Wave. IBM Wave is used to clone Linux and the cloned
Linux image is activated and the Oracle Database prerequisites are added to it. This Linux image can be
cloned many times and each time the clone will contain the Oracle Database prerequisites so that Oracle
Database can be immediately installed.

1
IBM Wave configuration
For this paper an IBM Wave system is available and is accessible with a browser at the site:
wavesrv.cmo-demo. The IBM Wave configuration has a Red Hat 6.5 Linux prototype already setup at this
site. Some of the initial wave screens will be shown in this section.
This first IBM Wave screen is displayed below.
Figure 1: IBM Wave initial screen
The last two selections on the initial wave screen provide access to IBM Wave online documentation. The
second selection provides a method to test the connection to target z/VM systems.
For this paper “Launch IBM Wave v1.1.0” is selected to access the IBM Wave login screen shown below.

2
Figure 2: IBM Wave login
There are several user settings and preferences available in IBM Wave and they are described in the IBM
Wave documentation. References to the documentation are in the Resources section of this paper.
For the login above, “waveadm” is an IBM Wave super-user. After logging on, the Wave screen shown
below is presented.

3
Figure 3: Initial IBM Wave graphical view
This is an IBM Wave graphical view for a single z/VM image. This is a very busy screen, but there is an
excellent description of the details on this screen on page 62 in the IBM Redbook “IBM Wave for z/VM
Installation, Implementation, and Exploitation”. The Redbook reference is in the Resources section.
The red and yellow on the screen above are IBM Wave graphical threshold indicators of things that
probably deserve a closer look. The red and yellow indicators don’t interfere with what is being done in
this paper, but for the curious, these things are:
1. There are no FCP devices available to z/VM.
2. The spool is 95% full.
3. Wave can’t determine the default NIC for one of the networks. IBM Wave has “Threshold
parameters” that can be set at red and yellow levels to indicate when resources need
attention.
One of the tabs in the screen above is “Prototypes”. The IBM Wave documentation details how to create
a Linux prototype. Selecting the prototypes tab will allow access to the Linux prototype that will be cloned
in the next section.

4
IBM Wave RH65GOLD prototype
From the discussion above, the prototype tab is selected and it discloses the RH65GOLD prototype that
will be cloned to create a new Linux environment. The screen below is only part of the actual IBM Wave
screen. This has been done so that the relevant parts of the screen can be enlarged to be readable in this
document. A right click has already been done on the Linux image to get the popup to display.
Figure 4: Part of IBM Wave screen showing RH65GOLD prototype
The z/VM system has a guest LAN that is RACF® protected. To get the clone process to be successful
the following RACF commands are issued before attempting the clone of RH65GOLD. The name of the
new Linux clone is “cloneora”.
rac au (cloneora) pass(xxxxxx) owner(ibmuser) dfltgrp(sys1) name(clone)
Ready; T=0.01/0.01 20:06:38
rac pe system.lanvmc1 class(vmlan) id(cloneora) access(alter)
Ready; T=0.01/0.01 20:07:34
Ready(00108); T=0.01/0.01 20:07:48
rac du (cloneora)
Ready; T=0.01/0.01 20:08:09
Listing 1: RACF Commands to enable access to guest LAN
The z/VM system used here had a guest LAN setup, however, the preferred network as stated in the IBM
redbook “Advanced Networking Concepts Applied Using Linux on IBM System z” is the virtual switch.

5
The three RACF commands above create a RACF user, permit the user access to the z/VM guest LAN,
and then delete the user. Deleting the user doesn’t remove the ID from access to the guest LAN, but it
allows the user to be created by dirmaint when the IBM Wave clone process is done.
After running the RACF commands, clicking “Clone From This Prototype” as in Figure 4 above results in
the initial clone screen in Figure 5 below.
Create CLONEORA as the base Linux image
Figure 5: Configuration for the CLONEORA Linux image
The new clone name, password, and storage group were entered on the screen and then “Update” was
clicked to save the information. The “Optional Configuration” tab was also used in the bottom part of the
screen to set the domain name and specify that the ssh keys be regenerated. Once this had been done,
“Go” was clicked on the bottom right of the screen. This starts the cloning process. When the “Cancel”
button changes to “Close” it is clicked to return to the prototype screen.
On the current configuration it takes approximately three (3) minutes for IBM Wave to create the Linux
system CLONEORA.

6
Returning to the IBM Wave z/VM User Groups display, inserting cloneora next to the “tag” button, and
clicking the tag button results in the cloneora linux guest being highlighted. Further, a right click on the
cloneora icon brings up an action list for cloneora.
Figure 6. CLONEORA before activation
After the right click on the picture, clicking “Activate” and doing additional steps of selecting “Go” and “OK”
CLONEORA is booted. As soon as it boots the Linux system CLONEORA is available at 192.168.150.7.
This is the IP address from Figure 5 above. The IBM Wave graphic for CLONEORA now looks like this.
Figure 7: CLONEORA is activated

7
Update CLONEORA Linux image
The next several steps will install the prerequisites on CLONEORA that are required for an Oracle
Database install. However, the Oracle Database will not be installed on CLONEORA. Once CLONEORA
has all the prerequisites it will be deactivated and used to create WAVEORAX clones. Then the IBM
Wave script that is installed with CLONEORA will be executed to install Oracle Restart on WAVEORAX.
The IBM Wave script that does the install is created as a global script so it can be executed by any user.
There is nothing unique about the WAVEORAX name other than that is the naming scheme adopted in
this paper. The database installation described later in this paper will be done on WAVEORA1.
This paper does not go into a lot of detail about the Oracle Database prerequisites, but documents
detailing the Oracle Database prerequisites can be found at: http://docs.oracle.com and at:
http://www.redbooks.ibm.com with specific references listed in the Resources section.
Add Linux user/groups

Linux groups oinstall and dba and user oracle are used for the Oracle Database installation. This is also
an Oracle Restart and ASM installation.
[root@CLONEORA ~]# groupadd asmoper
[root@CLONEORA ~]# groupadd oper
[root@CLONEORA ~]# groupadd oinstall
[root@CLONEORA ~]# groupadd dba
[root@CLONEORA ~]# useradd -g oinstall -G dba oracle
Listing 2: Add groups and oracle user
Add swap space

IBM Wave is used to create an ext4 file system. This is used for swap space for CLONEORA.

8
Figure 8: First step in adding an ext4 filesystem
Right click on CLONEORA then click more actions and click Manage Storage to get to the screen below.
Figure 9: Create a new partition

9
Figure 10: New filesystem configuration
After clicking Go and OK and waiting a couple of minutes for the 12GB to be formatted and mounted,
there is a 12GB ext4 filesystem mounted at /oratmp (wave created the mount point) and an entry has
been put into /etc/fstab.
The next step is to setup a 10GB swapfile at /oratmp. The IBM Wave User Preferences under the User
Tasks pull down in Figure 3 on page 4 have been updated so that cloneora can be accessed with PuTTY
directly from IBM Wave. Similar to what was done previously, but this time click on “Access” after right
clicking on cloneora, and the SSH Access appears as one of the options.

10
Figure 11: Access to PuTTY from IBM Wave
From here click on “SSH Access” and following screen appears to allow access to cloneora.
Figure 12: SSH access to cloneora
After logging in, continue with setting up a 10GB swapfile.

[root@CLONEORA ~]# cd /oratmp
[root@CLONEORA oratmp]# touch swapfile
[root@CLONEORA oratmp]# dd if=/dev/zero of=swapfile bs=1G count=10

11
10+0 records in
10+0 records out
10737418240 bytes (11 GB) copied, 224.491 s, 47.8 MB/s
[root@CLONEORA oratmp]# mkswap /oratmp/swapfile
mkswap: /oratmp/swapfile: warning: don't erase bootbits sectors
on whole disk. Use -f to force.
Setting up swapspace version 1, size = 10485756 KiB
no label, UUID=5ca0ed2f-7df9-4828-9df9-dc048a10c520
[root@CLONEORA oratmp]# swapon /oratmp/swapfile
[root@CLONEORA oratmp]# swapon -s
Filename Type Size Used Priority
/dev/dasda1 partition 079896 0 -1
/oratmp/swapfile file 10485752 0 -2
Listing 3: Setup 10GB swapfile
The swapfile will survive reboots with the entry, “/sbin/swapon /oratmp/swapfile”, added to
/etc/rc.d/rc.local.
[root@CLONEORA ~]# cat /etc/rc.d/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
/usr/wave/waveload
/sbin/swapon /oratmp/swapfile
Listing 4: Make swapfile available after a reboot
Verify/add prerequisite RPMs

The Oracle Note:1574413.1 “Requirements for Installing Oracle Database 12c Release 1 on RHEL 6 on
IBM: Linux on System z (s390x)” that is available on the “My Oracle Support” web site at:
https://support.oracle.com has information about Oracle prerequisites as well as an RPM checker that
can be down loaded. The RPM checker is used here to verify that all the prerequisites RPMs are installed
on CLONEORA.
[root@CLONEORA ~]# rpm -ivh ora-val-rpm-EL6-DB-12.1.0.1-1.s390x.rpm
Preparing... ########################################### [100%]
1:ora-val-rpm-EL6-DB ########################################### [100%]
****************************************************************************
* Validation complete - please install any missing rpms *
****************************************************************************
No missing RPMs are listed so CLONEORA has the prerequisites RPMs to install an Oracle Database.
Verify/add/change Linux kernel parameters

The referenced documentation has information about the kernel parameters and nothing further is added
here.

12
NFS mount the Oracle Database 12c libraries
The Oracle Database libraries are NFS mounted on CLONEORA. The libraries will not be used directly by
CLONEORA, but the specifications will be in WAVEORA1 when it is created as a clone from
CLONEORA. WAVEORA1 is the Linux system where eventually the Oracle Database will be installed.
The entry in the NFS server /etc/exports is “/root/unzips *(rw,sync,no_root_squash,no_subtree_check)”.
The corresponding CLONEORA entry in /etc/fstab is “xsrv:/root/unzips /mnt nfs
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,tcp”.
Use dirmaint to add two 5GB mdisks

Two mdisks at virtual addresses 400 and 401 will be added with z/VM dirmaint commands. The two
mdisks will be used for database storage. Similar to the comment above about the NFS mounted Oracle
Database libs, the mdisks won’t be used directly by CLONEORA. The clone WAVEORA1 will have the
same mdisk setup as CLONEORA.
dirm for cloneora amdisk 400 3390 autog 7500 bigd00 mr
DVHXMT1191I Your AMDISK request has been sent for processing to DIRMAINT
DVHXMT1191I at SVSCVMC.
Ready; T=0.01/0.01 14:41:48
DVHREQ2288I Your AMDISK request for CLONEORA at * has been accepted.
DVHSCU3541I Work unit 14144149 has been built and queued for processing.
DVHSHN3541I Processing work unit 14144149 as MAINT from SVSCVMC,
DVHSHN3541I notifying MAINT at SVSCVMC, request 170 for CLONEORA
DVHSHN3541I sysaffin *; to: AMDISK 0400 3390 AUTOG 7500 BIGD00 MR
DVHBIU3450I The source for directory entry CLONEORA has been updated.
DVHBIU3424I The next ONLINE will take place immediately.
DVHDRC3451I The next ONLINE will take place via delta object directory.
DVHBIU3428I Changes made to directory entry CLONEORA have been placed
DVHBIU3428I online.
DVHSHN3430I AMDISK operation for CLONEORA address 0400 has finished
DVHSHN3430I (WUCF 14144149).
DVHREQ2289I Your AMDISK request for CLONEORA at * has completed; with RC
DVHREQ2289I = 0.
dirm for cloneora amdisk 401 3390 autog 7500 bigd00 mr
DVHXMT1191I Your AMDISK request has been sent for processing to DIRMAINT
DVHXMT1191I at SVSCVMC.
DVHREQ2288I Your AMDISK request for CLONEORA at * has been accepted.
DVHSCU3541I Work unit 14144205 has been built and queued for processing.
DVHSHN3541I Processing work unit 14144205 as MAINT from SVSCVMC,
DVHSHN3541I notifying MAINT at SVSCVMC, request 171 for CLONEORA
DVHSHN3541I sysaffin *; to: AMDISK 0401 3390 AUTOG 7500 BIGD00 MR
DVHBIU3450I The source for directory entry CLONEORA has been updated.
DVHBIU3424I The next ONLINE will take place immediately.
DVHDRC3451I The next ONLINE will take place via delta object directory.
DVHBIU3428I Changes made to directory entry CLONEORA have been placed
DVHBIU3428I online.
DVHSHN3430I AMDISK operation for CLONEORA address 0401 has finished
DVHSHN3430I (WUCF 14144205).
DVHREQ2289I Your AMDISK request for CLONEORA at * has completed; with RC
DVHREQ2289I = 0.
Ready; T=0.01/0.01 14:42:17
Listing 5: Oracle ASM mdisks

[root@CLONEORA ~]# chccwdev -e 400 401
Setting device 0.0.0400 online

13
Done
Setting device 0.0.0401 online
Done
Listing 6: Bring mdisks online

[root@CLONEORA ~]# lsdasd 400 401
Bus-ID Status Name Device Type BlkSz Size Blocks
==============================================================================
0.0.0400 n/f dasdi 94:32 ECKD
0.0.0401 n/f dasdj 94:36 ECKD
[root@CLONEORA ~]# dasdfmt -b 4096 -y -f /dev/dasdi
Finished formatting the device.
Rereading the partition table... ok
0.0.0401 n/f dasdj 94:36 ECKD
[root@CLONEORA ~]# dasdfmt -b 4096 -y -f /dev/dasdj
Finished formatting the device.
Rereading the partition table... ok
[root@CLONEORA ~]# lsdasd 400 401
Bus-ID Status Name Device Type BlkSz Size Blocks
==============================================================================
0.0.0400 active dasdi 94:32 ECKD 4096 5273MB 1350000
0.0.0401 active dasdj 94:36 ECKD 4096 5273MB 1350000
Listing 7: Format the mdisks

[root@CLONEORA ~]# fdasd -a /dev/dasdi
reading volume label ..: VOL1
reading vtoc ..........: ok
auto-creating one partition for the whole disk...
writing volume label...
writing VTOC...
rereading partition table...
[root@CLONEORA ~]# fdasd -a /dev/dasdj
reading volume label ..: VOL1
reading vtoc ..........: ok
auto-creating one partition for the whole disk...
writing volume label...
writing VTOC...
rereading partition table...
Listing 8: Create ECKD partitions
Add entries to the file “/etc/dasd.conf” for disks 400 and 401.
0.0.0400 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0401 use_diag=0 readonly=0 erplog=0 failfast=0
Listing 9: "/etc/dasd.conf" entries
Creating the z/VM mdisks for ASM isn’t directly available in IBM Wave, however the mdisks will be
replicated when the CLONEORA image is cloned to create WAVEORA1.
Create UDEV entries for the two mdisks

UDEV entries are created with the owner, group, and permission specified so that the disks will be
available to Oracle ASM.

14
[root@CLONEORA rules.d]# cat 99-oracle.rules
KERNEL=="dasd*",SYMLINK=="disk/by-path/ccw-0.0.0400-
part1",OWNER="oracle",GROUP="oinstall",MODE="660",SYMLINK+="asm400"
KERNEL=="dasd*",SYMLINK=="disk/by-path/ccw-0.0.0401-
part1",OWNER="oracle",GROUP="oinstall",MODE="660",SYMLINK+="asm401"
[root@CLONEORA ~]# udevadm control --reload-rules
[root@CLONEORA ~]# start_udev
Starting udev: [ OK ] [root@CLONEORA ~]#
la /dev/asm*
lrwxrwxrwx. 1 root root 6 Sep 14 16:22 /dev/asm400 -> dasdi1
lrwxrwxrwx. 1 root root 6 Sep 14 16:22 /dev/asm401 -> dasdj1
[root@CLONEORA ~]# la /dev/dasd[ij]1
brw-rw----. 1 oracle oinstall 94, 33 Sep 14 16:22 /dev/dasdi1
brw-rw----. 1 oracle oinstall 94, 37 Sep 14 16:22 /dev/dasdj1
Listing 10: Bounce UDEV to load the new rules
NOTE: Stopping and starting UDEV seems to prevent access to Linux as the default gateway is
removed. A gateway parameter was explicitly added to the ifcfg-eth0 file and this seemed to
alleviate the problem.
Creating the UDEV entries isn’t directly available in IBM Wave, however the UDEV entries will be
replicated when the CLONEORA image is cloned to create WAVEORA1.
Add oracle user to /etc/sudoers

This line “oracle ALL=(ALL) NOPASSWD: ALL” is added to /etc/sudoers so that the “oracle” user can
run commands under root without specifying a password.
Miscellaneous
There may be some other files such as /etc/profile, /etc/pam.d/login, and /etc/security/limits.conf that will
need updating before the utility in the following section will run without warnings and errors. The key is to
review the documentation in the resources section carefully.
Run CLUVFY
The Oracle cluster verify utility is run under the “oracle” user to verify that the prerequisites for an Oracle
Restart install are on CLONEORA. The utility is on the Oracle libs that were NFS mounted previously.
The output of this utility should show that all pre-checks for an Oracle Restart configuration pass. For
more on using the CLUVFY utility see sections 3.4 and 4.1 of the IBM Redbook “Experiences with Oracle
Database 12c Release 1 on Linux on System z”.
Add Oracle Restart install script

The final step in prepping CLONEORA is adding the IBM Wave script that does a silent install of Oracle
Restart. The script also installs the database binaries, creates a container database, and lastly creates a
pluggable database in the container. The script needs access to the Oracle libs that were NFS mounted
previously and it also needs access to the Oracle response files that will be setup in this section.
The IBM Wave script manager is accessed from the “User Tasks” tab at the top of the wave home page.

15
Figure 13: Access IBM Wave Script Manager
This is the first screen of the IBM Wave Script Manager.
Figure 14: IBM Wave Script Manager
From the IBM Wave User Script Manager screen above select “Create New Script” to add the Oracle
installation script to IBM Wave.

16
Figure 15: IBM Wave script part 1 of 2
This screen and the next screen show the IBM Wave script. The variable above,
$WV_LINUX_HOST_NAME1, is an IBM Wave provided variable that identifies the host that the script is
being executed on.

17
Figure 16: IBM Wave script part 2 of 2
The mouse doesn’t work for cut and paste for adding the script to IBM Wave, but the “ctrl-c” and “ctrl-v”
keys do work for moving the script from a file to the IBM Wave scripting area.
On clicking “Save” the script is saved by IBM Wave and since global script was checked it is available to
all IBM Wave users.
Besides the NFS mounted Oracle libraries described previously, the script needs access to four response
files which are stored in the”/oracle/base/restart_install” directory on CLONEORA.

18
Response files
[oracle@CLONEORA restart_install]$ pwd

/oracle/base/restart_install
[oracle@CLONEORA restart_install]$ la
total 124
drwxr-xr-x. 2 oracle oinstall 4096 Sep 14 17:43 .
drwxr-xr-x. 3 oracle oinstall 4096 Sep 14 17:40 ..
-rw-r--r--. 1 oracle oinstall 99 Sep 14 17:42 cfgasm.rsp
-rw-r--r--. 1 oracle oinstall 58047 Sep 14 17:43 dbca_cdb.rsp
-rw-r--r--. 1 oracle oinstall 26809 Sep 14 17:43 db_install.rsp
-rw-r--r--. 1 oracle oinstall 24296 Sep 14 17:43 has_install.rsp
Listing 11: Oracle silent install response file location

oracle.assistants.asm|S_ASMPASSWORD=Oracle_01
oracle.assistants.asm|S_ASMMONITORPASSWORD=Oracle_01
Listing 12: cfgasm response file
Since the next three response files have numerous comments and are rather large, only the differences
between the response file and an Oracle Database 12c vanilla response file are shown in the listings
below.
[oracle@pazxxt01 ~]$ diff restart_install/dbca_cdb.rsp restart_12c/dbca.rsp
78c78
< GDBNAME = "oracdb.cmo-demo"
---
> GDBNAME = "orcl12c.us.oracle.com"
149a150,152
>
>
>
202c205
< SID = "oracdb"
---
> SID = "orcl12c"
212c215
< CREATEASCONTAINERDATABASE = true
---
> #CREATEASCONTAINERDATABASE =
222c225
< NUMBEROFPDBS = 0
---
> #NUMBEROFPDBS =
243c246
< NODELIST=
---
> #NODELIST=
274c277
< SYSPASSWORD = "Oracle_01"
---
> #SYSPASSWORD = "password"
284c287
< SYSTEMPASSWORD = "Oracle_01"
---
> #SYSTEMPASSWORD = "password"
450c453
< RECOVERYAREADESTINATION=/oracle/base/flash_recovery_area
---
> #RECOVERYAREADESTINATION=

19
460c463
< STORAGETYPE=ASM
---
> #STORAGETYPE=FS
469,471c472,473
< #
< DISKGROUPNAME=DATA
< #
---
> #DISKGROUPNAME=DATA
>
479c481
< ASMSNMP_PASSWORD="Oracle_01"
---
> #ASMSNMP_PASSWORD=""
499,500c501,502
< CHARACTERSET = "AL32UTF8"
< #
---
> #CHARACTERSET = "US7ASCII"
>
509c511
< NATIONALCHARACTERSET= "AL16UTF16"
---
> #NATIONALCHARACTERSET= "UTF8"
556c558
< LISTENERS = "LISTENER"
---
> #LISTENERS = "listener1 listener2"
595c597
< SAMPLESCHEMA=TRUE
---
> #SAMPLESCHEMA=TRUE
Listing 13: dbca_cdb response file differences

[oracle@WAVEORA1 base]$ diff restart_install/db_install.rsp
response_12c/db_install.rsp
29c29
< oracle.install.option=INSTALL_DB_SWONLY
---
> oracle.install.option=
42c42
< UNIX_GROUP_NAME=oinstall
---
> UNIX_GROUP_NAME=
49c49
< INVENTORY_LOCATION=/oracle/oraInventory
---
> INVENTORY_LOCATION=
91c91
< ORACLE_HOME=/oracle/base/db
---
> ORACLE_HOME=
96c96
< ORACLE_BASE=/oracle/base
---
> ORACLE_BASE=
107c107
< oracle.install.db.InstallEdition=EE
---
> oracle.install.db.InstallEdition=

20
125c125
< oracle.install.db.DBA_GROUP=dba
---
> oracle.install.db.DBA_GROUP=
131c131
< oracle.install.db.OPER_GROUP=oper
---
> oracle.install.db.OPER_GROUP=
136c136
< oracle.install.db.BACKUPDBA_GROUP=dba
---
> oracle.install.db.BACKUPDBA_GROUP=
141c141
< oracle.install.db.DGDBA_GROUP=dba
---
> oracle.install.db.DGDBA_GROUP=
146c146
< oracle.install.db.KMDBA_GROUP=dba
---
> oracle.install.db.KMDBA_GROUP=
419c419
< SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
---
> SECURITY_UPDATES_VIA_MYORACLESUPPORT=
431c431
< DECLINE_SECURITY_UPDATES=true
---
> DECLINE_SECURITY_UPDATES=
483c483
< oracle.installer.autoupdates.option=SKIP_UPDATES
---
> oracle.installer.autoupdates.option=
Listing 14:db_install response file differences

[oracle@WAVEORA1 base]$ diff restart_install/has_install.rsp
response_12c/grid_install.rsp
60c60
< INVENTORY_LOCATION=/oracle/oraInventory
---
> INVENTORY_LOCATION=
110c110
< oracle.install.option=HA_CONFIG
---
> oracle.install.option=
115c115
< ORACLE_BASE=/oracle/base
---
> ORACLE_BASE=
120c120
< ORACLE_HOME=/oracle/has
---
> ORACLE_HOME=
136c136
< oracle.install.asm.OSDBA=dba
---
> oracle.install.asm.OSDBA=
142c142
< oracle.install.asm.OSOPER=asmoper
---
> oracle.install.asm.OSOPER=
148c148

21
< oracle.install.asm.OSASM=dba
---
> oracle.install.asm.OSASM=
316c316
< oracle.install.asm.SYSASMPassword=Oracle_01
---
> oracle.install.asm.SYSASMPassword=
324c324
< oracle.install.asm.diskGroup.name=data
---
> oracle.install.asm.diskGroup.name=
335c335
< oracle.install.asm.diskGroup.redundancy=EXTERNAL
---
> oracle.install.asm.diskGroup.redundancy=
351c351
< oracle.install.asm.diskGroup.AUSize=1
---
> oracle.install.asm.diskGroup.AUSize=
363c363
< oracle.install.asm.diskGroup.disks=/dev/asm400,/dev/asm401
---
> oracle.install.asm.diskGroup.disks=
375c375
< oracle.install.asm.diskGroup.diskDiscoveryString=/dev/asm4*
---
> oracle.install.asm.diskGroup.diskDiscoveryString=
380c380
< oracle.install.asm.monitorPassword=Oracle_01
---
> oracle.install.asm.monitorPassword=
Listing 15: has_install response file differences
Deactivate CLONEORA
Now that CLONEORA has been prepped for an Oracle silent install it will be deactivated. The deactivated
CLONEORA will itself be cloned to WAVEORA1 and that is where the Oracle Database will be installed.
CLONEORA can be cloned as many times as needed and the new clone will have the Oracle Database
install prerequisites in place.

22
Figure 17: Deactivate cloneora
CLONEORA is shutdown or deactivated in IBM Wave terms by right clicking and then selecting
Deactivate.
Oracle Database install using IBM Wave

Now that CLONEORA has been deactivated, it can be used to provide one or more Linux clones. Each
clone will have all the prerequisites required for an Oracle Restart install.
So now with three steps an operational Oracle Database on Linux can be made available. The first step is
to create Linux WAVEORA1 as a clone of CLONEORA. The second step is to activate WAVEORA1. The
third step is to execute the IBM Wave script on WAVEORA1. There are a few “glitches” from the three
steps and they will be explained in the discussion below.
There are a few things that need notes:
 The ASM response file expects the disks /dev/asm400 and /dev/asm401 that were added to
CLONEORA to be available. The ASM discovery string is “/dev/asm*”.
 The script and response files use “oracdb” for the container name.
 The script and response files use “orapdb” for the pluggable database name.
Everything in this paper has dealt with a single z/VM system, but IBM Wave supports z/VM systems
which are members of a Single System Image (SSI) cluster.

23
Clone “CLONEORA”
The Linux system to be used to do the first Oracle Restart install will be cloned from CLONEORA. This
happens by right clicking the deactivated CLONEORA Linux image and then selecting “Cloning” followed
by “Clone”.
But first WAVEORA1 (the new clone) needs to be provided with RACF access to the z/VM guest LAN.
These are the same RACF commands that were used before CLONEORA was created.
rac au (waveora1) pass(icc630) owner(ibmuser) dfltgrp(sys1) name(clone)
Ready; T=0.01/0.01 20:22:38
rac pe system.lanvmc1 class(vmlan) id(waveora1) access(alter)
Ready; T=0.01/0.01 20:23:12
rac du (waveora1)
Ready; T=0.01/0.01 20:23:24
Figure 18: WAVEORA1 access to the guest LAN
Figure 19: Clone CLONEORA
Once “Clone” has been selected the name, password, disk group, and other parameters are specified in
the same way that was done previously when CLONEORA was generated from RH65GOLD.

24
Figure 20: Configuration for WAVEORA1
After clicking “Go”, clicking “Close” after the “Cancel” changes to “Close”, and waiting a few minutes,
WAVEORA1 is ready to be activated.

25
Figure 21: Activate WAVEORA1
Boot WAVEORA1 by doing a right click on the icon and then clicking “Activate”.

26
Displaying the details of WAVEORA1 shows the following screen.
Figure 22: WAVEORA1 details
Now that WAVEORA1 is running, Oracle Restart can be installed.
Oracle silent install using IBM Wave script

The known_hosts file needs updated with hostname WAVEORA1. This is required as the silent install
script uses “ssh waveora1 <command>” and unless known_hosts is updated a message as shown next
will appear that expects a response.

27
[oracle@WAVEORA1 ~]$ ssh waveora1 date
The authenticity of host 'waveora1 (192.168.150.5)' can't be established.
RSA key fingerprint is 1e:bb:38:8b:43:82:60:6e:7d:81:d3:d3:36:c4:c9:f2.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'waveora1,192.168.150.5' (RSA) to the list of known
hosts.
Sun Sep 14 20:44:52 CDT 2014
[oracle@WAVEORA1 ~]$ ssh waveora1 date
Sun Sep 14 20:44:58 CDT 2014
Listing 16: Add “waveora1” to known_hosts file
Figure 23: Execute Oracle install script
Now by right clicking the newly minted Linux and clicking “Execute Script”, the script to install the Oracle
Database can be run. The execute screen appears and a few details need to be filled in for the script to
execute successfully.

28
Figure 24: Script configuration setup
The script is run under the “oracle” user so the user and password are entered at the top of the screen.
The “Apply credentials to selected guests below” is selected and then “Browse” is selected to find the
install script to run.
The script does a silent install of Oracle Restart, a silent install of Oracle Database binaries, a silent
create of a container database, and a silent create of a pluggable database.
To run the script click “Go”, click “OK” on the popup. The cancel button will be changed to “Close” and
click “Close”. The silent install is running. When the script finishes an Oracle pluggable database running
on ASM is available.
The script ended successfully and generate output confirming that:
 Creation of the pluggable database is 100% complete
 The user “scott” was created
The script WAVEInit.oracle_install finished with return code:0. This shows that a pluggable database was
created as the latter part of the silent install script. The script also created a user “scott”. The command:

29
“sqlplus scott/tiger@WAVEORA1:1523/orapdb.cmo-demo” can be used to connect the user “scott” to the
newly created pluggable database.
Summary
IBM Wave was used to create a Linux image, CLONEORA. This image was created so that the original
Linux image, RH65GOLD, would remain as a prototype so that other pure Red Hat 6.5 Linux systems
could be built. After CLONEORA was created as a clone of RH65GOLD, the prerequisites necessary for
an Oracle Database installation were added to it. Once the prerequisites were installed, CLONEORA was
deactivated or shutdown by IBM Wave.
IBM Wave was then used to clone CLONEORA and create the Linux system WAVEORA1. A silent mode
Oracle product install was done on WAVEORA1 without the need of installing and verifying that
WAVEORA1 contained the prerequisites necessary for an Oracle Database install. Similarly, other clones
of the Linux image CLONEORA could be produced and they would be immediately available for an
Oracle Restart Installation.
Everything in this document was done on a single z/VM image, but IBM Wave supports multiple z/VM
systems which are members of a Single System Image (SSI) cluster.

30
Resources
IBM Wave for z/VM: Administration and Customization
SC27-6118-02
IBM Wave for z/VM: User Guide and Reference

SC27-6119-02
IBM Redbook
IBM Wave for z/VM Installation, Implementation, and Exploitation
SG24-8192-00
IBM Redbook
Experiences with Oracle Database 12c Release 1 on Linux on System z
SG24-8159-00
IBM Redbook
Advanced Networking Concepts Applied Using Linux on IBM System z
SG24-7995-00
The following Oracle Installation Guides are at http://docs.oracle.com:

 Oracle Grid Infrastructure Installation Guide 12c Release 1 (12.1) for Linux, E17888
 Oracle Database Installation Guide 12c Release 1 (12.1) for Linux, E17720
 Oracle Database Release Notes 12c Release 1 (12.1) for Linux, E17734
 Oracle Database Quick Installation Guide 12c Release 1 (12.1) for IBM: Linux on System z,
E18443

31
About the author
Terry Elliott is an IBM z Systems specialist working in the IBM Oracle International Competency Center
at IBM Foster City. He has over 30 years of experience in information technology. Before joining the IBM
Oracle International Competency Center, Terry was an ERP z Systems performance specialist.
Thanks to the following people for their contributions to this project:
Stephen McGarril
System z Client Center in Poughkeepsie
Stephen Dulin
IBM Wave Service/Build/Test in Poughkeepsie

32
Trademarks and special notices
© Copyright. IBM Corporation 2015. All rights reserved.
References in this document to IBM products or services do not imply that IBM intends to make them
available in every country.
IBM, the IBM logo, RACF, z Systems, and z/VM are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both:
Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks
or registered trademarks of Red Hat, Inc., in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
The information provided in this document is distributed “AS IS” without any warranty, either express or
implied.
The information in this document may include technical inaccuracies or typographical errors.
Information concerning non-IBM products was obtained from a supplier of these products, published
announcement material, or other publicly available sources and does not constitute an endorsement of
such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly
available information, including vendor announcements and vendor worldwide homepages. IBM has not
tested these products and cannot confirm the accuracy of performance, capability, or any other claims
related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the
supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without
notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller
for the full text of the specific Statement of Direction.
Some information addresses anticipated future capabilities. Such information is not intended as a
definitive statement of a commitment to specific levels of performance, function or delivery schedules with
respect to any future products. Such commitments are only made in IBM product announcements. The
information is presented here to communicate IBM's current investment and development activities as a
good faith effort to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled
environment. The actual throughput or performance that any user will experience will vary depending
upon considerations such as the amount of multiprogramming in the user's job stream, the I/O
configuration, the storage configuration, and the workload processed. Therefore, no assurance can be
given that an individual user will achieve throughput or performance improvements equivalent to the
ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part
of the materials for this IBM product and use of those Web sites is at your own risk.

33

Oracle Database Deployment Using IBM Wave For ZVM

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Oracle Database Deployment Using IBM Wave For ZVM

Caricato da

Copyright:

Formati disponibili

Oracle Database deployment using IBM

Wave for zVM

© Copyright IBM Corporation, 2015. All Rights Reserved.

Oracle Database deployment using IBM Wave for zVM

Oracle Database install preliminary work

Oracle Database deployment using IBM Wave for zVM

Figure 1: IBM Wave initial screen

Oracle Database deployment using IBM Wave for zVM

Oracle Database deployment using IBM Wave for zVM

Oracle Database deployment using IBM Wave for zVM

Figure 4: Part of IBM Wave screen showing RH65GOLD prototype

Listing 1: RACF Commands to enable access to guest LAN

Oracle Database deployment using IBM Wave for zVM

Create CLONEORA as the base Linux image

Figure 5: Configuration for the CLONEORA Linux image

Oracle Database deployment using IBM Wave for zVM

Figure 6. CLONEORA before activation

Figure 7: CLONEORA is activated

Oracle Database deployment using IBM Wave for zVM

Add Linux user/groups

Listing 2: Add groups and oracle user

Add swap space

Oracle Database deployment using IBM Wave for zVM

Figure 9: Create a new partition

Oracle Database deployment using IBM Wave for zVM

Oracle Database deployment using IBM Wave for zVM

Figure 12: SSH access to cloneora

After logging in, continue with setting up a 10GB swapfile.

Oracle Database deployment using IBM Wave for zVM

Listing 3: Setup 10GB swapfile

Listing 4: Make swapfile available after a reboot

Verify/add prerequisite RPMs

Verify/add/change Linux kernel parameters

Oracle Database deployment using IBM Wave for zVM

Use dirmaint to add two 5GB mdisks

Listing 5: Oracle ASM mdisks

Oracle Database deployment using IBM Wave for zVM

Listing 6: Bring mdisks online

Listing 7: Format the mdisks

Listing 8: Create ECKD partitions

Listing 9: "/etc/dasd.conf" entries

Create UDEV entries for the two mdisks

Oracle Database deployment using IBM Wave for zVM

Listing 10: Bounce UDEV to load the new rules

Add oracle user to /etc/sudoers

Add Oracle Restart install script

Oracle Database deployment using IBM Wave for zVM

This is the first screen of the IBM Wave Script Manager.

Figure 14: IBM Wave Script Manager

Oracle Database deployment using IBM Wave for zVM

Oracle Database deployment using IBM Wave for zVM

Oracle Database deployment using IBM Wave for zVM

[oracle@CLONEORA restart_install]$ pwd

Listing 11: Oracle silent install response file location

Listing 12: cfgasm response file

Oracle Database deployment using IBM Wave for zVM

Listing 13: dbca_cdb response file differences

Oracle Database deployment using IBM Wave for zVM

Listing 14:db_install response file differences

Oracle Database deployment using IBM Wave for zVM

Listing 15: has_install response file differences

Oracle Database deployment using IBM Wave for zVM

Oracle Database install using IBM Wave