B Creating an Oracle Database

Using the Oracle Database Configuration Assistant to Create a Database

These instructions assume that you have installed the Oracle software (using the Oracle Universal Installer) into an Oracle home. The instructions begin after the Oracle Database Configuration Assistant has been launched. The Oracle Database Configuration Assistant is located in the following directory:

%ORACLE_HOME%\assistants\dbca

1. Select the General Purpose or Transaction Processing database template to ensure that initialization and other database sizing parameters meet or exceed all requirements listed in the pre-installation requirements.

   The General Purpose or Transaction Processing template also creates the necessary password file for the database, which must be there during Oracle CM SDK configuration. The password file enables you to connect to the service name using SYS 'AS SYSDBA'.

2. Enter a name for the database.

3. Select Unicode (UTF8) as the database character set to enable full multi-language functionality in Oracle CM SDK. Specifying a different database character set can limit Oracle CM SDK functionality.

   When you finish selecting the database details, the Oracle Database Configuration Assistant launches and creates the database, assigning it the name entered in step 2.

   After creating the database, log on to the database and change the system/manager and sys/change_on_install passwords (you can also do this during the Database Configuration Assistant process).

4. Use the command-line version of SQL*Plus to log on to the database and enter the following command to change the default SYS password:

   ALTER USER sys IDENTIFIED BY new_password;
   
   

Once the database is operational, create tablespaces for the various Oracle CM SDK schema objects, such as Oracle Text tables and indexes.

Creating Custom Tablespaces

During Oracle CM SDK configuration, you must select whether to store all schema objects in the USERS tablespace or in custom tablespaces. The USERS tablespace is not the optimal tablespace to use for a production environment, so Oracle recommends creating custom tablespaces for the various tables and indexes that comprise the system (see Table B-1) before attempting to configure Oracle CM SDK.

To create custom tablespaces for Oracle CM SDK, Oracle recommends that you create tablespaces as locally-managed tablespaces. Locally-managed tablespaces track all extent information in the tablespace itself, using bitmaps, resulting in simplified space allocation, ease of management, and performance benefits.

Locally-managed tablespaces have been available since Oracle 8.1. Beginning with the Oracle 10g Database Server, locally-managed is the default for all non-SYSTEM permanent tablespaces whenever the type of extent management is not explicitly specified.

The following is an example of the SQL syntax used to create custom tablespaces:

CREATE TABLESPACE "tbspname" 
LOGGING 
DATAFILE 'D:\oradata\sidname\tbspname_01.dbf' SIZE 50M EXTENT MANAGEMENT LOCAL AUTOEXTEND

• If you create locally-managed custom tablespaces, use the default options. Specifically, use the default value for the segment-space management type. The default value is manual. Most Oracle CM SDK data is stored as LOBs, and automatic segment-space management does not support LOBs. By default, locally-managed tablespaces are created correctly for use with Oracle CM SDK.

• Create custom tablespaces on disk storage appropriate for your implementation. See the Oracle9i Database Performance Tuning Guide and Reference for more information.

See Table B-1 for additional information about the various custom tablespaces and what they contain. Use the table to note the names and specific information about the custom tablespaces that you create.

For more information about creating tablespaces and about locally-managed tablespaces, see the Oracle Database Administrator's Guide.