Creating Empty Oracle Database

Database creation prepares several operating system files to work together as an Oracle database. Creating a database includes these topics:

EDM provides default values for all these parameters, you can accept these defaults, and start the database creation process. If you do not want to use the default values, see Setting Up Database Creation Parameters to define your own values.

Once you have completed the steps defined in this document, refer to CES Administration Guide : Oracle Text Search to learn how to install the Text Search option in the new Oracle database.

Before you create a database, you need to:

  • Plan your database tables, indexes, and estimate the space requirement.

  • Plan how to protect your database, including the configuration of its online, archived redo log, and a backup strategy.

  • Select the database character set.

To create a new database, you must:

  • Belong to the ORA_DBA group for Windows, and dba group for UNIX.

  • Have sufficient memory to start the Oracle10g instance.

  • Have sufficient disk storage space for the planned database on the server that executes Oracle10g.

  • Have enough space for the default data directory.

On Windows, the database ORACLE_SID can contain only alphanumeric characters. If you use an underscore (_) in the name, the database creation fails with an ORA-12560 error.

Using Database Creation Wizard

The database creation wizard allows you to carry out several tasks. This table describes the command buttons:
Button Description
Use this option to proceed to the next page in the database creation wizard.
Use this option to cancel the database creation, and return to the ENOVIA/CES Database Manager main window.
Use this option to start the database creation, accepting all the default values.
Use this option to view summary of the information.

Setting Up Database Creation Parameters

This task explains how to set up the database creation parameters:
  1. From the navigation pad, select Build > Create an Empty Database.

    The Password Setup dialog box appears.

  2. Type the passwords in these fields:

  • SYS Password

  • SYSTEM Password

  • CISDBA Password

    Note: The password for CISDBA user should be cis2. The user should not enter any other password.

  • CISQUERY Password

  • CISEDITOR Password

  1. Click OK.

    The DB Setup window appears.

  2. Specify the values for optimum performance of the database that you are creating. The values you specify are used to generate default values for some of the parameters used during the database creation.

    This table explains the fields displayed in the DB Setup window:
     

    Fields

    Description

    Number of CPUs

    Specify the number of CPUs.

    Physical RAM

    Specify the physical RAM.

    Note: The values you specify for the Number of CPUs and Physical RAM of the database server machine should be based on the assumption that the entire machine is available for this database. If two databases are running on the same machine, you should divide the Number of CPUs and Physical RAM appropriately.

    Concurrent Users

    The approximate number of users that are to be concurrently, that is, simultaneously connected to the database. Four categories are available, namely:

    • Enterprise (200)

    • Company (100)

    • Department (20)

    • Me (2)

    Size of Database

    Four database size models are supported in CES, namely:

    • Tiny ( 3 - 4 GB)

    • Small (10 - 12 GB)

    • Medium (29 - 30 GB)

    • Large (48 - 50 GB)

    These are default sizes and cannot be modified.

    Types of Database

    • OLTP: Many concurrent users performing numerous transactions requiring rapid access to data. Availability, speed, concurrence, and reliability are key issues.

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

    • Hybrid: This is a mixed workload environment and both types of applications, that is, OLTP and DSS can access the database.

    Server Type

    The server types can be:

    Dedicated Server: There is one server process for each client. You can select this mode if:

    • You are using your database in a DSS environment.

    • The number of total client connections is expected to be small.

    • Clients need to make persistent, long-running requests to the database.

    Shared Server (SS): With Shared Server configuration, many user processes connect to a dispatcher. The dispatcher directs multiple incoming network session requests to a common queue. A small pool of server processes can serve a large number of requests. You can select this mode if:

    • You are using your database in an OLTP environment.

    • You have a large number of users who need to connect to the database.

    • You have many constraints.

    • You want to use Oracle Net (formerly known as Net8 and SQL*Net) features, such as connection spooling, connection concentration, and load balancing.

    • You are managing and utilizing system resources, which to a high degree is an important criterion.

    • Predictable and fast connection times are very important.

    Parallel Query Option

    If selected Yes, parallel query processing is enabled. This means, multiple processes can work together to simultaneously process a single SQL statement where a Full Table Scan (FTS) is involved.

    Note: If the Server Type is Shared Server and / or Parallel Query Option is set to Yes, the related parameters and their default values are displayed in the Initialization Parameters window. Depending on your system configuration, you might need to modify these values.

  3. Click Next.

    The Control Files window appears.

Defining Control Files

Every Oracle database has a control file, which records the physical structure of the database. The physical structures are:

  • Name

  • Timestamp of its creation

  • Names and locations of its data

  • Redo files

  • Checkpoint information

  • Current log sequence number

By default, three control files are created during the database creation. The path of each file and the parameters are displayed in the Control Files window.

This task explains how to define values in the Control Files window:

  1. When you have clicked Next in the DB Setup window, the Control File window appears.

  2. In the Control Files table, select the row, and then click Change.

    You are prompted for the new destination directory in the ENOVIA/CES Database Manager - Control File dialog box.

  3. In the Destination Directory field, enter the directory path and folder, or click Browse to select from the list.

    The Destination Directory: Selection dialog box appears.

  4. In the Look in field select the path, and then from the corresponding list displayed, select the folder.

    The selected path and folder are displayed in the File Name field.

  5. Click OK.

    The selected path and folder are displayed in the ENOVIA/CES Database Manager - Control File dialog box.

  6. Click OK.

    The changes made appear in the Control Files window, and the file is stored in the new location specified.

    The default values displayed in the fields can be changed.

    This table describes the fields displayed in the Control File Parameters:

    Fields

    Description

    Database Block Size

    This is the block size of the database. The block size cannot be changed after the database is created except by recreating the database.

    The valid values for Database block size are 4K to 32K (8K is the default), but your operating system might have a narrower range. If your system is not able to support the database block size which you had specified, the error message "ORA-00374:parameter db_block_size = 32768 invalid, valid range [2048..16384]" appears.

    Character Set

    Specify the character set to be used by the database. A character set might support a specific language, a group of related languages or attempt to encompass all known languages.

    Maximum Instances

    Specify the maximum number of instances that can simultaneously have the database mounted and open or accept the default entry. The minimum value is 1 (one) and the maximum value depends on your operating system.

    Maximum Log Files

    Specify the maximum number of redo log file groups that can be created for the database. Oracle uses this value to allocate the amount of space in the control file for the names of the redo log files.

    Maximum Data files

    Specify the maximum number of data files that can be created for the database.

    Maximum Log Members

    Specify the maximum number of members, or identical copies, for a redo log file group. Oracle uses this value to determine how much space in the control file to allocate for the names of redo log files. The minimum value is 1 (one). The maximum and default values depend on your operating system.
  7. Click Next.

    The Tablespaces window appears.

On UNIX systems, you can specify the physical location of the destination directory in the Symbolic Link window.

Defining Tablespaces

A database is divided in to one or more logical storage units, and is called tablespaces. The tablespaces can be used to:

  • Control disk space allocation for database data.

  • Assign specific space quotas for database users.

  • Control availability of data by taking individual tablespaces online or offline.

  • Perform partial database backup and recovery operations.

  • Allocate data storage across devices to improve performance.

The tasks that you can carry out in Defining Tablespaces are:

This task explains how to define tablespaces in the Tablespaces window:

  1. When you have clicked Next in the Control Files window, the Tablespaces window appears.

    Every tablespace has one or more physical data files associated with it. These data files contain all the database data. You can add more tablespaces, if required. The default display is System tab.

  2. In the Tablespaces window, click the required tablespaces tab to define tablespace details.

    This table explains the tabs displayed in the Tablespaces window:

    Tabs and Elements

    Description

    System

    Every Oracle database contains a tablespace named SYSTEM.
    Oracle creates the SYSTEM tablespace automatically when the
    database is created.

    Auxiliary Tablespace

    Auxiliary tablespace provided in Oracle10g named SYSAUX.

    Data

    This consists of your application data.

    Root Class Data

    This tablespace is used to store the CES root class data.

    Index

    This tablespace is used to store indexes associated with the data in the Data tablespace.

    Temp

    This tablespace is used during sorting operation on data.

    Undo

    This tablespace is used solely for storing undo information. In automatic undo management mode (manual undo management is not supported in CES when a new database is created), each Oracle instance is assigned one undo tablespace. Undo data is managed within an undo tablespace using undo segments that are automatically created and maintained by Oracle.

    Tools

    This tablespace is created for use if the user wants to install any third party, Oracle tools, or products.

    Users

    This tablespace is currently not used.

    This table details the availability of table-types displayed in the Tablespaces window:

    Tab

    Table

    Data files

    Extent Management

    Default Storage Parameters

    Segment Management

    System

    Yes

    Yes

    Yes

    No

    Auxiliary Tablespace

    Yes

    Yes

    Yes

    No

    Data

    Yes

    Yes

    No

    Yes

    Root Class Data

    Yes

    Yes

    No

    Yes

    Index

    Yes

    Yes

    No

    Yes

    Temp

    Yes

    Yes

    Yes

    No

    Undo

    Yes

    Yes

    No

    No

    Tools

    Yes

    Yes

    No

    Yes

    Users

    Yes

    Yes

    No

    Yes

    This table explains the various elements displayed in the Tablespaces window:

    Elements

    Description

    Tablespace Name

    Name of the tablespace which is part of the database.

    Tablespace Size

    Total size (in Mega or Giga Bytes) of the tablespace.

    Data files Table

    Datafile Name

    Displays the name of the datafile, which is associated with tablespace.

    File Size

    Displays the size of datafile in Mega or Giga Bytes.

    Use this option to delete an entry of datafile.

    Use this option to change the entry of datafile.

    Use this option to add the entry for datafile.

    Extent Management

    DICTIONARY

    Select this option to manage the extents in the tablespace using dictionary tables.

    LOCAL

    Select this option to manage the tablespace locally. Locally managed tablespaces have some part of the tablespace set aside for a bitmap.

    AUTO ALLOCATE

    Select this option to system-manage the tablespace. You cannot specify an extent size.

    UNIFORM

    Select this option to manage the tablespace with uniform extents.

    Size

    Use this option to specify the uniform extent size in Kilo or Mega Bytes.

    Default Storage Parameters

    Initial

    Specifies the size (in Kilo or Mega Bytes) of the objects first extent.

    Next

    Specifies the size (in Kilo or Mega Bytes) of the next extent to be allocated to the object.

    Minimum Extents

    Specifies the total number of extents to allocate when the object is created.

    Maximum Extents

    Specifies the total number of extents, including the first, that Oracle can allocate for the object.

    % Increase

    Specifies the percent by which the third and subsequent extents grow over the preceding extent.

    Segment Management

    AUTO

    Oracle manages the free space of segments in the tablespace using a bitmap.

    MANUAL

    Oracle manages the free space of segments in the tablespace using free lists.

    Use this option to add new tablespace to the database.

    Use this option to delete given tablespace (apart from required) in the database.

Adding New Datafile

You can use the Datafiles table in the Tablespaces window to add a new data file.

This task explains how to add a new data file in the Datafile table of the Tablespaces window:

  1. In the Tablespaces window, click Add.

    The Add Tablespace Datafile Details dialog box appears.

  2. Enter the destination directory and the file size in these fields respectively:

    Destination Directory

    Datafile Size

  3. If you wish to change the destination directory from the displayed path, click Browse.

    The Destination Directory dialog box appears.

  4. In the Look in field select the path, and then from the corresponding list displayed, select the folder.

    The selected path and folder appear in the File Name field.

  5. Click OK.

    The selected path and folder appear in the Add Tablespace Datafile Details dialog box.

  6. In the Datafile Size field, specify the size in MB.

  7. Click OK to add the new data file.

    The new file details appear in the Datafiles table.

Changing Datafile

You can use the Datafiles table in the Tablespaces window to edit the data file details.

This task explains how to edit data file in the Datafile table of the Tablespaces window:

  1. In the Datafiles table, select the data file to be changed.

    The selected file is highlighted.

  2. Click Change.

    The Edit Tablespace Datafile Details dialog box appears with the details of destination directory and the data file size.

  3. You can change the destination directory and the file size in these fields respectively:

    Destination Directory

    Datafile Size

    The data file name displayed cannot be modified.

  4. If you wish to change the destination directory from the displayed path, click Browse.

    The Destination Directory dialog box appears.

  5. In the Look in field select the path, and then from the corresponding list displayed, select the folder.

    The selected path and folder appear in the File Name field.

  6. Click OK.

    The selected path and folder appear in The Edit Tablespace Datafile Details dialog box.

  7. In the Datafile Size field, specify the modified size in MB.

  8. Click OK to change the data file.

    The changed values appear in the Datafiles table.

Removing Datafile

You can use the Datafiles table in the Tablespaces window to delete the data file.

This task explains how to delete the data file in the Datafile table of the Tablespaces window:

  1. In the Datafiles table, select the data file to be deleted.

    The selected file is highlighted
    .

  2. Click Delete.

    You are prompted to confirm the deletion
    .

  3. Click Yes to delete file.

    The selected data file is deleted
    .

Adding Tablespace

You can use the Default Storage Parameters or the Segment Management table in the Tablespaces window to add tablespace.

This task explains how to add tablespace in the Tablespaces window:

  1. In the Default Storage Parameters or the Segment Management table, as the case may be, click Add Tablespace.

    The Add Tablespace dialog box appears.

  2. In the Tablespace Name field, enter the new tablespace name.

  3. In the Datafile Name field, enter the new datafile name.

  4. In the Destination Directory field, enter the path and folder. If you wish to make changes to the displayed detail or if you are not aware of the path details, click Browse.

    The Destination Directory: Selection dialog box appears.

  5. In the Look in field select the path, and then from the corresponding  list displayed, select the folder.

    The selected path and folder appear in the File Name field.

  6. Click OK to continue.

    The selected path and folder appear in The Add Tablespace dialog box.

  7. In the Extent Management section, select your option.

    The AUTOALLOCATE and the UNIFORM options are enabled, only if you select the LOCAL option.

    You can specify size only if you select the UNIFORM option.

  8. In the Segment Management section, select your option. This section is relevant only if you have selected the LOCAL option in the Segment Management section.

  9. Click OK.

    The tablespace is added.

Deleting Tablespace

You can use the Default Storage Parameters or the Segment Management table in the Tablespaces window to delete tablespace.

This task explains how to delete tablespace in the Tablespaces window:

  1. In the Default Storage Parameters or the Segment Management table, as  the case may be, click Delete Tablespace.

    You are prompted to confirm the deletion.

  2. Click OK to confirm the deletion.

    The selected tablespace is deleted.

  3. After you have completed the tasks in the Tablespaces window, click Next to continue.

    The Redo Logs/Trace/Arch window appears.

    1. Each tablespace should have at least one data file.

    2. On UNIX systems, you can specify the physical location of the destination directory in the Symbolic Links window.

    3. You cannot delete any pre-defined tablespace.

Defining Redo Log Files and Tracing Archive Directories

Every database has a set of two or more redo log files. Redo logs are used to hold a record of all changes made to the data. If a database failure occurs before the data is written to the disk, the changes can be obtained from the redo log files. This prevents the data from being lost. The tasks that you can carry out in Defining Redo Log file are:

The adding group, member, and deleting redo log file are based on these conditions:

  • The redo log of a database consists of at least two redo log files.

  • A database consists of at least two redo log file groups.

  • Each redo log file group contains one or more redo log file members.

  1. When you have clicked Next in the Tablespaces window, the Redo Logs/Trace/Arch window appears.

    This table describes the details displayed in the columns of Redo Log File and Trace/Archive Directories tables:

    Column

    Description

    Group This displays a set of redo log files that are classified under various groups. You can add members to a group.
    Redo Log File Name This displays the name of the redo log file.
    File Size This displays the size of the redo log file.
    Trace/Archive Directories This lists the directories where the debug files are stored.
  2. This table describes the command options displayed in the Redo Logs/Trace/Arch window:

    Button

    Details

    Use this option to add redo log file (or member) to an existing group.
    Use this option to add redo log group.
    Use this option edit the redo log file information.
    Use this option to delete an entry of redo log file information in a given redo log group.
On UNIX systems, you can specify the physical location of the destination directory in the Symbolic Link window.

Adding Group

You can add a group in the Redo Logs.

This task explains how to add a new group:

  1. In the Redo Logs/Trace/Arch window, click Add Group.

    The Add Redo Log file details dialog box appears.

    1. The Group list displays the next group number. The number is auto generated, and cannot be modified.

    2. The Redo Log File field displays the redo log file name. The display is in read-only mode.

    3. The Redo Log Directory field displays the file destination. You can change the directory and path.

  2. In the File Size field, specify the size in MB.

  3. Click OK.

    The group and the details appear in the Redo Logs/Trace/Arch window.

Adding Member

You can add a member or members to a group in the Redo Logs.

This task explains how to add a new member to the group:

  1. In the Redo Logs/Trace/Arch window, select a group to which you want to add a member.

    The selected group is highlighted.

  2. Click Add Member to add a new member to the selected group.

    The Add Redo Log file details dialog box appears.

  • The Group list displays the group number selected in the Redo Logs/Trace/Arch window.

  • The Redo Log File field displays the redo log file name. The display is in read-only mode.

  • The Redo Log Directory field displays the file destination. You can change the directory and path. 

  1. In the File Size field, specify the size in MB.

  2. Click OK.

    The member is added to the group and the details appear in the Redo Logs/Trace/Arch window.

Changing Redo Log File

You can change the destination directory of file or file size for a selected Redo Log file.

This task explains how to change the destination directory of file or file size in the group:

  1. In the Redo Logs/Trace/Arch window, select a group to change the file size.

    The selected group is highlighted.

  2. Click Change to change the file size.

    The Edit Redo Log file details dialog box appears.

  • The Group list displays the group number selected in the Redo Logs/Trace/Arch window.

  • The Log File field displays the redo log file name. The display is in read-only mode.

  • The Destination Directory field displays the file destination. You can change the directory and path.

  1. In the File Size field, specify the size in MB. In the selected group, the entire redo log files must be the same size. The size you specify
    will be the same for other files also.

    You are prompted to confirm.

  2. Click Yes.

    The file size specified is applied to all the files in the selected group.

Deleting Redo Log File

You can delete a redo log file in a given group.

This task explains how to delete a redo log file in a given group:

  1. In the Redo Log Files table of the Redo Logs/Trace/Arch window, select a redo log file in a group to delete.

  2. Click Delete to delete the selected redo log file in a given group.

    You are prompted to confirm the deletion.

  3. Click Yes to confirm.

    The selected redo log file in a given group is deleted and removed from the list.

Changing Trace/Archive Directories

You can change the file destination of trace/archive directories.

This task explains how to change the destination of trace/archive directories:

  1. In the Trace/Archive Directories table of the Redo Logs/Trace/Arch window, select the directory.

    The selected directory is highlighted.

  2. Click Change to change the destination directory.

    The Trace/Archive Directory dialog box appears.

  3. The Destination Directory field displays the destination folder. Enter the new destination, or click Browse to select the new directory.

    The new destination directory entered or selected from the list appears in the Redo Logs/Trace/Arch window.

  4. Click Next to continue.

    The Symbolic Links Specifications window appears.

    On UNIX systems, you can specify the physical location of the destination  directory in the Symbolic Links window.
     

Specifying Symbolic Links

When you install or create your database, you can create symbolic links that point from the /<ORACLE_DATA>/<ORACLE_SID> directory to the actual location of each file on separate physical drives.

The symbolic links to all the files and directories defined so far are displayed. In the Symbolic Links window, you can specify the corresponding
physical directories.

The Symbolic Links window appears only on UNIX systems.

This task explains how to create symbolic links:

  1. When you have clicked Next in the Redo Logs/Trace/Arch window, the Symbolic Links window appears.

  2. In the Symbolic Link Specification table, select a symbolic link.

    To specify the directory, you can select:

  • One symbolic link to update.

  • More than one symbolic link to update.

  • All symbolic links to update.

    Update Selection is used to update the selected link or links, and Update All is used to update all the links.

  1. In the Physical Directory field, enter the directory name, or click Browse to select the directory.

    The selected directory appears in the Physical Directory field.

  2. Click Update Selection or Update All based on the selection of symbolic links.

    The selected links are updated.

  3. Click Next.

    The Defining Initialization Parameters window appears.

Defining Initialization Parameters

The initialization parameters file contains configuration parameter values that control memory sizing, processing setting for your database instance, and this file is read each time the database instance is started. Initialization parameters can be used to:

Optimize performance by adjusting memory structures. For example, the number of database buffers in memory.

  • Set database limits. For example, the maximum number of database users.

  • Specify names of files.

The tasks that you can carry out in defining initialization parameters are:

This task explains how to define the initialization parameters:

  1. When you have clicked Next in the Symbolic Links (on UNIX systems) or  the Redo Logs/Trace/Arch window (on Windows systems), the Initialization Parameters window appears.

    This table describes the initialization parameters with default values:

    Name

    Description

    Default Values

    BITMAP_merge_area_size

    Relevant only for systems containing bitmap indexes. It specifies the amount of memory Oracle uses to merge bitmaps retrieved from a range scan of the index. A larger value usually improves performance, because the bitmap segments must be sorted before being merged into a single bitmap.

    Range: OS dependent

    Oracle: 1048576 (1 MB)

    EDM:16777216 (16 MB)

    (For SS mode only)

    COMPATIBLE

    Allows you to use a new release, while at the same time guaranteeing backward compatibility with an earlier release. This parameter also allows you to take advantage of the maintenance improvements of a new release immediately in your production systems without testing the new functionality in your environment.

    This is helpful when you need to revert to an earlier release.

    Range: Default release to current one

    Oracle: 10.2.0

    EDM: 10.1.0

    CREATE_bitmap_area_size

    Relevant only for systems containing bitmap indexes. It specifies the size of memory allocated for bitmap creation.

    Range: OS dependent

    Oracle: 8388608 (8 MB)

    EDM: 16777216 (16 MB)

    (For SS mode only)

    CURSOR_sharing

    Determines what kind of SQL statements can share the same cursors.

    EXACT causes only identical SQL statements to share a cursor.

    FORCE forces statements that might differ in some literals, but are otherwise identical to share a cursor unless the literals affect the meaning of the statement.

    SIMILAR allows to share a cursor by statements which might differ in some literals, but are otherwise identical.

    Range: FORCE | EXACT |

    SIMILAR

    Oracle: EXACT

    EDM: FORCE

    CURSOR_space_for_time

    Allows you to use more space for cursors in order to save time. It affects both the shared SQL area and the clients private SQL area.

    TRUE: Shared SQL areas are kept pinned in the shared pool.

    FALSE: Shared SQL can be de-allocated from the library cache to make room for new SQL statements.

    Range: TRUE | FALSE

    Oracle: FALSE

    EDM: TRUE

    DB_cache_size

    Specifies the size of the DEFAULT buffer pool for buffers with the primary block size (the block size defined by the DB_Block_SIZE parameter).

    The value must be at least the size of one granule (smaller values are automatically rounded up to the granule size).

    A value of zero is the size of DEFAULT pool for the SYSTEM tablespace.

    Oracle 48 MB, rounded up to the nearest granule size.

    EDM: OLTP (40% of Total Memory for Oracle).

    DSS (35% of Total Memory for Oracle)

    Hybrid (45% of Total Memory for Oracle)

    where,

    Total Memory for Oracle is 70 percent of Physical RAM

    DB_files

    Specifies the maximum number of database files that can be opened for this database. If you increase the value of DB_files, you  must shut down and restart all instances accessing the database before the new value can take effect.

    Range: Min: Actual no. of datafiles in database.

    Max: Value specified in the MAXDATAFILES clause the last time CREATE DATABASE or CREATE  CONTROLFILE was executed.

    Oracle: 200

    EDM: Me (100). Department (255), Company (500), Enterprise (1000)

    DB_file_multiblock_ read_count

    This is one of the parameters you can use to minimize I/O during table scans. It specifies the maximum number of blocks read in one I/O operation during a sequential scan.

    Range: OS dependent

    Oracle: 8

    EDM: OLTP (16), DSS(64)

    Hybrid (32)

    DISPATCHERS

    Configures dispatcher processes in the Shared Server architecture. The parsing software supports a name value syntax to enable the specification of attributes in a position-independent case-insensitive manner. If you want the dispatcher to listen on specific port/listener for the Shared Server, you can specify PORT and LISTENER attributes in addition to PROTOCOL, DISPATCHERS and CONNECTIONS.

    Oracle None

    EDM: (PROTOCOL=TCP) (DISPATCHERS=1) (CONNECTIONS=1024)

    (For SS mode only)

    HASH_area_size

    Relevant to parallel execution operations and to the query portion of DML or DDL statements. It specifies the maximum amount of memory, in bytes, to be used for hash joins.

    Range: 0 to OS dependent

    Oracle: 2 * value of SORT_area_size

    EDM: 2 * value of SORT_area_size

    (For Shared Server (SS) mode only)

    HASH_join_enabled

    Specifies whether the optimizer should consider using a hash join as a join method. When set to FALSE, hashing is not available as a join method.

    When set to TRUE, the optimizer compares the cost of a hash join with other types of joins, and selects hashing if it gives the best cost.

    Range: TRUE, FALSE

    Oracle: TRUE

    EDM:

    TRUE for DSS / Hybrid

    FALSE for OLTP

    JAVA_pool_size

    Specifies the size in bytes of the Java pool, from which the Java memory manager allocates most Java state during runtime execution.

    Range:

    Min - the granule size

    Max - OS dependent

    Oracle: 24 MB, rounded up to the nearest granule size

    EDM: 1 M

    JOB_queue_processes

    Specifies the maximum number of processes, which can be created for the execution of user jobs. If you have Text Indexes, you need this parameter to be set for scheduling text index sync and optimize.

    Range: 0 to 1000

    Oracle: 0

    EDM: 10

    LARGE_pool_size

    Allows you to specify the size in bytes of the large pool allocation heap. The large pool allocation heap is used in shared server systems for session memory, by parallel execution for message buffers, and by backup processes for disk I/O buffers.

    Range: 300 KB to at least 2 GB (actual maximum is OS specific)

    Oracle: 0 if:

    Pool is not required by parallel execution

    DBWR_io_slaves is not set

    Otherwise, derived from values of:

    • PARALLEL_threads_per_cpu

    • PARALLEL_server_instances

    • DISPATCHER

    • DBWR_io_slaves

    • PARALLEL_max_servers

    EDM: 20 M, If Shared Server

    (SS) mode is enabled.

    (For SS mode only)

    LOCAL_listener

    Specifies a network name that resolves to an address or address list of Oracle Net local listeners (that is, listeners that are running on the same machine as this instance). The address or address list is specified in the TNSNAMES.ORA file or other address repository as configured for your system.

    CES uses this parameter when Shared Server (SS) is enabled in order to make the dispatchers listen to the listener port. This parameter will be useful when non-default listener port number (Other than 1521) is used with Sharer Server mode.

    Oracle (ADDRESS = (PROTOCOL=TCP)(HOST=)(PORT=1521))

    EDM: (ADDRESS = (PROTOCOL=TCP)(HOST=<hostname>)(PORT=<Value of TNS Listener Port specified in EDM Database Setup>))

    (For SS mode only)

    LOG_buffer

    Specifies the size of memory, in bytes, that Oracle uses when buffering redo entries to a redo log file.

    Range: Operating system dependent

    Oracle: Operating system specific. Maximum: 500K or 128K * CPU_COUNT, whichever is greater.

    EDM: 512K or 128k * CPU COUNT, whichever is lesser.

    LOG_checkpoint_interval

    Specifies the frequency of checkpoints in terms of the number of redo log file blocks that can exist between an incremental checkpoint and the last block written to the redo log.

    Range: Unlimited

    Oracle: Oracle 0

    EDM: 101% of the Redo Log file size

    LOG_checkpoint_timeout

    Specifies that the incremental checkpoint is at the position where the last write to the redo log (sometimes called the "tail of the log") was integer seconds ago. This parameter also signifies that no buffer will remain dirty (in the cache) for more than integer seconds. The value is specified in seconds.

    Oracle 1800 secs

    EDM:: 0

    MAX_dispatchers

    Specifies the maximum number of dispatcher processes allowed to be running simultaneously. The default value applies only if dispatchers have been configured for the system.

    Range: 5 or number of dispatchers configured, whichever is greater.

    Oracle: 5

    EDM: 4

    (For SS mode only)

    MAX_dump_file_size

    Specifies the maximum size of trace files (excluding the alert file).

    Range: 0 to Unlimited, or UNLIMITED

    Oracle: UNLIMITED

    EDM: 10240

    MAX_shared_servers

    Specifies the maximum number of shared server processes allowed to be running simultaneously.

    If artificial deadlocks occur too frequently on your system, you should increase the MAX_shared_ servers

    Range: OS dependent

    Oracle: Derived from

    SHARED_SERVERS (either 20 or 2*SHARED_SERVERS)

    EDM:

    6 (For Me Concurrent Users model)

    8 (For Department Concurrent Users model)

    12 (For Company Concurrent Users model)

    18 (For Enterprise Concurrent Users model)

    (For SS mode only)

    NLS_date_format

    Specifies the default data format to use within TO_CHAR and TO_DATE functions.

    Range: Any valid format mask not exceeding a fixed length.

    Oracle: Derived from NLS_territory

    EDM: YYYY-MM-DDHH24.MI.SS

    NLS_language

    Specifies the default language of the database. This language is used for messages, day and month names, symbols for AD, BC, AM, and PM, and the default sorting mechanism.

    Range: Any valid language name

    Oracle: OS dependent, derived from NLS_LANG environment variable.

    EDM: Specified in the NLS_LANG field while setting up the environment variables for the database.

    NLS_terrritory

    Specifies the name of the territory whose conventions are to be followed for day and week numbering. This parameter also establishes the default date format, the default decimal character and group separator, and the default ISO and local currency symbols.

    Range: Any valid territory name

    Oracle: OS dependent

    EDM: Specified in the

    NLS_LANG field while setting up the environment variables for the database.

    OPEN_cursors

    Specifies the number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors.

    Range: 1 to 4294967295 (4 GB -1)

    Oracle: 50

    EDM: 1024

    OPTIMIZER_features _enable

    Allows you to  change the behavior of the Oracle optimizer based on a release number. For example, if you migrate your database from 8.0.5 to 8.1.5, but you want to keep the 8.0.5 optimizer behavior, you can do so by setting this parameter to 8.0.5.

    Range: 8.0.0, 8.0.3 - 8.0.7, 8.1.0, 8.1.3 to 8.1.7, 9.0.0, 9.0.1, 9.2.0, 10.1.0, 10.2.0

    Oracle: 10.2.0

    EDM: 10.1.0

    OPTIMIZER_index_caching

    Allows you to adjust the behavior of cost-based optimization to favor nested loops joins and IN-list iterators.

    Range: 0 to 100

    Oracle: 0

    EDM: OLTP (99), DSS (15),

    Hybrid (40)

    OPTIMIZER_index_cost_ adj

    Allows you to tune optimizer behavior for access path selection to be more or less index friendly that is, to make the optimizer more or less prone to selecting an index access path over a full table scan.

    Range: 1 to 10000

    Oracle: 100

    EDM: 10 OLTP (10), DSS (100), Hybrid (45)

    OPTIMIZER_max_ permutations

    Restricts the number of permutations of the tables the optimizer will consider in queries with joins. Such a restriction ensures that the parse time for the query stays within acceptable limits.

    Range: 4 to 80000

    Oracle: If OPTIMIZER_FEATURES_ENABLE is set to 9.0.0 or higher, then 2000.

    OPTIMIZER_FEATURES_ENABLE is set to 8.1.7 or lower, then 80000.

    EDM: 999

    OPTIMIZER_mode

    OPTIMIZER_mode specifies the goal of optimization of SQL statements.

    RULE specifies that rule-based optimization is to be used unless hints are specified in the query.

    CHOOSE specifies cost-based optimization for a SQL statement if the data dictionary contains statistics for at least one table accessed in the statement. If no such statistics are present, the optimizer uses the rule-based approach.

    FIRST_ROWS causes the optimizer to use cost-based optimization to choose execution plans that minimize response time.

    ALL_ROWS causes the optimizer to use cost-based optimization to choose execution plans that minimize total execution time.

    Range: FIRST_ROWS_ [1 | 10|100| 1000] | FIRST_ROWS | ALL_ROWS| CHOOSE RULE

    Oracle: CHOOSE

    EDM: CHOOSE

     

    PGA_aggregate_target

    Specifies the target aggregate PGA memory available to all server processes attached to the instance. You must set this parameter to enable the automatic sizing of SQL working areas used by memory- intensive SQL operators such as sort, group by, hash-join, bitmap merge, and bitmap create.

    Range:

    Min: 10 MB

    Max: 4096 GB - 1

    Oracle: 0 (automatic memory management is turned OFF by default)

    EDM:

    OLTP (20% of Total Memory for Oracle)

    DSS (50% of Total Memory for Oracle)

    Hybrid (25% of Total Memory for Oracle)

    where,

    Total Memory for Oracle is 70 percent of Physical RAM

    PRE_page_sga

    Determines whether all SGA pages are brought into memory at instance startup.

    Range: TRUE, FALSE

    Oracle: FALSE

    EDM:: TRUE

    PROCESSES

    Specifies the maximum number of operating system user processes that can simultaneously connect to Oracle.

    Range: 6 to OS dependent

    Oracle: Derived from PARALLEL_max_servers

    EDM:

    If Dedicated Server is selected, then 7 + #Concurrent Users + JOB_queue_processes+20

    If Parallel Query Optimizer is selected, then 7 + #Concurrent Users + PARALLEL_max_servers + JOB_queue_processes+20

    If Shared Server (SS) is selected then 7+MAX_shared_servers+MAX_dispatchers+JOB_ queue_ processes+20

    If PQO and Shared Server (SS) are selected, then 7+PARALLEL_max_servers+MAX_shared_servers+  MAX_ dispatchers+JOB_queue_processes+20

    QUERY_rewrite_enabled

    Allows you to enable or disable query rewriting globally for the database.

    Range: TRUE, FALSE

    Oracle: FALSE

    EDM: TRUE

    SESSIONS

    SESSIONS specifies the maximum number of sessions that can be created in the system. Because every login requires a session, this parameter effectively determines the maximum number of concurrent users in the system.

    You should always set this parameter explicitly to a value equivalent to your estimate of the maximum number of concurrent users, plus the number of background processes, plus approximately 10% for recursive sessions.

    Range: 1 to 231

    Oracle: Derived: (1.1 * PROCESSES) + 5

    EDM: Value of "Concurrent Users" in EDM: DB Setup screen + BACKGROUND SESSIONS (7) + Anticipated DEDICATED CONNECTIONS (20) + CUSHION (20)

    (For SS mode only)

     

    SESSION_cached_cursors

    Allows you to specify the number of session cursors to be cached. Repeated parse calls of the same SQL statement causes the session cursor for that statement to be moved into the session cursor cache. Subsequent parse calls will find the cursor in the cache and need not reopen the cursor. Oracle uses a least recently used (LRU) algorithm to remove entries in the session cursor cache to make room for new entries when needed.

    Range: 0 to OS dependent

    Oracle: 0

    EDM: 50

    SGA_max_size

    Specifies the maximum size of SGA for the lifetime of the instance.

    Oracle Initial size of SGA at startup, dependent on the sizes of different pools in the SGA such as buffer cache, shared pool, large pool and so on.

    EDM: (80% of PHYSICAL RAM - Total Memory of Oracle) + (Buffer Cache + Log Buffer + Java Pool + Shared Pool)

    where,

    Total Memory of Oracle is 70% of PHYSICAL RAM Buffer cache is OLTP (40% of Total Memory for Oracle)

    DSS (35% of Total Memory for Oracle)

    Hybrid (45% of Total Memory for Oracle)

    Log Buffer is MIN (512K, 128K*CPU COUNT), Java Pool is 1 MB, and Shared pool is OLTP (35% of Total Memory for Oracle)

    DSS (10% of Total Memory for Oracle)

    Hybrid (25% of Total Memory for Oracle)

    SHARED_pool_size

    Specifies the size of the shared pool in bytes. The shared pool contains shared cursors, stored procedures, control structures and other structures.

    Range:

    Min - the granule size

    Max - OS dependent

    Oracle:

    32 - bit platforms: 8MB, rounded up to the nearest granule size

    64 - bit platforms: 64 MB, rounded up to the nearest granule size

    EDM:

    OLTP (35% of total memory for Oracle)

    DSS (10% of Total Memory for Oracle)

    Hybrid (25% of total memory for Oracle)

    where,

    total memory for Oracle is 70% of Physical RAM

    SHARED_servers

    Specifies the number of server processes that you want to create when an instance is started up. If system load decreases, this minimum number of servers is maintained. Therefore, you should take care not to set SHARED_servers to a very high value at system startup.

    Range: OS dependent

    Oracle: If Shared Server architecture is enabled, 1 else 0

    EDM:

    2 (For Me Concurrent Users and Department Concurrent Users model)

    4 (For Company Concurrent Users and Enterprise Concurrent Users model)

    (For SS mode only)

    SHARED_server_sessions

    Specifies the total number of shared server architecture user sessions to allow. Setting this parameter enables you to reserve user sessions for dedicated servers.

    Range: 0 to SESSIONS - 5

    Oracle: Derived: the lesser of CIRCUITS and SESSIONS - 5

    EDM: Value of "Concurrent Users" in EDM: DB Setup screen + CUSHION (20)

    (For SS mode only)

    SORT_area_size

    Specifies in bytes the maximum amount of memory Oracle will use for a sort.

    Range:

    • Min: the value equivalent to six database blocks

    • Max: OS dependent Oracle65536

    EDM: 8388608

    (For SS mode only)

     

    STAR_transformation _enabled

    Determines whether a cost-based query transformation will be applied to star queries.

    Range: TRUE | FALSE | TEMP_DISABLE

    Oracle: FALSE

    EDM: TEMP_DISABLE

    STATISTIS_level

    Sets the statistics collection level of the database.

    Range: ALL | TYPICAL | BASIC

    Oracle: TYPICAL

    EDM: TYPICAL

    UNDO_management

    Specifies which undo space management mode the system should use. When set to AUTO, the instance starts in automatic undo management mode. In manual undo management mode, undo space is allocated externally as rollback segments.

    Range: MANUAL | AUTO

    Oracle: MANUAL

    EDM: AUTO

    UNDO_retention

    Specifies (in seconds) the amount of committed undo information to retain in the database. You can use UNDO_ RETENTION to satisfy queries that require old undo information to rollback changes to produce older images of data blocks. You can set the value at instance startup.

    Range: 0 to maximum value represented by 32 bits

    Oracle: 900

    EDM: 900

    UNDO_tablespace

    Specifies the undo tablespace to be used when an instance starts up. if this parameter is specified when the instance is in manual undo management mode, an error occurs and startup fails.

    Range: Legal name of an

    existing undo tablespace

    Oracle: The first available undo

    tablespace in the database

    EDM: UNDO_TS1

    Parallel Query Option

    PARALLEL_min_servers

    Specifies the minimum number of parallel execution processes for the instance. This value is the number of parallel execution processes Oracle creates when the instance is started.

    Range: 0 to value of PARALLEL_max_servers

    Oracle: 0

    EDM:: 2

    PARALLEL_max_servers

    Specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. As demand increases, Oracle increases the number of processes from the number created at instance startup up to this value.

    Range: 0 to 3599

    Oracle: Derived from the values of CPU_COUNT, PARALLEL_automatic_tuning, and PARALLEL_adaptive_multi_user

    EDM: 8

     

    PARALLEL_min_percent

    Operates in conjunction with PARALLEL_max_servers and PARALLEL_min_ servers. It allows you to specify the minimum percentage of parallel execution processes (of the value of PARALLEL_ max_servers) required for parallel execution.

    Range: 0 to 100

    Oracle: 0

    EDM: 0

    PARALLEL_threads_per  _cpu

    Specifies the default degree of parallelism for the instance and determines the parallel adaptive and load balancing algorithms. The parameter describes the number of parallel execution processes or threads that a CPU can handle during parallel execution.

    Range: Any non-zero number

    Oracle: OS dependent, usually 2

    EDM: 4

    PARALLEL_adaptive_multi_ user

    When set to TRUE, enables an adaptive algorithm designed to improve performance in multiuser environments that use parallel execution.

    Range: TRUE | FALSE

    Oracle: Derived from the value of PARALLEL_automatic_tuning

    EDM:TRUE

    PARALLEL_automatic_  tuning

    When set to TRUE, Oracle determines the default values for parameters that control parallel execution.

    Range: TRUE | FALSE

    Oracle: FALSE

    EDM: FALSE

Changing Parameter Values

You can define your own values to the parameters in the Initialization Parameters window.

This task explains how to change the parameter values:

  1. Select the parameter in the Initialization Parameters window.

    The selected parameter is highlighted.

  2. In the Initialization Parameters window, click Change.

    The Edit Initialization Parameter dialog box with the configured value for the selected parameter appears.

  3. Specify the value for the selected parameter.

  4. Click OK.

    The changed value appears in the Initialization Parameters window.

Saving Parameter Values in a File

You can save the changes made to the parameter values in the Initialization Parameters window.

This task explains how to save the parameter values:

  1. Make changes to the parameter values.

  2. In the Initialization Parameters window, click Save As.

    The init.ora File Name dialog box appears.

  3. Specify the file name, and then click OK to save the changes in to a file.

Viewing Summary

Before completing the database creation process, you can view the summary of changes after configuring Initialization Parameters.

This task explains how to view the summary:

  1. Click View Summary.

    The Database Creation Summary window appears.

  2. Review all the information displayed, and then click Close.

  3. If you need to make any changes, click Previous to revert to the previous page, or click the specific link provided on the left side of
    the database creation wizard.

If you want to execute the database creation, click Finish. You can choose to:

  1. Start the database creation immediately.

  2. Save the information to a batch file, which can be executed later.

  • If you decide to start the database creation process immediately, the database creation process starts, and the Progress window appears.

  • If you decide to execute the database creation process later, the database creation scripts are stored in a batch file, which can be executed later.

Executing DB Creation

 The last step in setting up database creation parameters is executing the database creation.

 This task explains how to execute the database creation process:

  1. After making changes in the Initialization Parameters window, in the navigation pad, click Execute DB Creation.

    You are prompted to either create the database or save the information to a batch file to be executed later.

  2. Click OK to start the database creation process.

    The Progress window displays the sequence of operations that are being performed during the database creation.


    As each sequence is completed, a check mark appears beside it, confirming the completion.

    Each action that occurs during the database creation process is written to a log file, which is created in your default destination directory. All the actions are also displayed in the bottom pane.

    After successful completion, a message appears confirming the process.

  3. Click OK.

    If a fatal error occurs during the database creation process or if you interrupt the process, the database creation process halts and you cannot proceed. The entire procedure is undone and all the generated files are cleaned. This process might take some time. When the cleanup is complete, you can revert to the previous window, and modify the details.