Skip Headers
Oracle® Database 2 Day DBA
11g Release 1 (11.1)

B28301-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

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

2 Installing Oracle Database and Creating a Database

This chapter describes how to install Oracle Database software and create a database.

If you are using an earlier release of Oracle Database and want to install a later release of the Oracle Database software, you can upgrade your existing Oracle Database and use it with the new release of the database software. See "Upgrading a Database".

This chapter contains the following sections:

Overview of Installing Oracle Database Software and Creating a Database

To install your Oracle Database software, use Oracle Universal Installer (OUI). OUI is a graphical user interface utility that enables you to view the Oracle Database software that is already installed on your computer, install new Oracle Database software, and deinstall Oracle Database software that you no longer intend to use. Online Help is available to guide you through the installation process.

During the installation process, you are given the opportunity to create a database. If you choose to do so, OUI automatically starts Oracle Database Configuration Assistant (DBCA) to guide you through the process of creating and configuring a database.

If you do not create a database during installation, then you must run DBCA at some point after installation to create a database.

Note:

After you create a database, either during installation or as a standalone operation, you do not need to create another. Each Oracle instance works with a single database only. Rather than requiring that you to create multiple databases to accommodate different applications, Oracle Database uses a single database, and accommodates multiple applications by enabling you to separate data into different schemas within the single database. See "About User Accounts" for more information about schemas.

Checking Prerequisites

Before installing the software, OUI performs a number of automated checks to ensure that your computer fulfills the basic hardware and software requirements for an Oracle Database installation. If your computer does not meet a requirement, an error message is displayed. The requirements may vary depending upon the type of computer and operating system you are running, but some prerequisites include:

  • There is a minimum of 512 MB (Microsoft Windows or Linux) or 1 GB (UNIX and other operating systems) of physical memory.

  • Sufficient paging space is available.

  • The appropriate service packs or patches for your operating system are installed.

  • An appropriate file system format is being used.

OUI automatically sets any operating system environment variables that Oracle Database requires for its operation.

See Also:

Installation Choices

Oracle Universal Installer guides you through an interview phase where you specify your choices for installation and database creation. The exact sequence of steps depends on your operating system.

The installation options are divided into basic and advanced. During a basic installation, you need to make only basic choices. For all other cases, you make both basic and advanced choices.

Basic Installation

When you install Oracle Database during basic and advanced installations, you need answers for the questions listed in this section. OUI provides default values for every choice.

  • What database product do you want to install?

    You can install one of the following:

    • Enterprise Edition—This installation type is the full-featured Oracle Database product that provides data management for enterprise-level applications. It is intended for mission-critical, high-security online transaction processing (OLTP) and data warehousing environments.

    • Standard Edition—This installation type is suitable for workgroup or department-level applications, and for small to medium-sized enterprises. It provides core relational database management services and options.

    • Personal Edition (Microsoft Windows operating systems only)—This installation type installs the same software as the Enterprise Edition, but supports only a single-user, development and deployment environment.

    • Custom Install—This installation type enables you to customize the Enterprise Edition. Use Custom Install to add a component to your existing installation that would not usually be installed, or to prevent certain components from being installed.

  • Do you want to create a database in addition to installing the Oracle Database software?

    You can install a preconfigured database or a custom-configured database.

    Preconfigured databases are based on templates that Oracle provides or that you create. Each Oracle-provided template is optimized for a particular workload type. See Table 2-2, "Oracle-Provided DBCA Templates and Their Corresponding Workloads" for information about the types of preconfigured databases.

    To create a custom database in which you configure your own database structure, see "Advanced Installation".


    Note:

    If you need to create a new database, Oracle recommends that you install a preconfigured database, which is faster and easier. You can customize the database after it has been created.

  • What are your database configuration options?

    These options include your global database name and system identifier (SID), whether or not you want the sample schemas installed, and the passwords for the administrative accounts. The SID is a unique identifier that is used to distinguish this instance from other Oracle Database instances that you may create later and run concurrently on your system.

    The global database name is the full name of the database that uniquely distinguishes it from any other database. The global database name is in the form database_name.database_domain, for example sales.example.com. The database name portion sales is a simple name you call your database. The database domain portion example.com specifies the database domain in which the database is located. Together, the database name and domain make up the global database name.

    During basic installation, Oracle Database automatically installs the sample schemas.

    You will also be prompted to enter the desired passwords for the SYS and SYSTEM accounts, which enable you to manage and administer the database.

Advanced Installation

During advanced installations, you are prompted to make the choices listed in this section, in addition to the basic options. The installation process provides default values for every choice.

The advanced installation choices are described, but the advanced installation steps are not documented in this chapter. For more information, see Oracle Database Installation Guide for your platform.

During an advanced installation, you are asked the following questions:

  • Install the sample schemas?

    To complete the exercises in this guide and related course material, you must install the sample schemas. This data is also used in most examples throughout Oracle Database documentation. Oracle recommends that you install the sample schemas.

    This choice is a configuration option only during advanced installation. The default is No for this option with the advanced installation. However, sample schemas are installed by default during basic installation.

  • What kind of storage mechanism do you want your database to use?

    A database includes several files that store the user data, database metadata, and information required to recover from failures. As an administrator, you decide what kind of storage subsystem to use for these files. You can select from the following options:

    • File System—This default option creates database files that are managed by the file system of your operating system. You can specify the directory path where database files are to be stored. Oracle Database can create and manage the actual files.

      If you are not certain about which option to use, select File System (the default).

    • Automatic Storage ManagementThis option enables you to define pools of storage called disk groups, in which Oracle Database automatically manages database file placement and naming. For environments with a large number of disks, this option simplifies database administration and maximizes performance. Automatic Storage Management (ASM) performs software striping and mirroring at the file level for maximum storage flexibility, performance, and availability.

      ASM uses an ASM instance, which is distinct from the database instance, to configure and manage disk groups. OUI guides you through the creation and starting of an ASM instance and its components. For more information, see "About Automatic Storage Management" and Oracle Database Storage Administrator's Guide.

    • Raw Devices—This option enables you to manage your storage devices outside of the operating system file system by providing Oracle Database with unformatted physical disk space called raw devices. This method is primarily used in Oracle Real Application Clusters (Oracle RAC) environments. If you select this option, ensure that the raw devices were created with an operating system command, and that they are not being used for any other purpose or by other Oracle databases.

  • What are your database management options?

    You specify whether to manage your database centrally or locally using Oracle Enterprise Manager. Central management enables you to manage multiple targets, such as databases and application servers, using a single interface. Using local management you can manage only a single database instance at a time.

    If you want to use central management, it requires an Oracle Enterprise Management agent to exist on each host, or computer that has Oracle Database software installed on it. These agents are responsible for monitoring all components on that host. If an agent is not found on the local host, then this option is disabled during installation.

    If you are setting up a single database for the first time, it is recommended that you configure local management with Oracle Enterprise Manager, which is the default. You can later install additional databases and configure central management using Enterprise Manager.

At the end of the interview, a summary window displays the options that you chose, the requirements for space based on those options, and the components that will be installed. If you chose to install a database, then this step is performed immediately after the software installation is complete.

Installing Oracle Database Software

This section briefly describes the steps for basic installation. Most steps are common to all platforms and involve running the Oracle Universal Installer. Platform-specific steps are noted. For further assistance, consult the online Help or the Oracle Database Installation Guide for your platform.

Note:

The following steps describe the Oracle Universal Installer workflow for a host computer that has no previous Oracle software installed. If your host computer already has Oracle software installed, you may see a different workflow.

To perform a basic installation:

  1. Log on to your computer as a member of the administrative group that is authorized to install Oracle Database software and to create and run the database.

    Refer to your operating system-specific documentation or contact your system administrator to determine whether or not you have the necessary privileges and permissions to install new software.

  2. Do one of the following:

    • If you are installing from distribution media, then insert the distribution media for the database into your computer.

      The Autorun feature opens the Select a Product to Install window automatically.

    • If you downloaded the installation software from the Oracle Web site, then follow the instructions on the site to run the Oracle Universal Installer. Or, see the Oracle Database Installation Guide for your platform.

  3. If the Select a Product to Install window is displayed, select Oracle Database 11g, and then click Next.

    The Select Installation Method Window appears.

    Figure 2-1 Oracle Universal Installer Select Installation Method Window

    Description of Figure 2-1 follows
    Description of "Figure 2-1 Oracle Universal Installer Select Installation Method Window"

  4. Select Basic Installation and provide the configuration details for the database.

    In the Select Installation Method window you choose either Basic or Advanced Installation. Select the Basic Installation method to quickly install Oracle Database. This method requires minimal user input. It installs the software and optionally creates a general-purpose database based on the information you provide.

    When you choose Basic Installation you must also provide the following information:

    • Oracle Home and Oracle Base Location—You must specify a new Oracle home directory for each new installation of Oracle Database software.

      By default, the Oracle home directory is a subdirectory of the Oracle base directory. See the Oracle Database Installation Guide for your platform for more information about ORACLE_BASE.

      If you did not set the ORACLE_BASE environment variable before starting OUI, the Oracle home directory is created in an app/username/directory on the first existing and writable directory from /u01 through /u09 for UNIX and Linux systems, or on the disk drive with the most available space for Windows systems. If /u01 through /u09 does not exist on the UNIX or Linux system, then the default location is user_home_directory/app/username.

      You can click Browse to find the directory where you want to install the Oracle Database software.

    • Installation Type—Select either Enterprise Edition, Standard Edition, Standard Edition One, or Personal Edition (Microsoft Windows platforms only). See "Basic Installation".

    • UNIX DBA Group (Linux and UNIX platforms only)—Specify the operating system DBA group. Host computer users in this group have administrative privileges on the database. This group is typically named dba. Refer to Oracle Database Installation Guide for Linux or for your UNIX platform for more details.

    • Create Starter Database—Select this option to create a preconfigured database during installation. Oracle recommends that you select this option for first-time installations. You must enter a Global Database Name and Database Password for the SYS, SYSTEM, SYSMAN, and DBSNMP administrator accounts. The global database name is described in "Basic Installation".

    You can choose the Advanced Installation option if you want to customize your installation. For example, you use this method to configure Automatic Storage Management for your database, install the Sample Schemas, configure a specific character set for your database, or configure automated backups. Selecting this option guides you through a series of installation steps that are not documented in this guide. For more information about the advanced choices, see "Advanced Installation". Also see Oracle Database Installation Guide for your platform.

    After you select Basic Installation and enter the required information, click Next. The Preparing to Install progress bar appears.

  5. For first time installations on Linux and UNIX operating systems only, specify a directory for installation files and the name of an operating system group that has write permissions for that directory.

    If this is the first time you are installing any Oracle software on this computer, then the Specify Inventory Directory window appears. You must specify a local for the inventory, which OUI uses to keep track of all Oracle software installed on the computer. This information is used while applying patches or upgrading an existing installation, and while deinstalling Oracle software. Note that this directory is different from the Oracle home directory, which you specify later. The recommended value for the inventory directory is Oracle_base/oraInventory, where Oracle_base is the location of your Oracle base directory.

    In this window you can also specify the operating system group that has write permissions on the inventory directory. This prevents other users from writing over the Oracle product installation files.

    After you enter a directory path and optionally specify an operating system group, click Next to continue.

    The Product-Specific Prerequisite Checks window appears.

  6. For Linux and UNIX operating systems only, after verifying that your system meets the minimum requirements for installing and configuring the chosen products, click Next.

    OUI performs a number of environment checks and indicates whether the check was a success, or resulted in a warning or failure. Details of the checks are provided in the displayed window. The installation can proceed only when all checks have a status of either Succeeded or Warning. If any of the environment checks failed, they must be resolved manually. See "Checking Prerequisites" for more information.

    After you click Next, the Oracle Configuration Manager Registration window appears.

  7. In the Product-Specific Prerequisite Checks window, ensure that all checks succeeded, and then click Next. If any checks failed, take corrective actions.

  8. In the Oracle Configuration Manager Registration window, click Next without enabling Oracle Configuration Manager.

    Oracle Configuration Manager is used to collect and upload the configuration information to the Oracle configuration repository. Using Oracle Configuration Manager can help to reduce time for resolution of support issues and allow you to receive problem avoidance information. You can configure this option later, after the database installation is complete.

    After you click Next, a summary window appears, showing information such as your global settings, space requirements, and the new products to be installed.

  9. Review the installation summary, then click Install to start the installation.

    The Install window appears, showing the installation progress. At the end of the installation phase, the Configuration Assistants window appears. This window lists the configuration assistants that are started automatically. If you chose to create a starter database, then Database Configuration Assistant starts automatically in a separate window.

    At the end of database creation, a window is displayed that summarizes the database creation.

  10. (Optional) Click Password Management to unlock user accounts to make the accounts accessible to users.

    The SYS, SYSTEM, SYSMAN, and DBSNMP accounts are unlocked by default.

  11. Click OK to continue the installation.

  12. For Linux and UNIX operating systems only, run the specified scripts, then click OK.

    In the Execute Configuration Scripts window, you are prompted to open a new terminal window, and to run scripts as the root user. After you run the scripts, return to this window and click OK.

  13. Make note of the information in the End of Installation window, then click Exit to exit OUI. In the confirmation window, click Yes.

    Your installation and database creation is now complete. The End of Installation window displays one or more important URLs, including one for the Oracle Enterprise Manager Database Control console. (The console is the user interface—the Web application—portion of Oracle Enterprise Manager Database Control.) You can go to this URL with your browser and log in as the SYS user with the associated password, and connect as SYSDBA. You use Oracle Enterprise Manager Database Control to perform common database administration tasks. See Chapter 3, "Getting Started with Database Administration".

    The URL and port information for Database Control can be found after installation in the Oracle_home/install/portlist.ini file.

Creating and Managing a Database with DBCA

During Oracle Database installation, if you choose to create a starter database (see Step 4), Oracle Universal Installer automatically runs Database Configuration Assistant (DBCA) after software installation is complete. DBCA then guides you through the steps to create the database. If you do not create a starter database and later want to create one, or if you want to create additional databases, then you use DBCA.

Note:

With Oracle Database, you typically have a single database that hosts more than one application. You do not need multiple databases to run multiple applications. Instead, you separate the objects that support each different application into different schemas in the same database. However, there may be situations in which you want to create more than one Oracle database on the same host computer. When you do this with DBCA, the new databases typically use the same Oracle home directory as the first database, but store database data files separately from those of the first database.

DBCA also enables you to modify a database configuration, delete a database, and more. This section describes the following DBCA tasks:

Online Help is available by clicking Help. It provides information that guides you in selecting configuration options.

Starting DBCA

Follow the steps in this section to start DBCA.

Note:

If you choose to create a starter database while installing the Oracle Database software, OUI automatically starts DBCA.

To start DBCA:

  1. Log on to your computer as a member of the administrative group that is authorized to install Oracle Database software and to create and run the database.

  2. Do one of the following:

    • To start DBCA on a Microsoft Windows operating system, click Start, select Programs (or All Programs), then Oracle - HOME_NAME, then Configuration and Migration Tools, and then Database Configuration Assistant.

    • To start DBCA on UNIX or Linux, or at the command-line prompt on the Windows operating system, enter the following command:

      dbca
      

      The dbca utility is typically located in the Oracle_home/bin directory.

  3. Click Next to bypass with Welcome window.

Creating a Database Using DBCA

DBCA enables you to create an Oracle database by following a step-by-step guided workflow.

To create a database using DBCA:

  1. Start DBCA as described in "Starting DBCA".

  2. In the Operations window, select Create a Database and click Next to start the guided workflow for creating a database. The workflow requests your input in the following windows:

The following sections provide details on each window. Most windows provide default settings.

Step 2 - Database Templates

This window enables you to select the type of database that you want to create. You can use DBCA to create a database from templates supplied by Oracle or from templates that you create. The templates contain settings optimized for a particular type of workload.

Oracle ships templates for the following two workload types:

  • General purpose or transaction processing

  • Data warehouse

Click Show Details to see the configuration for each type of database. Select the template suited to the type of workload your database will support. If you are not sure which to choose, select the default General Purpose or Transaction Processing template.

For more complex environments, you can select the Custom Database option. This option does not use templates and results in a more extensive interview, which means that it will take longer to create your database.

For more information about using database templates, see "Managing Templates with DBCA".

Step 3 - Database Identification

In the Global Database Name field, enter the database name in the form database_name.domain_name.

In the SID field, enter the system identifier. The SID defaults to the database name and uniquely identifies the instance that runs the database.

Step 4 - Management Options

Use this window to set up your database so it can be managed with Oracle Enterprise Manager. Oracle Enterprise Manager provides Web-based management tools for individual databases, and central management tools for managing your entire Oracle environment.

Select Configure Enterprise Manager to use Enterprise Manager. Then, select one of the following options:

  • If the Oracle Management Agent is installed on your host computer, then you can choose central management by selecting Register with Grid Control for centralized management and then selecting the Management Service.

  • To manage your database locally, select Configure Database Control for local management. You can then optionally configure email notification of database alerts or a daily backup of the database.

Step 5 - Database Credentials

In this window, specify the passwords for the administrative accounts such as SYS and SYSTEM.

Step 6 - Storage Options

In this window, specify the type of storage mechanism you would like your database to use. For more information, see "Advanced Installation".

Step 7 - Database File Locations

In this window, specify the Oracle software home and the directory path in which to create the database files. Select one of the following options:

  • Use Database File Locations from Template—This option instructs DBCA to use the directory information as specified in the template. Later, you can make modifications to database file names and locations.

  • Use Common Location for All Database Files—This option requires you to specify a new directory for the Oracle home. All the database files will be created in this location. Later, you can make modifications to database file names and locations.

  • Use Oracle-Managed Files—This option instructs Oracle Database to directly manage operating system files comprising an Oracle database. You specify the default location, called a database area, for all your files. Oracle Database thereafter automatically creates and deletes files in this location, as required. You can also create multiple copies of your redo and online log files by selecting Multiplex Redo Logs and Control Files. To learn more about redo logs and control files, see Chapter 9, "Performing Backup and Recovery".

    Selecting this option enables you to delegate the complete management of database files to the database. You no longer need to specify the file names, location, or their sizes.

Step 8 - Recovery Configuration

When you create a new database, it is important to configure the database so you can recover your data in the event of a system failure. Redo logs contain a record of changes that were made to datafiles. Redo logs are stored in redo log groups, and you must have at least two redo log groups for your database. After the redo log files in a group have filled up, the log writer process (LGWR) switches the writing of redo records to a new redo log group. Oracle Database can automatically save the inactive group of redo log files to one or more offline destinations, known collectively as the archived redo log (also called the archive log). The process of turning redo log files into archived redo log files is called archiving.

Archiving can be performed only if the database is running in ARCHIVELOG mode. This means a group of redo log files cannot be reused by the log writer (LGWR) process until the group is archived. If the database is running in NOARCHIVELOG mode, then when a group becomes inactive after the LGWR process switches to a new group, the inactive group is available for immediate reuse by the LGWR process.

The NOARCHIVELOG mode protects a database from instance failure but not from media failure. Only the most recent changes made to the database, which are stored in the online redo log groups, are available for instance recovery. To restore a database operating in NOARCHIVELOG mode, you can use only entire database backups taken while the database is closed. Therefore, if you decide to operate a database in NOARCHIVELOG mode, back up the entire database at regular, frequent intervals.

The archiving of redo log files has these advantages:

  • A database backup, together with online and archived redo log files, guarantees that you can recover all committed transactions in the event of an operating system or disk failure.

  • You can recover the database using a backup that was taken while the database was open and being used, as long as you have a copy of the archived log files that were written while the database was being backed up.

  • You can perform online tablespace backups, and use these backups to restore a tablespace following media failure.

  • You can keep a standby database current with its original database by continuously applying the original archived redo logs to the standby database.

Before you can archive redo logs, you must determine the destination to which you will archive. Oracle recommends that the archive log be stored in a flash recovery area because it can simplify backup and recovery operations for your database. A flash recovery area is a location in which Oracle Database can store and manage files related to backup and recovery. It is distinct from the database area, which is a location for the current database files (datafiles, control files, and online redo logs).

When creating your database, you can select the following options:

  • Specify Flash Recovery Area—Select this option to specify a backup and recovery area and its directory location and size. You can use variables to identify standard locations.

  • Enable Archiving—Select this option to enable the archiving of database redo logs, which can be used to recover a database. Selecting this option is the same as enabling Archive Log Mode in Oracle Enterprise Manager Database Control or running the database in ARCHIVELOG mode.

    Oracle recommends you select Enable Archiving. Selecting this option provides better protection for your database in the case of software or hardware failure. If you do not select this option now, you can enable ARCHIVELOG mode later. See "Configuring Your Database for Basic Backup and Recovery".

Step 9 - Database Content

When you create your database, you can load it with data using either of the following methods:

  • Sample Schemas—Select Sample Schemas to include the Sample Schemas (EXAMPLE) tablespace in your database. Oracle guides and educational materials contain examples based upon the Sample Schemas. Oracle recommends that you include them in your database.

  • Custom Scripts—In the Custom Scripts subpage, optionally specify one or more SQL scripts to run after your database is created. Scripts are useful for performing postinstallation tasks, such as loading custom schemas. Note that if you choose to run scripts after installation, your scripts must include a connection string that identifies the database. Click Help for more information.

Step 10 - Initialization Parameters

The links in this window provide access to additional windows that enable you to change the default initialization parameter settings. These parameters fall into the following categories:

You can also click the All Initialization Parameters button at the bottom of the window to display a list of all the database initialization parameters and their current settings.

Memory

Use this window to set the initialization parameters that control how the database manages its memory. You can choose from one of the following methods for memory management:

  • Typical—This method requires little configuration, and allocates memory as a percentage of total overall physical system memory. Select Typical and enter a percentage value. Click Show Memory Distribution to see how much memory DBCA assigns to the System Global Area (SGA) and the aggregate Program Global Area (PGA). With this setting, the system automatically tunes many of the memory components of the SGA, and allocates memory to individual PGAs as needed. The system can also dynamically decrease or increase the total amount of memory allocated to the SGA or aggregate PGA, depending on processing demands. The total memory used for the database instance never exceeds the amount you specify. This automatic memory tuning for the instance is known as automatic memory management. To learn more about PGA and SGA, see "About Instance Memory Structure".

  • Custom—This method requires more configuration than the Typical option, but gives you more control over how the database uses system memory. This option is meant for more experienced database administrators. You can directly specify memory sizes for the SGA and aggregate PGA and their substructures, such as the shared pool and buffer cache.

    Select one of the following options for customized memory management:

    • Automatic Shared Memory Management to allocate specific amounts of memory to the SGA and aggregate PGA. With this setting, automatic shared memory management is enabled for the SGA, and memory is allocated to the individual PGAs as needed.

    • Manual Shared Memory Management to enter specific values for each SGA component and the aggregate PGA. This disables automatic shared memory management and enables you to determine how the SGA memory is distributed among the SGA memory components.

See Also:

Sizing

In this tab, you specify the smallest block size and the maximum number of operating system user processes that can simultaneously connect to the database.

  • Block Size—Use this list to select the block size, or accept the default. Oracle Database data is stored in data blocks of the size specified. One data block corresponds to a specific number of bytes of physical space on disk. Selecting a block size other than the default 8 kilobytes (KB) value requires advanced knowledge and should be done only when absolutely required.

    While using predefined templates, this list is not enabled because the database will be created with the default block size of 8 KB. While using the custom option, you can change the block size.

  • Processes—In this field, specify the maximum number of processes that can simultaneously connect to the database. Enter a number or accept the default value of 150. The default value for this parameter is appropriate for many environments. The value you select should allow for all background processes, user processes, and parallel execution processes.

Character Sets

Use this tab to define the character sets used by your database. Character sets are the encoding schemes used to display characters on your computer screen. The character set determines what languages can be represented in the database.

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. The default character set suggested or used by Oracle Universal Installer and Database Configuration Assistant is based on the language configuration of the local operating system. If you choose to use a different character set, choose the character set most frequently used by the clients connecting to this database, for example WE8MSWIN1252. You might choose this character set if most clients connecting to the database run under the Microsoft Windows operating system.

  • Database Character Set—In this section, select from one of the following options:

    • Use the Default—Select this option to support only the language currently used by the operating system for all your database users and database applications.

    • Use Unicode (AL32UTF8)—Select this option to support multiple languages for your database users and database applications.

    • Choose from the list of character sets—Select this option if you want Oracle Database to use a character set other than the default character set used by the operating system.

  • National Character Set—In this list, select a character set or accept the default. The national character set is an alternative character set that enables you to store Unicode characters in a database that does not have a Unicode database character set. Choosing a national character set can make programming for multiple languages easier.

  • Default Language—In this list, select a default database language or accept the default. The default language determines how the database supports locale-sensitive information such as day and month abbreviations, default sorting sequence for character data, and reading direction (left to right or right to left).

  • Default Territory—In this list, select the name of the territory whose conventions are to be followed for day and week numbering or accept the default. The default territory also establishes the default date format, the default decimal character and group separator, and the default International Standardization Organization (ISO) and local currency symbols. For example, in the United Kingdom, the default date format is DD-MON-YYYY, where DD is the day of the month (1-31), MON is the abbreviated name of the month, and YYYY is the 4-digit year.

Connection Mode

Use this window to select the database mode. You can run the database in either of the following modes:

  • Dedicated Server Mode—This mode allows a dedicated server process for each user process. Select this option when the number of total clients is expected to be small, for example, 50 or fewer. You might also choose this option when database clients will typically make persistent, long-running requests to the database. By default, the database is configured for dedicated server processes.

  • Shared Server Mode—This mode allows several client connections to share a database-allocated pool of resources. Use this mode in configurations in which client load is expected to cause a strain on memory and other system resources. If you choose shared server mode, then you must indicate the number of server processes you want to create when a database instance is started. For more information about setting this parameter, click Help.

Step 11 - Security Settings

In this window, choose to use either the enhanced default security settings or the settings of a previous release, optionally disabling certain security features. The enhanced security settings include case-sensitive passwords.

Step 12 - Automatic Maintenance Tasks

On this page you decide whether or not you want to enable the automatic maintenance tasks feature of Oracle Database 11g. Automated maintenance tasks are tasks that are started automatically at regular intervals to perform maintenance operations on the database. They are:

  • Automatic Optimizer Statistics Collection—Collects optimizer statistics for all schema objects in the database for which there are no statistics or only stale statistics.

  • Automatic Segment Advisor—Identifies segments that have space available for reclamation, and makes recommendations on how to defragment those segments.

  • Automatic SQL Tuning Advisor—Examines the performance of high-load SQL statements, and makes recommendations on how to tune those statements.

See Oracle Database Administrator's Guide for more information.

Step 13 - Database Storage

In this window, a navigation tree displays the storage structure of your database (control files, datafiles, redo log groups, and so forth). If you are not satisfied with the storage structure or parameters, then you can make changes.

Note that if you selected one of the preconfigured templates for a database, then you cannot add or remove control files, datafiles, or undo segments.

Step 14 - Creation Options

In this window, select any of the following options for creating the database:

  • Create Database—Select this option to create your database at this time.

  • Save as a Database Template—Select this option to save the database definition as a template to use at a later time.

  • Generate Database Creation Scripts—Select this option to generate a SQL database creation script that you can run at a later time.

After you make your choice, click Finish. A confirmation window appears after a short period of time. Review the information, and click OK to proceed.

Changing the Configuration of a Database Using DBCA

You can use DBCA to change the configuration of an existing database. For example, you can:

  • Change default security settings

  • Change server mode from dedicated to shared, or the reverse

  • Add database options that were not previously configured (for example, Oracle Label Security or Oracle OLAP)

To change the configuration of a database using DBCA:

  1. Start DBCA as described in "Starting DBCA".

  2. In the Operations window, select Configure Database Options and click Next.

  3. Follow the instructions in the DBCA guided workflow.

Deleting a Database Using DBCA

You can also use DBCA to delete a database. When DBCA deletes a database, it shuts down the database instance and then deletes all database files. On the Windows platform, it also deletes associated Windows services.

To delete a database using DBCA:

  1. Start DBCA as described in "Starting DBCA".

  2. In the Operations window, select Delete a Database and click Next.

  3. Select the database to delete and click Finish.

Managing Templates with DBCA

DBCA templates are XML files that contain information required to create a database. Templates are used in DBCA to create new databases and duplicate existing databases. The information in templates includes database options, initialization parameters, and storage attributes (for datafiles, tablespaces, control files, and online redo logs).

Templates can be used just like scripts, but they are more powerful than scripts because you have the option of duplicating a database. Duplication saves time because you copy the files of an existing database, referred to as a seed database, to the correct locations.

Templates are stored in the following directory:

Oracle_home/assistants/dbca/templates

Advantages of Using Templates

Using templates has the following advantages:

  • Time saving. If you use a template, you do not have to define the database.

  • Easy duplication. By creating a template containing your database settings, you can easily create a duplicate database without specifying parameters twice.

  • Easy editing. You can quickly change database options from the template settings.

  • Easy sharing. Templates can be copied from one computer to another.

Types of Templates

Templates are divided into the following types:

  • Seed templates

  • Nonseed templates

The characteristics of each are shown in Table 2-1.

Table 2-1 DBCA Template Types

Type File Extension Includes Datafiles Database Structure

Seed

.dbc

Yes

This type of template contains both the structure and the physical datafiles of an existing database, referred to as the seed database. Your new database starts as a copy of the seed database, and requires only the following changes:

  • Name of the database

  • Destination of the datafiles

  • Number of control files

  • Number of redo log groups

  • Initialization parameters

Other changes can be made after database creation using custom scripts that can be invoked by DBCA, command-line SQL statements, or Oracle Enterprise Manager Database Control.

The datafiles for the seed database are stored in compressed RMAN backup format in a file with a .dfb extension. The seed database control file is stored in a file with .ctl extension. (This file is needed only when storing datafiles in Automatic Storage Management (ASM) disk groups or as Oracle managed files.) The .dbc file contains the location of the seed database datafiles and contains the source database name used to mount the control file.

Nonseed

.dbt

No

This type of template is used to create a new database. It contains the characteristics of the database to be created. Nonseed templates are more flexible than their seed counterparts because all datafiles and online redo logs are created to your specification, and names, sizes, and other attributes can be changed as required.


DBCA Templates Provided by Oracle

Oracle provides the templates shown in Table 2-2.

Table 2-2 Oracle-Provided DBCA Templates and Their Corresponding Workloads

Template Workload

Data warehouse

Users perform numerous, complex queries that process large volumes of data. Response time, accuracy, and availability are key issues.

These queries (SELECT statements) range from a fetch of a few records to queries that sort thousands of records from many different tables.

General Purpose or Transaction processing

Many concurrent users perform numerous transactions that require rapid access to data. Availability, speed, concurrency, and recoverability are key issues.

Transactions consist of reading (SELECT statements), writing (INSERT and UPDATE statements), and deleting (DELETE statements) data in database tables.

Custom database

This template allows you maximum flexibility in defining a database because you can change any of the settings for the database being created.


Creating Templates Using DBCA

Follow the instructions in this section to create your own templates.

To create templates:

  1. Start DBCA as described in "Starting DBCA".

  2. In the Operations window, select Manage Templates and click Next.

  3. In the Template Management window, select one of the following options, and click Next.

    • From an existing template

      Using an existing template, you can create a new template based on the predefined template settings. You can add or change any template settings such as initialization parameters, storage parameters, or whether or not to use custom scripts.

    • From an existing database (structure only)

      You can create a new template that contains structural information from an existing database, including database options, tablespaces, datafiles, and initialization parameters. User-defined schemas and their data will not be part of the created template. The source database can be either local or remote. Select this option when you want the new database to be structurally similar to the source database, but not contain the same data.

    • From an existing database (structure as well as data)

      You can create a new template that has both the structural information and physical datafiles of an existing database. Databases created using such a template are identical to the source database. User-defined schemas and their data will be part of the created template. The source database must be local. Select this option when you want a template from which you can create an exact replica of the source database.

    When creating templates from existing databases, you can translate file paths into Optimal Flexible Architecture (OFA) or maintain existing file paths. OFA is a set of file naming and placement guidelines for Oracle software and databases. Using OFA is recommended if the target computer on which you plan to create a database using the template has a different directory structure than computer on which the template was defined. Standard file paths can be used if the target computer has a directory structure that is similar to the directory structure on the source computer.

  4. Follow the instructions in the DBCA guided workflow to create your template.

Deleting Templates

When you delete a template, it is no longer available to create a new database or a new template.

To delete a template:

  1. Start DBCA as described in "Starting DBCA".

  2. In the Operations window, select Manage Templates and click Next.

  3. In the Template Management window, select Delete a database template and click Next.

  4. Select the template to delete and click Finish.

Configuring Automatic Storage Management Using DBCA

You can also use DBCA to configure Automatic Storage Management (ASM) as a separate operation from creating a database. In this case, DBCA creates the ASM instance in its own Oracle home instead of using the Oracle home of a database. After you create the ASM instance and define disk groups, you can then perform a separate DBCA operation to create a database that uses those disk groups for storing database files. Creating an ASM instance in its own Oracle home is recommended, and has the advantage of enabling more than one Oracle database to use the ASM disk groups. This configuration differs from the configuration that you can choose with advanced installation as described in "Advanced Installation", in which you create a database, and as part of the database creation process, you create an ASM instance that uses the same Oracle home as the database. See the installation and platform guides for your environment for more information. For an overview of ASM, see Appendix A, "Administering Automatic Storage Management". For more detailed information, see Oracle Database Storage Administrator's Guide

To configure Automatic Storage Management using DBCA:

  1. Configure Cluster Synchronization Services (CSS) by running the following command as the root user (UNIX and Linux) or as an administrative user (Windows):

    Oracle_home/bin/localconfig add
    
  2. Start DBCA as described in "Starting DBCA".

  3. In the Operations window, select Configure Automatic Storage Management, and then follow the guided workflow to create and start the ASM instance and create disk groups.

Installation: Oracle By Example Series

Oracle By Example (OBE) has a series on the Oracle Database 2 Day DBA guide. This OBE steps you through the tasks in this chapter and includes annotated screenshots.

To view the Installation OBE, in your browser, enter the following URL:

http://www.oracle.com/webfolder/technetwork/tutorials/obe/db/11g/r1/2day_dba/install/install.htm