Search This Blog

Wednesday, December 15, 2010

Reinstalling OEM 11g

  • When reinstalling OEM 11g from any reasons don’t forget to clean up your environment from previous installation attempts.
  • Clean up ORACLE_HOME directories on OMS server
  • Get rid of EM stuff from EM managed database

  • The first issue I faced is the existence of SYSMAN schema. I ran the following command to drop it:
[oracle@host ~]$  $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD / 
<sys pasword> -SYSMAN_PWD <sysman password>
  • Also drop “sysman_mds” schema and recompile invalid objects (if applicable) in DBSNMP and MGMT_VIEWschemas. Re-compile invalid objects using:
SQL> @$ORACLE_HOME/sysman/admin/emdrep/sql/core/latest/admin/admin_recompile_invalid.sql SYSMAN
  • After the above script was executed you must check invalid objects:
  • SQL> select count(*) from dba_objects where status<>'INVALID';

  • If invalid objects still exists you must re-compile them: see http://dbataj.blogspot.com/2007/08/how-to-compile-invalid-objects.html

  • During the first install the MDS Schema Configuration inserts 1 line into table SCHEMA_VERSION_REGISTRY. When reinstalling OEM "MDS Schema Configuration" will fail.
  • Don’t forget to delete that entry from SCHEMA_VERSION_REGISTRY table:
SQL> delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services';

  • Then retry and the "MDS Schema Configuration" will be configured successfully.

Friday, December 10, 2010

11g Grid Control - how to change the OMS Repository Database Listener Port or Hostname

In versions prioor to 11g Grid Control we had to update the emoms.properties file in case we needed to modify the Listener Port used to connect to the repository database. But in 11g OEM, it has been changed and we now have to use the emctl command.

There are a lot of other options added to the emctl command which can be seen via the emctl -help command.
To change the listener port or the hostname of the Repository Database we now have to use the emctl config oms command as shown below.
emctl config oms -store_repos_details -repos_port 1528 -repos_sid emrep -repos_host wintest01 -repos_user SYSMAN -repos_pwd oracle11g
To check what are the OMS Repository details we can use the emctl config oms -list_repos_details command.
For example –
D:\Oracle\Product\Middleware\oms11g\BIN>emctl config oms -list_repos_details
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Repository Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=wintest01)(PORT=1528)))(CONNECT_DATA=(SID=emrep)))
Repository Host : wintest01
Repository Port : 1528
Repository SID : emrep
Repository User : SYSMAN
The emoms.properties file actually has these lines ….
###########################################################################################################
##################################### README ###########################################
###########################################################################################################
#NOTE
#—-
#1. EMOMS(LOGGING).PROPERTIES FILE HAS BEEN REMOVED
#2. OMS PROPERTIES / LOGGING PROPERTIES SHOULD BE MODIFIED USING EMCTL GET/SET/DELETE/LIST PROPERTY COMMANDS
#3. The USAGE OF EMCTL GET/SET/DELETE/LIST PROPERTY IS PROVIDED BELOW, BUT
# FOR LATEST UPDATED COMMANDS PLEASE CHECK EMCTL HELP MESSAGE

Tuesday, December 7, 2010

Installing Oracle Management Agent 11g with response file

Hello Again,

As you know, we installed Oracle EM Grid control 11g in Linux server 2 day ago, now we are trying install management agent in server where is our DB's

First of all download install packages from:
http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html

Our example is for :
Agent Software for 64-bit Platforms,Linux x86-64

1. copy zip files in server

2. unzip Linux_x86_64_Grid_Control_agent_download_11_1_0_1_0.zip file(for example /0 folder)

3. make changes on file additional_agent.rsp located linux_x64/response sub folder.

We should set some init parameters

SECURITY_UPDATES_VIA_MYORACLESUPPORT=FALSE
DECLINE_SECURITY_UPDATES=TRUE
ORACLE_AGENT_HOME_LOCATION=/u1/app/oracle/agent11g(you can change as you wish)
OMS_HOST=OEMserver (host where is installed EM grid 11g)
OMS_PORT=4889
AGENT_REGISTRATION_PASSWORD=****** (Agent registration password, if you set it during Oracle EM installation )

4. execute runinstaller with specified parameters
./runInstaller -silent -responseFile /0/linux_x64/response/additional_agent.rsp


Source: http://vmantua.blogspot.com/2010/05/installing-oracle-management-agent-11g.html

Installing Oracle Management Agent Using Response File

This chapter describes how you can install Oracle Management Agent (Management Agent) using a response file. In particular, this section covers the following:

Overview

By default, the Management Agent software comes with a response file, additional_agent.rsp, which helps you install a Management Agent silently, without having to use the GUI screens of Enterprise Manager Grid Control. The response file captures all the information required for installing a Management Agent, and it is available in the//response directory.
For example, if you have an Oracle Management Service (OMS) running on a Linux host and if you have the Management Agent software on that host, then the response file is available at oms11g/sysman/agent_download/11.1.0.1.0/linux/response/additional_agent.rsp. And, if you do not have an OMS but if you have downloaded the Management Agent software for Linux operating system to /private/temp, then the response file is available at/private/temp/linux/response/additional_agent.rsp.
This installation type is best suited when you want to install additional Management Agents on the destination hosts, from the destination hosts itself, and without having to use the Agent Deployment Wizard in the Enterprise Manager Grid Control console.
The following are the basic differences between Agent Deployment Wizard and the additional_agent.rsp file.
  • While the Agent Deployment Wizard is GUI-based, the additional_agent.rsp file is file -based. Therefore, using the file is a silent, non-GUI way of installing Management Agents.
  • If you use the Agent Deployment Wizard, then you will have to use the interview screens and provide basic source details every time you install a Management Agent. If you use the additional_agent.rsp file, then you will update a response file with the basic source details for once and use the same response file for multiple installations.
  • While the Agent Deployment Wizard can be run from a source or destination host, the additional_agent.rsp file must be run only from a destination host. Therefore, if you want to install only a few Management Agents, then use the additional_agent.rsp file.
  • While the Agent Deployment Wizard enables you to install multiple Management Agents at a time, the additional_agent.rsp file enables you to install only one Management Agent at a time.
  • The Agent Deployment Wizard pushes the software binaries from a central source location to the destination hosts. The additional_agent.rsp file pulls the software binaries from the source host to the destination hosts.

Prerequisites

Before installing the Management Agent, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 12-1 Prerequisites for Installing Oracle Management Agent Using Response File
RequirementDescriptionYes/No
Hardware Requirements
Ensure that you meet the hard disk space and physical memory requirements as described inAppendix A, "Meeting Hardware Requirements".
Operating System Requirements
Ensure that you install the Management Agent only on certified operating systems as mentioned inMy Oracle Support note 412431.1.
Package Requirements
Ensure that you install all the platform-specific packages as described in Appendix B, "Meeting Package and Library Requirements ".
User and Operating System Group Requirement
Ensure that the destination host where you want to install the Management Agent has the appropriate users and operating system groups created.
For information about creating operating system groups and users, see Appendix C, "Creating Operating System Groups and Users Requirements".
Temporary Directory Space Requirements
Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. For example, /tmp on UNIX hosts and c:\Temp on Microsoft Windows hosts.
Central Inventory Requirements
Ensure that you allocate 100 MB of space for the central inventory directory.
Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.
Installation Base Directory Requirements
Ensure that the installation base directory you specify in the response file is empty and has writepermission.
Software Availability Requirements
By default, the software for Oracle Management Agent 11g Release 1 is available on the host where Oracle Management Service 11g Release 1 is running. However, this Management Agent software is for the platform on which the OMS is running.
Therefore, if you have an OMS and if you want to install Oracle Management Agent 11g Release 1 on a platform that is the same as the one on which the OMS is running, then you already meet this prerequisite; you do not have to take any action.
However, if you do not have an OMS or if you want to install Oracle Management Agent 11g Release 1 on a platform that is different from the one on which the OMS is running, then ensure that you download the Management Agent software for that platform.
For more information about downloading the Management Agent software, see Procuring Oracle Management Agent Software.
Destination Host Requirements
Ensure that all the destination hosts have the same operating system credentials and file system structure.
/etc/hosts File Requirements
If the destination host and the host on which OMS is running belong to different network domains, then ensure that you update the /etc/hosts file on the destination host to add a line with the IP address of that host, the fully-qualified name of that host, and the short name of the host.
For example, if the fully-qualified host name is mypc.cn.company.com and the short name is mypc, then add the following line in the /etc/hosts file:
12.123.123.12 mypc.cn.company.com mypc
Installing User Requirements
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group.
Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory.
For example, if the inventory owner is user1, and user installing the Management Agent is user2, then ensure that user1 and user2 belong to the same group, and they have read and write access to the inventory.
Permission Requirements
  • Ensure that you have readwrite, and execute permissions on oraInventory on all remote hosts. If you do not have these permissions on the default inventory (typically at/etc/oraInst.loc) on any remote host, then you can specify the path to an alternative inventory location by using the -i  option in the Additional Parameters section.
    For information about oraInventory permissions, see What Is Oracle Inventory Directory?.
  • Ensure that you have write permission on the Installation Base Directory and the temporary directory where the executables will be copied. For example, /tmp or c:\Temp.
SUDO Privilege Requirement
Ensure that you have SUDO privileges to run root.sh and /bin/sh (UNIX platforms only). You must specify the invoking user's password here.
To verify whether you have SUDO privileges to run these files, access the /etc/sudoers file and check whether you have a similar entry as shown below. If you do not see a similar entry, then add one.
=PASSWD: /home/em/agent11010/agent11g/root.sh, /bin/sh
SUDOERS File Configuration Requirements
Ensure that you configure /etc/sudoers file so that while running a command using SUDO, you are always prompted for a password.
If /etc/sudoers file is configured in such a way that SUDO never prompts for a password, then a directory with the host password as the title gets created in the invoking users home directory.

Installation Procedure

To install a Management Agent using the response file, follow these steps:
  1. Navigate to the location where the Management Agent software is available.
    For example, oms11g/sysman/agent_download/11.1.0.1.0/linux if the Management Agent software is available in the Oracle home of the OMS.
    Alternatively, /private/temp/11.1.0.1.0/linux if you have downloaded the Management Agent software to /private/temp on your local system.
  2. Compress the files from the  directory using the WinZIP utility, and transfer the compressed file to the destination host where you want to install the Management Agent. For example, linux.zip.
  3. On the destination host, do the following:
    1. Extract the contents of the compressed file you just transferred.
    2. Navigate to the following location and edit the additional_agent.rsp file as described in Table 12-2.
      //response/ additional_agent.rsp
      For example:
      /scratch/john/linux/response/ additional_agent.rsp
    3. Navigate to the following location and invoke the installer:
      If this is the first Oracle product you are installing on the host, then run the following command:
      //agent/runInstaller -silent -responseFile /additional_agent.rsp [-invPtrLoc ]
      For example,
      /scratch/john/linux/agent/runInstaller -silent -responseFile /scratch/john/linux/response/additional_agent.rsp -invPtrLoc /scratch/OracleHomes/oraInst.loc
      Otherwise, run the following command:
      //agent/runInstaller -silent -responseFile /additional_agent.rsp
      For example,
      /scratch/john/linux/agent/runInstaller -silent -responseFile /scratch/john/linux/response/additional_agent.rsp
Note:
  • For Microsoft Windows platforms, run setup.exe instead of runInstaller.
  • After the installation ends successfully, the Management Agent starts automatically. If you do not want it to start automatically, then invoke the installer with the b_startAgent=false argument.
  • If the installation fails, then review the log files described in Appendix L, "Installation and Configuration Log Files".
Table 12-2 Modifying Parameters for Installing Additional Oracle Management Agent
ParameterDescription
SECURITY_UPDATES_VIA_MYORACLESUPPORT
  • Specify TRUE if you want to download and install security updates. Then, specify the credentials for the following parameters:
    MYORACLESUPPORT_USERNAME
    MYORACLESUPPORT_PASSWORD
  • Specify FALSE if you do not want to download and install security updates:
DECLINE_SECURITY_UPDATES
  • Specify TRUE if you want to decline the security updates. In this case, you should have specified FALSE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.
  • Specify FALSE if you do not want to decline the security updates. In this case, you should have specified TRUE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.
ORACLE_AGENT_HOME_LOCATION
Specify the full path to the installation base directory where you want to install the Management Agent. The Oracle home of the Management Agent is created inside this installation base directory.
For example, if you specify the installation base directory as /home/john/, then the Oracle home is created as /home/john/agent11g.
For information about installation base directory, see What Is Installation Base Directory?.
OMS_HOST
Specify the name of the host on which the OMS is running.
OMS_PORT
Specify the port used by the OMS.
AGENT_REGISTRATION_PASSWORD
To secure the communication between the OMS and the Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.

After You Install

After you install the Management Agent, do these:
  1. Verify the installation:
    1. Navigate to the Oracle home of the Management Agent and run the following command to see a message that confirms that the Management Agent is up and running:
      $/bin/emctl status agent
      Note:
      If the status of the Management Agent is down for some reason, then manually start the Management Agent by running the following command from its Oracle home:$/bin/emctl start agent
    2. Navigate to the Oracle home of the Management Agent and run the following command to see a message that confirms that EMD upload completed successfully:
      $/bin/emctl upload
    Note:
    (For UNIX operating systems) Before running the emctl command to start the Management Agent, ensure that the environment variable NLS_LANG is set with a value that is compatible with the operating system default locale setting and the character set of the Oracle Database, which houses the Management Repository.
  2. (Only for UNIX Operating Systems) Run the following scripts as a root user on each of the hosts where the installation was done:
    • If you have not specified the inventory location while invoking the installer and if this is the first Oracle product you just installed on the host, then run theoraInstRoot.sh script from the Central Inventory:
      $HOME/oraInventory/oraInstRoot.sh
      For example, if you are using SUDO to change to a root user, then you will run the following command:
      /usr/local/bin/sudo $Home/oraInventory/oraInstRoot.sh
      
    • Run the root.sh script from the Oracle home of the Management Agent (agent11g):
      /root.sh
      For example, if you are using SUDO to change to a root user, then you will run the following command:
      /usr/local/bin/sudo /scratch/OracleHomes/agent11g/root.sh
      
  3. (Optional) If you have not secured the communications between the Management Agent and the OMS, then secure it by running the following command from the Oracle home of the Management Agent:
    /bin/emctl secure agent
    Note:
    Even after securing the Management Agent, some data might still be transferred over the network without being encrypted.
  4. (Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca script to reconfigure and discover all new targets.
    For information about the agentca script, see What Is Agent Configuration Assistant Used For?.
    For information about reconfiguring the Management Agent and discovering all new targets, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".
  5. (Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.
    For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.
    For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.
    Both these guides are available at:
    http://www.oracle.com/technology/documentation/oem.html

Wednesday, November 10, 2010

ORA-00845: MEMORY_TARGET not supported on this system

SQL> STARTUP
ORA-00845: MEMORY_TARGET not supported on this system
Cause of the Problem
-Starting from Oracle 11g the automatic memory management feature is now defined with parameter MEMORY_TARGET and MEMMORY_MAX_TARGET.
-On linux file system the shared memory need to be mounted on /dev/shm directory on the operating system.
-And the size of /dev/shm needs to be greater than MEMORY_TARGET or MEMMORY_MAX_TARGET.
-The AMM (Automatic Memory Management) now in 11g manages both SGA and PGA together by MMAN process.
-The MEMORY_TARGET parameter in 11g comes for (SGA_TARGET+PGA_AGGREGATE_TARGET) which was in 10g.
-And MEMORY_MAX_TARGET parameter in 11g comes instead of SGA_MAX_TARGET parameter which was in 10g.
-The ORA-00845:can arises for the following two reasons on linux system.
1)If the shared memory which is mapped to /dev/shm directory is less than the size of MEMORY_TARGET or MEMORY_MAX_TARGET.
or,
2)If the shared memory is not mapped to /dev/shm directory.

Solution 
Make sure /dev/shm is properly mounted. You can see it by,
df -h
The output should be similar like
$ df -k
Filesystem            Size  Used Avail Use% Mounted on

shmfs                 3G    1000M 1000M  50% /dev/shm
We see here for /dev/shm we have assigned 3G memory. Now if you set MEMORY_TARGET more than 3G then above ORA-845 will arise.
For example if you have MEMORY_TARGET or MEMORY_MAX_TARGET set to 3G then you can mount shared memory to 3G like below.
As a root user,
# mount -t tmpfs shmfs -o size=3g /dev/shm
In order to make the settings persistence so that it will affect after restarting machine add an entry in /etc/fstab similar to the following:
shmfs /dev/shm tmpfs size=3g 0

Tuesday, November 9, 2010

Can not connect to Oracle 11g from TOAD but SQLPLUS is can

If you have set the SEC_CASE_SENSITIVE_LOGON parameter to true, then the database expects "case sensitive" passwords. TOAD somehow seems to convert the passwords to uppercase before logon.

Workarounds: 

1) Set your password in the database to UPPER case -- or --
2) Set SEC_CASE_SENSITIVE_LOGON parameter to false.

Monday, November 1, 2010

Linux Hard Disk Format Command

here are total 4 steps involved for hard disk upgrade and installation procedure:

Step #1 : Partition the new disk using fdisk command

Following command will list all detected hard disks:
# fdisk -l | grep '^Disk'
Output:

Disk /dev/sda: 251.0 GB, 251000193024 bytes
Disk /dev/sdb: 251.0 GB, 251000193024 bytes

A device name refers to the entire hard disk. For more information see Linux partition naming convention and IDE drive mappings.
To partition the disk - /dev/sdb, enter:
# fdisk /dev/sdb
The basic fdisk commands you need are:
  • m - print help
  • p - print the partition table
  • n - create a new partition
  • d - delete a partition
  • q - quit without saving changes
  • - write the new partition table and exit

Step#2 : Format the new disk using mkfs.ext3 command

To format Linux partitions using ext2fs on the new disk:
# mkfs.ext3 /dev/sdb1

Step#3 : Mount the new disk using mount command

First create a mount point /disk1 and use mount command to mount /dev/sdb1, enter:
# mkdir /disk1
# mount /dev/sdb1 /disk1
# df -H

Step#4 : Update /etc/fstab file

Open /etc/fstab file, enter:
# vi /etc/fstab
Append as follows:

/dev/sdb1               /disk1           ext3    defaults        1 2

Save and close the file.

Task: Label the partition

You can label the partition using e2label. For example, if you want to label the new partition /backup, enter
# e2label /dev/sdb1 /backup
You can use label name insted of partition name to mount disk using /etc/fstab:
LABEL=/backup /disk1 ext3 defaults 1 2

Wednesday, October 27, 2010

Platform-Specific Package and Kernel Requirements

This appendix lists the recommended software packages and kernel parameters required for a successful Enterprise Manager Grid Control installation on each of the supported platforms. For the most current list of supported operating system-specific software, refer to My Oracle Support (formerly Metalink) at http://metalink.oracle.com.
This appendix has the following sections:

Package Requirements

The following sections list the package requirements for each platform.

Required Packages on Linux

The following (or later) packages must be running on your Linux systems.
Red Hat Enterprise Linux 3.0
  • glibc-2.2.4-31.7
  • make-3.79
  • binutils-2.11.90.0.8-12
  • gcc-2.96
  • openmotif21-2.1.30-9
Red Hat Enterprise Linux 4.0
  • glibc-2.3.4-2.9
  • glibc-devel-2.3.4-2.9.i386.rpm
  • make-3.79
  • binutils-2.15.92.0.2-13
  • gcc-3.4.3-22.1
  • libaio-0.3.96
  • glibc-common-2.3.4-2.9
  • setarch-1.6-1
  • pdksh-5.2.14-30
  • openmotif21-2.1.30-11
  • sysstat-5.0.5-1
  • gnome-libs-1.4.1.2.90-44.1
  • libstdc++-3.4.3-22.1
  • libstdc++devel-3.4.3-22.1
  • compat-libstdc++-296-2.96-132.7.2
  • compat-db-4.1.25-9
  • control-center-2.8.0-12
  • xscreensaver-4.18-5.rhel4.2
Red Hat Enterprise Linux 5.x
  • make-3.79
  • binutils-2.14
  • gcc-3.2
  • libXp.so.6
SUSE Linux Enterprise Server 9
  • glibc-2.2.4-31.7
  • make-3.79
  • binutils-2.11.90.0.8-12
  • gcc-c++
  • db1
  • gnome-libs
  • orbit
SUSE Linux Enterprise Server 10
IMPORTANT:
This platform is supported only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
  • make-3.79
  • binutils-2.14
  • gcc-3.2
Oracle Enterprise Linux 4
IMPORTANT:
This platform is supported only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
  • make-3.79
  • binutils-2.14
  • gcc-3.2
Oracle Enterprise Linux 5
IMPORTANT:
This platform is supported only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
  • make-3.79
  • binutils-2.14
  • gcc-3.2

Required Packages for Linux x86_64

The following (or later) package versions must be running on your Linux x86_64 systems:
For Red Hat Enterprise Linux 3.0
  • glibc-2.2.4-31.7
  • make-3.79
  • binutils-2.11.90.0.8-12
  • gcc-2.96
  • openmotif2.1.30-11
For Red Hat Enterprise Linux 4.0
  • glibc-2.3.4-2.9
  • make-3.79
  • binutils-2.15.92.0.2-13
  • gcc-3.4.3-22.1
  • libaio-0.3.96
  • glibc-common-2.3.4-2.9
  • setarch-1.6-1
  • pdksh-5.2.14-30
  • openmotif21-2.1.30-11
  • sysstat-5.0.5-1
  • gnome-libs-1.4.1.2.90-44.1
  • libstdc++-3.4.3-22.1
  • compat-db-4.1.25-9
  • control-center-2.8.0-12
  • xscreensaver-4.18-5.rhel4.2
  • libstdc++devel-3.4.3-22.1
  • compat-libstdc++-296-2.96-132.7.2
  • glibc-devel-2.3.4-2.9.i386.rpm
  • libgcc-3.2.3-20.i386.rpm
  • compat-gcc-7.3-2.96.122.i386.rpm
  • compat-glibc-7.x-2.2.4.32.5.i386.rpm
For Red Hat Enterprise Linux 5.x
  • make-3.79
  • binutils-2.14
  • gcc-3.2
  • libXp.so.6
For SUSE Linux Enterprise Server 9
  • glibc-2.2.4-31.7
  • make-3.79
  • binutils-2.11.90.0.8-12
  • gcc-2.96
  • openmotif2.1.30-11
For SUSE Linux Enterprise Server 10
  • make-3.79
  • binutils-2.14
  • gcc-3.2
For Oracle Enterprise Linux 4
  • make-3.79
  • binutils-2.14
  • gcc-3.2
For Oracle Enterprise Linux 5
  • make-3.79
  • binutils-2.14
  • gcc-3.2

Required Packages on Solaris

The following (or later) package versions must be running on your Solaris systems:
  • SUNWarc
  • SUNWbtool
  • SUNWhea
  • SUNWlibm
  • SUNWlibms
  • SUNWsprot
  • SUNWsprox
  • SUNWtoo
  • SUNWi1of
  • SUNWxwfnt
To check if the required operating system packages have been installed on your system, enter the following command:
prompt> pkginfo SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1 of SUNWxwfnt
Note:
If any packages are missing, contact your system administrator.

Checking for 32-Bit and 64-Bit Application Support

Check whether or not your system is configured to support 32-bit and 64-bit applications by entering the following command:
prompt> /usr/bin/isainfo -v

Required Patches

The patches required for the different Solaris versions are the following:
Solaris 8
  • 108652-74 or later: X11 6.4.1: Xsun patch
  • 108921-18 or later: CDE 1.4: dtwm patch
  • 108940-57 or later: Motif 1.2.7 and 2.1.1: Runtime library patch
  • 108773-18 or later: IIIM and X input and output method patch
  • 111310-01 or later: /usr/lib/libdhcpagent.so.1 patch
  • 109147-26 or later: Linker patch
  • 111308-04 or later: /usr/lib/libmtmalloc.so.1 patch
  • 111111-03 or later: /usr/bin/nawk patch
  • 112396-02 or later: /usr/bin/fgrep patch
  • 110386-03 or later: RBAC feature patch
  • 111023-02 or later: /kernel/fs/mntfs and /kernel/fs/sparcv9/mntfs patch
  • 108987-13 or later: Patch for patchadd and patchrm
  • 108528-26 or later: Kernel update patch
  • 108989-02 or later: /usr/kernel/sys/acctctl and /usr/kernel/sys/exacctsys patch
  • 108993-45 or later: LDAP2 client, libc, libthread and libnsl libraries patch
  • 111023-02 or later: Unable to load fontset ... iso-1 or iso-15
Solaris 9
  • 113096-03 or later: X11 6.6.1: OWconfig patch
  • 112785-35 or later: X11 6.6.1: Xsun patch

Checking for Patches

To determine the patches that have been installed on the system, follow these steps:
  1. Run the showrev command with the -p option. The following command saves the sorted output to a file called patchList.
  2. Enter the following command:
    prompt> showrev -p | sort > patchList
     
  3. Open the file in a text editor and search for the patch numbers.
Note:
If the required patches have not been installed, you can download them from http://sunsolve.sun.com.

Required Packages on HP-UX PA-RISC

The following (or later) package versions must be running on your HP-UX PA-RISC systems:
HP-UX PA-RISC 11i V1 (11.11)
  • For installation on HP-UX PA-RISC 11.11, the following packages or later versions are required:
    • HP-UX PA-RISC 11i June 2003 Consolidated Quality Patch Bundle
    • Jun03GQPK11i_Aux_Patch
  • Make sure that Motif 2.1 Development Environment (X11MotifDevKit.MOTIF21-PRG)B.11.11.01 is installed
    Either install this package or create symbolic links as follows:
    1. Log in as root.
    2. Change directory to /usr/lib as follows:
      # cd /usr/lib
    3. Create the required links:
      # ln -s libX11.3 libX11.sl
      # ln -s libXIE.2 libXIE.sl
      # ln -s libXext.3 libXext.sl
      # ln -s libXhp11.3 libXhp11.sl
      # ln -s libXi.3 libXi.sl
      # ln -s libXm.4 libXm.sl
      # ln -s libXp.2 libXp.sl
      # ln -s libXt.3 libXt.sl
      # ln -s libXtst.2 libXtst.sl
  • The following patches or later are required:
    • PHCO_28123, cumulative SAM patch
    • PHKL_29198, Psets Enablement Patch
    • PHNE_28476, Cumulative STREAMS Patch
    • PHNE_28923, LAN product cumulative patch
    • PHSS_28871, ld(1) and linker tools cumulative patch
    • PHSS_28880, HP aC++ -AA runtime libraries (aCC A.03.50)
    • PHCO_26331, mountall cumulative patch
    • PHCO_29109, Pthread enhancement and fixes
    • PHKL_25468, eventport (/dev/poll) pseudo driver
    • PHKL_25842, Thread Abort
    • PHKL_25993, thread nostop for NFS, rlimit, Ufalloc fix
    • PHKL_25994, Thread NOSTOP, Psets Enablement, Ufalloc
    • PHKL_25995, eventport syscalls; socket close(2); Ufalloc
    • PHKL_26468, Shared mutex synchronization support patch
    • PHKL_28489, copyin EFAULT, LDCD access type
  • To determine whether or not a bundle, a product, or file set is installed, enter a command similar to the following, where level refers to the bundle, patch or file set.
    # /usr/sbin/swlist -l level |more
HP-UX PA-RISC 11i V2 (11.23)
  • For installation on HP-UX PA-RISC 11.23, the following packages or later versions are required:
    • Patch Bundle for HP-UX PA-RISC 11i V2 (B.11.23), September 2004
    • BUNDLE11i, Revision B.11.23.0409.3
HP-UX PA-RISC 11i V3 (11.31)
  • Base-VXFS- B.11.31
  • OnlineDiag- B.11.31.01.03

Required Packages for HP-UX Itanium

The following (or later) package versions must be running on your HP-UX Itanium systems:
HP-UX IA-64 11i V2 (11.23)
  • For installation on HP-UX 11.23, the following packages or later versions are required:
    • Patch Bundle for HP-UX 11i V2 (B.11.23), September 2004
    • BUNDLE11i, Revision B.11.23.0409.3
  • The following patches or later versions are required:
    • PHSS_31849:linker + fdp cumulative patch
    • PHSS_31852: aC++ Runtime (PA A.03.61)
HP-UX IA-64 11i V3 (11.31)
IMPORTANT:
This platform is supported only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
  • For installation on HP-UX 11.31, the following packages or later versions are required:
    • BUNDLE-B.11.31
  • The following operating system patches or later versions are required:
    • PHKL_35936

Required Packages on AIX

The follwoing packages must be running on your AIX systems:
AIX 5L Version 5.2
The following file sets must be installed and committed:
  • bos.perf.libperfstat
  • bos.perf.proctools
The following Authorized Problem Analysis Reports (APARs) must be installed:
  • IY43980: libperfstat.h not ANSI-compliant
  • IY44810: DSI IN BMRECYCLE
  • IY45462: Definition of isnan() in math.h incorrect
  • IY45707: J2 READAAHEAD/CIO INTERACTION
  • IY46214: dropping partial connections leaves them on so_q0
  • IY46605: exec of 32 bit application can fail on 64 bit kernel
  • IY51801: race condition in aio_nwait_timeout
AIX 5L Version 5.3
The following file sets must be installed and committed:
  • bos.perf.libperfstat
  • bos.perf.proctools
The following Authorized Problem Analysis Reports (APARs) must be installed:
  • IY70159: KRTL relocation problem
  • IY68989: write to mmapped space hangs
AIX 6L Version 6.1
IMPORTANT:
This platform is supported only for Enterprise Manager 10g Grid Control Release 5 (10.2.0.5).
The following file sets must be installed and committed:
  • bos.adt.base-0.0
  • bos.adt.lib-0.0
  • bos.adt.libm-0.0
  • bos.perf.libperfstat-0.0
  • bos.perf.perfstat-0.0
  • bos.perf.proctools-0.0
  • rsct.basic.rte-0.0
  • rsct.compat.clients.rte-0.0
  • xlC.aix61.rte-9.0.0.0
  • xlC.rte-9.0.0.0

To Verify Whether the Filesets Are Installed and Committed

To determine whether or not the required file sets are installed and committed, execute the foollowing command:
# lslpp -l bos.adt.base bos.adt.lib bos.adt.libm \
bos.perf.perfstat bos.perf.libperfstat 
Note:
If a file set is not installed and committed, you need to install it. Refer to your operating system or software documentation for information on handling file sets.

Verify Whether or Not APAR is Installed

To determine whether or not an authorized program analysis report (APAR) is installed, execute the following command:
# /usr/sbin/instfix -i -k " IY43980, IY44810,..."
Note:
If an APAR is not installed, you need to install it. For installing and downloading the APAR, refer to:
https://techsupport.services.ibm.com/server/aix.fdc

Kernel Parameter Requirements

The following sections list the kernel parameter requirements for each platform.

Kernel Parameter Requirements on Linux

The systems must have at least the following recommended kernel parameters:
Red Hat Enterprise Linux 3.0, SUSE Linux Enterprise Server 9, and SUSE Linux Enterprise Server 10
  • semmsl = 250
  • semmns = 32000
  • semopm = 100
  • semmni = 128
  • shmmax = 2147483648
  • shmmni = 4096
  • shmall = 2097152
  • shmmin = 1
  • shmseg = 10
  • filemax = 65536
Red Hat Enterprise Linux 4.0, Red Hat Enterprise Linux 5.x, Oracle Enterprise Linux 4, and Oracle Enterprise Linux 5
  • semmsl = 250
  • semmsl2 = 250
  • semmns = 32000
  • semopm = 100
  • semmni = 128
  • shmmax = 536870912
  • shmmni = 4096
  • shmall = 2097152
  • filemax = 65536
  • ip_local_port_range = 1024 65000
  • rmem_default = 262144
  • rmem_max = 262144
  • wmem_default = 262144
  • wmem_max = 262144
To check your kernel parameter settings, run the commands listed in Table D-1.
Table D-1 Execute Commands to Check Kernel parameter Settings
Parameter Command
semmsl, semmns, semopm, semmni
# /sbin/sysctl -a | grep semFoot 1 
shmall, shmmax, shmmni
# /sbin/sysctl -a | grep shm
file-max
# /sbin/sysctl -a | grep file-max
ip_local_port_range
# /sbin/sysctl -a | grep ip_local_port_range
rmem_default
# /sbin/sysctl -a | grep rmem_default
rmem_max
# /sbin/sysctl -a | grep rmem_max
wmem_default
# /sbin/sysctl -a | grep wmem_default
wmem_max
# /sbin/sysctl -a | grep wmem_max
Footnote 1 This command displays the value of the four semaphore parameters in the order listed.
To change your kernel parameter settings, use any text editor to create or edit the /etc/sysctl.conf file to add or modify the necessary entries. You may need to restart your system after changing kernel parameters.
Note:
Include lines only for the kernel parameter values that you want to change. For the semaphore parameters (kernel.sem), you must specify all four values in order. If the current value of any of your system's kernel parameters is higher than the recommended value, keep your current value.
For example, your /etc/sysctl.conf file may look like this:
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
rmem_default = 262144
rmem_max = 262144
wmem_default = 262144
wmem_max = 262144
By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system.
On SUSE systems only, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:
# /sbin/chkconfig boot.sysctl on

Kernel Parameter Requirements on Linux x86_64

The systems must have at least the following recommended kernel parameters:
Red Hat Enterprise Linux 3.0, SUSE Linux Enterprise Server 9, SUSE Linux Enterprise Server 10
  • semmsl = 250
  • semmns = 32000
  • semopm = 100
  • semmni = 128
  • shmmax = 2147483648
  • shmmni = 4096
  • shmall = 2097152
  • shmmin = 1
  • shmseg = 10
  • filemax = 65536
Red Hat Enterprise Linux 4.0, Red Hat Enterprise Linux 5.x, Oracle Enterprise Linux 4.0, Oracle Enterprise Linux 5.0
  • semmsl = 250
  • semmsl2 = 250
  • semmns = 32000
  • semopm = 100
  • semmni = 128
  • shmmax = 536870912
  • shmmni = 4096
  • shmall = 2097152
  • filemax = 65536
  • ip_local_port_range = 1024 65000
  • rmem_default = 262144
  • rmem_max = 262144
  • wmem_default = 262144
  • wmem_max = 262144

Kernel Parameter Requirements on Solaris

The system must have at least the following recommended kernel parameters:
Solaris 8 and 9
Verify that the following kernel parameters have been set to a equal to or greater than the value specified in Table D-2.
Table D-2 Recommended Kernel Parameter Values for Solaris 8 and 9
Parameter Recommended Value
semsys:seminfo_semmni
100
semsys:seminfo_semmsl
256
shmsys:shminfo_shmmax
4294967295
shmsys:shminfo_shmmin
1
shmsys_shminfo_shmmni
100
shmsys:shminfo_shmseg
10
semsys:seminfo_semvmx
32767
noexec_user_stack
1
Note:
The following parameters are obsolete in Solaris 9:
  • shmsys:shminfo_shmmin
  • shmsys:shminfo_shmseg
Solaris 10
On Solaris 10, verify that the kernel parameters shown in Table D-3 are set to values equal to or greater than the recommended values. Table D-3 also lists the resource controls that replace the /etc/system file for a specific kernel parameter.
Table D-3 Recommended Kernel Parameter Values for Solaris 10
Parameter Resource Control Recommended Values
noexec_user_stack
NA
1

View and Change Kernel Parameter Values on Solaris 8 and 9

To view the current values of the kernel parameters, enter the following commands:
# grep noexec_user_stack/etc/system
# /usr/sbin/sysdef | grep SEM
# /usr/sbin/sysdef | grep SHM
To change any of the current values, follow these steps:
  1. Create a backup copy of the /etc/system file, by using a command similar to the following:
    # cp /etc/system/etc/system.orig
  2. Open the /etc/system file in any text editor, and if required, add lines similar to the following (edit the lines if the file already contains them):
    set semsys:seminfo_semmni=  100
    set semsys:seminfo_semmsl        =256
    set shmsys:shminfo_shmmax        =4294967295
    set shmsys:shminfo_shmmin        =1
    set shmsys_shminfo_shmmni= 100
    set shmsys:shminfo_shmseg        =10
    set semsys:seminfo_semvmx        =32767
    set noexec_user_stack     =1
  3. Enter the following command to restart the system
    # /usr/sbin/reboot
  4. After you have restarted the system, log in to the system and switch to the root user.

View and Change Kernel Parameter Values on Solaris 10

To view the current values of the resource control, enter the following commands:
#id -p //to verify the project ID
uid = 0 (Root) gid = 0 (Root) projid = 1 (user.root)
#prctl -n project.max-shm-memory -i project user.root
#prctl -n project.max=sem-ids -i project user.root
To change any of the current values, follow these steps:
  1. To modify the value of max-shm-memory to 6GB:
    #prctl -n project.max-shm-memory -v 6gb -r -i project user.root
  2. To modify the value of max-sem-ids to 256:
    #prctl -n project.max-sem-ids -v 256 -r -i project user.root

Kernel Parameter Requirements on HP-UX

Verify that the kernel parameters listed in Table D-4 are set to the values greater than or equal to the recommended value shown. The procedure following Table D-4 describes how to verify and set the values.
Table D-4 Recommended Kernel Parameter Values for HP-UX
Parameter Recommended Value
ksi_alloc_max
32768
max_thread_proc
256
maxdsiz
1073741824
maxdsiz_64bit
2147483648
maxssiz
134217728
maxssiz_64bit
1073741824
maxswapchunks
16384
maxuprc
3687
msgmap
4098
msgmni
4096
msgseg
32767
msgtql
4096
ncsize
34816
nfile
63488
nflocks
4096
ninode
34816
nkthread
7184
nproc
4096
semmap
4098
semmni
4096
semmns
8192
semmnu
4092
semvmx
32767
shmmax
1073741824
shmmni
512
shmseg
120
vps_ceiling
64
Note:
The following parameters are obsolete in HP-UX 11.23:
  • maxswapchunks
  • semmap
If the current value of any parameter is higher than the value listed in this table, do not change the value for that parameter.

View and Change Kernel Parameter Values

To view the current value of these kernel parameters, and to change them, if necessary, follow these steps:
  1. Set the DISPLAY environment variable to specify the display of the local system. This is an optional step.
    Bourne, Bash or Korn shell:
    $ DISPLAY=localhost:0.0; export DISPLAY
    C Shell
    $ setenv DISPLAY localhost:0.0
  2. Start System Administration Manager (SAM)
    # /usr/sbin/sam
  3. Choose the Kernel Configuration area and the Configurable Parameters area.
  4. Check the value or formula specified for each of these parameters and if necessary, modify that value or formula. Refer to the SAM Online Help for more details.
  5. Exit from SAM.
  6. If you have modified the value for any of the parameters, you must restart your system.
    # /sbin/shutdown -r now
  7. After you have restarted the system, log in and switch to the root user if necessary.

Kernel Parameter Requirements on HP-UX Itanium

Verify that the kernel parameters listed in Table D-5 are set to the values greater than or equal to the recommended value shown.
Table D-5 Recommended Kernel Parameter Values on HP-UX Itanium
Parameter Recommended Value
ksi_alloc_max
32768
max_thread_proc
256
maxdsiz
1073741824
maxdsiz_64bit
2147483648
maxssiz
134217728
maxssiz_64bit
1073741824
maxuprc
3687
msgmni
4096
msgseg
32767
msgtql
4096
ncsize
34816
nfile
63488
nflocks
4096
ninode
34816
nkthread
7184
nproc
4096
semmni
4096
semmns
8192
semmnu
4092
semvmx
32767
shmmax
1073741824
shmmni
512
shmseg
120
vps_ceiling
64

Configure Shell Limits and System Configuration Parameters on AIX

On AIX systems, you do not need to configure the kernel parameters. However, Oracle recommends that you set shell limits and system configuration parameters as described in this section.

Configuring Shell Limits

Verify that the shell limits shown in Table D-6 are set to the values shown. The procedure following the table describes how to verify and set the values.
Table D-6 Shell Limits
Shell Limit (as shown in smit) Recommended Value
Soft FILE size
-1 (Unlimited)
Soft CPU size
-1 (Unlimited)
Soft DATA segment
-1 (Unlimited)
Soft STACK size
-1 (Unlimited)
Do the following to view and change the values that are currently specified for these shell limits:
  1. Execute the following command:
    # smit chuser
  2. In the User Name field, specify the user name of the Oracle software owner, for example oracle.
  3. Scroll down the list and verify whether the value for the soft limits is -1. If not, edit the existing value as recommended in Table D-6.
  4. When you have finished making changes, press F10 to exit.

Specifying System Configuration Parameters

Ensure the maximum number of processes allowed per user is set to 2048 or higher. The following procedure describes how to verify and set the value.
To specify the system configuration parameters:
  1. Execute the following command:
    # smit chgsys
  2. Ensure the value shown for Maximum Number of Processes allowed per user is greater than or equal to 2048. If not, edit the existing value.
  3. When you have finished making changes, press F10 to exit.
Related Posts with Thumbnails