Blogs.Oracle.Com - Oracle E-Business. Oracle Database 10gR2 Patch Set 10.2.0.5.0 is now certified with Oracle E-Business Suite Release 12 (12.0.4 and higher, 12.1.1 and higher. Fifth Recommended Patch Collection for EBS. This document supplements Oracle Database Readme and may be updated after it is released. To check for updates to this document and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web sitehttp: //www. For additional information about this release, refer to the readme files located in the $ORACLE. These documents are available with the media in the same location as the software and on Oracle Technology Network. This document contains the following topics: 1 Certification Information. The latest certification information for Oracle Database 1. Release 2 (1. 0. 2) is available on My Oracle Support (formerly Oracle. Meta. Link) at: https: //support. Linux Certification. Thanks for this information. 64 bit is the next step in evaluation and I have already read these pages. I was specifically looking for 10.2.0.4.0 patch on 32 bit Windows Server 2008 as some of our installations would not need.
Starting with Oracle Database 1. Release 2 (1. 0. 2. Oracle Database Installation Guide for Linux x. Asianux 3. Oracle Linux 4/Oracle VMOracle Linux 5/Oracle VMRed Hat Enterprise Linux 4/Oracle VMRed Hat Enterprise Linux 5/Oracle VMSUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. Refer to Oracle Database Installation Guide for Linux x. Refer to . However, Oracle Database 1. Release 2 is not supported by Grid Control 1. Preinstallation Requirements. You must review the following sections before installing Oracle Database 1. Release 2: 3. 1 Install libaio Before Installing or Upgrading. Before upgrading to or installing Oracle Database 1. Release 2, install the libaio package. Install oracleasm- support to use ASMLib. Install oracleasm- support package version 2. ASMLib on all Linux operating systems. Oracle HTTP Server on Oracle Linux 4 and Red Hat Enterprise Linux 4. If you intend to use Oracle HTTP server, which is included in Companion CD of Oracle Database 1. Release 2 (1. 0. 2) Media pack, refer to the My Oracle Support( formerly Oracle. Metalink) note 3. Oracle HTTP server on Oracle Linux 4 and Red Hat Enterprise Linux 4 . Oracle HTTP Server on Oracle Linux 5 and Red Hat Enterprise Linux 5. If you intend to use Oracle HTTP Server, which is included in Companion CD of Oracle Database 1. Release 2 (1. 0. 2) Media pack, refer to the My Oracle Support( formerly Oracle. Metalink) note 5. Oracle HTTP Server on Oracle Linux 5 and Red Hat Enterprise Linux 5. Legacy entry points required by this version of Apache (libdb. You must create a symlink using the following command. Kernel Requirement for SUSE Linux Enterprise Server 1. The kernel requirement for Oracle Database 1. Release 2 (1. 0. 2) is 2. Configuring Kernel Parameters. After updating the values of kernel parameters in the /etc/sysctl. On SUSE Linux Enterprise Server 9, ensure that you set the following kernel parameter. For example, on a system using a group named dba with the dba: !: 1. In this makefile version, the default database name (db. This issue will be seen even in other platforms when makefile version 3. The workaround is to use makefile version 3. Follow the instructions documented in My Oracle Support( formerly Oracle. Metalink) note 2. This issue is tracked with Oracle bug 3. Oracle Universal Installer Operating System Prerequisite Checks. If you are installing Oracle Database 1. Oracle Linux 5, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. Oracle Universal Installer does not recognized these operating systems as supported operating systems and does not perform the installation. Workaround #1 (recommended): Run the Oracle Universal Installer using the ignore. Sys. Prereqs flag which causes the installer to skip the operating system check and continue with the installation. Sys. Prereqs. As a side effect, the installer also skips other checks during the installation. Workaround #2: On Oracle Linux 5 and Red Hat Enterprise Linux 5, the installation will pass the operating system prerequisite checks if you change each Oracle Linux 5 and Red Hat Enterprise Linux 5 to Oracle Linux 4 and Red Hat Enterprise Linux 4 in the /etc/redhat- release file. Ensure that you replace the original values in the /etc/redhat- release file after the Oracle installation is complete. Original Value. Changed Value. Enterprise Release Enterprise Linux server release 5(On Oracle Linux 5)Enterprise Release Enterprise Linux server release 4. Red Hat Enterprise Linux server release 5(On Red Hat Enterprise Linux 5)Red Hat Enterprise Linux server release 4. On SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 1. SUSE Linux Enterprise Server 9 in the /etc/Su. SE- release file. Ensure that you replace the original values in the /etc/Su. SE- release file after the Oracle installation is complete. Original Value. Changed Value. SUSE Linux Enterprise Server 1. VERSION = 1. 0SUSE Linux Enterprise Server 9 (x. VERSION = 9. SUSE Linux Enterprise Server 1. VERSION = 1. 1SUSE Linux Enterprise Server 9 (x. VERSION = 9. This workaround causes Oracle Universal Installer to consider the system to be running earlier version of the operating system and the operating system check passes. The changes to the release file should be reverted after the installation of all Oracle software is complete. The changes to the release file could impact the ability of other tools to be properly installed on the operating system. Installing Oracle Clusterware. Near the end of the installation of Oracle Clusterware, Oracle Universal Installer prompts for the $CRS. When the root. sh script is run on the last node in the cluster, the script calls the VIPCA utility, which fails on Oracle Linux 5, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Linux 1. SUSE Linux Enterprise Linux 1. Ensure that you do not comment out line 1. Adding a Node to a Shared Oracle Clusterware Configuration. Before running root. Oracle Clusterware home, add the following line in the $ORA. The following error message is displayed when you run the rootupgrade. Use the - A argument to include the existing interfaces for the VIP. A 1. 00. 2. 00. 3. This issue is tracked with Oracle bug 4. Raw Devices on Oracle Linux and Red Hat Enterprise Linux. When you restart an Oracle Linux 4, Oracle Linux 5, Red Hat Enterprise Linux 4, or Red Hat Enterprise Linux 5 system, raw devices revert to their original owners and permissions by default. If you are using raw devices with this operating system for the Oracle files, for example, for ASM storage or Oracle Clusterware files, you need to override this default behavior. To do this, add an entry to the /etc/rc. As an example, here are sample entries in a /etc/rc. ASM disk files (/dev/raw/raw. Oracle Cluster Registry files (/dev/raw/raw. Oracle Clusterware voting disks (/dev/raw/raw. Oracle Clusterware Daemon Fails on Computer Restart. If different user IDs are used for installing Oracle Database 1. Oracle Clusterware, then restarting the system results in OCR errors. Refer to the My Oracle Support( formerly Oracle. Metalink) note 5. Workaround: Oracle recommends that you apply patch set 1. Oracle Clusterware installation before patching Oracle Database. This issue is tracked with the Oracle bug 4. Configuring Storages Devices for Oracle Clusterware on 2. Kernel Distributions. This section is for database and system administrators who intend to install or migrate to Oracle RAC 1. Release 2 (1. 0. 2) on Red Hat Enterprise Linux 5 or Oracle Linux 5, and who need to configure raw devices for Oracle RAC and Oracle Clusterware. The Linux 2. 6 kernel with these distributions requires additional configuration steps. The section contains the following topics: 4. Overview of Device Naming Persistence Changes. With the Linux 2. The preferred way to access block devices is direct input/output to the devices using O. Therefore, /etc/sysconfig/rawdevices file of Red Hat Enterprise Linux 4 and Oracle Linux 4, and /etc/udev/rules. Red Hat Enterprise Linux 5 and Oracle Linux 5 are deprecated. For details, refer to the Linux documentation for your 2. The 2. 4 kernel device file naming scheme devlabel maintained persistent device file names between server restarts. By default, the 2. If udev applies default settings, then it changes device file names and owners for voting disks or Oracle Cluster Registry partitions, corrupting them when the server is restarted. For example, a voting disk on a device named /dev/sdd owned by the user Cluster Ready Services may be on a device named /dev/sdf owned by root after restarting the server. To prevent corruption, you need to create a custom rules file. When udev is started, it sequentially carries out rules (configuration directives) defined in rule files. These files are in the path /etc/udev/rules. Rules files are read in lexical order. For example, rules in file 1. Where rules files describe the same devices, on Asianux, Red Hat, and Oracle Linux, the last file read is the one that is applied. To do this, complete the following task: Modify the /etc/scsi. For example. # cp scsi. For example. # /sbin/fdisk - l /dev/sdb. Disk /dev/sdb. 1: 2. MB, 2. 61. 89. 00. Units = cylinders of 5. Disk /dev/sdb. 1 does not contain a valid partition table. Disk /dev/sde. 1: 5. MB, 5. 24. 03. 20. Units = cylinders of 1. Disk /dev/sde. 1 does not contain a valid partition table. In some cases, to see newly provisioned or modified) devices on shared storage, you may need to update cluster node operating systems. Do this either by restarting the nodes, or by using commands such as /sbin/partprobedevice, or sfdisk - rdevice. Resolve any issues preventing cluster nodes from correctly seeing or accessing storage devices you intend to use for Clusterware files before proceeding. Note. At this point, cluster nodes may refer to the devices using different device file names. This is expected. Run the command scsi. When running the scsi. For example. # /sbin/scsi. This step is optional, but recommended. The default rule files affecting storage devices are rule files 5. So, create a custom rules file using the format . For example: 5. 5- oracle- naming. To do this, complete the following tasks: Create a custom udev device naming rule file. For example. # touch /etc/udev/rules.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |