text:
LEoa�, mimetypeapplication/epub+zipPK LE iTunesMetadata.plistd��
This appendix describes how to use response files to perform a silent or response file mode installation of Oracle Database Client. It covers the following topics:
Performing an In-place Oracle Database Client Upgrade Using the Response File
You can automate the installation and configuration of Oracle software, either fully or partially, by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values in the response file to provide answers to some or all of the Oracle Universal Installer prompts.
Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run Oracle Universal Installer at a command prompt using either of the following modes:
Silent mode: Oracle Universal Installer does not display any screens. Instead it displays progress information in the command window where you started it. To use silent mode, you run
setup.exe with the
-silent parameter and include a response file, which contains responses to the Oracle Universal Installer prompts.
Response file mode: Oracle Universal Installer only displays screens for which you did not supply information in the response file. You can use variables in the response file or command-line prompts to suppress other Oracle Universal Installer screens, such as Welcome and Summary, that do not prompt for information. To use response file mode, run
setup.exe without the
-silent parameter, but include the response file or any other parameters that apply.
You define the settings for a silent or response file installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home, you would supply the appropriate value for the
ORACLE_HOME variable, as in the following example:
See Also:
Table B-1describes several reasons why you might want to run Oracle Universal Installer in silent mode or response file mode.
Table B-1 Reasons for Using Silent Mode or Response File Mode
Use silent mode to:
Oracle Universal Installer displays progress information in the window that you used to start it, but it does not display the Oracle Universal Installer screens.
Response file
Use response file mode if you want to complete similar Oracle software installations on multiple systems, providing default answers to some, but not all, of Oracle Universal Installer prompts.
If you do not specify information required for a particular Installer screen in the response file, Oracle Universal Installer displays that screen. It suppresses screens for which you have provided all of the required information.
You follow these general steps to install Oracle Database Client using response files:
Customize or create a response file for the installation settings that you need.
You can create the response file by using either of the following methods:
Modify one of the sample response files that is provided with the installation.
Save response file option during run time.
"Preparing a Response File" explains how to customize or create the response file.
Run Oracle Universal Installer from a command prompt, specifying the response file, using either silent or response file mode.
Note:Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012, require Administrator privileges at the command prompt.
"Running Oracle Universal Installer Using the Response File" explains how to run Oracle Universal Installer with a response file.
This section describes the methods that you can use to prepare a response file for use during silent-mode or response file-mode installations:
Oracle provides response file templates for the database client and the configuration tool. These files are located in the
client\response directory on the Oracle Database installation media.
Table B-2 lists the available Oracle Database Client sample response files:
Table B-2 Response Files
|Response File Name
Oracle Database Client installation
Oracle Net Configuration Assistant to perform the configuration with the client installation types.
To copy and modify a response file:
Copy the appropriate response files from the
client\response directory on the Oracle Database media to your hard drive.
Modify the response files with a text file editor.
See Also:Oracle Universal Installer and OPatch User's Guide for detailed information about creating response files. In an installed Oracle Database, select Start, then Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer Concepts Guide. It appears in HTML format.
Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section.
You can use the Oracle Universal Installer in interactive mode to save a response file, which you can edit and then use to complete silent mode or response file mode installations.
Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file during installation by clicking Save Response File on the Summary page. You can use the generated response file for a silent installation later.
When you save the response file, you can either complete the installation, or you can exit from the installer on the Summary page, before it starts to copy the software to the system.
If you save a response file during a silent installation, then Oracle Universal Installer saves the variable values that were specified in the original source response file into the new response file.
Note:Oracle Universal Installer does not save passwords in the response file.
To save a response file:
Ensure that the computer on which you are creating the response file has met the requirements described in Chapter 2.
When you run Oracle Universal Installer to save a response file, it checks the system to verify that it meets the requirements to install the software. For this reason, Oracle recommends that you complete all of the required preinstallation tasks and save the response file while completing an installation.
At the command prompt, use the
cd command to change to the directory that contains the Oracle Universal Installer
setup.exe executable.
Note:Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012, require Administrator privileges at the command prompt.
On the installation DVD,
setup.exe is located in the
database directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
After Oracle Universal Installer starts, enter the installation settings, to save the response file.
When the installer displays the Summary screen, perform the following:
Click Save Response File and specify a file name and location for the response file. Then, click Save to save the values to the file.
Click Finish to create the response file and continue with the installation.
Click Cancel if you only want to create the response file but not continue with the installation. The installation will stop, but the settings you have entered will be saved in the response file.
Before you use the saved response file on another system, edit the file and make any required changes.
Use the instructions in the file as a guide when editing it.
At this stage, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. On Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012, you must open the command prompt with Administrator privileges. The Oracle Universal Installer executable,
setup.exe, provides several options. For help information about the full set of these options, run
setup.exe with the
-help option, for example:
setup.exe_location setup -help
A new command window appears, with the "Preparing to launch..." message. In a moment, the help information appears in that window.
To run Oracle Universal Installer and specify a response file:
Place the response file on the computer where you want to install Oracle Database Client.
At a command prompt, run Oracle Universal Installer with the appropriate response file. On Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012, you must open the command prompt with Administrator privileges.
To start Oracle Universal Installer in silent or response file mode, enter a command similar to the following:
setup.exe_location[-silent] "variable=setting" [-nowelcome] [-nowait] [-noconfig] -responseFile
Note:Do not specify a relative path to the response file. If you specify a relative path, then Oracle Universal Installer fails.
In this example:
DRIVE_LETTER: Path of the database directory on the DVD.
setup.exe_location: Indicates the location of
-silent: Indicates that you want to run Oracle Universal Installer in silent mode.
"variable=setting" refers to a variable within the response file that you may prefer to run at the command line rather than set in the response file. Enclose the variable and its setting in quotes.
-nowelcome: Suppresses the Welcome window that appears during installation.
-nowait: Closes the console window when the silent installation completes.
-noconfig: Suppresses running the configuration assistants during installation, performing a software-only installation instead.
filename: The full path and file name of the installation response file that you configured.
Starting with Oracle Database 11g Release 2 (126.96.36.199), you can perform an in-place Oracle Database Client upgrade using the response file:
Edit the
oracle.install.client.upgrading entry in the
client_install.rsp file and set it to
true. By default, the
oracle.install.client.upgrading entry is set to
Run Oracle Universal Installer in silent mode as described in "Running Oracle Universal Installer Using the Response File".
This appendix describes the following Globalization Support topics:
Installing and Using Oracle Components in Different Languages
This section describes the following procedures:
You can specify the language and the territory, or locale, in which you want to use Oracle components. The locale setting of a component determines the language of the user interface of the component and the globalization behavior, such as date and number formatting. Depending on the Oracle component, the locale of the component is either inherited from the operating system session that started the component, or is defined by the
NLS_LANG environment variable.
The operating system locale usually influences Oracle components that are based on Java technology. The
NLS_LANG environment variable usually influences Oracle components that use Oracle Client libraries such as OCI.
Note:The user interface of an Oracle component will be displayed in a selected language only if the appropriate translation is available and has been installed. Otherwise, the user interface will be displayed in English.
The locale setting of your operating system session determines the language of the user interface and the globalization behavior for components such as Oracle Universal Installer, Oracle Net Configuration Assistant, and Oracle Database Configuration Assistant. It also determines the globalization behavior of Oracle Database sessions created by a user application through Oracle JDBC driver, unless overridden by the application.
Open the Control Panel from the Start menu to modify the operating system locale settings. On Windows XP, Windows 2003, Windows Server 2003 R2, and in the classic view of the Control Panel on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click Regional and Language Options. In the default view of the Control Panel on Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click Change keyboards or other input methods.
To set locale for the current operating system user on Windows XP, Windows 2003, and Windows Server 2003 R2, select the desired locale from the pop-up list in Standards and formats area on the Regional Options tab. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, select the desired locale from the Current format pop-up list on the Formats tab.
Some of the locales may be unavailable until you install required operating system support files. On Windows XP, Windows 2003, and Windows Server 2003 R2, make sure the relevant check boxes are checked in "Supplemental language support" area on Languages tab.
Some Oracle components, such as SQL*Plus, require that the Windows System Locale is also set to the language in which the components are to be run. System Locale is called Language for non-Unicode programs on Windows XP, Windows 2003, Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. On Windows XP and Windows 2003, select the locale from the pop-up list in the "Language for non-Unicode programs" area on the Advanced tab. On Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2, click the Change system locale... button on the Administrative tab, accept the use of administrative privileges, if User Account Control is active, and select the locale from the pop-up list in the opened dialog box.
Note:The operating system must be restarted after the System Locale is changed. See the operating system documentation for further information about Windows locale settings.
NLS_LANG environment variable determines the language of the user interface and the globalization behavior for components such as SQL*Plus, exp, and imp. It sets the language and territory used by the client application and the database user session. It also declares the character set for entering and displaying data by the client application.
NLS_LANG environment variable uses the following format:
In this format:
language specifies the language used for displaying user interface, error messages, sorting, day names, and month names
territory specifies the conventions for default date, monetary and numeric formats
characterset specifies the encoding of the database client, which is the character set for data entered or displayed by a client program
In most cases, this is the Oracle character set that corresponds to the Windows ANSI Code Page as determined by the System Locale.
NLS_LANG parameter on Windows can be set
in Registry under the subkey corresponding to a given Oracle home,
as an environment variable.
When you install Oracle Database components and the
NLS_LANG parameter is not yet set in the Registry subkey of the target Oracle home, Oracle Universal Installer sets the
NLS_LANG parameter to a default value derived from the operating system locale for the current user.
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.0 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation.
Using database character set UTF8 for XML data could 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 a question mark) is substituted for it. This will terminate parsing and raise an exception.
See Also:
For example:
Arabic (U.A.E.) -
Chinese (PRC) -
Chinese (Taiwan) -
English (United Kingdom) -
English (United States) -
French (Canada) -
French (France) -
German (Germany) -
Hebrew -
Japanese -
Russian -
Spanish (Spain) -
Spanish (Mexico) -
Spanish (Venezuela) -
Before you can use Oracle utilities such as SQL*Plus, SQL Loader, Import, and Export from the Command Prompt window, you may have to set the character set field of the
NLS_LANG parameter to a value different than the one set in Registry.
This is required because programs running in console mode use, with a few exceptions, a different code page (character set) from programs running in GUI mode. The default Oracle home
NLS_LANG parameter in the Registry is always set to the appropriate GUI code page. If you do not set the
NLS_LANG parameter for the console mode session correctly, incorrect character conversion can corrupt error messages and data.
For Japanese, Korean, Simplified Chinese, Traditional Chinese, Thai, and Vietnamese, the console (OEM) code page is identical to the GUI (ANSI) code page. In this case, you do not need to set the
NLS_LANG parameter. For other languages, set the correct character set value of
NLS_LANG by issuing a
SET NLS_LANG command in the same Command Prompt window in which you want to start the affected utility.
Similarly, in batch mode, set the correct character set value of
NLS_LANG by inserting a
SET NLS_LANG command at the start of the batch procedure, according to the character set of the files to be processed in the procedure.
To find the current console code page, issue the
CHCP command in the Command Prompt window. Use the reported code page number to look up the corresponding Oracle character set name in Table C-1.
Table C-1 lists the Oracle character sets that correspond to the console mode code pages.
Table C-1 Oracle Character Sets for Console Mode (OEM) Code Pages
|OEM Code Page
|Oracle Character Set for Console Mode
737 (Greek)
775 (Baltic)
850 (Multilingual Latin I)
852 (Latin II)
855 (Cyrillic)
857 (Turkish)
858 (Multilingual Latin I + Euro)
866 (Russian)
874 (Thai)
932 (Japanese Shift-JIS)
936 (Simplified Chinese GBK)
949 (Korean)
950 (Traditional Chinese Big5)
1258 (Vietnam)
To view the user interface of Oracle components in different languages, you must install the appropriate language translations along with the component. To select the translation resources that you want to install:
Note:Part of Oracle Database Vault user interface text is stored in database tables in the DVSYS schema. By default, only the English language is loaded into these tables. You can use Oracle Database Vault Configuration Assistant to add more languages to Oracle Database Vault. For the necessary steps, see Appendix C in Oracle Database Vault Administrator's Guide.
Start Oracle Universal Installer.
On the Select Installation Option screen, select the installation option and click Next.
On the System Class screen, select the type of system for installing the database, and click Next.
On the Grid Installation Options screen, select the type of database installation you want to perform, and click Next.
On the Select Install type screen, select the type of installation, and click Next.
On the Select Product Languages screen, select the language in which you want to run the product from the Available Languages field.
Note:The Available Languages field lists all languages supported by Oracle globalization libraries. The set of languages for which a translation is actually available is usually smaller and depends on a particular component. The scope of translation for a given component may differ between languages. For example, some translations may include all user interface text, while others may include only error messages and no help files.
Use the > arrow to move the selected language to the Selected Languages field, and then click OK.
Note:Oracle Universal Installer will ignore languages in the Selected Languages field for which no translation is available.
The operating system locale determines the language in which Oracle Universal Installer runs. Oracle Universal Installer may run in one of the following languages:
Brazilian Portuguese
Simplified Chinese
Traditional Chinese
To run Oracle Universal Installer in a desired language:
Change the locale for the operating system user and the System Locale as described in "Determining the Operating System Locale" section.
Run Oracle Universal Installer by following the instructions in the "Installing the Oracle Database Client Software" section.
If the selected language is not from the languages listed earlier, then Oracle Universal Installer runs in English.
This chapter describes the different types of Oracle Database Client installations that you can perform, and issues to consider before you install the software:
The Oracle Database Client installation process consists of five steps:
Read the release notes: Read the Oracle Database Release Notes before you begin the installation. The release notes are available with the platform-specific documentation. The latest version of the release notes is available on Oracle Technology Network at
Plan your installation: This overview chapter describes the installation types that you can use to install Oracle Database Client and issues to consider before you begin.
You may also want to refer to Appendix A, "Frequently Asked Questions about Installation," in Oracle Database Installation Guide. This appendix advises on the best way to install Oracle products depending on your site's requirements.
Complete preinstallation tasks: Chapter 2 describes preinstallation tasks that you must complete before installing Oracle Database Client.
Install the software: Use the following sections to install Oracle Database Client:
Chapter 3 describes how to use the Oracle Universal Installer (OUI) GUI to install Oracle Database Client.
Appendix B describes how to perform a silent installation using response files.
"Installing and Using Oracle Components in Different Languages" describes how to install and use Oracle components in different languages.
Appendix D provides troubleshooting advice in case you encounter problems with the installation.
Chapter 5 describes how to remove Oracle Database Client.
Complete postinstallation tasks: Use the following sections to complete the postinstallation tasks:
Chapter 4 describes recommended and required postinstallation tasks.
Appendix C provides information about globalization support.
For information about interoperability between different versions of Oracle Database Client and Oracle Database releases, see Note 207303.1 on the My Oracle Support (formerly OracleMetaLink) Web site at
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 cannot be placed on NTFS. Usage of Oracle ACFS and Oracle ASM or NTFS instead of FAT32 is recommended to ensure security of these files.
See Also:"File Permissions" in Oracle Database Platform Guide for Microsoft Windows for information about the default permissions when using Oracle Universal Installer and Database Configuration Assistant to install the Oracle Database software
To ensure that only trusted applications run on your computer, Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012 provide User Account Control. If you have enabled this security feature, then, depending on how you have configured it, Oracle Universal Installer prompts you for either your consent or your credentials when installing Oracle Database. Provide either the consent or your Windows Administrator credentials as appropriate.
You must have Administrator privileges to run some Oracle tools, such as Database Configuration Assistant, Net Configuration Assistant, and OPatch, or to run any tool or application that writes to any directory within the Oracle home. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run each of these commands in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly invoke these tasks with Windows Administrator privileges. All the Oracle shortcuts that require Administrator privileges will be invoked as "Administrator" automatically when you click the shortcuts. However, if you run the above tools from a Windows command prompt, you must run them from an Administrator command prompt. OPatch does not have a shortcut and has to be run from an Administrator command prompt.
See Also:"Running Tools with Windows User Account Control" in Oracle Database Platform Guide for Microsoft Windows for more information
To start a command prompt window with Windows Administrator privileges:
On your desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the desktop.
Right click the icon for the newly created shortcut, and specify "Run as administrator."
When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.
You can choose one of the following installation types when installing Oracle Database Client:
Instant Client: Installs only the shared libraries required by Oracle Call Interface applications that use the Instant Client feature. This installation type requires much less disk space than the other Oracle Database Client installation types.
Included in the Instant Client installation is Instant Client Light. You may want to use this version of Instant Client if your applications generate error messages in American English only. The advantage of using Instant Client Light is that it has a much smaller footprint than regular Instant Client. Hence, your applications use less memory.
Administrator: Enables applications to connect to an Oracle database on the local system or on a remote system. It provides tools that let you administer an Oracle database.
Runtime: Enables applications to connect to an Oracle database on the local system or on a remote system.
Custom: Enables you to select individual components from the list of Administrator and Runtime components.
Starting with Oracle Database 11g Release 2 (11.2), the patching process of
TIMESTAMP WITH TIME ZONE data type values is simplified.
See Also:"Oracle Database 11g Release 2 (11.2) New Features in Globalization" and "Clients and Servers Operating with Different Versions of Time Zone Files" in Oracle Database Globalization Support Guide for more information about the simplified patching process and how certain clients work with server with different time zone files
Use the Software Updates feature to dynamically download and apply the latest updates released by Oracle; such as, interim patch updates, critical patch updates, Oracle Universal Installer updates, and the latest patch set updates. This functionality is available starting with Oracle Database 11g Release 2 (18.104.22.168).
You can choose to download the latest updates by providing My Oracle Support credentials or you can apply previously downloaded updates. You can also download the updates separately using the
-downloadUpdates option and later apply them during the installation by providing the location where the updates are present.
See Also:"Procedure for Installing Oracle Database Client" for more information about the
-downloadUpdates option, and dynamically applying software updates during the installation
Client Installation Guide
11g Release 2 (11.2) for Microsoft Windows
April 2014
Oracle Database Client Installation Guide 11g Release 2 (11.2) for Microsoft Windows
Copyright © 1996, 2014, Oracle and/or its affiliates. All rights reserved.
Primary Author: Reema Khosla
Contributing Authors: Janet Stern, Prakash Jashnani
Contributors: Eric Belden, Sudip Datta, David Friedman, Alex Keh, Peter LaQuerre, Rich Long, Matt McKerley, Sham Rao Pavan, Hanlin Qian, Janelle Simmons, Helen Slattery, Sujatha Tolstoy, Michael Verheij, Madhu Velukur, Sergiusz Wolicki, Sue Mavris, Mohammed Shahnawaz Quadri, Rahul S Joshi, Vishal Saxena, Krishna Itikarlapall
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
This appendix describes how to install Java Access Bridge, which enables use of a screen reader with Oracle components:
Note:Java Access Bridge is not supported on Windows x64 for 64-bit database installations.
Java Access Bridge 2.0.2 enables assistive technologies to read Java applications running on the Windows platform. Assistive technologies can read Java-based interfaces, such as Oracle Universal Installer and Oracle Enterprise Manager Database Control.
Java Access Bridge 2.0.2 is supported on Windows Server 2008 (32-bit), Windows Server 2008 x64, Windows Server 2008 R2 x64, Windows 7 (32-bit), Windows 7 x64, Windows 8 (32-bit), Windows 8 x64, Windows 8.1 (32-bit), Windows 8.1 x64, and Windows Server 2012 x64 for 64-bit database installations. For a list of supported system configurations, including supported versions of Microsoft Windows and Java SE, see section "Supported System Configuration" available at the following link location:
During installation, Oracle Universal Installer uses Java Runtime Environment (JRE) 1.6 contained in Oracle Database, Oracle Database Client, and Oracle Database installation media. The JRE enables use of Java Access Bridge 2.0.2 during installation. See "Setting Up Java Access Bridge 2.0.2" for information about installing and configuring Java Access Bridge after you install Oracle components.
This section describes how to install and configure Java Access Bridge 2.0.2 for Windows after installing Oracle components.
To set up Java Access Bridge 2.0.2 on a Windows 32-bit and 64-bit operating system, follow these steps:
Go to Java Standard Edition (Java SE) Downloads page to download the latest build of JDK 7:
Install JDK 7 after accepting the Oracle license agreement.
Note:You must have administrator privileges to install JDK on Windows.
Press Windows key+U to open the Ease of Access Center, and select Use the computer without a display.
Select Enable Accessbridge check box. Click Save to save the changes.
Download Java Access Bridge 2.0.2:
Download the
accessbridge-2_0_2-fcs-bin-b06.zip file, after accepting the Oracle license agreement.
accessbridge-2.0.2 to a directory on your system where you plan to install Java Access Bridge. For example, name the directory as follows:
Open the command prompt and navigate to one of the directory depending on the type of installation (database, client, or companion) you performed by typing the
To access the files in
Disk1 directory, type the following:
DRIVE_LETTER:\>cd Disk1
Run the following command once you are in the
Disk1 directory:
setup.exe -jreLoc
Oracle Universal Installer starts and JAWS is able to read all prompts and controls on the screen.
Once you click the Install button, you must open Windows Explorer to see the directory where the database is installed (
dbhome_1), until the JDK folder is created. Once the JDK folder is created, you must copy the files listed in Table A-1 and Table A-2 from the Java Access Bridge source location to the JDK destination folder. Copying these files will enable accessibility for both Oracle Database Configuration Assistant and Oracle Net Configuration Assistant.
Table A-1 Copy Files to JDK Directory on Windows 32-Bit
Table A-2 Copy Files to JDK Directory on Windows 64-Bit
connect descriptor
A specially formatted description of the destination for a network connection. A connect descriptor contains destination service and network route information.
The destination service is indicated by using its service name for the Oracle Database or its Oracle system identifier (SID) for Oracle release 8.0, or version 7 databases. The network route provides, at a minimum, the location of the listener through use of a network address.
default domain
The network domain within which most client requests take place. It can be the domain where the client resides, or a domain from which the client often requests network services. The default domain is also the client configuration parameter that determines what domain to append to unqualified network name requests. A name request is unqualified if it does not have a "." character within it.
easy connect naming
A Naming method that allows clients to connect to a database server without any configuration. Clients use a simple TCP/IP address, which consists of a host name and optional port number, service name, and instance name:
SQL>CONNECT user_name@host[:port][/service_name][/instance_name] Enter password: password
installation type
An installation type is a predefined component set that automatically selects which components to install. See "Oracle Database Client Installation Types" for a list of installation types available with each top-level component.
Interprocess Communication (IPC)
A protocol used by client applications that resides on the same node as the listener to communicate with the database. IPC can provide a faster local connection than TCP/IP.
ldap.ora file
A file created by the Oracle Net Configuration Assistant that contains the following directory access information:
Type of directory
Location of directory
Default administrative context the client or server uses to look up or configure connect identifiers for connections to database services
ldap.ora file resides in
A process that resides on the server and whose responsibility is to listen for incoming client connection requests and manage the traffic to the server.
When a client requests a network session with a database server, a listener receives the actual request. If the client information matches the listener information, then the listener grants a connection to the database server.
listener.ora file
A configuration file for the listener that identifies the:
Listener name
Protocol addresses on which it is accepting connection requests
Services for which it is listening
listener.ora file resides in
An Oracle Database 11g Release 2 (11.2) does not require identification of the database service because of service registration. However, static service configuration is required for an Oracle Database 11g Release 2 (11.2) if you plan to use Oracle Enterprise Manager.
local naming
A Naming method that resolves a net service name into a connect descriptor. This name is configured and stored in the tnsnames.ora file on each individual client.
Naming method
A resolution method used by a client application to resolve a connect identifier to a network address when attempting to connect to a database service. Oracle Net Services supports the following naming methods:
Local naming
Directory naming
Easy Connecting naming
NIS External naming
net service name
A simple name for a service that resolves to a connect descriptor. Users initiate a connect request by passing a username and password along with a net service name in a connect string for the service to which they want to connect:
SQL> CONNECT username@net_service_identifier Enter password: password
Depending on your needs, net service names can be stored in a variety of places, including:
Local configuration file,
tnsnames.ora, on each client
Directory server
External naming service, such as Network Information Service (NIS) or Cell Directory Service (CDS)
operating system authenticated connections
Windows login credentials can be used to authenticate users connecting to an Oracle Database. The benefits of Windows native authentication include:
Enabling users to connect to multiple Oracle Databases without supplying a username or password
Centralizing Oracle Database user authorization information in Windows, which frees Oracle Database from storing or managing user passwords
The initialization file parameter
OS_AUTHENT_PREFIX enables users to specify a prefix that Oracle uses to authenticate users attempting to connect to the database. Oracle concatenates the value of this parameter to the beginning of the user's operating system account name. When a connection request is attempted, Oracle compares the prefixed username with Oracle usernames in the database.
The default value of this parameter is
"" (a null string), thereby eliminating the addition of any prefix to operating system account names. In earlier releases,
OPS$ (short for operating system specific) was the default setting.
Oracle Context
The root of a directory subtree with a relative distinguished name of
cn=OracleContext, under which all Oracle software information is kept. There may be one (or multiple) Oracle Context in a directory. An Oracle Context can be associated with a directory naming context.
The Oracle Context can contain the following Oracle entries:
Connect identifiers for use with Oracle Net Services directory naming to make database connections
Enterprise user security for use with Oracle Advanced Security
Oracle home
The directory path to install Oracle components (for example,
n where
n is the number of the Oracle home). You are prompted to enter an Oracle home in the Path field of the Oracle Universal Installer File Locations window.
Oracle schema
A set of rules that determine what can be stored in an LDAP-compliant directory server. Oracle has its own schema that is applied to many types of Oracle entries, including Oracle Net Services entries. The Oracle schema for Oracle Net Services entries includes the attributes the entries may contain.
Oracle Net foundation layer
A networking communication layer that is responsible for establishing and maintaining the connection between the client application and server, and exchanging messages between them.
protocol address
An address that identifies the network address of a network object.
When a connection is made, the client and the receiver of the request, such as the listener, or Oracle Connection Manager, are configured with identical protocol addresses. The client uses this address to send the connection request to a particular network object location, and the recipient "listens" for requests on this address. It is important to install the same protocols for the client and the connection recipient, as well as configure the same addresses.
A set of tables located in any Oracle database accessible to the Oracle Management Server. Oracle Management Server uses a repository to store all system data and application data, information about the state of managed nodes distributed throughout the environment, as well as information about the separately licensable management packs.
service registration
A feature by which the PMON process (an instance background process) automatically registers information with a listener. Because this information is registered with the listener, the listener.ora file does not need to be configured with this static information.
Service registration provides the listener with the following information:
Service name(s) for each running instance of the database
Instance name(s) of the database
Service handlers (dispatchers and dedicated servers) available for each instance
This allows the listener to direct a client's request appropriately.
Dispatcher, instance, and node load information
This allows the listener to determine which dispatcher can best handle a client connection's request. If all dispatchers are blocked, the listener can spawn a dedicated server for the connection.
This information allows the listener to determine how best to service a client connection request.
The Oracle system identifier that distinguishes the database from all other databases on your computer. The SID automatically defaults to the database name portion of the global database name (
sales in the example
sales.us.example.com) until you reach eight characters or enter a period. You can accept or change the default value.
sqlnet.ora file
A configuration file for the client or server that specifies the:
Client domain to append to unqualified service names or net service names
Order of naming methods for the client to use when resolving a name
Logging and tracing features to use
Route of connections
External naming parameters
Oracle Advanced Security parameters
sqlnet.ora file resides in
system identifier
See SID.
Terminal Server
Microsoft Windows Terminal Server is a Windows thin-client terminal server, a product that adds support for multiple, simultaneous client sessions on the Windows Server. Windows Terminal Server provides an operating system graphical user interface (GUI) to users of Oracle databases.
tnsnames.ora file
A configuration file that contains net service names mapped to connect descriptors. This file is used for the local naming method. The
tnsnames.ora file resides in
typical configuration
Oracle Universal Installer option that performs a default configuration of a connection between Oracle Database Client and Oracle Database. It configures the following:
One net service name in the tnsnames.ora file.
local naming and easy connect naming methods in the sqlnet.ora file.
When Oracle Database Client attempts to connect, it tries local naming first, followed by easy connect naming.
This chapter describes the following postinstallation tasks:
Required Product-Specific Postinstallation Task – Configuring Oracle Net Services
Note:This chapter describes basic configuration only. See Oracle Database Platform Guide for Microsoft Windows and product-specific administration and tuning guides for more sophisticated configuration and tuning information.
This section covers the following topics:
To download required patches, check the My Oracle Support (formerly OracleMetaLink) Web site for required patches for your installation. Doing so ensures that you have the latest update of Oracle Database Client.
Note:You cannot update Instant Client by downloading a patch. Use the procedure under "Updating Instant Client" to update Instant Client.
To find and download patches:
Use a web browser to view the My Oracle Support website:
Log in to My Oracle Support.
Note:If you are not a My Oracle Support registered user, then click Register here and follow the registration instructions.
On the main My Oracle Support page, click Patches and Updates tab.
In the Patch Search group, select Product or Family (Advanced).
In the Product field, select Oracle Database.
In the Release field select the release number. For example, Oracle 126.96.36.199.0.
Click Search.
Any available patch updates are displayed in the Patch Search page.
Select the patch number and click ReadMe. The README page is displayed and contains information about the patch set and how to apply the patches to your installation.
Return to the Patch Search page, click Download, and save the file on your system.
Use the unzip utility provided with Oracle Database 12c to uncompress the Oracle patch updates that you downloaded from My Oracle Support. The unzip utility is located in the
\bin directory.
Download Instant Client from Oracle Technology Network
Place the new files directly on top of the previous files.
If you place the files into a different directory (and remove the previous files), be sure to update your
PATH environment variable setting to reflect the new location.
Oracle recommends that you perform the tasks in the following sections after completing an installation:
Connecting Instant Client or Instant Client Light to an Oracle Database
Using Oracle9i Language and Definition Files with Oracle Database 11g Release 2
To configure Instant Client Light, you must make it the default instead of Instant Client.
To configure Instant Client Light:
In the
ORACLE_CLIENT_HOME directory, either rename or delete the
oraociei11.dll file.
oraociei11.dll file is the main binary for Instant Client.
From the
\install\instantclient\light directory, copy the
oraociicus11.dll file to the
ORACLE_CLIENT_HOME directory.
oraociicus11.dll file is the binary for Instant Client Light.
Ensure that the
PATH environment variable points to the
ORACLE_CLIENT_HOME directory.
Note:If the Instant Client
PATH is not set, applications will try to load the regular Instant Client libraries first. If the applications cannot find these, they will attempt to load the Instant Client Light library next.
After you run Oracle Universal Installer to install Oracle Database Client, you must use Net Configuration Assistant (NetCA) to configure Oracle Database Client to connect to an Oracle database. At the end of installation, Oracle Universal Installer prompts you to configure the database connection. If you bypassed that option, or if you need to change the database connection later on, use the following procedure if you installed the Administrator, Runtime, or Custom installation types.
See Also:"Connecting Instant Client or Instant Client Light to an Oracle Database" if you had installed the Instant Client installation type
To connect Oracle Database Client to an Oracle Database:
From the Start menu, choose Oracle - HOME_NAME, then Configuration and Migration Tools, then Net Configuration Assistant.
In the Welcome window, select Local Net Service Name configuration and click Next.
In the Net Service Name Configuration window, select Add and click Next.
In the Service Name window, enter the name of the Oracle database to which you want to connect and click Next.
In the Select Protocols window, select the protocol you want and click Next.
In the Protocol window, depending on the protocol you selected, enter the appropriate information and click Next.
In the Net Test window, select whether you want to test the connection, and click Next.
In the Net Service Name window, enter a name for the net service and click Next.
Answer the remaining prompts, which allow you to configure another net service name, and then click Finish to complete the configuration.
Net Configuration Assistant creates the
tnsnames.ora file in the following location:
See Also:Oracle Database Net Services Administrator's Guide for more information about Oracle Net Configuration Assistant
Before you can connect Instant Client or Instant Client Light to an Oracle database, ensure that the
PATH environment variable specifies the directory that contains the Instant Client libraries. (By default, Oracle Universal Installer updates the
PATH variable for you during the installation process, but another user may have inadvertently reset it since then.) This directory is the Oracle home directory that you specified during installation.
For example, for regular Instant Client, it is in:
For Instant Client Light, it is in:
After you have checked the
PATH environment variable, you can use any of the following methods to specify Oracle Database connection information for client applications:
Specifying a Connection by Using the Easy Connect Naming Method
Specifying a Connection by Using an Empty Connect String and the LOCAL Variable
You can specify a connection address to an Oracle Database directly from a client application, without having to configure a
tnsnames setting for the Instant Client. This method is convenient in that you do not have to create and manage a
tnsnames.ora file. However, your application users must specify the host name and port number when they want to log in to your application.
For example, suppose you are running SQL*Plus on the client computer and want to connect to the
sales_us database, which is located on a server whose host name is
shobeen and port number is 1521. If you launch SQL*Plus from the command line, you could log in as follows:
sqlplus system/admin@//shobeen:1521/sales_us
Similarly, in your application code, you can use Oracle Call Interface net naming methods to create the Instant Client-to-Oracle Database connection. For example, the following formats in the
OCIServerAttach() call specify the connection information:
Specify a SQL connect URL string using the following format:
For example:
Alternatively, you can specify the SQL connect information as an Oracle Net keyword-value pair. For example:
"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=shobeen) (PORT=1521))(CONNECT_DATA=(SERVICE_NAME=sales_us)))"
See Also:Oracle Call Interface Programmer's Guide for more information about using Oracle Call Interface Instant Client
By default, when you install Instant Client, Oracle Universal Installer does not include a sample
tnsnames.ora file nor the Oracle Net Configuration Assistant utility normally used to create it. However, if you want to shield users from having to specify actual host names and port numbers, you may want to consider using a
tnsnames.ora file to set the Instant Client-to-Oracle Database connection.
You can create the
tnsnames.ora file manually by copying and modifying a version of this file from another Oracle installation, or you can use Oracle Net Configuration Assistant to create and manage it for you.
To install Oracle Net Configuration Assistant:
Run Oracle Universal Installer.
Select the Custom installation type.
In the Available Product Components list, select Oracle Network Utilities and click Next.
In the Summary window, click Install, then click Exit and Yes to exit Oracle Universal Installer.
After you have installed Oracle Net Configuration Assistant, follow the procedure in "Connecting Oracle Database Client to an Oracle Database" for each client computer.
Then, on each client computer, configure either of the following settings:
Set the
TNS_ADMIN environment variable to specify the location of the
tnsnames.ora file and specify a service name from that file.
Place the
tnsnames.ora file in the
\network\admin directory, and ensure that the
ORACLE_HOME environment has been set to this Oracle home.
See Also:Oracle Call Interface Programmer's Guide for more information about Oracle Call Interface Instant Client connection strings
You can set the connect string to an empty connect string (""), and then set the
LOCAL environment variable to one of the following values:
A direct address, as described under "Specifying a Connection by Using the Easy Connect Naming Method"
Oracle Net keyword-value pair
tnsnames.ora entry and
TNS_ADMIN is set to the location of
tnsnames.ora entry and the following:
tnsnames.ora file located in
ORACLE_HOME environment variable set to this Oracle home
This method allows your applications to specify internally a connection string if the application code itself uses an empty connection string. The benefit of an empty connect string is that the application itself does not need to specify the
tnsnames.ora entry. Instead, when a user invokes the application, the location of the database is determined by a script or the environment, depending on where you have set the
LOCAL environment variable. The disadvantage of using empty strings is that you must configure this additional information in order for your application to connect to the database.
For information about setting up additional user accounts, see Oracle Database Platform Guide for Microsoft Windows.
Changes have been made to the content of some of the language and territory definition files in Oracle Database 10g and later releases. These updates are necessary to correct the legacy definitions that no longer meet the local conventions in some of the languages and territories that Oracle Database supports.
Oracle Database 11g Release 2 customers should review their existing application code to ensure that the correct cultural conventions, which were introduced and defined in Oracle Database 10g, are being used. For customers who may not be able to make the necessary code changes to support their applications, Oracle Database offers Oracle9i locale definition files with this release of Oracle Database. If the Oracle Database server installation has been configured to use the Oracle9i files, then you must enable this functionality in each client installation as well.
To enable this functionality:
Run the
cr9idata.pl script, by default located in
If the client installation type you chose does not include this directory, you can find the
cr9idata.pl script in the same directory path in a default Oracle Database installation.
Set the
ORA_NLS10 environment variable to point to the directory where you installed the new language and territory definition files, which by default are in
Restart Oracle Database.
See Also:
Before you can use to view Oracle-specific counters, you must specify the system password using
operfcfg.exe located in the
\bin directory.
To set the system password, enter the following:
DRIVE_LETTER:\> ORACLE_HOME\bin\operfcfg.exe Enter user-name: system Enter password: password Enter tns-alias: orcl operfcfg: New registry values have been successfully set.
See Also:Oracle Database Platform Guide for Microsoft Windows for additional information about Oracle Counters for Windows Performance Monitor
You can configure Oracle Database Client to communicate with Oracle Net Services by adding the appropriate entries to the
tnsnames.ora and
listener.ora files. If you have a previous release or Oracle software, you can just copy information in the Oracle Net
tnsnames.ora and
listener.ora configuration files from the previous release to the corresponding files in the new release.
Note:The default location for the
tnsnames.ora and
listener.ora files is the
\network\admin directory.
This section describes tasks that you must complete after you install the software:
The first time you start SQL Developer after installing it or after adding any extensions, you are asked if you want to migrate your user settings from a previous release. (This occurs regardless of whether there was a previous release on your system.)
Note:Migration of user settings is supported only from SQL Developer Release 1.0 to Release 1.1. It is not supported for migration from a pre-release version of 1.1 to Release 1.1.
These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must re-specify these using the new release.
To migrate user settings from SQL Developer Release 1.0:
Install Oracle SQL Developer.
When you start SQL Developer Release 1.1, click Yes when asked if you want to migrate settings from a previous release.
In the dialog box that is displayed, do not accept the default location for the settings. Instead, specify the location of your Release 1.0 settings, which might be a folder whose path ends with
See also Section 4.4.2, "Migrating Information from Previous Releases."
If you have used a previous release of SQL Developer or a pre-release version of the current release, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections.
If you want to use any user-defined reports or the SQL history from a previous version, see "Location of User-Related Information" for information about where these are loc��ated. If you want to use any user-defined reports or the SQL history from Release 1.0 with both Releases 1.0 and 1.1, you must save them before using Release 1.1, because Release 1.1 modifies the files to a format that is incompatible with Release 1.0.
SQL Developer preferences (specified by clicking Tools and then Preferences) from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.
SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, and SQL Developer user preferences.
SQL Developer user preferences are stored under the installation directory. To preserve preferences when upgrading to a more recent version of the same SQL Developer release, but not to upgrade from Release 1.0 to 1.1, use the Check for Updates feature (click Help, then Check for Updates) to upgrade your system.
This user-related information is stored in or under the
HOME environment variable location, if defined; otherwise the
SQLDEVELOPER_USER_DIR location, if defined; otherwise as indicated in the following table.
The table shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory or folder named
Table 4-1 Default Locations for User-Related Information
|Resource Type
|Windows Systems
User-defined reports
C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml
User-defined snippets
C:\Documents and Settings\<user-name>\.sqldeveloper\UserReports.xml
SQL history
C:\Documents and Settings\<user-name>\.sqldeveloper\SqlHistory.xml
SQL Worksheet archive files
C:\Documents and Settings\<user-name>\.sqldeveloper\tmp\
SQL Developer user preferences
SQL Worksheet archive files contain SQL statements that you have entered. These files begin with sqldev and then have a random number (for example,
sqldev14356.sql). If you close SQL Developer with a SQL Worksheet open that contains statements, then you will be prompted to save these files.
To specify a nondefault
SQLDEVELOPER_USER_DIR location, do either of the following:
Set the
SQLDEVELOPER_USER_DIR environment variable to specify another directory path.
Edit the
\sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file and substitute the desired directory path for
SQLDEVELOPER_USER_DIR in the following line:
SetUserHomeVariable SQLDEVELOPER_USER_DIR
If you want to prevent other users from accessing your user-specific SQL Developer information, you must ensure that the appropriate permissions are set on the directory where that information is stored or on a directory above it in the path hierarchy. For example, you may want to ensure that the
sqldeveloper folder and the
\.sqldeveloper folder under
Documents and Settings are not sharable.
This guide provides instructions about installing and configuring Oracle Database Client for both Microsoft Windows (32-Bit) and Microsoft Windows (x64). Only the features of Oracle Database for Microsoft Windows (32-bit) and Microsoft Windows (x64) are discussed in this guide.
This preface contains these topics:
Oracle Database Client Installation Guide for Microsoft Windows is intended for anyone installing an Oracle Database Client.
To use this document, you need the following:
A supported Microsoft Windows operating system installed and tested on your computer system
Administrative privileges on the computer where you are installing Oracle Database Client
Familiarity with object-relational database management concepts
See Also:
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
For more information, see these Oracle resources:
Oracle Enterprise Manager Grid Control Basic Installation Guide
Many of the examples in this book use the sample schemas, which are installed by default when you select the Basic Installation option with an Oracle Database installation. Refer to Oracle Database Sample Schemas for information about how these schemas were created and how you can use them yourself.
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at
The following text conventions are used in this document:
|Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
|Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
|Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
You can use 32-Bit media for installing Oracle Database Client on all supported operating systems. You can use 64-Bit media for installing Oracle Database Client on all supported 64-bit x64 operating systems. This guide is for both Windows 32-Bit and Windows x64. This chapter covers the following topics:
Preinstallation Considerations Before Installing Oracle Database Client
The Oracle Database Client software is available on the Oracle Technology Network (OTN) Web site. In most cases, you use the graphical user interface (GUI) provided by Oracle Universal Installer to install the software. However, you can also use Oracle Universal Installer to complete silent-mode installations using response files, without using the GUI.
Review the information in Chapter 1, "Oracle Database Client Installation Overview" and complete the tasks listed in Chapter 2, "Oracle Database Client Preinstallation Requirements" before beginning the installation.
Next, consider the following issues:
Installing Oracle Database Client Installations in Silent or Response File Mode
Installing Oracle Database Client into Multiple Oracle Homes
Installing Oracle Database Client on a System with an Existing Oracle Software
On Windows Vista, Windows Server 2008, Windows Server 2008 R2, Windows 7, Windows 8, Windows 8.1, and Windows Server 2012, command prompts should be opened with Administrator privileges.
If you need to perform multiple installations of Oracle Database Client, you may want to use silent or response file mode, with response files. In these modes, at each computer, you run Oracle Universal Installer from the command line using a response file. The response file is a text file containing the settings you normally enter in the Oracle Universal Installer GUI dialog boxes. This method lets you quickly perform multiple installations using similar settings for each computer.
See Also:Appendix B, "Installing Oracle Database Client Using Response Files" for instructions on performing silent or response file mode installations
If you install Oracle Database Client on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, one or more Oracle base directories already exist. In the latter case, Oracle Universal Installer offers you a choice of Oracle base directories into which you can install Oracle Database Client.
You are not required to create an Oracle base directory before installation, but you can do so if you want.
Note:You can choose to create a new Oracle base directory, even if other Oracle base directories exist on the system.
You can install all Oracle components in multiple Oracle homes on the same computer. However, some components can only support one active instance at a time. This means that the current (latest) installation renders the previous one inactive. These components are:
Note:Oracle Objects for OLE is not supported on Windows x64.
Oracle Database Client can be installed in the same Oracle Database home if both products are at the same release level. For example, you can install Oracle Database Client 10g Release 2 (10.2) into an existing Oracle Database 10g Release 2 (10.2) home. If you apply a patch set before installing the client, then you must apply the patch set again. Oracle Universal Installer will prompt you for an Oracle home directory, whether you have other Oracle software installed on the computer or not. You cannot install products from one release of Oracle Database Client into an Oracle home directory of a different release. For example, you cannot install Oracle Database 11g release 1 (11.1) software into an existing Oracle9i Oracle home directory.
You can install this release more than once on the same system as long as each installation is installed in a separate Oracle home directory.
Use the In-Place Upgrade feature to upgrade an existing client installation to the latest release by installing the new client software into an existing client home with the same installation type. For example, if release 188.8.131.52 is installed, then use Oracle Universal Installer to upgrade to release 22.214.171.124.
Consider the following before selecting this option:
This upgrade is only possible in a client home and not in any other Oracle home that contains non-client installations, such as Database installations.
This upgrade does not delete files in the client home that are commonly updated by other users. For example, configuration data files.
This upgrade cannot be performed if processes associated with the Oracle Database Client home are running.
This functionality is available starting with Oracle Database 11g Release 2 (184.108.40.206).
The Oracle Database Client software is available on installation media or you can download it from the Oracle Technology Network (OTN) Web site, or Oracle Software Delivery Cloud Web site. To install the software from the hard disk, you must either download it and unpack it, or copy it from the installation media, if you have it.
You can access and install Oracle Database Client by using the following scenarios:
Installing on Remote Computers Through Remote Access Software
If the computer where you want to install Oracle Database Client does not have a DVD drive, you can perform the installation from a remote DVD drive. You must complete the following steps:
The remote DVD drive that you want to use must allow shared access. To set this up, perform these steps on the remote computer that has the DVD drive:
Log in to the remote computer as an Administrator user.
Start Windows Explorer.
Right-click the DVD drive letter and choose Sharing (or Sharing and Security).
Click the Sharing tab and do the following:
Select Share this folder.
In Share name, give it a share name such as
dvd. You will use this name when you map the DVD drive on the local computer in step d of the next section.
Click Permissions. You need at least "read" permission for the user who will be accessing it to install Oracle Database.
Click OK when you are finished.
Insert the DVD labeled Oracle Database 11g Release 2 (11.2) into the DVD drive.
Perform these steps on the local computer to map a remote DVD drive and to run Oracle Universal Installer from the mapped drive:
Map the remote DVD drive.
Start Windows Explorer on the local computer.
From the Tools menu, select Map Network Drive to display the Map Network Drive dialog.
Select a drive letter to use for the remote DVD drive.
In Folder, enter the location of the remote DVD drive using the following format:
remote_hostname is the name of the remote computer with the DVD drive.
share_name is the share name that you entered in step 4 of the previous procedure. For example
If you need to connect to the remote computer as a different user, click different user name, and enter the username.
Click Finish.
Run Oracle Universal Installer from the mapped DVD drive.
Go to the "Installing the Oracle Database Client Software" section.
If you want to install and run Oracle Database Client on a remote computer (that is, the remote computer has the hard drive and will run Oracle Database Client components), but you do not have physical access to the computer, you still can perform the installation on the remote computer if it is running remote access software such as VNC or Symantec pcAnywhere. You also need the remote access software running on your local computer.
You can install Oracle Database Client on the remote computer in one of two ways:
If you have copied the contents of the Oracle Database Client DVD to a hard drive, you can install from the hard drive.
You can insert the DVD into a drive on your local computer, and install from the DVD.
If you have copied the contents of the Oracle Database Client DVD to a hard drive, you can install from the hard drive.
The steps that must complete are:
Make sure that the remote access software is installed and running on the remote and local computers.
Share the hard drive that contains the Oracle Database Client DVD.
On the remote computer, map a drive letter to the shared hard drive. You would use the remote access software to do this on the remote computer.
Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared hard drive.
Go to the "Installing the Oracle Database Client Software" section.
You can insert the DVD into a drive on your local computer, and install from the DVD.
The steps that you need to complete are:
Make sure that the remote access software is installed and running on the remote and local computers.
On the local computer, share the DVD drive.
On the remote computer, map a drive letter to the shared DVD drive. You would use the remote access software to do this on the remote computer.
These steps are described in the "Installing from a Remote DVD Drive" section.
Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared DVD drive.
Go to Section 3.3, "Installing the Oracle Database Client Software."
You can download the trial version of the installation files from the Oracle Technology Network (OTN) or Oracle Software Delivery Cloud Web site and extract them on your hard disk. Make sure that you completely review and understand the terms of the license. Most downloads include the Development License. This section contains the following topics:
Downloading the Software from Oracle Software Delivery Cloud
To download the installation archive files from Oracle Technology Network:
Use any browser to access the software download page from Oracle Technology Network:
Navigate to the download page for the product that you want to install.
On the download page, identify the required disk space by adding the file sizes for each required file.
The file sizes are listed next to the filenames.
Select a file system with enough free space to store and expand the archive files.
In most cases, the available disk space must be at least twice the size of all the archive files.
On the file system that you selected in step 4, create a parent directory for each product, for example
OraDBClient11g, to hold the installation directories.
Download all of the installation archive files to the directories that you created in step 5.
Verify that the files you downloaded are the same size as the corresponding files on Oracle Technology Network. Also verify the checksums are the same as noted on Oracle Technology Network.
Extract the files in each directory that you just created.
After you have extracted the required installation files, see the "Installing the Oracle Database Client Software" section.
You can download the software from Oracle Software Delivery Cloud as Media Packs. A Media Pack is an electronic version of the software that is also available to Oracle customers on CD-ROM or DVD. To download the Media Pack:
Use any browser to access the Oracle Software Delivery Cloud Web site:
Complete the Export Validation process by entering information (name, company, e-mail address, and country) in the online form.
In the Media Pack Search page, specify the Product Pack and Platform to identify the Media Pack you want to download. If you do not know the name of the Product Pack, you can search for it using the License List.
Optionally, select the relevant product to download from the Results list.
In the search results page, click Readme to download and review the Readme file for download instructions and product information.
After you review the Readme, choose the appropriate Media Pack from the search results to download the individual zip files. Follow the Download Notes instructions in this page. Once you download and extract the contents of the required zip files, proceed with the installation of the software.
Note:Print the page with the list of downloadable files. It contains a list of part numbers and their corresponding descriptions that you may need to refer during the installation process.
After you download the files, click View Digest to verify that the MD5 or SHA-1 checksum matches with what is listed in the media download page.
See Also:
To extract the installation archive files, perform the following steps:
If necessary, change to the directory that contains the downloaded installation archive files.
The Oracle Database software is available as a zip file. Ensure that you extract the zip file to the same directory.
When you have extracted all of the required installation files, see "Installing the Oracle Database Client Software" section .
To copy the contents of the media to a hard disk:
Create a directory for the installation files on your hard drive. For example:
Copy the contents of the installation media to the directory that you just created.
When you have copied the required installation files, see the "Installing the Oracle Database Client Software" section.
This section covers the following topics:
In most cases, you use the graphical user interface (GUI) provided by Oracle Universal Installer to install Oracle Database Client. However, you can also use Oracle Universal Installer to complete silent installations using a response file, without using the GUI. This method is particularly useful if you need to perform multiple installations of Oracle Database Client.
As you install Oracle Database Client, follow these guidelines:
See Also:Appendix B, "Installing Oracle Database Client Using Response Files" for information about silent or response file mode installations
Do not use Oracle Universal Installer from an earlier Oracle product release to install components from this release.
Use the same installation media to install Oracle Database Client on all supported Windows platforms.
If you reinstall Oracle software into an Oracle home directory where Oracle Database Client is already installed, you must reinstall any components that were installed before you began the reinstallation.
Do not modify the Java Runtime Environment (JRE) except by using a patch provided by Oracle Support Services. Oracle Universal Installer automatically installs the Oracle-supplied version of the JRE. This version is required to run Oracle Universal Installer and several Oracle assistants.
If you encounter errors during installation, click Help or see Appendix D, "Troubleshooting the Oracle Database Client Installation" for advice.
Products not installed by default, in case of Custom installation:
Oracle Connection Manager
Oracle Net Listener
Oracle Scheduler Agent
Oracle Services for Microsoft Transaction Server
Oracle Counters for Windows Performance Monitor
Use Oracle Universal Installer to install the Oracle Database Client software.
To install Oracle Database Client perform the following steps:
Log on as a member of the Administrators group to the computer to install Oracle components.
If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.
Insert the Oracle Database Client installation media and navigate to the
client directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
Use the same installation media to install Oracle Database on all supported Windows platforms.
setup.exe to start Oracle Universal Installer.
Starting with Oracle Database 11g Release 2 (184.108.40.206), if you plan to run the installation in a secured data center, then you can download updates before starting the installation by starting Oracle Universal Installer on a system that has Internet access in update download mode. To start Oracle Universal Installer to download updates, enter the following command:
./setup.exe -downloadUpdates
Provide the My Oracle Support user name and password, and provide proxy settings if needed on the Provide My Oracle Support credentials screen. Then, enter the Download location and click Download on the Download software updates screen. If updates are available, then they are downloaded in the location provided. The Finish Updates screen shows the successful download of the updates. Click Close.
After you download updates, transfer the update file to a directory on the server where you plan to run the installation.
See Also:
If you have an existing Oracle Database Client 11g Release 2 (11.2) installed on your system, the Select Installation Mode screen is displayed. Select New Install to install Oracle Database Client software in to a new location.
Starting with Oracle Database 11g Release 2 (220.127.116.11), if you want to upgrade an earlier release of Oracle Database Client, then select Upgrade and follow the instructions in "Performing an In-place Oracle Database Client Upgrade"
In the Select Installation Type screen, select the type of installation that you want: Instant Client, Administrator, Runtime, or Custom and click Next.
Starting with Oracle Database 11g Release 2 (18.104.22.168), you can use the Software Updates feature to dynamically download and apply latest updates. In the Download Software Updates screen, select one of the following options, and click Next:
Use My Oracle Support credentials for download to download and apply the latest software updates.
Click Proxy Settings to configure a proxy for Oracle Universal Installer to use to connect to the Internet. Provide the proxy server information for your site, along with a user account that has access to the local area network through which the server is connecting. Starting with Oracle Database 11g Release 2 (184.108.40.206), you can enter the Proxy Realm information. The proxy realm information is case-sensitive. If you do not have a proxy realm, then you do not need to provide an entry for the Proxy Username, Proxy Password, and Proxy Realm fields.
Click Test Connection to ensure that your proxy settings are correctly entered, and the installer can download the updates.
Use pre-downloaded software updates to apply previously downloaded software updates.
Skip software updates if you do not want to apply any updates.
See Also:"Software Updates Option"
The Apply Software Updates screen is displayed if you select to download the software updates or provide the pre-downloaded software downloads location. If you selected Use My Oracle Support credentials for download in the previous screen, then select Download and apply all updates, and click Next. If you selected Use pre-downloaded software updates, then select Apply all updates, and click Next.
The Select Product Languages screen enables you to select the language in which you want to run the product.
Select the product language from the Available Languages list, transfer it to the Selected Languages list. Click Next.
This screen is not displayed if you select Instant Client as the type of installation in step 5.
In the Specify Installation Location screen, enter the following details:
Oracle Base: This path appears by default. You can change the path based on your requirement.
The Oracle Base section is not displayed if you select Instant Client as the type of installation in step 5.
In the Software Location section, accept the default value or enter the Oracle home directory path in which you want to install Oracle components. The directory path should not contain spaces. Click Next.
If you selected Custom as the type of installation in step 5, then the Available Product Components screen is displayed. Select the products that you want to install and click Next.
Note:Starting with Oracle Database 11g Release 2 (11.2), you can install Oracle Connection Manager, Oracle Net Listener, and Oracle Scheduler Agent using the Custom install option.
In step 10, if you select Oracle Scheduler Agent as one of the components that you want to install, then the Oracle Database Scheduler Agent screen is displayed. The Scheduler Agent Host Name, and the Scheduler Agent Port Number is displayed by default. Click Next.
The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product. Click Next.
Note:Oracle recommends that you use caution in checking the Ignore All option. If you check this option, then Oracle Universal Installer may not confirm that your system is able to install Oracle Database successfully.
Review the information displayed in the Summary screen, and click Install.
Note:Starting with Oracle Database 11g Release 2 (11.2), you can save all the installation steps into a response file by clicking Save Response File. Later, this file can be used for a silent installation.
The Install Product screen shows the progress of a client installation. After Oracle Database Client is installed, click OK.
If you are performing a Custom installation, and selected Oracle Net Listener from the list of components to install in step 10, then go to "Using Oracle Net Configuration Assistant" for instructions.
In the Finish screen, click Close to exit Oracle Universal Installer.
Using Oracle Net Configuration Assistant
During a Custom Oracle Database Client installation, if you select Oracle Net Listener from the list of components to install in step 10, then Oracle Universal Installer automatically starts Oracle Net Configuration Assistant as part of the Oracle Database Client installation. Perform the following to configure the listener and naming methods using Oracle Net Configuration Assistant:
In the Welcome screen, click Next.
In the Listener Configuration screen, enter a Listener name or accept the default value. Click Next.
In the Listener Configuration, Select Protocol screen, select one or more protocols from the Available Protocols list, and move it to the Selected Protocols list. Click Next.
In the Listener Configuration, TCP/IP Protocol screen, select the standard port number, or enter a different port number. Click Next.
Select No if you do not want to configure an additional listener, and click Next.
The listener configuration is now complete, click Next to proceed.
In the Naming Methods Configuration screen, select Yes to configure naming methods. Click Next.
In the Naming Methods Configuration screen, select the naming method you want from the list of Available Naming Methods and then click Next.
Typically, Local Naming is sufficient.
In the Net Service Name Configuration screen, enter Service Name, and click Next.
In the Net Service Name Configuration screen, select the protocol for the database you want to access, and click Next.
In the Net Service Name Configuration screen, enter the Host name of the computer where the Oracle database is installed. Use the standard port number, or specify a different port number, and click Next.
In the Net Service Name Configuration, Test screen, click Yes to test the database connection. Click Next.
In most cases, the test fails only because the default user name and password Oracle Universal Installer supplies in the dialog box do not match the user name and password for the target database. Click Change Login, reenter the user name and password, and then click OK.
In the Connecting screen, click Next.
In the Net Service Name screen, enter the name of the Net Service Name, and click Next.
Answer the remaining prompts to complete the configuration.
In the Finish screen, click Close, to exit from Oracle Universal Installer.
You can also run Oracle Net Configuration Assistant after the installation in standalone mode to configure the listener, naming methods, net service names, and directory server usage.
To start Oracle Net Configuration Assistant in standalone mode, select Programs from the Start menu, and then select Oracle -
HOME_NAME. Next, select Configuration and Migration Tools, and then Oracle Net Configuration Assistant.
See Also:"Using Oracle Net Configuration Assistant to Configure Network Components" in Oracle Database Net Services Administrator's Guide
Starting with Oracle Database 11g Release 2 (188.8.131.52) you can perform an in-place upgrade of Oracle Database Client 11g Release 2 (11.2) using the following instructions:
Note:You can perform an in-place Oracle Database Client upgrade only if you have an existing Oracle Database Client 11g Release 2 (22.214.171.124) or later client home installed on your system.
Perform Steps 1 through 3 listed in "Procedure for Installing Oracle Database Client".
The Select Installation Mode screen is displayed only if you have an existing Oracle Database Client 11g Release 2 (220.127.116.11) or later installed on your system, . Select Upgrade to upgrade the existing Oracle Database Client software to the latest version.
In the Specify Installation Location screen, accept the default Software Location value or enter the Oracle home directory path in which you want to install Oracle components. The directory path should not contain spaces. Click Next.
In the Download Software Updates screen, select one of the following options, and click Next:
Use My Oracle Support credentials for download
Use pre-downloaded software updates
Skip software updates
See Step 6 in "Procedure for Installing Oracle Database Client" for more information about the options in the Download Software Updates screen.
The Apply Software Updates screen is displayed if you select to download the software updates or provide the pre-downloaded software updates location. Select either Download and apply all updates or Apply all updates, as applicable, and click Next.
See Step 7 in "Procedure for Installing Oracle Database Client" for more information about the options in the Apply Software Updates screen.
The Select Product Languages screen enables you to select the language in which you want to run the product.
Select the product language from the Available Languages list, transfer it to the Selected Languages list. Click Next.
The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product. Click Next.
Review the information displayed in the Summary screen, and click Install.
The Install Product screen displays the progress of the client upgrade.
Review the information in the Finish screen and click Close to exit Oracle Universal Installer.
This appendix contains the following information about troubleshooting:
Before you try any of the troubleshooting steps in this appendix, do the following:
Check that the system meets the requirements and that you have completed all of the preinstallation tasks specified in Chapter 2, "Oracle Database Client Preinstallation Requirements."
Read the release notes for the product on your platform before installing it.You can find the latest version of the release notes on the Oracle Technology Network Web site:
If you encounter an error during installation:
Do not exit Oracle Universal Installer.
If you clicked Next after you entered incorrect information about one of the installation windows, click Back to return to the window and correct the information.
If you encounter an error while Oracle Universal Installer is copying or linking files, then see "Reviewing the Log of an Installation Session" for interactive installations or "Silent-Mode Response File Error Handling" for silent or response file mode installations.
If you encounter an error while configuration assistant is running, then see Section D.5, "Troubleshooting Configuration Assistants."
If you cannot resolve the problem, then remove the failed installation by following the steps listed in Section D.7, "Cleaning Up After a Failed Installation."
When you run Oracle Universal Installer on a computer with no Oracle software installed, it creates a directory called:
DRIVE_LETTER:\Program Files\Oracle\Inventory\logs
During this first installation and all subsequent installations, Oracle Universal Installer saves all of the actions that it performs in a log file in this directory. If you encounter problems during the installation, review the log file for information about possible causes of the problem.
Log filenames for interactive installations take the form:
installActionsdate_time.log oraInstalldate_time.err oraInstalldate_time.out
For example, if an interactive installation occurred at 9:00:56 A.M. on February 14, 2005, the log file would be named:
Note:Do not delete or manually alter the
Inventory directory or its contents. Doing so can prevent Oracle Universal Installer from locating products that you install on your system.
To determine whether a silent or response file mode installation succeeds or fails, check the
.log file, located in the
:\Program Files\Oracle\Inventory\logs directory.
A silent installation fails if:
You do not specify a response file.
You specify an incorrect or incomplete response file.
Oracle Universal Installer encounters an error, such as insufficient disk space.
Oracle Universal Installer or a configuration assistant validates the response file at run time. If the validation fails, the installation or configuration process ends.
See Also:"Reviewing the Log of an Installation Session" for information about interactive installation log files
To troubleshoot an installation error that occurs when a configuration assistant is running:
Review the installation log files listed in Section D.3, "Reviewing the Log of an Installation Session."
Review the specific configuration assistant log file located in the
\cfgtoollogs directory. Try to fix the issue that caused the error.
If you see the
Fatal Error. Reinstall message, look for the cause of the problem by reviewing the log files. Refer to "Irrecoverable Errors" for further instructions.
Oracle configuration assistant failures are noted at the bottom of the installation window. The configuration assistant interface displays additional information, if available. The configuration assistant execution status is stored in the
.log file.
The execution status codes are listed in the following table:
|Result Code
|Configuration assistant succeeded
|Configuration assistant failed
|Configuration assistant canceled
If you receive an irrecoverable error while a configuration assistant is running:
Remove the failed installation as described in Section D.7, "Cleaning Up After a Failed Installation."
Correct the cause of the irreoverable error.
Reinstall the Oracle software.
If you face any of the following situations for Oracle home, then run the
opatch lsinventory -detail command to list the contents of the inventory and see section "Recovering from inventory corruption" in the Oracle Universal Installer and OPatch User's Guide for information about fixing the issue.
Oracle home is cloned without completing the inventory steps.
There is bad inventory.
Inventory is not available but it is created when the Oracle Enterprise Manager Agent is installed in a separate Oracle home.
If an installation fails, you must remove files that Oracle Universal Installer created during the attempted installation and remove the Oracle home directory. Follow the instructions in Chapter 5, "Removing Oracle Database Client Software" to run the Deinstallation tool.


text:
More than just what happened and why: From the History and Philosophy of Science to Applied Ethics and Religion, our courses connect across the OSU campus providing a broad perspective and a unique insight into the issues facing our world. Our students and faculty research on and collaborate with a wide array of disciplines from Oceanography to Nuclear Engineering - from Music to Environmental Science. Our school provides students with a series of lenses though which they can examine the universe and their place in it.
Montpellier surgeon Barthélémy Cabrol (1529-1603) first published his Alphabet anatomic in 1594. A series of tables that graphically represented the parts of the body, it was immensely popular, with eleven editions in the seventeenth century as well as translations into … Continue reading
The post A Sonnet for Anatomist Barthélémy Cabrol appeared first on School of History, Philosophy, and Religion.Read full story.
by Joshua McGuffie With summer drawing to a close, I took the opportunity to ride the Amtrak Coast Starlight from Albany, Oregon to Union Station in Los Angeles. I'd never taken the train for such a long trip, 28 hours each way. On such a long trip landscapes pass by, fixed in their space but… Continue reading
The post Environmental History on the Rails appeared first on History of Science at Oregon State University.Read full story.
After editing a couple of dozen H-Environment roundtables himself, it is great to have one of Jake Hamblin's own books, Arming Mother Nature, as the subject of one – this time guest-edited by Michael Egan of McMaster University. You can … Continue reading
The post Roundtable on 'Arming Mother Nature' appeared first on School of History, Philosophy, and Religion.Read full story.
Laws of nature, historical contingency, and the wolves and moose of Isle Royale
Dr. John A. Vucetich
Associate Professor of Animal Ecology
Co-Director of the Isle Royale Wolf-Moose Project
Michigan Technological University

subset: commoncrawl


text:
Julie Packard
Julie Packard Executive Director, Monterey Bay Aquarium
I eat fish. I do. It's interesting. Many of my colleagues that work in ocean conservation don't. Everyone has a different take on that question of eating fish. I believe, I guess, I'm a believer in progress, not perfection.
Working at the aquarium here, we really see our role to be accessible. People come into our institution from all walks of life. They're not coming here because they're hardcore conservation advocates. They're coming here for a fun family outing for the day. We have people of all political persuasions, faith persuasions, you name it, and so we work on a message that's accessible and approachable, and we don't want to be sounding too rabid about things.
I've kind of adopted that at a personal level, as well. I mean, it is true that we're eating wildlife. Fish is the last commercially-harvested wildlife that humanity still has the enterprise on, which is interesting. Many of the others, we drove to extinction or virtual through the market hunts for birds in the early part of the history of our country, or we can look at the buffalo, obviously. But when it comes to fish, I do believe that, harvested in the right way and the right level, there's a way that we can have seafood be part of our diet.
I view the important -- my role and the role of our institution is to really get people to think about the seafood they're eating and use their consumer power to drive change in how fish is globally caught and farmed.
How can I help with conservation efforts?
Answered by Planet Green
What happens if Earth's coral reefs disappear?
Answered by Sylvia Earle
What are some of the benefits of saving endangered species?
Answered by Planet Green


text:
The folks from careers are running some resume writing workshops for the on-campus crew, here are the details:
Come, book into the RESUME WORKSHOP session the Careers staff are running, held in the Learning Commons, Dixon Library at midday, every second Wednesday in June. The seminar provides you with how to write a professional resume. This session is vital for students who are looking for work or looking for some work experience.
To book drop in and see Rosina at Student Assist or phone 02 6773 2897.