Skip Headers
Oracle® Database Client Installation Guide
10g Release 2 (10.2) for Microsoft Windows Itanium (64-Bit)

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

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Oracle Database Client Preinstallation Requirements

This chapter describes the following tasks that you must complete before you can install the Oracle Database Client products:

2.1 Oracle Database Client Hardware Requirements

Table 2-1 lists the required hardware components for Oracle Database Client.

Table 2-1 Hardware Requirements

Requirement Minimum Value

Physical memory (RAM)

1 GB mininum

Virtual memory

Double the amount of RAM

Hard disk space

Total ranges from 280–855 MB. See Table 2-2 for details.

Video adapter

256 colors

Processor

Intel Itanium 2 or later


2.1.1 Hard Disk Space Requirements

This section lists system requirements for Windows platforms that use the NT File System (NTFS) file systems. FAT32 space requirements are slightly larger. Oracle recommends installing Oracle components on NTFS.

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 Client components include space required 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, then installation fails and an error message appears.

Table 2-2 lists the space requirements for NTFS.

Table 2-2 Disk Space Requirements for NTFS

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

Instant Client

100 MB

1 MB

180 MB

281 MB

Administrator

100 MB

1 MB

870 MB

971 MB

Runtime

100 MB

1 MB

460 MB

561 MB

Custom (all components installed)

100 MB

1 MB *

710 MB *

811 MB *


* This size varies, depending on the on the installation components selected.

See Also:

"NTFS File System and Windows Registry Permissions" in Oracle Database Platform Guide for Microsoft Windows Itanium (64-Bit)

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

  1. Determine the physical RAM size. For a computer using Windows Server 2003, for example, double-click System in the Windows Control Panel and click the General tab. 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 a computer using Windows Server 2003, for example, double-click System in the Control Panel, click the Advanced tab, and click Settings in the Performance section. Then select the Advanced tab. 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 a computer using Windows Server 2003, for example, double-click My Computer, right-click the drive where the Oracle software is to be installed, and choose Properties.

  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 needed for the Oracle software to be installed.

    If there is less than 100 MB of disk space available in the temp directory, then first delete all unnecessary files. If the temp disk space is still less than 100 MB, then set the TEMP or TMP environment variable to point to a different hard drive. For a computer using Windows Server 2003, for example, double-click System in the Control Panel, click the Advanced tab, and click Environment Variables.

2.2 Oracle Database Client Software Requirements

This section covers the following topics:

2.2.1 General Oracle Database Client Software Requirements

Table 2-3 lists the software requirements for Oracle Database Client.

Table 2-3 Software Requirements

Requirement Value

System Architecture

Processor: Intel Itanium 2 or later

Note: Oracle provides 32-bit (x86), 64-bit (Itanium), and 64-bit (x64) versions of Oracle Database for Windows. The 64-bit (Itanium) database version, which this installation guide describes, runs on the 64-bit version of Windows on Itanium hardware. For additional information, visit My Oracle Support (formerly OracleMetaLink) at:

https://support.oracle.com

Operating System

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

  • Windows Server 2003 Datacenter Edition for 64-bit Itanium 2 Systems

  • Windows Server 2003 Enterprise Edition for 64-bit Itanium 2 Systems

  • Windows Server 2008 for Itanium-Based Systems

  • Windows Server 2008 R2 for Itanium-Based Systems

Windows Multilingual User Interface Pack is supported on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2.

Windows XP is not supported.

Compiler

The following components are supported with the Windows Server 2003 Microsoft Platform SDK or later compiler and Intel compiler versions 7.1 and 8.1

  • Oracle C++ Call Interface

  • Oracle Call Interface

  • External callouts

  • PL/SQL native compilation

  • Pro*C

  • XDK

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 10g Release 2 (10.2) from a release of Oracle Database Client that is earlier than 10g Release 2 (10.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 updated information.

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

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

https://support.oracle.com


2.2.2 Instant Client Light Language and Character Set Requirements

In addition to the requirements described in the previous section, if you plan to use Instant Client Light, your applications must use the following languages and character sets:

  • Language: US English

  • Territory: Any territory that is supported by Oracle

  • Character sets:

    • Single byte

      • US7ASCII

      • WE8DEC

    • Unicode

      • UTF8

      • AL16UTF16

      • AL32UTF8

The language, territory, and character sets are determined by the NLS_LANG parameter, which is stored in the registry under the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID\NLS_LANG subkey, where ID is the unique number identifying the Oracle home.

Caution:

AL32UTF8 is the Oracle Database character set that is appropriate for XMLType data. It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters.

Do not confuse Oracle Database database character set UTF8 (no hyphen) with database character set AL32UTF8 or with character encoding UTF-8. Database character set UTF8 has been superseded by AL32UTF8. Do not use UTF8 for XML data. UTF8 supports only Unicode version 3.1 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.

Using database character set UTF8 for XML data could potentially cause an irrecoverable error or affect security negatively. If a character that is not supported by the database character set appears in an input-document element name, a replacement character (usually "?") is substituted for it. This terminates parsing and raises an exception.

See Also:

Appendix B, "Configuring Oracle Database Client Globalization Support" for more information about NLS_LANG

2.3 Oracle Database Client Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support (formerly OracleMetaLink) Web site for the most up-to-date list of certified hardware platforms and operating system versions. This Web site also provides compatible client and database versions, patches, and workaround information for bugs. The My Oracle Support (formerly OracleMetaLink) Web site is available at the following URL:

https://support.oracle.com/

You must register online before using My Oracle Support (formerly OracleMetaLink). After logging in, click the Certifications tab at the top of the page. Other options include Dashboards, Knowledge, Service Requests, Patches & Updates, Community, Systems, On Demand, and More.

The following sections list the following certification information:

2.3.1 Windows Telnet Services Support

Windows Server 2003 includes a Telnet Service that allows remote users to log on to the operating system and run console programs using the command line, in the same way that they do on UNIX. Oracle supports the use of command line utilities, such as SQL*Plus, Export, Import, and SQL*Loader, using this feature, but does not support their GUI tools.

Note:

Make sure that the Telnet service is started on the Windows Services utility.

2.3.2 Windows Terminal Services and Remote Desktop Support

Oracle supports Terminal Services on Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2. Oracle does not support the installation of Oracle components from a remote Terminal Services Client on to a 64-bit Windows server that is running a Terminal Server service. Start all configuration tools from the Terminal Server console (using mstsc/console) and not from the Terminal Services Client.

You can have multiple Remote Desktop sessions on Windows Server 2008 and Windows Server 2008 R2. You can configure Windows Server 2003, Windows Server 2008, and Windows Server 2008 R2 to use Terminal Services in Remote Desktop for Administration Mode or Terminal Server Mode.

See Also:

2.3.3 Components Not Supported on Windows Itanium

All Oracle Database components are supported on Windows Itanium operating systems with the following exceptions:

  • Oracle Procedural Gateway

  • Business Components for Java (BC4J)

  • DCE and CyberSafe Adapter Support

  • Entrust PKI Support

  • Generic Connectivity

  • Java Server Pages

  • nCipher Accelerator Support

  • Oracle Enterprise Manager Grid Control Media

    Oracle Enterprise Manager Grid Control is not available on Windows 64-bit platforms. Only the Management Agent is provided for this platform. To manage targets on Windows 64-bit platforms with Oracle Enterprise Manager Grid Control, go to OTN to download the Microsoft Windows (64-bit Itanium) agent.

  • Oracle Enterprise Manager Java Console

  • Oracle Migration Workbench

    You can execute Oracle Migration Workbench from a 32-bit Windows environment to migrate third-party databases, as supported by release 9.2.0.2.1 or later, to an Oracle Database 10g Release 2 (10.2) database installed on a 64-bit Windows computer.

  • Oracle Objects for OLE

  • Oracle Workflow Builder

  • Pro*COBOL is not supported on Windows Server 2008 R2.

2.3.4 Web Browser Support

The following Web browsers are supported:

  • Netscape Navigator 7.2

  • Netscape Navigator 8.1

  • Microsoft Internet Explorer 6.0 SP2

  • Microsoft Internet Explorer 7.0

  • Mozilla version 1.7

  • Firefox 1.0.4

  • Firefox 1.5

  • Firefox 2.0

  • Safari 1.2

See Note 412431.1 on My Oracle Support (formerly OracleMetaLink) for the latest certification.