• Design
  • Tuning
  • Apache Derby
  • IBM DB2
  • MySQL
  • Oracle
  • SQL Server
  • Installing and running Oracle on IBM z/OS

    You are currently using a web browser that does not support HTML pages with style sheets. Please try the XHTML 1 or XHTML 1 Mobile version of this page instead.

    Runing Oracle Universal Installer (OUI) on z/OS

    Runing Oracle Universal Installer (OUI) on z/OS

    1. If necessary , delete any dumps or other /tmp files, UNIX files and MVS datasets from a previous installation failure.
    2. Connect to UNIX on z/OS via Telnet
    3. Make sure /etc/startup.mk exists. If not, copy it from /samples/startup.mk. OUI may crash with Java and CEE dumps if it does not exist.
    4. Set up the environment for the required version of Java and start OUI: export PATH=/bin:/usr/lpp/java/J1.4/bin export JAVA_HOME=/usr/lpp/java/J1.4 /usr/lpp/Oracle/runInstaller -ignoresysprereqs > ~/ouistdout 2> ~/ouistderr Redirecting STDOUT and STDERR prevent OUI from failing with a IEC141I 013-C0 error on the MVS console.
    5. Rename the ~/ouistdout and ~/ouistderr before starting OUI for the next installation or configuration.
    Installing Patches on z/OS

    Installing Patches on z/OS

    1. Log into USS with the login ID which owns the Oracle installation directories.
    2. Download the patch to be installed and put it in the ORACLE_HOME directory.
    3. Download the latest version of OPatch (patch #4898608) and put it in the ORACLE_HOME directory.
    4. Download the OS/390 version of the UnZip utility from the Oracle Metalink UnZip Utilities Download page.
    5. Uncompress the UnZip utility and add execute permission: uncompress unzip_os390.Z chmod ug+x unzip_os390
    6. UnZip OPatch and the patch to be applied: ./unzip_os390 -a p4898608_10203_GENERIC ./unzip_os390 pnnnnnnn_10203_MVS Use the -a option when extracting OPatch to convert ASCII to EBCDIC. The patch itself probably contains binary files and may not need to be extracted with the -a option, but it might not hurt to include it anyway.
    7. Make sure the environment variables and PATH are properly set: export JAVA_HOME=/usr/lpp/java/J1.4 export ORACLE_HOME=/usr/lpp/Oracle/product/otg/10.2.0.3 export ORACLE_HLQ_PDS=ORACLE.OTG.V10203 export PATH=$ORACLE_HOME/OPatch:$ORACLE_HOME/perl/bin:$PATH The PATH should include the OPatch directory and the directory that contains the version of Perl that was installed with Oracle.
    8. Verify the versions of Java and Perl: java -version perl -version
    9. Make sure oraInst.loc points to the correct oraInventory location (ex: $ORACLE_BASE/oraInventory or $ORACLE_HOME/oraInventory). cat /var/opt/oracle/oraInst.loc #Oracle Installer Location File Location #Ddd Mmm dd hh:mm:ss ZZZ yyyy inst_group=MVSNFSC inventory_loc=/usr/lpp/Oracle/10.2.0.3/oraInventory
    10. Verify oraInventory exists where indicated by oraInst.loc: ls -l /usr/lpp/Oracle/10.2.0.3/oraInventory
    11. Test running OPatch: opatch lsinventory
    12. Shut down the gateways if they are running.
    13. Perform any pre-installation instructions indicated by the ReadMe file, such as allocating data sets.
    14. Apply the patch: cd nnnnnnn opatch apply
    15. Perform any post-installation instructions indicated by the ReadMe file.

    Last updated Wednesday October 18, 2006


    Printer-friendly PDF* format:

    Oracle on IBM z/OS

    This Section

    You are currently viewing this page in XHTML 2 Style Sheet* format (* see Clicklets for more infomation). This document is also available in HTML Style Sheet*XHTML 1* XML* HTML 4*HTML 5 Style Sheet*HTML 5 XML*HTML 5 non-XML* XHTML Mobile* WML Mobile* and printer-friendly PDF* formats. This is accomplished with Single Source Publishing, a content management system that uses templates in XSLT style sheets provided by XML Styles .com to transform the source content for various content delivery channels. There is also RDF* metadata that describes the content of this document.