PK
;7Aoa, mimetypeapplication/epub+zipPK ;7A iTunesMetadata.plistR
This chapter describes how to completely remove Oracle software and configuration files related to the specified Oracle home. It includes information about removing Oracle software using the deinstallation tool.
The deinstall
command removes standalone Oracle Database installations, Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) from your server, and also Oracle Real Application Clusters (Oracle RAC) and Oracle Database client installations.
Starting with Oracle Database 11g Release 2 (11.2), Oracle recommends that you use the deinstallation tool to remove the entire Oracle home associated with the Oracle Database, Oracle Clusterware, Oracle ASM, Oracle RAC, or Oracle Database client installation. Oracle does not support the removal of individual products or components.
The following sections describe the deinstall
command, and provide information about additional options to use the command:
Downloading the Deinstallation Tool for Use with Failed Installations
Deinstallation Parameter File Example for Oracle Grid Infrastructure
Caution: If you have a standalone database on a node in a cluster and you have multiple databases with the same global database name (GDN), then you cannot use the deinstall tool to remove one database only. |
See Also:
|
The deinstallation tool (deinstall
) is available in the installation media before installation, and is available in Oracle home directories after installation. It is located in the $ORACLE_HOME/deinstall
directory.
The deinstall
command uses the information you provide, plus information gathered from the software home to create a parameter file. You can alternatively supply a parameter file generated previously by the deinstall
command using the –checkonly
option, or by editing the response file template.
The deinstallation tool stops Oracle software, and removes Oracle software and configuration files on the operating system for a specific Oracle home. If you run the deinstallation tool to remove an Oracle Grid Infrastructure for a standalone server, then the deinstaller prompts you to run the roothas.pl
script, as the root
user, to deconfigure Oracle Restart.
Caution: When you run thedeinstall command, if the central inventory (oraInventory) contains no other registered homes besides the home that you are deconfiguring and removing, then the deinstall command removes the following files and directory contents in the Oracle base directory of the Oracle Database installation owner:
Oracle strongly recommends that you configure your installations using an Optimal Flexible Architecture (OFA) configuration, and that you reserve Oracle base and Oracle home paths for exclusive use of Oracle software. If you have any user data in these locations in the Oracle base that is owned by the user account that owns the Oracle software, then the |
The deinstall
command uses the following syntax, where variable content is indicated in italics:
deinstall -home complete path of Oracle home [-silent] [-checkonly] [-local] [-cleanupObase] [-paramfile complete path of input parameter property file] [-params name1=value name2=value . . .] [-o complete path of directory for saving files] [-help]
The default method for running the deinstallation tool is from the deinstall directory in the Oracle home as the installation owner:
$ $ORACLE_HOME/deinstall/deinstall
Provide information about your servers as prompted or accept the defaults.
The deinstall
command stops Oracle software, and removes Oracle software and configuration files on the operating system.
In addition, you can run the deinstallation tool from other locations, or with a parameter file, or select other options to run the tool.
The options are:
-home
Use this flag to indicate the home path of the Oracle home to check or deinstall. To deinstall Oracle software using the deinstall
command in the Oracle home you plan to deinstall, provide a parameter file in another location, and do not use the -home
flag.
If you run deinstall
from the $ORACLE_HOME/deinstall
path, then the -home
flag is not required because the tool knows from which home it is being run. If you use the standalone version of the tool, then -home
is mandatory.
-silent
Use this flag to run the command in silent or response file mode. If you use the -silent
flag, then you must use the -paramfile
flag, and provide a parameter file that contains the configuration values for the Oracle home to deinstall or deconfigure.
You can generate a parameter file to use or modify by running deinstall
with the -checkonly
flag. The deinstall
command then discovers information from the Oracle home to deinstall and deconfigure. It generates the properties file, which you can then use with the -silent
option.
You can also modify the template file deinstall.rsp.tmpl
, located in the $ORACLE_HOME/deinstall/response
folder.
-checkonly
Use this flag to check the status of the Oracle software home configuration. Running the deinstall
command with the -checkonly
flag does not remove the Oracle configuration. The -checkonly
flag generates a parameter file which you can then use with the deinstall
command and the -silent
option.
-local
Use this flag on a multinode environment to deinstall Oracle software in a cluster.
When you run deinstall
with this flag, it deconfigures and deinstalls the Oracle software on the local node (the node where deinstall
is run). On remote nodes, it deconfigures Oracle software, but does not deinstall the Oracle software.
-cleanupOBase
Use this flag to force the removal of all the contents in the Oracle base directory, including the admin
, oradata,
and flash_recovery_area
directories. This flag forces an Oracle base removal only if the Oracle home that you specify with the -home
flag is the only Oracle home associated with the Oracle base directory. You must Use the -cleanupOBase
flag to force an Oracle base removal for both command-line interface deinstall and response file mode deinstall.
This flag is available with the deconfig tool available in the Oracle Grid Infrastructure and Oracle Database 11.2.0.3 patch release, and from Oracle Technology Network (OTN).
-paramfile
complete path of input parameter property file
Use this flag to run deinstall
with a parameter file in a location other than the default. When you use this flag, provide the complete path where the parameter file is located.
The default location of the parameter file depends on the location of deinstall
:
From the installation media or stage location: $ORACLE_HOME/inventory/response
From a unzipped archive file from OTN: /
ziplocation
/response
After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response
-params
[name1
=value
name 2
=value
name3
=value
. . .]
Use this flag with a parameter file to override one or more values to change in a parameter file you have created.
-o
complete path of directory for saving response files
Use this flag to provide a path other than the default location where the properties file (deinstall.rsp.tmpl
) is saved.
The default location of the parameter file depends on the location of deinstall
:
From the installation media or stage location before installation: $ORACLE_HOME/
From a unzipped archive file from OTN: /
ziplocation
/response/
After installation from the installed Oracle home: $ORACLE_HOME/deinstall/response
-help
Use the help option (-help
) to get additional information about the command option flags.
Deinstalling Previous Release Grid Home
For upgrades from previous releases, if you want to deinstall the previous release Grid home, then as the root
user, you must manually change the permissions of the previous release Grid home, and then run the deinstall command.
For example:
# chown -R grid:oinstall /u01/app/grid/11.2.0 # chmod -R 775 /u01/app/grid/11.2.0
In this example, /u01/app/grid/11.2.0
is the previous release Grid home.
If you require the deinstallation tool (deinstall
) to remove failed or incomplete installations, then it is available as a separate download from the Oracle Technology Network (OTN) Web site.
To download the deinstallation tool:
Go to the following URL:
http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
Under Oracle Database 11g Release 2, click See All for the respective platform for which you want to download the deinstallation tool.
The deinstallation tool is available for download at the end of this Web page.
As the deinstall
command runs, you are prompted to provide the home directory of the Oracle software to remove from your system. Provide additional information as prompted.
Use the optional flag -paramfile
to provide a path to a parameter file.
In the following example, the deinstall
command is in the path /u01/app/oracle/product/11.2.0/dbhome_1/deinstall
, and it uses a parameter file in the software owner location /home/usr/oracle
:
$ cd /u01/app/oracle/product/11.2.0/dbhome_1/deinstall $ ./deinstall -paramfile /home/usr/oracle/my_db_paramfile.tmpl
For the Oracle Grid Infrastructure home, use the deinstallation script in the Oracle Grid Infrastructure for a standalone server home, which in this example is /u01/app/oracle/product/11.2.0/grid
:
$ cd /u01/app/oracle/product/11.2.0/grid/deinstall $ ./deinstall -paramfile /home/usr/oracle/my_grid_paramfile.tmpl
If you enter the deinstall
command outside of the $ORACLE_HOME/deinstall
folder, then help is displayed, unless you enter a -home
flag and provide a path. If you run the deinstall
command from the $ORACLE_HOME/deinstall
folder, then deinstallation starts without prompting you for a home address.
You can run the deinstall
command on a standalone Oracle Database with the -paramfile
option to use the values you specify in the parameter file. The following is an example of a parameter file, in which the Oracle Database binary owner is oracle
, the Oracle Database home (Oracle home) is in the path /u01/app/oracle/product/11.2.0/dbhome_1/
, the Oracle base (where other Oracle software is installed) is /u01/app/oracle/
, the central Oracle Inventory home (oraInventory) is /u01/app/oraInventory
, the virtual IP address (VIP) is 192.0.2.1
, the local node (the node where you run the deinstallation session from) is myserver
, and the OSDBA group is dba
:
#Copyright (c) 2005, 2006 Oracle Corporation. All rights reserved. #Mon Feb 16 06:48:39 UTC 2009 DISK_GROUPS.sidb= ASM_HOME= ASM_LOCAL_SID= LOGDIR=/u01/app/oracle/product/11.2.0/dbhome_1/oraInventory/logs/ ORACLE_BASE.sidb=/u01/app/oracle/ RECOVERY_LOC.sidb= STORAGE_TYPE.sidb=FS ORACLE_BASE=/u01/app/oracle/ INVENTORY_LOCATION=/u01/app/oraInventory DB_TYPE.sidb=SI_DB NODE_LIST.sidb=myserver ARCHIVE_LOG_DESTINATION_LOC.sidb= LOCAL_SID.sidb=sidb DB_UNIQUE_NAME_LIST=sidb ASM_FILES.sidb= HOME_TYPE=SIDB CRS_HOME=false RAW_MAPPING_FILE.sidb= SID_LIST.sidb=sidb ORACLE_BINARY_OK=true DATAFILE_LOC.sidb=/u01/app/oracle/oradata local=false LOCAL_NODE=myserver CREATION_MODE.sidb=y CONFIGFILE_LOC.sidb= DIAG_DEST.sidb=/u01/app/oracle/ silent=false ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1/ SPFILE_LOC.sidb=
You can run the deinstall
command on an Oracle Grid Infrastructure for a standalone server home with the -paramfile
option to use the values you specify in the parameter file.
The following is an example of a parameter file, in which the Oracle Grid Infrastructure binary owner is oracle
, the Oracle Grid Infrastructure home is in the path /u01/app/oracle/product/11.2.0/grid
, the Oracle base (where other Oracle software is installed) is /u01/app/oracle/
, the central Oracle Inventory home (oraInventory) is /u01/app/oraInventory
, the local node (the node where you run the deinstallation session from) is myserver
, and the OSDBA group is dba
:
#Copyright (c) 2005, 2009 Oracle Corporation. All rights reserved. #Thu Mar 05 11:36:03 PST 2009 LOCAL_NODE=myserver HOME_TYPE=SIHA ASM_REDUNDANCY=EXTERNAL ORACLE_BASE=/u01/app/oracle/ SCAN_PORT=0 silent=false ASM_UPGRADE=false ORA_CRS_HOME=/u01/app/oracle/product/11.2.0/grid GPNPCONFIGDIR=$ORACLE_HOME LOGDIR=/home/oracle/tmp/deinstall/logs/ ASM_DISCOVERY_STRING=/u02/stor/asm* GPNPGCONFIGDIR=$ORACLE_HOME ORACLE_OWNER=oracle ASM_DISKSTRING= CRS_STORAGE_OPTION=0 ORACLE_BINARY_OK=true OCR_VOTINGDISK_IN_ASM=false ASM_ORACLE_BASE=/u01/app/oracle NETCFGJAR_NAME=netcfg.jar ORA_DBA_GROUP=dba JREDIR=/u01/app/oracle/grid/jdk/jre/ ORA_ASM_GROUP=dba LANGUAGE_ID='AMERICAN_AMERICA.WE8ISO8859P1' CSS_LEASEDURATION=400 ASM_HOME=/u01/app/oracle/grid SHAREJAR_NAME=share.jar HELPJAR_NAME=help4.jar SILENT=false local=false INVENTORY_LOCATION=/u01/app/oraInventory GNS_CONF=false JEWTJAR_NAME=jewt4.jar EMBASEJAR_NAME=oemlt.jar ASM_DISKS=/u02/stor/asm/asm0,/u02/stor/asm/asm2,/u02/stor/asm/asm3,/u02/stor/asm/asm1,/u02/stor/asm/asm4,/u02/stor/asm/asm5,/u02/stor/asm/asm6, /u02/stor/asm/asm7,/u02/stor/asm/asm8 ORACLE_HOME=/u01/app/oracle/grid CRS_HOME=true ASM_IN_HOME=true EWTJAR_NAME=ewt3.jar ASM_DROP_DISKGROUPS=false ASM_LOCAL_SID=+ASM JLIBDIR=/u01/app/oracle/grid/jlib VNDR_CLUSTER=false ASM_DISK_GROUP=DATA
This section describes new features that are documented in this guide and provides pointers to additional information.
Starting with Oracle Database 11g Release 2 (11.2.0.3) you can enter the Proxy Realm information when providing the details for downloading software updates. The proxy realm identifies the security database used for authentication. If you do not have a proxy realm, then you do not have to provide an entry for the Proxy Username, Proxy Password, and Proxy Realm fields. It is case-sensitive.
This proxy realm is for software updates download only.
The following is a list of new features or enhancements provided with Oracle Database 11g Release 2 (11.2.0.2):
Starting with the release of the 11.2.0.2 patch set for Oracle Database 11g Release 2, Oracle Database patch sets are full installations of the Oracle Database software. Note the following changes with the new patch set packaging:
Direct upgrades from previous releases (11.x, 10.x) to the most recent patch set are supported.
Out-of-place patch set upgrades, in which you install the patch set into a new, separate Oracle home, are the best practices recommendation. In-place upgrades are supported but are not recommended.
New installations consist of installing the most recent patch set, rather than installing a base release and then upgrading to a patch release.
See Also: My Oracle Support note 1189783.1, "Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2", available from the following URL:
|
This functionality is available starting with Oracle Database 11g Release 2 (11.2.0.2). Use the Software Updates feature to dynamically download and apply software updates as part of the Oracle Database installation. 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.
This functionality is available starting with Oracle Database 11g Release 2 (11.2.0.2). Use the In-Place Upgrade feature of Oracle Database Client to upgrade an existing Oracle Database Client 11g Release 2 (11.2) version with the latest Oracle Database Client version.
See Also: Oracle Database Client Installation Guide for Linux for more information about In-Place Upgrade |
Transparent Data Encryption (TDE) can automatically detect whether the database host system includes specialized cryptographic silicon that accelerates the encryption or decryption processing. When detected, TDE uses the specialized silicon for cryptographic processing accelerating the overall cryptographic performance significantly.
Starting with Oracle Database 11g Release 2 (11.2.0.2), cryptographic hardware acceleration for TDE is available on Intel Xeon with AES-NI, and for Linux x86 and Linux X86-64 on Oracle Linux 5 and Red Hat Enterprise Linux 5.
The following is a list of new features or enhancements provided with Oracle Database 11g Release 2 (11.2.0.1):
Oracle Database 11g Release 2 introduces the Oracle Grid Infrastructure installation. For single instance databases, Oracle Grid Infrastructure includes Oracle Automatic Storage Management (Oracle ASM), the listener, and Oracle Restart. Oracle Restart is a new feature that provides the ability to monitor, manage, and automatically restart if the Oracle Database environment including the Oracle Database instance, Oracle Automatic Storage Management instance, and listeners fails. In a clustered environment, Oracle Grid Infrastructure includes Oracle Clusterware, Oracle ASM, and the listener.
To use Oracle Grid Infrastructure for a standalone server, you must install the Oracle software from the Oracle Grid Infrastructure media before you install the database.
Oracle Database 11g Release 2 introduces a new option that enables you to specify the type of system on which the database is installed. If you are installing on a laptop or a desktop, then select the Desktop Class option; otherwise, select the Server Class option to install on a server. These options are available on the System Class screen.
There is no difference in the software that gets installed after you select any one option but the Desktop Class option installs a single instance database without the advanced configuration options.
See Also: "Interactive Installation Types" for more information about the desktop and server class options |
When time zone version files are updated due to daylight saving time changes, TIMESTAMP WITH TIMEZONE (TSTZ) data could become stale. In previous releases, database administrators ran the SQL script utltzuv2.sql
to detect TSTZ data affected by the time zone version changes and then had to perform extensive manual procedures to update the TSTZ data.
With this release, TSTZ data is updated transparently with minimal manual procedures using newly provided DBMS_DST PL/SQL packages. In addition, there is no longer a need for clients to patch their time zone data files.
See Also:
|
Starting with Oracle Database 11g Release 2 (11.2), Oracle ASM administration must be done with the SYSASM
privilege. The SYSASM
privilege also can be granted using password authentication on the Oracle ASM instance.
You can designate OPERATOR
privileges (a subset of the SYSASM
privileges, including starting and stopping Oracle ASM) to members of the OSOPER
for an Oracle ASM group.
Using the SYSASM
privilege for ASM administration creates a clear division of responsibility between ASM administration and database administration. It also provides the optional capability to prevent different databases using the same storage from accidentally overwriting each other's files.
See Also: Oracle Automatic Storage Management Administrator's Guide for more information about theSYSASM privilege, ASMSNMP account, and OSASM operating system group |
Starting with Oracle Database 11g Release 2 (11.2), the Oracle Universal Installer (OUI) detects when minimum requirements for an installation are not completed, and creates scripts, called fixup scripts, to resolve many incomplete system configuration requirements. If OUI detects an incomplete task, then click the Fix & Check Again button to generate the fixup script.
For Oracle Clusterware, you also can have Cluster Verification Utility (CVU) generate fixup scripts before the installation.
The fixup script is generated during the installation. You are prompted to run the script as root in a separate terminal session. When you run the script, it sets some system parameters to Oracle-recommended values, if necessary, and completes other operating system configuration tasks.
Database Smart Flash Cache feature is a transparent extension of the database buffer cache using solid state device (SSD) technology. The SSD acts as a Level 2 cache to the (Level 1) Oracle system global area (SGA).
SSD storage is faster than disk storage, and cheaper than RAM. Database Smart Flash Cache with SSD storage gives you the ability to greatly improve the performance of your Oracle databases by reducing the amount of disk I/O at a lower cost than adding an equivalent amount of RAM.
Database Smart Flash Cache is supported on Oracle Solaris and Oracle Linux only.
See Also:
|
Oracle Universal Installer no longer provides the custom installation option of individual components. Use the chopt
tool, a command-line utility that is located in the ORACLE_HOME
/bin
directory, to configure the database options.
Use the new deinstallation tool (deinstall
) available as an Oracle Technology Network download (before installation) and in the Oracle home directory (after installation) to remove Oracle Database software.
See Chapter 7, "Removing Oracle Database Software"
The Intelligent Data Placement feature enables you to specify disk regions on Oracle ASM disks to ensure that frequently accessed data is placed on the outermost (hot) tracks which provide higher performance.
See Also: Oracle Automatic Storage Management Administrator's Guide for more information about Oracle ASM Intelligent Data Placement |
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a new multiplatform, scalable file system, and storage management design that extends Oracle ASM technology, to support data that cannot be stored in Oracle ASM, in both single instance and cluster configurations. Additionally, Oracle ACFS provides snapshot functionality for a point in time copy of an Oracle ACFS system.
The software required for Oracle Automatic Storage Management Cluster File System is installed with the Oracle Grid Infrastructure installation.
See Also:
|
Data Pump provides a legacy mode in which you can use original export and import parameters when performing Oracle Data Pump export and import operations.
Oracle Restart is a new feature included in this release to enhance the availability of Oracle databases in a single-instance environment. If you install Oracle Restart, and there is a temporary failure of any part of the Oracle Database software stack, including the database, listener, and Oracle ASM instance, Oracle Restart automatically restarts the failed component. In addition, Oracle Restart starts all these components when the database host computer is restarted. The components are started in the proper order, taking into consideration the dependencies among components.
See Also: Chapter 4, "Configuring Automatic Restart of an Oracle Database" in the Oracle Database Administrator's Guide for more information about Oracle Restart |
In past releases, Oracle ASM was installed as part of the Oracle Database installation. With Oracle Database 11g Release 2 (11.2), Oracle ASM is installed when you install the Oracle Grid Infrastructure components and shares an Oracle home with Oracle Clusterware when installed in a cluster such as with Oracle Real Application Cluster (Oracle RAC) or with Oracle Restart on a single instance database.
If you want to upgrade an existing Oracle ASM, then you must upgrade Oracle ASM by running an Oracle Grid Infrastructure upgrade. If you do not have Oracle ASM installed and you want to use Oracle ASM as your storage option, then you must complete an Oracle Grid Infrastructure installation before you start your Oracle Database installation.
See Also: "Oracle Grid Infrastructure" for more information about installing the Oracle Grid Infrastructure software |
SRVCTL was enhanced to support single-instance databases with Oracle Restart on standalone servers and on clusters with Oracle Clusterware. SRVCTL is a command-line interface used to manage Oracle processes (database instance, listener, Oracle ASM instance) when using Oracle Restart. With SRVCTL, you can manage the Oracle Restart configuration, see the status of processes managed by Oracle Restart, and start or stop processes such as the Oracle Database.
See Also: Chapter 4, "Configuring Automatic Restart of an Oracle Database" in the Oracle Database Administrator's Guide for more information about SRVCTL commands |
The following are not supported or not available anymore with Oracle Database 11g Release 2:
Installing data files directly on raw devices is no longer available during installation with Oracle Universal Installer or Database Configuration Assistant. You must use a file system or use Oracle ASM.
Oracle Ultra Search
Installation Guide
11g Release 2 (11.2) for Linux
E24321-07
September 2012
Oracle Database Installation Guide, 11g Release 2 (11.2) for Linux
E24321-07
Copyright © 2011, 2012, Oracle and/or its affiliates. All rights reserved.
Primary Author: Prakash Jashnani
Contributing Authors: Reema Khosla, Douglas Williams
Contributors: David Austin, Subhranshu Banerjee, Janelle Simmons, Mark Bauer, Robert Chang, Jonathan Creighton, Sudip Datta, Thirumaleshwara Hasandka, Joel Kallman, George Kotsovolos, Simon Law, Richard Long, Shekhar Vaggu, Rolly Lv, Padmanabhan Manavazhi, Sreejith Minnanghat, Krishna Mohan, Rajendra Pingte, Hanlin Qian, Roy Swonger, Ranjith Kundapur, Aneesh Khandelwal , Barb Lundhild, Barbara Glover, Binoy Sukumaran, Hema Ramamurthy, Prasad Bagal, Martin Widjaja, Ajesh Viswambharan, Eric Belden, Sivakumar Yarlagadda, Rudregowda Mallegowda , Matthew McKerley, Trivikrama Samudrala, Akshay Shah, Sue Lee, Sangeeth Kumar, James Spiller, Saar Maoz, Rich Long, Mark Fuller, Sunil Ravindrachar, Sergiusz Wolicki, Eugene Karichkin, Joseph Francis, Srinivas Poovala, David Schreiner, Neha Avasthy, Dipak Saggi, Sudheendra Sampath, Mohammed Shahnawaz Quadri, Shachi Sanklecha, Zakia Zerhouni, Jai Krishnani, Darcy Christensen., Kevin Flood, Clara Jaeckel, Emily Murphy, Terri Winters
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.
The Oracle Database software is available on installation media, or you can download it from the Oracle Technology Network Web site, or the Oracle Software Delivery Cloud portal. 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, without using the GUI.
Review the information in Chapter 1, "Overview of Oracle Database Installation" and complete the tasks listed in Chapter 2, " Oracle Database Preinstallation Requirements".
If you must perform multiple installations of Oracle Database, you may want to use silent mode or response file mode. In response file mode, at each node, you run Oracle Universal Installer from the command line using a response file. The response file is a text file that contains the settings you typically enter in the Oracle Universal Installer GUI dialog boxes.
Review the following guidelines before starting Oracle Universal Installer:
Using Oracle Universal Installer from an earlier Oracle release to install components from this release is no longer allowed.
Oracle Automatic Storage Management
In previous releases, Oracle Automatic Storage Management (Oracle ASM) was installed as part of the Oracle Database installation. With Oracle Database 11g Release 2 (11.2), Oracle ASM is part of an Oracle Grid Infrastructure installation, either for a cluster, or for a standalone server.
To upgrade an existing Oracle ASM installation, upgrade Oracle ASM by running an Oracle Grid Infrastructure upgrade. If you do not have Oracle ASM installed and you want to use Oracle ASM as your storage option, then you must complete an Oracle Grid Infrastructure installation before you start your Oracle Database installation.
See Also: Chapter 3, "Oracle Grid Infrastructure" for information about Oracle Grid Infrastructure for a standalone server |
If Oracle Clusterware and Oracle RAC are installed on the system, Oracle Universal Installer displays the Specify Hardware Cluster Installation page. You must select the Local Installation option, unless you want to install Oracle RAC.
Oracle Database uses the database character set for:
Data stored in SQL character datatypes (CHAR, VARCHAR2, CLOB, and LONG).
Identifiers such as table names, column names, and PL/SQL variables.
Stored SQL and PL/SQL source code, including text literals embedded in this code.
After a database is created, changing its character set is usually very expensive in terms of time and resources. Such operations may require converting all character data by exporting the whole database and importing it back. Therefore, it is important that you carefully select the database character set at installation time.
Oracle recommends Unicode AL32UTF8 as the database character set. Unicode is the universal character set that supports most of the currently spoken languages of the world. It also supports many historical scripts (alphabets). Unicode is the native encoding of many technologies, including Java, XML, XHTML, ECMAScript, and LDAP. Unicode is ideally suited for databases supporting the Internet and the global economy.
Because AL32UTF8 is a multibyte character set, database operations on character data may be slightly slower when compared to single-byte database character sets, such as WE8MSWIN1252. Storage space requirements for text in most languages that use characters outside of the ASCII repertoire are higher in AL32UTF8 compared to legacy character sets supporting the language. The increase in storage space concerns only character data and only data that is not in English. The universality and flexibility of Unicode usually outweighs these additional costs.
Consider legacy character sets when compatibility, storage requirements, or performance of text processing is critical and the database supports only a single group of languages. The database character set to be selected in this case is the character set of most clients connecting to this database.
The default character set suggested or used by Oracle Universal Installer and Database Configuration Assistant in this release is based on the language configuration of the operating system.
For most languages, the default character set is one of the Microsoft Windows character sets, for example WE8MSWIN1252, even though the database is not installed on Windows. This results from the assumption that most clients connecting to the database run under the Microsoft Windows operating system. Because the database should be able to store all characters coming from the clients and Microsoft Windows character sets have a richer character repertoire than the corresponding ISO 8859 character sets, the Microsoft Windows character sets are usually the better choice. For example, the EE8MSWIN1250 character set supports the Euro currency symbol and various smart quote characters, while the corresponding EE8ISO8859P2 character set does not support them. Oracle Database converts the data between the database character set and the client character sets, which are declared by the NLS_LANG settings.
The list of database character sets that is presented to you for selection by Oracle Universal Installer contains only the recommended character sets. Even though Oracle Database supports many more character sets, they are either deprecated or they are binary subsets of another recommended character set. For example, WE8DEC is a deprecated character set and US7ASCII and WE8ISO8859P1 are both binary subsets of WE8MSWIN1252.
If, for compatibility reasons, you must create a database in one of the character sets that was not recommended, select the Advanced database configuration option. Database Configuration Assistant in the interactive mode gives you the opportunity to select any of the database character sets supported on Linux.
This section is optional and describes how to identify disk groups and determine the free disk space that they contain. You can store either database or recovery files in an existing Oracle ASM disk group that you created during the Oracle Grid Infrastructure installation.
Note: The Oracle ASM instance that manages the existing disk group runs in the Oracle Grid Infrastructure home directory. |
To determine if an existing Oracle ASM disk group exists or to determine if there is sufficient disk space in a disk group, use the following procedure:
View the contents of the oratab
file to determine if an Oracle ASM instance is configured on the system:
# more /etc/oratab
If an Oracle ASM instance is configured on the system, then the oratab
file contains a line similar to the following:
+ASM:oracle_home_path:N
In this example, +ASM
is the system identifier (SID
) of the Oracle ASM instance and oracle_home_path
is the Oracle home directory where Oracle ASM is installed. By convention, the SID
for an Oracle ASM instance should be +ASM
.
Open a shell prompt and temporarily set the ORACLE_SID
and ORACLE_HOME
environment variables to specify the appropriate values for the Oracle ASM instance to use.
For example, if the Oracle ASM SID
is named +ASM
and is located in the grid
subdirectory of the ORACLE_BASE
directory, then enter the following commands to create the required settings:
Bourne, Bash, or Korn shell:
$ ORACLE_SID=+ASM $ export ORACLE_SID $ ORACLE_HOME=/u01/app/oracle/product/11.2.0/grid/ $ export ORACLE_HOME
C shell:
% setenv ORACLE_SID +ASM % setenv ORACLE_HOME /u01/app/oracle/product/11.2.0/grid
Using SQL*Plus, connect to the Oracle ASM instance as the SYS
user with SYSASM
privilege and start the instance if necessary:
# $ORACLE_HOME/bin/sqlplus /nolog
SQL> CONNECT SYS as SYSASM
Enter password: SYS_password
SQL> STARTUP
Enter the following command to view the existing disk groups, their redundancy level, and the amount of free disk space in each one:
SQL> SELECT NAME,TYPE,TOTAL_MB,FREE_MB FROM V$ASM_DISKGROUP;
From the output, identify a disk group with the appropriate redundancy level, and note the free space that it contains.
If necessary, install or identify the additional disk devices required to meet the storage requirements listed in the previous section.
The Oracle Database software is available on installation media, or you can download it from the Oracle Technology Network Web site, or the Oracle Software Delivery Cloud portal. 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 by using one of the following methods:
To copy the software to a hard disk, see "Copying the Software to the Hard Disk"
To download the software from Oracle Technology Network, see "Downloading Oracle Software"
You can download the trial version of the installation files from the Oracle Technology Network (OTN) or the Oracle Software Delivery Cloud portal and extract them on your hard disk. Ensure that you review and understand the terms of the license. Most downloads include the development license. This section contains the following topics:
To download the installation archive files from Oracle Technology Network:
Use any browser to access the software download page from Oracle Technology Network:
http://www.oracle.com/technetwork/indexes/downloads/index.html
Go to the download page for the product 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 file names.
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 of the archive files.
On the file system that you selected in Step 4, create a parent directory for each product, for example OraDB11g
, to hold the installation directories.
Download all of the installation archive files to the directory that you created in Step 5.
Verify that the files you downloaded are the same size as the corresponding files on Oracle Technology Network.
Extract the files in each directory that you just created.
After you have extracted the required installation files, see "Installing the Oracle Database Software" .
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 portal:
https://edelivery.oracle.com/
Complete the Export Validation process by entering information (name, company, email 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.
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. After 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 refer during the installation process. |
See Also: Frequently Asked Questions section on the Oracle Software Delivery Cloud portal for more information about Media Packs |
To extract the installation archive files, perform the following steps:
If necessary, change to the directory that contains the downloaded installation archive files.
If the downloaded file has the zip
extension, use the following command to extract the content:
unzip file_name.zip
If the downloaded file has the cpio.gz
extension, use the following command:
$ gunzip filename.cpio.gz
This command creates files with names similar to the following:
filename.cpio
To extract the installation files, enter a command similar to the following:
$ cpio -idcmv < filename.cpio
Note: See the download page for information about the correct options to use with thecpio command.
Some browsers uncompress files while downloading them, but they leave the |
For each file, this command creates a subdirectory named Disk
n
, where n
is the disk number identified in the file name.
When you have extracted all of the required installation files, see the "Installing the Oracle Database Software".
Before installing Oracle Database, you might want to copy the software to the hard disk to enable the installation process to run faster. Before copying the installation media content to the hard disk, you must mount the disk. The following sections describe how to mount the disk and copy its content to the hard disk.
On most Linux systems, the disk mounts automatically when you insert it into the disk drive. If the disk does not mount automatically, then follow these steps to mount it:
If necessary, log in as the root
user and enter a command similar to one of the following to eject the currently mounted disk, then remove it from the drive:
Asianux, Oracle Linux, and Red Hat Enterprise Linux:
# sudo eject /mnt/dvd
SUSE Linux Enterprise Server:
# eject /media/dvd
In these examples, /mnt/dvd
and /media/dvd
are the mount point directories for the installation media.
Insert the appropriate installation media into the disk drive.
To verify if the disk is mounted automatically, enter one of the following commands depending on the platform:
Asianux, Oracle Linux, and Red Hat Enterprise Linux:
# ls /mnt/dvd
SUSE Linux Enterprise Server:
# ls /media/dvd
Before running the following command, ensure that the /mnt/dvd
directory exists on Red Hat Enterprise Linux. If not, create the /mnt/dvd
as required, to mount the installation media.
If this command fails to display the contents of the installation media, enter a command similar to the following to mount it, depending on the platform:
Asianux, Oracle Linux, and Red Hat Enterprise Linux:
# mount -t iso9660 /dev/dvd /mnt/dvd
SUSE Linux Enterprise Server:
# mount -t iso9660 /dev/dvd /media/dvd
In these examples, /mnt/dvd
and /media/dvd
are the mount point directories for the installation media.
If Oracle Universal Installer displays the Disk Location dialog box, enter the disk mount point directory path, for example:
/mnt/dvd
To continue, go to one of the following sections:
To copy software to a hard disk, see "Copying the Oracle Database Software to a Hard Disk".
To install the software from the installation media, see "Installing the Oracle Database Software".
Note: If the system does not have an installation media, you can copy the software from the disk to a file system on another system, then either mount that file system using NFS or use FTP to copy the files to the system where you want to install the software. |
To copy the contents of the installation media to a hard disk:
Create a directory on the hard disk, outside of the Oracle base directory, to hold the Oracle software:
$ mkdir OraDb11g
Change the directory to the directory you created in Step 1:
$ cd OraDb11g
Mount the disk, if it is not mounted.
Some platforms automatically mount the disk when you insert it into the drive. If the disk does not mount automatically, see the "Mounting Disks" section for platform-specific information.
Copy the contents of the mounted disk to the corresponding new subdirectory as follows:
$ cp -R /directory_path OraDb11g
In this example, /
directory_path
is the disk mount point directory.
If necessary, mount the next disk and repeat Step 4.
During installation, you are prompted to select a database security configuration. The Secure Configuration option configures the database with database auditing options, and password policy and expiration settings.
For new database installations, the default configuration for Oracle Database 11g Release 2 (11.2) includes the Secure Configuration option. To disable these enhanced security controls you can deselect the Assert all new security settings check box in the Specify Configuration Option screen that appears during the database installation. Oracle Database is then installed with default options for Oracle Database 10g Release 2. You can enable or disable auditing or password security settings, or revert to a previous security setting. After installation, you can enable or disable the security configuration by starting Database Configuration Assistant through the command-line interface.
To enable the security configuration:
dbca -silent -configureDatabase -sourceDB SID
-disableSecurityConfiguration NONE -enableSecurityConfiguration true
To disable the security configuration:
dbca -silent -configureDatabase -sourceDB SID
-disableSecurityConfiguration [ALL|PASSWORD_PROFILE] -enableSecurityConfiguration false
SID
is the system identifier.
For database upgrades, the upgraded database retains your existing database security configuration to ensure compatibility with existing applications.
Starting with Oracle Database 11g Release 2 (11.2), the Security Enhanced Linux (SELinux) feature is supported for Oracle Linux 4, Red Hat Enterprise Linux 4, Oracle Linux 5, and Red Hat Enterprise Linux 5.
Note:
|
In most cases, you use the graphical user interface (GUI) provided by Oracle Universal Installer to install Oracle Database. The instructions in this section explain how to run the Oracle Universal Installer GUI to perform most database installations.
Note:
|
For any type of installation process, start Oracle Universal Installer and install the software, as follows:
Logon as the Oracle software owner user (typically, oracle
) to the computer on which you want to install Oracle components.
If you are installing the software from installation media, mount the disk if it is not mounted.
If the disk does not mount automatically, see the "Mounting Disks" section for platform-specific information.
Some platforms automatically mount the disk when you insert the installation media into the drive.
To start Oracle Universal Installer, complete one of the following steps depending on the location of the installation files:
Note: Start Oracle Universal Installer from the terminal session where you logged in as theoracle user and set the user's environment. |
If the installation files are on installation media, enter commands similar to the following, where directory_path
is the path of the database
directory on the installation media:
$ /directory_path/runInstaller
If the installation files are on the hard disk, change the directory to the database
directory and enter the following command:
$ ./runInstaller
Downloading Updates Before Installation
Starting with Oracle Database 11g Release 2 (11.2.0.2), 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 the updates, enter the following command:
$ ./runInstaller -downloadUpdates
Provide the My Oracle Support user name and password, and provide proxy settings, if needed, in the Provide My Oracle Support credentials screen. Then, enter the Download location and click Download in 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 the updates, transfer the update file to a directory on the server where you plan to run the installation.
See Also:
|
If Oracle Universal Installer is not displayed, see "X Window Display Errors" and "Remote Terminal Installation Error" for information about troubleshooting.
Use the following guidelines to complete the installation:
Do not install Oracle Database 11g Release 2 (11.2) software into an existing Oracle home.
Follow the instructions displayed on the Oracle Universal Installer screens. If you need additional information, click Help.
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 errors are displayed while installing the software, see Appendix G for information about troubleshooting.
If you chose an installation type that runs Oracle Database Configuration Assistant in interactive mode, then you must provide detailed information about configuring the database and network.
If you need help when using the Oracle Database Configuration Assistant in interactive mode, click Help on any screen.
Note: If you chose a default installation, Oracle Database Configuration Assistant does not run interactively. |
When the configuration assistant tasks are complete click finish, click Exit, then click Yes to exit from Oracle Universal Installer.
During the database installation, when Oracle Universal Installer prompts you to run a script with root
privileges, enter a command similar to the following in a terminal where you are logged in as the root
user, then click OK:
# /script_path/script_name
For more information see screen "Install product" in the installation table that follows.
See Chapter 5 for information about tasks that you must complete after you install Oracle Database.
The following table lists the various screens displayed during an Enterprise Edition installation for Oracle Database 11g Release 2 (11.2):
Screen | Action |
---|---|
Configure Security Updates | Enter your email address, preferably your My Oracle Support email address or user name in the Email field.
Select the I wish to receive security updates via My Oracle Support check box to receive security updates. Enter your My Oracle Support password in the My Oracle Support Password field. Click Next. |
Download Software Updates | Starting with Oracle Database 11g Release 2 (11.2.0.2), you can use the Software Updates feature to dynamically download and apply the latest updates. Select one of the following options, and click Next:
See Also: "Software Updates Option" |
Apply Software Updates | This screen is displayed if you select to download the software updates, or provide the pre-downloaded software updates location.
|
Select Installation Option | Select one of the following installation options, and click Next:
|
System Class | Select the type of system for installing the database, and click Next.
|
Grid Installation Options | Select the type of database installation you want to perform, and click Next.
|
Select Install Type | Select one of the following, and click Next:
|
Select Product Languages | This option enables you to select the language in which you want to run the product.
Select the product language from the Available Languages list, and move it to the Selected Languages list. Click Next. |
Select Database Edition | Select Enterprise Edition, Standard Edition, or Standard Edition One. Click Next.
If you click Select Options, then based on your selection you can enable or disable components from the components list. This screen enables you to customize the database. The components available in this screen are:
Click OK to continue. Note: The Select Options button is enabled only if you select the Enterprise Edition installation type. |
Specify Installation Location | The Oracle base path appears by default. You can change this path based on your requirement. Specify Oracle Base, Software Location, and click Next.
The Oracle base directory is a top-level directory for Oracle software installations owned by an Oracle installation owner account. The default Oracle base path is In the Software Location field, accept the default value or enter the Oracle home directory path in which you want to install Oracle software.The directory path must not contain spaces. Click Next. Note: This screen is available only with Advanced Installation. Ensure that the Oracle home path for the database home and the Oracle base path use only ASCII characters. At the time of this release, the use of non-ASCII characters for an Oracle database home or Oracle base is not supported. See Also: "Naming Directories" and "Identifying Required Software Directories" |
Create Inventory | You are prompted by the installer to specify the Inventory Directory path for the central inventory the first time you install any Oracle software on your computer.
Select the oraInventory Group Name of the operating system group that will own the Oracle Inventory directory (the Oracle Inventory group). Click Next. Note: By default, the Oracle Inventory directory is not installed under the Oracle Base directory. This is because all Oracle software installations share a common Oracle Inventory, so there is only one Oracle Inventory for all users, whereas there is a separate Oracle Base directory for each user. |
Select Configuration Type | Select one of the following, and click Next:
See the online help provided by either Oracle Universal Installer or Oracle Database Configuration Assistant for a description of these preconfigured database types. |
Specify Database Identifiers | Provide the following information, and click Next:
Database Naming Provide the Global Database Name using the following syntax: db_unique_name.db_domain
Note: Ensure that the combination of database name (first 8 unique characters of the unique name for the database), delimiter, and the database domain name does not exceed 128 characters. For example: sales.us.example.com
When you enter the Global Database Name, Oracle Universal Installer automatically populates the SID prefix with the database name. You can change this name in Advanced Installation. Oracle Universal Installer limits the SID to 12 alphanumeric characters and the SID cannot contain an underscore (_), dollar sign ( $), or pound sign (#). See "Setting the ORACLE_HOSTNAME Environment Variable" and "Identifying Databases" |
Specify Configuration Options | Provide the following configuration information, and click Next:
Memory: The Enable Automatic Memory Management option is selected by default. This option enables the database to automatically distribute memory between SGA and PGA. If you deselect this option, then the SGA and PGA must be sized manually. Character Sets: This option enables you to store the character data in the database in one of the following methods:
See Also:
Security: The Assert all new security settings option is selected by default. This setting includes enabling auditing and using new password profile. Note: Oracle recommends that you use the default settings. Sample Schemas: The Create database with sample schemas option is not selected by default. You can select this option, to create a starter database with sample schemas. |
Specify Management Options | Select one of the following options, and click Next:
|
Specify Database Storage Options | Select one of the following options, and click Next.
Note: Installing Oracle data files on an Oracle ACFS file system is not supported. Oracle recommends that these data files are installed in Oracle ASM disk groups. See Also: "Using an Oracle Automatic Storage Management Disk Group" |
Specify Recovery Options | Select one of the following options, and click Next.
|
Select ASM Disk Group | This screen is displayed only if you select Oracle Automatic Storage Management as your storage option in the Specify Storage Option screen.
Disk groups are created during the Oracle Grid Infrastructure installation. Disk groups are configured with the The table in this screen displays existing disk groups created during the Oracle Grid Infrastructure installation. Select the disk group to use for database file storage. |
Specify Schema Passwords | Enter and confirm passwords for the privileged database accounts, and click Next.
Note: Optionally, you can use the same password for all accounts. However, Oracle recommends that you specify a different password for each account. You must remember the passwords that you specify. See Also: "Unlocking and Changing Passwords" for information about password guidelines |
Privileged Operating System Groups | The operating system groups are selected by default. You can also manually select the OSDBA and OSOPER groups.
Click Next. See Also: "Creating Required Operating System Groups and Users" for more information. |
Perform Prerequisite Checks | This option verifies that the minimum system requirements to perform the database installation are met.
If you click Check Again, then you can run the prerequisite check again to see if the minimum requirements are met to carry on with the database installation. Click Fix & Check Again, if you want the installer to fix the problem and verify the system requirements again. Note: The Fix & Check Again option generates a script that you must run as the See Also: "Installation Fixup Scripts" for more information. To get a list of failed requirements, select ShowFailed from the list. To get a list of all the prerequirement checks run by the OUI, select Show All. To get a list of the prerequirement checks that are successful, select Show Succeeded. Note: Oracle recommends that you use caution when selecting the Ignore All option. If you select this option, then Oracle Universal Installer may not confirm that your system can install Oracle Database successfully. See Also: Chapter 2, " Oracle Database Preinstallation Requirements" |
Summary | Review the information displayed on this 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. |
Install Product | This screen displays the progress of a database installation. After the database is installed, you are prompted to execute a root configuration script for new inventory as the root user. Click Next.
This screen then displays the status information for the configuration assistants that configure the software and create a database. A message is displayed at the end of the Database Configuration Assistant process. Click OK. Execute the See Also: Oracle Database 2 Day DBA for information about Oracle Database Configuration Assistant |
Finish | This screen is shown automatically when all the configuration tools are successful.
Review the Enterprise Manager Database Control URL information displayed in this screen and click Close. |
Caution: After installation is complete, do not manually remove or runcron jobs that remove /tmp/.oracle or /var/tmp/.oracle directories or their files while Oracle software is running. If you remove these files, then the Oracle software can intermittently stop responding. Oracle Restart installations fail with the following error:
CRS-0184: Cannot communicate with the CRS daemon. |
If you plan to use the following products or features, then download and install the products from the Oracle Database Examples media:
Oracle JDBC Development Drivers
Oracle Database Examples
Oracle Text Knowledge Base
Various Oracle product demonstrations
For information about installing software and various Oracle product demonstrations from the Oracle Database Examples media, see Oracle Database Examples Installation Guide.
This appendix describes the following Globalization Support topics:
See Also: Oracle Database Globalization Support Guide for an overview of globalization support for Oracle Database |
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 is displayed in a selected language only if the appropriate translation is available and has been installed. Else, the user interface is displayed in English. |
This section describes the following procedures:
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.
The operating system locale is determined by the value of the LANG
environment variable. Depending on your desktop environment, such as KDE, GNOME, or telnet, you can select a default session locale on a login screen, in a configuration panel, or in a configuration file.
Note: Refer to the operating system documentation on how to select a locale for the operating system session in your desktop environment. |
You can modify the LANG
variable in the environment of your shell to start an Oracle component in a selected language. For example, to start Oracle Database Configuration Assistant in German, enter one of the following commands:
Bourne shell (sh), or Korn shell (ksh), or Bash shell (bash):
$ LANG=de_DE.iso88591 dbca
C shell (csh):
% (setenv LANG de_DE.iso88591; dbca)
Note: TheLC_ALL environment variable overrides the value of the LANG environment variable. For the commands listed in this section to work, either ensure that the LC_ALL environment variable is not set in the environment, or substitute LC_ALL for LANG . |
To modify the operating system locale for all Oracle components started by the given shell, modify the LANG
variable using one of the following commands:
Bourne shell (sh), or Korn shell (ksh), or Bash shell (bash):
$ LANG=de_DE.iso88591; export LANG $ ...
C shell (csh):
% setenv LANG de_DE.iso88591 $ ...
The value of the LANG
environment variable must be a valid operating system locale. To see the list of valid locales, enter the following command:
$ locale -a
Note: Refer to the operating system documentation for a mapping between values of theLANG environment variable and the languages and territories that they represent. |
The 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.
The NLS_LANG
environment variable uses the following format:
NLS_LANG=language_territory.characterset
In this format:
language
specifies the language used for displaying Oracle messages, sorting, day names, and month names
territory
specifies the conventions for default date, monetary, and numeric formats
characterset
specifies the encoding used by the client application
In most cases, this is the Oracle character set that corresponds to the character set of the user terminal or the operating system.
The NLS_LANG
environment variable is set as a local environment variable for the shell on all UNIX-based platforms. For example, if the operating system locale setting is en_US.UTF-8
, then the corresponding value of NLS_LANG
environment variable is AMERICAN_AMERICA.AL32UTF8
.
See Also: Oracle Database Globalization Support Guide for information about theNLS_LANG parameter and Globalization Support initialization parameters |
The following examples illustrate some valid values for the NLS_LANG
environment variable.
Note: Refer to the operating system documentation on how to determine the operating system locale environment setting. |
Operating System Locale | NLS_LANG Values |
---|---|
French (France) | FRENCH_FRANCE.WE8ISO8859P15 FRENCH_FRANCE.WE8ISO8859P1 FRENCH_FRANCE.WE8MSWIN1252 FRENCH_FRANCE.AL32UTF8 |
Japanese (Japan) | JAPANESE_JAPAN.JA16EUC JAPANESE_JAPAN.JA16SJIS JAPANESE_JAPAN.AL32UTF8 |
To view the user interface of Oracle components in different languages, you must install the appropriate language translations along with the component.
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, refer to Appendix C in Oracle Database Vault Administrator's Guide. |
To install the translation resources:
Start Oracle Universal Installer.
In the Configure Security Updates screen enter the relevant information and click Next.
In the Download Software Updates and Apply Software Updates screens, enter the relevant information and click Next.
In the Select Installation Option screen, select the installation option and click Next.
In the System Class screen, select the type of system class for installing the database, and click Next.
In the Grid Installation Options screen, select the type of database installation you want to perform, and click Next.
In the Select Product Languages screen, select the language in which you want to use Oracle components 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 Next.
Note: Oracle Universal Installer ignores languages in the Selected Languages field for which no translation is available. |
Your 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 (pt_BR)
French (fr)
German (de)
Italian (it)
Japanese (ja)
Korean (ko)
Simplified Chinese (zh_CN)
Spanish (es)
Traditional Chinese (zh_TW)
To run Oracle Universal Installer in an available language, change the locale in which your operating system session is running before you start Oracle Universal Installer with the ./runInstaller
command. If the selected language is not one of those that were listed earlier, Oracle Universal Installer runs in English.
You must ensure that the selected value for the LANG
environment variable starts with the appropriate language abbreviation. In the aforementioned list of languages, in which Oracle Universal Installer can run, the required abbreviation appears in parentheses beside the language name. For example, fr_FR and fr_CA are valid values to run the Oracle Universal Installer in French.
Cloning an Oracle home involves creating a copy of the Oracle home and then configuring it for a new environment. If you are performing multiple Oracle Database installations, then you may want to use this method to create each Oracle home, because copying files from an existing Oracle Database installation takes less time than creating a new version of them. This method is also useful if the Oracle home that you are cloning has had patches applied to it. When you clone the Oracle home, the new Oracle home has the patch updates.
When you clone Oracle homes using release 11.2 Database Control, you must update the exclude file list. This file list specifies files that need not be included when the source Oracle home is archived because these files are not required for the cloning operation. Do not include the following files in the archive:
sqlnet.ora
tnsnames.ora
listener.ora
oratab
Note: In addition to cloning an Oracle home, you can clone individual Oracle Database installations by using Oracle Enterprise Manager Database Control. Oracle Database Administrator's Guide provides detailed information about cloning Oracle Database installations and Oracle homes. |
This appendix includes information about the following topics:
Perform the following to clone an Oracle home:
Verify that the installation of Oracle Database to clone is successful.
You can do this by reviewing the installActions
date_time
.log
file for the installation session, which is typically located in the /
orainventory_location
/logs
directory.
If you install patches, then check their status using the following:
$ cd $ORACLE_HOME/OPatch
Include $ORACLE_HOME/OPatch
in $PATH
$ opatch lsinventory
Stop all processes related to the Oracle home. See Chapter 7, "Removing Oracle Database Software" for more information about stopping the processes for an Oracle home.
Create a ZIP file with the Oracle home (but not the Oracle base) directory.
For example, if the source Oracle installation is in the /u01/app/oracle/product/11.2.0/dbhome_1
, then you zip the dbhome_1
directory by using the following command:
# zip -r dbhome_1.zip /u01/app/oracle/product/11.2.0/dbhome_1
Do not include the admin
, fast_recovery_area
, and oradata
directories that are under the Oracle base directory. These directories are created in the target installation later, when you create a new database there.
Copy the ZIP file to the root directory of the target computer.
Extract the ZIP file contents by using the following command:
# unzip -d / dbhome_1.zip
Repeat steps 4 and 5 for each computer where you want to clone the Oracle home, unless the Oracle home is on a shared storage device.
On the target computer, change the directory to the unzipped Oracle home directory, and remove all the .ora (*.ora) files present in the unzipped $ORACLE_HOME/network/admin
directory.
From the $ORACLE_HOME/clone/bin
directory, run the clone.pl
file for the unzipped Oracle home. Use the following syntax:
$ORACLE_HOME/perl/bin/perl clone.pl ORACLE_BASE="target_oracle_base
" ORACLE_HOME="target_oracle_home
" OSDBA_GROUP=OSDBA_privileged_group
OSOPER_GROUP=OSOPER_privileged_group
-defaultHomeName
For example:
$ORACLE_HOME/perl/bin/perl clone.pl ORACLE_BASE="/u01/app/oracle/" ORACLE_HOME="/u01/app/oracle/product/11.2.0/dbhome_1" OSDBA_GROUP=dba OSOPER_GROUP=oper -defaultHomeName
Oracle Universal Installer starts, and then records the cloning actions in the cloneActions
timestamp
.log
file. This log file is typically located in /
orainventory_location
/logs
directory.
To configure the connection information for the new database, run Net Configuration Assistant:
$ cd $ORACLE_HOME/bin $ ./netca
To create a new database for the newly cloned Oracle home, run Database Configuration Assistant:
$ cd $ORACLE_HOME/bin $ ./dbca
See Also:
|
Perform the following to configure Oracle Configuration Manager for a cloned Oracle home:
Run the following command from $ORACLE_HOME/ccr/state
:
$ rm -rf *.ll*
Run the following command from $ORACLE_HOME/ccr/inventory
:
$ cp core.jar pending
Run the following commands from $ORACLE_HOME/ccr/bin
:
$ ./emSnapshotEnv $ ./deployPackages
Run the following command from $ORACLE_HOME/ccr/bin
and provide the proper credentials:
$ ./configCCR
If Oracle Configuration Manager was manually configured using setupCCR
, then perform the following in the cloned Oracle home:
Delete all the subdirectories of the $ORACLE_HOME/ccr/hosts
directory to remove previously configured hosts.
Run the following command from $ORACLE_HOME/ccr/bin
:
$ ./configCCR -a
If you installed Oracle Configuration Manager in the original Oracle home but have not configured it, then run the following command in the cloned Oracle home:
$ setupCCR