Welcome
Tuesday
To apply opatch in database
This post has been written on request of one of regular visitor of my blog (Altaaf). This post is all about Oracle Patching Utility (OPATCH) and various options that can be used along with Opatch.
We will begin the discussion by knowing what exactly is Opatch?
- OPatch is a java based utility that allow the application and rolling back of interim patches to an Oracle product. The program has sub-commands that may take arguments. The program requires java(JVM) to be present on the current system.OPatch expects users to have commands such as fuser, jar, ar and make on Unix platforms and jar on Windows platforms to be available in their PATH.
Opatch Details
How to check the Opatch version?
-bash-3.00$ ./opatch version
Invoking OPatch 10.2.0.3.0
OPatch Version: 10.2.0.3.0
OPatch succeeded.
How to know which version is the correct version of Opatch for your RDBMS home?
You can verify whether the Opatch version for your RDBMS release is correct or not using metalink note ID 357221.1.
This note ID gives the copatibilities between OPatch version and RDBMS version.
How to get the latest version of OPatch?
You can download the latest version of OPatch from metalink using following URL.
http://updates.oracle.com/download/6880880.html
In the release dropdown you can select the OPatch release that you want to download based on your RDBMS version. Please read the README.txt before applying the patch.
What is Oracle Database Inventory and where it is located?
Oracle Inventory is the location or the place where all the information about an Oracle Home is stored and maintained. When ever we install an RDBMS Oracle Home, a new inventory gets created. Applying any new patch to Oracle Home will update the invnrtory for that Oracle Home and record the details for the patch applied. This inventory is in the form of XML files.
The location of inventory is defined in a file called oraInst.loc. The path for this file is provided while installing Oracle Home. If we dont supply any path, the is file will be present at central location /etc/oraInst.loc. Also we can have a central inventory if its not used by any other oracle installation. If the central inventory is used by previous Oracle installation we can create local inventory. The content of oraInst.loc file is as shown below.
-bash-3.00$ cd $ORACLE_HOME
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
Here “inventory_loc” gives the location of Inventory directory where as inst_group gives the name of the group which is the owner of this inventory.
How to create Local Inventory?
You can create local inventory at any location while installing Oracle Home. You need to use -invPtrLoc variable along with runInstaller command and give the location of oraInst.loc. Otherwise the default path assumed for oraInst.loc is /etc/oraInst.loc.
./runInstaller -invPtrLoc /slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInst.loc
After the installation starts it will ask for location of oraInventory directory and group which should own it. It will make entry of these into oraInst.loc file.
Having know the above information about opatch, now we will move to details about using opatch and various options available.
Opatch help
You can get all the options using opatch -help
-bash-3.00$ ./opatch -help
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.
Usage: opatch [ -help ] [ -r[eport] ] [ command ]
command := apply
lsinventory
prereq
query
rollback
util
version
:= -help Displays the help message for the command.
-report Print the actions without executing.
example:
‘opatch -help’
‘opatch apply -help’
‘opatch lsinventory -help’
‘opatch prereq -help’
‘opatch rollback -help’
‘opatch util -help’
OPatch succeeded.
You can get specific help for any command of opatch using opatch -help. Example opatch apply -help.
Applying single patch using opatch
1. You MUST read the Readme.txt file included in opatch file, look for any prereq. steps/ post installation steps or and DB related changes. Also, make sure that you have the correct opatch version required by this patch.
2.Make sure you have a good backup of database.
3. Make a note of all Invalid objects in the database prior to the patch.
4. Shutdown All the Oracle Processes running from that Oracle Home , including the Listener and Database instance, Management agent etc.
5. You MUST Backup your oracle Home and Inventory
tar cvf - $ORACLE_HOME $ORACLE_HOME/oraInventory | gzip > Backup_Software_Version.tar.gz
6. Unzip the patch in $ORACLE_HOME/patches
If you are applying a single intrim patch to oracle home, then change the location to the directory of that patch and then invoke following command.
Example if I need to apply patch 6972343 to RDBMS Oracle Home
-bash-3.00$ cd 6972343
-bash-3.00$ pwd
/slot/ems2029/oracle/db/tech_st/11.1.0/patches/6972343
-bash-3.00$ ls
etc files README.txt
$ORACLE_HOME/OPatch/opatch apply
If you have created local inventory then you need to give the correct path for local inventory stored in oraInst.loc. If you have updated /etc/oraInst.loc with correct location of your inventory, then above command will work, If not you can give the correct location by giving local oraInst.loc file.
$ORACLE_HOME/OPatch/opatch apply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Remember that when we are applying patch, patch number is NOT provided as an input to opatch command. So we have to to be in the directory of patch since opatch will pick the patch files from current directory.
Rolling back a patch
In case if a patch did not fix the issue or if you has applied wrong patch to oracle home, you can always rollback the patch using following comamnd.
opatch rollback -id
Applying bundle patches
Some times if you have to apply bundle patch having many patches, example lets say you want to a bundle patch 6778860 ( 11.1.0.6 BUNDLED PATCH FOR EBS 11I)) containing many other patches to RDBMS home, OPatch provides a facility to apply many patches to RDBMS home using a single comamnd. Following command should be used for applying bundle patches.
Download the patch and extract the same. You will see many directories (one for each patch) inside the main patch directory. Execute following command to apply all patches.
$ORACLE_HOME/OPatch/opatch util NApply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
NApply -> Will apply all patches to RDBMS home.
You can also use -phBaseDir to point to the directory where bundle patch is installed. So you can run opatch command from any location
$ORACLE_HOME/OPatch/opatch util NApply -phBaseDir /slot/ems2029/oracle/db/tech_st/11.1.0/patches/6778860 -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
You can also apply specific patches using NApply
opatch util napply -id 1,2,3 -skip_subset -skip_duplicate
This will apply patches 1, 2, and 3 which are under < the patch_location> directory. OPatch will skip duplicate patches and subset patches (patches under that are subsets of patches installed in the ORACLE_HOME)
You can see all the options for NApply using following help command.
$ORACLE_HOME/OPatch/opatch util NApply -help
Query the inventory for patches applied
We can query the inventory to check various components installed for database as well as to check various patches applied to database. Use following command to get a minimum information from inventory about patches applied and components installed.
$ORACLE_HOME/OPatch/opatch lsinventory -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 5763576 : applied on Wed May 28 03:20:53 PDT 2008
Created on 6 Feb 2008, 02:26:04 hrs PST8PDT
Bugs fixed:
5763576
If you are using central inventory then -invPtrLoc variable is not required.
You can also get the detailed view of inventory using following command. In case of detail information it gives which are the files that this patch have touched.
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 6318357 : applied on Wed May 28 03:33:27 PDT 2008
Created on 4 Dec 2007, 22:02:16 hrs PST8PDT
Bugs fixed:
6318357
Files Touched:
udjvmrm.sql –> ORACLE_HOME/javavm/install/udjvmrm.sql
Patch Location in Inventory:
/slot/ems2029/oracle/db/tech_st/11.1.0/inventory/oneoffs/6318357
Patch Location in Storage area:
/slot/ems2029/oracle/db/tech_st/11.1.0/.patch_storage/6318357_Dec_4_2007_22_02_16
Which options are installed in Oracle Home?
You can check the options installed in RDBMS home using above command. The options installed will be listed at the start of output.
Example: $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
The complete output of this command can be seen at this location.
Opatch Log files
Log file for Opatch utility can be found at $ORACLE_HOME/cfgtoollogs/opatch
Advanced Option for OPatch
Here are some of the advanced options of OPatch utility.
UpdateRemoteNodes
It is used to propagate/remove files/directories to/from remote nodes using files under ORACLE_HOME/.patch_storage//rac/*.
The directories listed in copy_dirs.txt will be copied to remote nodes.
The files listed in copy_files.txt wil be copied to remote nodes.
The directories listed in remove_dirs.txt will be deleted from remote nodes.
The files listed in remove_files.txt will be deleted from remote nodes.
This is used where RAC setup is present.
Cleanup
It is used to clean up ‘restore.sh, make.txt’ files and ‘rac, scratch, backup’ directories in the ORACLE_HOME/.patch_storage directory. If -ps option is used, then it cleans the above specified areas only for that patch, else for all patches under ORACLE_HOME/.patch_storage. You will be still able to rollback patches after this cleanup.
Example: opatch util cleanup -ps 6121183_Ju _21_2007_04_19_42
CopyListedFiles
It is used to copy all files listed in ORACLE_HOME/.patch_storage//rac/copy_files.txt to remote nodes. If -fp option is used, then one can specify the path of the file containing the list of files to be copied. The files mentioned in this file will be copied to the remote nodes.
Example: opatch util copylistedfiles -fp a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedFilesTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedFiles.
Example: opatch util copylistedfilestest -fp /home/oracle/a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedDirs
It is used to recursively copy all directories listed in ORACLE_HOME/.patch_storage//rac/copy_dirs.txt to remote nodes. If -dp option is used, then one can specify the path of the file containing the list of directories to be copied. The directories mentioned in this file will be copied to the remote nodes.
This is used where RAC setup is present.
CopyListedDirsTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedDirs.
This is used where RAC setup is present.
RemoveListedFiles
It is used to remove files listed in ORACLE_HOME/.patch_storage//rac/remove_files.txt on remote nodes. If -fr option is used, then one can specify the path of the file containing the list of files to be removed. The files mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
RemoveListedFilesTest
It is used to remove a single file from remote nodes. The usage remains the same as RemoveListedFiles.
This is used where RAC setup is present.
RemoveListedDirs
It is used to recursively remove directories listed in ORACLE_HOME/.patch_storage//rac/remove_dirs.txt from remote nodes. If -dr option is used, then one can specify the path of the file containing the list of directories to be removed. The directories mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
RemoveListedDirsTest
It is used to remove a single directory from remote nodes. The usage remains the same as RemoveListedDirs.
This is used where RAC setup is present.
RunLocalMake
It is used to invoke re-link on the local node. The make commands are stored in ORACLE_HOME/.patch_storage//make.txt. You need to use the -ps option to specify the Patch ID with timestamp. A directory by this name will be present under ORACLE_HOME/.patch_storage. The make.txt file present under ORACLE_HOME/.patch_storage// will be used to perform the local make operation. This command cannot be run if you have already run Cleanup as it would have removed these make.txt files.
Example: opatch util runlocalmake -ps 6121250_ un_21_2007_04_16_11
RunRemoteMake
It is used to invoke re-link on remote nodes. The make commands are stored in
ORACLE_HOME/.patch_storage//rac/makes_cmd.txt. The usage remains the same as RunLocalMake.
This is used where RAC setup is present.
RunAnyCommand
It is used to run any command on remote nodes. The command should be specified using the -cmd option.
Example: opatch util runanycommand -remote_nodes ceintcb-a5 -cmd ls
This is used where RAC setup is present.
LoadXML
It is used to check the validity of an XML file. The -xmlInput option can be used to specify the path of the xml file.
@ Support can use this utility to verify the integrity of XML files contained in the local and central inventory.
Example: opatch util loadxml -xmlInput $ORACLE_HOME/inventory/ContentsXML/comps.xml
Verify
It is used to run the patch verification process to ensure that the patch was applied to the ORACLE_HOME. It uses the defined ORACLE_HOME and the given patch location via -ph, to run the check.
@ Support can use this utility to re-run the OPatch verification stage, if required for patch diagnosis. The patch staging area has to be present or created.
Example: opatch util verify -ph ~/6646853/6121183
Troubleshooting
Some times the inventory get corrupted because of some issues. In that case you need to repair the inventory. Following are the two methods which I know can be used to repair the inventory.
1) Development has released a utility (checkinv) which can be use to repair the inventory if it becomes corrupted for some reason.
Please note that this version of checkinv works only for 9.2 and 10.1 releases of oracle database. This doesn’t work for 10.2 releases of oracle database.
You can download the checkinv utility from Patch 4121946.
To cleanup the components, you should determine the unwanted or dangling components, then specify those using the option “-remcomp”, to cleanup the component list.
The utility detects and asks user’s permission to repair a bad inventory. In case you want to repair the inventory, the utility will first back up the files before any modification.
However, it is better that you backup the inventory before running the tool.
For more details, check metalink note ID 298906.1
2) Creating a new inventory using Oracle Universal Installer (OUI).
References:
Metalink note ID : 298906.1
Metalink note ID : 554417.1
Metalink note ID : 374092.1
Metalink note ID : 357221.1
Saturday
NFS Mounting on Linux
Most often it is required to do a NFS mount of your disks across different servers. This particularly useful for doing Applications Installations and Patching. There are two aspects of configuration involved here. One is the sever that is the which is sharing the file system and the other is client which the host that is mounting the shared file system.
Supposing you want to mount a u01/hemanth on Node_A to Node_B
Configurations on Node_A
edit the /etc/exports file
vi /etc/exports
add the filesystem to mount
/u01/sam ro Node_B
you can either use the option ro which means read only or in case you wish to allow node_b to write into the filesystem use the rw option which is read writeable.
The change in exports file takes effect only after the restart of your NFS service daemon. use the service command to do that.
# service nfs restart
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
Configuration for Node_B
On Node_B simply create the mount point to hold the shared file system and mount it using the mount command.
#mkdir hemanth
#mount -t nfs Node_A:/u01/hemanth /hemanth
11.5.10 prerequisites
Oracle® Applications Installation Update Notes
Release 11i (11.5.10) for Linux x86, Solaris SPARC, Microsoft Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX
Oracle® Applications
Installation Update Notes
Release 11i (11.5.10) for Linux x86, Solaris SPARC, Microsoft Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX
Required Packages and Patches
The following table lists the packages and individual patches required for each operating system. Unless otherwise note, the packages and patches must be installed manually.
Additional Information:
Refer to the vendor's operating system installation manual or the operating system media for information on obtaining and applying these patches.
Operating System Required Patches
Red Hat Enterprise Linux AS/ES 2.1
* pdksh-5.s.14-13 (Oracle Discoverer)
* openmotif-2.1.30-x
Red Hat Enterprise Linux AS/ES 3.0* Quarterly Update 1 or higher (Minimum required version)
Note: See Certify on OracleMetaLink for information on specific Quarterly Updates requirements.
Red Hat Enterprise Linux AS/ES 3.0* Quarterly Update 4 (Recommended version)
Note: From the Package Group Selection screen, select Legacy Software Development. The following components will be installed automatically:
* compat-db-4.0.14-5.1
* compat-gcc-7.3-2.96.128
* compat-libstdc++-7.3-2.96.128
* compat-gcc-c++-7.3-2.96.128
* compat-libstdc++-devel-7.3-2.96.128
* setarch-1.3-1
* pdksh-5.2.14-21 (Oracle Discoverer)
The following required component must be installed manually:
* openmotif-2.1.30-x
Note: Available on Disk 3 of Quarterly Update 4 media.
Red Hat Enterprise Linux AS/ES 4.0* Legacy Software Development package and X Software Development package
Note: Select these packages from the Package Group Selection screen. If the operating system is already installed, use System Settings > Add/Remove Applications to install these two packages.
The following components will be installed automatically:
* compat-db-4.1.25-9
* compat-gcc-32-3.2.3-47.3yyyyyyyyy
* compat-gcc-32-c++-3.2.3-47.3
* compat-oracle-rhel4-1.0-5yyyyyyyyy
* compat-libcwait-2.0-2yyyyyyyyyyy
* compat-libgcc-296-2.96-132.7.2
* compat-libstdc++-296-2.96-132.7.2
* compat-libstdc++-33-3.2.3-47.3
* xorg-x11-deprecated-libs-devel-6.8.1-23.EL
* xorg-x11-deprecated-libs-6.8.1-23.EL
The following required component must be installed manually:
* openmotif-2.1.30-x
Note: For information on downloading the openmotif component, see the instructions at the following URL: https://rhn.redhat.com/errata/RHSA-2005-412.html
SUSE Linux Enterprise Server 8 The following required components must be installed manually:
* openmotif-2.1.30-x
* gcc 2.95.3
* SUSE Linux Enterprise Server 8 Service Pack 3
Note:You can download "openmotif-2.1.30-x" at the following URL:
http://support.novell.com/techcenter/search/search.do?cmd=displayKC&externalId=70bbf5fc1e287442b21b3c602acd7f71html
You can download the SUSE Linux Enterprise Server 8 Service Pack 3 at the following URL:
http://download.novell.com/directed
gcc 2.95.3 is included in the SUSE Linux Enterprise Server 8 operating system CDs named as gcc_old package
Install glibc-devel during the installation of the operating system by selecting the "C/C++ Compiler and Tools" option. If the operating system is already installed, manually select the package when installing SUSE Linux Enterprise Server 8 Service Pack 3.
SUSE Linux Enterprise Server 9 The following required components must be installed manually:
* openmotif-2.1.30-x
* gcc 2.95.3
* orarun-1.8-109
Note:
* /suse/s390/openmotif21-libs-2.1.30MLI4-119.1.s390.rpm is available in SUSE Linux Enterprise Server 9 CD2
* gcc 2.95.3 is included in the SUSE Linux Enterprise Server 9 operating system CDs named as gcc_old package
* orarun-1.8-109 can be downloaded from http://ftp.novell.com/partners/oracle/sles-9/
Solaris 8 (2.8) None
Solaris 9 (2.9) 113886-22, 113887-22, 113096-03, 112785-42
HP-UX PA-RISC 11.00 C++ Compiler C.03.27** (or higher)
HP-UX PA-RISC 11.11 PHCO_25452, PHNE_25084, PHNE_25642, PHSS_24638 (C++), GOLDQPK11i-December 01, C++ Compiler C.03.27** (or higher)
HP-UX PA-RISC 11.23 C++ Compiler A.03.60** (or higher)
HP-UX Itanium 11.23 None
IBM AIX 5L (5.1, 5.2, 5.3) Visual Age C++ 6.0.0.5 and Oct. 2003 PTF (or higher) or IBM XL 7.0 C/C++** (or higher)
Windows 2000 Service Pack 2. See also General Requirements for Windows.
Windows Server 2003 See General Requirements for Windows.
*After installing these patches, run ldconfig -v.
Setting Kernel Parameters
Most oracle products require certain kernel parameters to be set as a pre requisite for installation. Common kernel parameters include parameters for shared memory .
The /etc/sysctl.conf file takes care of your kernel parameters.
#vi /etc/sysctl.conf
kernel.shmmax = 2147483648
kernel.shmmni = 128
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
However changes made to this file take effect only after the next reboot.
The sysctl command can be used to set the kernel parameter at runtime in linux.
sysctl -p
sysctl -w kernel.shmmax=2147483648
11.5.10.2 Prerequisites
Oracle® Applications Installation Update Notes
Release 11i (11.5.10.2) for Linux x86, Solaris SPARC, Microsoft Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX
Required Packages and Patches
The following table lists the packages and individual patches required for each operating system. Unless otherwise noted, the packages and patches must be installed manually.
Additional Information:
See the installation instructions (software and hardware requirements section) for information on the RDBMS-specific version for your platform. See also the vendor's operating system installation manual or the operating system media for information on obtaining and applying patches.
Operating System Required Patches
Oracle Enterprise Linux 4*
Quarterly Update 4 or higher (Recommended Version)
* compat-db-4.1.25-9
* compat-gcc-32-3.2.3-47.3
* compat-gcc-32-c++-3.2.3-47.3
* compat-oracle-rhel4-1.0-5 (from Oracle patch 4198954)
* compat-libcwait-2.1-1 (from Oracle patch 4198954)
* compat-libgcc-296-2.96-132.7.2
* compat-libstdc++-296-2.96-132.7.2
* compat-libstdc++-33-3.2.3-47.3
* xorg-x11-deprecated-libs-devel-6.8.2-1.EL.13.37
* xorg-x11-deprecated-libs-6.8.2-1.EL.13.37
* openmotif-2.2.3-10.RHEL4.5
Oracle Enterprise Linux 5*
Red Hat Enterprise Linux 5* (base and Advanced Platform)
Update 1 (OEL 5.1) or higher is required
Update 1 (RHEL 5.1) or higher is required.
The following packages are not part of the OEL 5 or RHEL 5 distribution media and must be installed manually:
* compat-libstdc++-egcs-1.1.2-11
* compat-libcwait-2.1-11
* compat-oracle-el5-1.0-51
* openmotif21-2.1.30-11.EL51
* binutils-2.152
The following packages must be installed from the OEL 5 or RHEL 5 distribution media:
* libXp-1.0.0-8.1.el5
* compat-libgcc-296-2.96-138
* compat-libstdc++-33-3.2.3-61
* compat-db-4.2.52-5.1
Note :
1: Download from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/ (for both OEL 5 and RHEL 5)
2: GNU linker (ld) version 2.15 is required for relinking the modules in Advanced Planning & Scheduling (MSC, MSO, MSR) - download binutils-2.15 from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/
(for both OEL 5 and RHEL 5)
Red Hat Enterprise Linux AS/ES 2.1
* pdksh-5.s.14-13 (Oracle Discoverer)
* openmotif-2.1.30-x
* Note: In accordance with the Red Hat Enterprise Linux Errata Support Policy, the 7 year life-cycle of Red Hat Enterprise Linux AS/ES 2.1 has ended effective June 1, 2009. For instructions on migrating Red Hat Enterprise Linux 2.1 or 3 to Red Hat Enterprise Linux 4, see My Oracle Support Document 303237.1.
Red Hat Enterprise Linux AS/ES 3* Quarterly Update 1 or higher (Minimum required version)
Note: See Certifications on My Oracle Support for information on specific Quarterly Updates requirements.
Red Hat Enterprise Linux AS/ES 3* Quarterly Update 4 (Recommended version)
Note: From the Package Group Selection screen, select Legacy Software Development. The following components will be installed automatically:
* compat-db-4.0.14-5.1
* compat-gcc-7.3-2.96.128
* compat-libstdc++-7.3-2.96.128
* compat-gcc-c++-7.3-2.96.128
* compat-libstdc++-devel-7.3-2.96.128
* setarch-1.3-1
* pdksh-5.2.14-21 (Oracle Discoverer)
The following required component must be installed manually:
* openmotif-2.1.30-x
Note: Available on Disk 3 of Quarterly Update 4 media.
Red Hat Enterprise Linux AS/ES 4* Legacy Software Development package and X Software Development package
Note: Select these packages from the Package Group Selection screen. If the operating system is already installed, use System Settings > Add/Remove Applications to install these two packages.
The following components will be installed automatically:
* compat-db-4.1.25-9
* compat-gcc-32-3.2.3-47.3
* compat-gcc-32-c++-3.2.3-47.3
* compat-oracle-rhel4-1.0-5 (from Oracle patch 4198954)
* compat-libcwait-2.1-1 (from Oracle patch 4198954)
* compat-libgcc-296-2.96-132.7.2
* compat-libstdc++-296-2.96-132.7.2
* compat-libstdc++-33-3.2.3-47.3
* xorg-x11-deprecated-libs-devel-6.8.1-23.EL
* xorg-x11-deprecated-libs-6.8.1-23.EL
The following required component must be installed manually:
* openmotif-2.1.30-x
Note: For information on downloading the openmotif component, see the instructions at the following URL: https://rhn.redhat.com/errata/RHSA-2 005-412.html
SUSE Linux Enterprise Server 8 The following required components must be installed manually:
* openmotif-2.1.30-x
* gcc 2.95.3
* SUSE Linux Enterprise Server 8 Service Pack 3
Note:
* Download "openmotif-2.1.30-x" from:
http://support.novell.com/techcenter/search/search.do?cmd=displayKC&externalId 061;70bbf5fc1e287442b21b3c602acd7f71html
* Download the SUSE Linux Enterprise Server 8 Service Pack 3 from: http://download.novell.com/directed
* gcc 2.95.3 is included in the SUSE Linux Enterprise Server 8 operating system CDs named as gcc_old package
* Install glibc-devel during the installation of the operating system by selecting the "C/C++ Compiler and Tools" option. If the operating system is already installed, manually select the package when installing SUSE Linux Enterprise Server 8 Service Pack 3.
SUSE Linux Enterprise Server 9 The following required components must be installed manually:
* openmotif-2.1.30-x
* gcc 2.95.3
* orarun-1.8-109
Note:
* /suse/s390/openmotif21-libs-2.1.30MLI4-119.1.s390.rpm is available in SUSE Linux Enterprise Server 9 CD2
* gcc 2.95.3 is included in the SUSE Linux Enterprise Server 9 operating system CDs named as gcc_old package
* orarun-1.8-109 can be downloaded from http://ftp.novell.com/partners/oracle/sles-9/
SUSE Linux Enterprise Server 10 Service Pack 1 (SP1) or higher is required. The following components must also be installed manually:
* db1-1.85-991
* gcc 2.95.3 1
* gdbm-devel-1.8.3-243.22
* binutils-2.153
Additionally, the following must be installed manually from the SLES 10 distribution media if not already on the system:
* openmotif21-libs-2.1.30MLI4-143.2
* orarun-1.9-21.2 (for SLES 10 SP1) / orarun-1.9-21.24 (for SLES 10 SP2)
Note :
1: Download from the Novell site: ftp://ftp.novell.com/partners/oracle/ebiz11i
2: Install from SLES 10 distribution media if not already installed as part of "C/C++ Compiler & Tools" Development package
3: GNU linker (ld) version 2.15 is required for relinking the modules in Advanced Planning & Scheduling (MSC, MSO, MSR) - install it from the Novell site: ftp://ftp.novell.com/partners/oracle/ebiz11i
Solaris 8 (5.8), 9 (5.9)
J2SE Solaris Recommended Patch Cluster, dated 7/05/05 or later
HP-UX PA-RISC 11.11
PHCO_25452, PHNE_25084, PHNE_25642, PHSS_24638 (C++), GOLDQPK11i-December 01, C++ Compiler C.03.27 (or higher) or HP C/aC++ Developer's Bundle**
HP-UX PA-RISC 11.23, 11.31 C++ Compiler A.03.60 (or higher) or HP C/aC++ Developer's Bundle**
HP-UX Itanium 11.23, 11.31 None
IBM AIX 5L (5.2, 5.3)
Visual Age C++ 6.0.0.5 (or higher)3 and Oct. 2003 PTF, or IBM XL 7.0 C/C++1,2,3 runtime libraries , or IBM XL 8.0 C/C++1,2 runtime libraries. For other minimum software versions and patches required to support Oracle Products on IBM pSeries, see
My Oracle Support Document 282036.1.
For installations on 32-bit kernel AIX 5.3 Technology Level (TL) 6 with Service Pack 4 and below, please install the APAR IZ05077 or use the 64-bit kernel.
IBM AIX 6 (6.1) Service Pack 1 (AIX 6100-00-01) or higher. IBM XL 8.0 C/C++ (at least at the November 2007 PTF level - 8.0.0.17) runtime libraries. APAR IZ10223 ('Olson Timezone settings is not working for 64-bit Applications') for base level AIX (6100-00).
Windows 2000 Service Pack 2. See also General Requirements for Windows.
Windows Server 2003 None. See General Requirements for Windows.
Tuesday
Apps 11.5.10 or 11.5.10 CU1 to CU2
My database version 9.2.0.5.0
If the release level of your system is 11.5.10 or 11.5.10 CU1, follow the instructions in this section to apply CU2.
Update Steps See Metalink document-316366.1
1.Compile invalid objects
2.Run auto config on Apps and DB tier
3.Install and run the Technology Stack Validation utility to verify minimum technology component versions and other configuration requirements.
Install the utility by applying patch 4318672 on all application tier server nodes.
See the patch readme file for instructions.
Note:Follow the instructions provided by the utility to fix any failures or warnings reported. Run it again on each node that reported a failure. We highly recommend that you also correct all warnings.
Then, perform the following tasks in the order listed.
* Apply AD patch 4229931.
* Apply patch 4297568 on the concurrent processing server node.
* Apply the CU2 driver (u3460000.drv).
Post-update Steps
If you have licensed Incentive Compensation (CN) or Human Resources Intelligence (HRI), you must complete additional Discoverer End User Layer (EUL) implementation steps after you apply CU2. See Discoverer 4i End User Layer (EUL) Maintenance for Oracle Applications 11i (Doc ID: 182106.1).
If you have Forms: 6.0.8.27.x --> You are on Developer 6i Patch 18
If you have Forms: 6.0.8.26.x --> You are on Developer 6i Patch 17
If you have Forms: 6.0.8.25.x --> You are on Developer 6i Patch 16
If you have Forms: 6.0.8.24.x --> You are on Developer 6i Patch 15
************* Start of AutoPatch session *************
AutoPatch version: 11.5.0
AutoPatch started at: Mon Oct 04 2010 22:21:59
AutoPatch end time at: Oct 05 06:30
Configure Linux sendmail with GMAIL
Configure Linux sendmail with GMAIL
1.Backup /etc/mail/sendmail.mc and /etc/mail/sendmail.cf
2.Create certs dir in /etc/mail
3.Edit sendmail.mc
Add this lines
define(`CERT_DIR', `/etc/mail/certs')
define(`confCACERT_PATH', `CERT_DIR')
define(`confCACERT', `CERT_DIR/ca-bundle.crt')
define(`confCRL', `CERT_DIR/ca-bundle.crt')
define(`confSERVER_CERT', `CERT_DIR/sendmail.pem')
define(`confSERVER_KEY', `CERT_DIR/sendmail.pem')
define(`confCLIENT_CERT', `CERT_DIR/sendmail.pem')
define(`confCLIENT_KEY', `CERT_DIR/sendmail.pem')
define(`confAUTH_OPTIONS', `A')dnl
define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
TRUST_AUTH_MECH(`EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
FEATURE(`authinfo', `Hash -o /etc/mail/authinfo')dnl
define(`SMART_HOST', `smtp.gmail.com')dnl
define(`RELAY_MAILER_ARGS', `TCP $h 587')
define(`ESMTP_MAILER_ARGS', `TCP $h 587')
Note: Sometime the quotes will not copy properly, check the quotes(two different quotes is there)4. Create authinfo file in /etc/mail dir
#touch authinfo
5.Copy the following commands in the authinfo file ( Replace gmail username and password)
AuthInfo:smtp.gmail.com "U:root" "I:yourid@gmail.com" "P:
AuthInfo:smtp.gmail.com:587 "U:root" "I:yourid@gmail.com" "P:
6. Go to /etc/mail/certs dir
Run these following commands to create certificates ( give appropriate values )
#openssl req -new -x509 -keyout cakey.pem -out cacert.pem -days 3650
#openssl req -nodes -new -x509 -keyout sendmail.pem -out sendmail.pem -days 3650
7. Compile sendmail.mc file using following command
#m4 sendmail.mc > sendmail.cf
8. Restart sendmail Service
#service sendmail restart
9. Check whether mails are going
#mailx -s “Test Mail” mailid@gmail.com
Test message
.
CC .
Check the log file
#tail –f /var/log/maillog
Now we can able to use this smtp relay with other application
Note:
Give smtp server name as “ localhost “ and Port 25 . it will work with localhost name only.
In Oracle Applications - We can use this . In OAM workflow mailer configuration give outbound server name “localhost” .
Then you can receive workflow notification mails, alert mails and all Apps related mails.
Friday
View Oracle Apps Table space free size and used in percentage
SELECT /* + RULE */ df.tablespace_name "Tablespace",
df.bytes / (1024 * 1024) "Size (MB)",
SUM(fs.bytes) / (1024 * 1024) "Free (MB)",
Nvl(Round(SUM(fs.bytes) * 100 / df.bytes),1) "% Free",
Round((df.bytes - SUM(fs.bytes)) * 100 / df.bytes) "% Used"
FROM dba_free_space fs,
(SELECT tablespace_name,SUM(bytes) bytes
FROM dba_data_files
GROUP BY tablespace_name) df
WHERE fs.tablespace_name (+) = df.tablespace_name
GROUP BY df.tablespace_name,df.bytes
UNION ALL
SELECT /* + RULE */ df.tablespace_name tspace,
fs.bytes / (1024 * 1024),
SUM(df.bytes_free) / (1024 * 1024),
Nvl(Round((SUM(fs.bytes) - df.bytes_used) * 100 / fs.bytes), 1),
Round((SUM(fs.bytes) - df.bytes_free) * 100 / fs.bytes)
FROM dba_temp_files fs,
(SELECT tablespace_name,bytes_free,bytes_used
FROM v$temp_space_header
GROUP BY tablespace_name,bytes_free,bytes_used) df
WHERE fs.tablespace_name (+) = df.tablespace_name
GROUP BY df.tablespace_name,fs.bytes,df.bytes_free,df.bytes_used
ORDER BY 4 DESC;
Sample output:
Tablespace Size (MB) Free (MB) % Free % Used
------------------------------ ---------- ---------- ---------- ----------
UNDOTBS1 65 17.8125 27 73
EXAMPLE 100 22.625 23 77
USERS 5 1.0625 21 79
TEMP 20 2 10 90
SYSAUX 625.125 54.5 9 91
SYSTEM 700 9.0625 1 99