PL SQL Developer v6.0.5 serial key or number

Note:

For more information about silent-mode installations, refer to Appendix A.

2.2.1 Memory Requirements

The following are the memory requirements for installing Oracle Database 11g Release 1:

• At least 1 GB of RAM

  To determine the RAM size, enter the following command:

  # grep MemTotal /proc/meminfo

  If the size of the RAM is less than the required size, then you must install more memory before continuing.

• The following table describes the relationship between installed RAM and the configured swap space requirement:

  Note:

  On Linux, the Hugepages feature allocates non-swappable memory for large page tables using memory-mapped files. If you enable Hugepages, then you should deduct the memory allocated to Hugepages from the available RAM before calculating swap space.

  RAM	Swap Space
  Between 1 GB and 2 GB	1.5 times the size of RAM
  Between 2 GB and 16 GB	Equal to the size of RAM
  More than 16 GB	16 GB

  
  

  To determine the size of the configured swap space, enter the following command:

  # grep SwapTotal /proc/meminfo

  If necessary, refer to the operating system documentation for information about how to configure additional swap space.

To determine the available RAM and swap space, enter the following command:

Automatic Memory Management

Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (and file descriptors. The size of the shared memory should be at least the greater of and for each Oracle instance on the computer. If or is set to a non zero value, and an incorrect size is assigned to the shared memory, it will result in an error at startup. The number of file descriptors for each Oracle instance should be at least . Also, the limit of descriptors for each process should be at least 512. If file descriptors are not sized correctly, you will notice from various Oracle processes and potentially errors in non-Oracle processes.

To determine the amount of shared memory available, enter the following command:

On the Initialization Parameters page, note that Memory Size (SGA and PGA), which sets the initialization parameter or . Note that the initialization parameters cannot be greater than the shared memory file system on the operating system. For example, if the shared memory file system allocation on your system is 1 GB, but you set Memory Size () to 2 GB, then the following error messages are displayed during database startup:

In addition, if you click All Initialization Parameters and the global database name is longer than 8 characters, then the database name value (in the parameter) is truncated to the first eight characters, and the parameter value is set to the global name.

2.2.2 System Architecture

To determine whether the system architecture can run the software, enter the following command:

This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you want to install. If you do not see the expected output, then you cannot install the software on this system.

2.2.3 Disk Space Requirements

The following are the disk space requirements for installing Oracle Database 11g Release 1:

• Between 150 and 200 MB of disk space in the directory

  To determine the amount of disk space available in the directory, enter the following command:

  # df -k /tmp

  If there is less than 400 MB of free disk space available in the directory, then complete one of the following steps:

  • Delete unnecessary files from the directory to meet the disk space requirement.

  • Set the and environment variables when setting the user's environment (described later).

  • Extend the file system that contains the directory. If necessary, contact the system administrator for information about extending file systems.

• To determine the amount of free disk space on the system, enter the following command:

  # df -k

• The following table describes the disk space requirements for software files for each installation type on Linux 86:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	3.47
  Standard Edition	3.22
  Custom (maximum)	3.45

  
  

  Between 3.5 GB and 5 GB of disk space for the Oracle software, depending on the installation type

• The following table describes the disk space requirements for each installation type on Linux x86-64:

  Installation Type	Requirement for Software Files (GB)
  Enterprise Edition	4.35
  Standard Edition	3.73
  Custom (maximum)	4.54

  
  

  Between 3.5 GB and 5 GB of disk space for the Oracle software, depending on the installation type

• The following table describes the disk space requirements for each installation type on Linux x86:

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	1.6
  Standard Edition	1.6
  Custom (maximum)	1.81

  
  

• The following table describes the disk space requirements for each installation type on Linux x86-64:

  Installation Type	Disk Space for Data Files (GB)
  Enterprise Edition	1.68
  Standard Edition	1.48
  Custom (maximum)	2.14

  
  

  Additional disk space, either on a file system or on an Automatic Storage Management disk group is required for the flash recovery area if you choose to configure automated backups.

2.2.4 Recommended Hardware Requirement for SQL Developer

The following table lists the recommended Memory and Display requirements for SQL Developer.

Note:

• This guide contains information required to install Oracle Database 11g Release 1 (11.1) on various platforms of Linux. Ensure that you review information related to the platform on which you intend to install Oracle Database 11g.

• Oracle Universal Installer performs checks on the system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.

2.3.1 Operating System Requirements

The following are the operating system requirements for Oracle Database 11g Release 1:

On Linux x86 and Linux x86-64:

• Asianux 2 SP2

• Asianux 3

• Oracle Linux 4

• Oracle Linux 5

• Red Hat Enterprise Linux 4

• Red Hat Enterprise Linux 5

• SUSE Linux Enterprise Server 10

To determine the distribution and version of Linux installed, enter the following command:

2.3.2 Kernel Requirements

The following are the Kernel requirements for Oracle Database 11g Release 1:

• On Asianux 2, Oracle Linux 4, and Red Hat Enterprise Linux 4:

  2.6.9 or later

• On Asianux 3, Oracle Linux 5, and Red Hat Enterprise Linux 5:

  2.6.18 or later

• On SUSE Linux Enterprise Server 10:

  2.6.16.21 or later

To determine whether the required kernel is installed, enter the following command:

The following is a sample output displayed by running this command on a Red Hat Enterprise Linux 4.0 system:

In this example, the output shows the kernel version () and errata level () on the system.

If the kernel version does not meet the requirement, then contact the operating system vendor for information about obtaining and installing kernel updates.

2.3.3 Package Requirements

The following are the list of packages required for Oracle Database 11g Release 1.

On Linux x86:

On Linux x86-64:

To determine whether the required packages are installed, enter commands similar to the following:

If a package is not installed, then install it from the Linux distribution media or download the required package version from the Linux vendor's Web site.

2.3.4 Compiler Requirements

Intel C++ Compiler 9.1 or later and the version of GNU C and C++ compilers listed under "Package Requirements" are supported with Pro*C/C++, Oracle Call Interface, Oracle C++ Call Interface, and Oracle XML Developer's Kit (XDK) for Oracle Database 11g Release 1.

Starting with Oracle Database 11g release 1 (11.1.0.7), Pro*COBOL is certified on Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 10.0, and XEN with Micro Focus Server Express 5.0 WP4.

2.3.5 Additional Software Requirements

Depending on the components you want to use, you must ensure that the following software are installed:

2.5.1 Configuring Name Resolution

When you run Oracle Universal Installer, an error may occur if name resolution is not set up. To avoid this error, before you begin installation, you must ensure that host names are resolved through the file.

To ensure that host names are resolved only through the file:

1. Verify that the file is used for name resolution. You can do this by checking the hosts file entry in the file as follows:

   # cat /etc/nsswitch.conf | grep hosts

   The output of this command should contain an entry for files.

2. Verify that the host name has been set by using the command as follows:

   # hostname

   The output of this command should be similar to the following:

   myhost.example.com

3. Verify that the domain name has not been set dynamically by using the command as follows:

   # domainname

   This command should not return any results.

4. Verify that the file contains the fully qualified host name by using the following command:

   # cat /etc/hosts

   The output of this command should contain an entry for the fully qualified host name and localhost.

   For example:

   127.0.0.1 localhost.localdomain localhost 192.168.100.16 myhost.us.example.com myhost

   If the file does not contain the fully qualified host name, then open the file and make the required changes in it.

2.5.2 Installing on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing enables a computer to have a different IP address each time it connects to the network. In some cases, the IP address can change while the computer is still connected. You can have a mixture of static and dynamic IP addressing in a DHCP system.

In a DHCP setup, the software tracks IP addresses, which simplifies network administration. This lets you add a new computer to the network without having to manually assign that computer a unique IP address.

2.5.3 Installing on Multihomed Computers

You can install Oracle Database on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name. In addition, you can set up aliases for the host name. By default, Oracle Universal Installer uses the environment variable setting to find the host name. If is not set and you are installing on a computer that has multiple network cards, then Oracle Universal Installer determines the host name by using the first entry in the file.

Clients must be able to access the computer either by using this host name or by using aliases for this host name. To verify this, ping the host name from the client computers using the short name (host name only) and the full name (host name and domain name). Both tests must be successful.

Setting the ORACLE_HOSTNAME Environment Variable

Use the following procedure to set the environment variable. For example, if the fully qualified host name is , then enter one of the following commands:

In Bourne, Bash, or Korn shell:

In C shell:

2.5.4 Installing on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP but with multiple aliases. The naming service resolves any of those aliases to the same computer. Before installing Oracle Database on such a computer, set the environment variable to the computer whose host name you want to use.

2.5.5 Installing on Non-Networked Computers

You can install Oracle Database on a non-networked computer. If the computer, such as a laptop, is configured for DHCP and you plan to connect the computer to the network after the Oracle Database installation, then use the command on the computer on which you want to install the database to check if the computer can connect to itself. Perform this step by first using only the host name and then using the fully qualified name, which should be in the file.

If the command fails, then contact the network administrator.

Connecting the Computer to the Network after Installation

If you connect the computer to a network after installation, then the Oracle Database instance on the computer can work with other instances on the network. The computer can use a static IP or DHCP, depending on the network to which you are connected.

Note:

2.6.1 Creating the Oracle Inventory Group

Log in as , and use the following instructions to locate or create the Oracle Inventory group and a software owner:

Determining Whether the Oracle Inventory Group Exists

When you install Oracle software on the system for the first time, Oracle Universal Installer creates the file. This file identifies the name of the Oracle Inventory group (typically, ), and the path of the Oracle Inventory directory. An file has contents similar to the following:

In the preceding example, central_inventory_location is the location of the Oracle Central Inventory, and group is the name of the group that has permissions to write to the central inventory.

If you have an existing Oracle Inventory, then ensure that you use the same Oracle Inventory for all Oracle software installations, and ensure that all Oracle software users you intend to use for installation have permissions to write to this directory.

To determine whether the Oracle Inventory group exists, enter the following command:

If the file exists, then the output from this command is similar to the following:

In the previous output example:

• The group shows the location of the Oracle Inventory

• The parameter shows the name of the Oracle Inventory group (in this example, ).

Creating the Oracle Inventory Group

If the file does not exist, then create the Oracle Inventory group by entering the following command:

2.6.2 Creating the OSDBA Group

You must create an OSDBA group in the following circumstances:

• An OSDBA group does not exist, for example, if this is the first installation of Oracle Database software on the system

• An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges in a new Oracle installation

To determine whether the group exists, enter the following command:

If the group does not exist or if you require a new group, then create it as follows. In the following command, use the group name unless a group with that name already exists.

2.6.3 Creating an OSOPER Group (Optional)

Create an OSOPER group only if you want to identify a group of operating system users with a limited set of database administrative privileges ( operator privileges). For most installations, it is sufficient to create only the group. If you want to use an OSOPER group, then you must create it in the following circumstances:

• If an OSOPER group does not exist, for example, if this is the first installation of Oracle Database software on the system

• If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation

If you require a new OSOPER group, then create it as follows. In the following command, use the group name unless a group with that name already exists.

2.6.4 Creating an OSASM Group

Create an OSASM group only if you want as a system privilege that enables the separation of the database administration privilege from the Automatic Storage Management storage administration privilege. If you want to use an OSASM group, then you must create it in the following circumstances:

• If an OSASM group does not exist, for example, if this is the first installation of Oracle Database software on the system

• If an OSASM group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation

To determine whether the OSASM group exists, enter the following command:

If the OSASM group does not exist or if you require a new OSASM group, then create it as follows. In the following command, use the group name unless a group with that name already exists.

2.6.5 Creating the Oracle Software Owner User

You must create an Oracle software owner user in the following circumstances:

• If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system

• If an Oracle software owner user exists, but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation

Note:

Note:

2.9.1 Oracle Base Directory

The Oracle base directory is a top-level directory for Oracle software installations. On Linux systems, the Optimal Flexible Architecture (OFA) guidelines recommend that you use a path similar to the following for the Oracle base directory:

In this example:

• is the mount point directory for the file system that will contain the Oracle software.

  The examples in this guide use for the mount point directory. However, you can choose another mount point directory, such as or .

• is the operating system user name of the Oracle software owner, for example .

You need to specify the Oracle base folder that contains all Oracle products.

You can use the same Oracle base directory for more than one installation or you can create separate Oracle base directories for different installations. If different operating system users install Oracle software on the same system, then each user must create a separate Oracle base directory. The following are the example of Oracle base directories that can exist on the same system:

2.9.2 Oracle Inventory Directory

The Oracle Inventory directory () stores an inventory of all software installed on the system. It is required and shared by all Oracle software installations on a single system. If you have an existing Oracle Inventory path, then Oracle Universal Installer continues to use that Oracle Inventory.

The first time you install Oracle software on a system, Oracle Universal Installer checks if you have created an OFA-compliant directory structure with the format , such as , and that the user running the installation has permissions to write to that path. If this is true, then Oracle Universal Installer creates the Oracle Inventory directory similar to . For example:

If you have set the environment variable for the user, then Oracle Universal Installer creates the Oracle Inventory directory similar to . For example, if is set to , then the Oracle Inventory directory is created similar to .

If you have neither created an OFA-compliant path nor set , then the Oracle Inventory directory is placed in the home directory of the user that is performing the installation. For example:

Oracle Universal Installer creates the directory that you specify and sets the correct owner, group, and permissions for it. You do not need to create it.

2.9.3 Oracle Home Directory

The Oracle home directory is the directory where you choose to install the software for a particular Oracle product. You must install different Oracle products or different releases of the same Oracle product in separate Oracle home directories. When you run Oracle Universal Installer, it prompts you to specify the path to this directory and a name that identifies it. The directory that you specify must be a subdirectory of the Oracle base directory. Oracle recommends that you specify a path similar to the following for the Oracle home directory:

Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct owner, group, and permissions on it. You do not need to create this directory.

Note:

2.10.1 Identifying an Existing Oracle Base Directory

Existing Oracle base directories may not have paths that comply with OFA (Optimal Flexible Architecture) guidelines. However, if you identify an existing Oracle Inventory directory or existing Oracle home directories, then you can usually identify the Oracle base directories, as follows:

• Identifying an existing Oracle Inventory directory. Refer to Creating the Oracle Inventory Group for more information.

  Note:

  Oracle recommends that you do not put the directory under Oracle base for a new installation. However, if you have an existing installation, then you should follow the steps suggested in this section.

• Identifying an existing Oracle home directory

  Enter the following command to display the contents of the file:

  # more /etc/oratab

  If the file exists, then it contains lines similar to the following:

  *:/u03/app/oracle/product/11.1.0/db_1:N *:/opt/orauser/infra_904:N *:/oracle/9.2.0:N

  The directory paths specified on each line identify Oracle home directories. Directory paths that end with the user name of the Oracle software owner that you want to use are valid choices for an Oracle base directory. If you intend to use the user to install the software, then you can choose one of the following directories listed in the previous example:

  /u03/app/oracle /oracle

  Note:

  If possible, choose a directory path similar to the first one (). This path complies with the OFA guidelines.

• Identifying an existing Oracle base directory

  After you have located the Oracle home directory, you can run the following command to confirm the location of Oracle base:

  cat inventory/ContentsXML/oraclehomeproperties.xml

Before deciding to use an existing Oracle base directory for this installation, ensure that it satisfies the following conditions:

• It should not be on the same file system as the operating system.

• It must have sufficient free disk space, as follows:

  Requirement	Free Disk Space
  The Oracle base directory will contain only software files.	Up to 3 GB
  The Oracle base directory will contain both software and database files (not recommended for production databases).	Up to 5.4 GB

  
  

  To determine the free disk space on the file system where the Oracle base directory is located, enter the following command:

  # df -k oracle_base_path

To continue:

• If an Oracle base directory exists and you want to use it, then refer to the "Choosing a Storage Option for Oracle Database and Recovery Files" section.

  When you configure the user's environment later in this chapter, set the environment variable to specify the directory you chose.

• If an Oracle base directory does not exist on the system or if you want to create an Oracle base directory, then refer to the following section.

2.10.2 Creating an Oracle Base Directory

Before you create an Oracle base directory, you must identify an appropriate file system with sufficient free disk space.

To identify an appropriate file system:

1. To determine the free disk space on each mounted file system use the following command:

   # df -k

2. From the display, identify a file system that has appropriate free space.

   The file system that you identify can be a local file system, a cluster file system, or an NFS file system on a certified NAS device.

3. Note the name of the mount point directory for the file system that you identified.

To create the Oracle base directory and specify the correct owner, group, and permissions for it:

1. Enter commands similar to the following to create the recommended subdirectories in the mount point directory that you identified and set the appropriate owner, group, and permissions on them:

   # mkdir -p /mount_point/app # chown -R oracle:oinstall /mount_point/app # chmod -R 775 /mount_point/app/

   For example:

   # mkdir -p /u01/app # chown -R oracle:oinstall /u01/app # chmod -R 775 /u01/app/

2. When you configure the user's environment later in this chapter, set the environment variable to specify the Oracle base directory that you have created.

Note:

2.12.1 Guidelines for Placing Oracle Database Files on a File System

If you choose to place the Oracle Database files on a file system, then use the following guidelines when deciding where to place them:

• The default path suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory.

• You can choose either a single file system or more than one file system to store the database files:

  • If you want to use a single file system, then choose a file system on a physical device that is dedicated to the database.

    For best performance and reliability, choose a RAID device or a logical volume on more than one physical device and implement the stripe-and-mirror-everything (SAME) methodology.

  • If you want to use more than one file system, then choose file systems on separate physical devices that are dedicated to the database.

    This method enables you to distribute physical input-output operations and create separate control files on different devices for increased reliability. It also enables you to fully implement the OFA guidelines described in Appendix D, "Optimal Flexible Architecture". You must choose either the Advanced database creation option or the Custom installation type during the installation to implement this method.

• If you intend to create a preconfigured database during the installation, then the file system (or file systems) that you choose must have at least 1.5 GB of free disk space.

  For production databases, you must estimate the disk space requirement depending on the use that you want to make of the database.

• For optimum performance, the file systems that you choose should be on physical devices that are used only by the database.

• The user must have write permissions to create the files in the path that you specify.

2.12.2 Creating Required Directories

To create directories for the Oracle database, or recovery files on separate file systems to the Oracle base directory:

1. Use the following to determine the free disk space on each mounted file system:

   # df -k

2. From the display, identify the file systems that you want to use:

   File Type	File System Requirements
   Database files	Choose either: A single file system with at least 1.5 GB of free disk space Two or more file systems with at least 1.5 GB of free disk space in total
   Recovery files	Choose a file system with at least 2.4 GB of free disk space

   
   

   If you are using the same file system for more than one type of file, then add the disk space requirements for each type to determine the total disk space requirement.

3. Note the names of the mount point directories for the file systems that you identified.

4. Enter commands similar to the following to create the recommended subdirectories in each of the mount point directories and set the appropriate owner, group, and permissions on them:

   • Database file directory:

     # mkdir /mount_point/oradata # chown oracle:oinstall /mount_point/oradata # chmod 775 /mount_point/oradata

     The default location for Database file directory is .

   • Recovery file directory (flash recovery area):

     # mkdir /mount_point/flash_recovery_area # chown oracle:oinstall /mount_point/flash_recovery_area # chmod 775 /mount_point/flash_recovery_area

     The default flash recovery area is . However, Oracle recommends that you keep the flash recovery area on a separate physical disk than that of the database file directory. This will enable you use the flash recovery area to retrieve data if the disk containing is unusable due to any reasons.

5. If you also want to use Automatic Storage Management for storage, then refer to the following section:

   "Preparing Disk Groups for an Automatic Storage Management Installation"

   Otherwise, refer to the "Stopping Existing Oracle Processes" section.