Ensure that you have followed the installation procedure of VMware Guest Operating System (http://www.oracle-forums.com/installing ... 2-t25.html) and Oracle Database 10g Software (http://www.oracle-forums.com/installing ... -t687.html)
Procedure:
- Login to your VMware.
- Set correct ORACLE_HOME
[oracle@oracle10g ~]$ export ORCLE_HOME=/u01/app/oracle/product/10.2.0/db_1
[oracle@oracle10g ~]$ echo $ORACLE_HOME
/u01/app/oracle/product/10.2.0/db_1
[oracle@oracle11g ~]$
[oracle@oracle10g ~]$ dbca
- Welcome
Welcome to the Database Configuration Assistant. After you install the Oracle Database software, you can use the Database Configuration assistant to create and configure your databases.
*** Overview of the Database Configuration Assistant
The Database Configuration Assistant guides you through the process of creating a new database, changing the configuration of an existing database, or deleting a database. Many of the database creation tasks you would normally perform manually are performed automatically after you select your database options with the Database Configuration Assistant. With the Database Configuration Assistant you can select from a list of pre-defined database templates, or you can use an existing database as a sample for creating a template. If you are using Real Application Clusters, you can use the Database Configuration Assistant to manage the instances and services associated with your Real Application Cluster environment. Note: Oracle recommends that you close other applications when running Database Configuration Assistant.
*** Notes for Real Application Cluster Users
Before the Database Configuration Assistant can create a Real Application Clusters database, you must complete the preinstallation tasks, and you must have completed the two-phase installation process for installing CRS (Cluster Ready Services) and the Oracle Enterprise Edition 10g with Real Application Clusters.
In addition, depending upon the type of database storage that you want to use, you should perform one of the following setup procedures before invoking the Database Configuration Assistant to create a RAC database.
# Set up raw disks on shared storage and use Oracle Automated Storage Manager (ASM) for database storage. DBCA will prompt you through the process of creating your ASM instance and defining your ASM disk groups.
# If your platform supports cluster file system, use cluster file system partition for database storage.
# Set up raw devices on shared storage and use these devices for storing database files.
For more information about configuring your disks, refer to the preinstallation procedures for your platform, as described in .
*** The Database Configuration Assistant enables you to create database, configure database options in an existing database, delete a database, and manage database templates.
Use this page to select the database configuration task that you want to perform with Database Configuration Assistant. The following table summarizes the tasks that you can select.
Note: Oracle recommends that you close other applications before performing these tasks.
# Create a Database: This option guides you through the steps of creating a new database or template. When you select a template, you can choose either a custom database template or a template with data files. If you select a custom database template (with no data files), you can save the database creation information as a script, which you can later use to create similar databases.
# Configure Database Options: This option guides you through the steps of changing your configuration from a dedicated server to a shared server. You can also add database options that have not been previously configured for use with your database.
# Delete a Database: This option deletes all the files associated with a selected database.
# Manage Templates: This option guides you through the steps of creating and managing database templates. Database templates save you time by saving your database definition to an XML file format on your local hard disk. The Database configuration Assistant provides several pre-defined templates you can use to create your databases. For more information, see Database Templates.
If you select the Manage Templates option, you have three ways to create a template:
@ From an existing template: create a new template using pre-defined template settings. You can add or change any template settings such as parameters, storage, or use custom scripts.
@ From an existing database (structure only): create a new template that has a structure identical to the existing database. This includes tablespaces and storage. You can use an existing database that is either local or remote.
@ From an existing database (structure as well as data): create a template that has both the structure and data of an existing database. You can only use an existing local database.
- Choose Create a Database
*** You can select the operation that you want to perform: Create a Database (choose this), Configure Database Options, Delete a Database, Manage Templates or Configure Automatic Storage Management
Use the Database Templates page to select a template. The Database Configuration Assistant shows this page when you are creating a new database and when you are managing your database templates.
*** About Database Templates
Database templates are XML files on your local hard disk that store database configuration information. Database Configuration Assistant provides several prepackaged templates, but you can also create your own templates.
Templates provide the following benefits:
@ Create a duplicate database without specifying all the database parameters again.
@ Quickly change database options from the template settings.
@ Share templates by copying the template from one machine to another.
A template may or may not contain data files. The following sections provide more details about templates with and without data files.
*** Selecting Templates Without Data Files
Templates without data files contain only the structure of the database and gives you full control to specify and change all database parameters. You will also be able to save the database creation information as a script.
Note: If you select a template without data files, database creation will take longer because all scripts must be run to create the schema.
*** Selecting Templates With Data Files
Templates that include data files contain both the structure and the physical data files of the existing database. If you select a template that also includes data files, the database is created faster since the schema is present in the data files. Also, all logfiles and control files are automatically created for the database. You can add/remove control files, log groups, change the destination and name of data files.
Important: If you select a database template that includes data files, you will not be able to add or remove data files, tablespaces, or rollback segments. Selecting this type of template allows you to change the following:
@ The name of the database
@ Destination of the data files
@ Controlfiles
@ Redo log groups
@ Initialization parameters
*** Viewing Template Information
After you select a template from the list, to find out complete details about the template, click Show Details. The detailed report is presented in HTML format. It shows the selected template's database creation parameters. Included in the report is information about initialization parameters, control files, data files, tablespace, database options, variables (if used), custom scripts (if used), and redo log groups.
- Select the 'General Purpose'
*** You can select a template from to create a database: Custom Database, Data Warehouse, General Purpose (choose this), or Transaction Processing.
Use this page to uniquely identify your Oracle Database. You identify your database using a global database name and a System Identifier (or SID).
*** Creating a Global Database Name
An Oracle database is uniquely identified by a Global Database Name. The global database name is the full name of the database which uniquely identifies it from any other database. The global database name is of the following form:
<database_name>.<database_domain>
For example, here is a typical global database name:
test.us.acme.com
The database name portion (in this example, test) is a simple name for your database. The database domain portion (in this case, us.acme.com) specifies the domain in which the database is located. When possible, Oracle recommends that your database domain mirror your network domain.
The database name portion of the global database name can be no more than 8 characters and can contain only contain only alphabetic and numeric characters.
The domain portion of the global database name can be no more than 128 characters and can contain only alphabetic and numeric characters, as well as the period (.) character.
*** Using a Database SID
The System Identifier (SID) identifies a specific instance of the Oracle Database sofware. For any database, there is at least one instance referencing the database. The SID can be any name that is not already used for another instance on this computer.
Note: In order to Change database configuration or Delete a database, you must define the SID (ORACLE_SID) environment variable in the shell from which Database Configuration Assistant is launched. If no SID is set, you cannot change database configuration settings or delete the database. If an incorrect SID is set, you can select these options in Database Configuration Assistant, but these options will not work.
Keep in mind the following platform-specific notes:
@ For Windows: Enter the system identifier (SID) for the database or accept the default SID. A SID is a unique identifier for an Oracle database instance that can be up to eight alphanumeric characters in length. Each database instance corresponds to a SID and a series of database files. For example, when you create a database with a SID of XXX, you also create the database instance and its database files (the initialization parameter file, control file, redo log files, and data files).
@ For UNIX: Enter the system identifier (SID) for the database. A SID is a unique name of up to eight characters in length for an Oracle database instance. Each database instance corresponds to a SID and a series of database files. For example, when you create a database with a SID of XYZ, you also create the database instance and its database files (the initialization parameter file, control file, redo log files, and data files) with names based on XYZ.
@ For Real Application Clusters: Instead of a SID, you provide a SID prefix for Real Application Clusters.
- Provide the Database name
*** An Oracle Database is uniquely identified by a Global Database Name, typically in the form "name.domain"
> Global Database Name: ORCL10G
*** A database is referenced by at least one Oracle instance which is uniquely identified from any other instance on this computer by an Oracle System Identifier (SID).
SID: ORCL10G
Use this page to set up your database so it can be managed with Oracle Enterprise Manager. Oracle Enterprise Manager provides Web-based management tools for managing individual database instances, as well as central management tools for managing your entire Oracle environment, including multiple databases, hosts, application servers, and other components of your network.
*** Using Grid Control for Database Management
When you run the Database Configuration Assistant, the assistant checks to see if the Oracle Management Agent has been installed on the host computer. If the assistant locates an Oracle Management Agent, select the Grid Control option and select an Oracle Management Service from the drop-down list. When you finish installing the Oracle Database, it will automatically be available as a managed target within the Oracle Enterprise Manager Grid Control.
You install the Oracle Enterprise Manager Grid Control and its related components from a separate CD-ROM, which is included in the Oracle Database CD-ROM pack.
For more information about centrally managing the databases, application servers, hosts, and other components of your network, see Oracle Enterprise Manager Concepts.
*** Using Database Control for Database Management
If you are not centrally managing your Oracle environment, you can still use Oracle Enterprise Manager to manage your database. When you install an Oracle Database, you automatically install the Oracle Enterprise Manager Database Control, which provides Web-based features for monitoring and administering the single-instance or clustered database you are installing.
To configure the database so it can be managed with the Oracle Enterprise Manager Database Control, select the Database Control option.
*** Enabling Email Notifications
When you select the Database Control management option, you can configure Enterprise Manager so that email notifications will be enabled immediately upon installation.
Select Enable Email Notifications if you want the SYSMAN user (the default Super Administrator and owner of the Management Repository schema) to receive email notification when a metric for a specified condition reaches a critical or warning threshold. For example, Enterprise Manager can send an email when a target goes down or when there are database space usage problems.
Use the following table to enter the information required in order for email notifications to work properly. If you do not provide the necessary information on this screen, email notification will not be enabled upon installation. You may set or change email notification settings using the Enterprise Manager Console after installation is complete. Refer to the Enterprise Manager online help for more information on notifications.
@ Outgoing Mail (SMTP) Server : Enter the name of the outgoing mail server; for example, mail.acme.com. For UNIX, the default SMTP server is the local host name. Use the fully-qualified host name (including domain).
@ Email Address : Specify the email address associated with the SYSMAN user to receive notifications. The address specified here will also serve as the sender's email address.
*** Enabling Daily Backups
If you select the Database Control management option, you can also enable automatic daily backups of your entire database.
Select Enable Daily Backups to use the Oracle-suggested backup strategy to back up your entire database with a minimum amount of configuration. Later, you can use Oracle Enterprise Manager to customize your backup strategy further. For more information, see the Oracle Enterprise Manager online help.
When you select this option, Enterprise Manager will be configured to back up your database, based on the scheduled start time you enter on this page, immediately after you finish installing the Oracle Database. Enterprise Manager will back up the database to the Flash Recovery Area that you specify later on the Recovery Configuration page of the Database Configuration Assistant.
After you select Enable Daily Backup, enter the following information, which is required in order to enable the automatic backup strategy:
@ Use the Backup Start Time fields to specify a time of day when the back up job will be submitted.
@ Use the OS Username and Password fields to enter the host credentials. The host credentials are required so Enterprise Manager can write to the disk recovery location, which is specified later on the Recovery Configuration page of the Database Configuration Assistant.
- Configure the Database with Enterprise Manager
*** Each Oracle database may be managed centrally using Oracle Enterprise Manager Grid Control or locally using the Oracle Enterprise Manager Database Control.
> Select "Use Database Control for Database Management"
> You may also Enable Email Notification of which you will have to provide Outgoing Mail (SMTP) Server and the Email Address to use.
> You may also Enable Daily Backup. With this option, you will have to set the Backup Start Time, OS Username and Password.
Use this page to secure your database with passwords for the most important database administrator accounts.
You can set a single password, which will be applied to each of these database user accounts, or enhance the security of the accounts by providing unique passwords for each.
The following table describes the accounts you must secure on this page:
@ SYS: The SYS users owns all base tables and user-accessible views of the data dictionary. No Oracle user should ever alter (update, delete, or insert) any rows or schema objects contained in the SYS schema, because such activity can compromise data integrity. The security administrator must keep strict control of this central account.
@ SYSTEM: The SYSTEM user is used to create additional tables and views that display administrative information, and internal tables and views used by various Oracle options and tools. The security administrator must keep strict control of this central account.
@ SYSMAN: The SYSMAN user represents the Enterprise Manager super administrator account. This Enterprise Manager administator can create and modify other Enterprise Manager administrator accounts, as well as administer the database instance itself.
@ DBSNMP: The DBSNMP user is used by Enterprise Manager to monitor the database. Enterprise Manager uses this account to access performance statistics about the database. The DBSNMP credentials sometimes referred to as the monitoring credentials.
For more information about the SYS and SYSTEM user accounts, see the Oracle Database Administrator's Guide.
For more information about the DBSNMP and SYSMAN accounts, see the Oracle Enterprise Manager online help after you install the database. For more information about Oracle Enterprise Manager, see Oracle Enterprise Manager Concepts.
- Specify the passwords
*** For security reasons, you must specify passwords for the following accounts in a new database. You can use the same passwords for all accounts or use different password for accounts SYS, SYSTEM, DBSNMP, and SYSMAN.
Use this page to select the storage mechanism you would like to use for your database files. Database files include the data files, control files, and log files associated with your database. The following table describes each of the available storage mechanisms you can select.
@ File System: Select File System to save and maintain your single-instance database files in a directory in your current file system. By default, DBCA will save the database files using the Optimal Flexible Architecture (OFA), whereby database files and administrative files, including initialization files, follow standard naming and placement practices.
You can modify these defaults later in the database configuration process by using the DBCA Database Storage page.
@ Cluster File System: For Real Application Clusters, this option replaces the File System option.
A cluster file system allows a number of nodes in a cluster to concurrently access a given file system. Every node sees the same files and data. This allows for easy management of data that needs to be shared across nodes.
If your platform supports a cluster file system, then you can use it to store your Real Application Cluster data files and controlfiles. See your platform-specific documentation for more information about cluster file sytem support. Information about Oracle Cluster File Systems is available on the Oracle Technology Network (OTN).
For example, a set of frequently asked questions about Oracle Cluster File Systems for Linux is available at:
http://otn.oracle.com/tech/linux/htdocs ... 31103.html
For more general information about storage options for Real Application Clusters, see Real Application Clusters Installation and Configuration.
@ Automatic Storage Management (ASM): Automatic Storage Management (ASM) is a new Oracle Database feature that simplifies the administration of database files. Instead of managing many database files, you manage only a small number of disk groups.
A disk group is a set of disk devices that ASM manages as a single, logical unit. You can define a particular disk group as the default disk group for a database and Oracle automatically allocates storage for and creates or deletes the files associated with the database object. When administering the database, you need only refer to database objects by name rather than by file name.
When you select this option, the Database Configuration Assistant displays a series of screens that you can use to create an ASM instance and populate your ASM disk groups.
For more information about the benefits and administration of ASM, see the chapter "Using Automatic Storage Management" in the Oracle Database Administrator's Guide.
Tip: After you set up an ASM instance with DBCA, you can use Oracle Enterprise Manager to manage your ASM instance. For more information, see the Oracle Enterprise Manager online help.
@ Raw Devices: A raw device is a disk or portion of a disk that is not managed by a file system. However, you can use this option only if your site has at least as many raw disk partitions as Oracle data files.
Before you can use raw devices to store your database files, you must configure and identify the raw devices. For example, you can use a mapping file to identify the raw device to be used for each database file. For information about creating an ASCII mapping file, see "Configuring Raw Devices for Real Application Clusters" in Real Application Clusters Installation and Configuration.
Note for Oracle Real Application Cluster users: Previous versions of Real Application Clusters required the use of raw devices instead of a file system for database files. As a result, you can learn about configuring raw devices in Real Application Clusters Installation and Configuration.
For Oracle Database 10g, Oracle Corporation recommends using Automatic Storage Management (ASM) with Oracle Managed Files (OMF), or a cluster file system with OMF for Real Application Clusters.
- Choose File System for Storage Options
*** Select the storage mechanism you would like to use for the database. File System: Use the File System for database storage; Automatic Storage Management (ASM): Automatic Storage Management (ASM) simplifies database storage administration and optimizes database layout for I/O performance. To use this option, you must either specify a set of disks to create an ASM disk group or specify an existing ASM disk group; RAW Devices: Raw partitions or volumes can provide the required shared storage for Real Application Cluster (RAC) databases if you do not use Automatic Storage Management and a Cluster File System is not available. You need to have created one raw device for each datafile, controlfile, and logfile you are planning to create in the database.
Use this page to specify where and how you want to store the database files. The options available on this page are described in the following table:
@ Use Datafile Locations from Template: Select this option to use the predefined location in the database template that you selected for this database. Even if you select this option, you will have an opportunity to review and make modifications to the database file names and locations on the Storage page, which is available later in the Database Configuration Assistant.
@ Use Common Location for All Files: Select this option to specify a new common area for all your database files. Even if you select this option and provide a new location, you will have an opportunity to review and make modifications to the database file names and locations on the Storage page, which is available later in the Database Configuration Assistant.
@ Use Oracle-Managed Files: Select this option to simplify the administration of your Oracle database. Oracle-Managed Files eliminate the need for you, the DBA, to directly manage the operating system files comprising an Oracle database. You specify operations in terms of database objects rather than filenames. Oracle internally uses standard file system interfaces to create and delete files as needed for tablespaces, redo log files, and control files.
Instead, you provide only the path to the Database Area, which serves as the root directory where the database stores its database files.
When you select this option, you can also multiplex the redo logs and control files. Click Multiplex Redo Logs and Control Files to identify multiple locations where duplicate copies of the files can be stored. Multiplexing provides greater fault-tolerance for the redo log and control file if one of the destinations fails.
Unlike the other options on this page, when you select this option, you cannot make modifications to the database files names on the Storage page, which is available later in the Database Configuration Assistant.
For more information about Oracle-Managed Files, see the chapter "Using Oracle-Managed Files" in the Oracle Database Administrator's Guide.
- Tick on Use Common Location for All Database Files then locate the database file locations.
*** You can specify the locations for the Database files to be created as: "Use Database File locations from Template", "Use Common Location for all Database files > Locate Database Files location", or "Use Oracle-Managed Files > Database Area".
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. Use this page to specify a flash recovery area and to enable archiving.
*** Specifying a Flash Recovery Area
The Flash Recovery Area can be used to recover data that would otherwise be lost during a system failure; this location is also used by Enterprise Manager if you have enabled local management and daily backups on the Management Options page shown previously in the Database Configuration Assistant.
The flash recovery area is an Oracle-managed directory, file system, or Automatic Storage Management disk group that provides a centralized disk location for backup and recovery files. Oracle creates archived logs in the flash recovery area. Enterprise Manager can store its backups in the flash recovery area, and it uses it when restoring files during media recovery. Oracle recovery components interact with the flash recovery area ensuring that the database is completely recoverable using files in flash recovery area. All files necessary to recover the database following a media failure are part of flash recovery area.
Use the Flash Recovery Area field to specify the location and size of your flash recovery area. You can use variables to identify some standard locations, such as the Oracle home. To review or add additional variables, click File Location Variables at the bottom of the Recovery Configuration page.
The flash recovery area serves as a type of disk cache for tape backups, shortening recovery times and allowing automated disk backup management. When you specify a flash recovery area, you must set the size of the recovery area in the Flash Recovery Area Size field.
*** Enabling Archiving
When you enable archiving, the database archives its redo logs. Archived redo logs can be used to recover a database, update a standby database, or to gain information about the history of a database using the LogMiner utility.
Enabling archiving is the same as turning on Archive Log Mode in Oracle Enterprise Manager or running the database in ARCHIVELOG mode. You must enable archiving to make the database recoverable from disk failure.
You can use the default archive log mode settings, you can click Edit Archive Mode Parameters to provide specific archive parameters for your database.
- Specify Flash Recovery Area and Enable Archiving
*** Specify Flash Recovery Area and Flash Recovery Area Size
*** Flash Recovery Area: This is used as the default for all backup and recovery operations, and is also required for automatic backup using Enterprise Manager. Oracle recommends that the database files and recovery files be located on a physically different disks for data protection and performance.
Human Resources: The Human Resources (HR) schema is a basic relational database schema. There are six tables in the HR schema: Employees, Departments, Locations, Countries, Jobs, and Job_History. The Order Entry (OE) schema has links into HR schema.
Order Entry: The Order Entry (OE) schema builds on the purely relational Human Relations (HR) schema with some object-relational and object-oriented features. The OE schema contains seven tables: Customers, Product_Descriptions, Product_Information, Order_Items, Orders, Inventories, and Warehouses. The OE schema has links into the HR schema and PM schema. This schema also has synonyms defined on HR objects to make access transparent to users.
Product Media: Product Media (PM) schema includes two tables, online_media and print_media, one object type, adheader_typ, and one nested table, textdoc_typ. The PM schema includes interMedia and LOB column types. Note: To use interMedia Text you must create an interMedia Text index.
Sales History: The Sales History (SH) schema is an example of a relational star schema. It consists of one big range partitioned fact table SALES and five dimension tables: TIMES, PROMOTIONS, CHANNELS, PRODUCTS and CUSTOMERS. The additional COUNTRIES table linked to CUSTOMERS shows a simple snowflake.
Queued Shipping: The Queued Shipping (QS) schema is actually multiple schemas that contain message queues.
Sample Schemas can be installed automatically for you by the Database Configuration Assistant or you can install it manually at a later time. The schemas and installation instructions are described in detail in Oracle Sample Schemas.
- You can specify whether or not to Load Sample Schemas to your database.
*** Sample schemas illustrate the use of layered approach to complexity, and are used by some demonstration programs. Installing this will give you the following schemas in your database: Human Resources, Order Entry, Online Catalog, Product Media, Information Exchange, Sales History. It will also create tablespace called EXAMPLE. The tablespace will be about 130MB.
*** Custom Scripts: You can also specify the SQL scripts you want to run after the database is created.
Use this page to set the initialization parameters that control how the database manages its memory usage. You can choose from two basic approaches to memory management:
@ Typical, which requires very little configuration and allows the database to manage how it uses a percentage of your overall system memory
@ Custom, which requires more configuration, but provides you with more control over how the database uses the available system memory
*** Using the Typical Approach to Memory Management
Select Typical to create a database with minimal configuration or user input. This option is sufficient for most environments and for Oracle Database administrators (DBAs) who are inexperienced with advanced database creation procedures.
Enter a value in the Percentage field. This value represents a percentage of your total available system memory (shown in parentheses) that will be allocated to the Oracle Database. Based on this value, the Database Configuration Assistant automatically allocates the most efficient amount of memory to the database memory structures.
Click Show Memory Distribution to see how much memory the Assistant will assign to the memory structures described in the following table. The table describes each memory structure and the corresponding initialization parameter.
Note: The memory allocation also includes another 40MB, which is required by the operating system to run the database executable.
@ System Global Area (SGA): SGA_TARGET: A shared memory region that contains data and control information for one Oracle instance. Oracle allocates the SGA when an instance starts and deallocates it when the instance shuts down. Each instance has its own SGA.
@ Program Global Area (PGA): PGA_AGGREGATE: A memory buffer that contains data and control information for a server process. A PGA is created by the Oracle Database when a server process is started. The information in a PGA depends on the Oracle configuration.
*** Using the Custom Approach to Memory Management
If you are an experienced database administrator and you want more control over the allocation of memory for the Oracle Database, select Custom.
To allocate specific amounts of memory to the SGA and PGA, select Automatic.
To customize how the SGA memory is distributed among the SGA memorys substructures, select Manual and enter specific values for each SGA subcomponent.
The following table lists a description of each SGA subcomponent, as well as the corresponding initialization parameter for each of these settings. You can review and modify these initialization parameters later in the Database Configuration Assistant.
@ Shared Pool: SHARED_POOL_SIZE: Enter the size in bytes of the area for shared SQL and PL/SQL statements or accept the default entry. Large values improve performance in multi-user systems. Small values use less memory.
Note: If you installed the Oracle interMedia and Advanced Replication options, the value for Shared Pool Size must be at least 15MB.
@ Buffer Cache: DB_CACHE_SIZE: Enter the size in bytes for the database buffer cache. This is the portion of the SGA that holds copies of data blocks read from data files.The initialization parameter specifies the number of buffers in the database buffer cache.
Each buffer in the cache is the size of one Oracle data block (which is specified by the initialization parameter DB_BLOCK_SIZE); therefore, each database buffer in the cache can hold a single data block read from a data file. All user processes concurrently connected to the instance share access to the database buffer cache.
@ Java Pool: JAVA_POOL_SIZE: Java pool memory is used in server memory for all session-specific Java code and data within the JVM.
@ Large Pool: LARGE_POOL_SIZE: Enter the size in bytes for the large pool allocation heap. The Large Pool allocation heap is used by the Shared Server for session memory, by Parallel Execution for message buffers, and by Backup for disk I/O buffers. If is left unset and the pool is required by parallel execution, then Oracle will compute a value automatically. The computation will add 250k per session for the shared server if MTS_DISPATCHERS is configured. A final computation will add a port-specific amount of memory for Backup I/O buffers.
Warning: this default computation can yield a size that is either too large to allocate or causes performance problems. In that case, you should set LARGE_POOL_SIZE to a number sufficiently small so that the database can start.
- Accept default value for the remaining configurations.
*** Memory: Typical - Allocate memory as a percentage of the total physical memory. Provide the Percentage. Click on Show Memory Distribution for detailed information. Custom - You can set Shared Memory Segment as Automatic or Manual. Provide the SGA Size and PGA Size.
*** Sizing: Block - A block is the smallest unit of storage for allocation and for I/O. It cannot be changed once the database is created. Processes - Specify the maximum number of operating system user processes that can be simultaneously connect to database. The value of the parameter must be 6 or greater (5 for the background processes plus 1 for each user process).
*** Character Sets: You can choose from the following Database Character Sets: Default - The default character set for this database is based on the language setting of this operating system. Use Unicode (AL32UTF8) - Setting character set to Unicode (AL32UTF8) enables you to store multiple language groups. Or Choose from the list of character sets. You will also need to set the National Character Set, Default Language, and Default Date Format.
*** Connection mode: Select the mode in which you want your database to operate by default. Dedicated Server Mode - For each client connection the database will allocate a resource dedicated to serving only that client. Use this mode when the number of total client connections is expected to be small or when the clients will be making persistent, long-running requests to the database. Shared Server Mode - Several client connections share the database-allocated pool or resources. Use this mode when large number or users need to connect to the database simultaneously while efficiently utilizing the system resources. The Oracle shared server feature will be enabled. Share servers specifies the number of server processes that you want to create when an instance is started up.
Use this page to specify storage parameters for the database. This page displays a tree listing and summary view (multi-column lists) to allow you to change and view the following objects:
@ Control files
@ Tablespaces
@ Datafiles
@ Rollback Segments
@ Redo Log Groups
Note: If you are using Automatic Undo Management, you do not need to configure rollback segments.
From any object type folder, click Create to create a new object. To delete an object, select the specific object from within the object type folder and click Delete.
Important: If you select a database template including data files, you will not be able to add or remove data files, tablespaces, or rollback segments. Selecting this type of template allows you to change the following:
@ Destination of the data files
@ Control files or log groups
*** Notes for Real Application Clusters
If you are not using Automatic Storage Management (ASM) or a cluster file system, then use this Database Storage page to manage database storage objects in your Real Application Clusters environment.
Although the Oracle Database Configuration Assistant creates these storage objects, you must change the names for the control files and data files for an Real Application Clusters database that uses raw devices. To do this, highlight the object on the left-hand side of the page; the General tab automatically appears on the right-hand side of the page.
The default file name appears in the General dialog in the Name field. Change the value in thisfield to the actual raw device file name for each object. Do this for the control files, all datafiles, and for the redo log group member file names.
If you are using Automatic Undo Management, also do this for the undo tablespaces. If you are using ASM or a cluster file system, then you do not have to change these file names.
Additional platform-specific issues are: UNIX cannot have default data file names because theDatabase Configuration Assistant does not know how you named your raw devices. WindowsNT and Windows 2000 use a default file naming syntax that incorporates your database name.
- Review Database Storage
*** From the Database Storage page, you can specify storage parameter for the database creation. This page displays a tree listing and summary view (multi-column lists) to allow you to change and view the following objects: Control files, Tablespaces, Datafiles, Rollback Segments and Redo Log Groups. From any object type folder, click Create to create a new object. To delete an object, select the specific object from within the object type folder and click Delete.
*** Important: If you select a database template including data files, you will not be able to add or remove data files, tablespaces, or rollback segments. Selecting this type of template allows you to change the following: Destination of the data files and Control files of log groups.
*** Create a database
Select this check box to create the database now. For more information on the creation parameters, refer to the Summary dialog, which appears before you start the database creation process. This option takes time to complete.
*** Save as a Database Template
Select this check box to save the database creation parameters as a template. This template will be automatically added to the list of available database templates.
Name: Enter a title for this template that will appear in the list of preconfigured templates.
Description: Provide a short description of the template type.
*** Generate Database Creation Scripts
This option allows you to generate database creation scripts for the selected database template.
Select this check box to access all the scripts used to create the database. These scripts are generated from the database parameters that you have provided in the previous pages. You can use the scripts as a checklist, or to create the database without using the Oracle Database Creation Assistant.
If you select the "Generate Database Creation Scripts" option, you must manually configure the following:
@ Directory Service
@ Listener.ora and TNSNAMES.ora
@ Services for NT
@ ORATAB entries for Solaris Destination
Directory: Specify the target where you want the generated script files to be saved. Alternatively, click Browse, and navigate to the required directory.
- Start the Database Creation
> Select Create Database and click Finish.
*** You can also save your configuration as Database Template for future database creation. You need to provide Name and Description for this option. You will also have the option to Generate Database Creation Scripts. Provide Destination Directory.
Use this page to review details of the selected database template. The details include common options, initialization parameters, data files, control files, and redo log groups.
These settings will be used when the Database Configuration Assistant creates your new database with the selected template.
Click Save as an HTML file to save the details to an HTML file. This information could be useful later, when you want to tune the database, review the details, or troubleshoot performance issues.
- Database creation is now initiated.
[oracle@oracle10g ~]$ netca
> Edit listener.ora
> [oracle@oracle10g ~]$ vi $ORACLE_HOME/network/admin/listener.ora
> Add/ Edit the following lines:
- Start Network ManagerSID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = ORCL10G)
(ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1)
(SID_NAME = ORCL10G)
)
)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle10g.localdomain)(PORT = 1521))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)
[oracle@oracle10g ~]$ netmgr
- Point to Oracle Net Configuration > Local > Listeners > LISTENER > Database Services
> Provide Net Service Name
> Input the correct hostname: e.g. oracle10g.localdomain
> Provide (Oracle8i or later) Service Name: e.g. ORCL10G
- Save the configuration. File > Save Network Configuration
- Another way to configure network configuration is to:
> Edit tnsnames.ora
> [oracle@oracle10g ~]$ vi $ORACLE_HOME/network/admin/tnsnames.ora
> Add/ Edit the following lines:
- Restart ListenerORCL10G =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = oracle10g.localdomain)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ORCL10G)
)
)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(Key = EXTPROC0))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
> [oracle@oracle10g ~]$ lsnrctl stop
> [oracle@oracle10g ~]$ lsnrctl start
-- End of Oracle Database 10g Creation --