Installing Oracle 10gR2 ( ) on z/os 1.9. Brent Howe, IBM Oracle International Competency Center

Transcription

1 Installing Oracle 10gR2 ( ) on z/os 1.9 Brent Howe, IBM Oracle International Competency Center Workshop Information These slides were generated to support the workshop presented by IBM at the Oracle zseries SIG. These slides are not intended to stand on their own. Please use these slides along side the Redbook and Oracle installation Documentation. Redbook Experiences with Oracle Database 10g on z/os Oracle Installation Documentation Oracle Database 10g Release 2 (10.2) Documentation 2

2 Agenda Part 1 Prepare z/os for installation Installation of the Oracle binaries Part 2 Create a Database Patch a database Part 3 Using WLM In a separate presentation 3 Agenda Part 1 Install Preparation System Access z/os USS login Requirements X-windows Setup Software Requirements Define Users and Groups Define and Format Filesystems Parmlib updates FTP the Oracle code Execution of the installation 4

3 Systems Access System Access Requirements for the install X-Windows Session for Oracle Universal Installer (OUI) processing tn3270 session for TSO file, and Database VSAM file maintenance Telnet connection required to from a client to z/os USS here are some popular options, this test used PuTTy from Windows. Used PuTTY from Windows client Available at Telnet from Intel Linux client Comes within the standard TCP/IP configuration TN3270 Client IBM Personal Communications Telnet Hummingbird Telnet 5 Login to MVS USS using Telnet Logging into to z/os USS using telnet usually requires a unique port address. This is defined in the system stack a common choice is 1023 for telnet thus reserving port 23 for tn3270 into z/os itself telnet mvs09:1023 EZYTE27I login: ibmuser EZYTE28I ibmuser Password: IBM Licensed Material - Property of IBM 5694-A01 (C) Copyright IBM Corp. 1993, 2001 (C) Copyright Mortice Kern Systems, Inc., 1985, (C) Copyright Software Development Group, University of Waterloo, All Rights Reserved. U.S. Government users - RESTRICTED RIGHTS - Use, Duplication, or Disclosure restricted by GSA-ADP schedule contract with IBM Corp. IBM is a registered trademark of the IBM Corp. IBMUSER:/u/ibmuser: > 6

4 X-Windows Requirements X-Windows is required to run the Oracle Universal Installer (OUI) Intel Linux xhost + <z/os hostname> VNC can be used Included in many Linux distributions Need to start a server on a Linux host Start on a separate host with an assigned port Allows any X-Windows host to be presented Export DISPLAY=xx.xx.xx.xx:<assigned port> Start on USS ( will require being downloaded and possibly built) Cygwin/Xfree86 on a Windows machine Must be installed onto client Start the linux environment Startxhost.sh invokes the X-Windows server xhost + <z/os hostname> Export DISPLAY=xx.xx.xx.xx:<assigned port> 7 XClock on MVS USS The XClock program is a sample program that can be used to validate the X-Windows connectivity environment. You will need to build the product. This is the procedure to build X-Clock >mkdir xclock >cp /usr/lpp/tcpip/x11r6/xamples/clients/xclock/* xclock >cd xclock >make c89 -c -D_ALL_SOURCE -W c,dll xclock.c c89 -c -D_ALL_SOURCE -W c,dll Clock.c c89 -o xclock xclock.o Clock.o /usr/lib/xaw.x /usr/lib/sm.x /usr/lib/ice.x /usr/lib/x11.x >export DISPLAY= < Display IP Address: port number > >xclock 8

5 Software Pre-Requisites z/os Operating System z/os 1.4 is the minimum requirement We used z/os 1.9, validated using the uname a command >uname a OS/390 OS/390 MVS PERL Now packaged with z/os Validated with the perl command $ perl -v This is perl, version 5.004_03 Make packaged with z/os Validated with the make command $ make -V make - Version z/os Shell and Utilities v1.9 9 Java Pre-requisite Java is a pre-requisite for Oracle database running on Z/OS 1.9. This is the verification of the release level. MVS09:/u/demo1>java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE IBM z/os Persistent Reusable VM build cm (SR10) (JIT enabled: jitc MVS09:/u/demo1> The correct level of Java can be obtained of the z/os Java Website. If the following error is received after installing the correct Java Version the resolution is listed below: FSUMF073 J1.4/bin/libawt.so: user not authorized to restore extended attribute created a generic RACF profile BPX.FILEATTR.* in the RACF FACILITY class, and granted the userid access to this profile. 10

6 USS.Profile validation User that does the install must have write access to /var/opt/oracle Set DISPLAY variable EXPORT DISPLAY= < Client IP Address: port # for x-windows displays > verify variables JAVA_HOME Should be set to Java as described previously PATH_JAVA export PATH_JAVA=$JAVA_HOME/bin PATH export PATH=$PATH_JAVA:$PATH LIBPATH export LIBPATH=$JAVA_HOME/lib:$PATHJAVA:$LIBPATH $ORACLE_HOME should be empty 11 Define Oracle User ID and Groups The Oracle Userids are needed for both the install and runtime processes. These are the recommended ID s and their attributes. You will need the appropriate authority to execute this job. //S0 EXEC PGM=IKJEFT01,DYNAMNBR=75,TIME=100,REGION=0M //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * ADDGROUP OINSTALL SUPGROUP(SYS1) OMVS(GID(100)) ADDGROUP ORADBA SUPGROUP(OINSTALL) OMVS(GID(101)) ADDUSER ORACLE DFLTGRP(OINSTALL) AD ORACLE.* UACC(READ) ALU oracle OMVS(HOME('/u/oracle') PROGRAM('/bin/sh') UID(100)) ALU oracle PASSWORD(ORACLE) PERMIT ACCT# CLASS(ACCTNUM) ACCESS(READ) ID(ORACLE) PERMIT ISPFPROC CLASS(TSOPROC) ACCESS(READ) ID(ORACLE) SETROPTS RACLIST(TSOPROC) REFRESH RDEFINE STARTED ORA1NET.** STDATA(USER(oracle)) RDEFINE STARTED ORA1DB.** STDATA(USER(oracle)) SETROPTS RACLIST(STARTED) REFRESH 12

7 Define and Format the File Systems The File System needs to be defined to z/os //S1 EXEC PGM=IDCAMS,REGION=0M //SYSPRINT DD SYSOUT=* DEFINE CLUSTER - (NAME(ZFS.ORACLE) - VOLUMES(ORA001) - MEGABYTES( ) - LINEAR - SHAREOPTIONS(2)) DEFINE CLUSTER - (NAME(ZFS.U.ORACLE) - VOLUMES(ORA001) - MEGABYTES(10 5) - LINEAR - SHAREOPTIONS(2)) Once Defined the file system needs to be formatted //S1 EXEC PGM=IOEAGFMT,REGION=0M, // PARM='-aggregate ZFS.ORACLE -compat' //SYSPRINT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD SYSOUT=* //S2 EXEC PGM=IOEAGFMT,REGION=0M, // PARM='-aggregate ZFS.U.ORACLE -compat' //SYSPRINT DD SYSOUT=* //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CEEDUMP DD SYSOUT=* 13 Mount Filesystems It is recommended that you follow both steps to mount the file systems 1. Dynamic for immediate access > mount -f ZFS.ORACLE -t ZFS /oracle > mount -f ZFS.U.ORACLE -t ZFS /u/oracle 2. Update BPXPRMxx for auto mount in subsequent IPL s FILESYSTYPE TYPE(ZFS) ENTRYPOINT(IOEFSCM) ASNAME(ZFS) MOUNT FILESYSTEM('ZFS.ORACLE') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/oracle') MOUNT FILESYSTEM('ZFS.U.ORACLE') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/u/oracle') 14

8 Additional Parmlib Member Updates 1. SCHED00 PPT PGMNAME(ORARASC) /* PROGRAM NAME */ NOCANCEL /* NOT CANCELABLE */ KEY(7) /* PROTECTION KEY 7 FOR DB */ NOSWAP /* PROGRAM IS NOT SWAPABLE */ SYST /* SYSTEM TASK, NOT TIMED */ PPT PGMNAME(ORANET) /* PROGRAM NAME */ NOCANCEL /* NOT CANCELABLE */ NOSWAP /* PROGRAM IS NOT SWAPABLE */ SYST /* SYSTEM TASK, NOT TIMED */ 2. PROGxx APF FORMAT(DYNAMIC) APF ADD DSNAME(DEMO01.V10203.AUTHLOAD) VOLUME(DEMO01) 15 TSO Dataset Conventions and Parameters Decide on the Names you will use for each item before you start the OUI. These values will be used during the installation processes, the database definitions, and the subsystem definitions. Name SID HLQ Service name DB Started task name Service name Net Started task name SYSDA VOLUME SubSystem Name Value used DEM1 DEMO1.V10203 DEMO1S10 DEM1S10 DEMO1N10 DEM1N DEMO01 DEMO Comments 4 characters Must be ID in RACF Must be ID in RACF For our installation 16

9 Check for Previous Installations of Oracle You can use the DEINSTALL option to remove the ORACLE_HOME files on OMVS or you can rm rf * to manually remove the files in USS. USS Rename or remove OraInventory Pointed to from within /var/opt/oracle/orainst.loc orainst.loc from /var/opt/oracle Oratab from /var/opt/oracle TSO Remove the previous files from TSO based on the high level qualifier that you plan to use for this installation. If using RAC, check the metalink notes on cleaning up RAC 17 Starting the Oracle Universal Installer (OUI) Change to the directory that the Installer has been staged into and issue the following command. Ensure the user executing does not have root attributes../runinstaller >./runinstaller >Starting Oracle Universal Installer... Checking requirements... Checking operating system version: must be 14.00, 15.00,16.00, 17.00,18.00 or Actual Passed Checking the version of Perl: must be 5.004,5.6.1 Perl is version Passed All requirements met. 18

10 Initial Splash Screen for the Oracle on z/os Install 19 Oracle Inventory and Product De-installation selection 20

11 Oracle Inventory Location Specification 21 Product Selection This test selected the complete Oracle Database 22

12 Installation Type Selection 23 Specify the Oracle Home Location and Name 24

13 High Level Qualifier Selection Though this is specified during the installation on USS this is the High level qualifier for the TSO datasets for both installation and run-time. 25 TSO Dataset allocation selection This provides the option of manual; SMS or to not pre-allocate the TSO datasets. 26

14 File Allocation parameters If the selection was made to manually allocate TSO datasets this screen is displayed. This test required update the unit as well as the volume parameter. 27 Insure the installation specifications are up to date. 28

15 The installation will proceed and status will be displayed here 29 Root Configuration Scripts This displayed necessary scripts must be run as root to complete this portion of the installation 30

16 Completion of the initial phase This panel signifies that the initial phase of the installation complete. 31 Agenda Part 2 Database and the Subsystem Definition Pre Installation Steps Run the OUI using runinstaller Setup and define the Subsystem Create the database Using OPatch Pre patch requirements Applying Opatch Post Patch requirements 32

17 The Database and Subsystem Definitions Prior to executing this ensure the following have been accomplished Started task names must be in RACF with OMVS segment Ensure the dataset that will be used for AUTHLOAD is an AFP authorized library Have the PPT entries in the PARMLIB file Have access to use the SETSSI and SETPROG commands or a person who can Obtain a High Level Qualifier for the TSO dataset that is in the catalog we used DEMO01.V10203 Obtain disk space for the TSO datasets we had Mod 9 should have at least 2 different volumes Have write access to a PROCLIB and LINKLIB Verify the valul\e for ORACLE_HOME This step of the installation requires execution of the Oracle OUI./runInstaller This will install and cusomize the fields in Parmlib and Instlib 33 Database and Subsystem Initial Splash Screen 34

18 Product Selection This panel has been displayed before, select the Database and Subsystem Configuration to continue with the installation. 35 Home Details The Installation should provide the correct details here, verify the accuracy and correct as necessary 36

19 High Level Qualifiers The installation software should again fill in the correct information; This needs to be verified prior to proceeding. 37 Parmlib Definition In this installation the Instlib was previously allocated, Parmlib will be allocated as a result of the specifications listed here 38

20 Subsystem Definition The Subsystem definition is next, these parameters need to be based on input on System programmer. This panel also defines the service name and the procedure name for managing Oracle database on z/os 39 The Subsystem definition Network Interface This panel requires the input of the network interfaces that will manage the TNS interface for the z/os Oracle Database. 40

21 OSDI Server Definitions This panels requires validation of the HLQ parameters. Otherwise the defaults should work. 41 File definitions The ORA$FPS file definitions panel will manage the dynamic allocation of datasets bases on this panel. The installation was executed by overriding the defaults to Site specific requirements. 42

22 The Summary 43 The Install Commences 44

23 Completion The database configuration and Subsystem definition parameters have now been successfully installed. See the next slide for verification of the successful installation. 45 Check the Telnet Session Validate that the Installation process completed without any errors EZYTE27I login: demo1 MVS09:/demo/install>./runInstaller MVS09:/demo/install>Starting Oracle Universal Installer... Checking installer requirements... Checking operating system version: must be 14.00, 15.00, 16.00, 17.00, 17.01, or Actual Passed All installer requirements met. Running java out of :/demo/j1.4//bin/java Oracle Universal Installer, Version Production Copyright (C) 1999, 2006, Oracle. All rights reserved. LISTCAT ENTRIES('DEMO1.V10203.PARMLIB') NONVSAM DEMO1.V10203.PARMLIB IN-CAT --- CATALOG.TSO Allocate: Dataset DEMO1.V10203.PARMLIB already exists, Bypassing allocate. 46

24 Define the Database Run the following from < High Level Qualifier >.INSTLIB These jobs will pre-allocate the VSAM database files. Member DEFINE This job allocates the VSAM files for the database. If you find???????? In place of valid volume parameters you will need to specify the volumes you want to use, All the files in this test were put on one volume, It is recommended that you should at least put LOG2, CONTROL2, and UNDO2 on separate volumes. Error warning The job is generated with comment commands /* */ starting in column 1. The resolution for this is to shift all of these characters into column 3 or greater. 47 Subsystem Definition Run the following from < High Level Qualifier >.INSTLIB These jobs will setup the Oracle Subsystem. Member COPYPROC This job copies the jobs to start and stop the address space to the system PROCLIB. This may need to be executed by the system programmer if you cannot write into the PROCLIB data set. These job names have to be in the RACF started task list. Member CPLNKLST You must put some of the members of AUTHLOAD in the system LINKLIST library. This job should be done by the system programmer. The JCL needs to be modified to the correct file names. The lowercase letters are there to prevent you from submitting the job without reviewing the JCL. Member ORASRVC Execute the job ORASRVC, This runs the SETSSI command. If you make an error in this, you must IPL the system to execute it a second time 48

25 Create the Database Run these jobs from <HLQ>.INSTLIB to create the database, The xxx is the first 3 letters of the subsystem name. SQLxxx11 SQLxxx12 SQLxxx13 SQLxxx14 SQLxxx15 The functions installed in the remaining four jobs were unnecessary for this exercise Database and listener should be up and running 49 Using Opatch OPatch is an Oracle-supplied utility that assists you with the process of applying interim patches to Oracle's software and rolling back interim patches from Oracle's software. The process for installing patch : The Patch was downloaded from Oracle Metalink Pre-installation requirements were met and installed The Patch was successfully applied The post application steps were executed The Patch process was completed 50

26 Opatch OPatch is an Oracle-supplied utility that assists you with the process of applying interim patches to Oracle's software and rolling back interim patches from Oracle's software. Opatch Commands View the OPatch documentation as delivered in $ORACLE_HOME/OPatch/docs The General usage of the OPatch command include the following $ 'opatch apply...' is to apply a patch $ 'opatch rollback...' is to roll back a patch $ 'opatch lsinventory' is to show inventory on an Oracle Home $ 'opatch query...' is to query a given patch from specific details $ 'opatch version' is to show the version of the OPatch being used. Adding help behind any of these commands displays the extended help information 51 Determine if any Patches are pending MVS09:/demo/demo1/OPatch>opatch lsinventory -invptrloc $ORACLE_HOME/oraInst.loc Invoking OPatch Oracle interim Patch Installer version Copyright (c) 2005, Oracle Corporation. All rights reserved.. Oracle Home : /demo/demo1 Central Inventory : /demo/orainventory from : /demo/demo1/orainst.loc OPatch version : OUI version : OUI location : /demo/demo1/oui Log file location : /demo/demo1/cfgtoollogs/opatch/opatch _ pm.log Lsinventory Output file location : /demo/demo1/cfgtoollogs/opatch/lsinv/lsinventory _ pm.txt Installed Top-level Products (2): Oracle z/os Database 10g Oracle z/os Database and Subsystem Configuration There are 2 products installed in this Oracle Home. There are no Interim patches installed in this Oracle Home OPatch succeeded. 52

27 Prepare the environment and the patch for installation Prepare to install the patch with OPatch unzip -a p _10203_mvs.zip inflating: /files/olap/admin/xumuts.plb [binary] inflating: /files/olap/admin/olapiboo.plb [binary] inflating: /files/olap/admin/olapimod.plb [binary] inflating: /files/olap/admin/olapimov.plb [binary] creating: /readmes/ inflating: /readmes/README-ebcdic.txt [binary] inflating: /readmes/README.txt [binary] Set the Environment Variables for executing Opatch export ORACLE_HOME=/your_installation_directory export ORACLE_HLQ_PDS=YOUR.HLQ 53 Pre-allocate TSO Datasets Dataset Name Tracks Device DEMO1.P V10203.AUTHLOAD DEMO1.P V10203.CMDLOAD DEMO1.P V10203.MESG

28 Apply the Patch From within the patch directory execute the patch apply /demo/demo1/opatch/opatch apply Invoking OPatch Oracle interim Patch Installer version Copyright (c) 2005, Oracle Corporation. All rights reserved.. Oracle Home : /demo/demo1 Central Inventory : /demo/orainventory from : /var/opt/oracle/orainst.loc OPatch version : OUI version : OUI location : /demo/demo1//oui Log file location : /demo/demo1/cfgtoollogs/opatch/opatch _ pm.log ApplySession applying interim patch ' ' to OH '/demo/demo1' Invoking fuser to check for active processes.... Invoking fuser on "/demo/demo1/bin/wrap" OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only. Backing up files and inventory (not for auto-rollback) for the Oracle Home.., Return Code = 0... Patch applied successfully 55 Patch Post Installation Steps Run the Post installation scripts For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catcpu.sql script as follows: cd $ORACLE_HOME/cpu/CPUJan2008 sqlplus /nolog SQL SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> QUIT Check the log files for errors, if any occur, reference the readme for resolution. 56

29 Patch Post Installation Scripts Recompile This particular patch requires a recompile of views within the database. Use the following patch delivered scripts to perform the re-compile. There is more detail on each of these scripts in the delivered read-me. Run the pre-check script, which reports the maximum number of views and objects that may be recompiled: cd $ORACLE_HOME/cpu/view_recompile sqlplus /nolog SQL> CONNECT / AS SYSDBA The purpose of this step is to help you determine whether view recompilation should be done at the same time as the CPU install, or scheduled later. Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA. cd $ORACLE_HOME/cpu/view_recompile sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP UPGRADE SQL> SHUTDOWN; SQL> STARTUP; Check the log file for any errors. The log file is in the current directory and is named: vcomp_<sid>_<timestamp>.log 57 Summary At this point we have: Installed the Oracle Binaries Configured the Subsystem Created a database Patched the database to the latest level Review the WLM presentation to set up for best performance 58