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 11g Software (http://www.oracle-forums.com/installing ... -t632.html)
Procedure:
- Login to your VMware.
- Set correct ORACLE_HOME
> [oracle@oracle11g ~]$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_2
- Welcome page, Standalone Mode[oracle@oracle11g ~]$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_2
[oracle@oracle11g ~]$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0/dbhome_2
Welcome to Oracle Net Configuration Assistant. The Oracle Net Configuration allows you to configure basic network components after installation.
*** Listener configuration
Select this option to create modify, delete or rename, a listener. The listener is a process on the server that receives and responds to client connection requests for a database. Clients using connect descriptors configured with the same protocol addresses can send a connection request to the listener.
Note: This option is not available on clients.
*** Naming Methods configuration
Select this option to configure naming methods. When an end user connects to a database service, a connect string that identifies the service through a simple name, called a connect identifier, is used. A connect identifier can be the actual name of the service or a net service name. The connect identifier is resolved to a connect descriptor, which contains the network location and identification of the service, by a naming method. You can configure this computer to resolve connect identifiers using any of the following methods:
@ Local naming
@ Directory naming
@ Easy connect naming
@ Sun Network Information Service (NIS)
Additionally, if the local naming method is selected on the client, you are prompted to configure connect descriptors in a client-side tnsnames.ora file.
*** Directory Usage Configuration
Select this option to configure usage of a LDAP-compliant directory server, if you plan to use:
@ Directory naming to centrally administer connect identifiers
@ Enterprise user security for use with Oracle Advanced Security
@ Other Oracle product features that use a centralized directory server to store entries
- Configure Listener (if you have not done so)
> [oracle@oracle11g ~]$ netca
The listener is a process that receives connection requests on behalf of a client application. The listener listens for client requests on a protocol address specified in the listener file.
When running Net Configuration Assistant in standalone mode, you can add, modify protocol address settings, rename, or delete a listener.
@ Add
Select to add a listener.
@ Reconfigure
Select to reconfigure the protocol address of a listener.
@ Rename
Select to change the listener name. If the listener you rename is running, the Net Configuration Assistant first stops the original listener, then restarts the renamed listener.
@ Delete
Select to remove a listener. If the listener is running, the Net Configuration Assistant stops the listener before deleting it.
> Select "Add" and then provide Listener Name.
- Listener Configuration, Listener Name
Enter a name that identifies a listener not currently in use. The name can be no longer than 138 characters.
The listener is a process that receives connection requests on behalf of a client application. Each listener is identified by a unique name. LISTENER is the default listener name for the first listener. Subsequent listeners are defaulted to LISTENER1, LISTENER2, and so on.
*** Notes for Real Application Clusters
Prior to Enterprise Manager version 10.2, the system checked only the local listener.ora file. Enterprise Manager version 10.2 and higher checks all Oracle homes on the cluster to determine whether a listener name is already used.
- Listener Configuration, Select Protocols
You can configure the listener to listen on a subnet and accept connections over one or more protocols. The listener receives client requests at a protocol address specified in the listener.ora file. Clients sending a request are also configured with the same protocol address.
Select the protocol(s) from the Available Protocols list to create a protocol address for the listener. The protocol address is stored in the listener.ora file.
To select protocols to use:
@ Select the subnet from the Select Subnet list.
@ Select protocol(s) from the Available Protocols list, and then choose the right-arrow button. The Selected Protocols move to the Selected Protocols list.
@ Order the protocols according to which protocols you expect clients to use the most with the up- or down-arrow buttons.
@ Choose Next. Based on your choice of protocol(s), you will be asked for protocol parameter information.
Note: If you decide to later change your choice of protocols, use Oracle Net Manager to make any modifications to listener configuration.
- Listener Configuration, TCP/IP Protocol
TCP/IP identifies a listener protocol address by a port number. Select the port number to use.
@ Use the standard port number of 1521:
Select this option to listen on the default port of 1521. Oracle Corporation recommends that use this port number for client connections to a database service.
By default, dynamic service registration uses a listener configured with TCP/IP, port 1521.
@ Use another port number:
Select this option to specify another port to use other than 1521. The listener should be the only piece of software on this computer that is listening on the port you specify.
Note: To have dynamic service registration for a nondefault TCP/IP address, you must configure the LOCAL_LISTENER parameter in the initialization parameter file and resolve the listener name through a naming method.
- Listener Configuration, More Listeners?
Specify whether or not to configure another listener for this node:
@ No
Select to not configure another listener.
@ Yes
Select to configure another listener. Selecting this creates another unique listener name with a protocol address. It is typically not necessary to configure more than one listener for a service on a node.
- Startup the newly configured listener.
[oracle@oracle11g ~]$ lsnrctl start LISTENER11G
- Start Database Configuration Assistant
> [oracle@oracle11g ~]$ dbca
Welcome to Database Configuration Assistant (DBCA).
After you install the Oracle Database software, you can use DBCA to create and configure your databases.
*** Overview of DBCA
DBCA 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 DBCA.
With DBCA 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.
Note: Oracle recommends that you close other applications when running DBCA.
*** Notes for Oracle Real Application Clusters (Oracle RAC) Users
Before DBCA can create an Oracle RAC database, you must complete the preinstallation tasks, and you must have completed the two-phase installation process for installing Oracle Clusterware and the Oracle Enterprise Edition 11g with Oracle RAC.
In addition, depending upon the type of database storage that you use, you should perform one of the following setup procedures before running DBCA to create an Oracle RAC database.
@ Set up raw disks on shared storage and use Automatic Storage Management (ASM) for database storage. Use ASMCA for creating and configuring ASM.
@ If your platform supports a cluster file system, then you can use a cluster file system partition for database storage.
@ Check if the default listener is running from the Grid Infrastructure home, if not use NETCA to configure the default listener.
For more information about configuring your disks, refer to the preinstallation procedures as described in your platform-specific Oracle Clusterware installation and configuration guide.
- Database Operations
Use this page to select the database configuration task that you want to perform with Database Configuration Assistant (DBCA). 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. DBCA 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.
@ Instance Management: This option enables you to add new, or delete existing database instances to/from an existing admin-managed Real Application Clusters database. If there are no admin-managed instances, or only policy-managed databases exist, then this option will be disabled.
- Choose "Create a Database"
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 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 that 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.example.com
The database name portion (in this example, test) is a simple name for your database. The database domain portion (in this case, us.example.com ) specifies the domain in which the database is located. When possible, Oracle recommends that your database domain should 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 software. 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 or Linux: 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 Oracle Real Application Clusters (Oracle RAC): Instead of a SID, you provide a SID prefix for Oracle RAC.
- Provide the Database name
Use this page to set up your database, so that 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, choose the Grid Control option, and select an Oracle Management Service from the drop-down list. When you complete installing the Oracle Database, it is automatically available as a managed target within the Oracle Enterprise Manager Grid Control.
You must 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 a clustered database that you are installing.
Click Configure Database Control for local management to configure the database so that it can be managed using the Oracle Enterprise Manager Database Control.
*** Enabling Alert Notification
When you select the Database Control management option, you can configure Enterprise Manager so that notifications are enabled immediately upon installation.
Select Enable Alert Notifications if you want the SYSMAN user (the default Super Administrator and owner of the Management Repository schema) to receive alert notification when a metric for a specified condition reaches a critical or warning threshold. For example, Enterprise Manager can send an alert 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 alert notifications to work properly. If you do not provide the necessary information on this screen, alert notification will not be enabled upon installation. You may set or change alert notification settings using the Enterprise Manager Console after the 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.example.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 Disk Backup to Recovery Area
If you select the Database Control management option, you can also enable automatic daily backups of your entire database.
Select Enable Daily Disk Backup to Recovery Area 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 is configured to back up your database based on the scheduled start time that you enter on this page, immediately after you complete installing the Oracle Database. Enterprise Manager will back up the database to the Flash Recovery Area that you specify on the Recovery Configuration page of the Database Configuration Assistant.
After you select Enable Daily Disk Backup to Recovery Area, enter the following information to enable the automatic backup strategy:
@ In the Backup Start Time field, specify a time of day when the back up job is submitted.
@ In the OS Username and OS Password fields, enter the host credentials. The host credentials are required for the Enterprise Manager to write to the disk recovery location, which is specified later on the Recovery Configuration page of the Database Configuration Assistant.
*** Switching from DB Control to Grid Control Configuration
In the configure mode, DBCA provides you an option to switch to Grid Control if the database is currently configured to DB Control. Switching to Grid Control migrates all targets from DB Control to Grid Control, along with collection and blackouts. It does not migrate metric data or jobs.
While switching to Grid Control management option, you can optionally delete the DB Control.
- Select "Configure Enterprise Manager"
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.
@ 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.
@ 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.
- You will have the option to "Use Different Administrative Password" or "Use the Same Administrative Password for All Accounts"
Use this page to select the storage mechanism that you would like to use for your database files and specify where, and how you want to store the database files. Database files include the data files, control files, and log files associated with your database.
@ File System: Select File System to save and maintain your single-instance database files in a directory in your current file system. By default, Database Configuration Assistant (DBCA) saves 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 Oracle Real Application Clusters (Oracle RAC), 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
@ Automatic Storage Management (ASM): ASM is an 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.
Use USMCA to configure ASM.
Tip: After you set up an ASM instance with USMCA, you can use Oracle Enterprise Manager to manage your ASM instance. For more information, see the Oracle Enterprise Manager online help.
@ Use Datafile Locations from Template: Select this option to use the predefined location in the database template that you selected for this database. Even after selecting this option, you will be able to override these defaults, 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 can 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.
- Specify storage type and locations for database files.
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 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 the Oracle Enterprise Manager, or running the database 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. You must enable archiving to make the database recoverable from disk failure.
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.
- Specify Flash Recovery Area (FRA) location and size and then "Enable Archiving"
The sample schemas contain scripts for the following types of tables:
@ 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.
- Load Sample Schemas
Use this page to set the initialization parameters that control the way 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. You can adjust the slider control to allocate Memory Size (SGA and PGA) from a continuous range of values. The minimum value of memory that must be alloted is 250 MB, the default value for all machines. You can move the slider to the right to increase the value of memory size. The maximum value that can be set is equal to the total available physical memory in the machine.
The Percentage field represents the percentage of your total available system memory 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.
To allow the Oracle instance to automatically manage instance memory, most platforms require you to set only the initialization parameter MEMORY_TARGET. To do this, select Use Automatic Memory Management. If you select this option, memory is managed automatically, i.e the database instance will manage SGA and PGA size automatically.
If you clear the Automatic Memory Management checkbox, the instance tunes to the value of Memory Size (SGA and PGA), redistributing memory between the system global area (SGA) and aggregate program global area (PGA aggregate). The Memory Size (SGA and PGA) initialization parameter is dynamic; you can change it any time, without restarting the database. You can click Show Memory Distribution button to see the memory allocated to SGA and PGA.
The following platforms support Automatic Memory Management:
@ Linux
@ Solaris
@ Windows
@ HP-UX
@ AIX
- Specify Memory Size
Use this page to specify storage parameters for the database. This page displays a tree listing and summary view (multi-column lists) to enable 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, then you do not need to configure rollback segments.
From any object type folder, click Create to add a new object. To delete an existing object, select the specific object from within the object type folder, and click Delete.
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 enables you to change the following:
@ Destination of the datafiles
@ Control files or log groups
*** Bigfile Tablespace
Select the "use bigfile tablespace" checkbox if you want to create a tablespace that can store a large datafile. A "bigfile tablespace" can typically store one datafile that is of size 4 MB (maximum).
*** Notes for Oracle Real Application Clusters (Oracle RAC)
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 Oracle RAC environment.
If you are using Automatic Undo Management, then 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.
Microsoft Windows uses a default file naming syntax that incorporates your database name.
- Adjust as necessary the Database Storage
*** 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 Cration 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.
- Select the database creation options
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.
- Review Summary