Skip Headers
Oracle® Database Installation Guide
11g Release 2 (11.2) for Microsoft Windows

Part Number E10843-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Oracle Database Preinstallation Requirements

This chapter describes the tasks that you must complete before you start Oracle Universal Installer. It includes information about the following tasks:

2.1 Oracle Database Hardware Requirements

This section describes hardware component and hard disk space requirements.

2.1.1 Hardware Component Requirements for Windows 32-Bit

The following table lists the hardware components that are required for Oracle Database on Windows 32-bit.

Table 2-1 Windows 32-Bit Hardware Requirements

Requirement Value

Physical memory (RAM)

1 GB minimum

Virtual memory

Double the amount of RAM

Disk space

Typical Installation Type total: 5.15 GB

Advanced Install Types total: 5.15 GB

See Table 2-3 for details.

Processor Type

Intel-compatible processor

Video adapter

256 colors

Screen Resolution

1024 X 768 minimum


2.1.2 Hardware Component Requirements for Windows x64

The following table lists the hardware components that are required for Oracle Database on Windows x64.

Table 2-2 Windows x64 Hardware Requirements

Requirement Value

Physical memory (RAM)

1 GB minimum

On Windows 7, 2 GB minimum

Virtual memory

Double the amount of RAM

Disk space

Total: 5.1 GB

See Table 2-3 for details.

Processor Type

AMD64, or Intel Extended memory (EM64T)

Video adapter

256 colors

Screen Resolution

1024 X 768 minimum


2.1.3 Hard Disk Space Requirements

This section lists system requirements for Windows platforms that use the NT File System (NTFS). Oracle strongly recommends that you install the Oracle database home (Oracle database binaries, trace files, and so on) on Oracle ACFS or NTFS; the database files themselves must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS instead of FAT32 is recommended to ensure security of these files.

The NTFS system requirements listed in this section are more accurate than the hard disk values reported by the Oracle Universal Installer Summary window. The Summary window does not include accurate values for disk space, the space required to create a database, or the size of compressed files that are expanded on the hard drive.

The hard disk requirements for Oracle Database components include 32 MB to install Java Runtime Environment (JRE) and Oracle Universal Installer on the partition where the operating system is installed. If sufficient space is not detected, installation fails and an error message appears.

Table 2-3 lists the disk space requirements on NTFS for Windows 32-bit.

Table 2-4 lists the disk space requirements on NTFS for Windows x64. The starter database requires 720 MB of disk space.

The figures in these tables include the starter database. FAT32 space requirements are slightly higher.

Table 2-3 Windows 32-Bit Disk Space Requirements on NTFS

Installation Type TEMP Space SYSTEM_DRIVE:\ Program Files\Oracle Oracle Home Data Files * Total

Typical Installation

500 MB

3.1 MB

2.8 GB

1.86 GB

5.15 GB

Advanced Install: All Editions

500 MB

4.86 MB

3.35 GB **

1.86 GB **

8.70 GB **


Table 2-4 Windows x64 Disk Space Requirements on NTFS

Installation Type TEMP Space SYSTEM_DRIVE:\ Program Files\Oracle Oracle Home Data Files * Total

Typical Installation

125 MB

2 MB

2.86 GB

1.60 GB

5.1 GB

Advanced Install: All Editions

125 MB

4.55 MB

3.5 GB **

1.6 GB **

5.22 GB **


* Refers to the contents of the admin, cfgtoollogs, flash_recovery_area, and oradata directories in the ORACLE_BASE directory.

** This size can be higher depending on the installation options selected, such as languages or additional components. If you choose to install Oracle Database with automated backups enabled, include at least 2 GB extra for data file disk space.

See Also:

"NTFS File System and Windows Registry Permissions" in Oracle Database Platform Guide for Microsoft Windows

2.1.4 Verifying Hardware Requirements

To ensure that the system meets these requirements, follow these steps:

  1. Determine the physical RAM size. For example, on a Windows Server 2003 computer, double-click System in the Windows Control Panel and click the General tab.

    On a Windows Server 2008 R2 computer, click System and Security in the Windows Control Panel, then click System.

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

  2. Determine the size of the configured virtual memory (also known as paging file size). For example, on a Windows 2003 computer, double-click System, click the Advanced tab, and click Settings in the Performance section. Then click the Advanced tab.

    On a Windows Server 2008 R2 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Settings in the Performance section. Then select the Advanced tab on Performance Options page.

    The virtual memory is listed in the Virtual Memory section.

    If necessary, see your operating system documentation for information about how to configure additional virtual memory.

  3. Determine the amount of free disk space on the system. For example, on a Windows 2003 computer, double-click My Computer, right-click the drive where the Oracle software is to be installed, and select Properties.

    On a Windows Server 2008 R2 computer, right-click My Computer and click Open.

  4. Determine the amount of disk space available in the temp directory. This is equivalent to the total amount of free disk space, minus what is required for the Oracle software to be installed.

    On Windows 32-bit, if there is less than 500 MB of disk space available in the temp directory, then delete all unnecessary files. If the temp disk space is still less than 500 MB, then set the TEMP or TMP environment variable to point to a different hard drive location.

    On Windows x64, if there is less than 125 MB of disk space available in the temp directory, then delete all unnecessary files. If the temp disk space is still less than 125 MB, then set the TEMP or TMP environment variable to point to a different hard drive location.

    For example, to change the environment variables on a Windows Server 2003 computer, double-click System, click the Advanced tab, and click Environment Variables.

    On a Windows Server 2008 R2 computer, click System and Security, then click System, click Advanced System Settings, click the Advanced tab on System Properties page, and then click Environment Variables.

2.2 Oracle Database Software Requirements

Table 2-5 lists the software requirements for Oracle Database on Windows 32-bit.

Table 2-6 lists the software requirements for Oracle Database on Windows x64.

Table 2-5 Windows 32-Bit Software Requirements

Requirement Value

System Architecture

Processor: Intel (x86), AMD64, and Intel EM64T

Note: Oracle provides 32-bit (Windows x86) and 64-bit (Windows x64) versions of Oracle Database for Microsoft Windows.

Operating System

Oracle Database for 32-bit Windows is supported on the following operating systems:

  • Windows Server 2003 - all editions

  • Windows Server 2003 R2 - all editions

  • Windows XP Professional

  • Windows Vista - Business, Enterprise, and Ultimate editions

  • Windows Server 2008 - Standard, Enterprise, Datacenter, Web, and Foundation editions. The Server Core option is not supported.

    Note: Check My Oracle Support (formerly OracleMetaLink) for more information about Hyper-V support.

  • Windows 7 - Professional, Enterprise, and Ultimate editions

Windows Multilingual User Interface Pack is supported.

See Also: "Hardware and Software Certification" for information about how to access the latest system requirements

Compiler

Pro*Cobol has been tested and certified with Net Express 5.0.

Object Oriented COBOL (OOCOBOL) specifications are not supported.

The following components are supported with the Microsoft Visual C++ .NET 2005 8.0, Microsoft Visual C++ .NET 2008 9.0, and Intel 10.1 C compilers:

  • Oracle Call Interface

  • External callouts

  • Pro*C/C++

  • XDK

Oracle C++ Call Interface is supported with

  • Microsoft Visual C++ .NET 2005 8.0

  • Microsoft Visual C++ .NET 2008 9.0 - OCCI libraries are installed under ORACLE_HOME\oci\lib\msvc\vc9. When developing OCCI applications with MSVC++ 9.0, ensure that the OCCI libraries are correctly selected from this directory for linking and executing.

  • Intel 10.1 C++ compiler with the relevant Microsoft Visual C++ .NET STLs.

Network Protocol

The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:

  • TCP/IP

  • TCP/IP with SSL

  • Named Pipes

Oracle Database Client

If you plan to connect to Oracle Database 11g Release 2 (11.2) from a release of Oracle Database Client that is earlier than 11g Release 2 (11.2), the following conditions apply:

  • Oracle Database Client is version 9.2.0.4 or higher. See Note 207303.1 on My Oracle Support (formerly OracleMetaLink) for more details and up to date information.

  • If the earlier Oracle Database Client is running on the same computer as Oracle Database 11g Release 2 (11.2), a bequeath connection cannot be used.

Oracle recommends upgrading Oracle Database Client to the latest patchset (9.2.0.8, 10.2.0.4, or later). You can download the patchset from the Patches and Updates section of My Oracle Support (formerly OracleMetaLink) at

https://support.oracle.com

Table 2-6 Windows x64 Software Requirements

Requirement Value

System Architecture

Processor: AMD64, and Intel EM64T

Note: Oracle provides limited certification for 32-bit Oracle Database Client on 64-bit Windows x64. For additional information, visit My Oracle Support (formerly OracleMetaLink) at

https://support.oracle.com/

Operating System

Oracle Database for Windows x64 is supported on the following operating systems:

  • Windows Server 2003 - all x64 editions

  • Windows Server 2003 R2 - all x64 editions

  • Windows XP Professional x64 Edition

  • Windows Vista x64 - Business, Enterprise, and Ultimate editions

  • Windows Server 2008 x64 and Windows Server 2008 R2 x64 - Standard, Enterprise, Datacenter, Web, and Foundation editions. The Server Core option is not supported.

    Note: Check My Oracle Support (formerly OracleMetaLink) for more information about Hyper-V support.

  • Windows 7 x64 - Professional, Enterprise, and Ultimate editions

Windows Multilingual User Interface Pack is supported.

See Also: "Hardware and Software Certification" for information about how to access the latest system requirements

Compiler

Pro*Cobol has been tested and certified with Net Express 5.0.

Object Oriented COBOL (OOCOBOL) specifications are not supported.

The following components are supported with the Microsoft Visual C++ .NET 2005 8.0, Microsoft Visual C++ .NET 2008 9.0, and Intel 10.1 C compilers:

  • Oracle Call Interface

  • External callouts

  • Pro*C/C++

  • XDK

Oracle C++ Call Interface is supported with

  • Microsoft Visual C++ .NET 2005 8.0

  • Microsoft Visual C++ .NET 2008 9.0 - OCCI libraries are installed under ORACLE_HOME\oci\lib\msvc\vc9. When developing OCCI applications with MSVC++ 9.0, ensure that the OCCI libraries are correctly selected from this directory for linking and executing.

  • Intel 10.1 C++ compiler with the relevant Microsoft Visual C++ .NET STLs.

Network Protocol

The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:

  • TCP/IP

  • TCP/IP with SSL

  • Named Pipes

Oracle Database Client

If you plan to connect to Oracle Database 11g Release 2 (11.2) from a release of Oracle Database Client that is earlier than 11g Release 2 (11.2), the following conditions apply:

  • Oracle Database Client is version 9.2.0.4 or higher. See Note 207303.1 on My Oracle Support (formerly OracleMetaLink) for more details and up to date information.

  • If the earlier Oracle Database Client is running on the same computer as Oracle Database 11g Release 2 (11.2), a bequeath connection cannot be used.

Oracle recommends upgrading Oracle Database Client to the latest patchset (9.2.0.8, or 10.2.0.4 or later). You can download the patchset from the Patches and Updates section of My Oracle Support (formerly OracleMetaLink) at

https://support.oracle.com

2.3 Windows Certification and Web Browser Support

The following sections provide certification information:

2.3.1 Windows Terminal Services and Remote Desktop Support

Oracle supports installing, configuring, and running Oracle Database through Terminal Services on Windows. To install Oracle Database, Oracle recommends that you start all configuration tools from the Terminal Server console session of the server (using mstsc/console).

Platform-specific support information is as follows:

  • Windows 2003 and Windows Server 2003 R2: You can configure Windows 2003 and Windows Server 2003 R2 to use Terminal Services in Remote Desktop for Administration Mode or Terminal Server Mode.

  • Windows XP, Windows Vista, and Windows 7: The Remote Desktop is only available in Single User Mode.

  • Windows Server 2008 and Windows Server 2008 R2: You can have multiple Remote Desktop sessions.

See Also:

2.3.2 Oracle Services for Microsoft Transaction Server

Oracle Services for Microsoft Transaction Server running on Windows Vista requires a minimum of Service Pack 1 or higher.

2.3.3 Unsupported Components on 32-Bit Windows Client Operating Systems

All Oracle Database components are supported on Windows XP, Windows Vista, and Windows 7 with the following exceptions:

  • DCE Adapter Support

  • Entrust Authority

  • Oracle RAC, including Oracle Cluster File System and Server Management

    It is not supported on any 32-bit Windows (server or client) operating system.

  • Oracle Grid Infrastructure

  • Thales is not supported on Windows XP and Windows 7.

    The Hardware Security Modules are from the nCipher product line.

  • SafeNet

  • Oracle Fail Safe Server

  • Oracle Messaging Gateway

2.3.4 Unsupported Components on Windows x64

All Oracle Database components are supported on Windows x64 with the following exceptions:

  • DCE Adapter

  • Oracle Fail Safe Server

  • Business Components for Java (BC4J)

  • CyberSafe Adapter Support

  • Entrust Authority

  • Java Server Pages

  • Thales is not supported on Windows XP and Windows 7.

    The Hardware Security Modules are from the nCipher product line.

  • SafeNet

  • Oracle Objects for OLE

  • Oracle Messaging Gateway is not supported on Windows XP, Windows Vista, and Windows 7

  • Oracle RAC (including Oracle Cluster File System and Server Management) and Oracle Grid Infrastructure

    These are not supported on Windows XP, Windows Vista, and Windows 7.

  • Oracle Warehouse Builder Design Center Client

2.3.5 Web Browser Support

The following Web browsers are supported for Oracle Enterprise Manager Database Control:

  • Microsoft Internet Explorer 6.0 SP2

  • Microsoft Internet Explorer 7.0

  • Microsoft Internet Exlorer 7.0 SP1

  • Microsoft Internet Explorer 8.0

  • Netscape 8.1

  • Netscape 9.0

  • Firefox 2.0

  • Firefox 3.0.7

  • Safari 3.0.4

  • Safari 3.1

  • Safari 3.2

2.4 Oracle Database Network Topics

Typically, the computer on which you want to install Oracle Database is connected to the network, has local storage to contain the Oracle Database installation, has a display monitor, and has a media drive.

This section describes how to install Oracle Database on computers that do not meet the typical scenario. It covers the following topics:

2.4.1 Installing Oracle Database on DHCP Computers

Dynamic Host Configuration Protocol (DHCP) assigns dynamic IP addresses on a network. Dynamic addressing allows 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. However, before installing Oracle Database onto a computer that uses the DHCP protocol, you must install a loopback adapter to assign a local IP address to that computer.

2.4.2 Installing Oracle Database on Computers with Multiple IP Addresses

You can install Oracle Database on a computer that has multiple IP addresses, also known as a multihomed computer. Typically, a multihomed computer has multiple network cards. Each IP address is associated with a host name; additionally, you can set up aliases for the host name. By default, Oracle Universal Installer uses the ORACLE_HOSTNAME environment variable setting to find the host name.

Clients must be able to access the computer using this host name, or using aliases for this host name. To check, 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 must work.

Setting the ORACLE_HOSTNAME Environment Variable

To set the ORACLE_HOSTNAME environment variable:

  1. Display System in the Windows Control Panel.

  2. In the System Properties dialog box, click Advanced.

  3. In the Advanced tab, click Environment Variables.

  4. In the Environment Variables dialog box, under System Variables, click New.

  5. In the New System Variable dialog box, enter the following information:

    • Variable name: ORACLE_HOSTNAME

    • Variable value: The host name of the computer to use.

  6. Click OK, then in the Environment Variables dialog box, click OK.

  7. Click OK in the Environment Variables dialog box, then in the System Properties dialog box, click OK.

2.4.3 Installing Oracle Database on Computers with Multiple Aliases

A computer with multiple aliases is registered with the naming service under a single IP address 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 ORACLE_HOSTNAME environment variable to the computer whose host name you want to use.

2.4.4 Installing Oracle Database 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, perform these steps before you install Oracle Database on the non-networked computer.

  1. Install a loopback adapter on the computer.

    The loopback adapter and local IP address simulate a networked computer. If you connect the computer to the network, Oracle Database still uses the local IP address and host name.

  2. Ping the computer from itself, using only the host name and using the fully qualified name, which should be in the DRIVE_LETTER:\system32\drivers\etc\hosts file.

    For example, if you installed a loopback adapter on a computer called mycomputer on the mydomain.com domain, check the following:

    DRIVE_LETTER:\>ping mycomputer                Ping itself using just the hostname.
    Reply from 10.10.10.10                    Returns local IP.
    DRIVE_LETTER:\>ping mycomputer.mydomain.com   Ping using a fully qualified name.
    Reply from 10.10.10.10                    Returns local IP.
    

    Note:

    When you ping a computer from itself, the ping command should return the local IP address (the IP address of the loopback adapter).

    If the ping command fails, contact your network administrator.

Connecting the Computer to the Network after Installation

If you connect the computer to a network after installation, the Oracle Database instance on your computer can work with other instances on the network. Remember that you must have installed a loopback adapter on your computer. Your computer can use a static IP or DHCP, depending on the network to which you are connected.

2.4.5 Installing a Loopback Adapter

When you install a loopback adapter, the loopback adapter assigns a local IP address for your computer. After the loopback adapter is installed, there are at least two network adapters on your computer: your own network adapter and the loopback adapter. To run Oracle Database on Windows, set the loopback adapter as the primary adapter.

You can change the bind order for the adapters without reinstalling the loopback adapter. The bind order of the adapters to the protocol indicates the order in which the adapters are used. When the loopback adapter is used first for the TCP/IP protocol, all programs that access TCP/IP first probe the loopback adapter. The local address is used for tools, such as Oracle Enterprise Manager. Any other applications that use a different Ethernet segment are routed to the network card.

A loopback adapter is required if:

This section covers the following topics:

2.4.5.1 Checking if a Loopback Adapter Is Installed on Your Computer

To check if a loopback adapter is installed on your computer, run the ipconfig /all command:

DRIVE_LETTER:\>ipconfig /all

Note:

Loopback Adapter installed on the computer should be made the Primary Network Adapter.

If there is a loopback adapter installed, you would see a section that lists the values for the loopback adapter. For example:

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix  . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.10.10
Subnet Mask . . . . . . . . . . . : 255.255.0.0

2.4.5.2 Installing a Loopback Adapter on Windows Server 2003, Windows Server 2003 R2, or Windows XP

To install a loopback adapter on Windows 2003, Windows Server 2003 R2, or Windows XP:

  1. Open the Windows Control Panel.

  2. Double-click Add Hardware to start the Add Hardware wizard.

  3. In the Welcome window, click Next.

  4. In the Is the hardware connected? window, select Yes, I have already connected the hardware, and click Next.

  5. In the The following hardware is already installed on your computer window, in the list of installed hardware, select Add a new hardware device, and click Next.

  6. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

  7. From the list of common hardware types, select Network adapters, and click Next.

  8. In the Select Network Adapter window, make the following selections:

    • Manufacturer: Select Microsoft.

    • Network Adapter: Select Microsoft Loopback Adapter.

  9. Click Next.

  10. In the The wizard is ready to install your hardware window, click Next.

  11. In the Completing the Add Hardware Wizard window, click Finish.

  12. If you are using Windows 2003, restart your computer.

  13. Right-click My Network Places on the desktop and choose Properties. If you are using Windows Vista or Windows Server 2008, then click Manage Network Connections. This displays the Network Connections Control Panel item.

  14. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

  15. On the General tab, select Internet Protocol (TCP/IP), and click Properties.

  16. In the Properties dialog box, click Use the following IP address and do the following:

    1. IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:

      • 192.168.x.x (x is any value between 0 and 255)

      • 10.10.10.10

    2. Subnet mask: Enter 255.255.255.0.

    3. Record the values you entered, which you need later in this procedure.

    4. Leave all other fields empty.

    5. Click OK.

  17. Click Close.

  18. Close Network Connections.

  19. Restart the computer.

  20. Add a line to the DRIVE_LETTER:\ WINDOWS\system32\drivers\etc\hosts file with the following format, after the localhost line:

    IP_address   hostname.domainname   hostname
    

    where:

    • IP_address is the non-routable IP address you entered in step 16.

    • hostname is the name of the computer.

    • domainname is the name of the domain.

    For example:

    10.10.10.10   mycomputer.mydomain.com   mycomputer
    
  21. Check the network configuration:

    Note:

    Domain name is optional.
    1. Open System in the Control Panel, and select the Computer Name tab. In Windows Vista and Windows Server 2008, the Computer Name tab is not available. In Full computer name, make sure you see the host name and the domain name, for example, sales.us.example.com.

    2. Click Change. In Computer name, you should see the host name, and in Full computer name, you should see the host name and domain name. Using the previous example, the host name would be sales and the domain would be us.example.com.

    3. Click More. In Primary DNS suffix of this computer, you should see the domain name, for example, us.example.com.

2.4.5.3 Installing a Loopback Adapter on Windows Vista and Windows Server 2008

To install a loopback adapter on Windows Vista or Windows Server 2008:

  1. Open the Windows Control Panel.

  2. Double-click Add Hardware to start the Add Hardware wizard.

  3. In the Welcome window, click Next.

  4. In the The wizard can help you install other hardware window, select Install the hardware that I manually select from a list, and click Next.

  5. From the list of hardware types, select the type of hardware you are installing window, select Network adapters, and click Next.

  6. In the Select Network Adapter window, make the following selections:

    • Manufacturer: Select Microsoft.

    • Network Adapter: Select Microsoft Loopback Adapter.

  7. Click Next.

  8. In the The wizard is ready to install your hardware window, click Next.

  9. In the Completing the Add Hardware Wizard window, click Finish.

  10. Go to step 12 of the previous section. The remaining steps are the same as given for Windows Vista.

2.4.5.4 Installing a Loopback Adapter on Windows 7

To install a loopback adapter on Windows 7:

  1. Click Start and enter hdwwiz in the Search box.

  2. Click hdwwiz to start the Add Hardware wizard.

  3. Go to step 3 of the previous section. The remaining steps are the same as given for Windows XP.

2.4.5.5 Removing a Loopback Adapter

To remove a loopback adapter:

  1. Display System in the Windows Control Panel.

  2. In the Hardware tab, click Device Manager. This tab is not available with Windows Vista and Windows Server 2008. Click Device Manager instead.

  3. In the Device Manager window, expand Network adapters. You should see Microsoft Loopback Adapter.

  4. Right-click Microsoft Loopback Adapter and select Uninstall.

  5. Click OK.

  6. Restart the computer.

  7. Remove the line from the DRIVE_LETTER:\WINDOWS\system32\drivers\etc\hosts file, added after the localhost line while installing the loopback adapter on other Windows operating systems.

2.5 Individual Component Requirements

This section contains these topics:

See Also:

2.5.1 Configuring Disk Storage for Oracle Data Files and Recovery Files

This section describes the storage options for storing Oracle data files and, optionally, Oracle database recovery files. After you choose the storage method to use for each file type, use the following sections to configure the required storage:

Note:

You do not have to use the same storage option for each file type.

2.5.1.1 Choosing a Storage Option for Oracle Data Files

If you want to create a database during the installation, you must choose one of the following storage options for the data files:

  • File system

  • Automatic Storage Management

The database files must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS.

2.5.1.2 Choosing a Storage Option for Oracle Database Recovery Files

If you want to enable automated backups during the installation, you must choose one of the following storage options for recovery files (the fast recovery area):

  • File system

  • Automatic Storage Management

The storage option that you choose for recovery files can be the same as or different to the option you choose for the data files. The recovery files must be placed on Oracle ASM if using Oracle ACFS; otherwise they can be placed on NTFS.

2.5.1.3 Configuring Disk Storage

For more information about these options, see the "Database Storage Options" section. For information about how to configure disk storage before you start the installation, see one of the following sections depending on your choice:

2.5.2 Creating Directories for Oracle Data Files or Recovery Files

If you decide to place the Oracle database or recovery files on a file system, use the following guidelines when deciding where to place them:

2.5.2.1 Guidelines for Placing Oracle Data Files on a File System

  • You can choose either a single file system or multiple file systems to store the data 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 redundant array of independent disks (RAID) device or a logical volume on multiple physical devices and implement the stripe and mirror everything (SAME) methodology.

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

      Select this method to distribute physical I/O and create separate control files on different devices for increased reliability. You must choose the Advanced database creation option 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 950 MB of free disk space.

    For production databases, you must estimate the disk space requirement depending how you plan to use database.

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

  • The default location suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory. However, this default location is not recommended for production databases.

2.5.2.2 Guidelines for Placing Oracle Recovery Files on a File System

Note:

You must choose a location for recovery files only if you intend to enable automated backups during the installation.

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

  • To prevent disk failure from making both the data files and the recovery files unavailable, place the recovery files in a file system on a different physical disk from the data files.

    Note:

    Alternatively, for both data files and recovery files, use an Automatic Storage Management disk group.
  • The file system that you choose should have at least 2 GB of free disk space.

    The disk space requirement is the default disk quota configured for the fast recovery area (specified by the DB_RECOVERY_FILE_DEST_SIZE initialization parameter).

    If you choose the Advanced database configuration option, you can specify a different disk quota value. After you create the database, you can also use Oracle Enterprise Manager Grid Control or Database Control to specify a different value.

    See Also:

    Oracle Database Backup and Recovery User's Guide for more information about the fast recovery area
  • The default location suggested by Oracle Universal Installer for the database file directory is a subdirectory of the Oracle base directory. However, this default location is not recommended for production databases.

2.5.2.3 Creating Required Directories

Note:

You must complete this procedure only to place the Oracle database or recovery files on a separate file system from the Oracle base directory.

To create directories for the Oracle database or recovery files on separate file systems from the Oracle base directory, follow these steps:

  1. Use Windows Explorer to determine the free disk space on the file system.

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

    File Type File System Requirements
    Data files Choose either:
    • A single file system with at least 950 MB of free disk space.

    • Two or more file systems with at least 950 MB of free disk space in total.

    Recovery files Choose a file system with at least 2 GB of free disk space.

    If you are using the same file system for multiple types of files, then add the disk space requirements for each type to determine the total disk space requirement.

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

  4. If you also want to use Automatic Storage Management, see "Preparing Disks for an Automatic Storage Management Installation" for instructions. Otherwise see the "Stopping Existing Oracle Services" section.

2.5.3 Stopping Existing Oracle Services

Note:

If you are installing additional Oracle Database 11g products in an existing Oracle home, then stop all processes running in the Oracle home. You must complete this task because you cannot overwrite files that are used by the running processes.

Consider the following before you install Oracle grid infrastructure or Oracle Database:

  • If you plan to use Oracle Restart, you must install the grid infrastructure before you install the database. As such, when you perform a database installation, then the database must use the same listener created during the grid infrastructure installation and you do not have to perform the steps listed in this section.

    The default listener and any additional listeners must run from the grid infrastructure home.

  • If you have an existing Oracle Database 11g Release 2 (11.2) running on Oracle Automatic Storage Management, then stop any existing Oracle ASM instance. After you finish installing the grid infrastructure software, start the Oracle ASM instance again.

If you choose to create a database during the installation, then most installation types configure and start a default Oracle Net listener using TCP/IP port 1521 and the IPC key value EXTPROC. However, if an existing Oracle Net listener process is using the same port or key value, Oracle Universal Installer looks for the next available free port (for example, 1522) and configures and starts the new listener on this available free port.

2.5.4 Oracle Advanced Security Requirements

Ensure that you meet the hardware and software requirements so that you can use authentication support with Oracle components.

See Also:

Oracle Database Advanced Security Administrator's Guide for more information about the hardware and software requirements for Oracle Advances Security features

2.5.5 Oracle Enterprise Manager Requirements

All Oracle Enterprise Manager products must belong to the same release. Older versions of Enterprise Manager are not supported with the new release.

Note:

All Oracle Enterprise Manager products, except Oracle Enterprise Manager Database Control, are released on the Enterprise Manager Grid Control installation media. Enterprise Manager Database Control is available on the Oracle Database installation media.

See Also:

2.5.6 Oracle-Managed Files Requirements

If you choose the Advanced database creation option, you can use the Oracle-managed files feature with the new database. If you use this feature, you need only specify the database object name instead of file names when creating or deleting database files. Configuration procedures are required to enable Oracle Managed Files.

See Also:

"Using Oracle-Managed Files" in Oracle Database Administrator's Guide

2.5.7 Oracle Real Application Clusters (Oracle RAC)

If you plan to install Oracle RAC, you must first install Oracle Clusterware.

See Also:

Oracle Real Application Clusters Installation Guide and Oracle Grid Infrastructure Installation Guide , available on the Oracle Clusterware installation media

2.5.8 Oracle Volume Shadow Copy Service (VSS) Writer

Oracle Volume Shadow Copy Service Writer is supported on Windows Server operating systems. On Windows Server 2003 without Service Pack 1, you can have only one database on the system. With Service Pack 1 or higher, you can have multiple Oracle databases on the system.

See Also:

"Performing Database Backup and Recovery with VSS" in Oracle Database Platform Guide for Microsoft Windows

2.5.9 Preinstallation Requirement for Oracle Database Vault

If you want to install Oracle Database Vault, then set the DB_BLOCK_SIZE initialization parameter to 4096 or larger. If the value is less than 4096, then you cannot change it. The only way to change the DB_BLOCK_SIZE value is by re-creating the database.