Home
Oracle Universal Installer and OPatch User's Guide for Windows and
Contents
1. SHOW ROOTSH CONFIRMATION true ruv BL Name SHOW END SESSION PAGE Datatype Boolean Description Set to true if the end of session page in the installer needs to be shown This page shows if the installation is successful or not Example SHOW END SESSION PAGE true Name SHOW EXIT CONFIRMATION Datatype Boolean Description Set to true if the confirmation when exiting the installer needs to be shown Example SHOW EXIT CONFIRMATION true Name NEXT SESSION Datatype Boolean Description Set to true to allow users to go back to the File Locations page for another installation This flag also needs to be set to true in order to process another response file see NEXT SESSION RESPONSE Example NEXT SESSION true A A ea ke tee ee ee ee ee ee NEXT SESSION true mcr onc CIIM Pn Name NEXT SESSION ON FAIL Datatype Boolean Description Set to true to allow users to invoke another session even if current install session has failed This flag is only relevant if NEXT SESSION is set to true Example NEXT SESSION ON FAIL true r O ea NEXT SESSION ON FAIL true Heck etter thee meee ete rhe eee ee ie oe ee me e Name SHOW DEINSTALL CONFIRMATION Datatype Boolean Description Set to true if deinstall confimation is needed during a deinstall session Example SHOW DEINSTALL CONFIRMATION true Name SHOW DEINSTALL PROGRESS
2. sss 2 14 Sample Oracle Home Directory Structure and Content sss 2 14 Variable Types and Representations seseeeese eee eee eee nennen nennt 3 5 Command Line Parameters for Prerequisite Checks sss 4 2 Parameters in oraparam ini cocccccccccnonnnnnnnorenncnnonrananacnnnnnnnnnnnnnrennnnrneranarern narran nne nnne nnne 4 3 Command line arguments in the clone pl script 6 5 UNIX and Linux System Based Variables for clone pl with the O Option 6 16 Windows System Based Variables for clone pl with the O Option 6 17 OPatch OUI based Commands cccccccccssessssecssecessecsseecseceesessecesscesseceaeecascesseecsseeeseceseeenseceseess 7 9 Apply Options for OUI Patches sse eene e nene nnns 7 10 Napply Options for OUI Patches sse nen nnns 7 13 Lsinventory Options for OUI Patches sese eee nene nenne 7 16 Query OP TONS M OT 7 17 Rollback Options for OUI Patches eese eee eene nennen 7 18 Nrollback Options for OUI Patches sssssssssseeeenen eene 7 20 OPatch Standalone Commands esses ethernet entere entren 7 23 Apply Options for Standalone Patches sss eene 7 24 Lsinventory Options for Standalone Patches sss 7 26 Query Opti ns scat eei ede NN 7 26 Rollback Options for Standalone Patches 7 27 Getting Pa
3. 6 10 Adding Nodes Using Cloning in Oracle Real Application Clusters Environments 6 11 Cloning Oracle RAC Environments on UNIX and Linux System Based Environments 6 11 vii Cloning Oracle Clusterware on UNIX and Linux System Based Environments 6 11 Cloning Oracle RAC Software on UNIX and Linux System Based Environments 6 12 Cloning Oracle RAC Environments on Windows System Based Environments 6 13 Cloning Oracle Clusterware on Windows System Based Environments 6 13 Cloning Oracle RAC Software on Windows System Based Environments 6 15 Cloning Script Variables and their Definitions sse eee 6 15 Variables for UNIX and Linux System Based Environments sess 6 16 Variables for Windows System Based Environments esses 6 17 7 Patching Oracle Software with OPatch About OPatel viii teet teure mde pee c men ee is niesie estet 7 1 OPatch Features 52iom ebbe eoe gnat Ban e dio ec tede rte de hebdo tva ptus 7 1 Getting Interim Patches o Dei tiet aee ip diete ee SER e 7 2 Environment Variables OPatch Uses sss tntntne trennen tn 7 2 Requirements fof OPatcli tete eterne A Deer ee enne AA eene 7 2 Prerequisite Checks for OPatch sess eene nennen nnne nnne recio 7 3 Checks for Single Instances and Real Application Clusters esses
4. sete a fetes Pe et Sele te ee aa DEINSTALL LIST oracle swd 2 2 1 2 0 RET Name SHOW SPLASH SCREEN Datatype Boolean Description Set to true if the initial splash screen in the installer needs to be shown Example SHOW SPLASH SCREEN true guis ae Fie a nen Pa A Tee a ae er eee SHOW_SPLASH SCREEN true PRECII I ee Lenten sions heme wtih Sh SUE CRUENTO E ERU eee AO ee Name SHOW WELCOME PAGE D 2 Oracle Universal Installer and OPatch User s Guide Sample Response File Datatype Boolean Description Set to true if the Welcome page in the installer needs to be shown Example SHOW WELCOME PAGE false He en Ie eam he eee ee eee E Reo ee eee See eee eret SHOW WELCOME PAGE false Host o E E E E E E E EE E E E Name SHOW COMPONENT LOCATIONS PAGE Datatype Boolean Description Set to true if the component locations page in the installer needs to be shown This page only appears if there are products whose installed directory can be changed I you set this to false you will prevent the user from being able to specify alternate directories Example SHOW COMPONENT LOCATIONS PAGE false AEE A SHOW COMPONENT LOCATIONS PAGE false rac M M ERREUR MMC E Ke Name SHOW CUSTOM TREE PAGE Datatype Boolean Description Set to true if the custom tree page in the installer needs to be shown In this page dependencies ca
5. esses enne eene erret nns B 3 erp I ati B 4 C Understanding Oracle Universal Installer Commands Options Available in Oracle Universal Installer sees eese eem C 1 Command line Variables Available in Oracle Universal Installer ssssss C 3 D Sample Files Sample Response Files ccoo seuss rie soz locas orcas ii ira iia D 1 Sample ORAPARAM INI File eese ai eenaa ear aeaaea ntt Ee ra Larai Sample Components File Index List of Figures 5 1 7 1 7 2 7 3 B 1 Troubleshooting Real Application Clusters Oracle Clusterware Installation 5 27 Al Node Patching ee rnt rere eee Eee Pee e rire e en etie Uta 7 34 Roling Patching eissien ini 7 34 Minimum Downtime Patching sees eee eene nnnenen 7 35 Setting Exceed s Window Manager to Native coconocncocononeneonnnnnnecnnncnrnenernrannncnrarnonrneraranannnoa B 5 Xi List of Tables xii 7 1 7 10 7 11 7 12 7 13 7 14 7 15 7 16 7 17 7 18 7 19 7 20 7 21 7 22 8 1 C 1 C 2 Oracle Installation Settings for Specify Home Details page ssssssssssss 2 2 ARU IDs ot Platforms entera tette Cede ede a edt etd 2 6 Other Folders in the Oracle Home Inventory sssssssssssseeeeeere ee 2 7 Oracle Home Directory for Windows Platforms sess 2 13 Sample ORACLE BASE Directory Structure and Content
6. Common Settings Monitor Info Use AllMonitors Monitors To Use For Screen f1 Window Mode Multiple AW Panning gt A g uto Load XRDB Default C Single Speed Slow y File srdb t t Ad d vanced Server Visual Amount 25 Edit Browse Auto Select Be Root Size pixels y Window Manager Width p Default To Native F Use Native WM for Embedded Clients Height p Fit Window To Display IV Cascade Windows Cancel Help Another known issue where Exceed fails to recognize fonts is documented at the following site http developer java sun com developer bugParade bugs 4262023 html Reflection X a Refection X 6 24 Select Settings Window Manager Default Local Window Manager Reflection Window Manager You may also have to select X terminal desktop m Reflection X 6 0 Select Connection New XDMCP Connection Connection Settings Direct method type host destination and click Connect Tarantella There is a known problem when using Tarantella to send DISPLAY to your Windows system for instance when using hosted UNIX systems The bottoms of some Oracle Universal Installer screens may appear truncated with buttons not visible The problem occurs only when you use an individual Tarantella terminal window so that the Oracle Universal Installer window appears alone without a broader X windowing environment To work around this problem do
7. export ORACLE HOME a Cshell setenv ORACLE BASE u01 app oracle setenv ORACLE HOME u01 crs oracle product 11 1 0 crs oo 4 Enter the following commands to ensure that the TNS_ ADMIN environment variable is not set Bourne Bash or Korn shell unset TNS ADMIN a Cshell unsetenv TNS ADMIN 5 To verify that the environment has been set correctly enter the following commands umask env more Verify that the umask command displays a value of 22 022 or 0022 and the environment variables that you set in this section have the correct values Pre installation Tasks for Real Application Clusters on Windows You need to complete the following pre installation tasks before you start the Oracle Universal Installer to install Oracle Clusterware and Oracle Real Application Clusters on Microsoft Windows systems Checking Hardware and Software Certification Oracle recommends you to review the certification matrix on the OracleMetaLink Web site for the most up to date list of certified hardware platforms and operating system versions for Oracle software This Web site also provides patches and workaround Installing Cluster Environments 5 13 Pre installation Tasks for Real Application Clusters on Windows information for bugs For more information on accessing the OracleMetaLink site see Download and Install Patches on page 5 22 Checking the Hardware Requirements Each system must meet minimum ha
8. 2 10 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Inventory Cause The Oracle home may be missing from the Central Inventory or the Central Inventory could be missing or corrupted Action Do the following Ifthe Oracle home is missing from the Central Inventory perform an attach home operation on the missing Oracle home The Central Inventory will be restored Ifthe Central Inventory is missing or corrupted restore the Central Inventory If you have not backed up the Central Inventory perform an attach home operation For more information on the attach home operation see Creating the Central Inventory on page 2 7 If multiple entries are in the inventory xml file for a given Oracle home Inventory Collection from the Grid Control perspective would have issues In this event you should remove these duplicate entries manually Here are some examples of the kind of incorrect entries that could be there HOME NAME db11g LOC product dbilg TYPE O IDX 1 gt HOME NAME oms11g LOC product em oms11g TYPE O IDX 2 gt HOME NAME db11g LOC product dbilg TYPE O IDX 3 gt In the above example the first and third entries are duplicates The Oracle home name and Oracle home location are identical In this example remove the third line Note that all duplicate inventory issues are caused by manual updates to the inventory xml file Use the OUI APIs to change th
9. See Oracle Universal Installer Inventory on page 2 1 for more information on the Central Inventory The remainder of this chapter describes the various parameters and settings you can modify within an Oracle Universal Installer response file Modifying a Response File If your product installation includes a response file template you can find it on your stage CD ROM under the root of CD gt response directory If your product installation does not include a response file template you can create a response file based on the installation options you select See Creating a Response File With Record Mode on page 3 2 for more information To modify the response file 1 Make a copy of the product s response file and open it in a text editor 3 2 Oracle Universal Installer and OPatch User s Guide Creating a Response File With Record Mode 2 Review any information provided in the response file or in the product installation guide Many software products use settings in the response file to customize the installation of their particular product See the response file template for suggestions or guidelines on how to set up the file for your installation 3 Getfamiliar with the organization and content of the response file using the information in the section Response File Format on page 3 4 4 Modify the response file to meet the needs of your organization and save the modified version 5 Seethe section In
10. Specifies to error out if the current patch s bugs to fix is a superset or same set of an installed patch s bugs fixed in the Oracle home directory Bypasses the inventory for reading and updates You cannot use this option with the local option This option places the installation into an unsupported state 7 10 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Table 7 2 Cont Apply Options for OUI Patches Option Description no relink no sysmod oh opatch init end opatch post end opatch pre end Patch Location post pre property file ptlConnect ptlPassword ptlSchema remote_nodes report retry runSql silent sqlScript This option does not perform any make operations You can use it during multiple patch applications and to perform the linking step only once OPatch does not keep track of the make operations it did not perform You need to make sure to execute OPatch without this option at the end for compilation Specifies that OPatch does not need to update the files in the system It only updates the inventory It also does not execute the pre and post scripts Specifies the Oracle home directory to use instead of the default This takes precedence over the environment variable ORACLE HOME Marks the end of the init options You use this option with the init option If you do not use this option everything after init until
11. Note that if you are cloning from an existing installation you should use 1 tableList Do not specify this variable for a clone installation ret PrivIntrList String List Return value from the Private Interconnect Enforcement table This variable has values in the format Interface Name Subnet Interface Type The value for Interface Type can be one of the following n 1 to denote public 2 to denote private a 3 to denote Do Not Use For example eth0 10 87 24 0 2 eth1 140 87 24 0 1 eth3 140 74 30 0 3 You can run the ipconfig command to identify the initial values from which you can determine the entries for ret PrivIntrList Sl tableList String List Set the value of this variable to be equal to the information in the cluster configuration information table This file contains a comma separated list of values The first field designates the public node name the second field designates the private node name and the third field designates the virtual host name Only OUI uses the fourth and fifth fields and they should default to N Y OUI parses these values and assigns s publicname and s privatename variables accordingly For example node1 nodel priv nodel vip N Y node2 node2 priv node2 vip N y S votingdisklocation String Set the value of this variable to be the location of the voting disk For example oradbshare oradata vdisk 6 16 Oracle Universal Installer and OPatch User s Guide Adding No
12. SHOW OPTIONAL CONFIG TOOL PAGE Datatype Boolean Description Set to true if the optional config tools page in the installer needs to be shown This page shows the list of optional configuration tools that are part of this installation and are configured to launch automatically It shows the status of each tool including any failures with detailed information on why the tool has failed Example SHOW OPTIONAL CONFIG TOOL PAGE true A O eMe eR tie as ae ire a ee en e ee aN tage Seta ei SHOW OPTIONAL CONFIG TOOL PAGE true DERE I eS O eee ee ee eee ee eee Rhee ae trae EI hes Name SHOW RELEASE NOTES Sample Files D 3 Sample Response File Datatype Boolean Description Set to true if the release notes of this installation need to be shown at the end of installation This dialog is launchable from the End of Installation page and shows the list of release notes available for the products just installed This also requires the variable SHOW_END SESSION PAGE variable to be set to true Example SHOW RELEASE NOTES true Hed Soe See te el eee ee A ee SE ee SHOW_RELEASE NOTES true a A a ER EN ccce Name SHOW ROOTSH CONFIRMATION Datatype Boolean Description Set to true if the Confirmation dialog asking to run the root sh script in the installer needs to be shown Valid only in Unix platforms Example SHOW ROOTSH CONFIRMATION true r0
13. Scripts JAR NAME install2 jar BOOK NAME oracle server hs gt PRE REQ DEF F gt PROD HOME DEF F gt LANG IDX MAP LANG LIST en fr ar bn pt BR bg fr CA ca hr cs da nl ar EG en GB et fi de el iw hu is in it ja ko es lv lt ms es MX no pl pt ro ru zh CN sk sl es ES sv th zh TW tr uk vi gt LANGSET IDX 1 BITSET 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 gt LANGSET IDX 2 BITSET 0 gt LANGSET IDX 3 BITSET 2 gt lt LANGSET IDX 4 BITSET 7 gt lt LANGSET IDX 5 BITSET 9 gt lt LANGSET IDX 6 BITSET 16 gt lt LANGSET IDX 7 BITSET 10 gt lt LANGSET IDX 8 BITSET 25 29 38 gt lt LANGSET IDX 9 BITSET 17 gt lt LANGSET IDX 10 BITSET 1 gt lt LANGSET IDX 11 BITSET 19 gt lt LANGSET IDX 12 BITSET 22 gt lt LANGSET IDX 13 BITSET 18 gt lt LANGSET IDX 14 BITSET 23 gt lt LANGSET IDX 15 BITSET 24 gt lt LANGSET IDX 16 BITSET 30 gt lt LANGSET IDX 17 BITSET 11 gt lt LANGSET IDX 18 BITSET 31 gt LANGSET IDX 19 BITSET 4 32 gt lt LANGSET IDX 20 BITSET 4 gt lt LANGSET IDX 21 BITSET 33 gt lt LANGSET IDX 22 BITSET 34 gt lt LANGSET IDX 23 BITSET 39 gt lt LANGSET IDX 24
14. Specifies the ORACLE HOME folder name This is used only on Windows platform Specifies the ORACLE HOME service name This is used only on Windows platform Specifies an anonymous login Specifies the login name Specifies the password Specifies the login category Specifies the group name on a UNIX platform Specifies the location from where the component gets installed This is the complete path to the products xml file Specifies the label of the CD where the products xml file resides in a multi CD installation The label can be found in the file disk label in the directory where the products xml resides Specifies the languages in which the components will be installed Specifies the selected languages Specifies the selected platforms Specifies the top level component to be installed in the current session Specifies the top level component id Specifies the installation type of the components Specifies whether the splash screen will be displayed in the current session Set to true if the splash screen needs to be displayed Specifies whether the welcome screen will be displayed in the current session Set to true if the Welcome page in the Oracle Universal Installer needs to be displayed Set to true if the confirmation dialogue asking to run the root sh script in the Oracle Universal Installer needs to be shown This flag can only be passed on UNIX platforms Specifies whether to display the confirmation dialo
15. Specifying a Response File To start Oracle Universal Installer and specify the response file enter the following command at the command line in the directory where the executable file is installed setup exe responseFile filename optional parameters on Windows runInstaller responseFile filename optional parameters on UNIX Note You must specify the complete responseFile path If you do not Oracle Universal Installer assumes the location to be relative to the oraparam ini associated with the launched Oracle Universal Installer Customizing and Creating Response Files 3 11 Installing with a Response File For help on command line usage enter the following at the command line in the directory where the executable file is stored setup help on Windows runInstaller help on UNIX In Windows when you execute setup help a new command window appears with the Preparing to launch message A moment later the help information appears in that window Optional Parameters When Specifying a Response File Optional parameters you can use with the responseFile flag are nowelcome Use the nowelcome flag with the responseFile flag to suppress the Welcome dialog that appears during installation a silent Use the silent flag with the responseFile flag to run Oracle Universal Installer in complete silent mode Note that the Welcome dialog is suppressed automatically formC
16. escaped double quotes gt opatch post end no sysmod property file Path to property file gt local node Local node name gt remote nodes List of remote nodes nodel node2 gt all nodes report Example The following example rolls back patches 1 2 and 3 that have been installed in the Oracle home opatch nrollback id 1 2 3 Options Table 7 7 lists the options available for this command Table 7 7 Nrollback Options for OUI Patches Option Description all nodes Rolls back the patch using the all nodes mode delay If you use the retry option with the rollback command specifies how many seconds OPatch should wait before attempting to lock the inventory again if a previous failure Occurs id Indicates the patch to be rolled back Use the 1sinventory option to display all patch identifiers Each one off patch is indicated by its ID To successfully roll back a patch you must provide the patch identifier invPtrLoc Specifies the location of the oraInst loc file You need to use this option if you used the invPtrLoc option during installation Oracle recommends the use of the default Central Inventory for a platform jdk Instructs OPatch to use JDK jar from the specified location instead of the default location under the Oracle home directory If you do not specify the j re option JVM is executed from the 3 dk location jre Specifies the location of a particular JRE Java for OP
17. lt PRD_LIST gt TL LIST COMP NAME oracle server VER 11 1 0 0 0 BUILD NUMBER 0 REP VER 0 0 0 0 0 RELEASE Production INV LOC Components oracle server 11 1 0 0 0 1 LANGS en Sample Files D 7 Sample Components File XML INV LOC Components21 oracle server 11 1 0 0 0 ACT INST VER 11 1 0 0 0 DEINST VER 11 1 0 0 0 INSTALL TIME 2007 Jun 03 11 39 07 IST INST _LOC home shiva oracle product 11 1 0 db 2 oracle server EXT NAME Oracle Database 11g EXT NAME lt DESC gt Installs an optional pre configured starter database product options management tools networking services utilities and basic client software for an Oracle database server DESC lt DESCID gt COMPONENT_DESC lt DESCID gt STG INFO OSP _VER 11 1 0 0 0 gt CMP JAR INFO INFO NAME filemapObj VAL Components oracle server vll 1 0 0 _0 filemap xml gt INFO NAME helpDir VAL Components oracle server vll 1 0 0 0 help gt INFO NAME actionsClass VAL Components oracle server vll 1 0 0 _0 CompActions gt INFO NAME resourceClass VAL Components oracle server v11 1 00 _0 resources CompRes gt INFO NAME identifiersXML VAL Components oracle server vll 1 0 0 0 identifiers xml gt INFO NAME contextClass VAL Components oracle server vll 1 0 0_ 0 CompContext gt INFO NAME fastCopyLogXML VAL Components oracle server v1l1_1 0 0 0 fastCopyLog xml gt lt CMP_JAR_INFO gt LOC INFO INST DFN LOC
18. opatch post end no sysmod property file Path to property file gt init parameters for the init script in escaped double quotes opatch init end report Patch Location gt Options Table 7 9 lists the options available for the Apply command Table 7 9 Apply Options for Standalone Patches Option Description force Removes conflicting patches from the system by enabling you to change the product and version number of the standalone Oracle home OPatch removes all the conflicting patches before applying the current patch init Passes parameters to the init script which executes before prerequisite checks are run The values for this option must be enclosed in double quotes jre Instructs OPatch to use JRE Java from the specified location instead of the default location under the Oracle home directory no bug superset Specifies to error out if the current patch s bugs to fix is a superset or same set of an installed patch s bugs fixed in the Oracle home directory no inventory Bypasses the inventory for reading and updates You cannot use this option with the local option This option places the installation into an unsupported state 7 24 Oracle Universal Installer and OPatch User s Guide Standalone Patching Table 7 9 Cont Apply Options for Standalone Patches Option Description no relink no sysmod oh opatch init end opatch post end opatch pre end
19. 1 2 Oracle Universal Installer and OPatch User s Guide Actions Performed by the Utilities Oracle Universal Installer to install Oracle products OPatch to apply interim patches Oracle Universal Installer OPatch Oracle Universal Installer 11g Release 1 11 1 is a Java based installer that enables you to install Oracle components from CDs or from a staged HTTP location It performs component based installations as well as complex installations such as integrated bundle and suite installations and installations over the Web OPatch is an Oracle supplied utility that assists you with the process of applying interim patches to Oracle s software OPatch 11 1 is a Java based utility that can run on either OUI based Oracle homes or standalone homes It works on all operating systems for which Oracle releases software For more information on OPatch see Chapter 7 Patching Oracle Software with OPatch Actions Performed by the Utilities Installation Deinstallation Cloning Patching Oracle Universal Installer and OPatch performs the following activities Installation is the process of choosing products from a release or stage area and deploying them in the target directory There are four modes of installation which are explained in the section Modes of Installation on page 1 5 Deinstallation is the process of removing an installed product from the installation area A de installation can be cancelled resumed o
20. Deinstalling Oracle Product Software on UNIX The following steps describe how to use Oracle Universal Installer to remove Oracle software from an Oracle home on UNIX systems Note Always use Oracle Universal Installer to remove Oracle software Do not delete any Oracle home directories without first using Oracle Universal Installer to remove the software Installing Cluster Environments 5 23 Deinstalling Real Application Clusters Software 1 Ifnecessary log in as the oracle user su oracle 2 Setthe ORACLE HOME environment variable to specify the path of the Oracle home directory that you want to remove Bourne Bash or Korn shell ORACLE HOME u01 app oracle product 11 1 0 db 1 export ORACLE HOME a Cshell setenv ORACLE HOME u01 app oracle product 11 1 0 db 1 3 Stop all processes running in this Oracle home 4 Start Oracle Universal Installer with the deinstall flag When you use this flag only the deinstallation occurs on the specified components The Oracle home is not removed from the Central Inventory This is equivalent to selecting only the components and clicking Deinstall in the GUI The syntax is as follows runInstaller deinstall ORACLE HOME LOCATION OF ORACLE HOME gt You can use the REMOVE HOMES variable to specify the location of the Oracle home to be removed When you use this variable the deinstallation occurs for the specified components and the Oracle home is removed fro
21. Home NAME sub key of the ORACLE key When an additional Oracle home is added to the system the PATH variable is adjusted again to add the new BIN directory of the newly installed Oracle software The registry variables are written to a key named KEY HOME NAME Oracle Home Directory Structure for Windows Platforms A typical Oracle home on Windows platforms contains the files and directories shown in Table 2 4 Table 2 4 Oracle Home Directory for Windows Platforms Oracle Home Directory Contents NBIN Product executable and DLLs LIB DLL files JLIB All JAR files DBS Common message files PROD1 PROD1 product files PROD2 PROD2 product files Optimal Flexible Architecture Directory Structure on UNIX The Optimal Flexible Architecture OFA standard is a set of configuration guidelines for fast reliable Oracle databases that require little maintenance OFA is designed to Organize large amounts of complicated software and data on disk to avoid device bottlenecks and poor performance Facilitate routine administrative tasks such as software and data backup functions which are often vulnerable to data corruption Alleviate switching among multiple Oracle databases Adequately manage and administer database growth Help eliminate fragmentation of free space in the data dictionary isolate other fragmentation and minimize resource contention The OFA directory structure is described in the following
22. If a bug superset condition is detected it is not considered an error situation All the subset patches are removed from the system and the new patch is applied Example Consider the following scenario a Patch A installed in the Oracle home fixed bugs 1 2 and 3 Patching Oracle Software with OPatch 7 35 About Patch Conflicts Patch B installed in the Oracle home fixed bugs 10 11 and 12 a Patch C to be installed fixes bugs 1 2 3 and 4 Patch C is considered a superset of Patch A Using the no bug superset Flag If you want OPatch to error out if the current patch bugs to fix is a superset or the same as an installed patch bugs fixed in the Oracle home directory you can use the no bug superset flag OPatch opatch apply no bug superset Path To Patch The following example output shows the message you would see when you use the no bug superset flag Oracle interim Patch Installer version 11 2 0 0 0 Copyright c 2007 Oracle Corporation All rights reserved Oracle Home home oracle TEST product 11 1 0 db 1 Central Inventory home OUIHome Opatch from home oracle TEST product 11 1 0 db 1 oraInst loc OPatch version 11 1 0 04 0 OUI version 11 1 0 0 0 OUI location home oracle TEST product 11 1 0 db 1 oui Log file location home oracle TEST product 11 1 0 db _1 cfgtoollogs opatch opatch 2007 May 25 14 03 33 IST Wed log ApplySession applying interim patch 111000 to OH home oracl
23. Product Language Selections Language Add on Installation Dialogs Language Oracle Universal Installer runs in the language of the operating system Oracle Universal Installer uses the language that Java detects the system locale value and sets that to the default language The Oracle Universal Installer dialogs are displayed in this language if available If specific Oracle Universal Installer dialogs are not translated in the language of the operating system these dialogs are shown in English Oracle Universal Installer displays the translated GUI only if the variable NLS ENABLED has been set to TRUE in the oraparam ini file If the NLS ENABLED variable is set to FALSE all text is shown in English Product Language Selections If multiple languages are defined for the products installed Oracle Universal Installer allows language selection for all installation types through the Languages button shown on the Available Products page when there is more than one top level component Note Ifthere is only one top level component the Languages button is shown on the Install Types page If the staging area has only one top level component with only one installation type the button is not shown and a Language Selection dialog is displayed later in the installation You can also control the selected languages by setting the SELECTED LANGUAGES variable in a response file or through the command line setup exe SELECTED LANGUAGE
24. The cloning process copies all of the files from the source Oracle home to the destination Oracle home Thus any files used by the source instance located outside the source Oracle home s directory structure are not copied to the destination location Cloning Oracle Software 6 1 Overview of the Cloning Process The size of the binaries at the source and the destination may differ because these are relinked as part of the clone operation and the operating system patch levels may also differ between these two locations Additionally the number of files in the cloned home would increase because several files copied from the source specifically those being instantiated are backed up as part of the clone operation OUI cloning is more beneficial than using the tarball approach because cloning configures the Central Inventory and the Oracle home inventory in the cloned home Cloning also makes the home manageable and allows the paths in the cloned home and the target home to be different Overview of the Cloning Process The cloning process uses the OUI cloning functionality This operation is driven by a set of scripts and add ons that are included in the respective Oracle software The cloning process has two phases Source Preparation Phase Cloning Phase Source Preparation Phase To prepare the source Oracle home to be cloned perform the following steps a At the source run a script called prepare clone p1 This is a Pe
25. Upgrading and Patching the Oracle Home You can apply patchsets and upgrade an existing Oracle home You can apply patchsets using Oracle Universal Installer For more information on upgrading or applying patchsets for an Oracle product refer to the respective Oracle product installation guide of the product that you want to upgrade Cloning Oracle Homes You can clone an Oracle home using Oracle Universal Installer For more information on cloning see Chapter 6 Cloning Oracle Software Backing up the Inventory You can back up the Oracle home using your preferred method You can use any method such as zip tar and cpio to compress the Oracle home Managing Oracle Homes 2 9 Oracle Universal Installer Inventory It is highly recommended to back up the Oracle home before any upgrade or patch operation You should also back up the Central Inventory when Oracle home is installed or deinstalled Example Consider a scenario where you have a Database Oracle home called DBHome that is registered with the default Central Inventory in the product directory You want to patch this database but decide to back up the database before patching 1 Enter the following to back up the database cd product DBHome tar cf gzip product archive DBHome tar gz If you are using a Win32 system you could use WinZip to zip up the Oracle home Do not use the jar command to zip the Oracle home as this causes the file permissions to be
26. You can run and manage checks from the command line for a silent installation For silent installations Oracle Universal Installer performs as many prerequisite checks as possible alerts you for all errors if any and provides the location of the installActions lt timestamp gt log file before exiting Standalone You can run checks without completing an installation See Table 4 1 for a description of the flags to use Installing Products 4 1 Installing Oracle Products Table 4 1 Command Line Parameters for Prerequisite Checks Command Description paramFile file Use this flag to specify the location of the oraparam ini file name to be used For example you can create your own parameters file and use that to operate Oracle Universal Installer Note that Oracle Universal Installer uses the file you specify for all operations including the prerequisite checks executeSysPreregs Use this flag on the command line to perform only the prerequisite check without continuing the installation This can be used to verify that the basic prerequisites have been met before deciding to perform an installation ignoreSysPrereqs Use this flag on the command line to ignore all prerequisite checks This may be useful when you know that the checks are faulty or the environment has already been verified This is an optional flag though not recommended by Oracle Inputs to the checker are listed in the prerequisite xml file Af
27. out files are also created and stored in the same logs directory The 10g err and out files for a particular session will be named with the same timestamp The installation log is used for debugging purposes only All actions queries everything that happens during the installation and all modifications to the target host are logged in the file A sample file is shown below installActions2002 08 16 09 52 16 AM log Environment variables ORACLE HOME PATH E OEM bin E ORACLE815 bin C Program Troubleshooting and Debugging Oracle Universal Installer B 1 Debugging Mechanisms in Oracle Universal Installer Files Oracle jre 1 1 7 bin C ORATST BIN CLASSPATH C Program Files Exceed nt hcljrcsv zip Username is jdoe The installer version is 2 2 1 0 0 Welcome Page Setting value of FROM LOCATION to E bootstrap cd Disk1 stage products jar Setting value of INVENTORY LOCATION to C Program Files Oracle Inventory Setting value of UNIX_GROUP_NAME to Setting value of FROM LOCATION to E bootstrap cd Disk1 stage products jar Setting value of ORACLE HOME to E Universal Setting value of ORACLE HOME NAME to Universal File Locations Page FromLocation FROM LOCATION E bootstrap cd Disk1 stage products jar ToLocation ORACLE HOME E Universal ToName ORACLE HOME NAME Universal Initializing installer access setup Setting value of ORACLE HOME to E Universal Setting value of ORACLE HOME
28. perform the compilation step only once Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE HOME environment variable Marks the end of the post options Use this option with the post option If you do not use this option everything after post until the end of the command is passed into post Marks the end of the pre options Use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies Specifies to OPatch the list of remote nodes to be used for rollback of the patch The node names must be separated with commas but without spaces You can use this option on Oracle Real Application Clusters environments Prints the actions to the screen without executing them Instructs OPatch how many times it should retry when there is an inventory lock failure Suppresses user interaction and defaults any yes no questions to yes A Real Application Clusters setup does not support this option Prints additional OPatch output to the screen as well as to the log file Patching Oracl
29. post parameters for the post script in escaped double quotes opatch post end no sysmod property file Path to property file local node Local node name remote nodes List of remote nodes nodel node2 all nodes phBaseFile Path to the file containing the location of the patches to be applied skip subset skip duplicate report Examples a The following example applies all patches under the patch location directory opatch napply patch location The following example applies patches 1 2 and 3 that are under the patch location directory opatch napply patch location id 1 2 3 The following example applies all patches under the patch location directory OPatch skips duplicate patches and subset patches patches under patch locations that are subsets of patches installed in the Oracle home opatch napply patch location skip subset skip duplicate See the description for the skip subset option in Table 7 3 for more information 7 12 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes The following example applies patches 1 2 and 3 that are under the patch location directory OPatch skips duplicate patches and subset patches patches under patch locations that are subsets of patches installed in the Oracle home opatch napply patch location id 1 2 3 skip subset skip duplicat
30. responseFile response file path For Oracle Clusterware you need to use the ormCluster flag You can pass session variables like nodelist ocr voting disk location and so forth from the command line for silent installation Oracle Clusterware Background Processes The following processes must be running in your environment after the Oracle Clusterware installation for Oracle Clusterware to function oprocd Process monitor for the cluster evmd Event manager daemon that starts the racgevt process to manage call outs ocssd Manages cluster node membership and runs as the Oracle user failure of this process results in node restart crsd Performs high availability recovery and management operations such as maintaining the OCR Also manages application resources and runs as the root user and restarts automatically upon failure Installing Oracle Clusterware on Windows This section provides you with information about how to use the Oracle Universal Installer to install Oracle Clusterware on Windows Running the Oracle Universal Installer to Install Oracle Clusterware Complete the following steps to install Oracle Clusterware on your cluster At any time during installation if you have a question about what you are being asked to do click Help in the Oracle Universal Installer page 1 Log in to Windows with Administrative privileges and run the setup exe command on the Oracle Clusterware media This ope
31. silent installation definition 3 1 reasons for performing 3 2 silent mode installing clusterware 5 16 single instance nodes converting to Real Application Clusters 5 27 Solaris Central Inventory pointer file 2 4 SOURCE parameter in ORAPARAM INI 4 3 specifying value of component variable 3 13 value of session variable 3 12 SSH configuration 5 6 staged HTTP location installing from 4 8 starting Oracle Universal Installer 4 12 storage clusterware 5 15 stty commands 5 8 system requirements diskspace 1 1 JRE 1 1 memory 1 1 T Tarantella troubleshooting B 5 targethome 2 3 TEMP TMP directory for CD ROMs 4 7 third party applications components file and 2 6 TOPLEVEL_COMPONENT parameter 3 8 translation installation dialogs language 8 1 language add on 8 2 product language selections 8 1 troubleshooting automated inventory backups B 3 central inventory backup B 3 debugging mechanisms B 1 Exceed B 4 installation log B 1 Oracle Universal Installer errors B 3 Reflection X B 5 Tarantella B 5 U UNIX creating required groups and users 5 5 directory structure for 2 13 installing Oracle clusterware 5 15 special installation instructions 4 8 UNIX GROUP NAME parameter 3 8 updating nodelist 1 4 nodes fora cluster 2 12 upgrades of products 1 4 USE BUILD NUMBER parameter in ORAPARAM INI 4 5 user equivalency 5 7 using optional flags to detach Oracle homes 2 8 uti
32. 24 19 Oracle Database Utilities 11 1 0 COD OnRPHErHEHE LEY N NN DN FE o HL oH E oo oo fo ooooooooeororooorrerroeocoooooeo FF PP PP SP PP POR KF ua a9 WP WP PP WWW 0 ms PP SPP POR W O c O O O O uUi O A O x0 DS CE CX go C XX cx X CX 4 XE CO OCC ES CX ek OC A C X EA A A A A O O O o CEX GE UE POF FF FF FPO Patching Oracle Software with OPatch 7 5 Prerequisite Checks for OPatch Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Oracle Parser PL SQL PL SQL Display Fonts Enterprise Manager Console DB Extended Windowing Toolkit Globalization Support Globalization Support Help For Java Help for the Web Ice Browser interMedia interMedia Annotator interMedia Client Option interMedia Java Advanced Imaging interMedia Locator interMedia Locator RDBMS Files Internet Directory Client Java Client JDBC Server Support Package JDBC OCI Instant Client JDBC THIN Interfaces JFC Extended Windowing Toolkit JVM LDAP administration Locale Builder Message Gateway Common Files Net Net Listener Net Required Support Files Net
33. 35 types 7 35 debugging logging and tracing 7 39 recovering from failed patching 7 39 resolving application errors 7 45 description of process 1 3 environment variables 7 2 getting interim patches 7 2 online 7 32 OPatch utility for OUI based Oracle homes 7 8 prerequisite checks 7 3 problem resolution 7 38 Real Application Clusters all node patching 7 33 Real Application Clusters adding nodes using cloning 6 11 Cache Fusion 5 3 clusterware 5 2 converting single instance nodes to 5 27 creating UNIX groups and users 5 5 hardware requirements 5 3 installed components 5 2 inventory for 2 11 IP address requirements 5 10 network hardware requirements 5 9 parameter requirements 5 9 node time requirements 5 10 Oracle base directory 5 11 5 12 Clusterware home directory 5 12 home directory 5 12 inventory directory 5 11 patching all node patching 7 33 minimum downtime patching 7 35 rolling patching 7 34 patchsets and upgrades 5 22 setup and pre install config tasks 5 4 software requirements 5 3 Index 5 SSH configuration 5 6 system installation requirements 5 3 troubleshooting 5 27 updating nodes 2 12 Real Application Tasks post installation tasks 5 22 backing up disk 5 22 configuring Oracle products 5 23 downloading and installing patches 5 22 verification 5 22 record mode 3 3 using to create response file 3 3 recovering from inventory corruption 2 10 2 11 Reflection X troubles
34. 7 8 Additional Checks for Real Application Clusters 7 4 Check for User Equivalence 6i oie tmt te d re hi on i Re UP tor ast 7 4 Check for OPatch L sinventoty inen tee tee qe tee tee etie i ga 7 4 Backup and Recovery Considerations for Patching sss 7 8 OPatch Utility for OUI based Oracle Homes sse eee eee ens 7 8 Apply Command for OUI based Oracle Homes oocoencncoconononennncnnnnnnnnnnnonnanaronennnnnnannrcrnarararannnnnraros 7 9 Napply Command for OUI based Oracle Homes sss 7 12 Lsinventory Command for OUI based Oracle Homes sss 7 15 Query Command for OUI based Oracle Homes sss 7 16 Rollback Command for OUI based Oracle Homes sees eee 7 17 Nrollback Command for OUI based Oracle Homes sse eee 7 20 Version Command for OUI based Oracle Homes sss 7 22 Standalone Patching noises ia ae S ee eee ete ce eme ee ESSR 7 22 Unsupported Services for Standalone Patching sss 7 22 Standalone Patching Requirements sss eee eene enne nnne nennen 7 23 OPatch Utility for Standalone HOMES ocooicicononinincnnonnnnonconananonononananononononanonon corona nennen nnne 7 23 Apply Command for Standalone OPatch sss 7 24 Lsinventory Command for Standalone OPatch sss 7 25 Query Command for Standalone OPatch s
35. All rights Reserved gt lt Do not modify the contents of this file by hand gt lt INVENTORY gt VERSION INFO SAVED WITH gt 11 1 0 0 0 lt SAVED WITH MINIMUM VER 2 1 0 6 0 MINIMUM VER VERSION INFO HOME LIST HOME NAME OraDbllg homel LOC home oracle dblig product 11 1 0 db 1 TYPE 0 IDX 1 gt HOME NAME OUIHome LOC D VOraHomel TYPE 0 IDX 2 gt HOME NAME OUIHome12 LOC D OraHomel2 TYPE 0 IDX 3 gt HOME NAME OUIHomel LOC D homes OraHome1 TYPE 0 IDX 4 gt HOME NAME OUIHomell1 LOC d homes ouill TYPE O IDX 2 REMOVED T gt HOME LIST INVENTORY Note Oracle recommends that you do not remove or manually edit this file as it could affect installation and patching Logs Directory The Central Inventory contains installation logs in the following location central inventory location gt logs The logs directory contains the logs corresponding to all installations performed on a particular node You can also find a copy of the installation log in the SORACLE _ HOME cfgtoollogs directory The installation logs for an installation are identified by the timestamp associated with the log files These files are generally saved in the following format Name of Action YYYY MM DD HH MM SS AM PM log For example consider an at tachHome operation performed on 17th May 2007 at 6 45AM The associated log file would be c
36. BITSET 15 gt lt LANGSET IDX 25 BITSET 36 gt lt LANGSET IDX 26 BITSET 40 gt D 8 Oracle Universal Installer and OPatch User s Guide Sample Components File LANGSET IDX 27 BITSET 42 gt lt LANGSET IDX 28 BITSET 35 41 gt lt LANGSET IDX 29 B TSET 32 gt lt LANGSET IDX 30 B TSET 38 gt lt LANGSET IDX 31 B TSET 35 gt lt LANGSET IDX 32 B TSET 41 gt LANGSET IDX 33 B TSET 0 157 165 23 gt lt LANGSET IDX 34 B TSET 25 gt lt LANGSET IDX 35 BITSET 0 dy 4 6 16 18 22 23 24 25 29 35 38 41 gt lt LANGSET IDX 36 BITSET 0 23 gt lt LANGSET IDX 37 BITSET gt lt LANGSET IDX 38 BITSET 0 Ty 4 Ty 222523 24 35 398 41 gt lt LANGSET IDX 39 BITSET 1 25135 5435 55 7607 Li Oy 9 105 SET 2 13 714 15 16 I7 18 19 20 21 227 23 25 26 21 y 428 295 305 31 32 33 34 36 37 38 39 40 42 43 44 gt lt LANGSET IDX 40 BITSET 1 25 Se AG b Oye Tj 95 9 10 L1 12 T3 14 15 16 17 18 19 20 21 22 23 24 25 26 27 298 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 gt LANG IDX MAP PLAT IDX MAP PLAT LIST 46 gt PLAT IDX MAP DST IDX MAP DST LIST SINVENTORY LOCATIONS ORACLE HOME s TMPDIR LOC s TEMP LOC gt DST IDX MAP DEP GRP LIST DEP GRP NAME Optional EXT NAME Pro
37. Clusterware configuration extend the Oracle Database software with RAC and then add the listeners and instances by running the Oracle assistants as described in the following procedures Cloning Oracle Clusterware on Windows System Based Environments Cloning Oracle RAC Software on Windows System Based Environments Cloning Oracle Clusterware on Windows System Based Environments Complete the following steps to clone Oracle Clusterware on Windows system computers Cloning Oracle Software 6 13 Adding Nodes Using Cloning in Oracle Real Application Clusters Environments 1 Skip this step if you have a shared Oracle Clusterware home If you do not have a shared Oracle Clusterware home zip the Oracle Clusterware home from the existing node and copy it to the new node Unzip the home on the new node in the equivalent directory structure as the directory structure in which the Oracle Clusterware home resided on the existing node For example assume that the location of the destination Oracle Clusterware home on the new node is CRS __ HOMES Note For more information on zipping and unzipping see Source Preparation Phase and Cloning Phase 2 On the new node go to the CRS_HOME clone bin directory and run the following command where CRS HOME is the location of the Oracle Clusterware home CRS HOME NAMEis the name of the Oracle Clusterware home and where new node new node privand new node vip are the name of the new
38. Clusterware software on the local node and validates the installation again The Oracle Universal Installer also creates any required OCFS file systems After validating the installation the Oracle Universal Installer completes the Oracle Clusterware software installation and configuration on the remote nodes 5 18 Oracle Universal Installer and OPatch User s Guide Adding More Nodes to the Cluster for Mass Deployment Running the Oracle Universal Installer in Silent Mode to Install Oracle Clusterware You can run the Oracle Universal Installer in silent mode to install Oracle Clusterware by entering the following command setup exe silent responseFile response file path For Oracle Clusterware you need to use the ormCluster flag You can pass session variables like nodelist ocr voting disk location and so forth from the command line for silent installation Oracle Clusterware Background Processes The following processes must be running in your environment after the Oracle Clusterware installation for Oracle Clusterware to function oprocd Process monitor for the cluster evmd Event manager daemon that starts the racgevt process to manage call outs ocssd Manages cluster node membership and runs as the Oracle user failure of this process results in node restart crsd Performs high availability recovery and management operations such as maintaining the OCR Also manages application resources and
39. Database home with Oracle RAC resided on the existing node For example assume that the location of the destination Oracle RAC home on the new node is SORACLE HOMES Note For more information on zipping and unzipping see Source Preparation Phase and Cloning Phase 2 Onthe new node go to the ORACLE HOMES V clone Vbin directory and run the following command where Oracle Home is the Oracle Database home Oracle Home Name is the name of the Oracle Database home existing node is the name of the existing node and new node is the name of the new node perl clone pl ORACLE HOME Oracle Home ORACLE HOME NAME Oracle Home Name O CLUSTER NODES existing node new node OLOCAL NODE new node O noConfig If you have a shared Oracle Database home with Oracle RAC append the O cfs option to the command example in this step and provide a complete path location for the cluster file system 3 On the existing node from the RAC_HOME oui bin directory run the following command where Oracle Home is the Oracle Database home with Oracle RAC existing node is the name of the existing node and new node is the name of the new node setup exe updateNodeList ORACLE HOME Oracle Home CLUSTER NODES existing node new node LOCAL NODE existing node 4 Onthe new node run NETCA to add a listener 5 From the node that you cloned run DBCA to add the database instance to the new node Cloning Script Variables and their Definiti
40. Datatype Boolean Description Set to true if deinstall progress is needed during a deinstall session Example SHOW DEINSTALL PROGRESS true D 4 Oracle Universal Installer and OPatch User s Guide Sample Response File Datatype StringList Description Languages in which the components will be installed The following choices are available The value should contain only one of these choices The choices are of the form Internal Name External name Please use the internal name while specifying the value en English ff French ar Arabic bn Bengali pt_BR Brazilian Portuguese bg Bulgarian fr_CA Canadian French ca Catalan hr Croatian cs Czech da Danish nl Dutch ar_EG Egyptian en GB English United Kingdom et Estonian fi Finnish de German el Greek iw Hebrew hu Hungarian 185 Icelandic in Indonesian it talian ja Japanese ko Korean es Latin American Spanish lv Latvian lt Lithuanian ms Malay es MX Mexican Spanish no Norwegian pl Polish pt Portuguese ro Romanian ru Russian zh_CN Simplified Chinese sk Slovak sl Slovenian es_ES Spanish sv Swedish th Thai zh_TW Traditional Chinese tr Turkish uk Ukrainian vi Vietnamese Example COMPONENT LANG
41. Example ORACLE HOME C OHOME1 A A A A ORACLE HOME Value Required ducis Sa Sh eo a c A Li eee Luce ie eL E LU LM eL pcr Name ORACLE HOME NAME Datatype String Description Oracle Home Name Used in creating folders services Example ORACLE HOME NAME OHOME1 A A AE iie eie ORACLE HOME NAME OHOMEI M Eq RM E TEE Name TOPLEVEL COMPONENT Datatype StringList Description The Toplevel component that has to be installed in the current session The following choices are available The value should contain only one of these choices The choices are of the form Internal Name Version External name Please use the internal name and version while specifying the value oracle swd 2 2 1 2 0 Oracle Installation Products 2 2 1 2 0 Example TOPLEVEL COMPONENT oracle swd 2 2 1 2 0 pi torio SEN si a a a tl Mo Dm ue ucc ae Lic t TOPLEVEL_COMPONENT oracle swd 2 2 1 2 0 A E A E A elm ed mate que akc et eae Ae ate ns Name DEINSTALL LIST Datatype StringList Description List of components to be deinstalled during a deinstall session The following choices are available The value should contain only one of these choices The choices are of the form Internal Name Version External name Please use the internal name and version while specifying the value oracle swd 2 2 1 2 0 Oracle Installation Products 2 2 1 2 0 Example DEINSTALL LIST oracle swd 2 2 1 2 0 Pr
42. Frequently Asked Questions A 1 Oracle Universal Installer more information on backing up the inventory see Backing up the Inventory on page 2 9 When your Oracle home inventory is corrupted or lost you can restore from the backup or you can install the Oracle home from an identical installation When I run the configuration assistants they fail What do I do To recover from this problem rename the configToolAllCommands and configToolFailedCommands files as follows In UNIX rename the configToolAllCommands and configToolFailedCommands files located in the OracleHome cfgtoollogs directory to configToolAllCommands sh and configToolFailedCommands sh respectively and execute them In Windows rename the configToolAllCommands and configToolFailedCommands files located in the OracleHome cfgtoollogs directory to configToolAllCommands bat and configToolFailedCommands bat respectively and execute them ConfigToolAllCommands sh bat is used when the installation was done with a noConfig option and you want to run all the configuration assistants in standalone mode outside the OUI context ConfigToolFailedCommands sh bat is used when the install was done with failed configuration assistants and you want to run only the failed configuration assistants later in standalone mode outside the OUI context When I apply a patchset or an interim patch the installer tries to propagate to a node that I disconnected a long time
43. If you do not have a shared Oracle Clusterware home tar the Oracle Clusterware home from an existing node and copy it to the new node Use CRS_ HOME as the destination Oracle Clusterware home on the new node Note For more information on archiving and unarchiving see Source Preparation Phase and Cloning Phase 2 If you do not have a shared Oracle Clusterware home navigate to the SORACLE HOME clone bin directory on the new node and run the following command where Oracle home name is the name of the Oracle home new node is the name of the new node new node priv is the private interconnect protocol address of the new node new node vipis the virtual interconnect protocol address of the new node and central inventory locationis the location of the Oracle Central Inventory perl clone pl ORACLE HOME SORACLE HOME ORACLE HOME NAME Oracle home name O sl tableList new node new node priv new node vip O noConfig O INVENTORY LOCATION central inventory location If you have a shared Oracle Clusterware home append the cfs option to the command example in this step and provide a complete path location for the cluster file system Cloning Oracle Software 6 11 Adding Nodes Using Cloning in Oracle Real Application Clusters Environments Note Only provide a value for the s1_tableList variable The Perl clone p1 script takes all other variable settings from the zipped Oracle Clusterware home This is only
44. Note Because most cloning is done in silent mode when cloning an Oracle home onto a clean host one that has no oralnst loc file Oracle Universal Installer creates a Central Inventory in the location specified by the INVENTORY LOCATION variable If this variable is not specified Oracle Universal Installer creates the Central Inventory in the cloned home oraInventory directory After cloning is finished you must run oraInstRoot shas root to move oraInventory to the final desired location About Oracle Universal Installer Log Files When you install or deinstall products using Oracle Universal Installer important information about each installation is saved not only in the inventory but also in a series of log files located in the following directory SORACLE HOME cfgtoollogs You can use these log files to troubleshoot installation problems These files are also crucial for removing and configuring the various software components you install on your Windows or UNIX computer Oracle Universal Installer displays the name and location of the current session s log file on the Install page Each installation or configuration utility provides a separate folder containing the logs inside the SORACLE HOME cfgtoollogs folder Note that the logs used to remove products are different from the installActions lt timestamp gt log generated during the install process The Installing Products 4 15 About Oracle Universal Installer Lo
45. OPatch commands option One of the OPatch command options Table 7 8 lists the commands available for standalone patching Table 7 8 OPatch Standalone Commands Command Description apply Installs an interim patch See Apply Command for Standalone OPatch for more information Isinventory Lists what is currently installed on the system See Lsinventory Command for Standalone OPatch for more information Patching Oracle Software with OPatch 7 23 Standalone Patching Table 7 8 Cont OPatch Standalone Commands Command Description query Queries a given patch for specific details See Query Command for Standalone OPatch for more information rollback Removes an interim patch See Rollback Command for Standalone OPatch for more information version Prints the current version of the patch tool See Version Command for Standalone OPatch for more information The following sections provide the syntax and options for each of these commands Apply Command for Standalone OPatch The Apply command applies an interim patch to a standalone home from the current directory Syntax Use the following syntax for this command opatch apply force jre LOC no bug superset no inventory oh ORACLE HOME silent verbose no relink pre parameters for the pre script in escaped double quotes opatch pre end post parameters for the post script in escaped quotes
46. Oracle Homes from the Central Inventory You can detach an Oracle home from the Central Inventory When you pass this flag it updates the inventory xml file present in the Central Inventory The syntax is as follows runInstaller silent detachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location gt ORACLE HOME NAME lt Oracle Home Names Using Optional Flags You can use the local flag to detach the Oracle home from the inventory of the local node If you are using a shared Oracle home use the cfs flag This ensures that the local node information is not populated inside a shared Oracle home runInstaller silent local cfs detachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt runInstaller silent detachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt You can completely clean the Oracle home and remove the home directory by using the removeallfiles flag The syntax is as follows runinstaller silent deinstall removeallfiles invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt If you want to disable the warning message that appears when you use the removeallfiles flag use the nowarningonremovefiles flag The syntax is as follows runInstaller silent deinstall nowarningonremovefiles invPtrLoc oraInst lo
47. Patch Location post pre property file silent verbose This option does not perform any make operations You can use it during multiple patch applications and to perform the linking step only once OPatch does not keep track of the make operations it did not perform You need to make sure to execute OPatch without this option at the end for compilation Specifies that OPatch does not need to update the files in the system It only updates the inventory It also does not execute the pre and post scripts Specifies the Oracle home directory to use instead of the default This takes precedence over the environment variable ORACLE HOME Marks the end of the init options You use this option with the init option If you do not use this option everything after init until the end of the command is passed into init Marks the end of the post option You use this option with the post option If you do not use this option everything after post until the end of the command is passed into post Marks the end of the pre options You use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location Specifies the parameters to be passed to the post script This script is executed after the patch is applied You need to enclo
48. RAC software on Windows system computers 1 Skip this step if you have a shared Oracle Database home If you do not have a shared Oracle Database home zip the Oracle Database home with Oracle RAC on the existing node and copy it to the new node Unzip the Oracle Database with Oracle RAC home on the new node in the same directory in which the Oracle Database home with Oracle RAC resided on the existing node For example assume that the location of the destination Oracle RAC home on the new node is SORACLE HOMES Note For more information on zipping and unzipping see Source Preparation Phase and Cloning Phase 2 Onthe new node go to the SORACLE_HOME clone bin directory and run the following command where Oracle Home is the Oracle Database home Oracle Home Name is the name of the Oracle Database home existing node is the name of the existing node and new node is the name of the new node perl clone pl ORACLE HOME Oracle Home ORACLE HOME NAME Oracle Home Name O CLUSTER NODES existing node new node OLOCAL NODE new node O noConfig If you have a shared Oracle Database home with Oracle RAC append the O cfs option to the command example in this step and provide a complete path location for the cluster file system Repeat this step for all nodes 3 On the new node run NETCA to add a listener 6 10 Oracle Universal Installer and OPatch User s Guide Adding Nodes Using Cloning in Oracle Real Applicatio
49. RESPONSEFILE VERSION 2 2 1 0 0 E a ee ee pe ee A e LU Name UNIX GROUP NAME Datatype String Description Unix group to be set for the inventory directory Valid only in Unix platforms Example UNIX GROUP NAME install C E UNIX GROUP NAME Value Unspecified gt Name FROM LOCATION Datatype String Description Complete path of the products jar Sample Files D 1 Sample Response File Example FROM LOCATION stage products jar Name FROM LOCATION CD LABEL Datatype String Description This variable should only be used in multi CD installations It includes the label of the Compact Disk where the file products jar exists The label can be found in the file disk label in the same directory as products jar Example FROM LOCATION CD LABEL CD Label Name NEXT SESSION RESPONSE Datatype String Description Optionally specifies the full path of next session s response file If only a file name is specified the response file is retrieved from lt TEMP gt oraInstall directory This variable is only active if NEXT SESSION is set to true Example NEXT SESSION RESPONSE nextinstall rsp Ar ds economie atcha cA Le ean aa p dl ace at NEXT SESSION RESPONSE Value Unspecified A O A eb ce Ro ee eS eS ee A A Se oa ete Name ORACLE HOME Datatype String Description Complete Location of the Oracle Home
50. SYSTEMROOT Nsystem32MdriversNorafenceservice sys Converting Single instance Nodes to Real Application Clusters You can convert single instance nodes to Real Application Clusters using Oracle Universal Installer For details on converting single instance nodes to Real Application Clusters see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 for your platform Troubleshooting Real Application Clusters Oracle Clusterware Installation The following flowchart explains how you can solve problems associated with the Real Application Clusters or Oracle Clusterware installation Figure 5 1 Troubleshooting Real Application Clusters Oracle Clusterware Installation The Central Inventory is not updated correctly On the node run attachHome as follows Does the Oracle Home OH oui bin lt runInstaller or setup exe gt atrachHome inventory xml and ORACLE HOME oracle home location gt NO oraclehomeproperties xml ORACLE HOME NAME oracle home name gt show up while doing CLUSTER NODES comma separated nodelist gt opatch sinventory detail LOCAL NODE local node noClusterEnabled YES The Oracle Home inventory on the node needs to be recovered by copying the entire OH inventory directory from another node to the faulty node If the OH inventory directory is corrupt on all the nodes NO the user would have to reinstall the oracle home on another machine at the same location an
51. Usage Command line variables are specified using name value for example session compName compName version variableName valueOfVariable Session Installer variables are specified using session varName value Ex 1 session ORACLE HOME NAME OraHome Ex 2 ORACLE HOME NAME OraHome The lookup order is session varName then just varName The session prefix is used to avoid ambiguity Component variables are specified using compInternalName Version varName Ex 1 oracle compl 1 0 1 varName VarValue Ex 2 oracle compl varName VarValue Ex 2 oracle compl varName VarValue The lookup order is compInternalName Version varName then compInternalName varName then just varName Using Oracle Universal Installer Exit Codes If you are starting and stopping Oracle Universal Installer programmatically for example by invoking Oracle Universal Installer using a response file you may need to consider the exit codes Oracle Universal Installer generates and perform a particular action depending on the code Oracle Universal Installer returns Oracle Universal Installer returns one of the following exit codes Code Description 0 All installations were successful 1 All installations were successful but some optional configuration tools failed 2 Local installations were successful but some remote operations failed 1 At least one installation failed Note that This feature does not wo
52. ago What do I do This may occur because the Oracle home is present in the Central Inventory Oracle Universal Installer allows you to remove the Oracle home from the Central Inventory in cases where the Oracle home is uninstalled To remove the Oracle home you need to execute runInstaller with the detachHome flag You can also completely remove the Central Inventory to remove traces of log files For more information see the section Detaching Oracle Homes from the Central Inventory on page 2 8 When I apply a patchset or an interim patch the patch is not propagated to some of my Real Application Clusters nodes What do I do In a Real Application Clusters environment the inventory contains a list of nodes associated with an Oracle home It is important that during the application of a patchset or an interim patch the inventory is correctly populated with the list of nodes If the inventory is not correctly populated with values the patch is propagated only to some of the nodes in the cluster Oracle Universal Installer allows you to update inventory xml with the nodes available in the cluster using the updateNodeList flag in Oracle Universal Installer For more information see the section Updating the Nodes of a Cluster on page 2 12 What if I just want to update the inventory without reapplying a one off patch The OPatch addpat ch p1 tool enables you to update the inventory with a given one off patch without actually reappl
53. appropriate command on the local node of the cluster as follows opatch apply local node node name remote nodes comma separated node names opatch rollback 1ocal node node name remote nodes comma separated node names Resolving OPatch Application Errors This section provides solutions to the following errors that may occur during patch application Nota valid patch area Opatch cannot find system commands like fuser make Unable to remove a partially installed interim patch Patching Oracle Software with OPatch 7 45 Problem Resolution Not a valid patch area Cause The directory that the OPatch utility is using to do the patch does not match the template for what it is checking This can also occur when you run the utility from an invalid shiphome directory Action When starting the OPatch utility the directory needs the following etc directory that has the metadata files a files directory that has the payload files a etc config inventory file and the actions file under the same directory If you did not start the OPatch utility from the patch id directory you can use the following command opatch apply lt Patch_Shiphome gt OPatch cannot find system commands like fuser make Cause The OPatch utility uses fuser on UNIX systems to check for active Oracle instances On certain hp ux systems only a super user can run fuser Action Perform these steps to resolve this probl
54. browser both to enable Oracle Enterprise Manager and to view online documentation For Oracle Database 11g requirements Oracle Clusterware provides the same functionality as third party vendor clusterware Using Oracle Clusterware also reduces installation and support complications However you may require third party vendor clusterware Installing Cluster Environments 5 3 Cluster Setup and Pre installation Configuration Tasks for Real Application Clusters if you use a non ethernet interconnect or if you have deployed clusterware dependent applications on the same cluster where you deploy Real Application Clusters Cluster Setup and Pre installation Configuration Tasks for Real Application Clusters Before installing Real Application Clusters perform the following procedures 1 Ensure that you have a certified combination of operating system and Oracle software version by referring to the OracleMetaLink certification information which is located at the following Web site http metalink oracle com Click Certify amp Availability and select 1 View Certifications by Product Note The layout of the OracleMetaLink site and the site s certification policies are subject to change 2 Configure a high speed interconnect that uses a private network Some platforms support automatic failover to an additional interconnect Determine the storage option for your system and configure the shared disk Ensure that the dire
55. called an upgrade A group of patches form a patchset For example you may want to convert your Oracle 11gR1 11 1 Database from version 11 1 1 to version 11 1 2 which is called applying a patchset Adding Nodes You can install an Oracle home on multiple nodes in a cluster You can extend the cluster for a particular Oracle home using the addNode flag of Oracle Universal Installer You can add more than one node to the Oracle home The Oracle Universal Installer with the addNode flag is always run on the local node and not on the node s to be added You can add nodes to an Oracle Clusterware node or a Real Application Clusters node depending upon whether the node addition is being performed at the Oracle Clusterware layer or the Real Application Clusters database layer You can use OH oui bin addNode sh to add nodes For more information on adding nodes see Installing Cluster Environments on page 5 1 Inventory Operations Oracle Universal Installer supports the following inventory operations Attaching Oracle Homes Oracle Universal Installer uses the attachHome flag to attach an Oracle home to the inventory to set up the Central Inventory or to register an existing Oracle home with the Central Inventory You can use attachHome sh bat from an Oracle home as well as from the shiphome For more information see Creating the Central Inventory on page 2 7 Detaching Oracle Homes Oracle Universal Installer uses the d
56. conjunction with any product specific installation guides available with your Oracle product Documentation Accessibility Our goal is to make Oracle products services and supporting documentation accessible with good usability to the disabled community To that end our documentation includes features that make information available to users of assistive technology This documentation is available in HTML format and contains markup to facilitate access by the disabled community Accessibility standards will continue to evolve over time and Oracle is actively engaged with other market leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers For more information visit the Oracle Accessibility Program Web site at http www oracle com accessibility Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document The conventions for writing code require that closing braces should appear on an otherwise empty line however some screen readers may not always read a line of text that consists solely of a bracket or brace Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites
57. dialog shown during the setup of next session This flag is used in chain installs Understanding Oracle Universal Installer Commands C 7 Command line Variables Available in Oracle Universal Installer C 8 Oracle Universal Installer and OPatch User s Guide D Sample Files This appendix provides the following sample files Sample Response File Sample ORAPARAM INI File Sample Components File Sample Response File Response files are of type rsp and are used by Oracle Universal Installer to run silent installations THHHHHHHHHBHHBHHHBHHBHHHBHHHBHHHBHHBHHHBHHHBHHHHHHHBHHHHBHHHBHHHHHHBHRE Copyright c Oracle Corporation 2007 All rights reserved HH HH Specify values for the variables listed below to customize HH your installation HH at HH Each variable is associated with a comment The comment HA identifies the variable type HH TH HH Please specify the values in the following format HH at HH HH Type Example HH HH String Sample Value HA HH Boolean True or False 4 Number 1000 TH iH StringList String value 1 String Value 2 HH at HH The values that are given as lt Value Required gt need to be HH specified for a silent installation to be successful HH HH HH HH HH This response file is generated by Oracle Software HH Packager iH HEHEHE HEHHE HEHHE HEHEHE HEE EHE HERE HE HEHEHE HE EHE HEERE HEHEHEHE EHEHE HERE PE HE EHE HEETE HEERE HE EEH HEE HEHEHE EE EH
58. environment The changes made by applying one off patches on the source Oracle home are also present after the clone operation The source and the destination path host to be cloned need not be the same During cloning OUI replays the actions that were run to install the home Cloning is similar to installation except that OUI runs the actions in a special mode referred to as clone mode Some situations in which cloning is useful are Creating an installation that is a copy of a production test or development installation Cloning enables you to create a new installation with all patches applied to it in a single step This contrasts with going through the installation process by performing separate steps to install configure and patch the installation Rapidly deploying an instance and the applications that it hosts Preparing an Oracle home and deploying it to many hosts The cloned installation behaves the same as the source installation For example the cloned Oracle home can be removed using OUI or patched using OPatch You can also use the cloned Oracle home as the source for another cloning operation You can create a cloned copy of a test development or production installation by using the command line cloning scripts The default cloning procedure is adequate for most usage cases However you can also customize various aspects of cloning for example to specify custom port assignments or to preserve custom settings
59. existing Oracle home with the Central Inventory when it is lost or corrupted If the Central Inventory does not already exist Oracle Universal Installer creates the Central Inventory in the location specified by the oraInst loc file You can set up the Central Inventory by using the attachHome flag of Oracle Universal Installer The syntax is as follows runInstaller silent attachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt CLUSTER NODES nodel node2 LOCAL NODE node name gt Using the Session Variables You can use the following session variables m ORACLE HOME ORACLE HOME NAME m CLUSTER_NODES REMOTE NODES LOCAL NODE In a cluster installation Ifyou do not pass the CLUSTER_NODES session variable Oracle Universal Installer takes it from the SORACLE HOME inventory ContentsXML oraclehomeproperties xml file Ifyou do not pass the LOCAL NODE session variable Oracle Universal Installer takes it from the SORACLE HOME inventory ContentsXML oraclehomeproperties xml file If it does not find an entry there it takes it from the Oracle Clusterware stack If it is not able to find it in the stack the first node of the CLUSTER NODES is taken as the LOCAL NODE You can pass the REMOTE NODES variable if you want to specify the list of remote nodes If you want to set up the Central Inventory in the local node you need to pass the local flag a
60. for OUI based homes 7 20 online patching 7 32 overview 7 1 prerequisite checks 7 3 problem resolution 7 38 Query command for OUI based homes 7 16 for standalone OPatch 7 26 Real Application Clusters patching all node patching 7 33 minimum downtime patching 7 35 rolling patching 7 34 requirements 7 2 Rollback command for OUI based homes 7 17 for standalone OPatch 7 27 standalone patching 7 22 inventory operations use cases 7 28 patching operations use cases 7 29 requirements 7 23 schema patching options 7 32 standalone SOL execution 7 32 unsupported services 7 22 utility for standalone homes 7 23 utility operations use cases 7 31 subset conflicts 7 36 superset conflicts 7 35 troubleshooting logging and tracing 7 39 recovering from failed patching 7 39 resolving application errors 7 45 types of conflicts 7 35 utility for OUI based Oracle homes 7 8 Version command for OUI based homes 7 22 for standalone OPatch 7 28 Index 4 OpenSSH 5 6 Optimal Flexible Architecture characteristics of OFA 2 13 directory structure 2 13 Optimal Flexible Architecture OFA ORACLE BASE directory 2 13 ORACLE HOME directory 2 14 optional response file parameters 3 12 OPTIONAL CONFIG TOOLS parameter 3 9 Oracle base directory 5 11 5 12 Oracle Cluster Registry location option 5 15 Oracle Clusterware home directory 5 12 setup 6 10 Oracle Diagnostic Logging ODL guidelines 7 39 Oracle home directory 5 12 Or
61. formCluster remotecp Path remoteshell Path Records a response file The information is recorded in the destination file path specified Removes the home directory after de installation of all the components This is used with the deinstall flag Removes all interim patches from the home Used for silent mode operations The input can be a response file or a list of command line variable value pairs You can use the responsefile flag along with this flag Updates the node list for this home in the Oracle Universal Installer inventory You can pass the ORACLE HOME LOCAL NODE and CLUSTER NODES session variable when using this flag Used on a Windows platform The command console will wait for Oracle Universal Installer to exit if you specify this flag Specifies to Oracle Universal Installer not to show background images Indicates that no cluster nodes are specified Suppresses the display of messages to the console Disables the warning message before removal of the home directory This is used with the deinstall flag Used on a Windows platform Specifies not to wait for the user to press Enter on the console after the task installation etc is complete Installs the Oracle Clusterware in order to form the cluster This flag can only be passed on UNIX platforms This is used only for cluster installs This flag specifies the path to the remote copy program on the local cluster node For example the
62. from the URL specified in the Product Registration Page Specifies whether to restart the system or not Set to true to allow automatic restart of the system If set to false the installer exits without restarting No exit confirmation dialog is shown Specifies whether to restart the remote system or not Set to true to allow automatic restarting of the remote system If set to false the installer does not restart remote systems No exit confirmation dialog is shown This session variable holds the current Oracle Universal Installer execution mode that is Install for an install and or de install session or Clone for a cloning home fix up session Specifies the log file location This variable specifies the directory that contains the log files generated during installation This directory is located within the Oracle home C 6 Oracle Universal Installer and OPatch User s Guide Command line Variables Available in Oracle Universal Installer Table C 2 Cont Command Line Variables in Oracle Universal Installer Command Line Variable Description IGNORE PREREQ ORACLE HOSTNAME PREREO CONFIG LOCATION PREREQ LOG LOCATION PREREQ ENTRY POINT ROOTSH STATUS SHOW CUSTOM ROOTSH MESSAGE ROOTSH_ LOCATION USE_PREREQ_ CHECKER USE_OLD_INSTALL_ PREREQS SHOW_NEXT_ SESSION_PROGRESS NEXT_SESSION_ PROGRESS_TITLE NEXT_SESSION_ PROGRESS_TEXT Specifies whether to skip the prerequisit
63. init Marks the end of the post options Use this option with the post option If you do not use this option everything after post until the end of the command is passed into post Marks the end of the pre options Use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location Specifies the valid patch directory area Rollback uses the command types found in the patch directory to identify which commands are used for the current operating system Specifies the parameters to be passed inside the post script This script executes after the patch is removed You must enclose the value of this option in double quotes Specifies the parameters to be passed inside the pre script This script executes before the patch is removed You must enclose the value of this option in double quotes Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies Specifies the connection string credentials of the portal schema Specifies the schema of the portal repository Specifies the password of the portal schema Specifies to OPatch the list of remote nodes to be used for rollback of the patch The node names must be
64. install UNIX GROUP NAME Value Unspecified Response File Parameters The following are parameters for Oracle Universal Installer All products installed using Oracle Universal Installer have these parameters in addition to product specific variables Customizing and Creating Response Files 3 5 Response File Format INCLUDE This parameter specifies the list of response files to be included in this response file If you want to include other response files in your main response file you must use this parameter Note that the values in the main response file have priority over the included response files INCLUDE filel rsp file2 rsp filen rsp You should specify the absolute path in the INCLUDE statement for each response file to be included If you wish to specify a relative path note that the location is relative to the current working directory the location of the oraparam ini file RESPONSEFILE_VERSION This parameter specifies the version number of the response file RESPONSEFILE VERSION lt version_number gt FROM_LOCATION The location of the source of the products to be installed The default generated value for this parameter is a path relative to the location of the runInstaller file oraparam ini Relative paths are necessary for shared response files used by multiple users over a network Since people may be mapping to different drives absolute paths will not work for shared response fil
65. installing After you view an online help topic choose Navigator from the Tools menu to display the navigator pane From the navigator pane you can browse the table of contents select other topics or search for a particular word or phrase in the online help 4 2 Oracle Universal Installer and OPatch User s Guide Installing Oracle Products Note Only generic help topics are available in the navigator or table of contents You can only access custom help topics by clicking the Help button on the dialogs or windows they describe About the ORAPARAM INI File The oraparam ini file is the initialization file for Oracle Universal Installer This file includes information that defines the behavior of certain Oracle Universal Installer features Each product installation possesses a unique oraparam ini file Generally you should not have to edit the contents of this file but in certain situations understanding the contents of this file can help you troubleshoot problems and understand certain aspects of the Oracle Universal Installer product For example for most installations Oracle Universal Installer provides a default value on the File Locations page that points to the location of the product s installation kit or stage This default value is stored in the oraparam ini file The oraparam ini file also identifies the location of the Java Runtime Environment JRE required for the installation In the staging area i
66. inventory of the local node It does not propagate the patch or inventory update to other nodes You can use this option on Oracle Real Application Clusters environments and non clustered environments If an entire cluster is shut down before patching you can use this option for non rolling patches Tells OPatch the local node for this cluster You can use this option on Oracle Real Application Clusters environments Specifies the order of nodes that OPatch should patch This option only applies to Oracle Real Application Clusters environments You cannot use it with the local option with a rolling patch Specifies to error out if the current patch s bugs to fix is a superset or same set of an installed patch s bugs fixed in the Oracle home directory Bypasses the inventory for reading and updates You cannot use this option with the local option This option places the installation into an unsupported state Patching Oracle Software with OPatch 7 13 OPatch Utility for OUl based Oracle Homes Table 7 3 Cont Napply Options for OUI Patches Option Description no relink no sysmod oh opatch post end opatch pre end Patch Location phBaseFile post pre property_file remote_nodes report retry silent skip_duplicate skip_subset This option does not perform any make operations You can use it during multiple patch applications and to perform the linking step only once OPat
67. location Unmounting a CD On UNIX if you have trouble installing a product from multiple CD ROMs try using the following procedure to unmount the first CD ROM and mount the second CD ROM If you still have problems refer to the documentation links at the end of this topic In most cases the following procedure helps with any problems you experience while switching to a second CD ROM while installing Oracle software If you inadvertently run the installer while the current working directory is in the CD ROM follow these steps to mount the next CD ROM 1 Change to the root directory of your system and log in as the root user by using the following commands cd su root Installing Products 4 7 Installing Oracle Products 2 Unmount and remove the CD ROM from the drive with the following command umount cdrom mount point directory 3 Insert and mount the next CD ROM into the drive by using the following command mount options device name cdrom mount point directory 4 Enter the correct mount point in the Installation dialog box 5 Click OK to continue If after attempting this procedure you are still having problems see the section on installing from multiple CD ROMs in the Oracle Database Installation Guide which is available from the Oracle Technology Network http otn oracle com documentation Installing from a staged HTTP location With Oracle Universal Installer you can install products from
68. node the private interconnect protocol address of the new node and the virtual interconnect protocol address of the new node respectively perl clone pl ORACLE HOME CRS HOME ORACLE HOME NAME CRS HOME NAME O sl tableList new node new node priv new node vip O noConfig OPERFORM PARTITION TASKS FALSE If you have a shared Oracle Clusterware home append the O c s option to the command example in this step and provide a complete path location for the cluster file system Note Only provide a value for the s1_tableList variable The Perl c1one p1 script takes all other variable settings from the zipped Oracle Clusterware home This is only true however if the source of the zipped home was from an existing node of the cluster that you are extending If you use any other Oracle RAC environment as your cloning source that is if you clone from a node in a cluster other than the one that you are extending you must provide values for all of the arguments This includes values for the Oracle Cluster Registry OCR and voting disk location arguments You must do this because the value for s1_ tableList is used as shown in the command example in this step You must also specify the OCR and voting disk locations using the sl OHPartitionsAndSpace valueFromDlg variable as well as provide values for the PERFORM PARTITION TASKS argument Only specify values for the new node for the 1 tableList options 3 Run the following c
69. occur if OPatch failed to update the inventory Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly in each node in the cluster Navigate to the SORACLE HOME patch storage patch id timestamp directory in each node in the cluster and execute the restore command as follows For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat Patching Oracle Software with OPatch 7 43 Problem Resolution 3 On UNIX source SORACLE HOME patch storage patch id timestamp make txt file if available in each node in the cluster as follows bin sh make txt 4 Roll back the patch in all the nodes in the cluster using the local flag SORACLE HOME OPatch opatch rollback local id Patch ID Note Ensure that all the nodes use the same OPatch version When I roll back a patch on a Real Application Clusters setup and execute opatch Isinventory on the local node it returns nothing Cause You might have lost all the patches applied earlier Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly in each node in the cluster 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command in each node in the cluster For UNIX SORACLE HOME patch storage patch id
70. of the default location under the Oracle home directory oh Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE_HOME environment variable patch Specifies the patches installed in the Oracle home property_file Indicates the user defined property file that OPatch should use The path to the property should be absolute This property file takes precedence over the property file that OPatch supplies Query Command for Standalone OPatch This command queries a specific patch for specific details It provides information about the patch and the system being patched Syntax Use the following syntax for this command opatch query all jre LOC oh lt LOC gt get component get os get date is rolling patch is online patch get base bug is portal patch has sql Patch Location Options Table 7 11 lists the options available for the Query command Table 7 11 Query Options Option Description all Retrieves all information about a patch This is equivalent to setting all available options get base bug Retrieves bugs fixed by the patch get component Retrieves components the patch affects get date Retrieves the patch creation date and time has sql Indicates true if the patch has SOL related actions Otherwise the option is false For information on SOL and PL SOL patching see Schema Patching is online patch I
71. parent directories of the Oracle Clusterware home directory after installing the software to grant write access only to the root user the Oracle Clusterware home directory must not be a subdirectory of the Oracle base directory Oracle Home Directory The Oracle home directory is the directory where you choose to install the software for a particular Oracle product You must install different Oracle products or different releases of the same Oracle product in separate Oracle home directories When you run Oracle Universal Installer it prompts you to specify the path to this directory as well as a name that identifies it The directory that you specify must be a subdirectory of the Oracle base directory Oracle recommends that you specify a path similar to the following for the Oracle home directory oracle base product 11 1 0 db 1 Oracle Universal Installer creates the directory path that you specify under the Oracle base directory It also sets the correct owner group and permissions on it You do not need to create this directory Identifying or Creating an Oracle Base Directory Before starting the installation you must either identify an existing Oracle base directory or if required create one For more information on identifying or creating an Oracle Base Directory see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Creating the Clusterware Home Directory Oracle Universal Installer create
72. path for scp is usr bin scp This flag can only be passed on UNIX platforms This is used only for cluster installs This specifies the path to the remote shell program on the local cluster node For example the path for ssh is usr bin ssh Command line Variables Available in Oracle Universal Installer Table C 2 lists the command line variables available in Oracle Universal Installer Table C 2 Command Line Variables in Oracle Universal Installer Command Line Variable INVENTORY LOCATION Description Specifies the inventory location Understanding Oracle Universal Installer Commands C 3 Command line Variables Available in Oracle Universal Installer Table C 2 Cont Command Line Variables in Oracle Universal Installer Command Line Variable Description ORACLE HOME ORACLE HOME NAME ORACLE HOME KEY ORACLE HOME FOLDER ORACLE HOME SERVICE ANONYMOUS LOGIN LOGIN NAME PASSWORD LOGIN CATEGORY UNIX GROUP NAME FROM LOCATION FROM LOCATION CD LABEL COMPONENT LANGUAGES SELECTED LANGUAGES SELECTED PLATFORMS TOPLEVEL COMPONENT ToplevelComp INSTALL TYPE SHOW SPLASH SCREEN SHOW WELCOME PAGE SHOW ROOTSH CONFIRMATION SHOW EXIT CONFIRMATION SHOW CUSTOM TREE PAGE Specifies the ORACLE HOME location Specifies the ORACLE HOME name in the target machine Specifies the ORACLE HOME key name This is used only on Windows platform
73. products xml Special Instructions for UNIX Users The following sections describe special instructions that apply when you are installing certain products on a UNIX system 4 8 Oracle Universal Installer and OPatch User s Guide Installing Oracle Products Failed to Connect to Server Error If you receive an Xlib error or a Failed to connect to Server error when you are running Oracle Universal Installer on the Solaris operating system do the following 1 Define the following environment variable on the host computer where you are running Oracle Universal Installer setenv DISPLAY machine name gt 0 0 2 Replace machine name gt with the name of the computer that will display Oracle Universal Installer 3 Onthe computer that will display Oracle Universal Installer enter the following command which allows other computers to display information on the computer s monitor xhost 4 Rerunthe runInstaller script after you have set the DISPLAY environment variable Note You can run Oracle Universal Installer without specifying the DISPLAY variable by running in silent mode using a response file Providing a UNIX Installer Location with Root Privileges You must have root privileges to perform various installation operations on the UNIX platform For example you must have root privileges to be able to create the Oracle Universal Installer inventory If you are installing Oracle Universal Installer
74. sections ORACLE BASE Directory ORACLE BASE specifies the BASE of the Oracle directory structure for OFA compliant databases A typical ORACLE BASE directory structure is described in Table 2 5 When installing an OFA compliant database using Oracle Universal Installer ORACLE BASE is set to pm app oracle by default Managing Oracle Homes 2 13 Home Selector Available on Win32 Platforms Table 2 5 Sample ORACLE BASE Directory Structure and Content Directory Content admin doc local product Administrative files online documentation Sub tree for local Oracle software Oracle software ORACLE HOME Directory Table 2 6 shows an example of the Oracle home directory structure and content for an Oracle Server Installation If you install an OFA compliant Oracle Server the Oracle home directory is mount _ point app oracle product release number Under UNIX the Oracle home directory might contain the following subdirectories as well as a subdirectory for each Oracle product selected Note The directory and content information in this table are only samples The directories that appear in your own Oracle home depend on whether the corresponding products are installed and the version of the Oracle Database you are running Table 2 6 Directory assistants bin ctx dbs install lib jlib md mlx network nlsrtl ocommon odg opsm oracore ord otrace plsql precomp Sample Orac
75. the end of the command is passed into init Marks the end of the post option You use this option with the post option If you do not use this option everything after post until the end of the command is passed into post Marks the end of the pre options You use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location Specifies the parameters to be passed to the post script This script is executed after the patch is applied You need to enclose the values for this option in double quotes Specifies the parameters to be passed to the pre script This script is executed before the patch is applied You need to enclose the values for this option in double quotes Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies Specifies the connection string credentials of the portal schema Specifies the password of the portal schema Specifies the schema of the portal repository Tells OPatch the list of remote nodes You can use this option on Oracle Real Application Clusters environments The node names must be separated with commas but without spaces Prints the action to the screen without executin
76. the first set and apply a patch to the second set You now bring up the second set All the nodes in the cluster are now patched This method leads to less downtime for the Real Application Clusters when both sets are brought down This mode is executed by using minimize downtime command line option You can also activate this option from the response file Figure 7 3 shows a basic example of Minimum Downtime Patching Figure 7 3 Minimum Downtime Patching MINIMUM DOWNTIME PATCHING Systems A B and C are nodes in this cluster It is divided into two sets Set 1 contains systems A and B and Set 2 contains system C When you perform Minimum Downtime Patching in this cluster you shut down Set 1 and apply a patch to it You now shut down Set 2 Then you bring up Set 1 and apply a patch to Set 2 After you apply the patch you bring up Set 2 again Now both Sets 1 and 2 are patched About Patch Conflicts All patches may not be compatible with one another For example if you apply a patch all the bugs the patch fixes could reappear after you apply another patch This is called a conflict situation OPatch detects such situations and raises an error when it detects a conflict Types of Conflicts OPatch can detect the following types of conflicts Superset If all the bugs fixed by a patch in the system are also fixed by the patch to be applied this patch the patch to be applied is considered a superset of the patch already applied
77. to program The default for remoteShell is usr local bin ssh The default for remoteCopy is usr local bin scp If these are not present Oracle Universal Installer defaults to rsh and rcp respectively Patchsets and Upgrades Oracle Universal Installer enables you to upgrade a product from one version to another version An upgrade is a major product enhancement that often requires installation of the upgraded software For example if you convert your Oracle 10g Database to Oracle 112R1 Database then it is called an upgrade A group of patches form a patchset For example if you convert your Oracle 11gR1 from version 11 1 1 to version 11 1 2 then it is called applying a patchset Post installation Tasks Verification After completing a Real Application Clusters installation it is advisable that you perform the following tasks After your Oracle product with Real Application Clusters installation is complete go to SORACLE HOME Opatch on each node and execute the following command SORACLE HOME OPatch opatch lsinventory detail This command lists the components installed inside the Oracle home and also lists the local and remote nodes for the home Verify this information You may also want to look at installation logs inventory xml and oraclehomeproperties xml See Troubleshooting Real Application Clusters Oracle Clusterware Installation on page 5 27 in case the check fails Back Up Disk after Installation After y
78. true however if the source of the zipped home was from an existing node of the cluster that you are extending If you use any other Oracle RAC environment as your cloning source that is if you clone from a node in a cluster other than the one that you are extending you must provide values for all of the arguments This includes values for the Oracle Cluster Registry and voting disk location arguments You must do this because the value for 1 tableList is used as shown in the command example in this step Also note that you should only specify values for the new node for the sl tableList options 3 Onthe new node go to the directory that contains the central Oracle inventory Run the orainstRoot sh script to populate the etc oraInst 1loc file with information about the Central Inventory location 4 Runthe following command on the existing node where new node is the name of the new node new node privis the private interconnect protocol address for the new node and new node vipis the virtual interconnect protocol address for the new node SORACLE HOME oui bin addNode sh silent CLUSTER NEW NODES new node CLUSTER NEW PRIVATE NODE NAMES new node priv CLUSTER NEW VIRTUAL HOSTNAMES new_node vip noCopy Note Because the clone pl script has already been run on the new node this step only updates the inventories on the nodes and instantiates scripts on the local node 5 On the existing node ru
79. value2 3 command line variable valuel1 value2 Options Available in Oracle Universal Installer Table C 1 lists the various options available in Oracle Universal Installer Table C 1 Options in Oracle Universal Installer Option Description clusterware oracle crs lt crs Version of the Oracle Clusterware installed version crsLocation Path Specifies the path to the Oracle Clusterware home location This flag is used only for cluster installations Specifying this flag overrides the CRS information obtained from the Central Inventory invPtrLoc full path of Points to a different inventory location The orainst loc file oraInst loc contains the following entries inventory loc location of central inventory gt inst_group lt gt This flag can only be passed on UNIX platforms Understanding Oracle Universal Installer Commands C 1 Options Available in Oracle Universal Installer Table C 1 Cont Options in Oracle Universal Installer Option Description jreLoc location logLevel level paramFile location of file responseFile Path sourceLoc location of products xml gt addLangs addNode attachHome cfs clone debug deinstall detachHome enableRollingUpgrade executeSysPrereqs force help ignorePatchConflicts ignoreSysPrereqs Path where the Java Runtime Environment is installed You need to mention this path t
80. want to download On the Patch Set page click View README and read the page that appears The README page contains information about the patch set and how to apply the patches to your installation Return to the Patch Set page click Download and save the file on your system Use the unzip utility provided with Oracle software to uncompress the Oracle patches that you downloaded from OracleMetaLink The unzip utility is located in the SORACLE HOME bin directory Note By default the patches would only be applied on the nodes on which the Oracle software installation was done You can change the node list by using the enableRollingUpgrade option Configure Oracle Products Many Oracle products and options must be configured before you use them for the first time Before using individual Oracle products or options refer to the manual in the product documentation library that is available on the documentation CD ROM or on the Oracle Technology Network Web site Deinstalling Real Application Clusters Software If you need to deinstall Real Application Clusters software you must run the Oracle Universal Installer to deinstall the software on the same node from which you performed the installation You must first deinstall the Oracle product before deinstalling the Oracle Clusterware software Perform the following procedures as described in the following sections to deinstall Oracle product and Oracle Clusterware software
81. which are homes installed on multiple cluster nodes have an attribute called Cluster Nodes which lists all the nodes associated with that home Availability Checking When the user clicks Next on the Specify Hardware Installation Mode page or Selected Nodes page Oracle Universal Installer performs the following availability checks on the nodes Network reachability Tests whether the remote cluster nodes are up and running Network configuration Tests whether the remote cluster nodes are properly network configured Inventory setup Tests whether the inventory is set up on the remote nodes If not set up on UNIX Oracle Universal Installer prompts you to run root scripts on the remote nodes to set up the inventory On Windows Oracle Universal Installer sets up the inventory location in the Windows registry Inventory permission Tests whether you can write to the Central Inventory location Oracle home permission Tests whether you can write to the Oracle home If all selected nodes are available the installation process continues to the next step If a node or nodes is not available the page redisplays with a Status column indicating the results of the check You must fix the problem or choose another set of nodes in order to proceed 5 20 Oracle Universal Installer and OPatch User s Guide Command Line Options for Cluster Installations UNIX Only If any of the remote nodes is unreachable check
82. 1 offers the following features An XML based centralized inventory Introduction to Oracle Universal Installer 1 1 Utilities Utilities The XML format allows third party Java applications to query the inventory for information about installed software For backward compatibility the Central Inventory continues to maintain the binary versions as well Cloning of existing Oracle homes Allows you to copy an existing Oracle home to another location and fix it up by updating the installation configuration to be specific to the new environment Cloning makes it easy to propagate a standard setup without having to install and configure installation after installation Better support for cluster environments Oracle Universal Installer now replicates its inventory to all nodes that participate in a cluster based installation You can invoke Oracle Universal Installer from any node on the cluster that is part of the installation You can then upgrade remove or patch existing software from any node True silent capability When running Oracle Universal Installer in silent mode on a character mode console you no longer need to specify an X server or set the DISPLAY environment variable on UNIX No GUI classes are instantiated making the silent mode truly silent Ability to record your Oracle Universal Installer session to a response file This feature makes it easy to duplicate the results of a successful installation on mul
83. Clusters setup the patching in one node is fine but when I execute opatch Isinventory on the other nodes the patch is not listed Cause This may occur because of a failed system or inventory update Action Perform the following steps 1 CopytheORACLE HOME inventory directory from the node that is fine to the other nodes 2 After copying the ORACLE HOME inventory directory make sure that the ORACLE HOME inventory ContentsXML comps xml file has the latest timestamp Note On Unix use touch to change the timestamp 3 Update the nodes of the cluster For more information on updating the nodes of the cluster see Updating the Nodes of a Cluster on page 2 12 4 Ensure that all the prerequisite checks pass that are listed in the section Prerequisite Checks for OPatch on page 7 3 When I apply or roll back a patch on a Real Application Clusters setup I am not able to apply or roll back the patch on all nodes Cause This may occur if the nodes are not properly updated Action Perform any one or more of the following Ensure that all the nodes in the cluster are up to date If they are not update the nodes of the cluster For more information on updating the nodes of the cluster see Updating the Nodes of a Cluster on page 2 12 Execute the appropriate command on all nodes of the cluster as follows opatch apply local patch location opatch rollback local patch location a Execute the
84. E NAMES CLUSTER NEW HOST NAMES CLUSTER NEW NODE NUMBERS CLUSTER NEW VIRTUAL HOSTNAMES ACCEPT LICENSE AGREEMENT REGISTRATION_ KEYWORD RESTART_SYSTEM RESTART_REMOTE_ SYSTEM SESSION_MODE LOG_LOCATION used with the deinstall flag Specifies the de install progress Set to true if de install progress is needed during a de install session This argument is used with the deinstall flag Specifies the list of the homes to be removed during a de install session Each home is represented by its full path This argument is used with the deinstall flag Specifies the cluster node names selected by the user for installation Specifies the new cluster nodes to be used for node addition Specifies the remote nodes Specifies the remote nodes which do not have an installation inventory set up Specifies the local node Specifies the remote nodes on which the current home is already installed Specifies whether the Oracle home is an Oracle Clusterware home or not Specifies the private node names for the new nodes that are used for node addition Specifies the host names for the new cluster nodes Specifies the node numbers of the new cluster nodes Specifies the virtual host names for the new cluster nodes Specifies the license agreement status By setting this variable to true you are accepting the license agreement Specifies the registration keyword value This can be obtained
85. E DESC gt LIST FO DEST VOLUME INVENTORY LOCATIONS SPACE REQ 2000 gt lt DEST VOLUME ORACLE HOMES SPACE REQ 98465 gt DEST VOLUME s TMPDIR LOC SPACE REQ 0 gt DEST VOLUME s TEMP LOC SPACE REQ 0 gt lt FILESIZEINFO gt lt COMP gt D 10 Oracle Universal Installer and OPatch User s Guide A ACCEPT LICENSE AGREEMENT parameter 3 11 adding nodes 1 4 all node patching 7 33 APPLTOP STAGE parameter in ORAPARAM INI 4 5 Apply command for OUI based homes 7 9 for standalone OPatch 7 24 patch conflict behavior 7 38 ARU IDs for platforms 2 6 attaching Oracle homes 1 4 background processes clusterware 5 16 Oracle Clusterware 5 19 BOOTSTRAP parameter in ORAPARAM INI 4 5 BOOTSTRAP SIZE parameter in ORAPARAM INI 4 5 C Cache Fusion 5 3 5 17 Central Inventory 2 4 creating 2 7 detaching homes from the Central Inventory 2 8 inventory file 2 4 logs directory 2 5 recovering from corruption 2 10 removing 2 9 on UNIX platforms 2 9 on Windows platforms 2 9 using session variables 2 7 verifying the operation 2 8 Central Inventory pointer file 2 4 Linux 2 4 Solaris 2 4 Windows 2 4 changing primary Oracle home 2 12 clone pl script variables 6 15 cloning about 6 1 adding nodes in RAC enviromments 6 11 Index adding nodes to RAC environments on UNIX and Linux 6 11 on Windows 6 13 cloning phase 6 3 clusterware 6 6 considerations 4 15
86. FS Cluster File System ensure the following is true for all nodes The registry key HKLM SOFTWARE Oracle osd9i ocr exists The registry key HKLM SOFTWARE Oracle osd9i ocr has a string value C sOcrRoot that points to a release 10 2 OCR CFS location Run CRS_HOME bin ocrconfig downgrade to downgrade the Cluster Registry to a release 10 2 OCR On each node copy CRS_HOME cfs OcfsFindVol exe to SYSTEMROOTS system32 osd9i cfs Run CRS_HOME oui bin setup exe to start Oracle Universal Installer On the Welcome page click Deinstall Products to list all the installed products Select the Oracle Clusterware home name from the displayed products and click Remove to deconfigure and deinstall the product On each node run SSYSTEMROOTS system32 osd9i olm OracleOBJService exe install to reinstall the Oracle 10 2 object service Then start Oracle Object Service On each node run SYSTEMROOT system32 osd9i cfs OcfsFindVol exe i SYSTEMROOTS system32 osd9i cfs OcfsFindVol exe to reinstall the Oracle Cluster Volume service Then start the Oracle Cluster Volume service 5 26 Oracle Universal Installer and OPatch User s Guide Troubleshooting Real Application Clusters Oracle Clusterware Installation 8 Froma 10 2 Real Application Clusters Oracle home on each node run the command ORACLE HOME bin gsdservice exe install Then start the OracleGSDService 9 On each node copy SYSTEMROOT system32 osd9i orafencedrv sys
87. HTTP location Note On Windows when you start the installer from a shared drive you need to map the shared drive and then invoke the installer from the shared drive The following sections discuss these different installation approaches Notes When you invoke runInstaller UNIX or setup exe Windows you should invoke it from the directory where this command is present or you must specify the complete path to runInstaller UNIX or setup exe Windows Installing from a Single CD ROM While installing Oracle products contained on a single CD ROM start Oracle Universal Installer by running the executable file setup exe or runInstaller sh located in install platform Where platform represents Win32 Win64 Solaris Linux and so on For UNIX systems run the script by typing runInstaller at the command line 4 6 Oracle Universal Installer and OPatch User s Guide Installing Oracle Products Note Oracle Universal Installer for win64 functions like Oracle Universal Installer for win32 However the startup directory on the CD is win64 instead of win32 Launching Oracle Universal Installer from the win32 directory launches Oracle Universal Installer in 32 bit mode used for installing 32 bit software Use win64 for installing 64 bit software When you install both 32 bit and 64 bit Oracle Universal Installer on a 64 bit machine two different inventories are created and ma
88. Homes for more information Isinventory Lists what is currently installed on the system See Lsinventory Command for OUI based Oracle Homes for more information query Queries a given patch for specific details See Duery Command for OUI based Oracle Homes for more information rollback Removes an interim patch See Rollback Command for OUI based Oracle Homes for more information nrollback Removes n number of patches hence nrollback See Nrollback Command for OUI based Oracle Homes for more information version Prints the current version of the patch tool See Version Command for OUI based Oracle Homes for more information To view additional information for any command use the following command Path to OPatch opatch command help For Perl use the following command perl opatch pl command help Apply Command for OUI based Oracle Homes This command applies an interim patch to an Oracle home from the current directory The ORACLE HOME environment variable must be set to the Oracle home to be patched Syntax Use the following syntax for this command opatch apply delay value force invPtrLoc Path to oraInst loc jre LOC 1ocal minimize downtime no bug superset no inventory oh ORACLE HOME retry value silent verbose no relink pre parameters for the pre script in escaped double quotes opatch pre end post parameters for the post s
89. KEY to Software ORACLE HOME3 Setting value of ORACLE HOME FOLDER to Oracle Universal Setting value of ORACLE HOME SERVICE to Universal Setting value of ToplevelComp to oracle swd 2 2 1 0 0 Setting value of SELECTED LANGUAGES to en Doing operation for installer access setup Initializing inventory setup WCCE Doing operation in inventory setup WCCE Available Products Page gt 0 0 912 453 615 50 601 173 467 295 87 610 198 918 913 162 2 30 21 10021 111 90 168 888 0H 0 TopLevelComp ToplevelComp oracle swd 2 2 1 0 0 50 0 912 453 615 50 601 173 467 295 87 610 198 918 913 162 2 30 21 10021 111 90 168 888 OH 0 LangsSel SELECTED LANGUAGES en Setting value of ToplevelComp to oracle swd 2 2 1 0 0 gt 0 0 912 453 615 50 601 173 467 295 87 610 198 918 913 162 2 30 21 10021 111 90 168 888 0H 0 Setting value of DepMode to Complete Setting value of TLDepModes to Complete Installation Types Page DepMode DepMode Complete TLDepModes TLDepModes Complete Setting value of DepMode to Complete Setting value of PROD HOME to E Universal oracle swd Setting value of PROD HOME to E Universal oracle swd Setting value of PRE REQUISITE to true Setting value of PROD HOME to E Universal oracle swd Setting value of SHOW COMPONENT LOCATIONS PAGE to true Component Locations Page ShowCompLocs SHOW COMPONENT LOCATIONS PAGE true Entering component oracle swd installa
90. ME Optional HOME DEP NAME oracle options VER 11 1 0 0 0 DEP GRP NAME Optional HOME _ Sample Files D 9 Sample Components File IDX 1 gt IDX 1 gt NAME Optional IDX 1 gt IDX 1 gt IDX 1 gt HOME IDX 1 DEP NAM IDX 1 gt lt DEP NAM NAME Required lt DEP NAM HOME IDX 1 DEP NAM NAME Optional DEP NAM NAME Optional DEP LIST REF LIST REF NAM REF LIST DEP NAME oracle network VER 11 1 0 0 0 DEP GRP NAME Optional HOME _ DEP NAME oracle sysman console db VER 11 1 0 0 0 DEP GRP_ HOME IDX 1 gt DEP NAME oracle rdbms oci VER 11 1 0 0 0 DEP GRP NAME Optional HOME _ DEP NAME oracle precomp VER 11 1 0 0 0 DEP GRP NAME Optional HOME DEP NAME oracle xdk VER 11 1 0 0 0 DEP GRP NAME Optional HOME _ DEP NAME oracle sqlplus isqlplus VER 11 1 0 0 0 DEP GRP NAME Optional gt E oracle odbc VER 11 1 0 0 0 DEP GRP NAME Optional HOME E oracle rdbms install common VER 11 1 0 0 0 DEP _GRP_ HOME IDX 1 gt E oracle swd oui VER 11 1 0 0 0 DEP GRP NAME OptionalDecideNow gt E oracle swd opatch VER 11 1 0 0 0 DEP GRP_ DecideNow HOME IDX 1 gt E oracle dbjava jdbci2 VER 11 1 0 0 0 DEP GRP_ DecideNow HOME IDX 1 gt E oracle server VER 11 1 0 0 0 HOME IDX 1 gt INST TYPE LIST INST TY INST TYPE FILESIZEIN PE NAME EE NAME ID EE DESC ID E
91. NAME NO BROWSE Location of a text file for License information This location is relative to the directory where oraparam ini exists The legal terms file should be a plain text file If you specify the LICENSE LOCATION variable Oracle Universal Installer asks for license acceptance after you click the Next button on the Welcome screen Oracle Universal Installer lets you proceed only after the license is accepted This parameter is ignored if the file is not found The value of this variable displays as the title of the license agreement Oracle Universal Installer only reads this value if the license dialog is displayed that is if the LICENSE LOCATION variable has a valid value Location of the Java Runtime Environment JRE that the Oracle Universal Installer uses Note For a single installation to point to two different JRE versions move the oraparam ini file one level below its original location and then specify the individual platform s JRE location For example if the original location is in the Disk1 install directory move it to the Disk1 install win32 or the Disk1 install solaris directory and then specify the individual platform s JRE location Points to the location of Oracle Universal Installer files used for interactive mode GUI based This parameter is optional if DISTRIBUTION TRUE Oracle Universal Installer computes this value using the OUI VERSION parameter Use this parameter if you want to overr
92. OME is set and the Oracle home has been patched using the standalone OPatch User Input Enter the following command opatch util verify ph patch 10c 123451 Note that patch verification is automatically invoked when OPatch applies a patch to an Oracle home You do not need to rerun verify after applying a patch OPatch Response 1 OPatch detects this is a standalone Oracle home 2 ObPatch examines patch 10c 123451 to make sure it isa valid patch area 3 OPatch examines the files in patch 10c 123451 to make sure the Oracle home was patched with the same bits 4 OPatch reports that both the patch inventory and patch binary are in the Oracle home Schema Patching There are two types of schema patches SQL patch This patches the Oracle database with updated procedures and schema changes PL SOL patch This also patches the Oracle database with updated procedures and schema changes as for the SOL patch However a PL SQL patch also mentions the procedure names in its patch metadata so that these procedures can be backed up for rollback The following sections discuss the following topics Patching Oracle Software with OPatch 7 31 Online Patching a Schema patching options a Standalone SQL execution Schema Patching Options Table 7 21 shows the schema patching options that OPatch supports for Apply and Rollback Table 7 21 Schema Patching Options Option Description runSql Instructs
93. OPatch how many seconds it should wait before attempting to lock the inventory again in case of a previous failure detail Reports the installed products and other details You cannot use group_by_date invPtrLoc jre oh patch property_file retry this option with the a11 option Specifies that OPatch should group all installed patches by the date they were installed in the Oracle home Specifies the location of the oraInst loc file You need this option if you used the invPtrLoc option during installation Oracle recommends the use of the default Central Inventory for a platform Specifies the location of a particular JRE Java for OPatch to use instead of the default location under the Oracle home directory Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE_HOME environment variable Specifies the patches installed in the Oracle home Indicates the user defined property file that OPatch should use The path to the property should be absolute This property file takes precedence over the property file that OPatch supplies Specifies how many times OPatch should retry when there is an inventory lock failure Query Command for OUI based Oracle Homes This command queries a specific patch for specific details It provides information about the patch and the system being patched Syntax Use the following syntax for this command opatch query al
94. OPatch to read the SQL script from the patch and run it on the specified SIDs You must specify this option for the patchmd xml SQL script specification and custom SQL script sglScript Specifies OPatch to run this custom SQL script This is an optional parameter connectString Provides a list of database instance SIDs user and password to be patched Each entry is separated by a comma The value for this option has the following format SID1 USER1 PASSWORD1 NODE1 SID2 USER2 PASSWORD2 NODE2 Standalone SQL Execution OPatch provides a utility to run only the SQL scripts to patch specified database instances Use this utility only when you cannot apply or roll back SQL procedure actions using normal Apply or Rollback sessions The syntax for Apply is as follows opatch util applySql id lt patchIDs gt connectString lt SID1 USER1 PASSWORD1 NODE1 gt The syntax for Rollback is as follows opatch util rollbackSql ph lt patchLocation gt or phBaseFile lt filename gt or phBaseDir lt dirname gt connectString lt SID1 USER1 PASSWORD1 NODE1 gt Online Patching Regular patches typically contain o object files and or a archive libraries and therefore require a relink of the RDBMS binary Online patches however contain so files which are dynamic shared libraries and do not require a relink of the RDBMS binary Consequently since a relink is not needed you can apply or roll back online patches
95. Oracle Universal Installer and OPatch User s Guide 11g Release 1 11 1 for Windows and UNIX B31207 01 August 2007 ORACLE Oracle Universal Installer and OPatch User s Guide 11g Release 1 11 1 for Windows and UNIX B31207 01 Copyright O 1996 2007 Oracle All rights reserved Primary Author Michael Zampiceni Contributor Sudip Datta Pradeep Kumar Itharaju Bharat Paliwal Phidien Nguyen Vijay Sriram The Programs which include both the software and documentation contain proprietary information they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright patent and other intellectual and industrial property laws Reverse engineering disassembly or decompilation of the Programs except to the extent required to obtain interoperability with other independently created software or as specified by law is prohibited The information contained in this document is subject to change without notice If you find any problems in the documentation please report them to us in writing This document is not warranted to be error free Except as may be expressly permitted in your license agreement for these Programs no part of these Programs may be reproduced or transmitted in any form or by any means electronic or mechanical for any purpose If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United Stat
96. Patchsets and Upgrades a Post installation Tasks Deinstalling Real Application Clusters Software Converting Single instance Nodes to Real Application Clusters Troubleshooting Real Application Clusters Oracle Clusterware Installation Oracle Universal Installer and Real Application Clusters The Oracle Universal Installer facilitates the installation of Oracle Clusterware In most cases you use the graphical user interface GUI provided by the Oracle Universal Installer to install the software However you can also use the Oracle Universal Installer to complete non interactive or silent installations without using the GUI The Oracle inventory maintains records of Oracle software versions and patches Each installation has a Central Inventory where the Oracle home is registered Oracle software installations have a local home directory whose path location is recorded in Installing Cluster Environments 5 1 Oracle Universal Installer and Real Application Clusters the Central Inventory The local inventory directory for each Oracle software installation contains a list of components and applied interim patches associated with that software Because faulty inventory information can corrupt your Oracle software installation the Oracle Universal Installer must perform all read and write operations on Oracle inventories Ensure that you do not modify files in the Central Inventory or the Oracle home inventory When you i
97. Real Application Cluster Environment using Cloning If you have a shared Oracle Clusterware home append the cfs option to the command example in this step and provide a complete path location for the cluster file system Ensure that n_storageTypeOCR and n storageTypeVDSK has been set to 2 for redundant storage Ensure that this value is set to 1 for non redundant storage In this case the mirror locations will also have to be specified On the other nodes execute the same command by passing the additional argument PERFORM_PARTITION_TASKS FALSE perl clone pl ORACLE HOME CRS HOME gt ORACLE HOME NAME CRS HOME NAME gt On_ storageTypeVDSK 2 On storageTypeOCR 2 O sl tableList node2 node2 priv node2 vip node3 node3 priv node3 vip O ret PrivIntrList private interconnect list O sl OHPartitionsAndSpace valueFromDlg partition and space information O noConfig OPERFORM PARTITION TASKS FALSE 3 From the CRS HOMES Ncfgtoollogs directory on the existing node run the following command lt CRS_HOME gt cfgtoollogs cfgToolAl1lCommands This instantiates the Virtual Protocol Configuration Assistant VIPCA the Oracle RAC Notification Service Utility racgons Oracle Clusterware Setup crssetup and oifcfg Note Oracle Clusterware cloning can only be performed in silent mode Cloning Oracle RAC Software on Windows System Based Environments Complete the following steps to clone Oracle Database with
98. Requirements minimice 5 14 Checking the Software Requirements sse eene nennen nnnenen 5 14 Checking the Network Requirements sse eene nnne e nennen ciones 5 14 Network Hardware Requirements sse eene nennen nnne nennen 5 14 IP Address Requirements t ette edet nte iibri etd 5 14 Checking Individual Component Requirements eese eee eee nennen 5 15 Configuring Storage for Oracle Clusterware sees eee nenne 5 15 Installing Oracle Clusterware on UNIX esee eee eee e eene nnnnnnn 5 15 Running the Oracle Universal Installer to Install Oracle Clusterware s 5 15 Running the Oracle Universal Installer in Silent Mode to Install Oracle Clusterware 5 16 Oracle Clusterware Background Processes sss eene 5 16 Installing Oracle Clusterware on Windows sse eee nennen 5 16 Running the Oracle Universal Installer to Install Oracle Clusterware ss 5 16 vi Running the Oracle Universal Installer in Silent Mode to Install Oracle Clusterware 5 19 Oracle Clusterware Background Processes sss 5 19 Adding More Nodes to the Cluster for Mass Deployment sss 5 19 Installing Product Software on a Cluster sees nennen 5 20 Cluster Detection a tient ead a e m Nd n HER abb e e itus 5 20 Availability Checkifig cirios eee tetto ree e ODER ederet
99. S fr de The language selections are for the top level component being installed A top level component is the product selected on the Products Selection dialog one per installation session If any sub components not top level do not have files defined for Oracle Internationalization and Translation 8 1 Language Add on the language you select only English only is installed The English files are always installed for all components regardless of user selection or operating system language During installation Oracle Universal Installer examines the language list of each file and file group to determine which files need to be copied The Oracle Universal Installer product is translated into nine languages as shown in Table 8 1 and includes translations for all generic Oracle Universal Installer dialogs Note that any custom dialogs and product specific information that are part of your installations must be translated and staged independently Table 8 1 Oracle Universal Installer Translated Languages Language Abbreviation French fr Brazilian Portuguese pt BR German de Italian it Japanese ja Korean ko Simplified Chinese zh CN Spanish es Traditional Chinese zh TW Language Add on Oracle Universal Installer 11 1 supports post installation language translation additions To get a version of an Oracle product with a particular language up and running you need to invoke Oracle Universal Installer in ad
100. Services Notification Service ODBC Driver ODBC Driverfor Instant Client OLAP OLAP API OLAP RDBMS Files One Off Patch Installer Partitioning Programmer RAC Required Support Files HAS Recovery Manager Security Developer Tools Spatial SQL Developer Starter Database Text UIX Ultra Search Common Files Ultra Search Middle Tier Ultra Search Server Ultra Search Server Rdbms Universal Installer Wallet Manager XML Development Kit Generator Required Support Files Perl Interpreter Embedded Gateway Platform Required Support Files Precompiler Common Files Precompiler Required Support Files Provisioning Advisor Framework 7 6 Oracle Universal Installer and OPatch User s Guide 9052 11 1 0 3 4 42 11 1 0 11 1 0 4 2 9 2 0 11 ul N O w e As EDGE EN EM Erben Eni E al N N PoP LS pO pO PO popa pe CO L3 pt Beo Or a EN CU Or OE A O CROP Qo SX d ga ux Oc Cx SO og x Xxx XO oerOC 0r E 4X 4X Cr o 4 CHO OO O p nB p mit N H HB H H t wor Hs PPP OK uu OK HPP COCK HE HPP PPP SPP COCK Hs SP PP 0 ms PPP PSP PP OCKr KH FPP SPP PSP PPP DOCO KR BRP ORO PA sO OO 0 0 Oi ee SS SO Q XQ 1 Q an OO O O O C Q0 Q O QU O QG OO 0X0 OG OO QUO O OA Om 0 0 O0 QUO OO GO oO 0 10 00 200 Prerequisite Checks for OPatch RDBMS Required Support Files RDBMS Required Support Files for Instant Client ID regexp 2 1 Required Support Files 11 Sample Schema Data Secure Socket Layer Secur
101. UAGES en Component oracle swd Phe sa cesta re a il Rs A a tS ll Aa net A component_languages en dls2esotimz cA tasi eM e Y DT teeter ee ee SY E oe Oe eke oct Name install_type Datatype String Description Installation type of the component The following choices are available The value should contain only one of these choices The choices are of the form Internal Name External name Please use the internal name while specifying the value Complete Complete Typical Minimum H Custom Custom Example INSTALL TYPE Complete Component oracle swd Sample Files D 5 Sample Response File Ea di a tl d LL UL install type Typical EE Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductName Component oracle swd fie wench ea A enc eu e ee cea eS bee eee eS i ee oracle swd prod_home lt Value Unspecified gt Pd AMT ee ee ELA ta Me eee A ee ee NE Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductName Component oracle swd oui EDAT A DE a ee EE oracle swd oui prod_home lt Value Unspecified gt A M Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductNam
102. Variables for clone pl with the O Option Variable Datatype Description CLUSTER_NODES String Represents the cluster node names you selected for installation For example List if you selected node1 CLUSTER NODES node1 b Response Boolean Only set this variable when performing a silent installation with a response file The valid values are true or false S clustername String Set the value for this variable to be the name of the cluster that you are creating from a cloning operation using a maximum of 15 characters Valid characters for the cluster name can be any combination of lower and uppercase alphabetic characters A Z numerics 0 9 hyphens pound signs and underscores Sl tableList String Set the value of this variable to be equal to the information in the cluster List configuration information table This file contains a comma separated list of values The first field designates the public node name the second field designates the private node name and the third field designates the virtual host name OUI only uses the fourth and fifth fields and they should default to N Y The OUI parses these values and assigns s publicname and S privatename variables accordingly For example nodel nodel priv nodel vip N Y node2 node2 priv node2 vip N Y Cloning Oracle Software 6 17 Adding Nodes Using Cloning in Oracle Real Application Clusters Environments Table 6 3 Cont Windows System Based Varia
103. XIT CONFIRMATION parameter 3 7 SHOW INSTALL PROGRESS PAGE parameter 3 8 SHOW OPTIONAL CONFIG TOOL PAGE 3 8 SHOW RELEASE NOTES 3 8 SHOW ROOTSH CONFIRMATION parameter 3 8 SHOW SPLASH SCREEN parameter 3 8 SHOW SUMMARY PAGE parameter 3 8 SHOW WELCOME PAGE parameter 3 8 silent installation 3 1 specifying 3 11 value of component variable 3 13 value of session variable 3 12 TOPLEVEL COMPONENT parameter 3 8 UNIX GROUP NAME parameter 3 8 using 3 11 variable lookup order 3 4 variable values 3 4 3 5 RESPONSEFILE VERSION parameter 3 6 RESTART SYSTEM parameter 3 7 Rollback command for OUI based homes 7 17 for standalone OPatch 7 27 rolling patching 7 34 RSA key 5 6 running in silent mode to install 5 16 OUI after installation 4 12 SELECTED_LANGUAGES 3 10 SELECTED_LANGUAGES variable 8 1 session variables using to create Central Inventory 2 7 setting response file variables 3 12 SHOW_COMPONENT_LOCATIONS_PAGE parameter 3 7 SHOW_CUSTOM_TREE_PAGE parameter 3 7 SHOW_DEINSTALL_CONFIRMATION parameter 3 9 SHOW_DEINSTALL_PROGRESS parameter 3 9 SHOW_END_SESSION_PAGE parameter 3 7 SHOW_EXIT_CONFIRMATION parameter 3 7 SHOW_INSTALL_PROGRESS_PAGE parameter 3 8 SHOW_OPTIONAL_CONFIG_TOOL_PAGE 3 8 SHOW RELEASE NOTES 3 8 SHOW ROOTSH CONFIRMATION parameter 3 8 SHOW SPLASH SCREEN parameter 3 8 SHOW SUMMARY PAGE parameter 3 8 SHOW WELCOME PAGE parameter 3 8 silent deinstallation 4 11
104. You can use this option only if you specify the retry option Removes conflicting patches from the system If a conflict exists that prevents the patch from being applied you can use this option to apply the patch OPatch removes all the conflicting patches before applying the current patch Passes parameters to the init script which executes before prerequisite checks are run The values for this option must be enclosed in double quotes Specifies the location of the oraInst loc file The invPtrLoc option is needed when this option is used during installation Oracle recommends the use of the default Central Inventory for a platform Instructs OPatch to use JRE Java from the specified location instead of the default location under the Oracle home directory Specifies that OPatch should patch the local node and update the inventory of the local node It does not propagate the patch or inventory update to other nodes You can use this option on Oracle Real Application Clusters environments and non clustered environments If an entire cluster is shut down before patching you can use this option for non rolling patches Tells OPatch the local node for this cluster You can use this option on Oracle Real Application Clusters environments Specifies the order of nodes that OPatch should patch This option only applies to Oracle Real Application Clusters environments You cannot use it with the local option with a rolling patch
105. a local file system Oracle recommends that you choose the following path oracle base oraInventory If the Oracle base directory is on a cluster file system or on an NFS file system on a NAS device you must specify a path for the Oracle Inventory directory on a local file system The Oracle base directory must be on a local file system to enable all of the nodes to have separate inventories Oracle Universal Installer creates the directory that you specify and sets the correct owner group and permissions for it You do not need to create it Installing Cluster Environments 5 11 Pre installation Tasks for Real Application Clusters on UNIX Note AllOracle software installations rely on the Oracle base directory Make sure that you back it up regularly Do not delete the Oracle base directory unless you have completely removed all Oracle software from the system Oracle Clusterware Home Directory The Oracle Clusterware home directory is the directory where you choose to install the software for Oracle Clusterware You must install Oracle Clusterware in a separate home directory When you run Oracle Universal Installer it prompts you to specify the path to this directory as well as a name that identifies it Oracle recommends that you specify a path similar to the following for the Oracle Clusterware home directory u01 crs oracle product 11 1 0 app Note Because you must change the permissions of all of the
106. ack subset and skips the automatic rollback conflict then asks you then an apply subset patch It then then a reapply to run again without continues and applies applying a bug conflict the other patches patch You can use the force option to instruct OPatch to automatically roll back the conflicting patch then apply the new patch Patch Conflict Detection and Resolution OPatch detects and reports any conflicts encountered when applying an Interim patch with a previously applied patch The patch application fails in case of conflicts You can use the force option of OPatch to override this failure If you use this option the installer first rolls back any conflicting patches and then proceeds with the installation of the desired interim patch You may encounter a bug conflict and might want to remove the conflicting patch This process is known as patch rollback During patch installation OPatch saves copies of all the files the new patch replaced before the new versions of these files are loaded and stores them in SORACLE HOME patch storage These saved files are called Rollback files and are the key to making patch rollback possible When you roll back a patch these Rollback files are restored to the system You should only override the default behavior by using the force flag if you completely understand the patch Rollback process To roll back a patch execute the following command OPatch opatch rollback id Pat
107. acle Universal Installer and OPatch User s Guide Response File Format Therefore you can either specify the location to look for it in the response file or you can copy them into the disk For example Product Shiphome Location stage RESTART SYSTEM Set this boolean variable to TRUE if you want to restart the system without the user s confirmation This is the force value for restarting the system NEXT SESSION Set this boolean variable to TRUE if the installer needs to go to the File Locations page for another installation or to another response file if you are performing a silent installation NEXT SESSION TRUE NEXT SESSION ON FAIL Set this boolean variable to TRUE to allow users to invoke another installation session even if the current installation session fails This variable is used only if the NEXT SESSION variable is set to TRUE NEXT SESSION ON FAIL TRUE NEXT SESSION RESPONSE Use this string variable to enter the complete path of the next session s response file if you want to automatically begin another silent installation when the current installation is complete If you specify only a file name the Installer looks for the response file in the TEMP orainstall directory This variable is only used if NEXT SESSION is set to TRUE otherwise Oracle Universal Installer ignores the value of this variable NEXT SESSION RESPONSE private usr2 nextinstall rsp ORACLE HOME The location where products ar
108. acle Database 11g 11 1 0 4 0 There are 1 products installed in this Oracle Home Installed Products 118 Agent Required Support Files 10 2 Assistant Common Files 1T Bali Share VIX Buildtools Common Files 11 Character Set Migration Utility Database Configuration and Upgrade Assistants Database SQL Scripts Database Workspace Manager Enterprise Edition Options Enterprise Manager Agent Enterprise Manager Agent Core Files Enterprise Manager Common Core Files Enterprise Manager Common Files Enterprise Manager Database Plugin Agent Support Enterprise Manager Database Plugin Management Service Support Enterprise Manager Database Plugin Repository Support Enterprise Manager Grid Control Core Files 10 2 Enterprise Manager plugin Common Files 1 Enterprise Manager Repository Core Files 10 2 Generic Connectivity Generic Connectivity Common Files HAS Common Files HAS Files for DB Installation Common Files Installer SDK Component JAccelerator COMPANION LDAP Required Support Files OLAP SQL Scripts Oracle 11g Warehouse Builder Server Oracle Advanced Security Oracle Application Express Oracle Call Interface OCI Oracle Clusterware RDBMS Files 11 1 Oracle Code Editor 201000 Oracle Configuration Manager 10 2 Oracle Containers for Java Oracle Core Required Support Files Oracle Data Mining RDBMS Files Oracle Database 11g Oracle Database 11g Oracle Database 11g interMedia Files 11 Oracle Database User Interface 2
109. acle Inventory logs directory For Linux based systems the logs are kept in the inventory location gt logs directory To determine the location of the Central Inventory see Locating and Viewing Log Files If you have installed patches you can check their status by running the following commands For Windows based system computers c YORACLE BASEVORACLE HOMEVOPatch set ORACLE HOME ORACLE HOME using patch c ORACLE BASEVORACLE HOMEVOPatch opatch lsinventory a For Linux based and UNIX based systems ORACLE BASE ORACLE HOME OPatch setenv ORACLE HOME ORACLE HOME using patch ORACLE BASE ORACLE HOME OPatch opatch lsinventory 2 Archive and compress the source Oracle home using your preferred tool for archiving For more information on this see Source Preparation Phase 6 4 Oracle Universal Installer and OPatch User s Guide Cloning an Oracle Database 11 1 Oracle Home Cloning an 11 1 Oracle Database To clone the 11 1 Oracle Database perform the following steps 1 2 Copy the compressed zip or archive file to the target computer Extract the contents of the compressed zip or archive file in the target computer For more information on extracting the contents see Cloning Phase On the target computer go to the SORACLE_HOME clone bin directory and run clone pl This is a Perl script that performs all parts of the cloning operation automatically by calling various utilities and OUI This sc
110. acle home inventory ARU IDs for platforms 2 6 components file comps xml 2 6 home properties file 2 6 Oracle homes attaching 1 4 changing with Home Selector 2 12 creating 2 1 default homes 2 2 description 1 5 detaching 1 4 detaching homes from the Central Inventory 2 8 directory structure UNIX 2 13 Windows 2 13 introduction 2 1 multiple homes support of 2 3 removing 2 2 4 10 target home definition 2 3 Oracle Inventory directory oralnventory 5 11 Oracle Inventory group and UNIX 5 5 Oracle MetaLink certification information 5 4 Oracle RAC Notification Service Utility 6 10 6 12 6 15 ORACLE section of ORAPARAM INI 4 3 Oracle Universal Installer attaching Oracle homes 1 4 Central Inventory 2 4 cloning 4 15 command line arguments 4 13 description 1 3 detaching Oracle homes 1 4 exit codes 4 14 features 1 1 installation modes 1 5 inventory 2 3 description 1 5 operations 1 4 inventory structure 2 3 Oracle home inventory 2 5 pointer file 2 4 logfiles 4 15 Oracle home description 1 5 running 4 12 starting 4 12 system requirements 1 1 updating nodelist 1 4 XML format 2 3 ORACLE BASE 2 3 ORACLE BASE directory 2 13 ORACLE HOME directory 2 14 ORACLE HOME response file parameter 3 7 ORACLE HOME NAME response file parameter 3 7 ORAPARAM NI file APPLTOP STAGE parameter 4 5 BOOTSTRAP parameter 4 5 BOOTSTRAP SIZE parameter 4 5 DEFAULT HOME LOCATION 4 4 DEFAULT HOME NAME para
111. alization installation dialogs language 8 1 language add on 8 2 product language selections 8 1 inventory about 2 3 backup 2 9 Central Inventory creating 2 7 detaching homes 2 8 inventory file 2 4 logs directory 2 5 recovering from corruption 2 10 removing 2 9 removing on UNIX platforms 2 9 removing on Windows platforms 2 9 using session variables 2 7 verifying the operation 2 8 Home Inventory recovering from corruption 2 11 operations 1 4 attaching Oracle homes 1 4 detaching Oracle homes 1 4 updating the nodelist 1 4 Oracle home inventory 2 5 ContentsXML folder 2 7 one offs folder 2 7 scripts folder 2 7 templates folder 2 7 pointer file 2 4 Real Application Clusters 2 11 structure of 2 3 Oracle home inventory 2 5 pointer file 2 4 IP address requirements Windows 5 14 J Java Runtime Environment JRE 1 1 JRE 1 1 JRE_LOCATION parameter in ORAPARAM INI 4 4 JRE MEMORY OPTIONS parameter in ORAPARAM INI 4 4 L LICENSE LOCATION parameter in ORAPARAM INI 4 4 LICENSE TITLE parameter in ORAPARAM INI 4 4 Linux Central Inventory pointer file 2 4 LOCATION FOR DISK2 parameter 3 6 log files for Oracle Universal Installer 4 15 locating and viewing for cloning 6 3 Lsinventory command for OUI based homes 7 15 for standalone OPatch 7 25 mass deployment 5 19 memory requirements 1 1 MetaLink certification information 5 4 minimum downtime patching 7 35 modes of ins
112. all components does not remove the Oracle home The backed up directories and files are ORACLE HOME inventory ContentsXML ORACLE HOME inventory Scripts ORACLE HOME inventory Clone ORACLE HOME inventory invDetails properties The backup is located here ORACLE HOME inventory backup time stamp Oracle Universal Installer Errors Refer to the release notes for information on any Oracle Universal Installer limitations for a particular version The most common Oracle Universal Installer errors are listed below Troubleshooting and Debugging Oracle Universal Installer B 3 Other Tips Other Tips a Out of temp space Make sure you have enough space in the default TEMP or TMP directory Otherwise the installation will not succeed The amount of space required depends on the product being installed Note On UNIX and Windows Oracle Universal Installer looks for TEMP then TMP If neither is set Oracle Universal Installer will default to tmp on UNIX and c NV temp on Windows Incomplete stage and missing files in file groups Make sure you have a good staging area You may have incorrectly copied the staging area from the CD to the hard disk a Exceptions from action libraries NT Services if a service is already started File permissions UNCAUGHT RUNTIME exception when you try to install the product on your machine This is a blanket error catch that catches any run time errors li
113. allation et e ee e d eben i i ete at n bee etes 1 3 Clon caida edad ld ipe eve ae erp etin 1 3 DCi T n 1 3 Upegrades and Patchsets n eet ede petet ete tentat 1 4 Adding Nodes nier ae t ride qae en e en rte ee e rie de em t de rad 1 4 Inventory Operations i sserrep ap a a ai nn arena enne enne nnne nnne nennen 1 4 Attaching Oracle Homes tette sme nete tete tace eei i eer a Dee tant 1 4 D taching Oracle Homes net e eem e ie n i iv putamen 1 4 Updating the Node List retener ode ente idee 1 4 Major Entities Created 1 aede eb ths Diada debo eie de toit rad berita ee Pr Rp be Ie ct 1 4 In vetitOLy i5 suce nona NOTO 1 5 Oracle Home eram eee nt veo e teen e Re ite es 1 5 Modes of Installation rex eese a tee ea dic ee 1 5 Interactive Mode ce daas aede eae deiecit ene 1 5 Suppressed Interactive Mode sse eene nennen nennen 1 5 Silent Mode oet Nee eee ee ites OR beet Ei ete Rr eee e eU t ian ERE Duet 1 5 Cluster Mode A m eet ER Ee eon t EH 1 6 2 Managing Oracle Homes Introduction to Oracle HOMES eese ene neeenenrner tenete nn ncnnn nara cnc etie te eaten eren sun 2 1 Installing an Oracle Product esses eee ee eene nnn nnne nnns 2 1 Removing Oracle Homnies os iue e e ee t de tte d et 2 2 Determining the Default Oracle Home 7o sss eee ee nenne enne 2 2 Multiple Oracle Homes eee A tede mre dert erbe d
114. alling the software from a PC or other system with X server software installed 1 Start the X server software 2 Configure the security settings of the X server software to permit remote hosts to display X applications on the local system 3 Connect to the remote system where you want to install the software and start a terminal session on that system for example an X terminal xterm 4 Ifyou are not logged in as the root user on the remote system enter the following command to switch user to root su root password Creating Required UNIX Groups and Users Depending on whether it is the first time an Oracle software product is being installed on a system and on the products that you are installing you may need to create several UNIX groups and a UNIX user account The following UNIX group and users are required for all installations The Oracle Inventory group oinstall You must create this group the first time you install Oracle software on the system The usual name chosen for this group is oinstall This group owns the Oracle inventory which is a catalog of all Oracle software installed on the system Note If Oracle software is already installed on the system the existing Oracle Inventory group must be the primary group of the UNIX user that you use to install new Oracle software The following sections describe how to identify an existing Oracle Inventory group a The Oracle software owner u
115. alues entered here are appended to the OUI command line which is run to perform the clone operation For example to specify a non default location for the Oracle inventory file on UNIX system computers you can add the following line to the cs properties file clone command line invptrloc private oracle oraInst loc Cloning Oracle Software 6 5 Creating an Oracle Real Application Cluster Environment using Cloning Note To specify multiple arguments separate each argument with a space 4 Locate the log file if desired after OUI starts and records the cloning actions in the cloneActionstimestamp 1log file For Windows based systems this log file is normally located in the following directory c Program Files Oracle Inventory logs For Linux based and UNIX based systems this log file is normally located in the following directory c Program Files Oracle Inventory logs 5 To configure the connection information for the new database run the Net Configuration Assistant a On Windows based systems select Start gt Programs gt Oracle HOME_NAME gt Configuration and Migration Tools gt Net Configuration Assistant a On Linux based and UNIX based systems set the ORACLE HOME variable and run SORACLE HOME bin netca 6 Tocreate a new database for the newly cloned Oracle home run the Oracle Database Configuration Assistant On Windows based systems select Start gt Programs gt Ora
116. and new node3 are the names of the new nodes and Oracle home name is the name of the Oracle home perl clone pl ORACLE HOME Path to the Oracle Home being cloned ORACLE HOME NAME Oracle Home Name for the Oracle Home being cloned O CLUSTER NODES new node 2 new node 3 O LOCAL NODE new node 2 6 8 Oracle Universal Installer and OPatch User s Guide Creating an Oracle Real Application Cluster Environment using Cloning If you have a shared Oracle Database home append the cfs option to the command example in this step and provide a complete path location for the cluster file system Note Set the LOCAL NODE to the node on which you run the clone command On the new node go to the SORACLE HOME directory and run the following command root sh On the new node run the Net Configuration Assistant NETCA to add a listener From the node that you cloned run the Database Configuration Assistant DBCA to add the new instance Creating Oracle RAC Environments on Windows System Based Environments This section explains how to clone an Oracle RAC environment by using Oracle cloning as described in the following procedures Cloning Oracle Clusterware on Windows System Based Environments Cloning Oracle RAC Software on Windows System Based Environments Cloning Oracle Clusterware on Windows System Based Environments Complete the following steps to clone Oracle Clusterware on Windows system compute
117. ans that the installation or inventory operation needs to be performed only on the local node The CLUSTER NODES session variable indicates that the specified nodes are part of the cluster runlInstaller local CLUSTER NODES a b c d In the above example the installation would be performed in the local node and nodes a b c and d would be taken as the part of the cluster When you use the REMOTE NODES session variable in a cluster installation it means that the installation or the inventory operation needs to be performed on the local node and the other nodes apart from the local node cunInstaller REMOTE NODES c d CLUSTER NODES a b c d In the above example the installation would be performed on the local node a and nodes c and d The nodes a b c and d would be taken as the part of the cluster Cluster Deinstallation When removing a clustered Oracle home Oracle Universal Installer first removes software from the node from which you are deinstalling then removes software from the other cluster nodes associated with the Oracle home Command Line Options for Cluster Installations UNIX Only When using Oracle Universal Installer in suppressed or silent mode specify the path to the remote copy or shell program on the local node to use for cluster installations using the following optional flags Installing Cluster Environments 5 21 Patchsets and Upgrades remoteShell path to program remoteCopy path
118. apply patch location skip subset skip duplicate Example 7 2 applies patches 1 2 and 3 that are under the patch location directory OPatch skips duplicate patches and subset patches patches under patch locations that are subsets of patches installed in the Oracle home Example 7 2 opatch napply patch location id 1 2 3 skip subset skip duplicate See the description for the skip subset option in Table 7 3 for more information Duplicate A duplicate patch fixes the same set of bugs fixed by another patch For example if you applied Patch A that fixed bugs 1 2 and 3 and now apply Patch B that also fixes bugs 1 2 and 3 then Patch B is a duplicate of Patch A A patch is always a duplicate of itself Using the skip duplicate Option If you specify this option OPatch removes duplicate patches from the list of patches to be applied For example if you used napp1y yesterday for Patch A discussed above then use napply today with the skip duplicate option for Patch A and other patches duplicate Patch A is skipped Bug Conflict A bug conflict occurs if a set of bugs to be fixed by the current interim patch intersects with some bugs already fixed by one or more previously installed interim patches You must remove the bug conflict before you proceed with the patching by using the apply command with the force flag which rolls back the conflicting patches before applying the new one Example Consider the following
119. applying interim patches to Oracle products using the Oracle proprietary tool OPatch Chapter 8 Oracle Internationalization and Translation This chapter contains information on the various languages in which Oracle produces software Appendix A Frequently Asked Questions This appendix contains frequently asked questions on Oracle Universal Installer and OPatch Appendix B Troubleshooting and Debugging Oracle Universal Installer This appendix contains information on how you can troubleshoot Oracle Universal Installer Appendix C Understanding Oracle Universal Installer Commands This appendix contains information on Oracle Universal Installer commands Appendix D Sample Files This appendix contains a sample response file a sample components file and ORAPARAM INI file Conventions The following text conventions are used in this document Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action or terms defined in text or the glossary italic Italic type indicates book titles emphasis or placeholder variables for which you supply particular values monospace Monospace type indicates commands within a paragraph URLs code in examples text that appears on the screen or text that you enter XV xvi 1 Introduction to Oracle Universal Installer This chapter is designed to aid developers administrators and all other users w
120. at least one optional configuration tool is available You can call the Net Configuration Assistant or the Database Configuration Assistant at the end of a database installation in silent mode also For example to launch the Net Configuration Assistant in silent mode you can pass the parameter s responseFileName netca rsp You can specify both the Auto launch optional tools and User launch optional tools in a string list Example OPTIONAL CONFIG TOOLS configtool2 configtool3 OPTIONAL CONFIG TOOLS Value Unspecified gt If no value is specified for this variable all the tools are run by default If there is a value specified only those optional tools are run while the rest of the tools are ignored Suppress the configuration tool by mentioning only the tools that you want to run as part of the OPTIONAL CONFIG TOOLS variable added for each component You should use the internal names of the configuration tool The response file generator generates these internal names also as part of the options provided for the variable For example if oracle server has Tooll and Tool2 and you want to run only Tool1 in the response file you can specify it as follows oracle server 11 1 0 0 0 0PTIONAL CONFIG TOOLS Tool1 INSTALL TYPE You can set the installation type variable to determine the installation type of the currently selected top level component The installation type variable is only generated for the top l
121. atch to use instead of the default location under the Oracle home directory 7 20 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Table 7 7 Cont Nrollback Options for OUI Patches Option Description local local node minimize downtime no sysmod no relink oh opatch post end opatch pre end Patch Location property file remote nodes report retry silent verbose Specifies that OPatch roll back the local node then update the inventory of the local node It does not propagate the patch or inventory update to other nodes You can use this option on Oracle Real Application Clusters environments and non clustered environments If an entire cluster is shut down before patching you can use this option for non rolling patches Specifies to OPatch that this is the local node for the cluster to be used for rollback You can use this option for Oracle Real Application Clusters environments Specifies the order of nodes that OPatch should patch This option only applies to Oracle Real Application Clusters environments You cannot use it with the local option with a rolling patch Specifies that OPatch need not update the files in the system only the inventory It also does not execute the pre and post scripts This option does not perform any make operation in the patch You can use this option during multiple patch removals and to
122. bles for clone pl with the O Option Variable Datatype Description Sl String OHPartitionsAndSp List ace valueFromDlg Set the value for this variable using the following format 1 Disk number a 2 Partition number a 3 Partition size a 4 Format type 0 for raw and 1 for cluster file system a 5 Drive letter This value is not applicable if you use raw devices Use the available drive letter if you are using a cluster file system 6 Usage type as follows 0 Data or software use only 1 Primary OCR only 2 Voting disk only 3 Primary OCR and voting disk on the same cluster file system partition 4 OCR mirror only 5 OCR mirror and voting disk on the same cluster file system partition For example to configure the OCR and voting disk on raw devices and to not use a cluster file system for either data or software set sl OHPartitionsAndSpace valueFromDlg to list only the partitions that you intend to use for an Oracle Clusterware installation using the following format sl OhPartitionsAndSpace valueFromDlg Disk Partition partition size 0 N A 1 Disk Partition partition size 0 N A 2 6 18 Oracle Universal Installer and OPatch User s Guide 7 Patching Oracle Software with 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 This chapter p
123. c ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt 2 8 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Inventory Removing the Central Inventory Even after all the Oracle homes on a host are removed you will find traces of the inventory with certain log files If you do not want to maintain these files and want to remove the Central Inventory do the following Removing the Central Inventory on UNIX Platforms You can remove the Central Inventory on UNIX by performing the following steps 1 Locate the oraInst 1oc file and get the Central Inventory location inventory loc parameter from this file For Solaris this file is located in the va opt oracle folder For Linux this file is located in the etc folder 2 Remove the Central Inventory by executing the following command rm rf central inventory location 3 Remove the oraInst 10c file by executing the following command with root privileges Solaris rm va opt oracle oraInst loc Linux rm etc oraInst loc Removing the Central Inventory on Windows Platforms You can remove the Central Inventory on Windows by performing the following steps 1 Locate the registry key ANHKEY LOCAL MACHINE Software Oracle inst_ loc 2 Getthe Central Inventory location from this key 3 Delete the Central Inventory directory and all its contents 4 Delete the registry key ANHKEY LOCAL MACHINE Software Oracle inst_loc
124. cation in Storage area scratch userid oracle product 11 1 0 db_1 patch_storage 100100 Apr 22 2007_ 23 57 54 Patch 300500 applied on Tue Jun 05 03 06 55 PDT 2007 Created on 07 Nov 2006 04 57 14 hrs US Eastern Bugs fixed 300500 300501 300502 Files Touched abcl sql ORACLE HOME jlib abci sql abc sql ORACLE HOME jlib abc sql Patch Location in Inventory Patching Oracle Software with OPatch 7 7 Backup and Recovery Considerations for Patching scratch userid oracle product 11 1 0 db 1 inventory oneoffs 300500 Patch Location in Storage area scratch userid oracle product 11 1 0 db_1 patch_storage 300500 Nov 07 2006 04 57 14 OPatch succeeded Backup and Recovery Considerations for Patching Note Itis highly recommended that you back up the ORACLE HOME before any patch operation You can back up the ORACLE HOME using your preferred method You can use any method such as zip cp r tar and cpio to compress the ORACLE HOME If the ORACLE HOME does not appear when you execute the opatch 1sinventory detail command the ORACLE HOME might be missing from the Central Inventory or the Central Inventory itself could be missing or corrupted If the ORACLE HOME is listed when you execute the opatch 1sinventory detail command but the products and components within the ORACLE HOME are not listed the inventory within the ORACLE HOME local inventory might be missing or corrupted If the local inven
125. ch 7 1 Requirements for OPatch a Scalability OPatch is scalable to support a large number of patches Reliability OPatch is reliable and protects the Oracle home and inventory It can bring back the Oracle home to a stable state from patch application failures It can also easily detect patch conflicts Availability Opatch s online patching improves system availability by allowing database patches to be applied without needing to shut down databases Portability OPatch is compatible with all operating systems for which Oracle releases software Robust OPatch is very robust It is very easy to apply a patch as well as remove it a Easy to maintain OPatch is easy to maintain and is also extensible Support for Silent Operation OPatch supports silent operation This mode allows you to run the software without any user interaction Support for Real Application Clusters OPatch supports Real Application Clusters and works well in that setup It is easy to extend it to Enterprise Manager Grid Control Easy to debug OPatch has various levels of logging and tracing mechanisms It also has a debug option that helps to easily diagnose software problems OPatch supports the following tasks Applying an interim patch a Rolling back the application of an interim patch Detecting a conflict when applying an interim patch after previous interim patches have been applied It also s
126. ch ID Problem Resolution The following sections provide information and instructions on the following tasks to resolve problems Using logs and traces Recovering from a failed patching session Resolving OPatch application errors 7 38 Oracle Universal Installer and OPatch User s Guide Problem Resolution Logging and Tracing Logging and tracing is a common aid for debugging OPatch maintains logs for all Apply Rollback and Lsinventory operations Each time you execute OPatch a new log file is created The log files are located in the ORACLE HOME cfgtoollogs opatch directory Each log file is tagged with the timestamp of the operation Log files are named as opatch date mm dd yyyy time hh mm ss gt log For example if a log file is created on May 17th 2007 at 11 55 PM it will be named as follows opatch 05 17 2007 23 55 00 10og Note You can set OPatch to debug mode by setting the environment variable OPATCH DEBUG to TRUE Command Index OPatch also maintains an index of the commands executed with OPatch and the log files associated with it in the history txt file located in the ORACLE HOME cfgtoollogs opatch directory An example of the history txt file is as follows Date amp Time Tue Apr 26 23 00 55 PDT 2007 Oracle Home private oracle product 11 1 0 db 1 OPatch Ver 11 1 0 0 0 Current Dir scratch oui OPatch Command lsinventory Log File private ora
127. ch does not keep track of the make operations it did not perform You need to make sure to execute OPatch without this option at the end for compilation Specifies that OPatch does not need to update the files in the system It only updates the inventory It also does not execute the pre and post scripts Specifies the Oracle home directory to use instead of the default This takes precedence over the environment variable ORACLE HOME Marks the end of the post option You use this option with the post option If you do not use this option everything after post until the end of the command is passed into post Marks the end of the pre options You use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location If you do not specify lt patch_locations use this option to point OPatch to a file containing a list of patches to be n applied Each line in the file points to a location of a patch Specifies the parameters to be passed to the post script This script is executed after the patch is applied You need to enclose the values for this option in double quotes Specifies the parameters to be passed to the pre script This script is executed before the patch is applied You need to enclose the values for this option in doubl
128. cle HOME NAME gt Configuration and Migration Tools gt Database Configuration Assistant a On Linux based and UNIX based systems run SORACLE HOME bin dbca Viewing Log and Error Files After cloning you can view the status of the clone operation by navigating to the SORACLE HOME clone 10g directory and by reviewing the log and err files For more information see the section Locating and Viewing Log Files on page 6 3 Creating an Oracle Real Application Cluster Environment using Cloning This section explains how to create an Oracle Real Application Clusters RAC environment by using Oracle cloning The following topics explain how to use cloning for both UNIX and Linux system environments as well as Windows system environments Creating Oracle RAC Environments on UNIX and Linux System Based Environments Creating Oracle RAC Environments on Windows System Based Environments Important Considerations when Cloning Oracle Real Application Clusters Before proceeding note the following advisory information when cloning the Oracle Database with Oracle RAC 6 6 Oracle Universal Installer and OPatch User s Guide Creating an Oracle Real Application Cluster Environment using Cloning The order of the nodes specified should always be the same on all hosts Oracle Clusterware should be installed on the cluster nodes before starting an Oracle RAC installation For a shared home you need to also provide a value f
129. cle product 11 1 0 db 1 cfgtoollogs opatch opatch 2007 Apr 26 23 00 55 PDT Tue log Levels of Logging OPatch follows the Oracle Diagnostic Logging ODL guidelines You can set the log level by using the 1ogLevel level option available This controls the amount of logging OPatch performs according to the ODL guidelines OPatch supports the following log levels a SEVERE a WARNING INFO a CONFIG a FINE a FINER a FINEST Recovering from a Failed Patching Session During patching updates can occur in two phases System Update In this phase the files are replaced in the Oracle home Inventory Update In this phase the details of the patch applied is recorded in the inventory Patching Oracle Software with OPatch 7 39 Problem Resolution The following scenarios for single instance setups and Real Application Clusters setups explain how you can recover from a failed patching session Single Instance Setup When you apply or roll back a patch an interim inventory update exception occurs Cause This occurs when the files on the system are patched but the inventory update has failed A corrupted inventory may cause this problem Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command For UNIX SORACLE HOME patch storage patch i
130. come lost 2 Suppose you apply the patch and something goes wrong You decide to delete the Oracle home from the Central Inventory and restore the original Oracle home To delete the Oracle home from the Central Inventory use the following command runInstaller silent detachHome ORACLE HOME product DBHome ORACLE HOME NAME DBHome On Win32 systems the command would be setup exe silent detachHome ORACLE HOME C product DBHome ORACLE HOME NAME DBHome 3 Delete the Oracle home cd product rm rf product DBHome 4 Restore the original Oracle home and update the Central Inventory Restore the Oracle home to its original location using the following commands mkdir p product DBHome gunzip lt product archive DBHome tar gz tar xf 5 Attach this Oracle home to the Central Inventory runInstaller silent attachHome ORACLE HOME product DBHome ORACLE HOME NAME DBHome On Win32 systems the command would be setup exe silent attachHome ORACLE HOME C product DBHome ORACLE HOME NAME DBHome Recovering from Inventory Corruption The inventory Central and the Oracle home inventory is critically important in the Oracle software life cycle management The following section explains what you need to do in case of inventory corruption Diagnosing and Recovering from Central Inventory Corruption When you execute opatch 1sinventory detail or when you click Installed Products the Oracle home does not appear
131. creating RAC environments on UNIX and Linux 6 7 on Windows 6 9 description of process 1 3 important considerations 6 6 log files 6 3 Oracle Database 11 1 6 4 6 5 overview 6 2 preparing the 11 1 Oracle Database source 6 4 script variables 6 15 source preparation phase 6 2 cluster adding more nodes 5 19 availability checking 5 20 creating clusterware home directory 5 12 deinstallation 5 21 5 23 on UNIX 5 23 on Windows 5 24 detection 5 20 hardware requirements 5 3 installation 5 20 5 21 command line options 5 21 insilent mode 5 21 product software 5 20 OPatch prerequisites 7 4 patching all node patching 7 33 minimum downtime patching 7 35 rolling patching 7 34 patchsets and upgrades 5 22 setup and pre install config tasks UNIX 5 4 Windows 5 13 software requirements 5 3 SSH configuration 5 6 system installation requirements 5 3 troubleshooting 5 27 updating nodes 2 12 Cluster File System CFS 5 21 CLUSTER_NODES parameter 3 9 Index 1 clusterware 5 2 5 16 adding nodes to RAC environments on UNIX and Linux 6 11 on Windows 6 13 background processes 5 16 5 19 cloning 6 6 creating home directory 5 12 RAC environments on UNIX and Linux 6 7 RAC environments on Windows 6 9 deinstallation 5 25 installation on UNIX 5 15 installing with OUI 5 16 in silent mode 5 19 Oracle Clusterware home directory 5 12 setup 6 10 storage 5 15 stty commands 5 8 troubleshooting 5 27 comma
132. cript in escaped quotes opatch post end no sysmod property file Path to property file gt local node Local node name remote nodes List of remote nodes nodel node2 connectString List of connect strings runSql sqlScript path of the sql file gt ptlSchema portal schema gt ptlPassword portal password gt ptlConnect portal connect string gt init parameters for the init script in escaped double quotes opatch init end report Patch Location gt Patching Oracle Software with OPatch 7 9 OPatch Utility for OUI based Oracle Homes Options Table 7 2 lists the options available for this command Table 7 2 Apply Options for OUI Patches Option Description connectString delay force init invPtrLoc local local node minimize downtime no bug superset no inventory Specifies the list of database instances on which the patch needs to be applied Specify the value for this option using the following syntax SID User Passwd Node Example oracle dba dba mymachine oraclel The SID is required but you can disregard the other parameters if desired because OPatch provides default values for them Note If the system is not part of a RAC setup and you want to patch just the local node provide the node name as an empty string Specifies how many seconds to wait before attempting to lock the inventory again for a previous failure
133. ct the partition s disk number and partition number from the list Click Next to proceed c Onthe Disk Configuration Oracle Cluster Registry OCR page choose a partition with sufficient space to hold your OCR and select the partition s disk number and partition number from the list Click Next to proceed d Onthe Disk Configuration Voting Disk page choose a partition with sufficient space to hold your voting disk and select the partition s disk number and partition number from the list Click Next to proceed Note The Oracle Universal Installer pages described in this step displays logical drives from which you must make your selections To be valid for selection a logical drive must be located on a disk without a primary partition 8 After you click Next the Oracle Universal Installer checks whether the remote inventories are set If they are not set the Oracle Universal Installer sets up the remote inventories by setting registry keys The Oracle Universal Installer also verifies the permissions to enable writing to the inventory directories on the remote nodes After completing these actions the Oracle Universal Installer displays a Summary page that shows the cluster node information along with the space requirements and availability Verify the installation that the Oracle Universal Installer is about to perform and click Finish 9 When you click Finish the Oracle Universal Installer installs the OCFS and Oracle
134. ctory structure is similar in all nodes Ensure that all nodes in the cluster have the same time zone settings eo a PF o Install the operating system patches for the Oracle software For more information see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Pre installation Tasks for Real Application Clusters on UNIX You need to complete the following pre installation tasks before you start the Oracle Universal Installer Logging In to the System as root Before you install the Oracle software you must complete several tasks as the root user To log in as the root user complete one of the following procedures Ifyou are installing the software from an X Window System workstation or X terminal then 1 Start a local terminal session for example an X terminal xterm 2 If you are not installing the software on the local system enter the following command to enable remote hosts to display X applications on the local X server xhost 3 Ifyou are not installing the software on the local system use the ssh rlogin or telnet command to connect to the system where you want to install the software telnet remote host 5 4 Oracle Universal Installer and OPatch User s Guide Pre installation Tasks for Real Application Clusters on UNIX 4 If you are not logged in as the root user enter the following command to switch user to root su root password If you are inst
135. d parties Oracle is not responsible for the availability of or any content provided on third party Web sites You bear all risks associated with the use of such content If you choose to purchase any products or services from a third party the relationship is directly between you and the third party Oracle is not responsible for a the quality of third party products or services or b fulfilling any of the terms of the agreement with the third party including delivery of products or services and warranty obligations related to purchased products or services Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party Contents BAG sn A NA AA tui penu dum AR T xiii Audi resaltados xiii Documentation Accessibility sene ro conan nnne nennen nnns xiii Str ctilteua sra fos dee Me s e mee O x Tihs es ae ron cae Ue oh te xiv CONVENIOS es ettet tata XV 1 Introduction to Oracle Universal Installer System Requirements 5 o ee prete digo Gd ng boe Bde Hb ebi dier Ri pri ture era a 1 1 Key Features oon det nente P AB sate seventeen E ende am pn ibd 1 1 Vi ae REC PR II ie ede 1 2 Oracle Universal Installer acude dee eiecit eec eni egre ala e Ed dede ket 1 3 OPatchisx acere Sates een ete ER at E RE e Ett 1 3 Actions Performed by the Utilities sssssssseeseeee eee eene 1 3 Installatiori 2 5 oen Rede bue e e e bete e I die ite i EE RAT 1 3 Demst
136. d timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt When you apply or roll back a patch an OiiOneoffException occurs Cause This occurs when the files on the system are patched but the inventory update has failed This may occur because the base component of the interim patch may not be present in the inventory Action OPatch tries to restore the Oracle home automatically and displays a message for the same If OPatch does not display a message stating that it has restored the Oracle home perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt When you apply a patch and execute opatch Isinventory it returns nothing Cause This may occur because all the patches applied before the application of the current patch are lost or the patches might not have been updated in the inventory Action Perform the following step
137. d to run the script only the first time you install Providing a UNIX Group Name If you are installing a product on a UNIX system the Installer also prompts you to provide the name of the group that owns the base directory You must choose a UNIX group name that has permissions to update install and remove Oracle software Members of this group must have write permissions to the base directory chosen Only users who belong to this group are able to install or remove software on this host Deinstalling Oracle Products The following sections describe how to remove products installed using Oracle Universal Installer Specifically these sections describe Removing Oracle Products and Oracle Homes Deinstalling Top level Products That Have Dependents Silent Deinstallation Removing Oracle Products and Oracle Homes You can deinstall Oracle products before selecting products to install or after a successful installation To remove an Oracle product or Oracle home using interactive mode perform the following steps 1 Start Oracle Universal Installer from a CD ROM or For Windows platforms launch Oracle Universal Installer from the Start menu by selecting Start Installation Products Oracle Universal Installer For UNIX platforms at the command line run the script called runInstaller from the directory where it is stored which is by default at the same level as the first Oracle home created on that host Clic
138. d with the same name and copy over the OH inventory directory from that home to all the faulty nodes Does the list of installed products in the Oracle Home and comps xml inside the Oracle Home show up on doing opatch Isinventory detail YES Is the node list and local node information corresponding to the Oracle_Home correct while doing opatch Isinventory detail CRS RAC Install Successful On the node run updateNodeList as OH oui bin lt runinstaller or setup exe gt updateNodeList ORACLE_HOME lt oracle home NO location gt CLUSTER_NODES lt comma separated nodelist gt LOCAL_NODE lt local node gt local Installing Cluster Environments 5 27 Troubleshooting Real Application Clusters Oracle Clusterware Installation 5 28 Oracle Universal Installer and OPatch User s Guide 6 Cloning Oracle Software This chapter provides information about Oracle cloning using Oracle Universal Installer OUI This chapter contains the following topics About Cloning Overview of the Cloning Process Locating and Viewing Log Files Cloning an Oracle Database 11 1 Oracle Home Creating an Oracle Real Application Cluster Environment using Cloning a Adding Nodes Using Cloning in Oracle Real Application Clusters Environments About Cloning Cloning is the process of copying an existing Oracle installation to a different location and updating the copied bits to work in the new
139. dLangs mode Perform the following steps to change the language of an installation using Oracle Universal Installer 1 Execute the following command runInstaller addLangs A welcome page with a language add on specific message appears 2 Click Next The Specify Home Details page appears 3 Select the name and full path of the home containing the product to which you want to add languages and click Next The Language Selection page appears 4 Select the languages for which you want your Oracle products to be upgraded and click Next A summary page displaying a snapshot of your preferences appears 5 Review your preferences and click Install After the languages are successfully updated the End of Language Upgradation page appears 6 Click Exit 8 2 Oracle Universal Installer and OPatch User s Guide A Frequently Asked Questions This appendix is organized into the following sections Oracle Universal Installer a OPatch Oracle Universal Installer This section answers the frequently asked questions for Oracle Universal Installer On Windows when I run Oracle Universal Installer setup exe it is not invoked This may occur because some system resources are being held by some services If you stop these services Oracle Universal Installer can be invoked To run Oracle Universal Installer again execute the following command setup J Dsun java2d noddraw true Dsun awt nopixfmt true When I start Orac
140. des Using Cloning in Oracle Real Application Clusters Environments Table 6 2 Cont UNIX and Linux System Based Variables for clone pl with the O Variable Datatype Description S OcrVdskMirrorlRetVal String Set the value of this variable to be the location of the first additional voting disk You must set this variable if you choose a value of 1 for then storageTypeVDSK variable or Not Redundant For example oradbshare oradata vdiskmirrorl S ocrpartitionlocation String Set the value of this variable to the OCR location Oracle places this value in the ocr loc file when you run the root sh script For example oradbshare oradata ocr S ocrMirrorLocation String Set the value of this variable to the value for the OCR mirror location Oracle places this value in the ocr 1oc file when you run the root sh script You must set this variable if you choose a value of 1forthen storageTypeOCR variable or Not Redundant For example oradbshare oradata ocrmirror s VdskMirror2RetVal String Set the value of this variable to be the location of the second additional voting disk You must set this variable if you choose a value of 1 for the n_storageTypeVDSK variable or Not Redundant oradbshare oradata vdiskmirror2 Variables for Windows System Based Environments Table 6 3 describes the variables that can be passed to clone p1 with the O option for Windows system environments Table 6 3 Windows System Based
141. duct Options TYPE 0 gt DEP LIST DEP NAME oracle rdbms VER 11 1 0 0 0 PLAT Linux gt DEP NAME oracle options VER 11 1 0 0 0 PLAT Linux gt DEP NAME oracle network VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle sysman console db VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle rdbms oci VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle precomp VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle xdk VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle doc VER 11 1 0 0 0 PLAT Linux gt DEP NAME oracle winprod VER 11 1 0 0 0 PLAT ALL PLATFORMS gt DEP NAME oracle sqlplus isqlplus VER 11 1 0 0 0 PLAT Linux gt lt DEP NAME oracle odbc VER 11 1 0 0 0 PLAT Linux gt lt DEP_LIST gt DEP GRP DEP GRP NAME Required EXT NAME Required Dependencies TYPE R gt lt DEP_LIST gt lt DEP NAME oracle rdbms install common VER 11 1 0 0 0 PLAT Linux gt lt DEP_LIST gt DEP GRP DEP GRP NAME OptionalDecideNow EXT NAME Installed Components TYPE 0 gt DEP LIST DEP NAME oracle DEP NAME oracle DEP NAME oracle DEP LIST DEP GRP DEP GRP LIST DEP LIST IDX 1 gt swd oui VER 11 1 0 0 0 PLAT Linux gt swd opatch VER 11 1 0 0 0 PLAT Linux gt dbjava jdbc12 VER 11 1 0 0 0 PLAT Linux gt DEP NAME oracle rdbms VER 11 1 0 0 0 DEP GRP NA
142. duct marketing name as specified in the oraparam ini file for example Db11g and home identifier 2 2 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Inventory is a counter derived from the Central Inventory For example the ORACLE HOME name could be OraDbiig 1 The ORACLE HOME path is taken first from the command line if specified or else from the response file if specified If not the ORACLE HOME environment variable is used If neither is specified the following conventions are used for the path IfORACLE_BASE has been specified in the environment SORACLE BASE product version short name counter For example SORACLE BASE product 11 1 0 Db 1 IfORACLE BASE has not been specified in the environment SHOME product version short name counter Where short name is the short product name for example Db and counter is picked up based on the existence of the files For example the ORACLE HOME path could be HOME product 11 1 0 Db 1 The instance related directory location is accepted first from the response file if specified If not the oradata flash recovery area admin and doc directories are created under ORACLE BASE If ORACLE BASE has not been specified the default is the SORACLE HOME oradata directory If the parent directory of the Oracle home is writable these directories are created in the parent directory of the Oracle home Multiple O
143. ducts that you intend to install verify that the required software is installed on the system For more information on software requirements see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Configuring Kernel Parameters Each cluster node must meet the recommended kernel values For information on verifying and setting the kernel parameters see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Identifying Required Software Directories You must identify or create the following directories for the Oracle software as follows Oracle Base Directory Oracle Inventory Directory Oracle Clusterware Home Directory Oracle Home Directory The following subsections describe the requirements for these directories 5 10 Oracle Universal Installer and OPatch User s Guide Pre installation Tasks for Real Application Clusters on UNIX Oracle Base Directory The Oracle base directory acts as a top level directory for Oracle software installations It is analogous to the C Oracle directory used for Oracle software installations on Windows systems On UNIX systems the Optimal Flexible Architecture OFA guidelines recommend that you use a path similar to the following for the Oracle base directory mount point app oracle sw owner In this example mount point is the mount point directory for the file system that will contain the Oracle software The examples in t
144. ducts xml gt To specify the shiphome location addLangs To add new languages to an already installed product addNode For adding node s to the installation attachHome For attaching homes to the OUI inventory cfs Indicates that the Oracle home specified is on cluster file system shared This is mandatory when local is specified so that Oracle Universal Installer can register the home appropriately into the inventory clone For making an Oracle Home copy match its current environment debug For getting the debug information from OUI deinstall For deinstall operations detachHome For detaching homes from the OUI inventory without deleting inventory directory inside Oracle home enableRollingUpgrade Used in cluster environment to enable upgrade of a product on a subset of nodes on which the product was installed executeSysPrereqs Execute system prerequisite checks and exit force Allowing silent mode installation into a non empty directory help Displays above usage ignorePatchConflicts Ignore all conflicts with existing interim patches during an upgrade The conflicting interim patches are removed from the home ignoreSysPrereqs For ignoring the results of the system prerequisite checks local Performs the operation on the local node irrespective of the cluster nodes specified printdiskusage Log debug information for disk usage printmemory Log debug information for memory usage printtime Log debug
145. e Lsinventory Command for OUI based Oracle Homes This command lists the inventory for a particular Oracle home or displays all installations that can be found This command does not have any required options Syntax Use the following syntax for this command opatch lsinventory all delay value detail all nodes invPtrLoc Path to oraInst loc jre LOC group by date oh ORACLE HOME retry value patch property file path to property file gt Example The following example shows the output of opatch 1sinventory detail Oracle interim Patch Installer version 11 1 0 0 0 Copyright c 2007 Oracle Corporation All rights reserved Oracle Home home oracle TEST product 11 1 0 db 1 Central Inventory home OUIHome Opatch from home oracle TEST product 11 1 0 db 1 oraInst loc OPatch version 11 1 0 0 0 OUI version L1 12050 50 OUI location home oracle TEST product 11 1 0 db 1 oui Log file location home oracle TEST product 11 1 0 db1 cfgtoollogs opatch opatch 2007 May 25 11 09 34 IST Wed log Lsinventory Output file location home oracle TEST product 11 1 0 db Installed Top level Products 1 Oracle Database 11g 11 1 0 0 0 There are 1 products installed in this Oracle Home Installed Products 10 Agent Required Support Files Assistant Common Files 11 Bali Share 11 1 Buildtools Common Files 11 Character Set Migration Utility Database Configuration and Up
146. e Component oracle swd oui core rH oracle swd oui core prod home Value Unspecified Hen Bot hee Sees owe Rea ek eee es ee ee R AS ee eee al Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductName Component oracle swd jre Ph iat E A e ee O n hapa eee ae ee nite ahs oe LE ee oracle swd jre 1 3 1 0 0a prod_home lt Value Unspecified gt Moe ce E IL LA MR SE E Ue A LL eee ee edet Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductName Component oracle swd jre rE SEE ss ee E ee A oracle swd jre 1 3 1 1 0a prod_home lt Value Unspecified gt A A See osay Name prod home Datatype String Description Complete path where the product needs to be installed Example PROD HOME C ProductName Component oracle swd jre dues Ace Ae eee to BS sh aha RA CU d aah A d att Ren E td e NEUE oracle swd jre 1 3 0 0 0 prod home Value Unspecified gt O ES APE A E AS A E EAS Name dependency list Datatype StringList Description List of Dependees that needs to be installed along with this product The following choices are available The value can contain any combination of these choices The choices are of the form Internal Name Version External name Please use the inter
147. e TEST product 11 1 0 db 1 Apply Session failed ApplySession failed to prepare the system Interim patch 111000 is a superset of the patch es 111000 in OH home oracle TEST product 11 1 0 db 1 System intact OPatch will not attempt to restore the system OPatch failed with error code 73 Subset Patches to be applied can be subsets of other patches installed in the Oracle home Example Consider the following scenario Patch A installed in the Oracle home fixed bugs 1 2 and 3 Patch B installed in the Oracle home fixed bugs 10 11 and 12 Patch D to be installed fixes bugs 1 and 2 Patch D is a subset of Patch A Using the skip subset Option When you want to skip patches formerly applied in the Oracle home that are now subsets of other patches you want to apply now you can use the Skip subset option of napply For example if you used napply yesterday for patch A that fixed bugs 1 and 2 then you use napply today with the Skip subset option for patch B that fixes bug 1 and patch C that fixes bugs 1 2 and 3 then subset patch A is skipped and patch C then becomes a superset of patch A Example 7 1 applies all patches under the patch location directory OPatch skips duplicate patches and subset patches patches under patch location that are subsets of patches installed in the Oracle home 7 36 Oracle Universal Installer and OPatch User s Guide About Patch Conflicts Example 7 1 opatch n
148. e See the description for the skip subset option in Table 7 3 for more information Options Table 7 3 lists the options available for this command Table 7 3 Napply Options for OUI Patches Option Description all nodes delay force invPtrLoc jdk jre local local_node minimize_downtime no_bug_superset no_inventory Applies the patch using the all node mode Specifies how many seconds to wait before attempting to lock the inventory again for a previous failure You can use this option only if you specify the retry option Removes conflicting patches from the system If a conflict exists that prevents the patch from being applied you can use this option to apply the patch OPatch removes all the conflicting patches before applying the current patch Specifies the location of the oraInst loc file The invPtrLoc option is needed when this option is used during installation Oracle recommends the use of the default Central Inventory for a platform Instructs OPatch to use JDK jar from the specified location instead of the default location under the Oracle home directory If you do not specify the j re option JVM is executed from the 3 dk location Instructs OPatch to use JRE Java from the specified location instead of the default location under the Oracle home directory You cannot specify the jdk and jre options together Specifies that OPatch should patch the local node and update the
149. e Oracle user s home directory and set the correct permissions for it mkdir ssh chmod 700 ssh 3 Enter the following commands to generate an RSA key for version 2 of the SSH protocol usr bin ssh keygen t rsa At the prompts Accept the default location for the key file 5 6 Oracle Universal Installer and OPatch User s Guide Pre installation Tasks for Real Application Clusters on UNIX Enter and confirm a different pass phrase from the Oracle user s password This command writes the public key to the ssh id_rsa pub file and the private key to the ssh id_rsa file Never distribute the private key to anyone Enter the following command to generate a DSA key for version 2 of the SSH protocol usr bin ssh keygen t dsa At the prompts Accept the default location for the key file Enter and confirm a pass phrase that is different from the Oracle user s password This command writes the public key to the ssh id_dsa pub file and the private key to the ssh id_dsa file Never distribute the private key to anyone Copy the contents of the ssh id_rsa pub and ssh id_dsa pub files tothe ssh authorized keys file on this node and to the same file on all other cluster nodes Note The ssh authorized keys file on every node must contain the contents from all of the ssh id_rsa pub and ssh id_dsa pub files that you generated on all cluster nodes Change the p
150. e Socket Layer L Plus SQL SQ L Required Support Files for InstantClient 114 Sun JDK T1455 XDK Required Support Files 11 L Plus Required Support Files LJ Runtime L Parser for Java L Parser for Oracle JVM C O 2 OQ O OO O C O C CO wo OQ GC PPP OK gu uua SPP uod gm O C0 0v CY OO 0 0 x C C UC There are 118 products installed in this Oracle Home In Pa terim patches 3 tch 300100 applied on Tue Jul 10 02 21 40 PDT 2007 Created on 01 Jan 2006 04 57 12 hrs US Eastern Bugs fixed 300101 Files Touched test pch ORACLE HOME hpatch test pch Instances Patched online venkat Patch Location in Inventory scratch userid oracle product 11 1 0 db_1 inventory oneoffs 300100 Patch Location in Storage area scratch userid oracle product 11 1 0 db_1 patch_storage 300100 Jan 01 2006 04 57 12 Patch 100100 applied on Thu Jun 21 21 01 35 PDT 2007 Created on 22 Apr 2007 23 57 54 hrs PST8PDT Bugs fixed 100100 100101 Files Touched shof o ORACLE HOME lib libagenti10 a oracle help AppletWindowManager class ORACLE HOME jlib help4 jar dbui2 jar ORACLE HOME jlib dbui2 jar DummaDummy class ORACLE HOME plsql DummaDummy class Sql scripts Executed scratch userid oracle product 11 1 0 db_1 scripts 2 sql Sql Procedures Touched JAN 300500 1 JAN 300500 2 Patch Location in Inventory scratch userid oracle product 11 1 0 db_1 inventory oneoffs 100100 Patch Lo
151. e Software with OPatch 7 21 Standalone Patching Version Command for OUI based Oracle Homes This command shows the current version number of the OPatch utility Use the following syntax for this command Path to OPatch opatch version Standalone Patching Standalone patching is available for Oracle homes that have not been installed using the Oracle Universal Installer Standalone patching does not have Central Inventory registration but still generates inventory files for the one off inventory and future conflict checking OPatch uses the presence of the OUI directory under ORACLE HOME to determine whether it should operate in OUI based or standalone mode The following sections discuss these standalone patching topics Unsupported services for standalone patching Standalone patching requirements OPatch commands for standalone patching Use cases Unsupported Services for Standalone Patching Standalone patching provides most of the services that OUI based patching provides However standalone patching does not provide the following services that OUI based patching provides Looking up the component inventory Standalone OPatch enables you to look up which patches have been applied to a standalone Oracle home but it does not support looking up product components For example if you run opatch lsinventory on a JDeveloper Oracle Home OPatch shows a list of patches applied on the home It does not show which compo
152. e applied Specify the value for this option using the following syntax SID User Passwd Node Example oracle dba dba mymachine oraclel The SID is required but you can disregard the other parameters if desired because OPatch provides default values for them Note If the system is not part of a RAC setup and you want to patch just the local node provide the node name as an empty string delay If you use the retry option with the rollback command specifies how many seconds OPatch should wait before attempting to lock the inventory again if a previous failure occurs id Indicates the patch to be rolled back Use the 1sinventory option to display all patch identifiers Each one off patch is indicated by its ID To successfully roll back a patch you must provide the patch identifier init Passes parameters to the init script which executes before prerequisite checks are run The values for this option must be enclosed in double quotes invPtrLoc Specifies the location of the oraInst loc file You need to use this option if you used the invPtrLoc option during installation Oracle recommends the use of the default Central Inventory for a platform jre Specifies the location of a particular JRE Java for OPatch to use instead of the default location under the Oracle home directory local Specifies that OPatch roll back the local node then update the inventory of the local node It does not propagate the patch or inventory
153. e characters The names are case sensitive The private network interface name must be the same on all nodes The public network interface name must be the same on all nodes a The public interface must be listed first in the ipconfig list Oracle supports the TCP IP protocol for the public and private networks IP Address Requirements Before starting the installation you must identify or obtain the following IP addresses for each node a An IP address and an associated host name registered in the domain name service DNS for each public network interface One unused virtual IP address and an associated virtual host name registered in DNS that you will configure for the primary public network interface 5 14 Oracle Universal Installer and OPatch User s Guide Installing Oracle Clusterware on UNIX The virtual IP address must be in the same subnet as the associated public interface After installation you can configure clients to use the virtual host name or IP address If a node fails then its virtual IP address fails over to another node A private IP address and optional host name for each private interface Oracle recommends that you use private network IP addresses for the private interfaces for example 10 or 192 168 You can use the sSystemRoot system32 drivers etc hosts file on each node to associate private host names with private IP addresses Checking Individual Component Requirements D
154. e checks or not Set to true to continue component installation even when the prerequisite check fails Specifies the host name of the system Specifies the location where prerequisite configuration files are available Specifies the prereqs log location where prerequisite results will be generated Specifies the log location where prerequisite results will be generated Specifies the root sh status whether root sh is required before config or after config This flag is used only on UNIX platforms Specifies the custom message shown for the root_sh dialogue This flag is used only on UNIX platforms Specifies the Root sh location By default it is set to OH root sh This flag is used only on UNIX platforms Specifies if the prereq checker is to be used during the installation or not The value for this variable is set based on the value in the oraparam ini file Specifies if old style system prereqs are to be enabled in the installation scripts The PRE REQUISITE code should use this variable to determine which checks can be turned on or off The value of this variable is set based on the value in the Oraparam ini Specifies if the progress dialog will be shown during the setup of the next session or not This flag is used in chain installs Specifies the title of the progress dialog shown during the setup of the next session This flag is used in chain installs Specifies the text above the progress bar in the progress
155. e directory that contains the Oracle Universal Installer executable file setup exe or runInstaller sh for your installation 2 Enter the following command setup record destinationFile response file name on Windows runInstaller record destinationFile response file name on UNIX Replace the response file name with the complete path for the new response file For example setup record destinationFile C response fileslinstall_oraclellg rsp on Windows runInstaller record destinationFile private temp install oraclellg rsp on UNIX Customizing and Creating Response Files 3 3 Response File Format 3 Use the Oracle Universal Installer user interface to select your installation options These will be recorded When Oracle Universal Installer displays the Summary page you can either continue with the installation or exit Oracle Universal Installer saves your new response file using the path and file name you specified on the command line Response File Format The following sections describe the organization and content of an Oracle Universal Installer response file Variable Values Comments a Headers Response File Parameters Note Oracle recommends using an absolute path for the file name However if the file name is a relative path it should be relative to the directory where the oraparam ini file is present Variable Values This section contains information on ho
156. e inventory Diagnosing and Recovering from Oracle Home Inventory Corruption When you execute opatch lsinventory detail or when you click Installed Products the Oracle home appears but the products and components within the Oracle home are not listed Cause This may be due to a missing or corrupted Oracle home inventory Action If the Oracle home inventory is missing or corrupted restore the Oracle home inventory If you have not backed up the Oracle home inventory you may have to install the software on a different node with the same platform and install the same patch levels including interim patches After that you can simply copy the inventory directory from the patched Oracle home to the location of the affected Oracle home Note For Oracle Universal Installer version 10 2 0 2 0 and above you can use the following scripts in Oracle home to recover from Oracle home inventory corruption detachHome bat detachHome sh Use this script if the Oracle home is corrupted or needs to be updated attachHome bat attachHome sh Use this script if the Oracle home needs to be added to the inventory Real Application Clusters In a Real Application Clusters environment the inventory also contains a list of nodes associated with an Oracle home It is important that during upgrade and patching the inventory is correctly populated with the list of nodes For more information see Chapter 5 Installing Cluster Envir
157. e it by using the updateNodeList flag of Oracle Universal Installer You can bypass remote actions using the local flag as shown below SORACLE HOME oui bin runInstaller or setup exe gt updateNodeList ORACLE HOME oracle home location CLUSTER NODES commaseparated nodelist for example nodel node2 node3 gt noClusterEnabled If you want to specify the local node or remote nodes of a Real Application Clusters setup to OPatch you can use the LOCAL NODE or REMOTE NODES session variable and specify the node name s as shown below SORACLE HOME oui bin runInstaller or setup exe ORACLE HOME oracle home location REMOTE NODES commaseparated nodelist for example nodel node2 node3 LOCAL NODE nodelist for example nodel gt If OPatch does not automatically detect Real Application Clusters or its nodes you need to investigate the contents of the inventory and ensure that it is complete You can patch Real Application Clusters in three different ways All Node Patching Rolling Patching Minimum Downtime Patching The following sections provide detailed information for these types of Real Application Clusters patching All Node Patching Figure 7 1 shows a basic example of All Node Patching Patching Oracle Software with OPatch 7 33 Real Application Clusters Patching Figure 7 1 All Node Patching ALL NODE PATCHING System A E System C Systems A B and C are nodes in this cluster When you per
158. e quotes Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies Tells OPatch the list of remote nodes You can use this option on Oracle Real Application Clusters environments The node names must be separated with commas but without spaces Prints the action to the screen without executing it Tells OPatch how many times it should retry when there is an inventory lock failure Suppresses user interaction and defaults any answers to yes y Skips patches to be applied that are duplicates of other patches installed in the Oracle home Two patches are duplicates if they fix the same set of bugs Skips patches to be applied that are subsets of other patches installed in the Oracle home One patch is a subset of another patch if the former fixes a subset of bugs fixed by the latter For example if you used napply yesterday for patch A that fixed bugs 1 and 2 then you use napp1y today with this option for patch B that fixes bug 1 and patch C that fixes bugs 1 2 and 3 then subset patch A is skipped and patch C then becomes a superset of patch A 7 14 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Table 7 3 Cont Napply Options for OUI Patches Option Description verbose Prints additional OPatch output to the screen as well as to the log fil
159. e to be installed You must enter a value for ORACLE HOME for a complete silent installation ORACLE HOME NAME The name of the current Oracle home You must enter a value for ORACLE HOME NAME fora complete silent installation SHOW COMPONENT LOCATIONS PAGE The location page which appears in a custom installation type can be suppressed by setting this value to FALSE If you set the value to FALSE the user is prevented from specifying alternate directories If there are products with installed directories which can be changed you may want to set the value to TRUE SHOW CUSTOM TREE PAGE Set SHOW CUSTOM TREE PAGE to TRUE if the custom tree page in the installer must be shown In the Custom Tree page dependencies can be selected or deselected This page appears only in a custom installation type SHOW END SESSION PAGE The installation success failure page which appears at the end of an installation can be suppressed by setting this value to FALSE SHOW EXIT CONFIRMATION Set to TRUE if you need to show the confirmation when exiting the installer SHOW EXIT CONFIRMATION TRUE Customizing and Creating Response Files 3 7 Response File Format SHOW INSTALL PROGRESS PAGE The installation progress page which appears during the installation phase can be suppressed by setting the value to FALSE SHOW OPTIONAL CONFIG TOOL PAGE Set to TRUE if you must show the Optional Configuration Tools page in the installer The Optional Conf
160. ect list of required files Why Perform a Silent Installation Silent installations can be useful if you have to install an Oracle product multiple times on multiple computers If the options you select while installing on each computer are always the same you save the time of reviewing each installation screen and selecting the various installation options Silent installations can also ensure that multiple users in your organization use the same installation options when they install your Oracle products This makes supporting those users easier because you already know what components and options have been installed on each computer Before you perform a silent installation you should review the settings in the response file template provided with your Oracle product Note If you attempt to perform a silent installation on a UNIX computer where no Oracle products have been installed Oracle Universal Installer uses the default inventory location then prompts you to run the oraInstRoot sh script with root privileges upon successful installation The script is saved in the Central Inventory oralnventory directory This script sets up the Central Inventory on a clean host You can override the default location by setting it in INVENTORY_ LOCATION Note that this location is ignored if a Central Inventory already exists and is pointed to by var opt oracle oralnst loc or etc oralnst loc for Linux AIX and Sequent
161. ed if you want to proceed For silent installations if a non empty existing directory is specified an error is logged in the console and in the installActions lt timestamp gt log file Also the Oracle Universal Installer aborts To override this condition use the force flag on the command line The effect of using the force flag is the same as selecting Yes while installing in interactive mode You receive a warning message but the installation continues Removing Oracle Homes To remove an existing Oracle home invoke Oracle Universal Installer and click Deinstall Products At the inventory dialog select the homes you want to delete and click Remove You can also use the REMOVE_HOMES variable in the command line or in a response file The syntax is as follows runInstaller deinstall ORACLE HOME LOCATION OF ORACLE HOME gt REMOVE _ HOMES LOCATION OF ORACLE HOME TO BE REMOVED gt silent Determining the Default Oracle Home By default when you start Oracle Universal Installer the software searches your system to determine the default Oracle home where Oracle software should be installed In all cases the ORACLE HOME name is taken first from the command line if it is specified or else from the response file if specified If not the following convention is used for the name Ora short marketing name in oraparam ini home identifier Where short marketing name in oraparam ini is the short pro
162. eeds 2 3 Target FIOM ess Goes dre s edd edle med a edes 2 3 Oracle Universal Installer Inventory sese eee eene nnne ntes 2 3 Structure of the Oracle Universal Installer Inventory sse 2 3 Central Inventory Pointer File ette ee Eae tet tiae erben iata 2 4 Centrallnyventory xen dete edad deii ette e ete Reo nte ERR Rad 2 4 Inventory Files nits tiit hoe hti eed ree dive espe t et eirca 2 4 Logs Directory ione tta e ceti o ea fS RAS er dole rin Se 2 5 Oracle Home Inventory 2 tet ete eee lated rte tiet s 2 5 Components Eileen eia terr rer re are ee dee a tre ree deas 2 6 Home Properties Pile ate reete Ede eto et eet estem 2 6 Other Folders RI RI Rt iubet eb D ee tiet ens 2 6 Creating the Central Inventoty teneret teh eh dra E de ena eerie 2 7 Using the Session Variables iet ette eee rca teet et three oboe ent 2 7 Verifying the Op ration e eee teeth nde pre ce te reed iue 2 8 Detaching Oracle Homes from the Central Inventory ssssssseseseeseeeneee 2 8 Using Optional Flags etiem een ere teet AD E A 2 8 Removing the Central Inventory eee nennen nennen 2 9 Removing the Central Inventory on UNIX Platforms sss 2 9 Removing the Central Inventory on Windows Platforms sess 2 9 Upgrading and Patching the Oracle Home sese ener 2 9 Cloning Oracle Homes coria 2 9 Backing up the Inventory eene nennt nennen nn
163. eeeeeeeeeeeeenee eene enn nennen 4 7 TEMP TMP Directory oho 2 ad E T 4 7 Unmounting a CD aid aea aeei a ean a aieo aa ete a pit ce nt etude 4 7 Installing from a staged HTTP location en nenne 4 8 Special Instructions for UNIX Users Tiero ipo Eirene erene Ene raaa EE Eeron ar eE EEE EREDE EERE 4 8 Failed to Connect to Server Error isisisi aie oaa a a adei ener ener nnns iia i 4 9 Providing a UNIX Installer Location with Root Privileges sese 4 9 Providing a UNIX Group Name sse ee eene nnne nennen nennen 4 10 Deinstallinig Oracle Products 5 ere eere tent tee nte ert Die ere ce eee nage 4 10 Removing Oracle Products and Oracle Homes sss 4 10 Deinstalling Top level Products That Have Dependents esses 4 11 Silent Destaca erae iro een e eese stver lees 4 11 Immediately Displaying the Inventory Dialog Box eese 4 11 Hiding the Inventory Dialog Box sssssseeeeee eene nnne nennen nennen 4 11 Hiding the Deinstallation Confirmation and Progress Dialog Boxes 4 12 Running Oracle Universal Installer After Installation sess eee 4 12 Starting Oracle Universal Installer essen nene nnne 4 12 Command Line Arguments rne hme i er ine nein tede ie ee ie ene ederet ee iei ere 4 13 Using Oracle Universal Installer Exit Codes esses eee 4 14 Cloning Considera
164. em 1 Set tmp in your PATH For more information see Check for System Commands on page 7 3 2 Create an empty file named fuser 3 Shut down the Oracle instances 4 Run the OPatch utility Caution Another way to resolve this problem is to give executable permission to other users for fuser However this exposes a potential security issue in the system and is not recommended Unable to remove a partially installed interim patch Cause Interruption in the patching process potentially causes this problem This may occur if you press Ctrl c during the patching process If the error is the one that OPatch detects it automatically resolves it Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command as follows For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt 7 46 Oracle Universal Installer and OPatch User s Guide 8 Oracle Internationalization and Translation The following sections describe how Oracle Universal Installer supports multiple languages and internationalization Installation Dialogs Language
165. epending on the Oracle products that you intend to install verify the required components for the Oracle software you are installing and ensure they are installed on the system You can find more information on the components in the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Configuring Storage for Oracle Clusterware You need to perform certain storage configuration tasks before you start Oracle Universal Installer For detailed information on the storage configuration tasks see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Installing Oracle Clusterware on UNIX This section provides you with information about how to use the Oracle Universal Installer to install Oracle Clusterware on UNIX Running the Oracle Universal Installer to Install Oracle Clusterware Complete the following steps to install Oracle Clusterware on your cluster At any time during installation if you have a question about what you are being asked to do click Help in the Oracle Universal Installer page 1 Start the runInstaller command with the ormCluster option from the main directory on the Oracle Clusterware 11g Release 1 11 1 CD ROM This is a separate CD that contains the Oracle Clusterware software When the Oracle Universal Installer displays the Welcome page click Next Oracle Universal Installer displays the Installation Prerequisite Checks page This screen shows the name type and stat
166. ermissions on the ssh authorized keys file on all cluster nodes chmod 600 ssh authorized keys At this point if you use ssh to log in to or run a command on another node you are prompted for the pass phrase that you specified when you created the DSA key Enabling SSH User Equivalency on Cluster Member Nodes To enable Oracle Universal Installer to use the ssh and scp commands without being prompted for a pass phrase follow these steps 1 On the system where you want to run Oracle Universal Installer log in as the Oracle user Enter the following commands exec usr bin ssh agent SSHELL usr bin ssh add At the prompts enter the pass phrase for each key that you generated If you have configured SSH correctly then you can use the ssh or scp commands without being prompted for a password or a pass phrase To test the SSH configuration enter the following commands from the same terminal session testing the configuration of each cluster node ssh nodenamel date ssh nodename2 date Installing Cluster Environments 5 7 Pre installation Tasks for Real Application Clusters on UNIX These commands should display the date set on each node If any node prompts for a password or pass phrase verify that the ssh authorized keys file on that node contains the correct public keys Note The first time you use SSH to connect to a node from a particular system you might see a message stating that the a
167. es Notes a You must enter a value for FROM LOCATION for a complete silent installation You may want to use the command line to set this parameter If the location is a relative path remember that the path should be relative to the location of the oraparam ini file a Make sure that var opt oracle oralnst loc or etc oralnst loc for Linux AIX and Sequent exists The response file for UNIX has a public variable setunixinstallgroup that only becomes effective when it is the first Oracle Universal Installer installation and the oraInst loc file is not already present in the location mentioned above FROM_LOCATION_CD_LABEL This parameter is used in multiple CD installations It includes the label of the compact disk where the file products jar exists You can find the label in the disk label file in the same directory as products jar LOCATION_FOR_DISK2 This parameter is for the complete path to other disks LOCATION FOR DISK2 F Vteststage cd VDisk2 If there are more than two disks more variables will be added as LOCATION FOR DISK3 and so on The CD location for a silent installation is located by two mechanisms 1 Oracle Universal Installer looks for the Location For Disk DiskNumber variable in the response file and uses that location 2 Ifthe variable does not have a value or does not have the required files it looks for the components under Disk DiskNumber stage from products jar 3 6 Or
168. es Government the following notice is applicable U S GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the Programs including documentation and technical data shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement and to the extent applicable the additional rights set forth in FAR 52 227 19 Commercial Computer Software Restricted Rights June 1987 Oracle USA Inc 500 Oracle Parkway Redwood City CA 94065 The Programs are not intended for use in any nuclear aviation mass transit medical or other inherently dangerous applications It shall be the licensee s responsibility to take all appropriate fail safe backup redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes and we disclaim liability for any damages caused by such use of the Programs Oracle JD Edwards PeopleSoft and Siebel are registered trademarks of Oracle Corporation and or its affiliates Other names may be trademarks of their respective owners The Programs may provide links to Web sites and access to content products and services from thir
169. etachHome flag to remove an Oracle home from the Central Inventory You can use detachHome sh bat from an Oracle home For more information see Detaching Oracle Homes from the Central Inventory on page 2 8 Updating the Node List Oracle Universal Installer uses the updateNodeList flag to get the list of nodes and update the inventory xml file If the CRS flag is set to TRUE then the oraclehomeproperties xml file is updated with the Oracle Clusterware home information For more information see Updating the Nodes of a Cluster on page 2 12 Major Entities Created The following major entities are created when you run Oracle Universal Installer 1 4 Oracle Universal Installer and OPatch User s Guide Modes of Installation Inventory Oracle Home The Oracle Universal Installer inventory stores information about all Oracle software products installed in all the Oracle homes on a host provided the product was installed using Oracle Universal Installer The inventory is organized as follows Central Inventory Oracle home inventory For more information on the inventory and the structure of the inventory see Oracle Universal Installer Inventory on page 2 3 An Oracle home is the system context in which the Oracle products run This context consists of the following Directory location where the products are installed Corresponding system path setup Program groups associated with the products insta
170. evel components and only when there is more than one installation type available Note You must enter a value for INSTALL TYPE SELECTED LANGUAGES You can set the languages in which the components will be installed You must use the internal name while specifying the value en English ff French de German ja Japanese For example to specify Japanese SELECTED LANGUAGES ja For more information on the languages Oracle Universal Installer supports see Product Language Selections on page 8 1 Note The SELECTED LANGUAGES variable is only generated when more than one language is available 3 10 Oracle Universal Installer and OPatch User s Guide Installing with a Response File ACCEPT LICENSE AGREEMENT Set this Boolean variable to TRUE if you agree with the license agreement This parameter requires you to set this variable to TRUE to indicate your acceptance of the license agreement normally accepted in the GUI This variable is used only in silent installations Installation cannot continue until this variable is set to TRUE Installing with a Response File Many Oracle software products provide tools and procedures for running Oracle Universal Installer from the command line without displaying Oracle Universal Installer screens or responding to questions during the installation These are called silent installations Instead of prompting you to select a series of installation o
171. f response file 3 4 FROM LOCATION response file parameter 3 6 FROM LOCATION CD LABEL parameter 3 6 H help getting while installing products 4 2 Home Inventory recovering from corruption 2 11 home properties file 2 6 ARU IDs for platforms 2 6 Home Selector 2 12 changing primary Oracle home 2 12 function of 2 12 overview 2 12 IMAGES section of ORAPARAM INI 4 5 INCLUDE response file parameter 3 6 INSTALL TYPE response file parameter 3 10 installation automatic prerequisite checks 4 1 cluster 5 21 insilent mode 5 21 command line options for cluster 5 21 description of process 1 3 from staged HTTP location 4 8 from the Web 4 8 getting help 4 2 media available 4 6 modes 4 5 onacluster 5 20 ORAPARAM NI file 4 3 post tasks for Real Application Clusters 5 22 backing up disk 5 22 configuring Oracle products 5 23 download and install patches 5 22 verfication 5 22 prerequisite check parameters 4 2 prerequisite checks 4 1 response file using 3 11 silent mode prerequisite checks 4 1 standalone prerequisite checks 4 1 TEMP TMP directory 4 7 UNIX special instructions 4 8 installation modes 1 5 clusters 1 6 interactive 1 5 4 5 silent 1 5 4 6 suppressed 1 5 4 6 installing Oracle Clusterware 5 16 Oracle Clusterware in silent mode 5 19 Oracle home on multiple nodes 1 4 Oracle products 4 2 product sofware on a cluster 5 20 interim patches getting 7 2 internation
172. fied is invalid Provide the correct patch location and apply the patch again When I apply a patch I receive an error that reads Exception in thread main java lang NoClassDefFoundError Class Name gt What do I do This may occur because OPatch cannot find the particular class listed in the error which is supposed to be located inside the SORACLE HOME OPatch jlib opatch jar file Check if you have the particular class file there To check this execute the following command the missing class file will be printed out cd SORACLE HOME OPatch jlib jar tf opatch jar Class File Name gt class It is recommended that you contact Oracle support when you encounter this error Another reason might be having done a file transfer of OPatch in non binary mode When I apply a patch I receive an error that reads OPatch cannot find the required command ar from Property file and your PATH What do I do ar isa command OPatch uses This message may appear if OPatch cannot locate this command For more details and a workaround for this problem see OPatch cannot find system commands like fuser make on page 7 46 When I apply a patch I receive an error that reads OPatch cannot find the required command fuser from Property file and your PATH What do I do fuser is a command OPatch uses This message may appear if OPatch cannot locate this command For more details and a workaround for this problem see OPatch cann
173. files Hence standalone OPatch does not support RAC it does not attempt to detect RAC and its utility will not work That is OPatch always runs as opatch apply local OPatch does not support any patch propagation from one node to another node Also standalone OPatch does not support RAC related utilities such as opatch util runRemoteMake invokes relink on remote node Performing patch set operations OPatch does not support patch set operations in either standalone or OUI modes You need to use OUI for patch set operations Standalone Patching Requirements Standalone patching requires the following environment a JRE version 1 4 or later Oracle home without OUI OPatch that supports standalone patching All of the required files and directories must exist for OPatch to function correctly If any of the files are missing OPatch perceives that the patch has not been applied You would then have to take corrective action returning the standalone inventory to a stable state OPatch Utility for Standalone Homes As with OUI based patching you can run the OPatch utility located in the Path to Oracle Home OPatch directory with various commands and options The following string shows the syntax for the OPatch utility Path to OPatch opatch help r eport command option where help Displays the help message for the command a report Prints the actions without executing a command One of the
174. for the first time you are prompted to run a shell script from another terminal window before proceeding with the installation Oracle Universal Installer prompts you to run root sh after installation completes only if the script is required to be run as root before configuration assistants are run Otherwise you are prompted to run root sh as root later Note When running Oracle Universal Installer in silent mode if root shis required prior to configuration assistants Oracle Universal Installer skips configuration assistants during the installation You must run root sh as root and then run the skipped configuration assistants after the silent installation is complete To successfully run the required shell script 1 Leave the Oracle Universal Installer window open and open another terminal window 2 Inthe new terminal window use the substitute user command to log in with root privileges su root 3 Change directory to the Oracle home into which you are currently installing your Oracle software product 4 Run the shell script root sh Installing Products 4 9 Deinstalling Oracle Products 5 When the script is finished and you are returned to the command prompt exit from the new terminal window and return to Oracle Universal Installer to continue the installation Note Do not exit the installation to run the shell script Exiting the installation removes this script You are prompte
175. form All Node Patching in this cluster you bring down systems A B and C apply patches to all these nodes then bring systems A B and C back up again Rolling Patching In Rolling Patching you shut down each node apply the patch then bring up each node again You do this separately for each node until you patch all nodes in the cluster This is the most efficient method of applying an interim patch to a Real Application Clusters setup because there is absolutely no downtime during the application of patches as only one system is brought down at any given time Only some patches can be applied in this mode The type is generally specified in the patch metadata Figure 7 2 shows a basic example of Rolling Patching Figure 7 2 Rolling Patching ROLLING PATCHING Shut Down System A Shut Down System B Shut Down System C Patch System A Patch System B Patch System C Start System A Start System B Start System C System C When you perform Rolling Patching in this cluster the patches are applied in a rolling fashion You initially bring down system A apply a patch to it then bring it back up You do the same thing for systems B and C 7 34 Oracle Universal Installer and OPatch User s Guide About Patch Conflicts Minimum Downtime Patching In Minimum Downtime Patching the nodes are divided into sets Initially you shut down the first set and apply a patch to it After this you shut down the second set You then bring up
176. g Files installActions timestamp 1log is easier to read and can be used to view the operations performed at installation time For more information about the log files generated by Oracle Universal Installer see the online help For more information about using the online help see Getting Help While Installing Oracle Products on page 4 2 4 16 Oracle Universal Installer and OPatch User s Guide 9 Installing Cluster Environments A cluster installation uses Oracle Universal Installer to install software on the nodes of a cluster that are network reachable and bound together by Oracle Clusterware You can use Oracle Universal Installer to extend the Oracle home of a product installation to include additional nodes on the cluster This chapter includes the following sections Oracle Universal Installer and Real Application Clusters General System Installation Requirements for Real Application Clusters Cluster Setup and Pre installation Configuration Tasks for Real Application Clusters Pre installation Tasks for Real Application Clusters on UNIX Pre installation Tasks for Real Application Clusters on Windows Configuring Storage for Oracle Clusterware Installing Oracle Clusterware on UNIX Installing Oracle Clusterware on Windows Adding More Nodes to the Cluster for Mass Deployment Installing Product Software on a Cluster Command Line Options for Cluster Installations UNIX Only
177. g it Tells OPatch how many times it should retry when there is an inventory lock failure Tells OPatch to run the SQL script and SOL procedures if they exist in the given patch For information on SOL and PL SOL patching see Schema Patching Suppresses user interaction and defaults any answers to yes Specifies the custom SQL script that OPatch should run after patching completes For information on SOL and PL SOL patching see Schema Patching Patching Oracle Software with OPatch 7 11 OPatch Utility for OUl based Oracle Homes Table 7 2 Cont Apply Options for OUI Patches Option Description verbose Prints additional OPatch output to the screen as well as to the log file Note Ifa patch consists of SOL changes follow the instructions in the patch readme which is included with the patch to apply the SOL scripts Napply Command for OUI based Oracle Homes This command applies interim patches to several Oracle homes at the same time Syntax Use the following syntax for this command opatch napply patch location id comma separated list of patch IDs delay value force invPtrLoc Path to oraInst loc jdk LOC jre LOC local minimize downtime no bug superset no inventory oh ORACLE HOME retry value silent verbose no relink pre parameters for the pre script in escaped double quotes opatch pre end
178. g the command opatch option silent For more information see OPatch Utility for OUI based Oracle Homes on page 7 8 Before applying a patch I want to know the impact of the patch You can use the command opatch option report For more information see OPatch Utility for OUI based Oracle Homes on page 7 8 What versions of OPatch can I use with Oracle Universal Installer 11 1 Oracle recommends using OPatch version 11 1 from the Oracle home with Oracle Universal Installer 11 1 Also note that OPatch is compatible only with the version of Oracle Universal Installer that is installed in the Oracle home Is Opatch 11 1 backward compatible Can I use OPatch 11 1 to apply 9 2 10 1 and 10 2 patches No OPatch 11 1 is not backward compatible You can use Opatch 11 1 only to apply 11 1 patches When I apply a patch I receive an error that reads as follows OPatchSession cannot load inventory for the given Oracle home Home Location Possible causes are No read or write permission to ORACLE HOMEJ patch storage Central Inventory is locked by another OUI instance No read permission to Central Inventory The lock file exists in ORACLE HOMEJ patch storage The Oracle home does not exist in Central Inventory A 4 Oracle Universal Installer and OPatch User s Guide OPatch What do I do This error may occur because of any one or more of the following reasons a IheORACLE HOME patch storage may not have read wr
179. grade Assistants Database SQL Scripts Database Workspace Manager DBJAVA Required Support Files Enterprise Edition Options There are 10 products installed in this Oracle Home Intermin patches 1 Patch 111000 applied on Mon May 23 19 44 08 IST 2007 Created on 27 Jul 2006 05 43 46 hrs PST8PDT Bugs fixed 111000 Files Touched qmtest o ORACLE HOME lib libserverll a libmapsym so ORACLE HOME lib libmapsym so ins rdbms mk ORACLE HOME rdbms lib ioracle CC CO sO O Or C 0 C C ooo Oo oo O O 0 C Ck x C Cr Xx es a Patching Oracle Software with OPatch 7 15 OPatch Utility for OUI based Oracle Homes oracle xml jaxb orajaxb class ORACLE HOME lib xml jar Patch Location in Inventory home oracle TEST product 11 1 0 db 1 inventory oneoffs 111000 Patch Location in Storage area home oracle TEST product 11 1 0 db 1 patch storage 111000 Jul 27 2006 05 43 46 OPatch succeeded Options Table 7 4 lists the options available for this command Table 7 4 Lsinventory Options for OUI Patches Option Description all Reports the name and installation directory for each Oracle home directory found all nodes Reports the patches installed on the given Oracle home in all nodes of the RAC system It also prints the Oracle binary s size and checksum on all nodes You cannot use this option with the all detail or patch options delay If you specify retry this option tells
180. gue for exiting the Oracle Universal Installer Set to true for exit Specifies if the custom tree page in the Oracle Universal Installer needs to be shown Use this page to select de select dependencies This page appears only in the custom installation type C 4 Oracle Universal Installer and OPatch User s Guide Command line Variables Available in Oracle Universal Installer Table C 2 Cont Command Line Variables in Oracle Universal Installer Command Line Variable Description SHOW Specifies if the components location page in the Oracle Universal COMPONENT Installer needs to be shown This page appears if there are products LOCATIONS PAGE SHOW NODE SELECTION PAGE SHOW SUMMARY PAGE SHOW INSTALL PROGRESS PAGE SHOW REQUIRED CONFIG TOOL PAGE SHOW CONFIG TOOL PAGE SHOW RELEASE NOTES SHOW END OF INSTALL MSGS SHOW END SESSION PAGE SHOW XML PREREQ_ PAGE NEXT_SESSION NEXT_SESSION_ ON_FAIL NEXT_SESSION_ RESPONSE LOCATION_FOR_ DISK DEINSTALL_LIST whose installed directory can be changed Set the value to false to prevent users from specifying an alternate directory Specifies if the node selection page should be shown Specifies if the summary page in the Oracle Universal Installer needs to be shown The summary page shows the list of components that need to be installed in this session Specifies if the installation progress page in the Oracle Universal Insta
181. his guide use u01 for the mount point directory However you could choose another mount point directory such as oracle or opt oracle for example oracle sw owner is the operating system user name of the Oracle software owner for example oracle You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations If different operating system users install Oracle software on the same system each user must create a separate Oracle base directory The following example Oracle base directories could all exist on the same system u01 app oracle u01 app orauser opt oracle app oracle Regardless of whether you create an Oracle base directory or decide to use an existing one you must set the ORACLE BASE environment variable to specify the full path to this directory Note The Oracle base directory can be on a local file system or on an NFS file system on a certified NAS device Do not create the Oracle base directory on an OCFS version 1 file system Oracle Inventory Directory The Oracle Inventory directory oraInventory stores an inventory of all software installed on the system It is required by and shared by all Oracle software installations on a single system The first time you install Oracle software on a system Oracle Universal Installer prompts you to specify the path to this directory If you are installing the software on
182. ho install Oracle software by understanding the system requirements features and key concepts of Oracle Universal Installer This chapter includes the following sections System Requirements Key Features Utilities Actions Performed by the Utilities Major Entities Created Modes of Installation System Requirements The minimum system requirements for Oracle Universal Installer are as follows Key Features Java Runtime Environment JRE Automatically installed with Oracle Universal Installer on most platforms Check the Release Notes or installation guide of the products that you are installing for the required version Memory Requirements Memory requirements vary depending on the number of components installed Check the Release Notes or installation guide for the products that you are installing for details 32 MB is the minimum recommended on all platforms Disk Space Requirements Oracle recommends at least 60 MB for Oracle Universal Installer files on Windows platforms and 70 MB on UNIX UNIX requires more memory because of the difference in JRE sizes for the platforms You may need up to 1 MB for the related inventory files When you run Oracle Universal Installer from an NFS mounted user home especially for Linux execute the quota command to check the space availability Never perform an installation on a user home for which space is allocated based on quota Oracle Universal Installer 112 Release 1 11
183. hooting B 5 REGISTRATION KEY parameter in ORAPARAM INI 4 5 REGISTRATION URL parameter in ORAPARAM INI 4 5 REMOVE HOMES parameter 3 8 removing Central Inventory 2 9 on UNIX platforms 2 9 on Windows platforms 2 9 Oracle homes 2 2 4 10 reponse file optional parameters 3 12 requirements diskspace 1 1 JRE 1 1 memory 1 1 response file ACCEPT_LICENSE_AGREEMENT parameter 3 11 CLUSTER_NODES parameter 3 9 creating with record mode 3 3 definition 3 1 DEINSTALL_LIST parameter 3 9 DEPENDENCY LIST parameter 3 9 format 3 4 FROM LOCATION response file parameter 3 6 FROM LOCATION CD LABEL parameter 3 6 general format comments 3 5 headers 3 5 values 3 4 INCLUDE parameter 3 6 INSTALL TYPE parameter 3 10 installing by using 3 11 location 3 2 LOCATION FOR DISK2 parameter 3 6 modifying 3 2 NEXT SESSION parameter 3 7 NEXT SESSION ON FAIL parameter 3 7 NEXT SESSION RESPONSE parameter 3 7 OPTIONAL CONFIG TOOLS parameter 3 9 ORACLE HOME parameter 3 7 ORACLE HOME NAME parameter 3 7 parameters 3 5 record mode using 3 3 REMOVE HOMES parameter 3 8 RESPONSEFILE VERSION parameter 3 6 Index 6 RESTART SYSTEM parameter 3 7 sample D 1 SELECTED LANGUAGES 3 10 setting variables from command line 3 12 SHOW COMPONENT LOCATIONS PAGE parameter 3 7 SHOW CUSTOM TREE parameter 3 7 SHOW DEINSTALL CONFIRMATION parameter 3 9 SHOW DEINSTALL PROGRESS parameter 3 9 SHOW END SESSION PAGE parameter 3 7 SHOW E
184. hosts file on UNIX and sSystemRoot system32 drivers etc hosts on Windows During Oracle Clusterware installation the information you enter as the private IP address determines which private interconnects are used by Real Application Clusters database instances One public IP address for each node to be used as the Virtual IP address for client connections and for connection failover This public Virtual IP address VIP must be associated with the same interface name on every node that is part of your cluster Additionally the IP addresses that you use for all of the nodes that are part of a cluster must be from the same subnet If you have a domain name server DNS register the host names for the VIP with DNS The Virtual IP address should not be in use at the time of the installation because this is a Virtual IP address that Oracle manages a One public fixed host name address for each node typically assigned by the system administrator during operating system installation If you have a DNS register both the fixed IP and the VIP address with DNS If you do not have DNS you must make sure that both public IP addresses are in the node host file Software Requirements for Real Application Clusters Setup Each node in a cluster requires a supported interconnect software protocol to support Cache Fusion and to support Oracle Clusterware polling Your interconnect must be certified by Oracle for your platform You should also have a Web
185. ide the default value stage Components oracle swd oui version 1 DataFiles Expanded Points to the location used for silent mode This parameter is optional If DISTRIBUTION TRUE then Oracle Universal Installer computes this value using the OUI_VERSION parameter Use this parameter if you want to override the default value stage Components oracle swd oui core lt version gt 1 DataFiles Expanded Set the version of Oracle Universal Installer that you are using You must properly set the version for the BOOTSTRAP to work Set to FALSE to suppress the display of the version of top level components in the Installation Type dialog during installation Set these to increase the initial heap threshold for JRE For example mx48m Location of the default Oracle home The default name for the Oracle home Use this parameter only if the installation occurs on a host with no previous Oracle installations Lists directories that you do not want to browse which are typically large directories that require a long time to view For example net nfs 4 4 Oracle Universal Installer and OPatch User s Guide Installing Oracle Products Table 4 2 Cont Parameters in oraparam ini Section Parameter Description NLS ENABLED BOOTSTRAP BOOTSTRAP SIZE USE BUILD NUMBER APPLTOP STAGE REGISTRATION URL REGISTRATION KEY IMAGES Set to TRUE for Oracle Universal Installer to enable NLS supp
186. if those nodes are up and running and if they are properly network configured If either the inventory or the Oracle home is not writable check for the appropriate permissions on the remote nodes for these directories Cluster Installation In a typical cluster installation when clusterware is present Universal Installer installs the Oracle software onto the node on which Oracle Universal Installer is running then propagates the Oracle home from the local node installation to the other nodes that are part of the installation Then Universal Installer runs attachHome on the remote nodes to update the inventory After this you need to run orainstRoot sh if required and root sh on the local and remote nodes After the scripts are run the configuration steps are executed If the cluster is Cluster File System CFS or Network File System NFS mounted Oracle Universal Installer does not propagate the Oracle home to other nodes as files are shared across nodes and the installation will exist on the shared disk Note For cluster installations you must run oraInstRoot sh on each node of the cluster to set up the inventory Cluster Installation in Silent Mode For Real Application Clusters installation you can specify the 1ocal flag CLUSTER NODES REMOTE NODES and LOCAL NODE session variables to indicate the nodes on which the installation needs to be done When you use the local flag in a cluster installation it me
187. iguration Tools page shows the list of optional configuration tools that are part of this installation and the status of each tool including detailed information on why the tool has failed SHOW ROOTSH CONFIRMATION Set to TRUE if you need to show the Confirmation dialog asking to run the root sh script in the installer This variable is valid only on UNIX platforms SHOW ROOTSH CONFIRMATION TRUE SHOW SPLASH SCREEN Set to TRUE if the initial splash screen in the installer needs to be shown SHOW SPLASH SCREEN TRUE SHOW SUMMARY PAGE The Summary page can be suppressed by setting this value to FALSE SHOW WELCOME PAGE Set to TRUE if you need to show the Welcome page in the installer SHOW WELCOME PAGE FALSE SHOW RELEASE NOTES Set this parameter to TRUE if you want the release notes for this installation to be shown at the end of the installation A dialog box lists the available release notes Note thatthe SHOW END SESSION parameter must be set to TRUE before you can use this parameter TOPLEVEL COMPONENT This parameter is the name of the component products and the version as a string list You must enter a value for TOPLEVEL COMPONENT Usually the components are represented with a pair of strings the first one representing the internal name the second representing the version For example RDBMS 11 1 may be represented as oracle rdbms 11 1 0 0 0 UNIX_GROUP_NAME This parameter is the UNIX group name to be
188. imestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat On UNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt If the files are properly patched but the information is not updated in the inventory execute the following command SORACLE HOME OPatch opatch apply no sysmod Path To Patch Ensure that the patch has been applied and recorded properly in the inventory by executing the following command SORACLE HOME OPatch opatch lsinventory detail When you press Ctrl C during the application or roll back of a patch and execute opatch Isinventory it does not return the details of the patch applied or rolled back Cause This may be because OPatch might have stopped the application or rollback of the patch on pressing Ctrl c Patching Oracle Software with OPatch 7 41 Problem Resolution Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command if it is available For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt When
189. information about the OPatch utility to check for updates and to get the latest versions go to OracleMetaLink at http www oracle com support metalink index html Prerequisite Checks for OPatch Before you invoke OPatch perform the prerequisite checks described in the following sections Checks for Single Instances and Real Application Clusters Check ORACLE HOME and Environment Variable OPatch verifies if the Oracle home is present You must ensure that the ORACLE HOME environment variable is set to the Oracle home of the product you are trying to patch Check the respective vendor documentation for details to set the environment variable Check for JRE OPatch requires JRE version 1 4 or higher to work properly Check for System Space When OPatch processes the script for the installation of a patch it simultaneously generates a Rollback script and saves a copy of every file edited or deleted during the patching OPatch also backs up the inventory information Consequently Oracle recommends that you have sufficient system space to accommodate the patch and the backup information Check for Oracle Universal Installer and OPatch Version Compatibility OPatch 11 1 requires Oracle Universal Installer 11 1 or higher to work properly If the Oracle Universal Installer version is less than what OPatch requires OPatch errors out Check for Patch Applicable on Operating System OPatch detects if a particular patch is applicable fo
190. information for time usage record destinationFile Path For record mode operation information is recorded in the destination file path removeallfiles For removing the home directory after deinstallation of all the components removeAllPatches Remove all interim patches from the home silent For silent mode operations the inputs can be a response file or a Installing Products 4 13 Running Oracle Universal Installer After Installation list of command line variable value pairs updateNodeList For updating node list for this home in the OUI inventory waitforcompletion For windows setup exe will wait for completion instead of spawning the java engine and exiting nobackground Do not show background image noclusterEnabled No cluster nodes specified noconsole For suppressing display of messages to console Console is not allocated nowarningonremovefiles To disable the warning message before removal of home directory nowait For windows Do not wait for user to hit Enter on the console after the task install etc is complete formCluster To install the Oracle clusterware in order to form the cluster remotecp Path Unix specific option Used only for cluster installs specifies the path to the remote copy program on the local cluster node remoteshell Path Unix specific option Used only for cluster installs specifies the path to the remote shell program on the local cluster node Command Line Variables
191. information in oraclehomeproperties xml overrides the information in inventory xml This file is located here SORACLE HOME inventory ContentsXML oraclehomeproperties xml The following example shows the Oracle home property file lt GUID gt 893051798 356758136 lt GUID gt lt HOME CRS T gt ARU PLATFORM INFO ARU ID246 ARU ID ARU ID DESCRIPTION gt Linux x86 ARU ID DESCRIPTION ARU PLATFORM INFO CLUSTER INFO LOCAL NODE NAME stacg30 gt NODE LIST NODE NAME stacg34 gt lt NODE NAME stacg30 gt lt NODE LIST2 CLUSTER INFO Table 2 2 lists the ARU IDs for some platforms Table 2 2 ARU IDs for Platforms Platform ARU ID HPUX 64 bit 59 IBM 5L 212 Linux 32 bit 46 Solaris 32 bit 453 Solaris 64 bit 23 Windows XP 912 Other Folders Table 2 3 lists the other folders you can find in the Oracle home inventory 2 6 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Inventory Table 2 3 Other Folders in the Oracle Home Inventory Folder Name Description Scripts Contains the scripts used for the cloning operation ContentsX ML Contains the details of the components and libraries installed Templates Contains the template files used for cloning oneoffs Contains the details of the one off patches applied Creating the Central Inventory Oracle Universal Installer enables you to set up the Central Inventory on a clean host or register an
192. ing disk are created in the data file directory Format one logical drive for software storage In this case the Oracle Universal Installer creates one cluster file system for the Oracle home and requires two additional partitions one for the OCR and one for the voting disk If you select this option you must have already configured the partitions before proceeding with the installation These partitions are stamped with ocrcfg for the OCR and votedsk for the voting disk Format one logical drive for data file storage In this case the Oracle Universal Installer creates one cluster file system for the database files which is also used to store the OCR and voting disk Do not format any logical drives In this case the Oracle Universal Installer requires two partitions one for the OCR and one for the voting disk If you select this option you must have already configured the partitions before proceeding with the installation These partitions are stamped with ocrcfg for the OCR and votedsk for the voting disk Click Next after making your selection in the Select Disk Formatting Options page The next page that the Oracle Universal Installer displays depends on your selection on the Select Disk Formatting Options page as described in the following step Installing Cluster Environments 5 17 Installing Oracle Clusterware on Windows 7 Ifyou selected the Format two logical drives for data and software storage optio
193. ing sections Checking Prerequisites Before Installation Installing Oracle Products a Deinstalling Oracle Products Running Oracle Universal Installer After Installation About Oracle Universal Installer Log Files Checking Prerequisites Before Installation Before installation Oracle Universal Installer checks the environment to see whether it meets the requirements for successful installation Early detection of problems with the system setup reduces the chances of encountering problems during installation for instance problems with insufficient disk space missing patches inappropriate hardware and so on Oracle Universal Installer is required to perform all prerequisite checks defined for the installation before installing any software whether they are Oracle Universal Installer specific tests or tests defined for a specific product Specific prerequisite checks are defined for each operating system on which Oracle Universal Installer runs All prerequisite check parameters must be defined in the oraparam ini file or another ini file that you define All the results are logged in the install Actions timestamp 10g file You can perform prerequisite checking in the following ways Automatically Checks are performed automatically when you run the Oracle Universal Installer executable during an installation Simply run Oracle Universal Installer to perform all predefined prerequisite checks Silent Mode
194. ing the location specified in the oraparam ini files JRE LOCATION parameter If Oracle Universal Installer cannot find the JRE specified an error is returned Command Line Arguments Following is the output from the runInstaller help command which gives you the full list of command line options and their descriptions as well as command line variables usage Usage runInstaller options lt CommandLineVariable Value gt Where options include clusterware oracle crs lt crs version gt Version of Cluster ready services installed crsLocation lt Path gt Used only for cluster installs specifies the path to the crs home location Specifying this overrides CRS information obtained from central inventory invPtrLoc lt full path of oraInst loc gt Unix only To point to a different inventory location The orainst loc file contains inventory loc location of central inventory inst group jreLoc location Path where Java Runtime Environment is installed OUI cannot be run without it logLevel level To filter log messages that have a lesser priority level than level Valid options are severe warning info config fine finer finest basic general detailed trace The use of basic general detailed trace is deprecated paramFile location of file Specify location of oraparam ini file to be used by OUI responseFile Path Specifies the response file and path to use sourceLoc location of pro
195. ing the standalone OPatch User Input Enter the following command opatch lsinventory detail OPatch Response 1 OPatch detects that this is a standalone Oracle home 2 OPatch looks for the standalone inventory file 3 OPatch prints out a list of installed interim patches as well as files affected by each interim patch Patching Operations The following tables explain the purpose of the use case along with preconditions and the process that occurs during the patching process Table 7 15 Applying an Interim Patch Case 1 Use Case Category Description Purpose Apply an interim patch on a standalone Oracle home Preconditions SORACLE HOME is set and the Oracle home has been patched using the standalone OPatch The patch has been downloaded User Input Enter the following command opatch apply patch_loc 123451 OPatch Response 1 OPatch detects that this is a standalone Oracle home 2 OPatch looks for the standalone inventory file and checks for conflicts 3 OPatch performs an automatic rollback if there are conflicting patches 4 OPatch applies a new patch to the home 5 OPatch updates its standalone inventory Patching Oracle Software with OPatch 7 29 Standalone Patching Table 7 16 Applying an Interim Patch Case 2 Use Case Category Description Purpose Preconditions User Input OPatch Response Apply an interim patch on a standalone Oracle home that exists within another OUI based O
196. intained However you cannot install 64 bit software in a 32 bit home and vice versa Installing from Multiple CD ROMs If you are creating a multiple CD installation on UNIX you might need to launch runInstaller in the background using the following command runInstaller amp By launching runInstaller in the background you can change your current directory after you launch Oracle Universal Installer allowing you to eject the CD It may also help to launch runInstaller as a foreground process from a different directory You may want to create a shell script that launches Oracle Universal Installer in the background and then exits If you choose to create a shell script remember to also pass all parameters that you passed to the shell script to runInstaller in the event that you want to install silently using a response file TEMP TMP Directory On both UNIX and Windows installations temporary copies of Oracle Universal Installer and JRE are placed in the TEMP or TMP directory in a subdirectory named OraInstall lt timestamp gt so that these applications can be launched when you change CD ROMs Note that temporary files are created for single CD installations as well On both UNIX and Windows Oracle Universal Installer looks for TEMP then TMP If neither is set Oracle Universal Installer defaults to tmp on UNIX and c temp on Windows Note The TEMP TMP directory should not be a cluster file system or a shared
197. inventory SORACLE HOME inventory The following example shows how to unarchive and decompress the source for various platforms To unarchive mkdir Destination oracle home cd Destination oracle home zcat temp dir archiveName tar Z tar xpf for hpux zcat temp dir archiveName tar Z tar xBpf for remaining UNIX based systems You must have Perl 5 6 or higher installed on your system to enable cloning Also ensure that you set the path environment variable to the correct Perl executable Note The cloned home and source home will not be identical in size because the cloned home will have additional files created during the cloning operation Locating and Viewing Log Files The cloning script runs multiple tools each of which may generate its own log files However the following log files that OUI and the cloning scripts generate are the key log files of interest for diagnostic purposes Central Inventory logs cloneActions timestamp log Contains a detailed log of the actions that occur during the OUI part of the cloning Central Inventory logs oralnstall timestamp err Contains information about errors that occur when OUI is running Central Inventory logs oralnstall timestamp out Contains other miscellaneous messages generated by OUI Cloning Oracle Software 6 3 Cloning an Oracle Database 11 1 Oracle Home S ORACLE HOME clone logs clone timestamp log Contains a detailed log
198. ite permissions Ensure that you provide read write permissions for this folder and apply the patch again Another Oracle Universal Installer instance may be running Stop the instance and try applying the patch again The Central Inventory may not have read permission Ensure that you provide read permission to the Central Inventory and then apply the patch again IheORACLE HOME patch storage directory might be locked If this directory is locked you will find a file named patch locked inside this directory This may occur because of a previously failed patch installation To remove the lock restore the Oracle home and remove the patch locked file from the ORACLE HOME patch storage directory The Oracle home may not be present in the Central Inventory This may occur because of a corrupted or lost inventory or the inventory may not be registered in the Central Inventory For more information see Diagnosing and Recovering from Central Inventory Corruption on page 2 10 Iam trying to install a patch on Windows but OPatch is not reading the complete patch location The patch location is c My Patches 300100 OPatch does not support paths with spaces The solution is to move the patch to a path that does not have spaces and then provide that location to OPatch OPatch does not work if there are spaces in paths of the Oracle home the patch location and JRE JDK locations What if I want to just update the inventory with
199. ity new_ node is the name of the new node and remote_port is the value from the output of the previous step racgons add config new node Remote Port Execute the following command to get the interconnect information You can use this information in the next step CRS HOME bin oifcfg iflist p Execute the oi c g command as follows oifcfg setif global interface name subnet public lt inteface_ name gt lt subnet gt cluster interconnect lt interface_name gt lt subnet gt public inteface name subnet cluster interconnect Note Oracle Clusterware cloning can only be performed in silent mode Cloning Oracle RAC Software on UNIX and Linux System Based Environments Complete the following steps to clone Oracle Database with RAC software on UNIX and Linux systems 1 If you do not have a shared Oracle Database home tar the Oracle RAC home from the existing node and copy it to the new node Assume that the location of the destination Oracle RAC home on the new node is SORACLE HOME Otherwise skip this step Note For more information on archiving see Source Preparation Phase Unarchive the home on the new nodes In the case of shared homes unarchive the home only once on the nodes Note For more information on unarchiving see Cloning Phase On the new nodes go to the CRS_HOME oui bin directory and run the following command where new node2
200. k Deinstall Products on the Welcome screen The Inventory panel appears Select the product s you want to remove from the Contents tab of the Inventory panel and click Remove You can also remove Oracle homes in the same manner After you have removed an Oracle home you can reuse its name and location to install other products The Remove Confirmation Dialog appears asking if you want to remove the products and their dependent components Click Yes 4 10 Oracle Universal Installer and OPatch User s Guide Deinstalling Oracle Products Oracle Universal Installer warns you of any product dependencies that might cause problems if particular products are removed and prompts you to confirm the deinstallation Pay special attention to the full list of products being removed before proceeding Oracle Universal Installer computes this list based on the dependencies of each component Note You can also remove products by using the Installed Products button on Oracle Universal Installer as long as you perform this action before making your selection of products to install Deinstalling Top level Products That Have Dependents A top level component is the most important component of an installation It is the installable product you see at the first installation screen You can only install one top level component for each installation session When you select a specific component for removal Oracle Universal Installer ana
201. ke NullPointers from libraries Check if the temp OraInstall lt timestamp gt err has any stack trace You will need to call support to debug the staging area The following tips may help you to troubleshoot problems Make sure the correct version of the JRE is specified in the PATH If Java cannot run applications from a Sun machine on an NCD X terminal Oracle Universal Installer does not start remove the following file SJAVA HOME lib font properties If you are deleting an Oracle home manually without using Oracle Universal Installer the products remain registered with Oracle Universal Installer You must then simulate a de install so that all Oracle Universal Installer references are removed Ifthe installation is canceled Products will not be registered with Oracle Universal Installer Some files may have been copied depending on when you issued the cancellation X terminal emulators that were tested with Oracle Universal Installer are listed in the following sections Exceed There is a known compatibility issue that Hummingbird has identified to be a problem with Exceed You can fix it by going into XConfig Screen Definition Screen 0 and changing Window Manager from Default to Native to Native See Figure B 1 to see the proper setup B 4 Oracle Universal Installer and OPatch User s Guide Other Tips Figure B 1 Setting Exceed s Window Manager to Native Screen 0 E xj n
202. l jre LOC oh lt LOC gt get component get os get date get base bug is portal patch is rolling patch is online patch 7 16 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Options has sql Patch Location Table 7 5 lists the options available for the Query command Table 7 5 Query Options Option Description all get base bug get component get date has sql is online patch is portal patch is rolling patch oh Patch Location Retrieves all information about a patch This is equivalent to setting all available options Retrieves bugs fixed by the patch Retrieves components the patch affects Retrieves the patch creation date and time Indicates true if the patch has SOL related actions Otherwise the option is false For information on SOL and PL SOL patching see Schema Patching Indicates true if the patch is an online patch Otherwise the option is false Indicates true if the patch has portal actions Otherwise the option is false Indicates true if the patch is a rolling patch Otherwise the option is false Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE HOME environment variable Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch locati
203. l address of the new node and central inventory locationis the location of the Oracle Central Inventory perl clone pl ORACLE HOME CRS HOME ORACLE HOME NAME Oracle home name On StorageTypeVDSK 2 On storageTypeOCR 2 O sl tableList new node new node priv new node vip O noConfig O INVENTORY LOCATION central inventory location If you have a shared Oracle Clusterware home append the cfs option to the command example in this step and provide a complete path location for the cluster file system Ensure that n storageTypeOCR and n storageTypeVDSK has been set to 2 for redundant storage Ensure that this value is set to 1 for non redundant storage In this case the mirror locations will also have to be specified On the new node go to the directory that contains the central Oracle inventory Run the orainstRoot sh script to populate the file etc oraInst 1oc with Cloning Oracle Software 6 7 Creating an Oracle Real Application Cluster Environment using Cloning information about the Central Inventory location On the new node go to the CRS HOME directory and run root sh This starts the Oracle Clusterware on the new node Determine the remote port to use in the next step by running the following command from the CRS_HOME opmn conf directory cat ons config grep remoteport On the new node run the following command from the CRS_HOME bin directory where racgons is the Oracle RAC Notification Service Util
204. le Home Directory Structure and Content Content configuration Assistants binaries for all products interMedia Text cartridge initsid ora 1ksid install related files Oracle product libraries Java classes Spatial cartridge Xerox Stemmer for interMedia Text cartridge Net8 NES run time loadable data common files for all products data gatherer Parallel Server Manager Components core libraries data cartridges Oracle TRACE PL SOL precompilers 2 14 Oracle Universal Installer and OPatch User s Guide Home Selector Available on Win32 Platforms Table 2 6 Cont Sample Oracle Home Directory Structure and Content Directory Content rdbms server files and libraries required for the database slax SLAX parser sqlplus SQL Plus Managing Oracle Homes 2 15 Home Selector Available on Win32 Platforms 2 16 Oracle Universal Installer and OPatch User s Guide 3 Customizing and Creating Response Files This chapter introduces you to Oracle Universal Installer s availability of response files for silent and suppressed installations This chapter also describes how to modify or create a response file so you can customize and standardize the installation of Oracle products in your organization This chapter is organized into the following sections About Response Files Modifying a Response File Creating a Response File With Record Mode Response File Format Installing with a Re
205. le Universal Installer from any location after setting the PATH environment variable I receive an error that reads Could not read any NLS message catalogue What do I do Oracle Universal Installer needs some files in the directory where the runInstaller UNIX or setup exe Windows is running So when you invoke runInstaller UNIX or setup exe Windows you should invoke it from the directory where this command is present or you must specify the complete path I have lost my Central Inventory but have a valid Oracle home s What do I do Oracle Universal Installer allows you to set up the Central Inventory or register an existing ORACLE HOME with the Central Inventory in case of inventory corruption or loss You need to execute the command with the attachHome flag For more information see the section Creating the Central Inventory on page 2 7 I want to deploy multiple Oracle home s from an existing Oracle home How do I do this Oracle Universal Installer creates Oracle homes during Oracle software installation To deploy multiple Oracle homes using an existing one you need to clone the Oracle home For more information on cloning and mass deployment see Chapter 6 Cloning Oracle Software I have lost my Oracle home inventory comps xml What can I do Oracle recommends backing up the inventory when an Oracle home is installed or removed Ensure that you back up the comps xm1 that has the latest time stamp For
206. ler to install software on the nodes of a cluster that are network reachable and bound together by Oracle Clusterware You can use Oracle Universal Installer to extend the Oracle home of a product installation to include additional nodes on the cluster You need to install Oracle Clusterware for a cluster installation For more information on cluster installations see Chapter 5 Installing Cluster Environments 1 6 Oracle Universal Installer and OPatch User s Guide 2 Managing Oracle Homes This chapter contains the following sections Introduction to Oracle Homes Installing an Oracle Product Removing Oracle Homes Determining the Default Oracle Home Multiple Oracle Homes Oracle Universal Installer Inventory Home Selector Available on Win32 Platforms Introduction to Oracle Homes The Oracle Universal Installer supports the installation of several active Oracle homes on the same host An Oracle home is a directory into which all Oracle software is installed This is pointed to by an environment variable The Oracle home consists of the following Directory location where the products are installed Corresponding system path setup Program groups associated with the products installed in the home where applicable Services running from the home Installing an Oracle Product When you install an Oracle product an Oracle home is created To install the product and create the Oracle home perform the following ste
207. lete the deinstallation by removing the Oracle Clusterware software using the following procedure 1 Run the command CRS HOME install rootdelete sh to disable the Oracle Clusterware applications running on the cluster node The rootdelete sh script requires three arguments If you are running this command on a remote node of the cluster use remote as the first argument otherwise use local as the first argument If the ocr loc file is on a shared file system use sharedvar Otherwise use nosharedvar as the second argument If the Oracle Clusterware home is on a shared file system use sharedhome otherwise use nosharedhome as the third argument Repeat this step on each node of the cluster from which you want to deinstall Oracle Clusterware 2 Runthescript CRS HOME install rootdeinstall shon a local node to remove the OCR You only need to run this script once 3 Start Oracle Universal Installer In the Welcome page click Deinstall Products to display the list of installed products Select the Oracle Clusterware home to deinstall Deinstalling Oracle Clusterware from a Windows Environment Deinstall each Oracle product Real Application Clusters home by running the procedure in the previous section Then complete the deinstallation by removing the Oracle Clusterware software using one of the following procedures Installing Cluster Environments 5 25 Deinstalling Real Application Clusters Software Deinstalling Oracle Clusterwa
208. lities actions performed 1 3 for software deployment 1 2 V variable lookup order response file 3 4 values for response file 3 5 variable NLS ENABLED 8 1 variable SELECTED LANGUAGES 8 1 VD Voting Disk Location location option 5 15 verifying the Central Inventory operation 2 8 Version command for OUI based homes 7 22 for standalone OPatch 7 28 Virtual Protocol Configuration Assistant VIPCA 6 10 6 15 Ww Web installation 4 8 Windows Central Inventory pointer file 2 4 hardware and software certification 5 13 hardware requirements 5 14 IP address requirements 5 14 network requirements 5 14 pre installation tasks for Real Application Clusters 5 13 software requirements 5 14 Windows directory structure for 2 13 X XML format OUI inventory and 2 3 Index 7 Index 8
209. lled in that home where applicable a Services running from that home For more information on Oracle homes see Chapter 2 Managing Oracle Homes Modes of Installation You can run the Oracle Universal Installer in the following modes Interactive Mode You can use the interactive mode to walk through the installation by providing information in the dialogs when prompted This method is useful when installing a small number of products in different setups on a small number of hosts Suppressed Interactive Mode Silent Mode You can use this mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs This is useful when an installation has a common set of parameters that can be captured in a response file in addition to the custom information that you must enter manually You can use this mode to bypass the Graphical User Interface GUI and supply the necessary information in a response file This method is useful when installing the same product multiple times on multiple hosts By using the response files you can also automate the installation of a product for which you know the installation parameters For more information on silent installation see Chapter 3 Customizing and Creating Response Files Introduction to Oracle Universal Installer 1 5 Modes of Installation Cluster Mode A cluster installation uses Oracle Universal Instal
210. ller needs to be shown This page shows the current status in the installation Specifies if the required config assistants page in Oracle Universal Installer needs to be shown This page shows the list of required configuration assistants that are part of this installation It shows the status of each assistant including any failures with detailed information on why it failed Specifies if the config assistants page in Oracle Universal Installer needs to be shown This page shows the list of configuration assistants that are part of this installation and are configured to launch automatically It shows the status of each assistant including any failures with detailed information on why it failed Specifies if the release notes of this installation need to be shown at the end of the installation This dialog can be launched from the End of Installation page and shows the list of release notes available for the products just installed This also requires the variable SHOW_END_ SESSION_PAGE variable to be set to true Specifies if the text on the end of the installation screen is to be shown The text is always available under Oracle Home install readme txt Specifies if the end of session page in Oracle Universal Installer needs to be shown This page shows if the installation is successful or not Specifies whether or not to show the prereq page Specifies if you want users to go back to the File Locations page for another installa
211. lts to classes12 jar The value specified for this should be packaged with OUI and should be relative to OUI expanded stagedir gt jlib THIN JDBC FILENAME classes12 jar JRE_OSDPARAM is to set OS dependent param for JRE mainly for native VM in 1 3 1 JRE_OSDPARAM is optional and should be set to native for the JRE s that support native VM mainly for Unix platforms in JRE 1 3 1 For JRE 1 4 1 this should be set to empty or the type of VM that is 3 E For w Hy D UU o A U UC supported client server The default value is native in UNIX platforms that supports native VM Unix supporting native JRE OSDPARAM native Unix NOT supporting native and 1 4 1 JRE OSDPARAM RE OSDPARAM LUSTERWARE oracle crs 11 1 0 0 0 RUN_OUICA specifies the batch script name that needs to be run The script is ouica bat for win32 and ouica sh for solaris If the value is not specified then the OUICA script is not run UN OUICA ouica sh Dt dE HQ Cj Certified Versions Linux redhat 2 1 UnitedLinux 1 0 redhat 3 SuSE 9 Linux redhat 2 1 optional Sample Components File The components file contains details of all the components as well as patchsets or interim patches installed in the Oracle home lt xml version 1 0 standalone yes gt lt Copyright c 2007 Oracle Corporation All rights Reserved gt lt Do not modify the contents of this file by hand gt
212. luster Use the formCluster flag for Oracle Clusterware installations to specify the cluster Note that when you specify the silent flag but no values are specified to a particular variable in a dialog the installer stops The success or failure of the installation when you specify this flag is generated as follows a Ina filenamed silentInstall lt timestamp gt log for hosts without an Oracle inventory This file is generated in the tmp directory on UNIX and the directory specified by the variable TEMP on Windows platforms Inthe inventory logs directory for hosts that already had an inventory Note Using the nowelcome option with the silent option is unnecessary since the Welcome screen does not appear when you use the silent option Setting Response File Variables From the Command Line With Oracle Universal Installer 2 1 and higher you can specify the value of certain variables when you start Oracle Universal Installer from the command line Specifically you can specify session and component variables For specific information about the format and organization of response files see Modifying a Response File on page 3 2 When you specify the value of a variable on the command line that value overrides the value of the variable if it is defined in the response file Specifying the Value of a Session Variable To specify the value of a session variable use the following command syntax runInstaller ses
213. lyzes the dependency information to determine if other components should be removed along with it Generally if a component is selected for removal the following components are removed with it All components that have a required dependency on the selected component Dependents of the selected component that have no other dependents A dependent is a component on which the top level component dependent has a dependency Silent Deinstallation Not only can you perform command line installations as described in section Installing with a Response File on page 3 11 you can also perform command line deinstallations A command line deinstallation enables you to remove Oracle products or Oracle homes from your system without using the Oracle Universal Installer graphical user interface You can choose to display no dialog boxes or prompts or you can selectively avoid displaying certain dialog boxes that are normally used during a deinstallation Immediately Displaying the Inventory Dialog Box Use the following commands to immediately display the Inventory dialog box which allows you to select items for removal without navigating the Oracle Universal Installer startup screen setup exe deinstall on Windows runInstaller deinstall on UNIX Hiding the Inventory Dialog Box If you want to hide the inventory dialog box during a deinstallation you can specify the products to be removed in the DEINSTALL LIST parameter of the re
214. m the Central Inventory This is equivalent to selecting an Oracle home and clicking Deinstall in the GUI The syntax is as follows runInstaller deinstall ORACLE HOME LOCATION OF ORACLE HOME gt REMOVE _ HOMES LOCATION OF ORACLE HOME TO BE REMOVED You can also use the removeallfiles flag with the REMOVE HOMES variable to completely deinstall the components remove the Oracle home from the Central Inventory and delete the Oracle home directory The syntax is as follows runInstaller deinstall ORACLE HOME LOCATION OF ORACLE HOME gt REMOVE _ HOMES LOCATION OF ORACLE HOME TO BE REMOVED removeallfiles For detailed instructions on deinstalling an Oracle product see the respective Oracle product installation guide Deinstalling Oracle Product Software on Windows 5 24 The following steps describe how to use Oracle Universal Installer to remove Oracle software from an Oracle home on Windows systems Note Always use Oracle Universal Installer to remove Oracle software Do not delete any Oracle home directories without first using Oracle Universal Installer to remove the software 1 Stop all the Oracle services running in this Oracle home 2 Start Oracle Universal Installer from the Start menu select Programs then ORACLE HOME NAME then Oracle Installation Products then Oracle Universal Installer The Welcome screen for Oracle Universal Installer appears Oracle Universal Ins
215. meet the following requirements Each node must have at least two network adapters one for the public network interface and one for the private network interface the interconnect a The interface names associated with the network adapters for each network must be the same on all nodes a For increased reliability you can configure redundant public and private network adapters for each node Forthe public network each network adapter must support TCP IP a For the private network the interconnect must support the user datagram protocol UDP using high speed network adapters and switches that support TCP IP Gigabit Ethernet or better recommended Note UDP is the default interconnect protocol for Real Application Clusters and TCP is the interconnect protocol for Oracle Clusterware Token Ring is not supported for the interconnect For the private network the end points of all designated interconnect interfaces must be completely reachable on the network Network Parameter Requirements If you are using NFS then you must set the values for the NFS buffer size parameters rsize and wsize to at least 16384 Oracle recommends that you use the value 32768 Installing Cluster Environments 5 9 Pre installation Tasks for Real Application Clusters on UNIX IP Address Requirements Before starting the installation you must identify or obtain the following IP addresses for each node a An IP address and a
216. meter 4 4 description 4 3 DISTRIBUTION parameter 4 3 IMAGES section 4 5 JRE LOCATION parameter 4 4 JRE MEMORY OPTIONS parameter 4 4 LICENSE LOCATION parameter 4 4 LICENSE TITLE parameter 4 4 NLS ENABLED parameter 4 5 NO BROWSE parameter 4 4 ORACLE section 4 3 OUI LOCATION parameter 4 4 OUI VERSION parameter 4 4 REGISTRATION KEY 4 5 REGISTRATION URL 4 5 sample D 7 SOURCE parameter 4 3 USE BUILD NUMBER parameter 4 5 out of temp space error B 4 P minimum downtime patching 7 35 rolling patching 7 34 requirements 7 2 standalone 7 22 inventory operations use cases 7 28 patching operations use cases 7 29 requirements 7 23 schema patching options 7 32 SOL execution 7 32 unsupported services 7 22 utility for standalone homes 7 23 utility operations use cases 7 31 troubleshooting logging and tracing 7 39 recovering from failed patching 7 39 resolving application errors 7 45 patchsets for upgrades 1 4 post installation tasks Real Application Clusters 5 22 prerequisite checks automatic checks 4 1 command line parameters 4 2 installing products 4 1 slient mode checks 4 1 standalone checks 4 1 Query command for OUI based homes 7 16 for standalone OPatch 7 26 parameters for response file 3 5 patching additional checks for RAC 7 4 backup and recovery considerations 7 8 conflict detection and resolution 7 38 conflicts duplicate 7 37 subset 7 36 superset 7
217. n Clusters sss 5 27 Troubleshooting Real Application Clusters Oracle Clusterware Installation 5 27 Cloning Oracle Software About Cloning ennt UUsaR UO dan rias 6 1 Overview of the Cloning Process sse eee eene nennen nennen a 6 2 Source Preparation PhasEc citadas qr gere aia traida 6 2 Cloning Phase sceeidrsteau abad 6 3 Locating and Viewing Log Files sse eee ne nenne enne 6 3 Cloning an Oracle Database 11 1 Oracle Home sese 6 4 Preparing the 11 1 Oracle Database Source sss eee eee 6 4 Cloning am 11 1 Oracle Database snipes nue eei ede erp n rt terria 6 5 Viewing Log and Error Piles vivacidad IR HI ena 6 6 Creating an Oracle Real Application Cluster Environment using Cloning 6 6 Important Considerations when Cloning Oracle Real Application Clusters 6 6 Creating Oracle RAC Environments on UNIX and Linux System Based Environments 6 7 Cloning Oracle Clusterware on UNIX and Linux System Based Environments 6 7 Cloning Oracle RAC Software on UNIX and Linux System Based Environments 6 8 Creating Oracle RAC Environments on Windows System Based Environments 6 9 Cloning Oracle Clusterware on Windows System Based Environments 6 9 Cloning Oracle RAC Software on Windows System Based Environments
218. n Clusters Environments 4 From the node that you cloned run DBCA to add the database instance to the new node Adding Nodes Using Cloning in Oracle Real Application Clusters Environments This section explains how to add nodes to existing Oracle RAC environments by using Oracle cloning These following topics explain how to use cloning for both UNIX and Linux system environments as well as Windows system environments Cloning Oracle RAC Environments on UNIX and Linux System Based Environments Cloning Oracle RAC Environments on Windows System Based Environments Cloning Oracle RAC Environments on UNIX and Linux System Based Environments These procedures assume that you have successfully installed and configured an Oracle RAC environment to which you want to add nodes and instances To add nodes to a UNIX or Linux system Oracle RAC environment using cloning extend the Oracle Clusterware configuration extend the Oracle Database software with RAC and then add the listeners and instances by running the Oracle assistants as described in the following procedures Cloning Oracle Clusterware on UNIX and Linux System Based Environments Cloning Oracle RAC Software on UNIX and Linux System Based Environments Cloning Oracle Clusterware on UNIX and Linux System Based Environments Complete the following steps to clone Oracle Clusterware on UNIX and Linux systems 1 Skip this step if you have a shared Oracle Clusterware home
219. n associated host name registered in the domain name service DNS for each public network interface One unused virtual IP address and an associated virtual host name registered in DNS or resolved in the host file or both that you will configure for the primary public network interface The virtual IP address must be in the same subnet as the associated public interface After installation you can configure clients to use the virtual host name or IP address If a node fails then its virtual IP address fails over to another node A private IP address and optional host name for each private interface Oracle recommends that you use non routable IP addresses for the private interfaces for example 10 or 192 168 You can use the etc hosts file on each node to associate private host names with private IP addresses Node Time Requirements Before starting the installation ensure that each member node of the cluster is set as closely as possible to the same date and time Oracle strongly recommends using the Network Time Protocol feature of most operating systems for this purpose with all nodes using the same reference Network Time Protocol server Checking Software Requirements The Oracle Universal Installer performs checks on your system to verify that it meets the requirements listed for your platform To ensure that these checks pass verify the requirements before you start the Installer Depending on the Oracle pro
220. n be selected or unselected This page appears only in a custom install type Example SHOW CUSTOM TREE PAGE false Go hte fotos eerie See eee OM open ce eee me ELE tae Be SHOW CUSTOM TREE PAGE false rn Name SHOW SUMMARY PAGE Datatype Boolean Description Set to true if the summary page in the installer needs to be shown The summary page shows the list of components that will be installed in this session Example SHOW SUMMARY PAGE true A nlt ee ete E AR O A ee E SHOW SUMMARY PAGE true a a a mene ces O eRe ier ce EC Nene mee Name SHOW INSTALL PROGRESS PAGE Datatype Boolean Description Set to true if the install progress page in the installer needs to be shown This page shows the current status in the installation The current status includes which product is being installed which file is being copied Example SHOW INSTALL PROGRESS PAGE true FT een ENT Mcd E RR Re ae SHOW INSTALL PROGRESS PAGE true Hecate E seers P Name SHOW REQUIRED CONFIG TOOL PAGE Datatype Boolean Description Set to true if the required config tools page in the installer needs to be shown This page shows the list of required configuration tools that are part of this installation It shows the status of each tool including any failures with detailed information on why the tool has failed Example SHOW REQUIRED CONFIG TOOL PAGE true Name
221. n on the Select Disk Formatting Options page you must complete the Select Software Storage Drive page and the Select Data Storage Drive page as described in Steps a and b respectively If you selected the Format one logical drive for software storage option on the Select Disk Formatting Options page you must complete the Select Software Storage Drive page the Disk Configuration Oracle Cluster Registry OCR page and the Disk Configuration Voting Disk page as described in Steps a c and d respectively If you selected the Format one logical drive for data file storage option on the Select Disk Formatting Options page you must complete the Select Data Storage Drive page as described in Step b If you selected the Do not format any logical drives option on the Select Disk Formatting Options page you must complete the Disk Configuration Oracle Cluster Registry OCR page and the Disk Configuration Voting Disk page as described in Steps c and d respectively a Onthe Select Software Storage Drive page choose a shared drive to see a list of available partitions on that drive Choose a partition with sufficient space to hold your Oracle home and select the partition s disk number and partition number from the list Click Next to proceed b Onthe Select Data Storage Drive page choose a shared drive to see a list of available partitions on that drive Choose a partition with sufficient space to hold your database files and sele
222. n the rootaddnode sh script from the SORACLE _ HOME install directory 6 Onthe new node go to the SORACLE HOME directory and run the root sh script to start the Oracle Clusterware on the new node 7 Determine the remote port to use in the next step by running the following command from the CRS_HOME opmn conf directory cat ons config 8 From the CRS_HOME bin directory on an existing node run the following command where racgons is the Oracle RAC Notification Service Utility new_ node is the name of the new node and remote_port is the value from the output of the previous step racgons add config new node remote port Cloning Oracle RAC Software on UNIX and Linux System Based Environments Complete the following steps to clone Oracle Database with RAC software on UNIX and Linux systems 6 12 Oracle Universal Installer and OPatch User s Guide Adding Nodes Using Cloning in Oracle Real Application Clusters Environments 1 If you do not have a shared Oracle Database home tar the Oracle RAC home from the existing node and copy it to the new node Assume that the location of the destination Oracle RAC home on the new node is SORACLE HOME Otherwise skip this step Note For more information on archiving and unarchiving see Source Preparation Phase and Cloning Phase 2 Ifyou do not have a shared Oracle Database home navigate to the SORACLE _ HOME c1one bin directory on the new node and run the foll
223. nal name and version while specifying the value oracle swd jre 1 3 1 1 0a Java Runtime Environment 1 3 1 1 0a oracle swd jre 1 3 1 0 0a Java Runtime Environment 1 3 1 0 0a oracle swd osp 2 2 1 2 0 Oracle Software Packager 2 2 1 2 0 Alpha oracle swd oil 2 2 1 2 0 Oracle Installation Libraries 2 2 1 2 0 oracle swd oui 2 2 1 2 0 Oracle Universal Installer 2 2 1 2 0 Alpha Example DEPENDENCY LIST Component oracle swd oracle swd jre 1 3 1 1 0a dependency list lt Value Unspecified gt D 6 Oracle Universal Installer and OPatch User s Guide Sample Components File Sample ORAPARAM INI File The oraparam ini file is Oracle Universal Installer s initialization file It should be located in the same directory as the Oracle Universal Installer executable file setup exe or runInstaller sh Oracle DISTRIBUTION TRUE SOURCE stage products xml LICENSE LOCATION LOCATION stage Components oracle swd jre 1 4 2 0 0 1 DataFiles RE MEMORY OPTIONS mx150m FAULT HOME LOCATION oracle product 11 1 0 db ULT HOME NAME OraDbllg home BROWSE net S ENABLED TRUE OOTSTRAP TRUE REREQ CONFIG LOCATION stage prereq OUI VERSION 11 1 0 0 0 SHOW_HOSTNAME ALWAYS SHOW shows the hostname panel always SHOW_HOSTNAME NEVER_ SHOW does not the hostname panel SHOW HOSTNAME CONDITION SHOW shows the hostname panel on condition SHOW HOSTNAME NEVER SHOW THIN JDBC FILENAME is optional and defau
224. nd 0 to 9 Enter a public and a private host name for each node Neither the public nor the private name should have a domain qualifier When you enter the public host name use the primary host name of each node that is the name displayed by the hostname command The private node refers to an address that is only accessible by the other nodes in this cluster and which Oracle uses for Cache Fusion processing You can enter either a private host name or a private IP address for each node Click Next after you have entered the cluster configuration information This saves your entries and opens the Specify Network Interface Usage page 5 Inthe Specify Network Interface Usage page the Oracle Universal Installer displays a list of cluster wide interfaces Use the drop down menus on this page to classify each interface as Public Private or Do Not Use The default setting for each interface is Do Not Use You must classify at least one interconnect as Public and one as Private Click Next when you have made your selections to open the Select Disk Formatting Options page 6 Inthe Select Disk Formatting Options page you indicate what OCFS you want the Oracle Universal Installer to format for you The formatting options are as follows Format two logical drives for data and software storage In this case the Oracle Universal Installer creates two cluster file systems one for the database files and one for the Oracle home The OCR and vot
225. nd line arguments for OUI 4 13 components file sample D 7 third party applications and 2 6 creating Oracle home 2 1 required UNIX groups and users 5 5 D debugging automated inventory backups B 3 central inventory backup B 3 installation log B 1 mechanisms B 1 Oracle Universal Installer errors B 3 default Oracle home determining 2 2 DEFAULT_HOME_LOCATION parameter in ORAPARAM INL 4 4 DEFAULT_HOME_NAME parameter in ORAPARAMLINI 4 4 DEINSTALL_LIST parameter 3 9 deinstallation cluster 5 21 dependents 4 11 description of process 1 3 Oracle Clusterware 5 25 Oracle products 4 10 Real Application Clusters software 5 23 on UNIX 5 23 on Windows 5 24 removing products and Oracle homes 4 10 silent 4 11 top level products 4 11 DEPENDENCY LIST parameter 3 9 detaching homes from the Central Inventory 2 8 using optional flags 2 8 detaching Oracle homes 1 4 diagnosing inventory corruption 2 10 2 11 directory structure Index 2 for UNIX 2 13 for Windows 2 13 disk space requirements 1 1 DISTRIBUTION parameter in ORAPARAM INI 4 3 E errors exceptions from action libraries B 4 failed to connect to server error 4 9 incomplete stage and missing files in file groups B 4 out of temp space B 4 UNCAUGHT RUNTIME exception B 4 Exceed tool B 4 exit codes for Oracle Universal Installer 4 14 F failed to connect to server error 4 9 features of Oracle Universal Installer 1 1 format o
226. nd of the post options Use this option with the post option If you do not use this option everything after post until the end of the command is passed into post opatch pre end Marks the end of the pre options Use this option with the pre option If you do not use this option everything after pre until the end of the command is passed into pre Patch Location Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location ph Specifies the valid patch directory area Rollback uses the command types found in the patch directory to identify which commands are used for the current operating system post Specifies the parameters to be passed inside the post script This script executes after the patch is removed You must enclose the value of this option in double quotes pre Specifies the parameters to be passed inside the pre script This script executes before the patch is removed You must enclose the value of this option in double quotes property file Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies report Prints the actions to the screen without executing them silent Suppresses user interaction and defaults any yes no questions to yes A Real Application Clusters setup does not support this option verbose Prints addi
227. nd the REMOTE NODES variable is empty The syntax is as follows runinstaller silent attachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME lt Oracle Home Name gt REMOTE NODES local Note When you use the local flag it performs the action on the local node irrespective of the cluster nodes specified Managing Oracle Homes 2 7 Oracle Universal Installer Inventory For a non Real Application Clusters setup you do not need to pass the LOCAL NODE variable and the CLUSTER NODES variable is empty The syntax is as follows runInstaller silent attachHome invPtrLoc oraInst loc ORACLE HOME Oracle Home Location ORACLE HOME NAME Oracle Home Name gt CLUSTER NODES You can use the 10ca1 flag to attach the local Oracle home If you are using a shared Oracle home with the 1ocal flag use the cfs flag This ensures that the local node information is not populated inside a shared Oracle home Verifying the Operation After attaching the Oracle home you can verify the success of the operation by verifying the contents of the log file present in the central inventory logs directory You can also view the contents of the inventory xml file under the lt central inventory gt ContentsXML directory to verify if the Oracle home is registered Note Oracle recommends cloning on Windows operating systems to create the Central Inventory Detaching
228. ndicates true if the patch is an online patch Otherwise the option is false is portal patch Indicates true if the patch has portal actions Otherwise the option is false is rolling patch Indicates true if the patch is a rolling patch Otherwise the option is false 7 26 Oracle Universal Installer and OPatch User s Guide Standalone Patching Table 7 11 Cont Query Options Option Description oh Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE HOME environment variable Patch Location Indicates the path to the patch location If you do not specify the location OPatch assumes the current directory is the patch location Rollback Command for Standalone OPatch The Rollback command removes an existing one off patch from the appropriate Oracle home directory indicated by the reference ID Syntax Use the following syntax for this command opatch rollback id ID ph Patch Location gt jre LOC oh ORACLE HOME gt silent verbose no relink pre parameters for the pre Script in escaped double quotes opatch pre end post parameters for the post script in escaped double quotes gt opatch post end no sysmod property file path to property file gt init parameters for the init script in escaped double quotes opatch init end report Options Table 7 12 lists the options available fo
229. ne nennen tenent nenenens 2 9 Recovering from Inventory Corruption sese nnne nennen 2 10 Diagnosing and Recovering from Central Inventory Corruption sess 2 10 Diagnosing and Recovering from Oracle Home Inventory Corruption 2 11 R al Application Clust rs ent irme ee naet 2 11 Updating the Nodes of a Cluster sse nenne 2 12 Home Selector Available on Win32 Platforms sess ennn et 2 12 Home Selector OVetvlew 3 se eere tree eite bct ee diste re e ee iR Plena 2 12 How Home Selector Works amic dale 2 12 Oracle Home Directory Structure for Windows Platforms sse 2 13 Optimal Flexible Architecture Directory Structure on UNIX sse 2 13 ORACLE_BASE Ditectoty ener eniin ee reti viene ree redada 2 13 ORACLE HOME Directory rre rn E e rhe pte tr tea eee tans 2 14 Customizing and Creating Response Files About Response Files neo reete e tee ite cine imr te de m er de 3 1 What Issa Silent Installation coin cete eiecti tei i IR Ee RUE sts 3 1 What s Response File sss erenn ad n pie i e ebd trus 3 1 Why Perform a Silent Installation isnin eot eene nennen 3 2 Modifying a Response File ete da eee epi eee e et ede 3 2 Creating a Response File With Record Mode sss 3 3 Using Record Mode iniret nne e ener nen bd bt eto Er e rene Eran 3 3 Response File Format asp
230. nents the home has however Looking up the Central Inventory You cannot run opatch lsinventory all to list all Oracle homes registered on the host through the Central Inventory repository Migrating from standalone to OUI based patching and vice versa The assumption is that after you have installed a product as standalone without OUI it remains standalone For example after having installed JDeveloper you cannot put OUI through copying or proper installation onto the Oracle home and expect OPatch to treat the home as an OUI based Oracle home Conversely the assumption is that after you have installed a product with OUI it remains OUI based For example after you install Oracle RDBMS you cannot remove OUI either by removing or proper deinstallation and expect OPatch to treat the home as a standalone Oracle home OPatch will not work properly in this case and will corrupt the home Interoperating between standalone and OUI based patches Since you cannot migrate a home from standalone to OUI based and vice versa OPatch does not support interoperability between standalone and OUI based Oracle homes 7 22 Oracle Universal Installer and OPatch User s Guide Standalone Patching Seamlessly working on a cloned standalone Oracle home If you clone a standalone Oracle home 1 to another Oracle home OH2 Opatch will not function properly on the new cloned OH2 Supporting RAC OPatch relies on OUI to detect RAC and propagate
231. network client 2007 07 13 12 03 18 PM log c gtoollogs cfgfw oracle has common 2007 07 13 12 03 18 PM log 6 2 Oracle Universal Installer and OPatch User s Guide Locating and Viewing Log Files c gtoollogs cfgfw oracle assistants server 2007 07 13 12 03 18 PM log cf gtoollogs cfgfw OuiConfigVariables 2007 07 13 12 03 18 PM log c gtoollogs cfgfw oracle sysman console db 2007 07 13 12 03 18 PM log cf gtoollogs cfgfw oracle sqlplus isqlplus 2007 07 13 12 03 18 PM log cfgtoollogs oui cloneActions2007 07 13 11 52 19AM log cfgtoollogs oui silentInstall2007 07 13 11 52 19AM 1log The following example shows how to archive and compress the source for various platforms To archive and compress tar cpf compress fv gt temp dir archiveName tar Z for aix or O eq hpux tar cpfX excludelistFile compress fv temp dir archiveName tar Z for remaining UNIX based systems Note Do not use the jar utility to archive and compress the Oracle home Cloning Phase On the destination system you unarchive the Oracle home and run the clone p1 script This Perl script performs all parts of the cloning operation automatically by running OUI and various other utilities This script uses the cloning functionality in OUI When you run the clone p1 script it handles the specifics that OUI may have missed The Central Inventory of the box where the home is being cloned is updated as is the Oracle home
232. ng a small number of products in different setups on a small number of hosts Suppressed Use Oracle Universal Installer s suppressed mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs You can choose which dialogs to suppress by supplying the information at the command line when you invoke Oracle Universal Installer This method is most useful when an installation has a common set of parameters that can be captured in a response file in addition to custom information that must be input by hand Silent Use Oracle Universal Installer s silent installation mode to bypass the graphical user interface and supply the necessary information in a response file This method is most useful when installing the same product multiple times on multiple hosts By using a response file you can automate the installation of a product for which you know the installation parameters For more information see Chapter 3 Customizing and Creating Response Files for detailed information on using response files and installing in silent mode Note Youcan use the noConsole flag on the Windows platform to suppress the display of messages in the console Installation Media For each of these three installation modes you can install from three different media Installing from a Single CD ROM Installing from Multiple CD ROMs Installing from a staged
233. ns the Oracle Universal Installer Welcome page After you click Next in the Welcome page the Specify File Locations page allows you to accept the displayed path name for the Oracle Clusterware products or select a different one You can also accept default directory and path name for the location of your Clusterware home or browse for an alternate directory and destination You must select a destination that exists on each cluster node that is part of this installation Click Next to confirm your choices and proceed to the Language Selection page Select the language or languages for your Oracle Clusterware installation in the Language Selection page then click Next for the Cluster Configuration page 5 16 Oracle Universal Installer and OPatch User s Guide Installing Oracle Clusterware on Windows 4 The Cluster Configuration page contains predefined node information if the Oracle Universal Installer detects that your system has the Oracle 10g Release 2 Clusterware Otherwise the Oracle Universal Installer displays the Cluster Configuration page without predefined node information Provide your own cluster name if you do not want to use the name provided by the Oracle Universal Installer Note that the selected cluster name must be globally unique throughout the enterprise and its allowable character set is the same as that for host names that is underscores hyphens and single byte alphanumeric characters a to z A to Z a
234. nstall Oracle Clusterware or Real Application Clusters the Oracle Universal Installer copies the Oracle software onto the node from which you are running it If your Oracle home is not on a shared file system the Oracle Universal Installer propagates the software onto the other nodes that you have selected to be part of your Oracle Universal Installer installation session The Oracle inventory maintains a list of each node that is a member of the Real Application Clusters database and lists the paths to each node s Oracle home This is used to maintain patches and updates for each member node of the Real Application Clusters database When the Oracle Universal Installer installs the Oracle software Oracle recommends that you select a preconfigured database or use the Database Configuration Assistant DBCA interactively to create your cluster database You can also manually create your database as described in procedures posted on the Oracle Technical Network which is at the following URL http www oracle com technology index htm Oracle recommends that you use Automatic Storage Management ASM If you are not using ASM or if you are not using a cluster file system then configure shared raw devices before you create your database Oracle software provides additional components to operate Real Application Clusters Some of the Real Application Clusters specific components include a Oracle Clusterware Installed Real Application Clus
235. o override the default path Filters log messages that have a lesser priority level than the level specified Valid options are severe warning info config fine finer and finest Specifies the location of the oraparam ini file to be used by Oracle Universal Installer Specifies the location of the response file to use This option is used with the silent flag Specifies the shiphome location Adds new languages to an already installed product Adds node s to the installation You cannot use this flag in silent mode with response files You can pass the required session variable through the command line You must pass the CLUSTER NEW NODES CLUSTER_NEW_PRIVATE_NODE_ NAMES and CLUSTER NEW VIRTUAL HOSTNAMES session variables when using this flag Attaches homes to the Oracle Universal Installer inventory You must pass the ORACLE HOME and ORACLE HOME NAME session variables when using this flag Indicates that the Oracle home specified is on a cluster file system shared This is mandatory when local flag is specified so that Oracle Universal Installer can register the home appropriately into the inventory Used for cloning an Oracle home from a source location to a target location You must pass the ORACLE HOME and ORACLE HOME NAME session variables when using this flag Used for getting the debug information from Oracle Universal Installer Used for de install operations You can pass the DEINSTALL_ LIST and o
236. of the actions that occur during the pre cloning and cloning operations a ORACLE_HOME clone logs error timestamp log Contains information about errors that occur during the pre cloning and cloning operations To find the location of the Oracle inventory directory On all UNIX system computers except Linux and IBM AIX look in the var opt oracle oraInst 1oc file On IBM AIX and Linux based systems look in the etc oraInst 1oc file On Windows system computers you can obtain the location from the Windows Registry key HKEY LOCAL MACHINE SOFTWARE ORACLE INST_LOC After the clone p1 script finishes running refer to these log files to obtain more information about the cloning process Cloning an Oracle Database 11 1 Oracle Home There are two steps involved in cloning an Oracle Database 11 1 Oracle home Preparing the 11 1 Oracle Database Source Cloning an 11 1 Oracle Database Preparing the 11 1 Oracle Database Source To prepare the source Oracle home to be cloned perform the following steps 1 Ensure that the Oracle Database installation whose home you want to clone has been successful For Windows system computers you can check the status of the installation by reviewing the installActionsdate time 10g file for the installation session where date time represents the date and time when the file was created for example installActions2007 05 30 10 28 04PM log This log file is normally located in the c Program Files Or
237. ommand on the existing node where new node new node priv and new node vip are the name of the new node the private interconnect protocol address of the new node and the virtual interconnect protocol address of the new node respectively SORACLE HOME oui bin addNode bat silent CLUSTER NEW NODES new node CLUSTER NEW PRIVATE NODE NAMES new node priv CLUSTER NEW VIRTUAL _ HOSTNAMES new node vip noCopy noRemoteActions 6 14 Oracle Universal Installer and OPatch User s Guide Adding Nodes Using Cloning in Oracle Real Application Clusters Environments Note Because you have already run the clone pl script on the new node this step only updates the inventories on the nodes and instantiates scripts on the local node 4 From the CRS HOMES V install directory on the existing node run the crssetup add bat script to instantiate the Virtual Protocol Configuration Assistant VIPCA and the Oracle RAC Notification Service Utility racgons Cloning Oracle RAC Software on Windows System Based Environments Complete the following steps to clone Oracle Database with RAC software on Windows system computers 1 Skip this step if you have a shared Oracle Database home If you do not have a shared Oracle Database home zip the Oracle Database home with Oracle RAC on the existing node and copy it to the new node Unzip the Oracle Database with Oracle RAC home on the new node in the same directory in which the Oracle
238. on Rollback Command for OUI based Oracle Homes This command removes an existing one off patch from the appropriate Oracle home directory indicated by the reference ID Syntax Use the following syntax for this command opatch rollback id ID ph Patch Location gt delay lt value gt invPtrLoc Path to oraInst loc jre LOC 1ocal oh ORACLE HOME gt retry lt value gt silent verbose no relink pre parameters for the pre Script in escaped double quotes opatch pre end post parameters for the post script in escaped double quotes gt opatch post end no sysmod property file path to property file gt local node Local node name gt remote nodes List of remote nodes nodel node2 gt connectString List of connect strings ptlSchema portal schema gt ptlPassword portal password gt ptlConnect portal connect string gt runSql sqlScript path of the sql file gt init lt parameters for the init script in escaped double quotes opatch init end report Patching Oracle Software with OPatch 7 17 OPatch Utility for OUI based Oracle Homes Options Table 7 6 lists the options available for the Rollback command Table 7 6 Rollback Options for OUI Patches Option Description all nodes Rolls back the patch using the all nodes mode connectString Specifies the list of database instances on which the patch needs to b
239. one of the following a Use keyboard shortcuts to invoke these commands Use Alt N for Next to move to the next screen Onthesummary page use Alt I to start the installation a Use the Window Manager window in Tarantella which displays the entire screen as if it were a UNIX monitor Installer dialogs will appear properly in Window Manager Troubleshooting and Debugging Oracle Universal Installer B 5 Other Tips B 6 Oracle Universal Installer and OPatch User s Guide C Understanding Oracle Universal Installer Commands The Oracle Universal Installer is run with various options and command line arguments This appendix lists the syntax of Oracle Universal Installer and the various command line options available in Oracle Universal Installer The following command shows the syntax for running the Oracle Universal Installer runInstaller or setup exe option command line variable value In the preceding command the following variables are used option The options available in Oracle Universal Installer They are described in Table C 1 Options in Oracle Universal Installer command line variable The command line variable for the option They are described in Table C2 Command Line Variables in Oracle Universal Installer Note Youcan pass the command line variable in either of the following three ways 1 command line variable valuel value2 2 command line variable valuel
240. onments Managing Oracle Homes 2 11 Home Selector Available on Win32 Platforms Updating the Nodes of a Cluster When you use the updateNodeList flag with the Oracle Universal Installer it retrieves the list of nodes and updates the inventory xml file If the CRS tag is set to TRUE the Oraclehomeproperties xml file is updated with the Oracle Clusterware home information For shared Oracle homes you need to use this with the cfs flag The syntax is as follows runlInstaller updateNodeList CLUSTER_NODES Nodel Node2 ORACLE HOME Oracle Home Location gt ORACLE HOME NAME lt Oracle Home Names LOCAL NODE Node Name Note You update the nodes of a cluster only under exceptional circumstances Oracle recommends that you perform this operation with the help of Oracle support Home Selector Available on Win32 Platforms The following sections describe the Home Selector which is installed as part of Oracle Universal Installer on Windows computers To view the Home Selector click the Environment tab of the Inventory dialog which appears when you click the Installed Products button on several Oracle Universal Installer screens Home Selector Overview The Home Selector is a part of the installation software The Home Selector enables you to easily change your primary Oracle home the one that appears first in the PATH environment variable If you need to switch the active home or need to perfo
241. ons This section describes the clone p1 script variables and their definitions for UNIX and Linux systems as well as Windows systems under the following topics Variables for UNIX and Linux System Based Environments Cloning Oracle Software 6 15 Adding Nodes Using Cloning in Oracle Real Application Clusters Environments Variables for Windows System Based Environments Variables for UNIX and Linux System Based Environments Table 6 2 describes the variables that can be passed to clone p1 with the O option for UNIX and Linux systems Table 6 2 UNIX and Linux System Based Variables for clone pl with the O Option Variable Datatype Description storageTypeVDSK Integer Set to 1 Not Redundant or 2 Redundant after the dialog returns n storageTypeOCR Integer Set to 1 Not Redundant or 2 Redundant after the dialog returns S clustername String Contains user entered cluster name information allow a maximum of 15 characters VdskMirrorNotReqd String Not required in the Oracle Cluster Registry OCR dialog CLUSTER CONFIGURATION String Passes the cluster configuration file information which is the same FILE file as that specified during installation You can use this file instead ofsl tablelist This file contains the public node name private node name and virtual host name which is white space delimited information for the nodes of the cluster For example nodel nodel priv nodel vip node2 node2 priv node2 vip
242. or the cfs parameter on the command line Creating Oracle RAC Environments on UNIX and Linux System Based Environments This section explains how to clone an Oracle RAC environment by using Oracle cloning as described in the following procedures Cloning Oracle Clusterware on UNIX and Linux System Based Environments Cloning Oracle RAC Software on UNIX and Linux System Based Environments Cloning Oracle Clusterware on UNIX and Linux System Based Environments Complete the following steps to clone Oracle Clusterware on UNIX and Linux systems 1 Skip this step if you have a shared Oracle Clusterware home If you do rot havea shared Oracle Clusterware home tar the Oracle Clusterware home from an existing node and copy it to the new node Use CRS HOME as the destination Oracle Clusterware home on the new node Note For more information on archiving see Source Preparation Phase Unarchive the home on the new nodes In the case of shared homes unarchive the home only once on the nodes Note For more information on archiving see Cloning Phase If you do not have a shared Oracle Clusterware home navigate to the SORACLE_ HOME c1one bin directory on the new node and run the following command where Oracle home name is the name of the Oracle home new node is the name of the new node new node privis the private interconnect protocol address of the new node new node vipis the virtual interconnect protoco
243. oracle gid 200 oinstall groups 201 dba 202 oper 2 From the output identify the user identity UID for the Oracle user and the group identities GIDs for the groups to which it belongs Creating the User and Groups on the Other Cluster Nodes To create the user and groups on the other cluster nodes repeat the following procedure on each node 1 Log in to the cluster node in which you want to create the user and groups as root 2 Enter commands as per the syntax to create the respective groups Use the g option to specify the correct GID for each group usr sbin groupadd g group id group name gt Configuring SSH on all Cluster Nodes Before you install and use Oracle Real Application Clusters you must configure secure shell SSH for the oracle user on all cluster nodes Oracle Universal Installer uses the ssh and scp commands during installation to run remote commands on and copy files to the other cluster nodes You must configure SSH so that these commands do not prompt for a password Note This section describes how to configure OpenSSH version 3 If SSH is not available then Oracle Universal Installer attempts to use rsh and rcp instead However these services are disabled by default on most Linux systems Configuring SSH on Cluster Member Nodes To configure SSH complete the following steps on each cluster node 1 Log in as the Oracle user 2 Ifnecessary create the ssh directory in th
244. ort Set to FALSE to disable the installation session translations Oracle Universal Installer displays in English even if you run on a non English system Set to TRUE or FALSE This parameter instructs Oracle Universal Installer to attempt a bootstrap Set to TRUE before cutting CDs but set to FALSE after you have copied the staging area to the hard disk Use this parameter to set the size the temporary space requires when BOOTSTRAP is set to TRUE For example when you install Oracle Universal Installer it sets the value of this parameter to the temporary space required by both Oracle Universal Installer and the JRE By default if this entry is not set Oracle Universal Installer assumes 45 MB for Win32 52 MB for Win64 and 69 MB for Solaris However these values could vary from one major release to the other based on the space required by newer versions of JRE If the shiphome contains advertisement images installation developers should add the space taken by the images to this value Oracle Universal Installer checks the temp space requirements before starting up and produces an error if there is not enough space for Oracle Universal Installer to run in bootstrap mode Use this parameter to control whether or not Oracle Universal Installer considers the build number of the component when determining whether or not to overwrite a previous version or copy of a component Note that this parameter is intended to be used in pre prod
245. ot find system commands like fuser make on page 7 46 How do I receive the information about a patch that I applied a long time ago Frequently Asked Questions A 3 OPatch You can look at the folder SORACLE HOME patch storage patch id timestamp gt It has detailed information about the patch You can also use opatch lsinventory detail to see the files that the patch has modified Where do I get the OPatch 11 1 log files You can look at the folder SORACLE HOME cfgtoollogs opatch for OPatch 11 1 log files How do I find out a list of Oracle home s for a host To find out the list of Oracle home s in a host use the command lsinventory all How can I minimize the downtime when applying a patch to a Real Application Clusters setup You can minimize the downtime when applying a patch to a Real Application Clusters setup by doing Minimum Downtime Patching For more information see Minimum Downtime Patching on page 7 35 Can I stop applying a patch after applying it to a few nodes What are the possible issues Yes it is possible to stop applying a patch after applying it to a few nodes However Oracle recommends that you do not do this There is a prompt that allows you to stop applying the patch This means you cannot apply another patch until the process is restarted and all the nodes are patched or the partially applied patch is rolled back Can I run patching in scripted mode Yes it is possible by usin
246. our Oracle product with Real Application Clusters installation is complete and after you are sure that your system is functioning properly make a back up of the contents of the disk Also make a back up of the disk contents after you complete any node additions or node deletions and after running any de installation procedures Download and Install Patches Go to the OracleMetaLink Web site for required patches for your installation To download the required patches 1 Usea Web browser to view the OracleMetaLink Web site http metalink oracle com 2 Login to OracleMetaLink 3 Onthe main OracleMetaLink page click Patches 4 Onthe Select a Patch Search Area page click New MetaLink Patch Search 5 22 Oracle Universal Installer and OPatch User s Guide Deinstalling Real Application Clusters Software 10 11 12 13 14 On the Simple Search page click Advanced On the Advanced Search page click the search icon next to the Product or Product Family field In the Search and Select Product Family field enter the Oracle product name in the For field and click Go Select the Oracle product under the Results heading and click Select The product name appears in the Product or Product Family field and the current release appears in the Release field Select your platform from the list in the Platform field and click Go Any available patches appear under the Results heading Click the number of the patch that you
247. out reapplying a one off patch The OPatch addpatch p1 tool enables you to update the inventory with a given one off patch without actually reapplying it to the Oracle home Use this tool if you are certain that the patch is present in the Oracle home but not in the inventory You can download it from MetaLink at patch number 4321390 to just add the patch to the inventory After using this option opatch 1sinventory shows the one off patch information along with other installed one offs Frequently Asked Questions A 5 OPatch A 6 Oracle Universal Installer and OPatch User s Guide Troubleshooting and Debugging Oracle Universal Installer This appendix is organized into the following troubleshooting sections Debugging Mechanisms in Oracle Universal Installer Oracle Universal Installer Errors Other Tips Debugging Mechanisms in Oracle Universal Installer Oracle provides the following types of debugging mechanisms Installation Log Automated Inventory Backups The following sections discuss each of these mechanisms Installation Log During the installation Oracle Universal Installer writes a text file that contains information on Variable settings a Action calls Queries Exception information The log of installation actions is written to a file named installActions lt date gt log located in the lt oraInventory gt logs directory The oraInstall timestamp err and oraInstall timestamp
248. owing command where existing node is the name of the node that you are cloning new node2 and new node3 are the names of the new nodes and Oracle home name is the name of the Oracle home perl clone pl O CLUSTER NODES existing node new node2 new_node3 O LOCAL NODE new node2 ORACLE HOME SORACLE HOME ORACLE HOME NAME Oracle home name O noConfig If you have a shared Oracle Database home append the cfs option to the command example in this step and provide a complete path location for the cluster file system 3 Run the following command on the existing node from the SORACLE _ HOME oui bin directory where existing nodeis the name of the original node that you are cloning and new node2 and new node3 are the names of the new node runInstaller updateNodeList ORACLE HOME S ORACLE HOME CLUSTER _ NODES existing node new node2 new node3 4 Onthe new node go to the SORACLE HOME directory and run the following command root sh 5 Onthe new node run the Net Configuration Assistant NETCA to add a listener 6 From the node that you cloned run the Database Configuration Assistant DBCA to add the new instance Cloning Oracle RAC Environments on Windows System Based Environments These procedures assume that you have successfully installed and configured an Oracle RAC environment to which you want to add nodes and instances To add nodes to a Windows system Oracle RAC environment using cloning extend the Oracle
249. ps 1 2 Run Oracle Universal Installer In the Specify Home Details page enter the Oracle home settings for the installation session See Table 2 1 for a description of the fields in this section of the screen Continue with your installation See Chapter 4 Installing Products for detailed information Managing Oracle Homes 2 1 Removing Oracle Homes Table 2 1 Oracle Installation Settings for Specify Home Details page Settings Functions Name Enter a name for the Oracle home This name identifies the program group associated with a particular home and the Oracle services installed on this home The Oracle home name must be between 1 to 127 characters long and can include only alphanumeric characters and underscores Path Enter the full path to an Oracle home or select an Oracle home from the drop down list of existing Oracle homes The Oracle home location is the directory where products are installed Data files may or may not be installed within an Oracle home You can use the Browse button to choose a directory to install your product For Windows platforms you must provide a valid path that is not in the Windows directory Different homes cannot share the same location Note Oracle recommends that you designate an Oracle home location that is an empty or non existing directory If you select a directory for the Oracle home location that is not empty or already exists you will be warned and ask
250. ptions Oracle Universal Installer installs the software using a predefined set of options These options are stored in a response file rsp Consider the following information about response files a If your product installation includes a response file you can find it on your stage CD ROM under the root of CD gt response directory You can modify the response file for your Oracle product to customize an installation for your organization See Modifying a Response File on page 3 2 for more information Youcan create your own response files using record mode See Creating a Response File With Record Mode on page 3 3 for more information a Ifyou start Oracle Universal Installer from the command line see Using Oracle Universal Installer Exit Codes on page 4 14 The following sections describe how to specify a response file when you start Oracle Universal Installer Note If you attempt to perform a silent installation on a UNIX computer where no Oracle products have been installed you will receive an error message Before you can perform a silent installation on such a computer you must first run the script oraInstRoot sh which is saved in the oraInventory directory You must run this script with root privileges This enables Oracle Universal Installer to set up the Central Inventory on a clean host See Oracle Universal Installer Inventory on page 2 3 for more information on the Central Inventory
251. r REMOVE HOMES along with ORACLE HOME and or ORACLE HOME NAME session variables when using this flag Detaches homes from the Oracle Universal Installer inventory without deleting the inventory directory inside the Oracle home You must pass the ORACLE HOME session variable when using this flag Used in cluster environments to enable an upgrade of a product on a subset of nodes on which the product was installed Executes system prerequisite checks and exits Allows silent mode installation on a non empty directory without warning Lists the syntax and help information Ignores all conflicts with existing interim patches during an upgrade The conflicting interim patches are removed from the home Ignores the results of the system prerequisite checks C 2 Oracle Universal Installer and OPatch User s Guide Command line Variables Available in Oracle Universal Installer Table C 1 Cont Options in Oracle Universal Installer Option Description local Performs the specified operation on the local node irrespective of the cluster nodes specified printdiskusage Logs debug information for disk usage printmemory Logs debug information for memory usage printtime Logs debug information for time usage record destinationFile lt Path gt removeallfiles removeAllPatches silent updateNodeList waitforcompletion nobackground noclusterEnabled noconsole nowarningonremovefiles nowait
252. r an operating system If it is not applicable OPatch displays an error message Check for System Commands OPatch supports a set of properties used for various software operations You can use these properties to control the internal operations of OPatch By default OPatch uses Patching Oracle Software with OPatch 7 3 Prerequisite Checks for OPatch the standard Java property format to specify the properties The following list shows the default properties and their values fuser sbin usr sbin ar usr ccs bin make usr bin You can specify OPatch properties in the following ways By using the default OPatch properties By specifying the location of the user defined properties file By using the command line The syntax is as follows PROPERTY NAME VALUE Example fuser sbin usr sbin Additional Checks for Real Application Clusters For Real Application Clusters ensure that you perform the following prerequisite checks besides the other checks listed in the preceding section Check for User Equivalence You must ensure that the cluster machines have user equivalence set for the user installing Oracle Clusterware Real Application Clusters On UNIX this means rsh or ssh or both should be set up on the cluster machines On Windows this means the same lt domain gt lt user gt should have administrative privileges on all the cluster machines and the machines should be a member of the domain If the use
253. r equivalence is set properly the following command will work properly rsh nodename date For more information on setting user equivalence see Configuring SSH on all Cluster Nodes on page 5 6 Check for OPatch Lsinventory Ensure that you are able to invoke the opatch 1sinventory detail command and are able to see the node information being printed out If you do not find the node information correctly printed out you need to update the node list For more information on updating the node list see Updating the Nodes of a Cluster on page 2 12 The following example shows the command output for 118 installed products and SQL PL SQL and online patches Invoking OPatch 11 1 0 6 0 Oracle Interim Patch Installer version 11 1 0 6 0 Copyright c 2007 Oracle Corporation All rights reserved Oracle Home scratch userid oracle product 11 1 0 db 1 Central Inventory home userid newDB oraInventory from etc oraInst loc 7 4 Oracle Universal Installer and OPatch User s Guide Prerequisite Checks for OPatch OPatch version 11 1 0 6 0 OUI version Lic1 0 2 0 OUI location scratch userid oracle product 11 1 0 db 1 oui Log file location scratch userid oracle product 11 1 0 db 1 cfgtoollogs opatch opatch2007 07 17 23 08 20PM log Lsinventory Output file location scratch userid oracle product 11 1 0 db 1 cfgtoollogs opatch lsinv lsinventory2007 07 17 23 08 20PM txt Installed Top level Products 1 Or
254. r rolled back It can be executed either interactively or silently Cloning is the process of copying an existing installation to a different location while preserving its configuration You can install multiple copies of the Oracle product easily on different computers using cloning During cloning Oracle Universal Installer is invoked in clone mode to adapt the home to the target environment Oracle Universal Installer in clone mode replays all the actions that have been executed to originally install the Oracle home The difference between installation and cloning is that during cloning Oracle Universal Installer runs the actions in the clone mode Each action decides how to respond during cloning For more information on cloning see Chapter 6 Cloning Oracle Software During patching a small collection of files are copied over an existing installation to fix certain bugs OPatch is an Oracle supplied utility that facilitates Oracle software patching For more information on OPatch see Chapter 7 Patching Oracle Software with OPatch Introduction to Oracle Universal Installer 1 3 Major Entities Created Upgrades and Patchsets Oracle Universal Installer enables you to upgrade a product from one version to another version An upgrade is a major product enhancement that often requires installation of the upgraded software For example you may want to convert your Oracle Database 10gR2 10 2 to Oracle 11g R1 11 1 Database which is
255. r the Rollback command Table 7 12 Rollback Options for Standalone Patches Option Description id Indicates the patch to be rolled back Use the 1sinventory option to display all patch identifiers Each one off patch is indicated by its ID To successfully roll back a patch you must provide the patch identifier init Passes parameters to the init script which executes before prerequisite checks are run The values for this option must be enclosed in double quotes jre Specifies the location of a particular JRE Java for OPatch to use instead of the default location under the Oracle home directory no sysmod Specifies that OPatch need not update the files in the system only the inventory It also does not execute the pre and post scripts no relink This option does not perform any make operation in the patch You can use this option during multiple patch removals and to perform the compilation step only once oh Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE HOME environment variable opatch init end Marks the end of the init options Use this option with the init option If you do not use this option everything after init until the end of the command is passed into init Patching Oracle Software with OPatch 7 27 Standalone Patching Table 7 12 Cont Rollback Options for Standalone Patches Option Description opatch post end Marks the e
256. racle Homes Target Home Oracle Universal Installer supports the installation of several active Oracle homes on the same host as long as the products support this at run time Multiple versions of the same product or different products can run from different Oracle homes concurrently Products installed in one home do not conflict or interact with products installed on another home You can update software in any home at any time assuming all Oracle applications services and processes installed on the target home are shut down Processes from other homes may still be running The Oracle home currently accessed by Oracle Universal Installer for installation or deinstallation is the target home To upgrade or remove products from the target homes these products must be shut down or stopped Oracle Universal Installer Inventory The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host provided the product was installed using Oracle Universal Installer Inventory information is stored in Extensible Markup Language XML format The XML format allows for easier diagnosis of problems and faster loading of data Any secure information is not stored directly in the inventory As a result during removal of some products you may be prompted to enter the required credentials for validation Structure of the Oracle Universal Installer Inventory The Oracle Universal Ins
257. racle home SORACLE HOME is set and the Oracle home has been patched using a new OPatch The patch has been downloaded The standalone Oracle home has a different directory patch than the OUI based Oracle home For example the OUI based Oracle home path is path whereas the standalone Oracle home is path dev Enter the following command opatch apply patch_loc 123451 1 OPatch detects that this is a standalone Oracle home 2 OPatch looks for the standalone inventory file and checks for conflicts 3 OPatch performs an automatic rollback if there are conflicting patches 4 OPatch applies a new patch to the home 5 OPatch updates its standalone inventory Table 7 17 Applying an Interim Patch Case 3 Use Case Category Description Purpose Preconditions User Input OPatch Response Apply an interim patch on a standalone Oracle It seems to be a standalone Oracle home but OPatch detects it as OUI based SORACLE HOME is set and the Oracle home has been patched using a new OPatch The patch has been downloaded Enter the following command opatch apply patch_loc 123451 1 OnPatch detects ORACLE HOME oui and believes it is an OUI based Oracle home 2 OPatch attempts to apply the patch as OUI based Oracle home patching if the patch is compatible with the home Table 7 18 Rolling Back an Applied Interim Patch Use Case Category Description Purpose Preconditions User Inpu
258. rdware requirements For more information on hardware requirements and the steps involved to check them see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Hard Disk Space Requirements Each system must meet certain hard disk space requirements For more information on hard disk space requirements see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Checking the Software Requirements Each system must meet minimum software requirements For more information on software requirements and the steps involved to check them see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Checking the Network Requirements There are some minimum networking hardware and Internet protocol IP address requirements Check that you have the networking hardware and Internet protocol IP address required for an Oracle Real Application Clusters installation For more information on the steps involved in checking these requirements see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Network Hardware Requirements Each node in the cluster must meet the following requirements Each node must have at least two network adapters one for the public network interface and one for the private network interface the interconnect a The private and public network interface names must be different from each other and cannot contain any multibyte languag
259. re Installation Errors Caused by stty Commands 5 8 Configuring the Oracle User Environment sess eene ener 5 9 Checking the Hardware Requirements sse e enne 5 9 Checking the Network Requirements sese nennen nnns 5 9 Network Hardware Requirements sese eene nennen nennen 5 9 Network Parameter Requirements sse eene nnns 5 9 IP Address Requirement ete al tala iet ee end ena de etg cinereis 5 10 Node Time Requiretients mirror attenti ee bee ea brescia dee 5 10 Checking Software Requirements ssssssssssee eene n nene nennen 5 10 Configuring Kernel Parameters sese nnne nennen 5 10 Identifying Required Software Directories sse eee nnns 5 10 Oracle Base Directory eet rere e eti rete oe einer e eet e eee tee 5 11 Ofacle Inventory Die Vaio iii et eee eet dee eere edited eene te us 5 11 Oracle Clusterware Home Directory sese eee nennen nennen 5 12 Oracle Home Directory iei nei datado 5 12 Identifying or Creating an Oracle Base Directory sss eee ee 5 12 Creating the Clusterware Home Directory sss 5 12 Pre installation Tasks for Real Application Clusters on Windows sss 5 13 Checking Hardware and Software Certification sse eene 5 13 Checking the Hardware Requirements sess eene nnne e nnne 5 14 Hard Disk Space
260. re with No Previous Cluster Software Versions Deinstalling Oracle Clusterware with Clusterware Downgrade to 10 2 Deinstalling Oracle Clusterware with No Previous Cluster Software Versions Perform the following steps to deinstall Oracle 11g Clusterware software from a Windows environment 1 Click Start and navigate to Settings then to Control Panel then to Administrative Tools and then to Services Stop the service oracleremexec 2 Start the Oracle Universal Installer On the Welcome page click Deinstall Products to display the list of installed products Select the Oracle Clusterware home you want to deinstall 3 If you have services with names such as OracleCRSTokenname remove them by running the following command crsuser remove user name where user name is a user name 4 Shut down and restart each node that is a member of your cluster 5 Ifyou are not using a cluster file system on each node use Windows Explorer to delete the Oracle directory its subdirectories and their contents Deinstalling Oracle Clusterware with Clusterware Downgrade to 10 2 Perform the following steps to deinstall Oracle 11g Clusterware software from a Windows environment that also has 10 2 Real Application Clusters 1 Run CRS HOMEMbinNGuiOracleOBJManager exe to make sure that the symbolic link named srvcfg exists and points to a disk partition if you are not using OCFS to store the OCR If Oracle10g release 10 2 Clusterware uses Oracle C
261. reated as follows AttachHome2007 05 17 06 45 00AM log Note The installation logs do not contain any errors or failures Oracle Home Inventory Oracle home inventory or local inventory is present inside each Oracle home It only contains information relevant to a particular Oracle home This file is located in the following location SORACLE HOME inventory It contains the following files and folders Components File Home Properties File Managing Oracle Homes 2 5 Oracle Universal Installer Inventory Other Folders Components File This file contains the details about third party applications like Java Runtime Environment JRE required by different Java based Oracle tools and components In addition it also contains details of all the components as well as patchsets or interim patches installed in the Oracle home This file is located here ORACLE HOME inventory ContentsXML comps xml For an example of the components file see Sample Components File on page D 7 Home Properties File This file contains the details about the node list the local node name and the CRS flag for the Oracle home In a shared Oracle home the local node information is not present This file also contains the following information GUID Unique global ID for the Oracle home ARU ID Unique platform ID The patching and patchset application depends on this ID a ARU ID DESCRIPTION Platform description The
262. ript uses the cloning functionality in OUI Note The clone pl script clones the software only and not the database instance The following command shows the syntax for the clone p1 script For Windows based systems perl lt Oracle_Home gt clone bin clone pl ORACLE HOME Path to the Oracle Home being cloned ORACLE HOME NAME Oracle Home Name for the Oracle Home being cloned command line arguments ForLinux based and UNIX based systems perl Oracle Home clone bin clone pl ORACLE HOME Path to the Oracle Home being cloned ORACLE HOME NAME Oracle Home Name for the Oracle Home being cloned command line arguments The preceding command uses the command line arguments variable Table 6 1 describes the command line arguments Table 6 1 Command line arguments in the clone pl script Command line Argument Description O If you use this argument anything following it is passed to the OUI clone command line For example you can use this option to pass the location of the oraparam ini file to be used by OUI 0 paramFile C OraHome_1 oui oraparam ini debug If you use this argument the script runs in debug mode help If you use this argument the script prints the help for the clone script You can also pass values in the command line by using the SORACLE_ HOME clone config cs properties file You can enter values in the line clone_command_line lt value gt The v
263. rk if Oracle Universal Installer is running in bootstrap mode In this case setup exe runInstaller just launches the JRE process and returns immediately without waiting for the exit code Oracle Universal Installer runs in bootstrap mode if the following line exists in the oraparam ini file BOOTSTRAP TRUE 4 14 Oracle Universal Installer and OPatch User s Guide About Oracle Universal Installer Log Files Ifyou exit without installing any products for example if you exit from the Welcome screen the exit code is 1 Cloning Considerations You can copy an existing Oracle home then configure it for its new environment This process is called cloning Note Patching and deinstallation on a cloned Oracle home act the same as a regularly installed Oracle home You can directly patch a cloned installation Invoke Oracle Universal Installer in clone mode using the following command runInstaller clone ORACLE HOME target location gt ORACLE HOME NAME unique name on node gt responseFile full path gt Use setup exe instead of runInstaller for Windows machines The responseFile parameter is optional You can supply clone time parameters on the command line or through the response file named on the command line Clone time activity is logged in the cloneActions lt timestamp gt log file at installation time For more information on cloning see Chapter 6 Cloning Oracle Software
264. rl script that prepares the source for cloning by recording the information required for cloning This script is generally found in the following location SORACLE HOME clone bin prepare clone pl During this phase prepare clone pl parses files in the source Oracle home to extract and store the required values For more information about the parameters to be passed see the section Cloning Script Variables and their Definitions Note The need to perform the preparation phase depends on the Oracle product you are installing This script needs to be executed only for the Application Server Cloning Database and CRS Oracle home cloning does not require this Archive and compress the source Oracle home using your preferred archiving tool For example you can use WinZip on Microsoft Windows system computers and tarorgzip on UNIX Make sure that the tool that you use preserves the permissions and file timestamps When archiving the home also ensure that you skip the 10g dbf listener ora sglnet ora and tnsnames ora for archiving Also ensure that you do not archive the following folders SORACLE HOME Hostname SID SORACLE HOME oc4j j2ee OC4J DBConsole Hostname SID The following sample shows an exclude file list cat excludedFileList txt install make log cf gtoollogs cfgfw CfmLogger 2007 07 13 12 03 16 PM log cfgtoollogs cfgfw oracle server 2007 07 13 12 03 17 PM log c gtoollogs cfgfw oracle
265. rm batch work which requires a default home to be active you can use the Home Selector to change the Windows NT system settings When using the Home Selector to make a specific Oracle home the active one the software installation in question is moved to the front of the PATH variable making it the first directory to be scanned for executable and library files Use the GUI in the Environment tab of the Inventory dialog to establish the order of Oracle homes in your PATH variable How Home Selector Works When you perform an installation on a system Oracle Universal Installer runs the selectHome bat file to register the Oracle home you selected In silent mode you perform this outside Oracle Universal Installer The first Oracle home is named the DEFAULT HOME and registers itself in the Windows NT registry under the key HKEY LOCAL MACHINE Software Oracle This is the default Windows NT registry hive which contains all the generic Oracle settings Also the PATH variable is adjusted and the BIN directory of the SORACLE HOME is added to the environment variable Some additional parameters is also written to the key HKEY LOCAL MACHINE Software 2 12 Oracle Universal Installer and OPatch User s Guide Home Selector Available on Win32 Platforms Oracle KEY ORACLE Home Name With Oracle Universal Installer you can change the DEFAULT HOME name to something else Also it registers all Oracle settings in the KEY
266. ro e i eE E EEEE enne tenente nennen tenete tenente 3 4 4 Variable Valtf s edet entes te EA AREA Ee Re etes EA LI EEN dioe D T 3 4 Variable Lookup Order retener deett erre 3 4 Setting the Recommendation Value sese eee eee nnne 3 5 COMENS coe a etes t D HO OR DO aae OU e e He ceeds isthe uada 3 5 latro 3 5 Responrise Pil Parameters ette tee qe irem eit een Wes ets eret den 3 5 Installing with a Response File eese eene nnne nennen 3 11 Specifying a Response File 1n sentent A erae ee eed 3 11 Optional Parameters When Specifying a Response File 3 12 Setting Response File Variables From the Command Line sess 3 12 Specifying the Value of a Session Variable sss 3 12 Specifying the Value of a Component Variable sssssssssssseee 3 13 Installing Products Checking Prerequisites Before Installation sese eee eee een 4 1 Installing Oracle Products iresi ea ea eee eene nnne nennen 4 2 Getting Help While Installing Oracle Products sssssssseeeeeeee eene 4 2 Aboutthe ORAPARAMINE Fille cuicos tiae re e Hv dee rines 4 3 Modes of Installation ie eg Ah e C e Cet e educ 4 5 Installation Media 55 Ree A eem tete d s 4 6 Installing from a Single CD ROM sseseeeeeeneee eene nnne nnne 4 6 Installing from Multiple CD ROMS ss
267. rovides information on using OPatch for these purposes This chapter includes the following topics About OPatch hequirements for OPatch Prerequisite Checks for OPatch Backup and Recovery Considerations for Patching OPatch Utility for OUI based Oracle Homes Standalone Patching Schema Patching Online Patching Real Application Clusters Patching About Patch Conflicts Problem Resolution About OPatch OPatch is a Java based utility that requires installation of the Oracle Universal Installer It is platform independent and runs on all supported operating systems Another version of OPatch called standalone OPatch is also available It runs on Oracle homes without Oracle Universal Installer Patches are a small collection of files copied over to an existing installation They are associated with particular versions of Oracle products When applied to the correct version of an installed product patches result in an upgraded version of the product Interim patches are bug fixes available to customers in response to specific bugs They require a particular base release or patchset to be installed before you can apply them They generally address specific bugs for a particular customer These patches are not versioned and are generally available in a future patchset as well as the next product release OPatch Features The OPatch 11 1 utility has the following features Patching Oracle Software with OPat
268. rs 1 Skip this step if you have a shared Oracle Clusterware home If you do not have a shared Oracle Clusterware home zip the Oracle Clusterware home from the existing node and copy it to the new node Unzip the home on the new node in the equivalent directory structure as the directory structure in which the Oracle Clusterware home resided on the existing node For example assume that the location of the destination Oracle Clusterware home on the new node is CRS _ HOMES Note For more information on zipping and unzipping see Source Preparation Phase and Cloning Phase If you do not have a shared Oracle Clusterware home navigate to the SORACLE_ HOME c1one bin directory on the new node and run the following command where Oracle home name is the name of the Oracle home new node is the name of the new node new node privis the private interconnect protocol address of the new node new node vipis the virtual interconnect protocol address of the new node and central inventory locationis the location of the Oracle Central Inventory perl clone pl ORACLE HOME CRS HOME gt ORACLE HOME NAME CRS HOME NAME On storageTypeVDSK 2 On storageTypeOCR 2 O sl tableList node2 node2 priv node2 vip node3 node3 priv node3 vip O ret PrivIntrList private interconnect list gt O sl OHPartitionsAndSpace valueFromDlg partition and space information O noConfig Cloning Oracle Software 6 9 Creating an Oracle
269. runs as the root user and restarts automatically upon failure Adding More Nodes to the Cluster for Mass Deployment If you want to add more nodes to the cluster by copying the Oracle Clusterware home to another node in the cluster complete the following procedure 1 Perform a single node cluster Oracle Clusterware installation on nodel In the following steps the variable CRS HOME represents the Oracle Clusterware home directory of the successfully installed Oracle Clusterware software Go to the directory CRS_HOME oui bin and run the script addNode sh The node selection page appears Select the nodes to be added and click Next The Summary page opens Verify if the Summary page contains the correct node information and click Next When prompted run the script rootaddnode sh on your local node If prompted to do so run the script orainstroot shon the node on which you are creating another Oracle Clusterware home directory Run the root sh script on the node on which you are creating another Oracle Clusterware home directory From the Oracle Clusterware home directory you created on the additional node in the path CRS_HOME bin run the following command racgons add config node2 4948 In the preceding syntax example the variable node2 is the name of the node on which you are configuring the additional Oracle Clusterware home directory Installing Cluster Environments 5 19 Installing Product Software on a Clu
270. s 1 Navigate to the SORACLE_HOME patch_storage lt patch id_ timestamp gt directory and execute the Restore command 7 40 Oracle Universal Installer and OPatch User s Guide Problem Resolution For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat On UNIX source ORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt If the files are properly patched but the information is not updated in the inventory execute the following command SORACLE HOME OPatch opatch apply no sysmod Path To Patch Ensure that the patch has been applied and recorded properly in the inventory by executing the following command SORACLE HOME OPatch opatch lsinventory detail If the files are still not patched properly but you are able to see the patch in the lsinventory flag you need to reapply the patch using the no inventory flag SORACLE HOME OPatch opatch apply no inventory Path To Patch When you apply a patch and execute opatch Isinventory it does not return the details of the patch applied Cause OPatch may not have recorded the details of this patch in the inventory Action Perform the following steps 1 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command For UNIX SORACLE HOME patch storage patch id t
271. s the Oracle Clusterware home directory for you Ensure before you start the installation that you provide sufficient disk space on a file system for the Oracle Clusterware directory and the parent directory of the Oracle Clusterware directory space is writable by the Oracle user To create the Oracle Clusterware home directory and specify the correct owner group and permissions for it follow these steps 5 12 Oracle Universal Installer and OPatch User s Guide Pre installation Tasks for Real Application Clusters on Windows 1 Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner group and permissions on them mkdir p mount point crs oracle sw owner product 11 1 0 crs chown R root oinstall mount point crs chmod R 775 mount point crs oracle sw owner If the mount point you identified is u01 the recommended Oracle Clusterware home directory path is as follows u01 crs oracle product 11 1 0 crs 2 Ifnecessary repeat the commands listed in the previous step to create the same directory on the other nodes in the cluster 3 Enter commands similar to the following to set the ORACLE BASE and ORACLE _ HOME environment variables in preparation for the Oracle Clusterware installation Bourne Bash or Korn shell ORACLE BASE u01 app oracle ORACLE HOME u01 crs oracle product 11 1 0 crs export ORACLE BASE
272. scenario Patch A installed in the Oracle home fixed bugs 1 2 and 3 Patch B installed in the Oracle home fixed bugs 10 11 and 12 a Patch E to be installed fixes bugs 3 and 4 Patch E conflicts with Patch A File Conflict A file conflict occurs if a set of files to be patched by the current interim patch includes files already patched by one or more previously installed interim patches and it is not a bug superset Example Consider the following scenario Patch A installed in the Oracle home fixed bugs 1 2 and 3 which modified files a b and c a Patch FE to be installed fixes bugs 1 2 3 and 4 and modifies files a d and f Patch F conflicts with Patch A Patching Oracle Software with OPatch 7 37 Problem Resolution Patch Conflict Behavior for Apply and Napply The expected behavior for the Apply and Napply commands is listed in Table 7 22 Table 7 22 Expected Behavior for Apply and Napply Commands File Conflict or Bug Command Superset Subset Duplicate Conflict Patch Apply OPatch performs an After the merge OPatch performs an OPatch reports the automatic rollback request OPatch automatic rollback conflict After the then an apply performs an then performs a merge request OPatch automatic rollback reapply performs an automatic then performs an rollback then an apply apply Napply OPatch performs an OPatch reports the OPatch performs an OPatch reports the automatic rollb
273. se the values for this option in double quotes Specifies the parameters to be passed to the pre script This script is executed before the patch is applied You need to enclose the values for this option in double quotes Specifies the user defined property file for OPatch to use The path to the property file should be absolute This property file takes precedence over the one that OPatch supplies Suppresses user interaction and defaults any answers to yes Prints additional OPatch output to the screen as well as to the log file Lsinventory Command for Standalone OPatch The Lsinventory command lists the inventory for a particular Oracle home or displays all installations that can be found This command does not have any required options Syntax Use the following syntax for this command opatch lsinventory all oh ORACLE HOME patch oh property file path to property file gt Options detail jre LOC Table 7 11 lists the options available for the Lsinventory command Patching Oracle Software with OPatch 7 25 Standalone Patching Table 7 10 Lsinventory Options for Standalone Patches Option Description all Reports the name and installation directory for each Oracle home directory found detail Reports the installed products and other details You cannot use this option with the a11 option jre Specifies the location of a particular JRE Java for OPatch to use instead
274. se 7 26 Rollback Command for Standalone OPatch sess 7 27 Version Command for Standalone OPatch sse eee 7 28 ERA NN veal iene tial Ress 7 28 Inventory Operations eerte nre dtt P tenere tee esa bei i reset Fen regendo 7 28 Patching Operations ce nasties ea get ite ata e p e iei ib dee de ERE RS 7 29 tility Opetatons titt tte iie aia 7 31 Schema Patching ene de tee pt ede eth tase 7 31 Schema Patching Options x iei ete e rimi eai a eet ebrei ee reddes 7 32 Staridalone SOL Ex c tion 5 eet Te ed e e i e is 7 32 Online P tching oen A ee aee it ecrire eu eee diee ee aee eee idea 7 32 Real Application Clusters Patching sees eee nennen nennen nnne nnns 7 33 viii AI Node Rath an ec tec tret Le tete IO ee s Cranes 7 33 Rolling Patching ie rette ia dien ced i ee terere peri ed etes 7 34 Minimum Downtime Patching eterne ire eere creen e cete tre iae cias 7 35 About Patch Conflicts totem iia 7 35 Types of Conflicts snot eee etate ete iie bb a ptite oa federe 7 35 DU POTS Cts LC AN 7 35 SubSeti zin dl niti ee 7 36 Duplicado ERREUR NM 7 37 Bite ConflicE unten a RU pone or et Pei eee d er tes 7 37 File Contlietz z un RR ER RARI AT S SS e BARS 7 37 Patch Conflict Behavior for Apply and Napply eese eee een 7 38 Patch Conflict Detection and Resolution cccccccccsscssessecsecssecsecssessscseseese
275. seeceseseeesecseesaecsscsaeerees 7 38 Problem Resol o ebrei rb eee PIER Se E HRS 7 38 Logging and Traci is adr eo n A in 7 39 Command Index ii a ete aei ER HER E be 7 39 Levels of Logging iuh b eret e eth bn n np mtt dine oibus 7 39 Recovering from a Failed Patching Session sse eee enne 7 39 Single Instance Setup sete att eae tite ie rette hue erba 7 40 Real Application Clusters Setup sss eene nennen nennen 7 42 Resolving OPatch Application Errors eessssssee eene nennen nennen 7 45 8 Oracle Internationalization and Translation Installation Dialogs Language sese nennen nnne nnne nenne nennen tenentes 8 1 Product Language Selections eee epe edere eei ee bit eet ati 8 1 Language Add ON iii etch igni ite i baee ei bd dete rie odere erue 8 2 A Frequently Asked Questions Oracle Universal Installer eet e e e e eed estere a eee e e e Evo A 1 O ird ri NEM teeter Ee OE E CL PDT NC HEUS EOM SM oP ae aR acid A 3 B Troubleshooting and Debugging Oracle Universal Installer Debugging Mechanisms in Oracle Universal Installer sese B 1 Installation LoS ii a f PRAET IR E av renati bcd p Pee atre eate et B 1 Automated Inventory Backups sseeeeeeee eee nennen nennen B 3 Central Inventory Backup dit eet Eie E eee tete rere tea ast B 3 Oracle Home Inventory Backup ete ee eie nett eiie pietre decade iet B 3 Oracle Universal Installer Errors
276. separated with commas but without spaces You can use this option on Oracle Real Application Clusters environments Prints the actions to the screen without executing them Instructs OPatch how many times it should retry when there is an inventory lock failure Instructs OPatch to run the SQL script and SQL procedures if they exist in the given patch For information on SOL and PL SQL patching see Schema Patching Specifies the custom SQL script that OPatch should run after patching completes For information on SQL and PL SQL patching see Schema Patching Suppresses user interaction and defaults any yes no questions to yes A Real Application Clusters setup does not support this option Prints additional OPatch output to the screen as well as to the log file Patching Oracle Software with OPatch 7 19 OPatch Utility for OUI based Oracle Homes Nrollback Command for OUI based Oracle Homes This command rolls back interim patches from several Oracle homes at the same time Syntax Use the following syntax for this command opatch nrollback id comma separated list of patch IDs delay value invPtrLoc Path to oraInst loc jdk LOC jre LOC local minimize downtime no relink oh ORACLE HOME gt retry lt value gt silent verbose pre parameters for the pre script in escaped double quotes opatch pre end post parameters for the post script in
277. ser oracle You must create this user the first time you install Oracle software on the system This user owns all of the software installed during the installation The usual name chosen for this user is oracle This user must have the Oracle Inventory group as its primary group You need to create other groups and users in addition to the ones created above For more information on creating the required groups and users see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Creating Identical Users and Groups on Other Cluster Nodes The Oracle software users and groups must exist and be identical on all cluster nodes To create these identical users and groups you must identify the user ID and group IDs assigned to them on the node where you created them then create the user and groups with the same name and ID on the other cluster nodes You must create Installing Cluster Environments 5 5 Pre installation Tasks for Real Application Clusters on UNIX identical users and groups on other cluster nodes only if you are using local users and groups If you are using users and groups defined in a directory service such as NIS they are already identical on each cluster node Identifying the User and Group IDs To determine the user ID UID and the group IDs GID for the groups follow these steps 1 Enter following command id oracle The output from this command is similar to the following uid 440
278. set for the inventory on UNIX platforms Note The UNIX group name is used for first time installations only REMOVE_HOMES Use this parameter to identify the Oracle homes you want to remove from the inventory during a deinstallation session For each home specify the home name using the full path information REMOVE_HOMES home oracle ora9i home oracle ora8i 3 8 Oracle Universal Installer and OPatch User s Guide Response File Format DEINSTALL LIST Use this parameter to enter a list of components to be removed during a silent deinstall session For each component specify the internal component name and version DEINSTALL LIST samplel 1 0 0 0 0 SHOW DEINSTALL CONFIRMATION Set this parameter to FALSE if you want to hide the deinstall confirmation dialog box during a silent deinstallation SHOW DEINSTALL PROGRESS Set this parameter to FALSE if you want to hide the deinstallation progress dialog box during a silent deinstallation DEPENDENCY LIST The DEPENDENCY LIST is the list of dependents on which the component depends These dependent components represent the list of components that appear as selected during installation Following is a list of some of this parameter s characteristics The DEPENDENCY LIST variable is only generated when dependencies are present and if the dependency is not a required one You cannot list components to appear as deselected items in a dialog Specifying req
279. sion lt variable name value on UNIX setup exe session lt variable name gt lt value gt on Windows For example to prevent the Universal Welcome page from displaying runInstaller session SHOW WELCOME PAGE false on UNIX setup exe session SHOW WELCOME PAGE false on Windows 3 12 Oracle Universal Installer and OPatch User s Guide Installing with a Response File Note that the session tag is optional and is used mainly to remove any possible ambiguity Specifying the Value of a Component Variable To specify the value of a component variable use the following command syntax runInstaller component name component version variable name value on UNIX setup exe component name component version variable name value on Windows For example to modify the value of a variable VAR1 in version 1 1 of a component called COMP2 runInstaller COMP2 1 1 0 0 0 VAR1 test on UNIX setup exe COMP2 1 1 0 0 0 VAR1 test on Windows Note that the component name and lt component_version gt optional tags are used mainly to remove any possible ambiguity If two variables exist with the same name for different components versions use these tags to distinguish between them Customizing and Creating Response Files 3 13 Installing with a Response File 3 14 Oracle Universal Installer and OPatch User s Guide 4 Installing Products This chapter includes the follow
280. sponse File About Response Files This section answers the following questions a What Is a Silent Installation a What Is a Response File Why Perform a Silent Installation What Is a Silent Installation A silent installation runs in the console and does not use the GUI The interactive dialogs you normally see are not displayed in a silent installation Instead of prompting you to select a series of installation options Oracle Universal Installer installs the software using a predefined set of options stored in a response file or passed on the command line You can view the progress of a silent installation in the console What Is a Response File A response file is a specification file containing information you normally through the Oracle Universal Installer user interface during an interactive installation session Each answer is stored as a value for a variable identified in the response file For example values for Oracle home or installation type can be set automatically within the response file Customizing and Creating Response Files 3 1 Modifying a Response File The response file template for the installation of your product can be found on your stage CD ROM under the root of CD gt response directory with pre populated values For example Products xml Location Response product installtype rsp Note Check the installation guide for the product that you are installing to get the corr
281. sponse file specify Oracle homes to be removed with the REMOVE HOMES variable For more information about response files see Installing with a Response File on page 3 11 See Chapter 3 Customizing and Creating Response Files for information about the DEINSTALL LIST parameter Installing Products 4 11 Running Oracle Universal Installer After Installation As with other response file parameters you can also specify the DEINSTALL LIST parameter on the Oracle Universal Installer command line For example on a UNIX machine enter runlInstaller deinstall DEINSTALL LIST component1 1 0 1 2 To remove Oracle homes from the inventory use the REMOVE HOMES variable For more information about specifying response file parameters see Setting Response File Variables From the Command Line on page 3 12 Hiding the Deinstallation Confirmation and Progress Dialog Boxes Use the following commands to hide the deinstallation confirmation and progress dialog boxes during a command line deinstallation On a Windows system setup exe deinstall session SHOW DEINSTALL PROGRESS false session SHOW DESINSTALL CONFIRMATION false On a UNIX system runInstaller deinstall session SHOW DEINSTALL PROGRESS false session SHOW DESINSTALL CONFIRMATION false Running Oracle Universal Installer After Installation The following sections describe the different ways that Oracle Universal Installer can be used after installation Specificall
282. st be specified for a silent installation to be successful For values that are given as value unspecified you can optionally specify a value where value can be one of the following types listed in Table 3 1 Table 3 1 Variable Types and Representations Type Representation Number 10 Boolean TRUE or FALSE case insensitive String Value String List value1 value2 The recommendation parameter can be specified as Forced or Default Ifyou specify Forced no dialog appears during installation The value is automatically used You cannot change the value a Ifyou specify Default the dialog appears during installation with the value as the default You can choose another value if desired Ifnothing is specified for recommendations Forced is used as the default Comments begin with a hash or pound symbol They contain information about the type of the variable state whether the variable appears in dialog and describe the function of the variable A variable and a value are associated with a comment For example TopLevelComponent StringList Used in Dialog TopLevelComponent Demo 1 0 The header is a comment that describes the different formats and comment conventions used in a response file For example Parameter UNIX GROUP NAME Type String Description UNIX group to be set for the inventory directory Valid only on UNIX platforms Example UNIX GROUP NAME
283. stalling with a Response File on page 3 11 for information on starting Oracle Universal Installer using your modified response file Creating a Response File With Record Mode You can create a new response file based on the installation options you select by using Oracle Universal Installer s record mode When you use record mode Oracle Universal Installer records the installation session into a response file You specify the name of the response file on the command line The recorded response file is generated immediately after the Summary page so you do not need to actually install your Oracle product to create the response file That is you can start the installation in Record mode and proceed through the installation options until you get to the Summary page In the Summary Page click Exit to stop the installation from proceeding with the installation However all the options you selected will be saved in the resulting response file You can use the newly created response file to run identical installation sessions on other computers in your organization Record mode can be also used during a silent installation In those cases the variable values specified in the original source response file will be recorded into the new response file The following sections describe how to use record mode on Windows and UNIX systems Using Record Mode To record a new response file 1 Atthe command prompt use the cd command to change to th
284. ster Installing Product Software on a Cluster After you have installed clusterware and completed pre installation tasks you are ready to install the cluster ready product on the cluster To do this you can use Oracle Universal Installer in interactive mode command line mode or silent mode using a response file See Also See Modes of Installation on page 4 5 for more information on the different modes Cluster Detection When Oracle Universal Installer detects that the destination you entered on the File Locations page is part of a cluster one of two dialogs appear a Ifthe Oracle home name entered is new the Specify Hardware Installation Mode page appears Use this page to select between cluster and non cluster installation Cluster installation Select the nodes for your installation from the list of nodes on which clusterware has been installed Non cluster installation Install on a single node only even though that node is part of a cluster Ifthe Oracle home name entered is a pre existing home the Selected Nodes page appears This is an information only page that displays the nodes associated with the Oracle home The installation is performed on all selected nodes If any of the selected nodes are down the installation is not allowed to proceed Note In Oracle Universal Installer click Installed Products to display the Inventory panel which lists all installed Oracle homes Clustered Oracle homes
285. t OPatch Response Roll back an interim patch applied earlier on a standalone Oracle home SORACLE HOME is set and the Oracle home has been patched using a standalone OPatch Enter the following command opatch rollback id 123451 1 OPatch detects this is a standalone Oracle home 2 OPatch examines the standalone inventory file to determine if patch 123451 was applied 3 OPatch rolls back patch 123451 4 OPatch updates its standalone directory 7 30 Oracle Universal Installer and OPatch User s Guide Schema Patching Utility Operations The following tables explain the purpose of the use case along with preconditions and the process that occurs during the patching process Table 7 19 Loading an Arbitrary XML File Use Case Category Description Purpose Load an XML file making sure it is XML parsable Preconditions SORACLE HOME is set User Input Enter the following command opatch util loadXML Note that the loadXML utility is often used as a debugging and troubleshooting tool OPatch Response 1 OPatch detects this is a standalone Oracle home 2 OPatch prompts for the complete path to the XML file that you want to load 3 OPatch opens the file and uses the XML parser to parse it 4 OPatch reports that the file is XML parsable Table 7 20 Verifying that the Patch is Applied Use Case Category Description Purpose Ensure that the patch was applied to the Oracle home Preconditions SORACLE H
286. t is located in the same directory as the executable file For example For UNIX systems cd Product Shiphome Location install solaris runInstaller cd Product Shiphome Location install solaris OraParam ini For Windows systems cd lt Product_Shiphome_Location gt install win32 setup exe cd lt Product_Shiphome_Location gt install win32 OraParam ini In the staging area the default OUI LOCATION is relative to the location of the oraparam ini file as follows stage Once installed the oraparam ini file is located in the oui directory Table 4 2 describes the parameters in the oraparam ini file and how to use them Table 4 2 Parameters in oraparam ini Section Parameter Description Oracle This section contains various parameters related to your installation DISTRIBUTION Set to TRUE if the oraparam ini file is on a distribution medium A distribution medium can be a CD ROM or a Web server Once installed this parameter is set to FALSE SOURCE Location of your staging area the products xml file This location is relative to the directory where oraparam ini exists Installing Products 4 3 Installing Oracle Products Table 4 2 Cont Parameters in oraparam ini Section Parameter Description LICENSE LOCATION LICENSE TITLE JRE LOCATION OUI LOCATION OUI CORE LOCATION OUI VERSION DISPLAY VERSION JRE MEMORY OPTIONS DEFAULT HOME LOCATION DEFAULT HOME
287. t_group oracle In UNIX if you do not want to use the Central Inventory located in the directory specified by the inventory pointer file you can use the invPtrLoc flag to specify another inventory pointer file The syntax is as follows runInstaller silent invPtrLoc Location of oraInst loc ORACLE _ HOME Location of Oracle Home gt ORACLE HOME NAME Name of Oracle Home gt Note Ifthe contents of the oraInst 1loc file is empty Oracle Universal Installer prompts you to create a new inventory Central Inventory The Central Inventory contains the information relating to all Oracle products installed on a host It contains the following files and folders Inventory File Logs Directory Inventory File This file lists all the Oracle homes installed on the node For each Oracle home it also lists the Oracle home name home index and nodes on which the home is installed It also mentions if the home is an Oracle Clusterware home or a removed Oracle home It can only detect removed Oracle homes created using Oracle Universal Installer version 11 1 and later This file is present in the following location 2 4 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Inventory central inventory location ContentsXML inventory xml The following code shows a sample inventory xml file lt xml version 1 0 standalone yes gt lt Copyright c 2007 Oracle Corporation
288. tallation 1 5 4 5 clusters 1 6 interactive 1 5 4 5 silent 1 5 4 6 suppressed 1 5 4 6 multi CD support response file 3 6 multiple Oracle homes 2 3 N Napply command for OUI based homes 7 12 patch conflict behavior 7 38 network hardware requirements 5 9 IP address requirements 5 10 node time requirements 5 10 parameter requirements 5 9 requirements for Windows 5 14 Network File System NFS 5 21 NEXT SESSION resonse file parameter 3 7 NEXT SESSION ON FAIL parameter 3 7 NEXT SESSION RESPONSE parameter 3 7 NLS ENABLED parameter in ORAPARAM INI 4 5 NLS ENABLED variable 8 1 NO BROWSE parameter in ORAPARAM INI 4 4 nodes adding 1 4 Nrollback command for OUI based homes 7 20 O OPatch additional checks for RAC 7 4 Apply command for OUI based homes 7 9 for standalone OPatch 7 24 backup and recovery considerations 7 8 Index 3 bug conflict 7 37 conflict detection and resolution 7 38 conflicts 7 35 bug conflict 7 37 duplicate 7 37 file conflict 7 37 subset 7 36 superset 7 35 types 7 35 debugging logging and tracing 7 39 recovering from failed patching 7 39 resolving application errors 7 45 description 1 3 duplicate conflicts 7 37 environment variables 7 2 features 7 1 file conflict 7 37 getting interim patches 7 2 Lsinventory command for OUI based homes 7 15 for standalone OPatch 7 25 Napply command for OUI based homes 7 12 Nrollback command
289. taller and OPatch User s Guide Deinstalling Real Application Clusters Software 3 Click Deinstall Products The Inventory screen appears 4 Expand the tree of installed components until you find the components to remove For example if you installed a database with the Enterprise Edition option and later installed additional components with the Custom option expand the Oracle home component to display all the components installed in the Oracle home 5 Select the components to remove 6 Click Remove The Confirmation screen appears 7 Click Yes to remove the selected components to initiate the removal process 8 After the components are removed from your computer the Inventory screen appears without the removed components 9 Click Close to close the Inventory screen 10 Click Cancel to exit Oracle Universal Installer 11 Click Yes to confirm that you want to exit For detailed instructions on deinstalling an Oracle product see the respective Oracle product installation guide Deinstalling Oracle Clusterware Before deinstalling Oracle Cluster software ensure that you have removed the respective Oracle product s home in each node by following the steps in the preceding section The following section explains deinstallation on Windows and UNIX Deinstalling Oracle Clusterware from a UNIX Environment Deinstall each Oracle product Real Application Clusters home by running the procedure in the previous section Then comp
290. taller inventory has the following hierarchical structure Managing Oracle Homes 2 3 Oracle Universal Installer Inventory Central Inventory Pointer File Central Inventory Oracle Home Inventory Central Inventory Pointer File Every Oracle software installation has an associated Central Inventory where the details of all the Oracle products installed on a host are registered The Central Inventory is located in the directory that the inventory pointer file specifies Each Oracle software installation has its own Central Inventory pointer file that is unknown to another Oracle software installation For Oracle homes sharing the same Central Inventory the Oracle Universal Installer components perform all read and write operations on the inventory The operations on the Central Inventory are performed through a locking mechanism This implies that when an operation such as installation upgrade or patching occurs on an Oracle home these operations become blocked on other Oracle homes that share the same Central Inventory The following list shows the location of the inventory pointer file for various platforms Solaris var opt oracle oraInst loc a Linux etc oraInst loc Windows The pointer is located in the registry key HKEY_LOCAL MACHINE Software Oracle inst loc The following string shows an example of the path for the oraInst loc file inventory_loc home oracle_db1l1g product 11 1 0 db 1 ins
291. tch Information reete ie reet petet E Pe ie ere i deeem 7 29 Getting Detailed Patch Information sse eene enne 7 29 Applying an Interim Patch Case 1 sess eee enne nnns 7 29 Applying an Interim Patch Case 2 sss eene nennen 7 30 Applying an Interim Patch Case 3 esses eee ene e nnns 7 30 Rolling Back an Applied Interim Patch esee nnns 7 30 Loading an Arbitrary XML File seen e enne nnns 7 31 Verifying that the Patch is Applied eee nee 7 31 Schema Patching Opt ons te eed De ee de ten IA 7 32 Expected Behavior for Apply and Napply Commands sees 7 38 Oracle Universal Installer Translated Languages ccccsescesesesceesesseneteseeceesesesnaneneneees 8 2 Options in Oracle Universal Installer eese ee eene C 1 Command Line Variables in Oracle Universal Installer sees C 3 Audience Preface This manual describes how to manage Oracle and third party software using the Oracle Universal Installer and OPatch This guide provides instructions for installing setting up and starting the Oracle Universal Installer software It also provides instructions on cloning and patching Oracle software This manual is intended for users installing Oracle software products using the Oracle Universal Installer and covers only the generic functionality and concepts Use this manual in
292. ter running the checker you can find the results along with the predefined inputs in the prerequisite results xml file These files are located in the oraInventory logs directory You can reuse the prerequisite results xml file as an input file for subsequent executions of the checker Installing Oracle Products The following sections describe how to start Oracle Universal Installer and install an Oracle product Specifically this section describes Getting Help While Installing Oracle Products About the ORAPARAM INI File Modes of Installation Installation Media Special Instructions for UNIX Users Getting Help While Installing Oracle Products Atany time while installing your product click Help for information about the screens specific to your installation Oracle Universal Installer provides two kinds of online help Generic online help provided with every copy of Oracle Universal Installer These topics describe the screens and dialog boxes that all Oracle Universal Installer users see regardless of the product they are installing Online help specific to a particular installation These topics are created by the product developer and describe the screens and dialog boxes specific to the product you are installing For example the help topic for the Installation Types page is often a custom help topic the installation developer creates that describes the specific installation types for the product you are
293. ters Components Oracle Clusterware The Oracle Universal Installer installs Oracle Clusterware on each node on which the Oracle Universal Installer detects that third party vendor clusterware is present If third party vendor clusterware is not present you must use the Oracle Universal Installer to enter the nodes on which you want the Oracle Clusterware to be installed The Oracle Clusterware home can be either shared by all nodes or private to each node depending on your responses when you run the Oracle Universal Installer When third party vendor clusterware is present Oracle Clusterware can interact with the third party vendor clusterware In using third party vendor clusterware note that Oracle Clusterware can integrate with third party vendor clusterware for all operating systems except Linux and Windows You need to have Oracle Cluster Registry and Voting Disks shared across all nodes Installed Real Application Clusters Components All instances in Real Application Clusters environment share the control file server parameter file redo log files and all data files These files reside on a shared cluster file system or on shared disks Either of these types of file configurations are accessed by all the cluster database instances Each instance also has its own set of redo log files During failures shared access to redo log files enables surviving instances to perform recovery 5 2 Oracle Universal Installer and OPatch User s G
294. that you modify these files to suppress all output on STDERR as in the following examples Bourne Bash or Korn shell if t 0 then stty intr C fi a Cshell test t 0 if status 0 then stty intr C endif 5 8 Oracle Universal Installer and OPatch User s Guide Pre installation Tasks for Real Application Clusters on UNIX Note When SSH is not available the Installer uses the rsh and rcp commands instead of ssh and scp This error can also occur if the remote shells load hidden files that contain stty commands Configuring the Oracle User Environment You run Oracle Universal Installer from the oracle account However before you start Oracle Universal Installer you must configure the environment of the oracle user For more information on configuring the environment see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Checking the Hardware Requirements Each system must meet certain minimum hardware requirements For more information on hardware requirements see the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 Checking the Network Requirements There are some minimum networking hardware and Internet protocol IP address requirements Check that you have the networking hardware and Internet protocol IP address required for an Oracle Real Application Clusters installation Network Hardware Requirements Each node in the cluster must
295. the Web You can publish your staging area from a Web server and then in the Oracle Universal Installer s Source location specify the HTTP location for the products xml file For example you can enter http www oracle com product ouiinstall stage products xml The Oracle Universal Installer recognizes a Web staging area just like a local network or CD ROM stage System administrators of large customers who may want to deploy Oracle software to more than one target can use a combination of the Web installation and response file features 1 Copy the staging area to a shared file system and make it accessible on the Intranet or a Web server 2 Include predetermined response files on the same location Different groups of users might rely on different response files 3 Clients run Oracle Universal Installer locally and use the local response file that is mailed or downloaded so they can perform a silent installation The Web installation capability relies on some guidelines that must be followed at installation development time Check the installation guide for your product to see if the installation of your product is certified for Web installation To test if your stage is Web enabled you can try the following procedure 1 Copy the stage to your Web server 2 Start the Oracle Universal Installer locally and point to the location of the products xml file For example http smpweb us oracle com product ouiinstall stage
296. tiere pepe Pda 5 20 Cluster InstallatiQt 1n en Rent mt ee etn ed Re eret etu Pe rie e EE EREERD 5 21 Cluster Installation in Silent Mode sss ennt tnnt 5 21 Cluster Deinstall ti n 3 2 uen huele e tei m o pe e Ee deir 5 21 Command Line Options for Cluster Installations UNIX Only sese 5 21 Patchsets and Upgrades cete ettet dente eee epe Le re e eee eines 5 22 Post installation Tasks ere ede ede eeu e ente ee e PH e ERE Een uen 5 22 VG TIPIC at OM PERO A da e E LaS 5 22 Back Up Disk after Installation sse nennen nne nnne nennen 5 22 Download and Install Patches adria 5 22 Configure Oracle Prod ucts unir it tee De ame ie 5 23 Deinstalling Real Application Clusters Software esses eee 5 23 Deinstalling Oracle Product Software on UNIX sese eee nens 5 23 Deinstalling Oracle Product Software on Windows ococicicinononinnononnnnoncononanonononananonononanananononenoso 5 24 Deinstalling Oracle Clusterware eese eene nene nnne n nennen 5 25 Deinstalling Oracle Clusterware from a UNIX Environment sees 5 25 Deinstalling Oracle Clusterware from a Windows Environment sess 5 25 Deinstalling Oracle Clusterware with No Previous Cluster Software Versions 5 26 Deinstalling Oracle Clusterware with Clusterware Downgrade to 10 2 5 26 Converting Single instance Nodes to Real Applicatio
297. timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp gt make txt file if available as follows bin sh make txt 4 Roll back the patch in the local node using the local flag SORACLE HOME OPatch opatch rollback local id Patch ID 5 Roll back the patch on the other nodes also using the local flag Note Ensure that all the nodes use the same OPatch version When I apply a patch on a Real Application Clusters setup the patching in one node is fine both the files and the inventory are fine but I am not sure about the other nodes Cause This may occur because of a failed system or inventory update Action Perform the following steps 1 Copy the Oracle home from the node that is fine to the other nodes 2 After copying the Oracle home make sure that the ORACLE _ HOME inventory ContentsXML comps xml file has the latest timestamp Note On Unix use touch to change the timestamp 7 44 Oracle Universal Installer and OPatch User s Guide Problem Resolution 3 Update the nodes of the cluster For more information on updating the nodes of the cluster see Updating the Nodes of a Cluster on page 2 12 4 Ensure that all the prerequisite checks pass that are listed in the section Prerequisite Checks for OPatch on page 7 3 When I apply a patch on a Real Application
298. tion Summary Page ShowSummary SHOW SUMMARY PAGE null Global Settings Source E bootstrap cd Disk1 stage products jar Destination E Universal Text files are also written in the temp directory B 2 Oracle Universal Installer and OPatch User s Guide Oracle Universal Installer Errors temp VOraInstallVoraInstall timestamp err temp VOraInstallVoraInstall timestamp out If a problem occurs during the installation you should look for messages with the SEVERE keyword and Java exceptions in these files Automated Inventory Backups You can recover from a corrupt inventory or failed installations by using the following types of automated inventory backups Central Inventory Backup Oracle Home Inventory Backup Central Inventory Backup The Central Inventory is automatically backed up whenever you execute the Oracle Universal Installer in any of the following modes a install new home deinstall remove home addNode attachHome detachHome updateNodeList The backed up directory and file are Central Inventory Location ContentsXML The backup is located here Central Inventory Location backup time stamp Oracle Home Inventory Backup The Oracle Home Inventory is automatically backed up on an existing Oracle home whenever you execute the Oracle Universal Installer in either of the following modes install patchsets upgrades and one offs a deinst
299. tion This flag also needs to be set to true in order to process another response file see NEXT SESSION RESPONSE This argument is used for chain installs Specifies the next session response Set to true to allow users to invoke another session even if the current installation session has failed This flag is only relevant if NEXT SESSION is set to true This argument is used for chain installs Specifies the full path of the next session s response file If only a file name is specified the response file is retrieved from the lt TEMP gt oralnstall directory This variable is active only if NEXT SESSION is set to true This argument is used for chain installs Name used to specify the complete path to the other disks Specifies the list of components to be removed during a de install session This argument is used with the deinstall flag Understanding Oracle Universal Installer Commands C 5 Command line Variables Available in Oracle Universal Installer Table C 2 Cont Command Line Variables in Oracle Universal Installer Command Line Variable Description SHOW DEINSTALL Specifies the de install confirmation Set to true if de install CONFIRMATION confirmation is needed during a de install session This argument is SHOW DEINSTALL PROGRESS REMOVE HOMES CLUSTER NODES CLUSTER NEW NODES REMOTE NODES REMOTE CLEAN MACHINES LOCAL NODE EXISTING REMOTE NODES CRS CLUSTER NEW PRIVATE NOD
300. tional OPatch output to the screen as well as to the log file Version Command for Standalone OPatch This command shows the current version number of the OPatch utility Use the following syntax for this command Path to OPatch opatch version Use Cases The following sections provide scenarios that administrators can encounter when implementing standalone patching for the following types of operations Inventory Patching Utility Inventory Operations The following tables explain the purpose of the use case along with preconditions and the process that occurs during the patching process 7 28 Oracle Universal Installer and OPatch User s Guide Standalone Patching Table 7 13 Getting Patch Information Use Case Category Description Purpose Show a list of interim patches installed on a standalone Oracle home Preconditions SORACLE HOME is set and the Oracle home has been patched using the standalone OPatch User Input Enter the following command opatch lsinventory OPatch Response 1 OPatch detects that this is a standalone Oracle home 2 OPatch looks for the standalone inventory file 3 OPatch prints out a list of installed interim patches Table 7 14 Getting Detailed Patch Information Use Case Category Description Purpose Show a detailed list of interim patches installed on a standalone Oracle home Preconditions SORACLE HOME is set and the Oracle home has been patched us
301. tions iie tere ipee Poet ui Past e Es tes Ere E EE 4 15 About Oracle Universal Installer Log Files nn 4 15 Installing Cluster Environments Oracle Universal Installer and Real Application Clusters sess 5 1 Oracle Cl ust tware u cin ott de eR ORO RM E dt BO rd 5 2 Installed Real Application Clusters Components sess 5 2 General System Installation Requirements for Real Application Clusters 5 3 Hardware Requirements for Real Application Clusters Setup sess 5 3 Software Requirements for Real Application Clusters Setup esses 5 8 Cluster Setup and Pre installation Configuration Tasks for Real Application Clusters 5 4 Pre installation Tasks for Real Application Clusters on UNIX sees 5 4 Logging In to the System as root sse nene nennen nennen 5 4 Creating Required UNIX Groups and Users sese een nennen 5 5 Creating Identical Users and Groups on Other Cluster Nodes sess 5 5 Identifying the User and Group IDs sees nnn nnns 5 6 Creating the User and Groups on the Other Cluster Nodes sss 5 6 Configuring SSH on all Cluster Nodes essen nennen 5 6 Configuring SSH on Cluster Member Nodes sss 5 6 Enabling SSH User Equivalency on Cluster Member Nodes sss 5 7 Preventing Oracle Clusterwa
302. tiple systems All the options you selected during the installation are saved in the resulting response file For information about recording your Oracle Universal Installer sessions see Creating a Response File With Record Mode on page 3 3 More accurate disk space calculations Oracle Universal Installer now uses a more accurate method of calculating the disk space your Oracle products require This feature reduces the risk of running out of disk space during an installation Automatically launched software after installation Some Oracle products now take advantage of a new feature that allows the software to launch automatically immediately after the installation Cleaner deinstallation and upgrades Deinstallation completely removes all software leaving no bits behind This also completely removes files associated with configuration assistants and patchsets Oracle homes can also be removed from the inventory and registry Integrated prerequisite checking Provides a prerequisite checking tool to diagnose the readiness of an environment for installation The prerequisite checks are run as part of the installation process but can also be run as a separate application Support for single click installation Provides a facility where you can perform single click installations for certain products for basic configurations You also have an advanced mode for more options Oracle offers two utilities for software deployment
303. tory is corrupted or lost for some reason you can simply restore the ORACLE HOME inventory ifit was backed up If a backup does not exist you may have to reinstall the software OPatch Utility for OUI based Oracle Homes Note OPatch also provides a standalone method of patching that does not require the Oracle Universal Installer OUI The options for these commands are a subset of those offered here for the standard method of patching using OUI For information on standalone patching and the available options for commands see Standalone Patching You can run the OPatch utility located in the Path to Oracle Home gt OPatch directory with various commands and options The following string shows the syntax for the OPatch utility Path to OPatch opatch help r eport command option where help Displays the help message for the command report Prints the actions without executing a command One of the OPatch commands described in Table 7 1 option One of the OPatch command options described starting with Table 7 2 7 8 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Table 7 1 OPatch OUI based Commands Command Description apply Installs an interim patch See Apply Command for OUI based Oracle Homes for more information napply Installs n number of patches hence napply See Napply Command for OUI based Oracle
304. uction shiphomes only Use this parameter when you want your users to specify the location of an Oracle Applications top APPL TOP directory When this parameter is set to TRUE the File Locations page includes fields for selecting an APPL TOP directory This is an optional parameter for use with Apps installs only If not specified the default is assumed to be FALSE This parameter is the URL where the user is directed from the Product Registration page in Oracle Universal Installer The REGISTRATION KEY parameter is validated at this site Set this parameter along with the REGISTRATION KEY parameter to invoke the Product Registration page Both are required This key is validated against an encrypted key at the REGISTRATION_URL location Set this parameter along with the REGISTRATION URL parameter to invoke the Product Registration page Both are required This section lists the images associated with an installation To show advertisements during an installation specify each image as a separate variable Modes of Installation You can use Oracle Universal Installer to install Oracle products in any of the three following modes Interactive Use Oracle Universal Installer s interactive mode to use the graphical user interface to walk through the installation providing information in the Installing Products 4 5 Installing Oracle Products installation dialogs when prompted This method is most useful when installi
305. uggests the best options to resolve a conflict Reporting on installed products and interim patches Getting Interim Patches Oracle releases interim patches frequently to fix a bug or a set of bugs You can get the interim patches by specifying the patch ID in OracleMetalink from the following location http www oracle com support metalink index html Environment Variables OPatch Uses OPatch uses the following environment variables ORACLE HOME Oracle home location PATH Path information OPATCH DEBUG Log level that specifies the amount of logging OPatch should perform Requirements for OPatch The OPatch utility requires the following environment a The Oracle home environment variable ORACLE HOME must point to a valid Oracle home directory and match the value used during installation of the Oracle home directory 7 2 Oracle Universal Installer and OPatch User s Guide Prerequisite Checks for OPatch JRE version 1 4 or higher Java commands for Windows and ar cp fuser and make commands for UNIX must be made available The library path must be set correctly for Oracle Real Application Clusters environments OPatch uses some APIs to detect if the system is a Real Application Clusters system Ensure that the library path is set correctly as follows For Solaris LD LIBRARY PATH SORACLE HOME 1ib32 ORACLE HOME lib For HP UX SHLIB PATH SORACLE HOME 1ib32 usr lib See Also For the latest
306. uide General System Installation Requirements for Real Application Clusters General System Installation Requirements for Real Application Clusters Each node that is going to be part of your Real Application Clusters installation must meet the following hardware and software requirements You will perform step by step tasks for hardware and software verification for the platform specific pre installation procedures Hardware Requirements for Real Application Clusters Setup Each node in a cluster requires the following hardware a External shared disks for storing the Oracle Clusterware files See the Oracle Real Application Clusters Installation Guide 11g Release 1 11 1 for information on the available disk configuration options Review these options before you decide which storage option to use in your Real Application Clusters environment One private Internet protocol IP address for each node to serve as the private interconnect The following must be true for each private IP address It must be separate from the public network It must be accessible on the same network interface on each node It must have a unique address on each node The private interconnect is used for inter node communication by both Oracle Clusterware and Real Application Clusters If the private address is available from a network name server DNS you can use that name Otherwise the private IP address must be available in each node s etc
307. uired dependents is redundant since they will be selected anyway The dependents selection can have the other two types of dependents optional and one or more The list of components is specified by an internal name and version number A typical example is listed here DEPENDENCY LIST oracle netclt 9 2 0 4 0 oracle netmgr 9 2 0 4 0 CLUSTER_NODES This parameter lists the nodes on the cluster on which the Oracle home is installed or would be installed For new installations this would be the node list on which the installation needs to be done including the local node For patching or upgrades this is the node list on which the Oracle home is already installed CLUSTER_NODES alpha 1 alpha 2 REMOTE_NODES This parameter lists the remote nodes apart from the local node on the cluster on which to install during a silent installation Oracle Universal Installer installs on all named nodes REMOTE NODES alpha 1 alpha 2 LOCAL NODE This parameter specifies the current node on which the installation occurs LOCAL NODE OPTIONAL CONFIG TOOLS While all the required configuration tools are launched by the installer you can control the optional configuration tools you would want to launch by specifying the tool s internal names in the OPTTONAL CONFIG TOOLS section Customizing and Creating Response Files 3 9 Response File Format Note TheOPTIONAL CONFIG TOOLS variable is only generated when
308. update to other nodes You can use this option on Oracle Real Application Clusters environments and non clustered environments If an entire cluster is shut down before patching you can use this option for non rolling patches local_node Specifies to OPatch that this is the local node for the cluster to be used for rollback You can use this option for Oracle Real Application Clusters environments no_sysmod Specifies that OPatch need not update the files in the system only the inventory It also does not execute the pre and post scripts no_relink This option does not perform any make operation in the patch You can use this option during multiple patch removals and to perform the compilation step only once 7 18 Oracle Universal Installer and OPatch User s Guide OPatch Utility for OUI based Oracle Homes Table 7 6 Cont Rollback Options for OUI Patches Option Description oh opatch init end opatch post end opatch pre end Patch Location ph post pre property file ptlConnect ptlSchema ptlPassword remote_nodes report retry runSql sqlScript silent verbose Specifies the Oracle home directory to use instead of the default directory This takes precedence over the ORACLE HOME environment variable Marks the end of the init options Use this option with the init option If you do not use this option everything after init until the end of the command is passed into
309. us for all prerequisite checks designed for the installation Click Next Oracle Universal Installer displays the Specify Cluster Nodes for Node Addition page Specify public private virtual IPs in this page and click Next Oracle Universal Installer displays the Specify Local Host Name page Specify at least one public and one private interface in this page and click Next Specify the Oracle Cluster Registry location option to provide a redundant OCR location and click Next Specify the VD Voting Disk Location location option to provide redundant VD locations and click Next Oracle Universal Installer displays the Summary page Click Install and proceed After the installation is done Oracle Universal Installer prompts you to run orainstRoot sh and root sh You need to run these scripts and click OK Installing Cluster Environments 5 15 Installing Oracle Clusterware on Windows After you run root sh on all of the nodes the Oracle Universal Installer runs the Oracle Notification Server Configuration Assistant and Oracle Private Interconnect Configuration Assistant These assistants run without user intervention 10 Oracle Universal Installer displays the End of Installation page Click Exit Running the Oracle Universal Installer in Silent Mode to Install Oracle Clusterware You can run the Oracle Universal Installer in silent mode to install Oracle Clusterware by entering the following command runInstaller silent
310. uster as follows 7 42 Oracle Universal Installer and OPatch User s Guide Problem Resolution 4 bin sh make txt Apply the patch in each node in the cluster using the local flag SORACLE HOME OPatch opatch apply local Path To Patch Note Ensure that all the nodes use the same OPatch version When I apply a patch on a Real Application Clusters setup and execute opatch Isinventory on the local node it returns nothing Cause You might have lost all the patches applied earlier Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly in each node in the cluster Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command in each node in the cluster For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat On UNIX source ORACLE HOME patch storage patch id timestamp gt make txt file if available in each node as follows bin sh make txt Apply the patch in each node using the local flag SORACLE HOME OPatch opatch apply local Path To Patch Note Ensure that all the nodes use the same OPatch version When I roll back a patch on a Real Application Clusters setup and execute opatch Isinventory on the local node it shows that the patch was not removed Cause This may
311. uthenticity of the host could not be established Enter yes at the prompt to continue You should not see this message again when you connect from this system to that node If you see any other messages or text apart from the date the installation can fail Make any changes required to ensure that only the date is displayed when you enter these commands You should ensure that any parts of login scripts that generate any output or ask any questions are modified so that they only act when the shell is an interactive shell 5 To ensure that X11 forwarding does not cause the installation to fail create a user level SSH client configuration file for the Oracle software owner user as follows a Using any text editor edit or create the oracle ssh config file b Make sure that the ForwardX11 attribute is set to no For example Host ForwardX11 no 6 You must run Oracle Universal Installer from this session or remember to repeat steps 2 and 3 before you start Oracle Universal Installer from a different terminal session Preventing Oracle Clusterware Installation Errors Caused by stty Commands During an Oracle Clusterware installation the Oracle Universal Installer uses SSH if available to run commands and copy files to the other nodes During the installation hidden files on the system for example bashrc or cshrc can cause installation errors if they contain stty commands To avoid this problem Oracle recommends
312. w variables are populated with values Variable Lookup Order All variable values within a response file are in the name value format If two components have a variable with the same name the expression should be written as follows to preserve each variable s uniqueness lt component gt lt variable gt lt value gt If two components have the same internal name but different versions resolve the ambiguity by specifying the expression as follows lt component gt lt version gt lt variable gt lt value gt Oracle Universal Installer looks for command line variables in the following order lt component gt lt version gt lt variable gt lt value gt lt component gt lt variable gt lt value gt lt variable gt lt value gt If command line variables are not found then Oracle Universal Installer looks for variables in the response file in the same order lt component gt lt version gt lt variable gt lt value gt lt component gt lt variable gt lt value gt lt variable gt lt value gt Note Oracle Universal Installer treats incorrect context format or type values within a response file as if no value were specified 3 4 Oracle Universal Installer and OPatch User s Guide Response File Format Comments Headers Setting the Recommendation Value Values for variables are specified as variable recommendation value The values that are given as value required mu
313. while the RDBMS instance is running This simplifies administration because no downtime is needed and also results in a much quicker turnaround time for installing or de installing Online Patches A regular RDBMS patch can require many minutes to install since it requires instance shutdown a relink and instance startup On the other hand you can install an online patch in just a few seconds Online patches are only applicable for Oracle RDBMS and not any other products Online patches are currently not supported in Windows and only supported on the following UNIX platforms m Linux x86 32 bit 7 32 Oracle Universal Installer and OPatch User s Guide Real Application Clusters Patching a LinuxIA64 a Linux PPC 64 m Solaris 64 bit Real Application Clusters Patching A Real Application Clusters environment enables active instances to concurrently execute transactions on a shared database Patching in a Real Application Clusters environment is slightly different compared to patching a single node Interim Patching using OPatch follows a similar approach as that performed by Oracle Universal Installer to detect Oracle home and nodes of a cluster OPatch interacts with the Oracle Universal Installer inventory through the Oracle Universal Installer Java SDK If OPatch detects a cluster it queries the inventory through Oracle Universal Installer to find the local node name and node list If your node list is not updated you can updat
314. xiii Structure xiv TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone TTY access to Oracle Support Services within the United States of America 24 hours a day seven days a week For TTY support call 800 446 2398 This manual contains the following chapters and is organized as follows Chapter 1 Introduction to Oracle Universal Installer This chapter contains overview information on Oracle Universal Installer Chapter 2 Managing Oracle Homes This chapter contains information on how you can manage Oracle homes and Oracle inventory using Oracle Universal Installer Chapter 3 Customizing and Creating Response Files This chapter contains information on how you can perform a silent installation using response files in the Oracle Universal Installer Chapter 4 Installing Products This chapter contains information on the prerequisites for installation and how you install and remove Oracle products Chapter 5 Installing Cluster Environments This chapter contains information on Oracle Clusterware and Real Application Clusters installation Chapter 6 Cloning Oracle Software This chapter contains information on Oracle software cloning using Oracle Universal Installer It also contains the steps to perform a database cloning Oracle Clusterware cloning and Real Application Clusters cloning Chapter 7 Patching Oracle Software with OPatch This chapter contains information on
315. y this section describes Starting Oracle Universal Installer Command Line Arguments Using Oracle Universal Installer Exit Codes Cloning Considerations Starting Oracle Universal Installer Oracle Universal Installer is installed on your system during the installation of your Oracle products Program Files Oracle oui on Windows At the same level as oraInventory on UNIX For all platforms the executable file setup exe or runInstaller sh is located in the following directory oui location bin A new version of Oracle Universal Installer replaces its older version Oracle Universal Installer is placed under Independent Products in the Inventory panel as a non Oracle home product To start Oracle Universal Installer On Windows platforms select Start Programs Oracle Installation Products Oracle Universal Installer a On UNIX execute runInstaller from the directory where it is installed 4 12 Oracle Universal Installer and OPatch User s Guide Running Oracle Universal Installer After Installation For example if the lt oraInventory gt is u01 oracle oraInventory Oracle Universal Installer will be located at u01 oracle oui A runInstaller sh script is also available so that you can launch Oracle Universal Installer directly from a different directory When Oracle Universal Installer is first installed and run it checks for the JRE path the location from which it runs us
316. ying it to the Oracle home Use this tool if you are certain that the patch is present in the Oracle home but not in the inventory You can download it from MetaLink at patch number 4321390 to just add the patch to the inventory After using this option opatch 1sinventory shows the one off patch information along with other installed one offs A 2 Oracle Universal Installer and OPatch User s Guide OPatch OPatch On two separate occasions I experienced a corrupt inventory and a failed installation Does OUI provide a backup facility I could use before I try to install again OUI provides automated backups for the Central Inventory and Oracle home Inventory For more information see Section Automated Inventory Backups in Appendix B Troubleshooting and Debugging Oracle Universal Installer This section answers the frequently asked questions for OPatch When I apply a patch I receive an error that reads Failed to load the patch object Possible causes are The specified path is not an interim patchshiphome Metadata files are missing from the patch area What do I do This simply means the directory OPatch is using to find the patch doesn t match the template it is checking for For more information on this error see Not a valid patch area on page 7 46 When I apply a patch I receive an error that reads Syntax error Patch location not valid What do I do This simply means that the patch location that you speci
317. you apply a patch you quit when OPatch failed to relink and prompted to continue Cause This may occur because of a relink failure Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory and execute the Restore command For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 Resolve the relink failure issue by ensuring that you are able to invoke make manually on a UNIX shell After this apply the patch again Real Application Clusters Setup When I apply a patch on a Real Application Clusters setup and execute opatch Isinventory on the local node the patch is not listed Cause This may occur if OPatch failed to update the inventory Action Perform the following steps 1 Ensure that the environment variable ORACLE HOME is set properly in all the nodes of the cluster 2 Navigate to the SORACLE HOME patch storage patch id timestamp directory of each node in the cluster and execute the Restore command as follows For UNIX SORACLE HOME patch storage patch id timestamp restore sh For Windows SORACLE HOME patch storage patch id timestamp restore bat 3 OnUNIX source SORACLE HOME patch storage patch id timestamp make txt file if available in each node of the cl
Download Pdf Manuals
Related Search
Related Contents
KDL-40Z5100 40 BRAVIA® Z Series LCD TV - Regal audio Grandstream Networks GXW-400x User's Manual manuale di installazione uso e manutenzione telepítési, kezelési és About this User`s Manual SolarView SolarView® オプションキット 取扱説明書 DIGITAL MULTIMETER Pocket Wi-Fi イー・モバイル D25HW セットアップマニュアル (ゲーム編) Copyright © All rights reserved.
Failed to retrieve file