| Oracle® Database Installation Guide 11g Release 1 (11.1) for Linux Part Number B32002-01 |
|
|
View PDF |
| Oracle® Database Installation Guide 11g Release 1 (11.1) for Linux Part Number B32002-01 |
|
|
View PDF |
The following is a list of new features or enhancements provided with Oracle Database 11g:
SYSASM Privilege for Automatic Storage Management Administration
Deprecated Components in Oracle Database 11g Release 1 (11.1)
The following are the new components available while installing Oracle Database 11g:
Oracle Application Express: This feature is installed with Oracle Database 11g. It was previously named HTML DB, and was available as a separate Companion CD component. Oracle Application Express is now installed by default with any Oracle Database 11g installation.
Oracle Configuration Manager: This feature is offered during installation. It was previously named Customer Configuration repository (CCR). It is an optional component for database installation and can be installed with any Oracle Database 11g installation. Oracle Configuration Manager gathers and stores details relating to the configuration of the software stored in database Oracle home directories.
Oracle Database Vault: This feature is installed with Oracle Database 11g. It is an optional component for database installation.
Oracle Real Application Testing: This feature is installed by default with the Enterprise Edition installation type of Oracle Database 11g.
Oracle SQL Developer: This feature is installed by default with template-based database installations, such as General Purpose/Transaction Processing, and Data Warehousing. It is also installed with database client Administrator, Runtime, and Custom installations.
Oracle Warehouse Builder: This feature is installed with Oracle Database 11g.
Note:
With Standard Edition and Enterprise Edition of Oracle Database 11g Release 1, Oracle Warehouse Builder with basic features is installed. However, with Enterprise Edition, you can purchase options that extend Oracle Warehouse Builder.See Also:
The following sections and guides for more information:Chapter 2, " Oracle Database Preinstallation Requirements" for information about the preinstallation requirements
Oracle Database Application Express User's Guide for more information about Oracle Application Express
The "Preinstallation Requirements for Oracle Configuration Manager" section for more information
Oracle Database Vault Administrator's Guide for more information about Database Vault
Oracle Database Performance Tuning Guide for more information about Oracle Real Application Testing
Oracle Database SQL Developer User's Guide for more information about Oracle SQL Developer
Oracle Warehouse Builder User's Guide for more information about Oracle Warehouse Builder
The following are install option changes for Oracle Database 11g:
Oracle Configuration Manager: Oracle Configuration Manager is integrated with Oracle Universal Installer. However, it is an optional component for database installation and can be installed with any Oracle Database 11g installation.
Oracle Data Mining: Enterprise Edition installation type selects Oracle Database Mining option by default. In Oracle Database 11g, the Data Mining metadata is created with SYS metadata when you select the Create Database option.
Oracle Database Vault: Oracle Database Vault is integrated with Oracle Universal Installer. However, it is an optional component with database installation. To install this product, you have to select the Custom Installation.
Oracle HTTP Server: Starting with Oracle Database 11g, Oracle HTTP Server is available on a separate media shipped with Oracle Database. In the previous releases, this product was available as a Companion CD component.
Oracle Ultra Search: Starting Oracle Database 11g, Oracle Ultra Search is integrated with Oracle Database. In the previous releases, this product was available as a Companion CD component.
Oracle XML DB: Starting with Oracle Database 11g, Oracle XML DB is no longer an optional feature. Database Configuration Assistant installs and configures it for all database installations.
See Also:
The following sections and guides for more information:The "Preinstallation Requirements for Oracle Configuration Manager" section for more information
Oracle Database SQL Language Reference for more information about Oracle Database Mining
Oracle Database Vault Administrator's Guide for more information about Database Vault
Oracle HTTP Server Administrator's Guide for more information about Oracle HTTP Server
Oracle Ultra Search Administrator's Guide for more information about Ultra Search
The "Oracle XML DB for Oracle Application Express" section for more information
The following additions and enhancements are made to Database Configuration Assistant:
The following options in Oracle Database 11g can be configured using Database Configuration Assistant:
Oracle Application Express
Oracle Database Vault
Oracle Warehouse Builder
This is a new initialization parameter in Oracle Database 11g to automate the memory allocation. By default, Database Configuration Assistant now uses MEMORY_TARGET instead of specifying individual values for SGA_TARGET and PGA_AGGREGATE_TARGET. The Memory management page of Database Configuration Assistant has a new option to select automatic memory management.
See Also:
The "Using Automatic Memory Management" section of Oracle Database Administrator's GuideThe directory that you specify when you are prompted for ORACLE_BASE by Oracle Universal Installer is stored in the Oracle home inventory. Database Configuration Assistant uses this value to derive the default database locations and the DIAGNOSTIC_DEST parameter. The diagnostic destination location contains all ADR directories (diagnostic files such as Alert logs and so on). Starting with Oracle Database Release 11g, the initialization parameter settings for background dump, user dump, and core dump destinations are replaced by the Diagnostic Destination.
See Also:
Appendix D, "Optimal Flexible Architecture" for more information on Oracle base and diagnostic destination configurationIn Oracle Database 11g, the data mining schema are created when you run the catproc.sql script as the SYS user. You no longer configure this option through the Database Features screen of Database Configuration Assistant.
See Also:
Oracle Database SQL Language Reference for more information on Oracle Database MiningOracle Database 11g has new defaults for audit and password profiles. Database Configuration Assistant has a new screen to enable the new security settings during the database creation and existing database configuration.
See Also:
The "Database Security Options" section for more informationIn previous releases, Database Configuration Assistant contains the functionality to configure a database either with Database Control, or with Grid Control. You can configure a database either while creating it or later. However, reconfiguring a database from Database Control to Grid Control requires significant manual effort. With Oracle Database 11g, Database Configuration Assistant provides the Enterprise Manager Configuration plug-in, which automates the process to switch configuration of a database from Database Control to Grid Control.
See Also:
Oracle Real Application Clusters Installation Guide for Linux and UNIX for more information on configuring Grid ControlThe following additions and enhancements are made to Database Configuration Assistant:
The command line option AUTOEXTEND facilitates auto extending of the data files as a part of the upgrade. This option automatically extends the data files during the upgrade and turns the autoextend back to its original settings after the upgrade. This option is useful if there is enough space on the disk, and if you do not need to add new data files or manually increase the size of the files.
See Also:
The "Altering a Bigfile Tablespace" section in Oracle Database Administrator's Guide for more information on the
AUTOEXTEND clauseFor single-instance databases, Oracle Database Upgrade Assistant configuration utility enables you to upgrade from Oracle Database Express Edition (Oracle Database XE) to Oracle Database 11g. The XE database files reside under the path ORACLE_BASE/oradata/XE. These files must be copied to a new location as the user may remove the XE Home after upgrade.
Database Upgrade Assistant uses the new pre-upgrade script for Oracle Database 11g. This script is used to estimate disk space, initialization parameters, statistics gathering, and displaying warnings.
You can move data files to ASM, OFS, or other storage devices, such as Storage Area Networks (SAN) and Network Area Storage (NAS), as part of the upgrade. If you move the database files during the upgrade, you can benefit from the typical downtime for this tablespace by rebalancing disks and moving files to a better storage device, such as SAN, NAS, or ASM.
See Also:
The "Preparing Disk Groups for an Automatic Storage Management Installation" for more information on preparing disk groups for Automatic Storage ManagementThe directory that you specify when you are prompted for ORACLE_BASE by Oracle Universal Installer is stored in the Oracle home inventory. Database Upgrade Assistant uses this value to derive the default database locations and the DIAGNOSTIC_DEST parameter. The diagnostic destination location contains all ADR directories (diagnostic files such as Alert logs and so on). This diagnostic destination directory is required while upgrading an earlier Oracle Database release to Oracle Database 11g release of the database. If the Oracle base directory already exists, Oracle Database Upgrade Assistant automatically retrieves this information and populates its path. Starting with Oracle Database 11g Release 1, the initialization parameter settings for background dump, user dump, and core dump destinations are replaced by the Diagnostic Destination.
See Also:
Appendix D, "Optimal Flexible Architecture" for more information on Oracle base and diagnostic destination configurationAutomatic Storage Management fast mirror resync quickly resynchronizes Automatic Storage Management disks within a disk group after transient disk path failures, as long as the disk drive media is not corrupted. Any failures that render a failure group temporarily unavailable are considered transient failures. Disk path malfunctions, such as cable disconnections, host bus adapter or controller failures, or disk power supply interruptions, can cause transient failures. The duration of a fast mirror resync depends on the duration of the outage. The duration of a resynchronization is typically much shorter than the amount of time required to completely rebuild an entire Automatic Storage Management disk group.
See Also:
The "Automatic Storage Management Fast Mirror Resync" section in Oracle Database Storage Administrator's Guide for more information on ASM fast mirror resyncOracle Database 11g introduces an optional system privilege, SYSASM, and an optional operating system group, OSASM, to secure privileges to perform Automatic Storage Management administration tasks. Oracle recommends that you use SYSASM instead of SYSDBA for Automatic Storage Management administration, to separate Automatic Storage Management administration from database administration. In a future release, Oracle may restrict access to Automatic Storage Management only to operating system users that are members of the OSASM operating system group, and require the use of SYSASM to administer Automatic Storage Management.
Note:
You can create an operating system group for Automatic Storage Management administrator, in addition todba and oper groups.See Also:
The "Authentication for Accessing ASM Instances" section in Oracle Database Storage Administrator's Guide for more information onSYSASM privilege for Automatic Storage ManagementThis feature provides out-of-the-box management of CPU distribution among the various database maintenance tasks, such as Automatic Optimizer Statistics Collection and Automatic Segment Advisor. Maintenance tasks are throttled to the extent that end-user activity gets the necessary resources to finish its work.
See Also:
Chapter 24, "Managing Automated Database Maintenance Tasks" of Oracle Database Administrator's Guide for more information on Automatic Maintenance task managementThe Automatic Diagnostic Repository is a feature added to Oracle Database 11g. It is a new system managed repository for storing and organizing trace files and other error diagnostic data. The Automatic Diagnostic Repository provides a comprehensive view of the critical errors encountered by the database. This feature also enables you to maintain the relevant data needed for problem diagnostics and their eventual resolution. The Automatic Diagnostic Repository reduces the time to resolve errors and code defects. The repository is stored as a directory structure under the ADR_base directory that contains the diag directory. The default location of the ARD_base directory is $ORACLE_BASE. However, this location can be changed by using the DIAGNOSTIC_DEST parameter of init.ora.
See Also:
The "Automatic Diagnostic Repository (ADR)" section in Oracle Database Administrator's Guide for more information on the Automatic Diagnostic RepositoryThe following enhancements are made to the Optimal Flexible Architecture in Oracle Database 11g:
In Oracle Database 11g, Oracle Universal Installer prompts you to specify the Oracle base. You can share this Oracle base across all of the Oracle homes you create on the system. Oracle recommends that you share an Oracle base for all of the Oracle homes created by the same user.
Oracle Universal Installer has a list box where you can edit or select the Oracle base. The installer derives the default Oracle home from the Oracle base location you provide in the list box. However, you can change the default Oracle home by editing the location.
When installing Oracle Clusterware, the Oracle Clusterware home should not be under Oracle base. This is because the root.sh script in Unix operating systems changes the ownership of the parent directories up to the root file system (/) to the root user. If you specify an Oracle Clusterware home under Oracle base, Oracle Universal Installer displays an error.
The following are the changes made in Oracle Database 11g with respect to Oracle base to make it Optimal Flexible Architecture compliant:
ORACLE_BASE is a recommended environment variable. However, this variable will be made mandatory in future releases.
Oracle recommends that you create the flash recovery area and data file location under Oracle base.
See Also:
Oracle Clusterware Installation Guide for Linux for more information on Oracle Clusterware homeIn Oracle Database 10g, the default locations for the flash recovery area and data file are one level above the Oracle home directory. However, in Oracle database 11g, Oracle base is the starting point to set the default locations for flash recovery and data file. However, Oracle recommends that you keep the flash recovery area and data file location on separate disks. To mount the disks you can use the following mount points for flash recovery area and data file location respectively:
$ORACLE_BASE/flash_recovery_area $ORACLE_BASE/oradata
If you do not use separate disks for flash recovery area and data file location, the installer displays a warning message with a recommendation to use separate disks for flash recovery area and data file location.
If you install Oracle RAC, you must share flash recovery area and data file location among all the nodes.
See Also:
Appendix D, "Optimal Flexible Architecture" for more information Optimal Flexible ArchitectureThis feature is implemented as a Direct Network File System client as a part of Oracle RDBMS Kernel in Oracle Disk Manager library. NAS-based storage systems use Network File System to access data. In Oracle Database 10g, NAS storage devices are accessed using the operating system provided kernel network file system driver, which require specific configuration settings to ensure its efficient and correct usage with Oracle. The following are the major problems that arise in correctly specifying configuration parameters:
Network File System clients are very inconsistent across platforms and vary across operating system releases.
The configuration parameters are difficult to tune. There are more than 20 Network File System parameters and they have subtle differences across platforms.
Network File System client stack is designed for general purpose. Therefore, it contains features like file attribute management that are not required for Oracle.
Oracle Direct Network File System implements NFS version 3 protocol within the Oracle RDBMS kernel.
The following are the main advantages of implementing Oracle Direct Network File System client functionality in Oracle RDBMS Kernel:
It enables complete control over input-output paths to Network File Servers, resulting in predictable performance, simplified configuration management, and superior diagnostics.
Its operations avoid the kernel network file system layer bottlenecks and resource limitations. However, the kernel is still used for network communication modules.
It provides a common Network File System interface for Oracle for potential use on all host platforms and supported Network File System servers.
It enables improved performance through load balancing across multiple connections to Network File System servers and deep pipelines of asynchronous input-output operations with improved concurrency.
See Also:
Oracle Clusterware Installation Guide for Linux for more information in Network File SystemThe following is a list of components that were part of Oracle Database 10g release 2 (10.2), and are not available for installation with Oracle Database 11g:
iSQL*Plus
Oracle Workflow
Oracle Data Mining Scoring Engine
Oracle Enterprise Manager Java console
