However, these applications must be corrected before upgrading to the next major release of the Oracle database. In release 9. This could lead to issues with memory management, frequent reloading of library cache objects, and ORA errors.
Starting with release 9. Most users do not need to modify the value of either of these parameters. This patch set enables you to install the included patches on multiple nodes in a cluster if release 9. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment.
If it is, then the Oracle Universal Installer displays the available nodes from the cluster. The hangcheck-timer module is not required, however Oracle recommends that you use it.
The following sections describe the hangcheck-timer module and describe how to configure it. The hangcheck-timer module monitors the Linux kernel for long operating system hangs that could affect the reliability of an RAC node and cause corruption of an RAC database. If the operating system hangs, then the hangcheck-timer module will reboot the node. This approach has the following advantages:. Node reboots are triggered from within the Linux kernel, making them less affected by system load.
The Oracle Cluster Manager on an RAC node can be stopped and reconfigured because its operation is completely independent of the kernel module. The features in the hangcheck-timer module closely resemble features found in the implementation of Oracle Cluster Manager for RAC on the Microsoft Windows platform, on which Oracle Cluster Manager for Linux x86 was based.
The changes are as follows:. These parameters should be removed from the cmcfg. The following configuration parameter has been added to allow the Oracle Cluster Manager to know the name of the hangcheck-timer module so it can be loaded correctly:. It will not prevent the process from running.
The module must be loaded before you start Oracle Cluster Manager. The CMDiskFile parameter has been changed from optional to mandatory. This ensures a cluster manager quorum partition is used and allows the Oracle Cluster Manager to reliably handle certain hardware and software errors that affect cluster participation. This parameter is the interval indicating how often the hangcheck-timer checks on the health of the system.
This parameter sets the margin of error to prevent unnecessary system resets due to certain kernel activities that may randomly introduce delays in the operation of hangcheck-timer.
Together, these two parameters indicate how long an RAC node must hang before the hangcheck-timer module reboots the system. The following are the recommended default configuration settings for the hangcheck-timer module.
These are in addition to the recommendations for parameters in the RAC documentation. On Red Hat Enterprise Linux 2. Remove or disable the mechanism that loads the softdog module at system start up, if that module is not used by other software on the node. This is necessary for subsequent steps in the installation process. This step may require log in as the root user.
If this method was used, then remove or comment out the following line in the file:. If this method was not used, then check with the system administrator to determine where and how the softdog module is loaded and used.
The softdog module is no longer needed in this release of Oracle Cluster Manager. Remove or disable the mechanism to start the Oracle watchdogd module at system start up. This action is necessary for the subsequent steps in the installation process. Check with the system administrator to determine where and how the watchdog daemon is started. If watchdogd is started using an rc script that starts Oracle or Oracle Cluster Manager, then remove or comment out the watchdogd start up in the script.
If the watchdog daemon is started by a separate rc script, then ensure the references to this script are removed from the runlevel script directories. For SUSE 9, load the hangcheck-timer kernel module using the following command as root user:. Repeat steps 1 through 5 on all RAC nodes where the kernel module must be installed. The kill and killall commands imply a full cluster restart because every node will restart when the commands are run if watchdogd is enabled.
If one or more nodes restart, then ensure that none of the preceding services are running when the nodes come back up. Shut down any services that start after the restart. Ensure that the hangcheck-timer module is loaded by running the following command as the root user:. Follow the steps in this section to install the Oracle Cluster Manager release 9. Only one instance of Oracle Cluster Manager can run per node.
If the system has multiple Oracle home directories, then make sure to apply the patch to the Oracle home directory where Oracle Cluster Manager is installed. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:. Enter the private node names in the same order that you entered the corresponding public node names on the Public Node Information screen, then click Next. When prompted, run the orainstRoot.
After the software has been installed, the End of Installation screen appears. Configure Oracle Cluster Manager to use the hangcheck-timer module on all cluster nodes as follows:. The changes include the following:.
The default value is In the preceding example, the file or raw device must be valid. If you specify the name of a file that does not exist, then the file is created if the base directory exists. If you specify a raw device, then that raw device must exist and have the correct ownership and permissions. Modify the ocmstartup. Make sure that Oracle Cluster Manager is running, and that the watchdog daemon process watchdogd is not running on all nodes before applying the database patch set.
You must install it in an existing Oracle9 i Oracle home. To identify Oracle home directories, view the file. If you are installing this patch set on an existing Real Application Clusters RAC installation, you must run the Installer from the same node from which you performed the initial installation. Before installing this patch set in a production environment, review document This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released.
If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment. Shut down any existing Oracle database instances with normal or immediate priority. On RAC systems, shut down all instances on each node. Stop all listener and other processes running in the Oracle home directory where you want to install the patch set. Oracle recommends that you create a backup of the Oracle9 i installation before you install the patch set.
After the patch set is installed, there is no way to remove it. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next. You can install the patch set either interactively or noninteractively.
See one of the following sections for information about how to complete the installation:. To install the patch set interactively, see the "Installing the Patch Set Interactively" section. To install the patch set noninteractively, see the "Installing the Patch Set Noninteractively" section.
Installing the Patch Set Interactively. The Oracle Universal Installer does not allow the installation to proceed. Click OK , then click Cancel to end the installation. Select the products.
For example:. If you are applying the patch set to an RAC installation, then run the root. Installing the Patch Set Noninteractively. Copy the response file template provided in the response directory where you unpacked the patch set archive file. Review the information in this section before using the upgraded software.
This section lists required and optional postinstallation tasks, depending on the installation type and the products that you want to use. To upgrade Oracle databases from a previous release directly to Oracle9 i release 2 9. Review the "Check Tablespace Sizes and Set Parameter Values" section and complete the steps in the "Upgrade the Database" section after you have installed the patch set software. If necessary, enter the following command to determine whether the system uses an initialization parameter file init sid.
This command displays the name and location of the server parameter file or the initialization parameter file. After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:. Review the patch. Run the utlrp. This step is optional but recommended. If Oracle Internet Directory release 9. You cannot remove the patch set software after you have installed it.
Oracle recommends that you back up the Oracle9 i installation before applying the patch set. If you do not want to use a patch set applied to an Oracle9 i installation, do one of the following:.
If you choose not to use a patch set because you are encountering a problem, contact Oracle Support Services to verify that the problem you are encountering is being addressed.
If you completed the steps in the "Upgrade the Database" section, you must do one of the following for each database that you upgraded to the patch set:. Use a point-in-time or full database backup and recovery to restore the database to its condition before you upgraded the database. Export, rebuild, and import the database.
If necessary, you can reinstall a patch set that has been applied to an Oracle9 i installation. You must reinstall the patch set interactively. Select the Oracle home that you want to upgrade in the Name field in the Destination section, then click Next. The Available Product Component screen appears.
This screen contains a list of all components that have been patched by the original patch set installation. These components are grayed out, indicating they cannot be selected for installation.
Expand the nodes for each component listed in the tree to display the patch that corresponds to each component. Repeat the process for each patch bundled in the patch set, then click Next. On the Summary screen, verify the list of patches to be reinstalled, then click Install. The error message can be ignored. The following is an example of a message that can be ignored:. The following is an example of a valid error message. Notice that the target of the makefile is identified.
Messages similar to the following should not be ignored, and you should contact Oracle Support Services. If you use Oracle Procedural Gateway for APPC, comment out the following parameters if they are present in the gateway shell script or init sid. If you use DBCA to create a new database using the seed database option, some of the components will be from an older version. This is because the seed database was created before the patch release. To correct this problem, run the catpatch.
This warning indicates that problems were detected in the LogMiner dictionary. See Oracle MetaLink note If it is not practical to take these actions, contact Oracle Support for alternative instructions to repair the LogMiner dictionary. When you apply a patch, you are doing so to the software, not directly to the database. The database runs under an Oracle software version. So although you can say that your database is 9. Let us know if you have additional questions. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.
The Tek-Tips staff will check this out and take appropriate action. Click Here to join Tek-Tips and talk with other members! Already a Member? Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free. Register now while it's still free! Already a member? Close this window and log in. Join Us Close.
Join Tek-Tips Forums! Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. I am trying to upgrade oracle 9. I am not sure what to use. Either use a patch or dbua. Please help. Let us know your results.
0コメント